Thanks for your help Peter.

If all 16 busses are assigned to one output port, the system
performance is not impaired. Each time I enable an additional output
port, system performance suffers. By the time I reach 12 to 16
separate output ports, the system stutters or won't play at all.
I've tried various combinations of output ports, selecting among the
2 DSP Factory cards, the Yamaha SW1000, the EMU APS and the Lexicon
Core2, all of which are loaded in this computer. All provide the
same system impairment once the number of separate outs reaches 12 to
16. In each case, the video display (the time read-out at the top
left corner) also stutters more and more as you add output ports.

For reference, I also regularly use Cakewalk Pro Audio and SawPro
with this configuration (all outputs enabled in Cakewalk and 12--the
maximum--enabled in Saw Pro). Neither of those programs suffers from
this problem, so it shouldn't have anything to do with poorly written
sound card drivers. It seems that Vegas is designed in such a way
that performance suffers dramatically as you assign separate output
ports to the various busses.

Do you have any other suggestions?

Bob G.


Peter Haller wrote:
>>Are each of the busses assigned to different output ports/devices
of
>>the DSPF?
>>
>>Is the performance just as bad if you have 16 busses all assigned
to
>>one output port/device?
>>
>>Peter
>>
>>Robert Goodridge wrote:
>>>>I'm running Vegas with 2 DSP Factory cards. With 8 busses
>>>>enabled (1 DSP Factory card used), the system runs OK; with
>>>>12 busses, the audio stutters. With 16, the audio won't
>>>>even play. To make full use of the DSP Factory, I have to
>>>>enable 16 busses. Is there any way to fix this? Why does
>>>>adding busses slow down the system so much?
>>>>
>>>>I've already tried adjusting the playback buffers to the
>>>>maximum. It helped a little, but still the system is
>>>>unusable. The RAM monitor shows about 62MB out of 256
>>>>being used. My system: Celeron 400, 256Meg RAM, Win 98.
>>>>
>>>>Bob G.

Hmmm. We have seen some performance problems related to large number
of main busses when assigned to multiple hardware devices. This only
occurs under Win9x. This was only occuring when the busses were
assigned accross multiple cards vs one card.

Could you try one thing for me: Close the mixer page down when
playing back. Does performance improve? (I know this is not a
reasonable solution, I am just trying to narrow it down.)

Increasing the buffering only helps track count as this allows for
more disk i/o to occur with out gapping.

I am looking at this and will let you know what I discover.

Peter


Robert Goodridge wrote:
>>Thanks for your help Peter.
>>
>>If all 16 busses are assigned to one output port, the system
>>performance is not impaired. Each time I enable an additional
output
>>port, system performance suffers. By the time I reach 12 to 16
>>separate output ports, the system stutters or won't play at all.
>>I've tried various combinations of output ports, selecting among
the
>>2 DSP Factory cards, the Yamaha SW1000, the EMU APS and the Lexicon
>>Core2, all of which are loaded in this computer. All provide the
>>same system impairment once the number of separate outs reaches 12
to
>>16. In each case, the video display (the time read-out at the top
>>left corner) also stutters more and more as you add output ports.
>>
>>For reference, I also regularly use Cakewalk Pro Audio and SawPro
>>with this configuration (all outputs enabled in Cakewalk and 12--
the
>>maximum--enabled in Saw Pro). Neither of those programs suffers
from
>>this problem, so it shouldn't have anything to do with poorly
written
>>sound card drivers. It seems that Vegas is designed in such a way
>>that performance suffers dramatically as you assign separate output
>>ports to the various busses.
>>
>>Do you have any other suggestions?
>>
>>Bob G.
>>
>>
>>Peter Haller wrote:
>>>>Are each of the busses assigned to different output ports/devices
>>of
>>>>the DSPF?
>>>>
>>>>Is the performance just as bad if you have 16 busses all assigned
>>to
>>>>one output port/device?
>>>>
>>>>Peter
>>>>
>>>>Robert Goodridge wrote:
>>>>>>I'm running Vegas with 2 DSP Factory cards. With 8 busses
>>>>>>enabled (1 DSP Factory card used), the system runs OK; with
>>>>>>12 busses, the audio stutters. With 16, the audio won't
>>>>>>even play. To make full use of the DSP Factory, I have to
>>>>>>enable 16 busses. Is there any way to fix this? Why does
>>>>>>adding busses slow down the system so much?
>>>>>>
>>>>>>I've already tried adjusting the playback buffers to the
>>>>>>maximum. It helped a little, but still the system is
>>>>>>unusable. The RAM monitor shows about 62MB out of 256
>>>>>>being used. My system: Celeron 400, 256Meg RAM, Win 98.
>>>>>>
>>>>>>Bob G.

