Hi
I've just started getting this error message when i run nuendo4. it seems to be saying that it can't see the ASIO modules. i definitely have them loaded in the project and the wave source/dest modules are working fine so the cards are basically working. i don't have any other software that uses ASIO to check, but i can still use my other audio interfaces with nuendo, so i'm guessing the problem is with the cards.
thanks for any suggestions
Problem loading Nuendo4
Problem loading Nuendo4
Pulsar2, Powersampler, Luna2496, Scope 4.5, Intel 2.6G QuadCore, 4G RAM, Nuendo 4.
no, it's more likely how Nuendo 4 handles the the Scope Asio driver and was reported recently by a couple of users in context with other sampling rates than 44.1k.
The workaround was to set Scope to 44.1k, start Nuendo and then switch the samplingrate to 48 (or 96k) in the Scope environment.
The problem does not exist with Nuendo 3, so the source is Steinberg not testing with Scope cards (anymore)
cheers, Tom
The workaround was to set Scope to 44.1k, start Nuendo and then switch the samplingrate to 48 (or 96k) in the Scope environment.
The problem does not exist with Nuendo 3, so the source is Steinberg not testing with Scope cards (anymore)
cheers, Tom
That workaround did the trick. Thanks 
It's a shame i didn't encounter it in time to make request a fix before the recent nuendo update, but i'll add it to my list of bugs that i've found in N4 for next time.
Thanks again.
It's a shame i didn't encounter it in time to make request a fix before the recent nuendo update, but i'll add it to my list of bugs that i've found in N4 for next time.
Thanks again.
Pulsar2, Powersampler, Luna2496, Scope 4.5, Intel 2.6G QuadCore, 4G RAM, Nuendo 4.
hello. me again. just to let you know, i just had a hunt on the steinberg forum for this problem and this is what the moderators had to say about it:
Changes have been made to the ASIO protocol for 4.1.
Most likely, these changes have revealed a bug/design flaw in the Creamware ASIO driver.
Of course, it can be a Nuendo bug too, but then almost every other card would have been affected too, and that's not the case.
I'll have a look into the internal Devtrack if this issue is reported, and if not i will enter a bug report for it.
then
PostPosted: Wed Dec 12, 2007 9:03 am .
Please don't overblow this whole issue.
There are no (major) problems found with any of the Sonic Cards, with the exception of the Creamware Scope card.
This card didn't had the same driver for almost 5 years now, and needs to be updated by them.
For that card, the driver update needs to come from the hardware manufacturer. There is nothing that Steinberg can do about this.
you may have seen this already, but just thought it might be helpful.
Changes have been made to the ASIO protocol for 4.1.
Most likely, these changes have revealed a bug/design flaw in the Creamware ASIO driver.
Of course, it can be a Nuendo bug too, but then almost every other card would have been affected too, and that's not the case.
I'll have a look into the internal Devtrack if this issue is reported, and if not i will enter a bug report for it.
then
PostPosted: Wed Dec 12, 2007 9:03 am .
Please don't overblow this whole issue.
There are no (major) problems found with any of the Sonic Cards, with the exception of the Creamware Scope card.
This card didn't had the same driver for almost 5 years now, and needs to be updated by them.
For that card, the driver update needs to come from the hardware manufacturer. There is nothing that Steinberg can do about this.
you may have seen this already, but just thought it might be helpful.
Pulsar2, Powersampler, Luna2496, Scope 4.5, Intel 2.6G QuadCore, 4G RAM, Nuendo 4.
yes, I've remember having read about it...
pretty lame excuse, as usual
... most likely this revealed... because of 5 years non-updating... LMAO
I wrote a piece of software once (1994) that used a driver which was written around 1990 and this thing was an office core application until 2003 without one single bit changed.
Mac OS went from 7 to 9 to OSX 10.2 with this same app unaltered.
Oh yes, it got one problem in it's final years...
M$'s in it's omnipotence started to mess the keyboard interupt handling (obviously patching the system) with their sh*tty office package - wtf has M$ to fiddle with an OS that isn't even their own ???
So whenever Word was running in the background, my app complained about an unknown interrupt.
Certainly a design flaw by me because I didn't foresee this possibility 10 years ago
cheers, Tom
pretty lame excuse, as usual
... most likely this revealed... because of 5 years non-updating... LMAO
I wrote a piece of software once (1994) that used a driver which was written around 1990 and this thing was an office core application until 2003 without one single bit changed.
Mac OS went from 7 to 9 to OSX 10.2 with this same app unaltered.
Oh yes, it got one problem in it's final years...
M$'s in it's omnipotence started to mess the keyboard interupt handling (obviously patching the system) with their sh*tty office package - wtf has M$ to fiddle with an OS that isn't even their own ???
So whenever Word was running in the background, my app complained about an unknown interrupt.
Certainly a design flaw by me because I didn't foresee this possibility 10 years ago
cheers, Tom
um
without wanting to play devil's advocate, steinberg may be completely in the wrong, but your customers probably don't really care too much about the ethics of it. i love creamware/sonic core gear but, at the end of the day, i could still perform my job adequately with a soundblaster card. however, i would be completely paralysed without nuendo. so, if i was faced with a choice between losing one or the other, it would regrettably have to be the soundcards. i'm sure there are a lot of your customers who are in the same position and steinberg are probably aware of this.
although you are, no doubt, right about who's responsibility this is, surely it would be better to bite the bullet and update the ASIO drivers, rather than risk losing loyal customers who just want to create hassle-free audio?
phobic
without wanting to play devil's advocate, steinberg may be completely in the wrong, but your customers probably don't really care too much about the ethics of it. i love creamware/sonic core gear but, at the end of the day, i could still perform my job adequately with a soundblaster card. however, i would be completely paralysed without nuendo. so, if i was faced with a choice between losing one or the other, it would regrettably have to be the soundcards. i'm sure there are a lot of your customers who are in the same position and steinberg are probably aware of this.
although you are, no doubt, right about who's responsibility this is, surely it would be better to bite the bullet and update the ASIO drivers, rather than risk losing loyal customers who just want to create hassle-free audio?
phobic
Pulsar2, Powersampler, Luna2496, Scope 4.5, Intel 2.6G QuadCore, 4G RAM, Nuendo 4.
just in case there was confusion, i'm not S/C and i have no control over what they do, but i'm sure they will update the driver.
i just resent steinberg's attitude on a personal level. they don't have to be jerks about the whole thing. i say this as a steinberg customer who prefers their sequencer, but has realized that all the other ones work just as well.
i just resent steinberg's attitude on a personal level. they don't have to be jerks about the whole thing. i say this as a steinberg customer who prefers their sequencer, but has realized that all the other ones work just as well.