when i tried VV on my win98 computer w/ nic card i noticed it crashed
4X as much when the NIC card was installed then when it wasn't ...
i'm running VV on my new win2K computer now and most of the time when
i edit i disable the NIC if i don't need files off other computers ..
after using win2K i dread going back on the win98 computer ... i now
notice that win 98 crashes everyday doesn't matter what program i'm
using ....

Charles de Montebello wrote:
>>Hey Joe -
>>I'm sorry to hear you're having such issues. I agree about the
video
>>glitches but I haven't had Vegas crash or freeze (with pre-release
>>and this new one) once. I have the 1010 also, with the 2nd to
latest
>>drivers.
>>Have you tried removing the NIC card?
>>
>>Joe Doria wrote:
>>>>Sorry about this - I really DO want it to work.
>>>>
>>>>Start with some pros on the subject:
>>>>Much better build, features are nice, I'm sure multi-
>>>>monitor is working (single monitor here), etc.
>>>>
>>>>However......
>>>>
>>>>I have had five freeze/crashes (no errors.. just freezes)
>>>>while mixing an 8 track 24-bit/44.1 project(s) since it was
>>>>installed. These projects have 2 FX busses and 2-3 plug-ins
>>>>on 2 busses.
>>>>
>>>>Repro:
>>>>- open a project as described above
>>>>- make edits, volumes whatever...play around for a long
>>>>while.
>>>>- during playback - RE-SIZE ALL WINDOWS IN VEGAS AND SLIDE
>>>>THE TIME BAR (JUST BELOW THE AUDIO WAVES) TO RIGHT OR LEFT
>>>>(ALL WHILE PLAYING).
>>>>
>>>>I HAVE CONSISTENTLY FROZE THIS SYSTEM (TAKES A WHILE) WITH
>>>>EVEN THESE MEAGER AMOUNT OF TRACKS AND FX/PLUG-INS.
>>>>
>>>>Jesus christ... I'm about to give up.
>>>>
>>>>
>>>>I KNOW this is related to Vegas2.0 only cause I'VE NEVER
>>>>SEEN THESE PROBLEMS IN VEGAS 1.0B. Not to this day...any
>>>>resizing is just fine... doesn't even hiccup playback
>>>>(va2.0b does hiccup)
>>>>
>>>>IT TOOK A LITTLE LONGER TO SEE THESE FREEZES NOW BUT A
>>>>CRASHES ARE CRASHES NONETHELESS...AND NOW I STILL CAN'T
>>>>TRUST VEGAS 2.0.
>>>>
>>>>I also still believe this is related somehow to video
>>>>issues. What changed video "usage-wise" with 2.0 versus
>>>>1.0b? Why so many weird video issues when re-sizing during
>>>>playback?
>>>>
>>>>Please offer some assistance SF. I've got 2 VERY (i MEAN
>>>>VERY)important CD's hanging on vegas. I would very much
>>>>like to use 2.0 (at least by now).
>>>>
>>>>I don't trust the damn thing still to this date after
>>>>seeing this.
>>>>
>>>>I'm not trying to be an a-hole....really...but enough is
>>>>enough and I need answers....I really want it to work...
>>>>and be stable.
>>>>
>>>>I'm trying to do a DR.Watson on this for ya - I'll update
>>>>when I capture it.
>>>>
>>>>I've listed my system in the past. No IRQ issues...no
>>>>problems in device manager...sys is tip-top. Never see
>>>>these problems in Vegas 1.0b
>>>>
>>>>here's the quick and dirty - in order of cards top to
>>>>bottom:
>>>>win98se
>>>>PIII 800mhz
>>>>asus P3V4X bios 1005
>>>>256 ram
>>>>- 3dfx voodoo3 2000 agp
>>>>- sb pci128
>>>>- adaptec 29160 (4 UW scsi hds external)
>>>>- Midiman delta 1010 latest version driver - 11-9-00
>>>>- fa310tx NIC
>>>>
>>>>Please help
>>>>
>>>>Joe

