Hi Keith,

We do this on a daily basis with less DAW power than you have.
Perhaps I can at least let you know what we do and see what the
difference is. First, unless I misunderstand you, I am a bit hazy on
why you are trying to synch Vegas to the DA-88's for the transfer?

KAC...


Keith wrote:
>>Okay, if I can do this, I will never need to open Cubase
>>VST24 ever again! I love Vegas. Mixing multitrack music
>>with recall is like a dream come true and it fulfills all
>>of my musical needs except---

Hi Keith
what is your setup? What type of midi interface are you using?
one of my tech's said that he's done this a few times but we got rid
of the Tascam and ADAT decks after we got Vegas.I still have one
Black face ADAT at home in my closet I can take it over to the
studio and hook it up if this will help you out? The only other HD
recorders we use are the Roland VS-1680,880 and the Fostex D-160.We
are using the MOTU Midi Timepiece AV with the 2408.

Keith wrote:
>>Okay, if I can do this, I will never need to open Cubase
>>VST24 ever again! I love Vegas. Mixing multitrack music
>>with recall is like a dream come true and it fulfills all
>>of my musical needs except---
>>I have not been able successfully transfer 24 tracks of
>>DA88 thru the 2408 into Vegas 1.0b.
>>What I have been doing is transferring the 24 tracks into
>>VST24(simultaneously- no problems), and then opening the
>>wavs in Vegas to do the editing... then re-opening VST with
>>the edited tracks and THEN transferring back to the DA88s.
>>Needless to say, it is quite a pain, but it works reliably.
>>
>>The best I can get Vegas to do- is a record a few seconds
>>of 24 track recording before it seems to choke and stops by
>>itself. Also, Vegas seems to chase to MTC for the first
>>take or so, then it stops syncing at all. Then I have to
>>close the program and re-open it to get it to sync again.
>>I don't think it's the MOTU, because the transfer happens
>>pretty reliably with VST. Help! I can't stand VST!
>>Anyone with a similar setup or suggestions? Perhaps I'm
>>missing something obvious? I run a PII 450 w/ IDE66 @
>>7200, 128 ram. No performance problems otherwise, and the
>>latest 2408 driver. Thanks, Keith

When Vegas "stops by itself" as you describe, is there an error msg
or any indication for why the stop occurred?

One overall suggestion when transferring large number of tracks from
MDM to Vegas. Disable SRP in the Options menu. This will save
considerable bandwidth of the PCI bus. Why? If Vegas is enabled for
SRP, then your mix bus is active as well since Vegas permits editing
during playback.

What we have typically seen as the biggest performance problem when
recording large number of tracks is the graphic card in a system.
Vegas draws the peaks during the record in real time. It is also
updateing the input meters in realtime. I have seen the number of
tracks/inputs that are recordable jump from 6 stereo on a system with
a Diamond Fire GL AGP to 20 stereo (all I had available) with a
Matrox G4000 Max.

We are working on ways to improve performance when recording large
numbers of tracks. We get so many different reports of how many then
can or can't record that there is no clear cut reason for somebody
achieving 24 tracks while another can't get 6 tracks.

Do you have a name for the tech support person that told you Vegas
was not designed for doing tracking like this?

Peter





Michael Martin wrote:
>>Keith,
>>I have been having similar problems while trying to transfer
>>Adat tracks to Vegas. (record for only a few seconds and stops by
>>itself) I have to use Alesis's AdatConnect much in the same way
>>as you are using VST24 to get Adat tracks into Vegas. Vegas has a
>>great interface and wonderful features. But "dang gummit" can't
>>somebody comes up with some better solutions. Sonic Foundry has
been
>>NO help to me regarding this matter. Why, even one of the Tech
Suport
>>persons told me that Vegas was not designed to be used for
tranfering
>>multi tracks. I politely said "Goodbye" Kinda makes "ya" wonder.
>>I mean what's the deal? Is this an issue of Soundcards, CPU,
>>MotherBoards, Sound Drivers, Chipsets? What?
>>Vegas has the best interface and features of any progran I have
>>seen. Let's hope somebody comes up with some better solutions.
>>
>>
>>Keith wrote:
>>>>Okay, if I can do this, I will never need to open Cubase
>>>>VST24 ever again! I love Vegas. Mixing multitrack music
>>>>with recall is like a dream come true and it fulfills all
>>>>of my musical needs except---
>>>>I have not been able successfully transfer 24 tracks of
>>>>DA88 thru the 2408 into Vegas 1.0b.
>>>>What I have been doing is transferring the 24 tracks into
>>>>VST24(simultaneously- no problems), and then opening the
>>>>wavs in Vegas to do the editing... then re-opening VST with
>>>>the edited tracks and THEN transferring back to the DA88s.
>>>>Needless to say, it is quite a pain, but it works reliably.
>>>>
>>>>The best I can get Vegas to do- is a record a few seconds
>>>>of 24 track recording before it seems to choke and stops by
>>>>itself. Also, Vegas seems to chase to MTC for the first
>>>>take or so, then it stops syncing at all. Then I have to
>>>>close the program and re-open it to get it to sync again.
>>>>I don't think it's the MOTU, because the transfer happens
>>>>pretty reliably with VST. Help! I can't stand VST!
>>>>Anyone with a similar setup or suggestions? Perhaps I'm
>>>>missing something obvious? I run a PII 450 w/ IDE66 @
>>>>7200, 128 ram. No performance problems otherwise, and the
>>>>latest 2408 driver. Thanks, Keith

