PlanetZ forums - scopeusers.com

I am just in the process of updating my Scope PCI cards machine to Scope 5, and while installing thought I would check some of the devices out again. But when using RD Drum I keep getting this error when loading presets from the wavelength bank. I think it is to do with "WAV Osc+AD Env.dev" module which is one of the RD Drum modules. Sometimes the module will load the sample fine but most of the time it just freezes Scope and I sometimes even get a BSOD. I am pretty sure it is that module, but possibly also "WAV Osc II.mdl" module which is in the RD II modules collection.

Loading the presets in the factory bank work fine as they reference different modules and none of those use the WAV Osc+AD Env.dev module.

I thought it might be due to an incompatibility with Scope 5 for PCI but I also just tried it on my other partition where I still have Scope 4.5 and the same thing happens.

Can anyone who has RD Drum and RD Drum modules and the RD II modules please try this out. Please try loading up RD Drum and check through the wavelength bank of presets. Thanks.

I will email John Bowen about this too and see if he has any ideas or can verify it as a bug.

Cheers

t_t

probably not of much use, but the Hummel bank worked without a glitch here... on the external box with Win98...

cheers, Tom

Hi Tom,

Thanks for the feedback. Hmm....not sure what the problem is then. I haven't used RD Drum for a while but as I mentioned previously the factory bank presets load fine and I can switch between any of them without a problem, although of course it takes a few secs for the different modules to load. None of those factory presets use the Wav OSC+ AD Env module or the WAV OSC II module whereas all the wavelength presets do, and although sometimes one of them will load up ok but not always, and the module itself just freezes stating that it is loading the wave file. And worst case it crashes Scope or gives a BSOD.

Anyway, I will try out some other things, probably try to make some presets with those modules and see if they work or not. It's not a massive issue, but would be good to figure out how to fix it.

Thanks again.

Tim

yeah, me too didn't use it much - it's a great device, but takes it's time to setup.
I never had midi crashes under Win98 and never experienced the infamous 'missing file bla bla' dialog either.
There are big differences in file handling between the respective OS versions, and it's likely an access problem: the wave file is 'blocked' for whatever reason and the osc module tries to load it anyway (or rather the invalid buffer) - crash.
That's why I'd like to keep up the outdated box - it's nothing on it but Scope booting from a 2GB compact flash thingy.

cheers, Tom

Yes it does take a bit of time to get configured although once you get used to it it's not too taxing. But yes it could be some kind of access problem, not getting access to the audio buffer each time the different wave files are loaded into the wave modules. Anyway, I was trying it out again last night and it worked fine when switching between patches in the wavelength bank. I'll try again later and see if it works properly again. Very strange.

And thanks again for the replies