anyone having recording problems with MOTU 2408 in Acid and
Vegas? my tracks are recorded with a delay proportional to
the Buffer Size value in the PCI324 console... this value
should influence monitoring latency, not the timing of
recordings to disk... this means that if I record new
tracks at higher Buffer Size values (1024, 4096, 8192...
iusefeul for minimum CPU strain...) I can clearly hear an
echo effect in the new audio parts... at minimum settings
(high CPU strain...) the delay is almost 0, but still there
if you zoom and analize the waveform... BTW, it's not my
own bad playing... just recorded the click track in a loop
to be rperfectly sure...
I suspect a fault in MOTU 2408 Wave driver (ASIO one works
perfectly in Cubase... sample accurate)... if this is
really true (anyone the same problem?) the MOTU2408 is not
compatible with "wave driver" applications like Vegas,
Acid, COol Edit PRO (all tested and all not working right,
timing wise...).
BTW, this is the mail I sent to tech support (at the moment
they have still no idea...)
anyone can help me? SF staff?
I'm going mad
ciao
leo
>>Hi
>>
>>I'd like to know if does exist any known problem
recording with the MOTU2408
>>using multimedia drivers...
>>In Acid and Vegas I got my recorded tracks delayed of the
same latency/buffer size
>>choosen in the PCI324 console... why?
>>for testing purposes I've recorded in a new audio track
the click track I
>>use as a reference in Acid... with minimum buffer
settings the new track is
>>"almost" no delayed, at max settings the new track sounds
like an echo...
>>In VST, using the ASIO driver the timing is rock solid...
no "flanging" at
>>all between the recorded track and the click...
>>maybe is a problem regarding only windows multimedia
drivers?
>>
>>at the moment I have installed the latest ASIO2 drivers.
Vegas? my tracks are recorded with a delay proportional to
the Buffer Size value in the PCI324 console... this value
should influence monitoring latency, not the timing of
recordings to disk... this means that if I record new
tracks at higher Buffer Size values (1024, 4096, 8192...
iusefeul for minimum CPU strain...) I can clearly hear an
echo effect in the new audio parts... at minimum settings
(high CPU strain...) the delay is almost 0, but still there
if you zoom and analize the waveform... BTW, it's not my
own bad playing... just recorded the click track in a loop
to be rperfectly sure...
I suspect a fault in MOTU 2408 Wave driver (ASIO one works
perfectly in Cubase... sample accurate)... if this is
really true (anyone the same problem?) the MOTU2408 is not
compatible with "wave driver" applications like Vegas,
Acid, COol Edit PRO (all tested and all not working right,
timing wise...).
BTW, this is the mail I sent to tech support (at the moment
they have still no idea...)
anyone can help me? SF staff?
I'm going mad
ciao
leo
>>Hi
>>
>>I'd like to know if does exist any known problem
recording with the MOTU2408
>>using multimedia drivers...
>>In Acid and Vegas I got my recorded tracks delayed of the
same latency/buffer size
>>choosen in the PCI324 console... why?
>>for testing purposes I've recorded in a new audio track
the click track I
>>use as a reference in Acid... with minimum buffer
settings the new track is
>>"almost" no delayed, at max settings the new track sounds
like an echo...
>>In VST, using the ASIO driver the timing is rock solid...
no "flanging" at
>>all between the recorded track and the click...
>>maybe is a problem regarding only windows multimedia
drivers?
>>
>>at the moment I have installed the latest ASIO2 drivers.