Thanks for the responses folks!
Karl, the reason I prefer to transfer tracks from the DA88's to Vegas
in sync are that 1. Sometimes I need to tune up and edit just one or
two tracks and need to fly them back to the DA88's in the same
location on the tape. 2. Even if I edit and mix in Vegas, it is often
quicker to archive the altered tracks back to the DA88 instead of
saving all of the 24 bit wave data to CD disks with a client paying
for the time. But Karl, if you have had great success transferring
24 tracks digitally back and forth without MTC sync with a similar
setup, PLEASE let me know, cause I might be willing to move all 24
tracks back and forth to a different location on the DA88 tape - even
if it means using more
tape, just to avoid using VST for the transfer!

Peter, no, the recording just stops and displays 24 tracks of the few
seconds that it has just recorded- as if I had pressed the space bar
or something. No pop up screens or anything to show an error. It
does bypass asking whether to keep or rename the recorded tracks,
though. I was not the person who spoke to tech support on this
issue. By the way, I just finished an 8 hour session using only
Vegas for a client today and I did notice two things on my newly
uploaded Vegas 1.0b.
1. Like someone mentioned before, when I was recording many multiple
takes and replacing them for short punch- ins, the later punch-ins
sounded time delayed.
2. I've gotten pretty quick with splitting and moving short parts
of tracks around and I noticed more crashes during these maneuvers
than in 1.0a. Could be my computer was having a "bad hair day"
though. Thanks for the responses. Vegas is still the best thing out
there of it's kind. -Keith