>>I also still believe this is related somehow to video
>>issues. What changed video "usage-wise" with 2.0 versus
>>1.0b? Why so many weird video issues when re-sizing during
>>playback?
>>


you have a VERY VERY much faster system than i do, and I used to have
problems ALL the time on 1.0 and 2.0 whenever I zoom, move the screen
or ANYTHING video card related,,,tried all different video cards

since your system is so fast thats prolly why you didnt have hiccups
zooming on 1.0

Peter says all video updating in vegas is passive, so I suppose its
some kind of buss mastering thats screwing up my stuff,

Truthfully NONE of this PC crap works as advertised...thats just the
way it is
We have all found ways to workaround most of the bugs and I bet we
ALL work in totally different ways...noone can really help you know?
its frustrating, I have a partner who does all the finance and
backing of this studio, not a music guy at all....he is in horror at
the number of reboots and crashes, and cussing coming out of my
mouth, but you know what?

In the end its all worth it, the final result speaks for itself, no
matter the road to hell that it took to get there...but it is
IMPOSSIBLE for me to charge for the hours of crap that we have to put
up with.

Hopefully someone can look into the video card issue and stop the
hiccups, but now that open copy in sound forge actually works, Im
somewhat of a happy camper....I wish they would HURRY up with 24 bit
sound forge though

Thanks for the replies.... but please realize when I say that nothing
mentioned has any real bearing on the problem. There shouldn't be
such a drastic difference between va 2.0 and vegas 1.0b.

It's not the NIC, but I will try disabling the NIC in windows and
testing just in case. This is my connection to the internet
however...and will stay before vegas 2.0 stays.
The NIC is on it's own IRQ and shouldn't relate any problems with
vegas (any version)


It's not the speed of my system. I'm sorry but that is ridiculous (I
don't mean this to be condescending to whoever suggested this...but
it is).
I was a hardware lab manager for win NT and 98 teams for years.
Processor speed doesn't reflect errors such as freezing/crash like
this. I also know how to build and maintain a PC..especially for
audio.

I can't say whether or not is is my video card. I doubt it however
based on all other facts. Vegas 2.0 has been the only app that
crashes on this system regularly. Vegas 1.0b doesn't have ANY probs
with my vid card.
If anybody has knowledge on the 3dfx voodoo3 2k's and any issues
please let me know.

The video card is the only hardware I would suspect causing the
issues with vegas audio 2.0 (a,Pre, or b)....but I highly doubt it.

Whether or not it's the delta is again anyones guess...but again.. I
doubt it.

Guys. You too will see these crashes (it now takes a hell of a lot
more to reproduce these feezes)... THEY ARE THERE. I'VE CAME ACROSS
4-5 IN THE HOUR I HAD THE NEW VERSION.
MUST REBOOT AFTER THESE FREEZES.

Just because you havn't come across it yet is no real breakthrough.

I'm glad they got a feature working for you and now all is
golden.....but excuse me when I say this is f-ing ridiculous this
late in the game.

I want answers. No real reason has been presented about Vegas 1.0b
NOT showing ANY of these errors.... and Vegas 2.? showing ALL the
errors I describe.

I'm sorry...but it's bull.

I would love to hear from any SF techs on this please. I do
appreciate your sympathy and concern... I too hope we can nail this
down.

thanks,
Joe

Have you called tech support? That's probably the FIRST thing anybody
should do whenever they request tech help after unsuccessful
troubleshooting attempts.


