I'm running Cubase SX 2.2.0 on an XP machine with a Pulsar 2 (Scope v4.0). When I run the ASIO Multimedia test I get the following message:
"Not all the selected devices in the current configuration were successfully tested with their selected options.
If this card is currently configured to accept a digital signal, and no digital signal is present, please either reconfigure the card to use an 'internal clock', or apply a digital signal, or if possible switch this port to accept an analog input."
Also I am able to perform audio mixdown to mp3 fine in SX unless I am using XTC effects, in which case the sound is badly distorted. I suspect these two problems are correlated.
Can anyone help me please?
ASIO Multimedia test fails with Cubase SX2
the test is meaningless. you must have WAV drivers in your routing window for the test to work. when using sx, you should choose asio scope. the scope card is not a traditional sound card, the parameters normally handled in sx(like latency) are handled in scope. midi and audio drivers must be in your scope project(including configuring the number of asio ports) BEFORE opening cubase.
since xtc effects are not native effects, but are really external effects, offline mixdowns don't work you must do the export in realtime.
since xtc effects are not native effects, but are really external effects, offline mixdowns don't work you must do the export in realtime.
-
- Posts: 22
- Joined: Sat Feb 05, 2005 4:00 pm
Thanks for your prompt post, GaryB.
A couple of follow up questions/points of clarification:
"you must have WAV drivers in your routing window"
>> what do you mean by 'WAV driver'?
>> what do you mean by 'routing window'?
"when using sx, you should choose asio scope."
>> where is this selection made?
"midi and audio drivers must be in your scope project(including configuring the number of asio ports) BEFORE opening cubase."
>> can you provide more detail on what you mean, here?
"you must do the export in realtime"
>> meaning, as an interin step, bounce the entire set of existing tracks to a new, single audio track in SX and then export from that track to mp3?
A couple of follow up questions/points of clarification:
"you must have WAV drivers in your routing window"
>> what do you mean by 'WAV driver'?
>> what do you mean by 'routing window'?
"when using sx, you should choose asio scope."
>> where is this selection made?
"midi and audio drivers must be in your scope project(including configuring the number of asio ports) BEFORE opening cubase."
>> can you provide more detail on what you mean, here?
"you must do the export in realtime"
>> meaning, as an interin step, bounce the entire set of existing tracks to a new, single audio track in SX and then export from that track to mp3?
obviously, you are only using xtc mode, not even checking out scope mode, and are therefore not taking advantage of the platform's real strengths. ok, that's your perogative, although i prefer to track in scope mode as it is far more flexible and useful for music production. scope mode uses a routing window, a virtual room/patchbay where you connect devices, i/o and applications. it behooves you to learn this mode even if you use xtc mode because there is an xtc project in scope/app/xtcapp called xtcproject.pro which has the i/o and routing assignments in it. you also might want to learn about traditional music production(recording studio texchniques and connections) as that is what is being modeled.On 2005-02-06 22:59, thebard2903 wrote:
>> what do you mean by 'WAV driver'?
>> what do you mean by 'routing window'?
"when using sx, you should choose asio scope."
>> where is this selection made?
"midi and audio drivers must be in your scope project(including configuring the number of asio ports) BEFORE opening cubase."
>> can you provide more detail on what you mean, here?
"you must do the export in realtime"
>> meaning, as an interin step, bounce the entire set of existing tracks to a new, single audio track in SX and then export from that track to mp3?
the bounce option you mentioned would work if the bounce was real-time, but i was talking about checking "real-time export" when exporting. the scope platform would allow you to(depending on total resource usage by your mix) open another app such as wavelab or samplitude, etc and using a wav dest module to connect to that ap stream from one program to another(using asio drivers in sx pressing play and using wav drivers in wavelab pressing record for example), using one app as a multitrack deck and another as a 2 track deck. you could also mix down to a new track in sx.
if none of this makes much sense, you really need to study the manual and then mess with scope mode. you really can't break it....
-
- Posts: 22
- Joined: Sat Feb 05, 2005 4:00 pm
-
- Posts: 22
- Joined: Sat Feb 05, 2005 4:00 pm