Peter Haller wrote:
>>When Vegas "stops by itself" as you describe, is there an error msg
>>or any indication for why the stop occurred?
>>
>>One overall suggestion when transferring large number of tracks
from
>>MDM to Vegas. Disable SRP in the Options menu. This will save
>>considerable bandwidth of the PCI bus. Why? If Vegas is enabled for
>>SRP, then your mix bus is active as well since Vegas permits
editing
>>during playback.
>>
>>What we have typically seen as the biggest performance problem when
>>recording large number of tracks is the graphic card in a system.
>>Vegas draws the peaks during the record in real time. It is also
>>updateing the input meters in realtime. I have seen the number of
>>tracks/inputs that are recordable jump from 6 stereo on a system
with
>>a Diamond Fire GL AGP to 20 stereo (all I had available) with a
>>Matrox G4000 Max.
>>
>>We are working on ways to improve performance when recording large
>>numbers of tracks. We get so many different reports of how many
then
>>can or can't record that there is no clear cut reason for somebody
>>achieving 24 tracks while another can't get 6 tracks.
>>
>>Do you have a name for the tech support person that told you Vegas
>>was not designed for doing tracking like this?
>>
>>Peter
>>
>>
>>
>>
>>
>>Michael Martin wrote:
>>>>Keith,
>>>>I have been having similar problems while trying to transfer
>>>>Adat tracks to Vegas. (record for only a few seconds and stops by
>>>>itself) I have to use Alesis's AdatConnect much in the same way
>>>>as you are using VST24 to get Adat tracks into Vegas. Vegas has
a
>>>>great interface and wonderful features. But "dang gummit" can't
>>>>somebody comes up with some better solutions. Sonic Foundry has
>>been
>>>>NO help to me regarding this matter. Why, even one of the Tech
>>Suport
>>>>persons told me that Vegas was not designed to be used for
>>tranfering
>>>>multi tracks. I politely said "Goodbye" Kinda makes "ya" wonder.
>>>>I mean what's the deal? Is this an issue of Soundcards, CPU,
>>>>MotherBoards, Sound Drivers, Chipsets? What?
>>>>Vegas has the best interface and features of any progran I have
>>>>seen. Let's hope somebody comes up with some better solutions.
>>>>
>>>>
>>>>Keith wrote:
>>>>>>Okay, if I can do this, I will never need to open Cubase
>>>>>>VST24 ever again! I love Vegas. Mixing multitrack music
>>>>>>with recall is like a dream come true and it fulfills all
>>>>>>of my musical needs except---
>>>>>>I have not been able successfully transfer 24 tracks of
>>>>>>DA88 thru the 2408 into Vegas 1.0b.
>>>>>>What I have been doing is transferring the 24 tracks into
>>>>>>VST24(simultaneously- no problems), and then opening the
>>>>>>wavs in Vegas to do the editing... then re-opening VST with
>>>>>>the edited tracks and THEN transferring back to the DA88s.
>>>>>>Needless to say, it is quite a pain, but it works reliably.
>>>>>>
>>>>>>The best I can get Vegas to do- is a record a few seconds
>>>>>>of 24 track recording before it seems to choke and stops by
>>>>>>itself. Also, Vegas seems to chase to MTC for the first
>>>>>>take or so, then it stops syncing at all. Then I have to
>>>>>>close the program and re-open it to get it to sync again.
>>>>>>I don't think it's the MOTU, because the transfer happens
>>>>>>pretty reliably with VST. Help! I can't stand VST!
>>>>>>Anyone with a similar setup or suggestions? Perhaps I'm
>>>>>>missing something obvious? I run a PII 450 w/ IDE66 @
>>>>>>7200, 128 ram. No performance problems otherwise, and the
>>>>>>latest 2408 driver. Thanks, Keith

Keith:

How are you setting up for MTC sync? What is your MIDI device? What
is your Master MTC device?

I am looking at the problem with takes being out of sync.

Peter


