PlanetZ forums - scopeusers.com

Tried this on WC Pro one and sb 404, it could work with the others also.

To test the workaround do it as it follows:

open a sequencer preset, or make some changes to the sequencer

as it is buggy, you will hear no changes

open samplerate settings

switch from master to slave and back (or the inverse, it depends on your setup) to reset the dsp's

now the sequencer should sound in the right way

everytime you change the sequencer settings the workaround must be applied.

i know this is not a final solution

Cool. annoying thing is that doing this means closing anything that uses the asio and re opening after (such as Cubase).
Or is that only needed when you change the sample rate?

ooh yeah, quite xited to test this out as this (along with the modular sequencer bug) is THE bug that annoys me most.

Awesome. Updated trouble shooting guide with these 2 tips.

http://www.hitfoundry.com/tsg/tsg_mast.htm

I've found that instead of changing from master to slave, change the samplerate from, for example 44hz to 33hz and back and you can keep stuff connected (with whatever software you have connected to asio etc just moaning about a samplerate change)

both accomplish the same thing, reloading the dsps.

garyb wrote:both accomplish the same thing, reloading the dsps.

Yeah indeed, but changing the master setting, for me, would lose asio connection from cubase and you would have to go in to cubase and re connect or restart it as it would crash etc. Changing the actual rate just causes cubase to produce a pop up window saying samplerate has changed, so no extra messing around.

yes, it's something to be done when asio apps are closed, also assigning back and forth to different dsp does the same and in that case asio is not involved an cubase should be ok

djmicron wrote:yes, it's something to be done when asio apps are closed, also assigning back and forth to different dsp does the same and in that case asio is not involved an cubase should be ok

Ah. Dsp re assign, that's the quickest option! Thanks for that info.
Cheers for working this all out in the first place.