Peter: here's some more information:
1. Yes, closing the mixer page does improve performance. With the
mixer page closed, Vegas made it through the whole song without
stuttering, although the video time display at the top left corner
still runs a bit choppy.

2. I also noticed that having 16 busses enabled, but actually using
only one bus (i.e., all tracks are assigned to one bus), causes the
stuttering (this is what I was doing when I posted my first email).
If I enable 16 busses, and assign the tracks each to a different bus,
system performance improves and there's no stuttering. But the video
time display is still choppy, indicating that this configuration
drags system performance more than when I have just one bus enabled.

With either of these workarounds, I can still see the drag on system
performance. I'm concerned that, when I start to add direct x
effects, the stuttering will return.

Thanks for your help.

Bob G.


Peter Haller wrote:
>>Hmmm. We have seen some performance problems related to large
number
>>of main busses when assigned to multiple hardware devices. This
only
>>occurs under Win9x. This was only occuring when the busses were
>>assigned accross multiple cards vs one card.
>>
>>Could you try one thing for me: Close the mixer page down when
>>playing back. Does performance improve? (I know this is not a
>>reasonable solution, I am just trying to narrow it down.)
>>
>>Increasing the buffering only helps track count as this allows for
>>more disk i/o to occur with out gapping.
>>
>>I am looking at this and will let you know what I discover.
>>
>>Peter
>>
>>
>>Robert Goodridge wrote:
>>>>Thanks for your help Peter.
>>>>
>>>>If all 16 busses are assigned to one output port, the system
>>>>performance is not impaired. Each time I enable an additional
>>output
>>>>port, system performance suffers. By the time I reach 12 to 16
>>>>separate output ports, the system stutters or won't play at all.
>>>>I've tried various combinations of output ports, selecting among
>>the
>>>>2 DSP Factory cards, the Yamaha SW1000, the EMU APS and the
Lexicon
>>>>Core2, all of which are loaded in this computer. All provide the
>>>>same system impairment once the number of separate outs reaches
12
>>to
>>>>16. In each case, the video display (the time read-out at the
top
>>>>left corner) also stutters more and more as you add output ports.
>>>>
>>>>For reference, I also regularly use Cakewalk Pro Audio and SawPro
>>>>with this configuration (all outputs enabled in Cakewalk and 12--
>>the
>>>>maximum--enabled in Saw Pro). Neither of those programs suffers
>>from
>>>>this problem, so it shouldn't have anything to do with poorly
>>written
>>>>sound card drivers. It seems that Vegas is designed in such a
way
>>>>that performance suffers dramatically as you assign separate
output
>>>>ports to the various busses.
>>>>
>>>>Do you have any other suggestions?
>>>>
>>>>Bob G.
>>>>
>>>>
>>>>Peter Haller wrote:
>>>>>>Are each of the busses assigned to different output
ports/devices
>>>>of
>>>>>>the DSPF?
>>>>>>
>>>>>>Is the performance just as bad if you have 16 busses all
assigned
>>>>to
>>>>>>one output port/device?
>>>>>>
>>>>>>Peter
>>>>>>
>>>>>>Robert Goodridge wrote:
>>>>>>>>I'm running Vegas with 2 DSP Factory cards. With 8 busses
>>>>>>>>enabled (1 DSP Factory card used), the system runs OK; with
>>>>>>>>12 busses, the audio stutters. With 16, the audio won't
>>>>>>>>even play. To make full use of the DSP Factory, I have to
>>>>>>>>enable 16 busses. Is there any way to fix this? Why does
>>>>>>>>adding busses slow down the system so much?
>>>>>>>>
>>>>>>>>I've already tried adjusting the playback buffers to the
>>>>>>>>maximum. It helped a little, but still the system is
>>>>>>>>unusable. The RAM monitor shows about 62MB out of 256
>>>>>>>>being used. My system: Celeron 400, 256Meg RAM, Win 98.
>>>>>>>>
>>>>>>>>Bob G.

Bob/Peter - I had a very similar experience just last night. I use
Vegas with a MOTU 1224 system, Win98, 466Celeron/128MB RAM/10K RPM
drives.