Keith wrote:
>>Thanks for the responses folks!
>>Karl, the reason I prefer to transfer tracks from the DA88's to
Vegas
>>in sync are that 1. Sometimes I need to tune up and edit just one
or
>>two tracks and need to fly them back to the DA88's in the same
>>location on the tape. 2. Even if I edit and mix in Vegas, it is
often
>>quicker to archive the altered tracks back to the DA88 instead of
>>saving all of the 24 bit wave data to CD disks with a client paying
>>for the time. But Karl, if you have had great success transferring
>>24 tracks digitally back and forth without MTC sync with a similar
>>setup, PLEASE let me know, cause I might be willing to move all 24
>>tracks back and forth to a different location on the DA88 tape -
even
>>if it means using more
>>tape, just to avoid using VST for the transfer!
>>
>>Peter, no, the recording just stops and displays 24 tracks of the
few
>>seconds that it has just recorded- as if I had pressed the space
bar
>>or something. No pop up screens or anything to show an error. It
>>does bypass asking whether to keep or rename the recorded tracks,
>>though. I was not the person who spoke to tech support on this
>>issue. By the way, I just finished an 8 hour session using only
>>Vegas for a client today and I did notice two things on my newly
>>uploaded Vegas 1.0b.
>>1. Like someone mentioned before, when I was recording many
multiple
>>takes and replacing them for short punch- ins, the later punch-ins
>>sounded time delayed.
>>2. I've gotten pretty quick with splitting and moving short parts
>>of tracks around and I noticed more crashes during these maneuvers
>>than in 1.0a. Could be my computer was having a "bad hair day"
>>though. Thanks for the responses. Vegas is still the best thing
out
>>there of it's kind. -Keith
>>
>>Peter Haller wrote:
>>>>When Vegas "stops by itself" as you describe, is there an error
msg
>>>>or any indication for why the stop occurred?
>>>>
>>>>One overall suggestion when transferring large number of tracks
>>from
>>>>MDM to Vegas. Disable SRP in the Options menu. This will save
>>>>considerable bandwidth of the PCI bus. Why? If Vegas is enabled
for
>>>>SRP, then your mix bus is active as well since Vegas permits
>>editing
>>>>during playback.
>>>>
>>>>What we have typically seen as the biggest performance problem
when
>>>>recording large number of tracks is the graphic card in a system.
>>>>Vegas draws the peaks during the record in real time. It is also
>>>>updateing the input meters in realtime. I have seen the number
of
>>>>tracks/inputs that are recordable jump from 6 stereo on a system
>>with
>>>>a Diamond Fire GL AGP to 20 stereo (all I had available) with a
>>>>Matrox G4000 Max.
>>>>
>>>>We are working on ways to improve performance when recording
large
>>>>numbers of tracks. We get so many different reports of how many
>>then
>>>>can or can't record that there is no clear cut reason for
somebody
>>>>achieving 24 tracks while another can't get 6 tracks.
>>>>
>>>>Do you have a name for the tech support person that told you
Vegas
>>>>was not designed for doing tracking like this?
>>>>
>>>>Peter
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>Michael Martin wrote:
>>>>>>Keith,
>>>>>>I have been having similar problems while trying to transfer
>>>>>>Adat tracks to Vegas. (record for only a few seconds and stops
by
>>>>>>itself) I have to use Alesis's AdatConnect much in the same way
>>>>>>as you are using VST24 to get Adat tracks into Vegas. Vegas
has
>>a
>>>>>>great interface and wonderful features. But "dang gummit"
can't
>>>>>>somebody comes up with some better solutions. Sonic Foundry
has
>>>>been
>>>>>>NO help to me regarding this matter. Why, even one of the Tech
>>>>Suport
>>>>>>persons told me that Vegas was not designed to be used for
>>>>tranfering
>>>>>>multi tracks. I politely said "Goodbye" Kinda makes "ya"
wonder.
>>>>>>I mean what's the deal? Is this an issue of Soundcards, CPU,
>>>>>>MotherBoards, Sound Drivers, Chipsets? What?
>>>>>>Vegas has the best interface and features of any progran I have
>>>>>>seen. Let's hope somebody comes up with some better solutions.
>>>>>>
>>>>>>
>>>>>>Keith wrote:
>>>>>>>>Okay, if I can do this, I will never need to open Cubase
>>>>>>>>VST24 ever again! I love Vegas. Mixing multitrack music
>>>>>>>>with recall is like a dream come true and it fulfills all
>>>>>>>>of my musical needs except---
>>>>>>>>I have not been able successfully transfer 24 tracks of
>>>>>>>>DA88 thru the 2408 into Vegas 1.0b.
>>>>>>>>What I have been doing is transferring the 24 tracks into
>>>>>>>>VST24(simultaneously- no problems), and then opening the
>>>>>>>>wavs in Vegas to do the editing... then re-opening VST with
>>>>>>>>the edited tracks and THEN transferring back to the DA88s.
>>>>>>>>Needless to say, it is quite a pain, but it works reliably.
>>>>>>>>
>>>>>>>>The best I can get Vegas to do- is a record a few seconds
>>>>>>>>of 24 track recording before it seems to choke and stops by
>>>>>>>>itself. Also, Vegas seems to chase to MTC for the first
>>>>>>>>take or so, then it stops syncing at all. Then I have to
>>>>>>>>close the program and re-open it to get it to sync again.
>>>>>>>>I don't think it's the MOTU, because the transfer happens
>>>>>>>>pretty reliably with VST. Help! I can't stand VST!
>>>>>>>>Anyone with a similar setup or suggestions? Perhaps I'm
>>>>>>>>missing something obvious? I run a PII 450 w/ IDE66 @
>>>>>>>>7200, 128 ram. No performance problems otherwise, and the
>>>>>>>>latest 2408 driver. Thanks, Keith

Thanks, Peter.
Master MTC device is the SY88 in the first of the 3 DA88's. To set
up for MTC sync, I go to the 2408 assignment screen and change the
clock to MTC. In Vegas, I set the chase to MTC device in sync/prefs,
then chase to MTC in options.
MIDI device is Midiman Portman PC/S. This is the oldest link in the
chain, but it's been trusty for midi and MTC syncing with VST24 so
far. I do have a MOTU Digital Timepiece that I never use, because I
have previously been able to execute the transfer back and forth
between VST24 and the DA88's. I scoured last years posts and noticed
that you experienced crashing with the 2408's 324card and suggested
using a different slot in the computer, so I will check that out.
Keith

