Audio Drivers in SX3
Hi,
I recently installed Cubase SX3; now I can't get access to the ASIO-Ports nor to the XTC mode. All I see in SX3 connections menu are the Scope hardware I/O's. When I swap to Scope App during playback, then playback stops. In SX1 everything works perfect.
Any chance to get it to work without reinstalling Scope (btw: It's Vers.4)
Kind regards, Gunnar
I recently installed Cubase SX3; now I can't get access to the ASIO-Ports nor to the XTC mode. All I see in SX3 connections menu are the Scope hardware I/O's. When I swap to Scope App during playback, then playback stops. In SX1 everything works perfect.
Any chance to get it to work without reinstalling Scope (btw: It's Vers.4)
Kind regards, Gunnar
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
(for non-XTC mode:)Krabat wrote:
I recently installed Cubase SX3; now I can't get access to the ASIO-Ports nor to the XTC mode. All I see in SX3 connections menu are the Scope hardware I/O's.
In SX2 / SX3, you have to set-up the 'VST connections' yourself (i.e. "manually").
Make sure that you have the correct (scope) ASIO driver selected in the VST Multitrack dislog, then select the 'VST connections' menu item and add input & output busses as required, connecting them up to the ASIO busses as you see fit (you can freely assign I/O busses to ASIO busses).
I can't help with the XTC mode stuff, as I never use that!
You've got the "unload ASIO driver in background" checkbox ticked in the VST Multitrack dialog - uncheck this box.When I swap to Scope App during playback, then playback stops.
HTH,
Royston
Well,.... I missed that. Thanks.
You've got the "unload ASIO driver in background" checkbox ticked in the VST Multitrack dialog - uncheck this box.
About the other points: It did confuse me, that the outputs are named 'Scope 16-bit', 'Pulsar SP-DIF' and 'Merge'. They are - in fact - all ASIO-Ports (which all are routed to the STM 1632); don't know, where they got their names from...
XTC: I don't use it either. I just tried to find the reason for the problems, so I tested it out. As it works with SX1 (although I get the message ' XTC does not work...'), I think it's a Cubase configuration problem. Maybe I find it uot later...
THANX for help, Gunnar
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
That's why I thought you were in XTC mode...one can't "see" the creamware hardware I/O from inside Cubase (as far as I understand things). Which ASIO modules are you using by the way? Maybe that makes a difference in terms of how Cubase names things (?)Krabat wrote:
About the other points: It did confuse me, that the outputs are named 'Scope 16-bit', 'Pulsar SP-DIF' and 'Merge'. They are - in fact - all ASIO-Ports (which all are routed to the STM 1632); don't know, where they got their names from...
Personally, I don't like the new "VST Connections" setup in Cubase, but at least you can save your connections as a preset after you've set them all up.
Royston
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
Well, that were my thoughts too, and that's why I tried to activate XTC-mode.On 2004-11-17 04:01, Counterparts wrote:
That's why I thought you were in XTC mode...one can't "see" the creamware hardware I/O from inside Cubase (as far as I understand things).
It have been the simple ASIO1 16Bit-modules. But the naming is the same with ASIO2 24bit.Which ASIO modules are you using by the way? Maybe that makes a difference in terms of how Cubase names things (?)
I would prefer a routing matrix like in scope, tooPersonally, I don't like the new "VST Connections" setup in Cubase, but at least you can save your connections as a preset after you've set them all up.

Regards, Gunnar