Joe Doria wrote:
>>Thanks for the replies.... but please realize when I say that
nothing
>>mentioned has any real bearing on the problem. There shouldn't be
>>such a drastic difference between va 2.0 and vegas 1.0b.
>>
>>It's not the NIC, but I will try disabling the NIC in windows and
>>testing just in case. This is my connection to the internet
>>however...and will stay before vegas 2.0 stays.
>>The NIC is on it's own IRQ and shouldn't relate any problems with
>>vegas (any version)
>>
>>
>>It's not the speed of my system. I'm sorry but that is ridiculous (I
>>don't mean this to be condescending to whoever suggested this...but
>>it is).
>>I was a hardware lab manager for win NT and 98 teams for years.
>>Processor speed doesn't reflect errors such as freezing/crash like
>>this. I also know how to build and maintain a PC..especially for
>>audio.
>>
>>I can't say whether or not is is my video card. I doubt it however
>>based on all other facts. Vegas 2.0 has been the only app that
>>crashes on this system regularly. Vegas 1.0b doesn't have ANY probs
>>with my vid card.
>>If anybody has knowledge on the 3dfx voodoo3 2k's and any issues
>>please let me know.
>>
>>The video card is the only hardware I would suspect causing the
>>issues with vegas audio 2.0 (a,Pre, or b)....but I highly doubt it.
>>
>>Whether or not it's the delta is again anyones guess...but again.. I
>>doubt it.
>>
>>Guys. You too will see these crashes (it now takes a hell of a lot
>>more to reproduce these feezes)... THEY ARE THERE. I'VE CAME ACROSS
>>4-5 IN THE HOUR I HAD THE NEW VERSION.
>>MUST REBOOT AFTER THESE FREEZES.
>>
>>Just because you havn't come across it yet is no real breakthrough.
>>
>>I'm glad they got a feature working for you and now all is
>>golden.....but excuse me when I say this is f-ing ridiculous this
>>late in the game.
>>
>>I want answers. No real reason has been presented about Vegas 1.0b
>>NOT showing ANY of these errors.... and Vegas 2.? showing ALL the
>>errors I describe.
>>
>>I'm sorry...but it's bull.
>>
>>I would love to hear from any SF techs on this please. I do
>>appreciate your sympathy and concern... I too hope we can nail this
>>down.
>>
>>thanks,
>>Joe
>>
>>

Oh sorry...yes I called tech support. It was the standard fare.
(this is why I also prefer input from the likes of Peter Haller,
Dave, etc here from SF and users here as well.)

They do not know exactly why this is happening. All is in order
system wise..nothing out of the ordinary.

They suggested I: update my voodoo3 drivers to 1.06, turn off hdwr
accell., etc.

The tech also is using the SAME video card I have... no problems (so
he says).

So I:
- updated the drivers (no change... exact same video issues with
va2.0b

- turned off hrdwr accell. (no change... exact same video issues on
va2.0b)

- even tried turning ON byte merge and Fast Writes in bios No change)

Now I KNOW one thing for sure...
Va2.0 video functionality is completely different in comparison to
vegas 1.0b. It is completely obvious.

I can go into vegas 1.0b with 28 24-bit/44.1 tracks with plugin's on
each and resize windows/scroll bars till the cows come home.

as audio is playingback...Vegas 2.0 hiccups, spurts, sputters and
freezes with any of these "outlandish acts" (excuse....i need to joke
at this point).

My question is WHY WASN'T ANY OF THIS FIXED? It certainly is a known
issue.

anyway, i'm really disappointed with this. I could really use the
functionality of 20.

jd