Midi interface is a Midiman Portman PC/S.
Peter Haller wrote:
>>Keith:
>>
>>How are you setting up for MTC sync? What is your MIDI device? What
>>is your Master MTC device?
>>
>>I am looking at the problem with takes being out of sync.
>>
>>Peter
>>
>>
>>Keith wrote:
>>>>Thanks for the responses folks!
>>>>Karl, the reason I prefer to transfer tracks from the DA88's to
>>Vegas
>>>>in sync are that 1. Sometimes I need to tune up and edit just one
>>or
>>>>two tracks and need to fly them back to the DA88's in the same
>>>>location on the tape. 2. Even if I edit and mix in Vegas, it is
>>often
>>>>quicker to archive the altered tracks back to the DA88 instead of
>>>>saving all of the 24 bit wave data to CD disks with a client
paying
>>>>for the time. But Karl, if you have had great success
transferring
>>>>24 tracks digitally back and forth without MTC sync with a
similar
>>>>setup, PLEASE let me know, cause I might be willing to move all
24
>>>>tracks back and forth to a different location on the DA88 tape -
>>even
>>>>if it means using more
>>>>tape, just to avoid using VST for the transfer!
>>>>
>>>>Peter, no, the recording just stops and displays 24 tracks of the
>>few
>>>>seconds that it has just recorded- as if I had pressed the space
>>bar
>>>>or something. No pop up screens or anything to show an error.
It
>>>>does bypass asking whether to keep or rename the recorded tracks,
>>>>though. I was not the person who spoke to tech support on this
>>>>issue. By the way, I just finished an 8 hour session using only
>>>>Vegas for a client today and I did notice two things on my newly
>>>>uploaded Vegas 1.0b.
>>>>1. Like someone mentioned before, when I was recording many
>>multiple
>>>>takes and replacing them for short punch- ins, the later punch-
ins
>>>>sounded time delayed.
>>>>2. I've gotten pretty quick with splitting and moving short parts
>>>>of tracks around and I noticed more crashes during these
maneuvers
>>>>than in 1.0a. Could be my computer was having a "bad hair day"
>>>>though. Thanks for the responses. Vegas is still the best thing
>>out
>>>>there of it's kind. -Keith
>>>>
>>>>Peter Haller wrote:
>>>>>>When Vegas "stops by itself" as you describe, is there an error
>>msg
>>>>>>or any indication for why the stop occurred?
>>>>>>
>>>>>>One overall suggestion when transferring large number of tracks
>>>>from
>>>>>>MDM to Vegas. Disable SRP in the Options menu. This will save
>>>>>>considerable bandwidth of the PCI bus. Why? If Vegas is enabled
>>for
>>>>>>SRP, then your mix bus is active as well since Vegas permits
>>>>editing
>>>>>>during playback.
>>>>>>
>>>>>>What we have typically seen as the biggest performance problem
>>when
>>>>>>recording large number of tracks is the graphic card in a
system.
>>>>>>Vegas draws the peaks during the record in real time. It is
also
>>>>>>updateing the input meters in realtime. I have seen the number
>>of
>>>>>>tracks/inputs that are recordable jump from 6 stereo on a
system
>>>>with
>>>>>>a Diamond Fire GL AGP to 20 stereo (all I had available) with a
>>>>>>Matrox G4000 Max.
>>>>>>
>>>>>>We are working on ways to improve performance when recording
>>large
>>>>>>numbers of tracks. We get so many different reports of how many
>>>>then
>>>>>>can or can't record that there is no clear cut reason for
>>somebody
>>>>>>achieving 24 tracks while another can't get 6 tracks.
>>>>>>
>>>>>>Do you have a name for the tech support person that told you
>>Vegas
>>>>>>was not designed for doing tracking like this?
>>>>>>
>>>>>>Peter
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Michael Martin wrote:
>>>>>>>>Keith,
>>>>>>>>I have been having similar problems while trying to transfer
>>>>>>>>Adat tracks to Vegas. (record for only a few seconds and
stops
>>by
>>>>>>>>itself) I have to use Alesis's AdatConnect much in the same
way
>>>>>>>>as you are using VST24 to get Adat tracks into Vegas. Vegas
>>has
>>>>a
>>>>>>>>great interface and wonderful features. But "dang gummit"
>>can't
>>>>>>>>somebody comes up with some better solutions. Sonic Foundry
>>has
>>>>>>been
>>>>>>>>NO help to me regarding this matter. Why, even one of the
Tech
>>>>>>Suport
>>>>>>>>persons told me that Vegas was not designed to be used for
>>>>>>tranfering
>>>>>>>>multi tracks. I politely said "Goodbye" Kinda makes "ya"
>>wonder.
>>>>>>>>I mean what's the deal? Is this an issue of Soundcards,
CPU,
>>>>>>>>MotherBoards, Sound Drivers, Chipsets? What?
>>>>>>>>Vegas has the best interface and features of any progran I
have
>>>>>>>>seen. Let's hope somebody comes up with some better
solutions.
>>>>>>>>
>>>>>>>>
>>>>>>>>Keith wrote:
>>>>>>>>>>Okay, if I can do this, I will never need to open Cubase
>>>>>>>>>>VST24 ever again! I love Vegas. Mixing multitrack music
>>>>>>>>>>with recall is like a dream come true and it fulfills all
>>>>>>>>>>of my musical needs except---
>>>>>>>>>>I have not been able successfully transfer 24 tracks of
>>>>>>>>>>DA88 thru the 2408 into Vegas 1.0b.
>>>>>>>>>>What I have been doing is transferring the 24 tracks into
>>>>>>>>>>VST24(simultaneously- no problems), and then opening the
>>>>>>>>>>wavs in Vegas to do the editing... then re-opening VST with
>>>>>>>>>>the edited tracks and THEN transferring back to the DA88s.
>>>>>>>>>>Needless to say, it is quite a pain, but it works reliably.
>>>>>>>>>>
>>>>>>>>>>The best I can get Vegas to do- is a record a few seconds
>>>>>>>>>>of 24 track recording before it seems to choke and stops by
>>>>>>>>>>itself. Also, Vegas seems to chase to MTC for the first
>>>>>>>>>>take or so, then it stops syncing at all. Then I have to
>>>>>>>>>>close the program and re-open it to get it to sync again.
>>>>>>>>>>I don't think it's the MOTU, because the transfer happens
>>>>>>>>>>pretty reliably with VST. Help! I can't stand VST!
>>>>>>>>>>Anyone with a similar setup or suggestions? Perhaps I'm
>>>>>>>>>>missing something obvious? I run a PII 450 w/ IDE66 @
>>>>>>>>>>7200, 128 ram. No performance problems otherwise, and the
>>>>>>>>>>latest 2408 driver. Thanks, Keith