I had about 10 recorded tracks going, 10 busses (even though 9 tracks
were assigned to just one buss), and I wanted to record some vocals.
As soon as I armed the 10th track to record, the system blue screened
on me, complaining about some exception errors. Eventually the MOTU
got real distorted, and finally quit working. Rebooting fixed the
sound card, but trying to record started the whole process over
again.

I finally reinstalled the MOTU system, and all seems to be well (with
just 4 live busses). I'm a bit scared to try 10 again, but I will
tonight. MOTU support seemed to think maybe I had overloaded the
system. I would sure hope not, 10 tracks/busses isn't a major session
in my book.

Also, not to say this isn't a MOTU problem, but I at least wanted to
comment, because of the likeness of my problems.

Robert Goodridge wrote:
>>Peter: here's some more information:
>>1. Yes, closing the mixer page does improve performance. With
the
>>mixer page closed, Vegas made it through the whole song without
>>stuttering, although the video time display at the top left corner
>>still runs a bit choppy.
>>
>>2. I also noticed that having 16 busses enabled, but actually
using
>>only one bus (i.e., all tracks are assigned to one bus), causes the
>>stuttering (this is what I was doing when I posted my first
email).
>>If I enable 16 busses, and assign the tracks each to a different
bus,
>>system performance improves and there's no stuttering. But the
video
>>time display is still choppy, indicating that this configuration
>>drags system performance more than when I have just one bus enabled.
>>
>>With either of these workarounds, I can still see the drag on
system
>>performance. I'm concerned that, when I start to add direct x
>>effects, the stuttering will return.

Bob/Peter/Justin-


Justin Folger wrote:
>>Bob/Peter - I had a very similar experience just last night. I use
>>Vegas with a MOTU 1224 system, Win98, 466Celeron/128MB RAM/10K RPM
>>drives.
>>
>>I had about 10 recorded tracks going, 10 busses (even though 9
tracks
>>were assigned to just one buss), and I wanted to record some
vocals.
>>As soon as I armed the 10th track to record, the system blue
screened
>>on me, complaining about some exception errors. Eventually the MOTU
>>got real distorted, and finally quit working. Rebooting fixed the
>>sound card, but trying to record started the whole process over
>>again.
>>
>>I finally reinstalled the MOTU system, and all seems to be well
(with
>>just 4 live busses). I'm a bit scared to try 10 again, but I will
>>tonight. MOTU support seemed to think maybe I had overloaded the
>>system. I would sure hope not, 10 tracks/busses isn't a major
session
>>in my book.
>>
>>Also, not to say this isn't a MOTU problem, but I at least wanted
to
>>comment, because of the likeness of my problems.
>>
>>Robert Goodridge wrote:
>>>>Peter: here's some more information:
>>>>1. Yes, closing the mixer page does improve performance. With
>>the
>>>>mixer page closed, Vegas made it through the whole song without
>>>>stuttering, although the video time display at the top left
corner
>>>>still runs a bit choppy.
>>>>
>>>>2. I also noticed that having 16 busses enabled, but actually
>>using
>>>>only one bus (i.e., all tracks are assigned to one bus), causes
the
>>>>stuttering (this is what I was doing when I posted my first
>>email).
>>>>If I enable 16 busses, and assign the tracks each to a different
>>bus,
>>>>system performance improves and there's no stuttering. But the
>>video
>>>>time display is still choppy, indicating that this configuration
>>>>drags system performance more than when I have just one bus
enabled.
>>>>
>>>>With either of these workarounds, I can still see the drag on
>>system
>>>>performance. I'm concerned that, when I start to add direct x
>>>>effects, the stuttering will return.
>>

Bob/Peter/Justin-
I am also having similar problems- I am using the MOTU 2408, Win98,
450 AMDK6-2, 256 meg RAM. I Have notice serious stuttering of audio
while having only recorded 3-4 tracks, sometimes w/ only one or two.
Could there be some windows/PCI conflicts happening? I am thinking
this way because we are all having very similar problems while trying
to add busses to our projects.
-Todd

