bb.linuxsampler.org

OK, one last post...

I think that the problem is with 32-bit and 64-bit operations or with the 48khz sample mode inside Sonar.

After switching to 44.1 khz and 24 bit, the problem disappeared...

I reproduced the crash with the demo version, on Windows XP, but it is not consistent, sometimes it works flawlessly. Try this: Start Sonar with WDM audio driver and create a new Linuxsampler synth track. Open a GIG file. Save the Sonar project. Now change the WDM driver to ASIO. There is a crash wh...

I installed my whole DAW system on a Windows Vista PC. No luck. The same bug persist under Vista too, but only if the ASIO driver is in use. I think it is a bug connected with the ASIO drivers. This can be the cause of the difference between the demo and full version of Sonar. The demo version is no...

After debugging it seems that the problem is with LinuxSampler32.dll. "I was told".

Maybe you should contact Cakewalk...

Unfortunately I'm not sure anymore that Linuxsampler VSTi and Sonar 8 full version are working together under Vista because I installed only a demo/trial version of Sonar 8 which works with Linuxsampler VSTi under XP too.

Hi, Sbenno wrote: Or alternatively we could ask them if they give us a Sonar license for development purposes. You should absolutely try that because Sonar is the most popular DAW under Windows in Europe too. If Linuxsampler works in Sonar as a VSTi it will be a true revolution (because of the hardd...

OK. It must be the difference between the trial version and the full version. I uninstalled the full version and installed the trial version and there is no crash at all. After I reinstalled the full version, there is the bug again, it is an "unhandled exception" c000005. I think Sonar 8 full versio...

I tried to reproduce the bug under Windows Vista but Linuxsampler works perfectly there. You can save and load without any problems.

So it seems it is a Windows XP (SP 3) specific problem. Some kind of missing registry?

Hi, Thanks for your reply. This is the part of the dmp file I succeded to view with windbg: Loading unloaded module list ......... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (fe0.f78): Access violation - code c0000005 (first/...

Any new information about this bug? Will it be fixed in a new release? How much time should it take?

I have to point out that in any case all users should be thankful for your excellent work with this project. So I'm not rushing things - I'm just curious.