Hi Keith,

For some reason I started out syncing Vegas to the DA-88's, when
needed, AFTER the tracks are recorded to the hard drive ... I just
set the ruler offset for the same spot on the DA-88 tape and, with a
rare bit of tweaking on ocassion, it locks right up.

I also most definitely disable "Simultaneous Play and Record".

One other thing to try is, as Peter intimated, to take your video
card's screen redraw's out of the loop while recording. Just start
recording and then minnimize Vegas immediately until the end of the
selection.

I still have to do this because there is a problem with our video
card and Vegas and I get pops and clicks in the recorded audio if I
don't. I keep meaning to get a Matrox, but just haven't had the
time ... its just been too easy to minnimize the screen. :)

(You can usually tell if you're still recording by watching your hard
drive LED.)

Let us know how your fare.

KAC ...


Keith wrote:
>>Thanks for the responses folks!
>>Karl, the reason I prefer to transfer tracks from the DA88's to
Vegas
>>in sync are that 1. Sometimes I need to tune up and edit just one
or
>>two tracks and need to fly them back to the DA88's in the same
>>location on the tape. 2. Even if I edit and mix in Vegas, it is
often
>>quicker to archive the altered tracks back to the DA88 instead of
>>saving all of the 24 bit wave data to CD disks with a client paying
>>for the time. But Karl, if you have had great success transferring
>>24 tracks digitally back and forth without MTC sync with a similar
>>setup, PLEASE let me know, cause I might be willing to move all 24
>>tracks back and forth to a different location on the DA88 tape -
even
>>if it means using more
>>tape, just to avoid using VST for the transfer!

