Pulsar II plus low input level...
use asio16bit or asio216bit drivers in the scope routing window and choose "asioSCOPE" in the device setup in cubase.
better yet, use 24bit drivers and record in 24bit. then you'll have 8bits of headroom since your final mix will be 16bit and you won't have to worry so much that you have hot, hot levels. you'll get the same resolution you get from a signal near the top of the meters in 16bit when the signal is halfway up the meter in 24bit......
better yet, use 24bit drivers and record in 24bit. then you'll have 8bits of headroom since your final mix will be 16bit and you won't have to worry so much that you have hot, hot levels. you'll get the same resolution you get from a signal near the top of the meters in 16bit when the signal is halfway up the meter in 24bit......
what device doesn't work in xtc mode?
xtc mode has it's own project in app/xtcapp called xtcproject.pro
i can't think of a reason to use xtc mode, but there are plenty who disagree with me.....it's an illusion that xtc mode is easier, at least for me. i like scope mode and it's easy to edit projects....
xtc mode has it's own project in app/xtcapp called xtcproject.pro
i can't think of a reason to use xtc mode, but there are plenty who disagree with me.....it's an illusion that xtc mode is easier, at least for me. i like scope mode and it's easy to edit projects....
Gary, if I use the booster without xtc mode all works Well, If I personalize the XTCpro template with Booster, there is no input sound in recording mode (XTC mode).
I've try to set 24Bit asio drivers and I've set Project properties to 24bit... nothing, the presonus amplifier is at maximum level to abtain -16 in cubase input. The pulsar 2 is the plus model, with balanced connection
I've try to set 24Bit asio drivers and I've set Project properties to 24bit... nothing, the presonus amplifier is at maximum level to abtain -16 in cubase input. The pulsar 2 is the plus model, with balanced connection
you don't specify what's send over the Adat port, but if it's digital content from another Adat device (like an RME card for example) then the software may contain a messed module.On 2006-07-18 12:07, Demmy71 wrote:
...The problem exists both, with analog input and if I use the ADAT input. ...
All levels are controlled by software only.
if it's an Adat converter box (like the A16) then it usually has switches for +4/-10db settings.
you could build an Adat loopback where:
a Scope synth is connected to a mixer
the mixer's out to adat destination
the respective adat source to another mixer
the synth should produce a reasonable level on the 1st mixer and the 2nd mixer should display the same value
cheers, Tom
run the i/o enabler and let scope know that you want to use i/o w/ xtc(it's in your scope or sfp folder in the IOenabler folder). this is an inconsistent feature in the installer, sometimes people just miss it....
as to the low level, if you're putting a -20 pre into the +4 analog ins of the scope card, the level WILL be low. just add some gain in the scope mixer. in xtc mode, you will have to add gain in the cubase mixer. the presonus may have a +4/-20 switch in which case you can change it there, otherwise, at least your bit depth won't be too bad because you are recording at 24bit....with the adat input, as astro said, the input of the ad/da may be switchable...
<font size=-1>[ This Message was edited by: garyb on 2006-07-21 18:11 ]</font>
as to the low level, if you're putting a -20 pre into the +4 analog ins of the scope card, the level WILL be low. just add some gain in the scope mixer. in xtc mode, you will have to add gain in the cubase mixer. the presonus may have a +4/-20 switch in which case you can change it there, otherwise, at least your bit depth won't be too bad because you are recording at 24bit....with the adat input, as astro said, the input of the ad/da may be switchable...
<font size=-1>[ This Message was edited by: garyb on 2006-07-21 18:11 ]</font>