Jim wrote:
>>Have you called tech support? That's probably the FIRST thing
anybody
>>should do whenever they request tech help after unsuccessful
>>troubleshooting attempts.
>>
>>
>>Joe Doria wrote:
>>>>Thanks for the replies.... but please realize when I say that
>>nothing
>>>>mentioned has any real bearing on the problem. There shouldn't
be
>>>>such a drastic difference between va 2.0 and vegas 1.0b.
>>>>
>>>>It's not the NIC, but I will try disabling the NIC in windows and
>>>>testing just in case. This is my connection to the internet
>>>>however...and will stay before vegas 2.0 stays.
>>>>The NIC is on it's own IRQ and shouldn't relate any problems with
>>>>vegas (any version)
>>>>
>>>>
>>>>It's not the speed of my system. I'm sorry but that is ridiculous
(I
>>>>don't mean this to be condescending to whoever suggested
this...but
>>>>it is).
>>>>I was a hardware lab manager for win NT and 98 teams for years.
>>>>Processor speed doesn't reflect errors such as freezing/crash
like
>>>>this. I also know how to build and maintain a PC..especially for
>>>>audio.
>>>>
>>>>I can't say whether or not is is my video card. I doubt it
however
>>>>based on all other facts. Vegas 2.0 has been the only app that
>>>>crashes on this system regularly. Vegas 1.0b doesn't have ANY
probs
>>>>with my vid card.
>>>>If anybody has knowledge on the 3dfx voodoo3 2k's and any issues
>>>>please let me know.
>>>>
>>>>The video card is the only hardware I would suspect causing the
>>>>issues with vegas audio 2.0 (a,Pre, or b)....but I highly doubt
it.
>>>>
>>>>Whether or not it's the delta is again anyones guess...but
again.. I
>>>>doubt it.
>>>>
>>>>Guys. You too will see these crashes (it now takes a hell of a
lot
>>>>more to reproduce these feezes)... THEY ARE THERE. I'VE CAME
ACROSS
>>>>4-5 IN THE HOUR I HAD THE NEW VERSION.
>>>>MUST REBOOT AFTER THESE FREEZES.
>>>>
>>>>Just because you havn't come across it yet is no real
breakthrough.
>>>>
>>>>I'm glad they got a feature working for you and now all is
>>>>golden.....but excuse me when I say this is f-ing ridiculous this
>>>>late in the game.
>>>>
>>>>I want answers. No real reason has been presented about Vegas
1.0b
>>>>NOT showing ANY of these errors.... and Vegas 2.? showing ALL the
>>>>errors I describe.
>>>>
>>>>I'm sorry...but it's bull.
>>>>
>>>>I would love to hear from any SF techs on this please. I do
>>>>appreciate your sympathy and concern... I too hope we can nail
this
>>>>down.
>>>>
>>>>thanks,
>>>>Joe
>>>>
>>>>

Guys, i must say that i apologize if I'm coming off as bashing this
release. That is NOT my point at all....I've laid some great tracks
with 1.0b so far and 2.0 is really MUCH better than (a, or Pre). So
I just want that said.

It's not the end of the world...so I don't want to paint that picture.
I was just REALLY hoping could gravitate from 1.0b to vegas 2.0 at
this point for the new functionality.

I've only had a day with this so I'm gonna try some different
configurations, new video board, and possible (last resort) a re-
install of the OS/drivers. Maybe it will work itself out.


thanks for the replies though,
Joe

Hang in there, Joe ... it took a completely new machine before we got
VV working with any stability whatsoever. Prior to that I could make
VV 2.0 lock up at will by minnimizing the track view three times in a
row, but I've never been able to repeat that behavior on another
machine, even with some of the same components, like the Video card.
That is why, as tough as it is to swallow, what you are describing
really sounds like a system dependent issue from this perspective.

Are you still running both versions on the same machine?

Good luck.

KAC ...

Joe Doria wrote:
>>Guys, i must say that i apologize if I'm coming off as bashing this
>>release. That is NOT my point at all....I've laid some great

Are you trying to be funny here?
Or are you always an idiot?

Take your act to the catskills humpy....or should I say Victor.

Wondering when you were gonna sneak in on moms computer again.


love,
jd

Have you tried moving your cards around into different PCI slots? How
about your IRQ assignments? In my case, this solved some weird
happenings with my PC.


Joe Doria wrote:
>>Guys, i must say that i apologize if I'm coming off as bashing this
>>release. That is NOT my point at all....I've laid some great tracks
>>with 1.0b so far and 2.0 is really MUCH better than (a, or Pre). So
>>I just want that said.
>>
>>It's not the end of the world...so I don't want to paint that
picture.
>>I was just REALLY hoping could gravitate from 1.0b to vegas 2.0 at
>>this point for the new functionality.
>>
>>I've only had a day with this so I'm gonna try some different
>>configurations, new video board, and possible (last resort) a re-
>>install of the OS/drivers. Maybe it will work itself out.
>>
>>
>>thanks for the replies though,
>>Joe
>>
>>