Justin Folger wrote:
>>Bob/Peter - I had a very similar experience just last night. I use
>>Vegas with a MOTU 1224 system, Win98, 466Celeron/128MB RAM/10K RPM
>>drives.
>>
>>I had about 10 recorded tracks going, 10 busses (even though 9
tracks
>>were assigned to just one buss), and I wanted to record some
vocals.
>>As soon as I armed the 10th track to record, the system blue
screened
>>on me, complaining about some exception errors. Eventually the MOTU
>>got real distorted, and finally quit working. Rebooting fixed the
>>sound card, but trying to record started the whole process over
>>again.
>>
>>I finally reinstalled the MOTU system, and all seems to be well
(with
>>just 4 live busses). I'm a bit scared to try 10 again, but I will
>>tonight. MOTU support seemed to think maybe I had overloaded the
>>system. I would sure hope not, 10 tracks/busses isn't a major
session
>>in my book.
>>
>>Also, not to say this isn't a MOTU problem, but I at least wanted
to
>>comment, because of the likeness of my problems.
>>
>>Robert Goodridge wrote:
>>>>Peter: here's some more information:
>>>>1. Yes, closing the mixer page does improve performance. With
>>the
>>>>mixer page closed, Vegas made it through the whole song without
>>>>stuttering, although the video time display at the top left
corner
>>>>still runs a bit choppy.
>>>>
>>>>2. I also noticed that having 16 busses enabled, but actually
>>using
>>>>only one bus (i.e., all tracks are assigned to one bus), causes
the
>>>>stuttering (this is what I was doing when I posted my first
>>email).
>>>>If I enable 16 busses, and assign the tracks each to a different
>>bus,
>>>>system performance improves and there's no stuttering. But the
>>video
>>>>time display is still choppy, indicating that this configuration
>>>>drags system performance more than when I have just one bus
enabled.
>>>>
>>>>With either of these workarounds, I can still see the drag on
>>system
>>>>performance. I'm concerned that, when I start to add direct x
>>>>effects, the stuttering will return.
>>

It's definitely not a PCI conflict issue, at least in my case. I
also run Cakewalk and Saw Pro on the same computer and neither of
those programs suffer from stuttering.

Todd Anisman wrote:
>>Bob/Peter/Justin-
>>I am also having similar problems- I am using the MOTU 2408, Win98,
>>450 AMDK6-2, 256 meg RAM. I Have notice serious stuttering of audio
>>while having only recorded 3-4 tracks, sometimes w/ only one or
two.
>>Could there be some windows/PCI conflicts happening? I am thinking
>>this way because we are all having very similar problems while
trying
>>to add busses to our projects.
>> -Todd
>>
>>Justin Folger wrote:
>>>>Bob/Peter - I had a very similar experience just last night. I
use
>>>>Vegas with a MOTU 1224 system, Win98, 466Celeron/128MB RAM/10K
RPM
>>>>drives.
>>>>
>>>>I had about 10 recorded tracks going, 10 busses (even though 9
>>tracks
>>>>were assigned to just one buss), and I wanted to record some
>>vocals.
>>>>As soon as I armed the 10th track to record, the system blue
>>screened
>>>>on me, complaining about some exception errors. Eventually the
MOTU
>>>>got real distorted, and finally quit working. Rebooting fixed the
>>>>sound card, but trying to record started the whole process over
>>>>again.
>>>>
>>>>I finally reinstalled the MOTU system, and all seems to be well
>>(with
>>>>just 4 live busses). I'm a bit scared to try 10 again, but I will
>>>>tonight. MOTU support seemed to think maybe I had overloaded the
>>>>system. I would sure hope not, 10 tracks/busses isn't a major
>>session
>>>>in my book.
>>>>
>>>>Also, not to say this isn't a MOTU problem, but I at least wanted
>>to
>>>>comment, because of the likeness of my problems.
>>>>
>>>>Robert Goodridge wrote:
>>>>>>Peter: here's some more information:
>>>>>>1. Yes, closing the mixer page does improve performance.
With
>>>>the
>>>>>>mixer page closed, Vegas made it through the whole song without
>>>>>>stuttering, although the video time display at the top left
>>corner
>>>>>>still runs a bit choppy.
>>>>>>
>>>>>>2. I also noticed that having 16 busses enabled, but actually
>>>>using
>>>>>>only one bus (i.e., all tracks are assigned to one bus), causes
>>the
>>>>>>stuttering (this is what I was doing when I posted my first
>>>>email).
>>>>>>If I enable 16 busses, and assign the tracks each to a
different
>>>>bus,
>>>>>>system performance improves and there's no stuttering. But the
>>>>video
>>>>>>time display is still choppy, indicating that this
configuration
>>>>>>drags system performance more than when I have just one bus
>>enabled.
>>>>>>
>>>>>>With either of these workarounds, I can still see the drag on
>>>>system
>>>>>>performance. I'm concerned that, when I start to add direct x
>>>>>>effects, the stuttering will return.
>>>>

Well, I just ran home at lunch and was 'showing off' my system to a
friend, and booted up the system, proceeded to arm a track to record,
and behold: the infamous blue screen again. This was on an empty
project!