Thanks to Peter, Karl and others. Well, I'm halfway there! I spent
all afternoon uninstalling and re-installing the 2408 and placing the
pci324 into a different slot. There was about 3 hours where my
computer would see the pci324 card, install the driver, then never
see the 2408 at all!!!! Argh!
To make a long story short, I was finally able to stream 24
simultaneous tracks from the DA88's into Vegas SYNC'd(chasing, not
triggered) to MTC! I even forgot to turn of SRP, but I did reduce
the screen like Karl suggested so the redraws were tiny. Seemed to
play fine, but I was too burnt to listen that carefully.
Halfway there!
Peter, I assume to stream back to the DA88's I must set up 12 stereo
busses(24 mono panned L or R) in order to pass the info back to the
MDM's? Also, it seems that the sync to MTC is still unstable with my
setup. What happens is that upon opening Vegas the sync works
perfectly, then after one or two record/stop/start cycles, it won't
sync no matter what I reset. I have tried to close and restart
Vegas, reset 2408's clock and bussing, turn on and off the 2408, but
the only way to get sync again is to reboot. I can work around this
for now if I can get the tracks to fly back! Thanks again for all
the help! Keith

Karl Caillouet wrote:
>>Hi Keith,
>>
>>For some reason I started out syncing Vegas to the DA-88's, when
>>needed, AFTER the tracks are recorded to the hard drive ... I just
>>set the ruler offset for the same spot on the DA-88 tape and, with
a
>>rare bit of tweaking on ocassion, it locks right up.
>>
>>I also most definitely disable "Simultaneous Play and Record".
>>
>>One other thing to try is, as Peter intimated, to take your video
>>card's screen redraw's out of the loop while recording. Just start
>>recording and then minnimize Vegas immediately until the end of the
>>selection.
>>
>>I still have to do this because there is a problem with our video
>>card and Vegas and I get pops and clicks in the recorded audio if I
>>don't. I keep meaning to get a Matrox, but just haven't had the
>>time ... its just been too easy to minnimize the screen. :)
>>
>>(You can usually tell if you're still recording by watching your
hard
>>drive LED.)
>>
>>Let us know how your fare.
>>
>>KAC ...
>>
>>
>>Keith wrote:
>>>>Thanks for the responses folks!
>>>>Karl, the reason I prefer to transfer tracks from the DA88's to
>>Vegas
>>>>in sync are that 1. Sometimes I need to tune up and edit just one
>>or
>>>>two tracks and need to fly them back to the DA88's in the same
>>>>location on the tape. 2. Even if I edit and mix in Vegas, it is
>>often
>>>>quicker to archive the altered tracks back to the DA88 instead of
>>>>saving all of the 24 bit wave data to CD disks with a client
paying
>>>>for the time. But Karl, if you have had great success
transferring
>>>>24 tracks digitally back and forth without MTC sync with a
similar
>>>>setup, PLEASE let me know, cause I might be willing to move all
24
>>>>tracks back and forth to a different location on the DA88 tape -
>>even
>>>>if it means using more
>>>>tape, just to avoid using VST for the transfer!

Keith wrote:
>>I spent
>>all afternoon uninstalling and re-installing the 2408 and placing
the
>>pci324 into a different slot. There was about 3 hours where my
>>computer would see the pci324 card, install the driver, then never
>>see the 2408 at all!!!! Argh!

Why? ... I would've thought that if CuBase saw the card and used it
properly, then it was likely installed properly to begin with?

>>triggered) to MTC! I even forgot to turn of SRP, but I did reduce
>>the screen like Karl suggested so the redraws were tiny. Seemed to
>>play fine, but I was too burnt to listen that carefully.

I meant MINNIMIZE the ENTIRE Vegas application, not just minnimize
the tracks. :)

>>I assume to stream back to the DA88's I must set up 12 stereo
>>busses(24 mono panned L or R) in order to pass the info back to the
>>MDM's?

Yes. 12 stereo busses, each alternate track from 1 to 24 assigned
to "L" and "R" respectively.

Then, making sure that the MOTU2408 inputs are out of record in the
PCI console and that your Word Clock is set appropriately, put the DA-
88's themselves in "Digital In" and enable record on each DA-88 track
you want to copy back to to DA-88s.

You will probably notice at this point that your levels going back to
the DA-88 are hotter than when coming off ... simply adjust them with
Vegas' output BUS faders, not the track faders.

Tip ... if you have the DA-88's outputs patched into a console at
this point (Digital IN, all DA-88 tracks in record, no tape) you can
mix through the DA-88's converters into the console and use your
outboard effects through the console, thereby saving wear and tear on
your DA-88 heads ... no need to even load tape. :)

KAC...

Karl Caillouet wrote:

>>
>>Why? ... I would've thought that if CuBase saw the card and used it
>>properly, then it was likely installed properly to begin with?