I haven't had enough time to see how stable this new version is but,
so far I'm pretty happy with the way it's responding on my system.
The issue of resizing windows while playing back seems to be more of
a user way of working problem to me then a Vegas problem. The
obvious solution is to have your windows where you want them and then
hit play. Why do you really need to resize the windows after you hit
play? You can easily hit "Cntrl-space bar" or "F-12" to start and
stop playback while looking at any window. Vegas's user interface
allows you to move and resize windows as you desire, this is a
feature that I very much enjoy, but I could imagine this is very
taxing on your system while it's trying to playback also. Other
audio software doesn't offer this versitility of resizing the windows
and controls, so I suppose this would be a "Vegas Only" bug, because
the solution to this so called bug would be to not offer this type of
user interface.

And Joe, one other thing, why are you using a Sound blaster card
along with your Delta 1010?, It seems like the Delta 1010 is a pro
audio card and your mixing it with a consumer piece of crap.....I
wouldn't work if I was Vegas just on that reasoning. Get rid of that
SB pci128 so you don't have any conflicts...sb pci128 is a sound card
isn't it? Sorry if it's not.

Thanks, there's my 2 peso's worth. :-)
Brian Franz

Jim wrote:
>>Have you tried moving your cards around into different PCI slots?
How
>>about your IRQ assignments? In my case, this solved some weird
>>happenings with my PC.
>>
>>
>>Joe Doria wrote:
>>>>Guys, i must say that i apologize if I'm coming off as bashing
this
>>>>release. That is NOT my point at all....I've laid some great
tracks
>>>>with 1.0b so far and 2.0 is really MUCH better than (a, or Pre).
So
>>>>I just want that said.
>>>>
>>>>It's not the end of the world...so I don't want to paint that
>>picture.
>>>>I was just REALLY hoping could gravitate from 1.0b to vegas 2.0
at
>>>>this point for the new functionality.
>>>>
>>>>I've only had a day with this so I'm gonna try some different
>>>>configurations, new video board, and possible (last resort) a re-
>>>>install of the OS/drivers. Maybe it will work itself out.
>>>>
>>>>
>>>>thanks for the replies though,
>>>>Joe
>>>>
>>>>