Reintsalling Win98 once a week is not a great option. Between the
support reactions/responses I've gotten from MOTU and SF, ProTools is
sounding better everyday......

Justin

>>Todd Anisman wrote:
>>>>Bob/Peter/Justin-
>>>>I am also having similar problems- I am using the MOTU 2408,
Win98,
>>>>450 AMDK6-2, 256 meg RAM. I Have notice serious stuttering of
audio
>>>>while having only recorded 3-4 tracks, sometimes w/ only one or
>>two.
>>>>Could there be some windows/PCI conflicts happening? I am
thinking
>>>>this way because we are all having very similar problems while
>>trying
>>>>to add busses to our projects.
>>>> -Todd
>>>>

An exception error in ***MOTKVD****, or something similar?

We had that problem a few times a while back before tech support
clued us in on how to record 24 bit mode with our MOTU 2408.

Powering the MOTU 2408 off and on (with the computer off, of course)
seemed to help when it happened. Unless you did that, the MOTU
console would screw up and would barf again when you tried
to "refresh".

I am pretty sure that our problem was with the MOTU driver and trying
to record 24 bit, though ... so this is just FWIW.

KAC ...


Justin Folger wrote:

>>As soon as I armed the 10th track to record, the system blue
screened on me, complaining about some exception errors.

Yeah, the errors are right along those lines, and I *am* recording at
24 bit. Unfortunately (for me), powering PC/MOTU off and back on
doesn't always clear it up the first time.

I do have a feeling it's the MOTU unit. It's easy to want to blame a
new software product like Vegas, but I just have a hunch it's MOTU.

I do like Vegas, just finished my first song on it, and it sounds
amazing (to me), compared to what I was doing on my old VS880.

I guess this begs the question: If not MOTU, then who else? I need
(want) a higher-end piece of hardware. I've always thought of MOTU as
a step above Event, Lexicon, Yamaha, etc.

I think my next step is to try installing NT instead of 98. I hear
they utilize different wave drivers and such, perhaps it's a more
stable environment for A/V.

Karl Caillouet wrote:
>>An exception error in ***MOTKVD****, or something similar?
>>
>>We had that problem a few times a while back before tech support
>>clued us in on how to record 24 bit mode with our MOTU 2408.
>>
>>Powering the MOTU 2408 off and on (with the computer off, of
course)
>>seemed to help when it happened. Unless you did that, the MOTU
>>console would screw up and would barf again when you tried
>>to "refresh".
>>
>>I am pretty sure that our problem was with the MOTU driver and
trying
>>to record 24 bit, though ... so this is just FWIW.
>>
>>KAC ...
>>
>>
>>Justin Folger wrote:
>>
>>>>As soon as I armed the 10th track to record, the system blue
>>screened on me, complaining about some exception errors.

One thing I forgot to mention. This blue screen thing first happened
when we were trying to set up a "default.veg" with 16 input
busses already assigned so we wouldn't have to go through that
tedious process everytime we wanted to open a new project.

I figured out real quick that the blue screens were happening on cue
if what I had in the "default.veg" file did not correspond *exactly"
to what was enabled in the MOTU PCI Console ... and once it started
it wouldn't stop until the MOTU AND the computer were both rebooted
and things were back in sync with the MOTU as far as the number of
inputs activated and from the correct source.

There might be a clue in there for you.

Again, this appears to me to be a virtual device driver issue with
the MOTU, and FWIW ... good luck.

