ASIO DirectX Full Duplex Driver: Instant Crash after changing buffer size

[user]

Changed sample rate in audio prefs, buze crashed *regular windows error (send report garbage) when reopening now have sound buffer setting on a bad setting, when trying to change it back to normal, buze will crash and not remember where it is, therfore currently stuck with bad samplerate and unable to change it back. please help cheers

[user]

sorry replace the words Sample rate with *Buffer size in the above ticket

[user]

This problem was rectified by changing the buffer size back via the registry;

Click start, run and enter the following command ; regedit

Expand HKEY_CURRENT_USER / SOFTWARE / ZZUB / BUZE / AUDIODEVICE

You can then edit BufferSize? by right clicking on it and chosing Modify

200 (hexadecimal) will be 11.61ms (512) the default setting

[calvin]

do you remember what buffer size you set to, and whether it was an asio device or a dsound device you set it on?

or actually - could you please create two dumps of the entire HKEY_CURRENT_USER / SOFTWARE / ZZUB / BUZE / AUDIODEVICE branch into a comment below - one dump where it crashes and one where it works after having adjusted the buffer size? thanks!

[user]

This is the proper settings (Defualt) that work fine for me in buze

[user]

Theese settings cause my buze to give the windows error crash, and unable to reopen or change settings in Buze

[user]

Basically i think its pretty simple fact that my sound card wont support that buffer rate? never the less it becomes unstable and you cant switch it so i took the liberty of creating a .reg file that sets your audio preferences of Buze back to default. This BuzeFix? zip file can be found @ buzzchurch.com on the second page of the BUZE thread.

Hope theese regs help, as its the least i can do

zip

[calvin]

apparently this is a driver problem, in particular with the driver called "ASIO DirectX Full Duplex Driver". IIRC this driver comes with some adobe product such as Premiere or Cubase.

This link describes what looks like the exact same problem with portaudio - any buffer size != 512 fails: http://techweb.rfa.org/pipermail/portaudio/2002-December/001366.html

No solution though, it will need more googling and probably modifications in rtaudio, which is what we're using instead of portaudio.