I hope you don't mind me not installing VB6. I hav eno time at this moment to get into that.


Still crashing (without giving an error message).
With this version (but perhaps also the earlier version, did not check): if I press 'Ramsete -> WAV' button' and then 'Ramsete -> .TIM' it crashes (again without message)

Does that help?

All the best,


Victor


No need, but thanks for telling what program arguments I have to give when using rams2wav.exe (the file name for the octave filter I would not have guessed!).
And don't rewrite the manual, as using rams2wav.exe is I hope not the preferred way of doing things.

All the best,


Victor

Of course, RAMS2WAV is an old DOS program, it is not using anything...
The crash occurs in the GUI of AudioConverter, which is written in Visual Basic 6. It is certainly due to some incompatibility with some of your OCX/DLL files.
The only way for me to debug this problem, is if you can send me your copy of your OCX/DLL files (of course, only those having the same name as those contained in the CAB file). You could pack them inside a ZIP container, and post it on your web storage space, then send me the link to it...
Thanks
Bye

[QUOTE=angelo.farina,22/7/2009, 12:01]

Understand.
I tried to run it using the arguments I thought were good (bcove-02.__a, wavtest.wav, 1,44100,w,N). And it produces the file. That is a workaround. THANKS.

Will do later on the day. Now I will go fro a swim;-)

All the best,


Victor

I just send them by separate e-mail.

All the best,


Victor

Please, can you send me a link to the Zip file instead? My server thought that these files are of illegal type, and destroyed your message...

Here is the file
<it seems rapidshare is very handy service to share files (up to 200 MByte, no costs and no account)>

All the best,


Victor

Downloaded your files from Rapidshare.
However, I compared them with mine, they are byte-by-byte identical...

So this is not the cause of your problem. Let's investigate something else.
Are you perhaps using Windows Vista? Are you running with Administrator privileges, or as a normal user?
If your are not administrator, can you check what happens if you set the properties for audiocnv.exe to run as administrator?
Finally, it is very suspicious that the program crashes when you attempt to browse the current directory (which should be C:\Ramsete25). Can you check that there are no strange access limitations on that directory, and that everyone can read and write inside it?
If it comes out that the problem is Vista-related, I can borrow a computer with Windows Vista for attempting to replicate the problem.
Here no-one is using Vista, indeed, so I am not 100% sure that all the modules of Ramsete are tested to work in any configuration of Vista (particularly with reference to the usage under restricted permissions, as some Vista users are doing).

Hello Angelo,


Ok tested on an older laptop here at home. It (with audiocnv.CAB of 21/7/2009) works on this old laptop! Again I only loaded your AudioConvertor2.5 and ramsete.ini.

I can make the impulse responses. So what is the difference between my old and new laptop?
They both are Windows XP Pro Version 2002 SP3. The new one is faster.
Checked the dll/ocx file lengths on the two computer: they are the same...

All the best,


Victor

Edited by vreijs - 22/7/2009, 23:30

So XP Pro or Home XP3 have problems. I have now two computer where it works and two were it does not work.
In all case the user has 'Computer administrator' privelages.
But it seems there is a difference between the first 'Computer administrator' and the second one (the one setup by the first 'Computer Administrator'), at least for audiocnv.exe...
On some PCs the second 'Computer administrator' is not able to run properly audiocnv.exe except when I let audiocnv.exe 'Run as...' (right clicking on audocnv.exe icon) under the first 'Computer administrator'.
So it seems that 'Computer administrator' rights are not enough! This is weird behavior.
With first 'Computer Administrator' the 'Run as..' is only remembered once...

So even if one is 'Computer administrator', on some systems 'Run as...' still needs to be set to the first 'Computer Administrator'!
Have no clue why on some systems it works correct: in 50% of my PCs it runs under the second 'Computer administrator' without additional 'Run as..'.

Does this help in solving the problem? And I hope this behavior can be changed.

Thanks.

All the best,

Victor

Edited by vreijs - 24/7/2009, 13:01