BTW, MOTU does not support NT, so that option is not available at
this time. :(

KAC ...


Justin Folger wrote:
>>Yeah, the errors are right along those lines, and I *am* recording
at 24 bit.

With out sounding like I am pointing fingers, Vegas can't really
produce a Blue Screen, at least not by itself.

Blue Screens are typically the result of error in a VxD not being
handled. Vegas may be stressing a driver - i.e. a VxD - to do
something that the driver was not implemented to handle. Vegas
unfortunatly cannot ask a driver "hey, are you going to choke if we
do this?"

I am looking into the problems with the MOTU hardware/drivers, as I
have seen this one to many times myself. What I am looking for now is
a consitant repro that I can forward to MOTU.

Peter


Justin Folger wrote:
>>Well, I just ran home at lunch and was 'showing off' my system to a
>>friend, and booted up the system, proceeded to arm a track to
record,
>>and behold: the infamous blue screen again. This was on an empty
>>project!
>>
>>Reintsalling Win98 once a week is not a great option. Between the
>>support reactions/responses I've gotten from MOTU and SF, ProTools
is
>>sounding better everyday......
>>
>>Justin
>>
>>>>Todd Anisman wrote:
>>>>>>Bob/Peter/Justin-
>>>>>>I am also having similar problems- I am using the MOTU 2408,
>>Win98,
>>>>>>450 AMDK6-2, 256 meg RAM. I Have notice serious stuttering of
>>audio
>>>>>>while having only recorded 3-4 tracks, sometimes w/ only one or
>>>>two.
>>>>>>Could there be some windows/PCI conflicts happening? I am
>>thinking
>>>>>>this way because we are all having very similar problems while
>>>>trying
>>>>>>to add busses to our projects.
>>>>>> -Todd
>>>>>>
>>

Bad news: There are no NT drivers for the MOTU hardware. Believe me,
I wish there were.

On another note, NT drivers are more difficult to develope and are
even more unforgiving than 9X drivers.

Peter


Justin Folger wrote:
>>Yeah, the errors are right along those lines, and I *am* recording
at
>>24 bit. Unfortunately (for me), powering PC/MOTU off and back on
>>doesn't always clear it up the first time.
>>
>>I do have a feeling it's the MOTU unit. It's easy to want to blame
a
>>new software product like Vegas, but I just have a hunch it's MOTU.
>>
>>I do like Vegas, just finished my first song on it, and it sounds
>>amazing (to me), compared to what I was doing on my old VS880.
>>
>>I guess this begs the question: If not MOTU, then who else? I need
>>(want) a higher-end piece of hardware. I've always thought of MOTU
as
>>a step above Event, Lexicon, Yamaha, etc.
>>
>>I think my next step is to try installing NT instead of 98. I hear
>>they utilize different wave drivers and such, perhaps it's a more
>>stable environment for A/V.
>>
>>Karl Caillouet wrote:
>>>>An exception error in ***MOTKVD****, or something similar?
>>>>
>>>>We had that problem a few times a while back before tech support
>>>>clued us in on how to record 24 bit mode with our MOTU 2408.
>>>>
>>>>Powering the MOTU 2408 off and on (with the computer off, of
>>course)
>>>>seemed to help when it happened. Unless you did that, the MOTU
>>>>console would screw up and would barf again when you tried
>>>>to "refresh".
>>>>
>>>>I am pretty sure that our problem was with the MOTU driver and
>>trying
>>>>to record 24 bit, though ... so this is just FWIW.
>>>>
>>>>KAC ...
>>>>
>>>>
>>>>Justin Folger wrote:
>>>>
>>>>>>As soon as I armed the 10th track to record, the system blue
>>>>screened on me, complaining about some exception errors.

You guys are probably a lot better plugged in to MOTU than the
average bear, but for the readers info here is a post I made not too
long ago on my conversations with MOTU on this very issue:

>>>snip
I both Faxed on company letterhead and e-mailed MOTU as we are
contemplating the purchase of a couple of 1224's to add to our MOTU
2408 and have definite plans to migrate to Win2000 to take advantage
of muli-processor /threaded software capability in the future.

MOTU's e-mail response was predictably vague and politically non-
committal on the issue, but the human call back response I got from
them on the FAX was encouraging.

The caller left no doubt that they perfectly understand that to not
support Win2000 for their legacy hardware would be a business mistake
they are not prepared to make.

Because Win2000 is not yet released, I understand their reluctance to
publicly commit on the drivers for same ... but I was definitely left
with the impression that our contemplated financial outlay would not
leave us stranded without drivers.

While it is still a business decision we must make based on our past
experience with vapor ware, I certainly feel a bit better after my
conversation with MOTU about making the outlay.

>>>snip
I personally can't wait for the day that we can crank up Vegas Pro on
NT ... it has to be a great experience based on the way it runs on
Win98. The only machine we have running around here that is not
running NT is the one running Vegas Pro because of the MOTU driver
issue.

KAC ...


Peter Haller wrote:
>>Bad news: There are no NT drivers for the MOTU hardware. Believe
me,
>>I wish there were.

I'm the one who first posted this problem. FYI, I've now tried Vegas
in NT and I'm experiencing the same problems with adding busses. I'm
using the latest DSP Factory NT drivers. Adding busses definitely
slows down the system. I've not tried other programs (Cakewalk, Saw
PRo, etc.) in NT yet, so I don't know if the problems in NT are
attributable to the drivers or Vegas, but I don't see any difference
in this issue on NT vs. Win98.