>>as audio is playingback...Vegas 2.0 hiccups, spurts, sputters and
>>freezes with any of these "outlandish acts" (excuse....i need to
joke


The big problem I have is that when I let tracks play for a whil;e,
sometimes, NOT always, the tracks will loose sync with each
other...then I hit play again and sometimes they are in sync and
sometimes out of sync....thing is: they should either ALWAYS be in
sync or ALWAYS out of sync if nothing else has changed...the
unpredictability is frightening

That is scary Aaron.I have never had this happen.Sounds like a
computer issue.I take that back,we had that happen once{not in Vegas}
and it was our soundcard acting up.I won't say the program.;-)


Aaron Carey wrote:
>>
>>
>>>>as audio is playingback...Vegas 2.0 hiccups, spurts, sputters and
>>>>freezes with any of these "outlandish acts" (excuse....i need to
>>joke
>>
>>
>>The big problem I have is that when I let tracks play for a whil;e,
>>sometimes, NOT always, the tracks will loose sync with each
>>other...then I hit play again and sometimes they are in sync and
>>sometimes out of sync....thing is: they should either ALWAYS be in
>>sync or ALWAYS out of sync if nothing else has changed...the
>>unpredictability is frightening
>>
>>

I would love to be rid of the sb128....however I work with 4-bit,
6053 khz files for work (telephony) and it is the only cards that
will playback these rates (the delta won't)....so that's why I'm
stuck. We're doing a full revamp rigt now.... so i record and mix
with the delta.... but after conversion.....it's now in thehands of
the pci128.

Resizing:

I resize and scroll while mixing a ton (I'm sure others do as well).
It is taxing... but it shouldn't be taxing (is my point). Vegas 1.0b
as i said can handle these things perfectly....and so should 2.0.

so there's that info.

JD

Brian Franz wrote:
>>I haven't had enough time to see how stable this new version is
but,
>>so far I'm pretty happy with the way it's responding on my system.
>>The issue of resizing windows while playing back seems to be more
of
>>a user way of working problem to me then a Vegas problem. The
>>obvious solution is to have your windows where you want them and
then
>>hit play. Why do you really need to resize the windows after you
hit
>>play? You can easily hit "Cntrl-space bar" or "F-12" to start and
>>stop playback while looking at any window. Vegas's user interface
>>allows you to move and resize windows as you desire, this is a
>>feature that I very much enjoy, but I could imagine this is very
>>taxing on your system while it's trying to playback also. Other
>>audio software doesn't offer this versitility of resizing the
windows
>>and controls, so I suppose this would be a "Vegas Only" bug,
because
>>the solution to this so called bug would be to not offer this type
of
>>user interface.
>>
>>And Joe, one other thing, why are you using a Sound blaster card
>>along with your Delta 1010?, It seems like the Delta 1010 is a pro
>>audio card and your mixing it with a consumer piece of crap.....I
>>wouldn't work if I was Vegas just on that reasoning. Get rid of
that
>>SB pci128 so you don't have any conflicts...sb pci128 is a sound
card
>>isn't it? Sorry if it's not.
>>
>>Thanks, there's my 2 peso's worth. :-)
>>Brian Franz
>>
>>Jim wrote:
>>>>Have you tried moving your cards around into different PCI slots?
>>How
>>>>about your IRQ assignments? In my case, this solved some weird
>>>>happenings with my PC.
>>>>
>>>>
>>>>Joe Doria wrote:
>>>>>>Guys, i must say that i apologize if I'm coming off as bashing
>>this
>>>>>>release. That is NOT my point at all....I've laid some great
>>tracks
>>>>>>with 1.0b so far and 2.0 is really MUCH better than (a, or
Pre).
>>So
>>>>>>I just want that said.
>>>>>>
>>>>>>It's not the end of the world...so I don't want to paint that
>>>>picture.
>>>>>>I was just REALLY hoping could gravitate from 1.0b to vegas 2.0
>>at
>>>>>>this point for the new functionality.
>>>>>>
>>>>>>I've only had a day with this so I'm gonna try some different
>>>>>>configurations, new video board, and possible (last resort) a
re-
>>>>>>install of the OS/drivers. Maybe it will work itself out.
>>>>>>
>>>>>>
>>>>>>thanks for the replies though,
>>>>>>Joe
>>>>>>
>>>>>>

Yes.. Yes.... yes

Now compare it to vegas 1.0b. You will see this is MUCH LESS of a
problem. Why can't we have this simple functionality throughout?

It is disconcerting to say the least.

JD

Aaron Carey wrote:
>>
>>
>>>>as audio is playingback...Vegas 2.0 hiccups, spurts, sputters and
>>>>freezes with any of these "outlandish acts" (excuse....i need to
>>joke
>>
>>
>>The big problem I have is that when I let tracks play for a whil;e,
>>sometimes, NOT always, the tracks will loose sync with each
>>other...then I hit play again and sometimes they are in sync and
>>sometimes out of sync....thing is: they should either ALWAYS be in
>>sync or ALWAYS out of sync if nothing else has changed...the
>>unpredictability is frightening
>>
>>

I feel it's vegas 2.0. I only had this happen RARELY with vegas 1.0b
lot's of plug-ins,etc..... even then it was bearable.

With 2.0.. it happens almost every other time I switch along the
timeline in 2.0

SF....are you seeing any of this? It is important.

I would do without ALL VIDEO functionality if we could get this
important basics back in order (as in vegas 1.0b)


JD



David W. Ruby wrote:
>>That is scary Aaron.I have never had this happen.Sounds like a
>>computer issue.I take that back,we had that happen once{not in
Vegas}
>>and it was our soundcard acting up.I won't say the program.;-)
>>
>>
>>Aaron Carey wrote:
>>>>
>>>>
>>>>>>as audio is playingback...Vegas 2.0 hiccups, spurts, sputters
and
>>>>>>freezes with any of these "outlandish acts" (excuse....i need
to
>>>>joke
>>>>
>>>>
>>>>The big problem I have is that when I let tracks play for a
whil;e,
>>>>sometimes, NOT always, the tracks will loose sync with each
>>>>other...then I hit play again and sometimes they are in sync and
>>>>sometimes out of sync....thing is: they should either ALWAYS be
in
>>>>sync or ALWAYS out of sync if nothing else has changed...the
>>>>unpredictability is frightening
>>>>
>>>>

No. I appreciate your findings...but I don't agree.

If vegas 1.0b is flawless wih my current hardware (more or less)...
than so too should vegas 2.0. I could see if I were using some no
name mobo, hd's, generic soundcard, etc... etc... but that is NOT the
case here at all.
all signs are pointing to minor coding errors relating to aspects of
video in vegas 2.0.

Vegas 2.0 is the only app in my box that acts flakey. I also hear
that the video team has some things to look at regarding both vegas
(es)...so I'm not giving up just yet.

Sorry Karl, no offense, but I don't buy that explaination.

What would you have one do....keep buying more hardware until vegas
works correctly? Uh... this isn't 1980... I don't think so.

If that is the case...then Vegas is a TOTAL joke. I don't feel vegas
is a TOTAL joke ...even at this point.

thanks,
JD


Karl Caillouet wrote:
>>Hang in there, Joe ... it took a completely new machine before we
got
>>VV working with any stability whatsoever. Prior to that I could
make
>>VV 2.0 lock up at will by minnimizing the track view three times in
a
>>row, but I've never been able to repeat that behavior on another
>>machine, even with some of the same components, like the Video
card.
>>That is why, as tough as it is to swallow, what you are describing
>>really sounds like a system dependent issue from this perspective.
>>
>>Are you still running both versions on the same machine?
>>
>>Good luck.
>>
>>KAC ...
>>
>>Joe Doria wrote:
>>>>Guys, i must say that i apologize if I'm coming off as bashing
this
>>>>release. That is NOT my point at all....I've laid some great

Ok, although I can't get Dr Watson to produce a log file on these
freezes which happen every time I use Vegas Audio 2.0b when re-
sizing, scrolling, clicking to point in the file (it jsut freezes to
hard to be able to create a .log) i can list this:

- To reproduce these freezes/crashes, you MUST HAVE ALL TRACKS
SELECTED (blue),

1. load up a 8+ track 24-bit 44.1 project, throw a couple reverb fx
chains and some plugs on the busses (I have busses 1-4 routing: 1 =
delta 1/2, 2 = delta 3/4, 3=delta 5/6, 4 = delta 7/8).

2. select all tracks...then playback.

3. now during playback resize windows (I usually resize the track
meters window up/down.. that usually does it), skip around, edit
volumes... all the stuff you would do in Vegas - then resize some
more. It probably won't crash right away, it takes a bit but the
resizing will freezethe system.

** I NOT SURE if I couldn't get this to happen when all tracks
weren't selected....but it happend consistently when they were.



UPDATE ON AUDIO SKIPPING, STUTTERING WHEN RESIZING/SCROLLING

I was able to make the stuttering and skipping stop when resizing a
window during playback by making some random guesstimate changes in
the following (sorry i can't be more specific...but in all honesty...
i don't knwo which parameter change fixed this issue...all i know is
that whatever I did with these changes IMEDIATLEY fixed the problems.

- deleted the video track in all projects (even though no video is
being used)
- file\properties\video: changed from NTSC DV to NTSC Standard
- file\properties\ruler: changed to BEATS/MEASURES (that's how I will
be using it when tracking)
- changed preview quality to "PREVIEW" mode
- SOMEHOW....I TURNED OFF VIDEO PREVIEW (supposed to be tab located
next to audio meters.... it is now gone. How do I turn this back on
to verify this was the culprit?).

again, I wish I could get a .log file in DRWATSON....it just won't do
it with this crash/freeze

thanks and hope this gets resolved VERY soon,
JD