I searched all of last years Vegas posts on this forum and at some
point, Peter had mentioned that he had seen a 2408 crashing often and
moved the pci324 to another slot with good results. (Probably a
conflict issue?) All my sound apps seemed to crash a little too
often during long intense musical editing sessions (with clients
waiting for blue screen reboots), so I thought I'd finally give it a
try, since I wasn't getting the Vegas- DA88 thing happening anyway.

>>
>>I meant MINNIMIZE the ENTIRE Vegas application, not just minnimize
>>the tracks. :)

I know, but I thought I'd try to PEEK just a little, and the tiny
buggers just kept on drawing, so I let it finish.
>>
>>>>I assume to stream back to the DA88's I must set up 12 stereo
>>>>busses(24 mono panned L or R) in order to pass the info back to
the
>>>>MDM's?
>>
>>Yes. 12 stereo busses, each alternate track from 1 to 24 assigned
>>to "L" and "R" respectively.
>>
>>Then, making sure that the MOTU2408 inputs are out of record in the
>>PCI console and that your Word Clock is set appropriately, put
the...

Thanks a million Karl! I will try it as soon as I get some free time
and if it works, No more fighting in VST24! Keith
>>
>>

Keith wrote:
>>
>>
>>Karl Caillouet wrote:
>>
>>>>
>>>>Why? ... I would've thought that if CuBase saw the card and used
it
>>>>properly, then it was likely installed properly to begin with?
>>
>>I searched all of last years Vegas posts on this forum and at some
>>point, Peter had mentioned that he had seen a 2408 crashing often
and
>>moved the pci324 to another slot with good results. (Probably a
>>conflict issue?) All my sound apps seemed to crash a little too
>>often during long intense musical editing sessions (with clients
>>waiting for blue screen reboots), so I thought I'd finally give it
a
>>try, since I wasn't getting the Vegas- DA88 thing happening
anyway.
>>
>>>>
>>>>I meant MINNIMIZE the ENTIRE Vegas application, not just
minnimize
>>>>the tracks. :)
>>
>>I know, but I thought I'd try to PEEK just a little, and the tiny
>>buggers just kept on drawing, so I let it finish.
>>>>
>>>>>>I assume to stream back to the DA88's I must set up 12 stereo
>>>>>>busses(24 mono panned L or R) in order to pass the info back to
>>the
>>>>>>MDM's?
>>>>
>>>>Yes. 12 stereo busses, each alternate track from 1 to 24 assigned
>>>>to "L" and "R" respectively.
>>>>
>>>>Then, making sure that the MOTU2408 inputs are out of record in
the
>>>>PCI console and that your Word Clock is set appropriately, put
>>the...
>>
>>Thanks a million Karl! I will try it as soon as I get some free
time
>>and if it works, No more fighting in VST24! Keith
>>>>
>>>>

Ok, I know I'm far behind in this but I'd like to post this so anyone
trying to sync up the DA-88 with the MOTU 2408 to Vegas can do it.
You need a Word Clock cable from the DA-88 out to the MOTU in. This
is the key. Inside the MOTU Console set it to Word Clock and put the
DA-88 to Internal. I believe it works with and without the
Simultaneous Record and Play selected. Now all that needs to be done
is to set the recording device and the amount of channels needed! I
have tested this and it does indeed work, but NOT WITHOUT A WORD
CLOCK CABLE!!! Enjoy!!
Gary(Sweetwater PC Support Tech!)

Gary Brenner wrote:
>>Ok, I know I'm far behind in this but I'd like to post this so
anyone
>>trying to sync up the DA-88 with the MOTU 2408 to Vegas can do it.
>>You need a Word Clock cable from the DA-88 out to the MOTU in...

Thanks, Gary. Yes, I have the word clock from the SY88 to the MOTU.
The main problem was- that I can transfer 24 tracks of DA88 back and
forth thru the 2408 sync'd-locked into Cubase VST24 flawlessly, but
I'd rather do it all in Vegas.
Although I can transfer the same tracks into Vegas Pro in sync, I can
NOT fly them back to the DA88's(locked to MTC) cause the sync is
wobbly and stops working after a couple of tries. I'd like to hear
from anyone who uses the same setup and requires tracks to be sync-
locked during the transfer in BOTH directions for some tips and
guidance. In the mean time, I'm trying to figure out if there's
anything I can do to optimize my system from my end. Thanks, Keith