Hello joe.
I had this at one time.Did you install with previous vegas still on
computer?
I remember I had to reinstall and also my matrox drivers were acting
up as well.Check those too.
This was an ongoing thing like you are experiencing.If anything email
Peter Haller.

Joe Doria wrote:
>>Asus P3V4X
>>PIII 800mHz
>>196 ram
>>adaptec 29160 U160 scsi card (own IRQ)
>>1 seagate cheetah 4gig = boot/apps, 3 more cheetah for audio/temp
>>drives
>>1 seagate udma 66 20 gig (pri master)
>>1 Maxtor DiamondMax plus 40 (secondary master)
>>1 atapi cd-rom (secondary slave)
>>(2x) Maudio Delta 1010 audio interface (error also happens with
just
>>1 delta 1010) (own IRQ)
>>Creative PCI128
>>3dfx voodoo 2 2k agp video (own IRQ)
>>1 Netgear FAX NIC
>>USB: connected 4x4 Midisport (working)
>>
>>again: the crash occurs when recording more than 40 seconds of 16-
>>tracks, 24-bit/44.1kHz audio at same time.
>>*** THIS REPRODUCES EVERYTIME
>>*** THIS DOES NOT REPRODUCE IN OLD VEGAS 1.0B (works ok)
>>
>>all are setup perfectly and device drivers are current.
>>no tsrs are loaded (extreme minimum)
>>
>>Ok - hope a fix arrives soon. any ETA?
>>
>>thanks,
>>Joe
>>
>>
>>Joe Doria wrote:
>>>>Got the upgrade and am doing tests. Thought you may like
>>>>to know some bugs found in vegas audio 2.0a (build 323).
>>>>
>>>>Below the listed bugs found is the copy/paste from the
>>>>stack dump crash I found in vegas audio 2.0 16 track mono
>>>>(more or less), 24-bit/44.1kHz multitrack recording (all at
>>>>same time).
>>>>
>>>>***THIS ERROR REPRODUCES EVERYTIME WITH THE ABOVE SETTINGS
>>>>WHEN RECORDING OVER 40 SECONDS***
>>>>
>>>>*** THIS ERROR DOES NOT OCCUR WITH SAME SETTINGS /SETUP ON
>>>>OLD VEGAS 1.0B ****
>>>>
>>>>NOTES:
>>>>- I have to have this working of course when I do my 16
>>>>track recordings. I guess I'll have to use the Old Vegas
>>>>1.0b as it works fine - but now my old projects will NOT
>>>>open in 1.0b (ones recorded in 2.0).
>>>>
>>>>- System is tip-top - PIII 800mHz, all drivers are updated,
>>>>and all is great in device manager, no TSRs loaded. I am
>>>>NOT a novice to PC building/repair just to note and build
>>>>DAW's regularly.
>>>>
>>>>- using 1 to 2 Delta 1010 (latest drivers of course)
>>>>
>>>>- Routing and audio prefs are identical to Vegas 1.0b
>>>>(which doesn't produce this error/crash)
>>>>
>>>>Please tell me this is known and will be addressed - it's
>>>>very important.
>>>>
>>>>
>>>>Description:
>>>>
>>>>Get a fatal error and details when pressing stop after
>>>>recording past 40 seconds of 16 tracks mono - 24-
>>>>bit/44.1khz (recording at the same time). I can read
>>>>(copy/paste) the error message (see below), and then it
>>>>gives another error message after saying OK (see also below
>>>>1st error message).
>>>>
>>>>Here is the copy/paste from error in vegas audio 2.0:
>>>>
>>>>Sonic Foundry Vegas Audio
>>>>Version 2.0a (Build 323)
>>>>Exception 0xC0000005 (access violation) READ:0xFFFFFFFF
>>>>IP:0x556B7A
>>>>In Module 'VEGAS.EXE' at Address 0x400000 + 0x156B7A
>>>>Thread: GUI ID=0xFFFD4409 Stack=0x96E000-0x970000
>>>>Registers:
>>>> EAX=00000000 CS=017f EIP=00556b7a EFLGS=00010206
>>>> EBX=0096f050 SS=0187 ESP=0096eda4 EBP=00000000
>>>> ECX=00000010 DS=0187 ESI=00000000 FS=3a0f
>>>> EDX=00557078 ES=0187 EDI=0096f004 GS=0000
>>>>Bytes at CS:EIP:
>>>> 00556B7A: 8B 06 50 FF 15 14 95 5A ..P....Z
>>>> 00556B82: 00 6A 00 6A 01 68 03 10 .j.j.h..
>>>>Stack Dump:
>>>> 0096EDA4: 00000435
>>>> 0096EDA8: 00000224
>>>> 0096EDAC: 0055707E 00400000 + 15707E (VEGAS.EXE)
>>>> 0096EDB0: 00000000
>>>> 0096EDB4: 0096F004 00860000 + 10F004
>>>> 0096EDB8: 0000C074
>>>> 0096EDBC: 0096F01C 00860000 + 10F01C
>>>> 0096EDC0: 0096F050 00860000 + 10F050
>>>> 0096EDC4: 00000000
>>>> 0096EDC8: 00000228
>>>> 0096EDCC: 03781984 03390000 + 3F1984
>>>> 0096EDD0: 00018570
>>>> 0096EDD4: 03781980 03390000 + 3F1980
>>>> 0096EDD8: 0096EE20 00860000 + 10EE20
>>>> 0096EDDC: BFF7B962 BFF70000 + B962 (KERNEL32.DLL)
>>>> 0096EDE0: 00740000 00740000 + 0
>>>>> 0096EDE4: BFF7B977 BFF70000 + B977 (KERNEL32.DLL)
>>>>> 0096EE00: BFFC94C0 BFF70000 + 594C0 (KERNEL32.DLL)
>>>>> 0096EE0C: BFF71547 BFF70000 + 1547 (KERNEL32.DLL)
>>>>> 0096EE14: BFFC05B4 BFF70000 + 505B4 (KERNEL32.DLL)
>>>>> 0096EE18: BFF79230 BFF70000 + 9230 (KERNEL32.DLL)
>>>>> 0096EE24: BFF74A5C BFF70000 + 4A5C (KERNEL32.DLL)
>>>>> 0096EE3C: BFB993E5 BFB70000 + 293E5 (COMCTL32.DLL)
>>>>> 0096EE48: BFB846DA BFB70000 + 146DA (COMCTL32.DLL)
>>>>> 0096EE58: BFC02471 BFC00000 + 2471 (USER32.DLL)
>>>>> 0096EE74: BFF714D9 BFF70000 + 14D9 (KERNEL32.DLL)
>>>>> 0096EE78: 0054017F 00400000 + 14017F (VEGAS.EXE)
>>>> 0096EE7C: 0096EE84 00860000 + 10EE84
>>>> 0096EE80: 000235E0
>>>> 0096EE84: 03DB8E9A 03C10000 + 1A8E9A
>>>> 0096EE88: 000017B7
>>>>> 0096EEC8: BFF714D9 BFF70000 + 14D9 (KERNEL32.DLL)
>>>>> 0096EED4: BFFC0187 BFF70000 + 50187 (KERNEL32.DLL)
>>>>> 0096EED8: BFF71547 BFF70000 + 1547 (KERNEL32.DLL)
>>>>> 0096EEEC: 00407737 00400000 + 7737 (VEGAS.EXE)
>>>> 0096EEF0: 00000001
>>>> 0096EEF4: 00000EC4
>>>> 0096EEF8: 00000000
>>>> 0096EEFC: 0000001F
>>>>> 0096EF28: BFC0D6C0 BFC00000 + D6C0 (USER32.DLL)
>>>>> 0096EF54: 0187EF94 01760000 + 11EF94 (ASFPLUG.DLL)
>>>> 0096EF58: 00000020
>>>> 0096EF5C: 1294BF68 056F0000 + D25BF68
>>>> 0096EF60: 35E017AF 056F0000 + 307117AF
>>>> 0096EF64: 12990002 056F0000 + D2A0002
>>>>> 0096EF6C: BFF728A2 BFF70000 + 28A2 (KERNEL32.DLL)
>>>>> 0096EF8C: BFC024B4 BFC00000 + 24B4 (USER32.DLL)
>>>>> 0096EF9C: BFF741F7 BFF70000 + 41F7 (KERNEL32.DLL)
>>>>> 0096EFAC: BFF7126A BFF70000 + 126A (KERNEL32.DLL)
>>>>> 0096EFB8: BFC0D6C0 BFC00000 + D6C0 (USER32.DLL)
>>>>> 0096EFD0: BFF741F7 BFF70000 + 41F7 (KERNEL32.DLL)
>>>>> 0096EFD4: BFFC9490 BFF70000 + 59490 (KERNEL32.DLL)
>>>>> 0096F000: BFF7363B BFF70000 + 363B (KERNEL32.DLL)
>>>>> 0096F020: BFF94407 BFF70000 + 24407 (KERNEL32.DLL)
>>>>> 0096F030: BFF719B8 BFF70000 + 19B8 (KERNEL32.DLL)
>>>>> 0096F03C: BFF7186D BFF70000 + 186D (KERNEL32.DLL)
>>>>> 0096F07C: 00556E70 00400000 + 156E70 (VEGAS.EXE)
>>>> 0096F080: 00000000
>>>> 0096F084: 00000000
>>>> 0096F088: 00000002
>>>> 0096F08C: 00000224
>>>>> 0096F0B8: 00556E70 00400000 + 156E70 (VEGAS.EXE)
>>>>- - -
>>>> 0096FFF0: 3A172CAE 056F0000 + 34A82CAE
>>>> 0096FFF4: 8333DFEC 8331F000 + 1EFEC
>>>> 0096FFF8: BFF89DD5 BFF70000 + 19DD5 (KERNEL32.DLL)
>>>> 0096FFFC: 00000000
>>>>
>>>>
>>>>Here is the 2nd error/crash message (before booting to
>>>>desktop after error)
>>>>____________________________________________________________
>>>>__________
>>>>
>>>>
>>>>VEGAS caused an invalid page fault in
>>>>module VEGAS.EXE at 017f:00556b7a.
>>>>Registers:
>>>>EAX=00000000 CS=017f EIP=00556b7a EFLGS=00010206
>>>>EBX=0096f050 SS=0187 ESP=0096eda4 EBP=00000000
>>>>ECX=00000010 DS=0187 ESI=00000000 FS=3a0f
>>>>EDX=00557078 ES=0187 EDI=0096f004 GS=0000
>>>>Bytes at CS:EIP:
>>>>8b 06 50 ff 15 14 95 5a 00 6a 00 6a 01 68 03 10
>>>>Stack dump:
>>>>00000435 00000224 0055707e 00000000 0096f004 0000c074
>>>>0096f01c 0096f050 00000000 00000228 03781984 00018570
>>>>03781980 0096ee20 bff7b962 00740000
>>>>
>>>>
>>>>
>>>>Other bug (I am sure you are aware of) is:
>>>>- blank wave(s) still remain after selecting DELETE OR
>>>>DELETE ALL takes after recording
>>>>
>>>>
>>>>
>>>>thanks and please let me know if this will be fixed. It is
>>>>a major functionality bug, so I assume it will be.
>>>>
>>>>Joe Doria
>>>>www.accessline.com

Hey,

I appreciate the responses but....

- (to david ruby) please resopnd only once. I don't want to cloud up
this post with multiple copies of the same reply. It may get
overlooked and it's too important right now.
Also david: please re-read the hardware i listed - I don't own a
Matrox card

- Please re-read: I don't have Vegas Video.... I own Vegas Audio 2.0.

- I am NOT going to format/re-install squat until I speak with a tech
at SF (in the works now - I will update y'all). I am in the middle
of a HUGE voicign revamp, demos, etc.

There is too much stuff on this system, it is TIP-TOP (I keep a
stable system), and I'm not diving into re-installs like the others
here....I would rather work the problem, find the bug and send to SF
to fix......not blow it away and hope for the best.
Plus - it will be better for ALL in the end - as finding the problem
and fix is better than an un-warrented re-install.

thanks though,
Joe

Karl Caillouet wrote:
>>I tried to keep both the old version of Vegas and the upgrade on
the
>>same Win98 machine and had similar problems. They cleared up for
the
>>most part upon deleting all vestiges of both versions and then
>>reinstalling the upgrade.
>>
>>Nonetheless, there were still a good many abberations that I never
>>solved after putting the upgrade on the same machine as a previous
>>version ... like Vegas Video blue screening without fail the third
>>time you hit "Minnimize All Tracks" menu ... and the stability was
>>never quite the same as with the old VP installation.
>>
>>I did the same thing on an NT machine with no problems, which would
>>lead me to believe that lingering registry issues with some
>>installations of Win98 may be at work ... and there is only one
sure
>>cure for that that I am aware of.
>>
>>I suspect that on some machines the best thing to do is to reformat
>>the OS drive and start from scratch when you run across the
problems
>>you are experiencing.
>>
>>We have an installation of Vegas Video on a freshly formatted Win2K
>>machine and it is rock solid.
>>
>>Good luck.
>>
>>KAC ...
>>
>>
>>Joe Doria wrote:
>>>>Asus P3V4X
>>

>>Also david: please re-read the hardware i listed - I don't own a
>>Matrox card


I think he meant video card drivers in general


>>
>>There is too much stuff on this system, it is TIP-TOP (I keep a
>>stable system), and I'm not diving into re-installs like the others
>>here....I would rather work the problem, find the bug and send to
SF
>>to fix......not blow it away and hope for the best.
>>Plus - it will be better for ALL in the end - as finding the
problem
>>and fix is better than an un-warrented re-install.


Ontrack makes a neat program called "fix it 2000"
If as Karl suggests, it is some ancient registry junk causing the
problem ( lingering registry happy crappy has been a problem in old
vegas too), fix it 2000 can show you "unused" (heh) stuff in your
registry and you can delete it....AFTER you used Norton Ghost to
clone your system drive of course...Maybe you can fix it that way...
I ,like you, hate to re f-disk my drive because I make extensive use
of a dx plug called "drummagog" and have to re-record ALL my drums
after a format

Sorry. I am just slammed with work doing demos, my own CD work, and
deadlines. I apologize for freaking out there...just anxious for a
response.

I shouldn't complain about any suggestions.

Well, I don't know. I guess I'll have to go back using 1.0b. I
can't re-install right now (work) - it wil have to wait till time
opens up (when the hell that is...I havn't a clue).

Reinstall IS the best way to see if it's reg problems. damn!
Murphys law is in FULL affect.

Joe, I too have similar problems with va2a. I too, am completely OCD
about my system and very knowledgeable with PCs. Don't waste your
time, (unless you have nothing better to...) and go back to vp1b.
VP1b may not be as 'robust' as VA2a, but at least it's more solid.
Wait until the next release is out (rumors has it out in September)
then read the buzz and see if the kinks have been taken out it. (I
will)
I trashed one of my mixes with 2A and had to do it over again in
VP1b. I can run identical mixes on either version, and VP1b runs it
flawlessly while VA2a chokes and sputters, so like you, I know it's
not my system.
Apart from the problems you noted:
Rendering - useless
CPU - consumption is way up
Waveforms that don't redraw themselves.

I want VA2B to be everything VP1b was (and more!) because it IS a
great program and want it it to work.

It's unfortunate that they didn't sufficiently beta test this program
before releasing it. I wouldn't blame the programmers, though; I
blame sales and management, because I'm sure they knew this software
was about 2 months premature of its release.

As a customer, user, and shareholder, I'm disappointed SF hasn't made
a public statement apologizing for wasting our time ($$) and throwing
added bugs into an already buggy Windows.

PS. Is anyone out there using WIN2K and has it been worth it?

My system:
P3-700 - 128meg ram - maudio Delta 66 - SBlive - Viper Ultra 770 -
SCSI HD and ATA/66 HD - WIN98SE

SF - do not delete this post as you did with my prior posts. I'm not
a crack, hack or even Victor. I'm not trashing the product, just this
release. I own other SF products and I'm COMPLETELY happy with them.
_________________________________________________________________
Joe Doria wrote:
>>Sorry. I am just slammed with work doing demos, my own CD work,
and
>>deadlines. I apologize for freaking out there...just anxious for a
>>response.
>>
>>I shouldn't complain about any suggestions.
>>
>>Well, I don't know. I guess I'll have to go back using 1.0b. I
>>can't re-install right now (work) - it wil have to wait till time
>>opens up (when the hell that is...I havn't a clue).
>>
>>Reinstall IS the best way to see if it's reg problems. damn!
>>Murphys law is in FULL affect.
>>
>>
>>
>>

I know it is frustrating to go from a stable system to an unstable
one with projects sitting on the front burner. Got caught in the same
trap ... we got to where we wouldn't even turn on Vegas Video in
front of a client after upgrading from a very stable Vegas Pro
installation.

Software aside, the point is that it is highly unlikely that your
problem is from an actual BUG in the program ... it is more likely
caused by an issue specific to your system's unique configuration and
software/hardware mix, otherwise everyone else would be screaming
about the exact same problem.

By all means call tech support, but as unpleasant as it is,
reinstalling and uninstalling, or failing that, reformatting and
starting over, is often the quickest way to a *permanent* resolution
of these types of system specific issues.

Besides, I certain wouldn't want to hold my breath waiting for a
specific BUG fix release to fix the problem while you wait to do your
important project.

KAC ...


Joe Doria wrote:
>>Sorry. I am just slammed with work doing demos, my own CD work,
and
>>deadlines. I apologize for freaking out there...just anxious for a
>>response.
>>
>>I shouldn't complain about any suggestions.
>>
>>Well, I don't know. I guess I'll have to go back using 1.0b. I
>>can't re-install right now (work) - it wil have to wait till time
>>opens up (when the hell that is...I havn't a clue).
>>
>>Reinstall IS the best way to see if it's reg problems. damn!
>>Murphys law is in FULL affect.

Absolutely ... Vegas Video (we just use the audio portion)is ROCK
solid on our new DAW running Win2k ... said machine put together
because we couldn't get VV to run reliably on our old Win98 box, for
whatever reason.

One caveat with the Delta's drivers for Win2k ... they do NOT work
with machines with dual processors at this time.

KAC ...

George Marrero wrote:

>>PS. Is anyone out there using WIN2K and has it been worth it?
>>
>>My system:
>>P3-700 - 128meg ram - maudio Delta 66 - SBlive - Viper Ultra 770 -
>>SCSI HD and ATA/66 HD - WIN98SE

Joe I am sorry I thought your hardware was a matrox vid card as I
skimmed by your post.Sorry for that.Well as far as repeated post.This
is not my doing thanx.I am not a teen full of spunk just learning the
curves.My eyes do play tricks but not my ears or fingers.
Just relax.I have done this reinstall routine many times.Also you
will find that if you have loaded any thing in the past couple of
weeks;trial software,fx,etc.You can currupt the registry causing many
probs.Norton and other help fixers are a no win situation as well
they do not see all that happens.Plain and simple answer is to blow
out your system every 6 months or so.It is like getting an oil change
if you use your rig on a daily 8 hr day.Run a network so you can
easily store your waves and editlists on another computer
This is what works and always has for us.
Hope something has helped.
goodluck.

Joe Doria wrote:
>>Sorry. I am just slammed with work doing demos, my own CD work,
and
>>deadlines. I apologize for freaking out there...just anxious for a
>>response.
>>
>>I shouldn't complain about any suggestions.
>>
>>Well, I don't know. I guess I'll have to go back using 1.0b. I
>>can't re-install right now (work) - it wil have to wait till time
>>opens up (when the hell that is...I havn't a clue).
>>
>>Reinstall IS the best way to see if it's reg problems. damn!
>>Murphys law is in FULL affect.
>>
>>
>>
>>

This system was rebuilt 3 months ago (format/reinstall)....which is
why I'm questioning a reinstall now. I agree about the gains in a
format re-isntall (roughly once a year).

I did choose to install Vegas 20 alongside 1.0b (didn't un-install
1.0b)...... and THANK GOD !!! I can at least use Vegas 1.0b as usual.

The techs are looking into it, I sent over a bunch of repro/debug
info...blah..blah. Let's see what they say..... both about re-
installs, re-format, or quick fixs (until an update hits).

thanks,
JoeD

David W. Ruby wrote:
>>Joe I am sorry I thought your hardware was a matrox vid card as I
>>skimmed by your post.Sorry for that.Well as far as repeated
post.This
>>is not my doing thanx.I am not a teen full of spunk just learning
the
>>curves.My eyes do play tricks but not my ears or fingers.
>>Just relax.I have done this reinstall routine many times.Also you
>>will find that if you have loaded any thing in the past couple of
>>weeks;trial software,fx,etc.You can currupt the registry causing
many
>>probs.Norton and other help fixers are a no win situation as well
>>they do not see all that happens.Plain and simple answer is to blow
>>out your system every 6 months or so.It is like getting an oil
change
>>if you use your rig on a daily 8 hr day.Run a network so you can
>>easily store your waves and editlists on another computer
>>This is what works and always has for us.
>>Hope something has helped.
>>goodluck.
>>
>>Joe Doria wrote:
>>>>Sorry. I am just slammed with work doing demos, my own CD work,
>>and
>>>>deadlines. I apologize for freaking out there...just anxious for
a
>>>>response.
>>>>
>>>>I shouldn't complain about any suggestions.
>>>>
>>>>Well, I don't know. I guess I'll have to go back using 1.0b. I
>>>>can't re-install right now (work) - it wil have to wait till time
>>>>opens up (when the hell that is...I havn't a clue).
>>>>
>>>>Reinstall IS the best way to see if it's reg problems. damn!
>>>>Murphys law is in FULL affect.
>>>>
>>>>
>>>>
>>>>

Thank you Karl. Also, thanks for the tip on the dual processor/delta
driver problem, as this 'was' the route I was going towards. I'll sit
on my single cpu for a bit, but apart from a Tyan or ASUS dual cpu
board, is there anything you recommend? I don't have, nor will I buy
a board that uses RDRAM, because I can't afford it. Conventional
pc100 DIMMs is what I use.

As for WIN2k permissions and such, are there any quirks I experience
with it and VP1b?
Thank you,
George

PS
Does VV have the same rendering problems as VA?
___________________________________________________________________
Karl Caillouet wrote:
>>Absolutely ... Vegas Video (we just use the audio portion)is ROCK
>>solid on our new DAW running Win2k ... said machine put together
>>because we couldn't get VV to run reliably on our old Win98 box,
for
>>whatever reason.
>>
>>One caveat with the Delta's drivers for Win2k ... they do NOT work
>>with machines with dual processors at this time.
>>
>>KAC ...
>>
>>George Marrero wrote:
>>
>>>>PS. Is anyone out there using WIN2K and has it been worth it?
>>>>
>>>>My system:
>>>>P3-700 - 128meg ram - maudio Delta 66 - SBlive - Viper Ultra 770 -

>>>>SCSI HD and ATA/66 HD - WIN98SE
>>

>>Apart from the problems you noted:
>>Rendering - useless


Why do you say this? I have some concerns about the rendering process
too, what is yours?

>>CPU - consumption is way up
>>Waveforms that don't redraw themselves.


Inaccurate waveforms was a problem in 1.0b too....you always had to
delete the *.sfk files when you did a big change or recorded,
otherwise the front of your snare would not be where the drawing
showed it...for example


>>PS. Is anyone out there using WIN2K and has it been worth it?
>>
>>My system:
>>P3-700 - 128meg ram - maudio Delta 66 - SBlive - Viper Ultra 770 -
>>SCSI HD and ATA/66 HD - WIN98SE
>>


I love win2k so much I could barf...if you have drivers for win2k for
your hardware, and can deal with the config stuff, you will be a
happy clam....just tricky getting and installing drivers...still
there is no release version of echo drivers...and other drivers too
are weird, but once it works, it WORKS

Hey Aaron:

>>>>Rendering - useless
>>Why do you say this? I have some concerns about the rendering
process
>>too, what is yours?

Well, for whatever reason, if you have a number of tracks that you
want to mix down, the result will be totally out of whack. By 'whack'
I mean: the levels will be totally off as compared to the original.
Not only is the output level some 12 to 18db lower, but the levels
among the tracks are completely wrong. I could try to save the file
in any format and it doesn't matter; it's all wrong. Sure, I could go
out to my board in analog and come back into the delta66 and back to
digital, but this isn't optimal....

>>>>Waveforms that don't redraw themselves.
>>
>>
>>Inaccurate waveforms was a problem in 1.0b too....you always had to
>>delete the *.sfk files when you did a big change or recorded,
>>otherwise the front of your snare would not be where the drawing
>>showed it...for example
>>
I really haven't noticed this in vp1b....maybe I'm doing something
wrong....
>>I love win2k so much I could barf...if you have drivers for win2k
for
>>your hardware, and can deal with the config stuff, you will be a
>>happy clam....just tricky getting and installing drivers...still
>>there is no release version of echo drivers...and other drivers too
>>are weird, but once it works, it WORKS
>>
Thank you for your comments on win2k. I've also heard similar from
others, so yes, I have the latest win2k drivers and the disk is in
the mail.....I can't wait!!!!
George

It states on the system requirements that Vegas Audio requires
Windows 98 Second Edition (SE). If you're trying to run it on an
older version of Win98, that may be part of the problem. There are
some fundamental system differences between Windows 98 and Windows 98
Second Edition.

Karl Caillouet wrote:
>>Absolutely ... Vegas Video (we just use the audio portion)is ROCK
>>solid on our new DAW running Win2k ... said machine put together
>>because we couldn't get VV to run reliably on our old Win98 box,
for
>>whatever reason.
>>
>>One caveat with the Delta's drivers for Win2k ... they do NOT work
>>with machines with dual processors at this time.
>>
>>KAC ...
>>
>>George Marrero wrote:
>>
>>>>PS. Is anyone out there using WIN2K and has it been worth it?
>>>>
>>>>My system:
>>>>P3-700 - 128meg ram - maudio Delta 66 - SBlive - Viper Ultra 770 -

>>>>SCSI HD and ATA/66 HD - WIN98SE
>>

George Marrero wrote:
>>Hey Aaron:
>>
>>>>>>Rendering - useless
>>>>Why do you say this? I have some concerns about the rendering
>>process
>>>>too, what is yours?
>>
>>Well, for whatever reason, if you have a number of tracks that you
>>want to mix down, the result will be totally out of whack.
By 'whack'
>>I mean: the levels will be totally off as compared to the original.
>>Not only is the output level some 12 to 18db lower, but the levels
>>among the tracks are completely wrong. I could try to save the file
>>in any format and it doesn't matter; it's all wrong. Sure, I could
go
>>out to my board in analog and come back into the delta66 and back
to
>>digital, but this isn't optimal....

OK now you got me scared...I render constantly, I render fx to save
cpu power, I render drumagog triggered tracks...I render groups of
vocals together, and very rarely, I do render a mix on Vegas, but I
havent noticed thios porblem(I think)...although that would explain
why sometimes I have to normalise a previously peaking at -0.3
file...hmmmm


EEEEK

Yeah, I always render my projects as I go along in order to conserve
CPU and in case the system crashes and I lose the .veg files... I do
anticipate the Gods of SF to check this and other promiment bugs
before the next 'update'.

And yes, I use W98SE at the moment............I going 2K soon....and
then I'll try VA2a again just for s & gs, though I'm almost sure the
bugs will persist until VA2b, which hopefully will have gone thru a
fine-toothed comb prior to my slow 28.8k download.....God help us.
G
Aaron wrote:

>>OK now you got me scared...I render constantly, I render fx to save
>>cpu power, I render drumagog triggered tracks...I render groups of
>>vocals together, and very rarely, I do render a mix on Vegas, but I
>>havent noticed thios porblem(I think)...although that would explain
>>why sometimes I have to normalise a previously peaking at -0.3
>>file...hmmmm
>>
>>
>>EEEEK
>>

There is definitely some funkiness with rendering in VV and VA 2.0a.
There is a known bug which causes double attenuation in a mixed file
if you have Bus gain reduction with an insertable FX in the chain.
This will be fixed in 2.0b (I hope). And as for the redering of whole
projects... I may be somewhat off here but the problem is that when
you render a multiple bus project, Vegas needs to figure out how to
prevent the output file from completely clipping. There is no way to
know if you have 4 busses routed to four outputs on your sound card
to your external mixer, how that mix is set up externally.
Essentially when you have separate busses in Vegas, you are telling
it that you want to mix elsewhere. If you want to mix internally, you
basically need to mix to one bus to know what the results will be.
This is why the master bus idea is essential - we need to be able to
route sub busses to an assignable master bus which goes to ONE
output. So, the problem is, if you have 4 busses, how does Vegas
mix...? you have some serious summing going on so Vegas needs to
attenuate all the busses before summing them. I think right now it
does some kind of equal weight attenuation of 6dB across all the
busses but the problem there is that the musical content of each buss
isn't necessarily equally weited and the attenuation might affect one
more than the other which results in the unpredictable mixes...

Basically the only thing that can be done to really remedy this is to
have a master bus (which is coming, just don't expect it in a 2.0
update). Or, mix to one bus only. Or bounce each bus individually,
put those mixes into new tracks and bus to one output and adjust
master levels. I'd love to hear other people's thoughts on this.

And, Peter or anyone else, feel free to correct my bad explanation of
how mixing works/doesn't work in Vegas. I know it was a shoddy one,
but approximate.

Charles.

George Marrero wrote:
>>Yeah, I always render my projects as I go along in order to
conserve
>>CPU and in case the system crashes and I lose the .veg files... I
do
>>anticipate the Gods of SF to check this and other promiment bugs
>>before the next 'update'.
>>
>>And yes, I use W98SE at the moment............I going 2K
soon....and
>>then I'll try VA2a again just for s & gs, though I'm almost sure
the
>>bugs will persist until VA2b, which hopefully will have gone thru a
>>fine-toothed comb prior to my slow 28.8k download.....God help us.
>>G
>>Aaron wrote:
>>
>>>>OK now you got me scared...I render constantly, I render fx to
save
>>>>cpu power, I render drumagog triggered tracks...I render groups
of
>>>>vocals together, and very rarely, I do render a mix on Vegas, but
I
>>>>havent noticed thios porblem(I think)...although that would
explain
>>>>why sometimes I have to normalise a previously peaking at -0.3
>>>>file...hmmmm
>>>>
>>>>
>>>>EEEEK
>>>>

Thanks ... but having beta tested and run SE exclusively since we
received it as a member of MSDN, that was definitely not an issue in
this case.

KAC ...

Brett Sherman wrote:
>>It states on the system requirements that Vegas Audio requires
>>Windows 98 Second Edition (SE). If you're trying to run it on an
>>older version of Win98, that may be part of the problem. There are
>>some fundamental system differences between Windows 98 and Windows
98
>>Second Edition.
>>
>>Karl Caillouet wrote:
>>>>Absolutely ... Vegas Video (we just use the audio portion)is ROCK
>>>>solid on our new DAW running Win2k ... said machine put together
>>>>because we couldn't get VV to run reliably on our old Win98 box,
>>for
>>>>whatever reason.

well - I just tried recording 16 tracks at 24 bit (44.1 stereo) for
more than 40 seconds and I just got the same above mentioned crash.
Whoa.

George Marrero wrote:
>>Yeah, I always render my projects as I go along in order to
conserve
>>CPU and in case the system crashes and I lose the .veg files... I
do
>>anticipate the Gods of SF to check this and other promiment bugs
>>before the next 'update'.
>>
>>And yes, I use W98SE at the moment............I going 2K
soon....and
>>then I'll try VA2a again just for s & gs, though I'm almost sure
the
>>bugs will persist until VA2b, which hopefully will have gone thru a
>>fine-toothed comb prior to my slow 28.8k download.....God help us.
>>G
>>Aaron wrote:
>>
>>>>OK now you got me scared...I render constantly, I render fx to
save
>>>>cpu power, I render drumagog triggered tracks...I render groups
of
>>>>vocals together, and very rarely, I do render a mix on Vegas, but
I
>>>>havent noticed thios porblem(I think)...although that would
explain
>>>>why sometimes I have to normalise a previously peaking at -0.3
>>>>file...hmmmm
>>>>
>>>>
>>>>EEEEK
>>>>

I was trying to repro this 24 bit bug and I think I got it. I tried
to record 16 tracks and then 10 and both times I had all tracks
minimized. Both times it crashed. Then I did the same thing and just
left the tracks at their default size and no crash. It also does this
at 16 bit.

Yikes. Anyone else able to repro this?

George Marrero wrote:
>>Yeah, I always render my projects as I go along in order to
conserve
>>CPU and in case the system crashes and I lose the .veg files... I
do
>>anticipate the Gods of SF to check this and other promiment bugs
>>before the next 'update'.
>>
>>And yes, I use W98SE at the moment............I going 2K
soon....and
>>then I'll try VA2a again just for s & gs, though I'm almost sure
the
>>bugs will persist until VA2b, which hopefully will have gone thru a
>>fine-toothed comb prior to my slow 28.8k download.....God help us.
>>G
>>Aaron wrote:
>>
>>>>OK now you got me scared...I render constantly, I render fx to
save
>>>>cpu power, I render drumagog triggered tracks...I render groups
of
>>>>vocals together, and very rarely, I do render a mix on Vegas, but
I
>>>>havent noticed thios porblem(I think)...although that would
explain
>>>>why sometimes I have to normalise a previously peaking at -0.3
>>>>file...hmmmm
>>>>
>>>>
>>>>EEEEK
>>>>

last one about the crash:
Ok - this is the way you have to repro this:
It only happens when the tracks are all selected at the same time.
Create 10 tracks. Ctrl-a to select all. Minimize all with the ~ key.
arm a track for record (which arms all). record for 10 seconds and
then hit enter. You will crash. The funny thing is, if you unselect
the tracks and then select them all again, this does NOT happen.
Go figure.
George Marrero wrote:
>>Yeah, I always render my projects as I go along in order to
conserve
>>CPU and in case the system crashes and I lose the .veg files... I
do
>>anticipate the Gods of SF to check this and other promiment bugs
>>before the next 'update'.
>>
>>And yes, I use W98SE at the moment............I going 2K
soon....and
>>then I'll try VA2a again just for s & gs, though I'm almost sure
the
>>bugs will persist until VA2b, which hopefully will have gone thru a
>>fine-toothed comb prior to my slow 28.8k download.....God help us.
>>G
>>Aaron wrote:
>>
>>>>OK now you got me scared...I render constantly, I render fx to
save
>>>>cpu power, I render drumagog triggered tracks...I render groups
of
>>>>vocals together, and very rarely, I do render a mix on Vegas, but
I
>>>>havent noticed thios porblem(I think)...although that would
explain
>>>>why sometimes I have to normalise a previously peaking at -0.3
>>>>file...hmmmm
>>>>
>>>>
>>>>EEEEK
>>>>

Charles: I have to say that the point is moot because, this is not a
problem with VP1b.....Also, I check my total level out by using the
control panel on my Delta 66. I've yet to get any clipping. I
normalize all my waveforms to -.1db, mix, check levels and render.
Never had a problem doing it this way.....
George

Charles de Montebello wrote:
>>There is definitely some funkiness with rendering in VV and VA
2.0a.
>>There is a known bug which causes double attenuation in a mixed
file
>>if you have Bus gain reduction with an insertable FX in the chain.
>>This will be fixed in 2.0b (I hope). And as for the redering of
whole
>>projects... I may be somewhat off here but the problem is that when
>>you render a multiple bus project, Vegas needs to figure out how to
>>prevent the output file from completely clipping. There is no way
to
>>know if you have 4 busses routed to four outputs on your sound card
>>to your external mixer, how that mix is set up externally.
>>Essentially when you have separate busses in Vegas, you are telling
>>it that you want to mix elsewhere. If you want to mix internally,
you
>>basically need to mix to one bus to know what the results will be.
>>This is why the master bus idea is essential - we need to be able
to
>>route sub busses to an assignable master bus which goes to ONE
>>output. So, the problem is, if you have 4 busses, how does Vegas
>>mix...? you have some serious summing going on so Vegas needs to
>>attenuate all the busses before summing them. I think right now it
>>does some kind of equal weight attenuation of 6dB across all the
>>busses but the problem there is that the musical content of each
buss
>>isn't necessarily equally weited and the attenuation might affect
one
>>more than the other which results in the unpredictable mixes...
>>
>>Basically the only thing that can be done to really remedy this is
to
>>have a master bus (which is coming, just don't expect it in a 2.0
>>update). Or, mix to one bus only. Or bounce each bus individually,
>>put those mixes into new tracks and bus to one output and adjust
>>master levels. I'd love to hear other people's thoughts on this.
>>
>>And, Peter or anyone else, feel free to correct my bad explanation
of
>>how mixing works/doesn't work in Vegas. I know it was a shoddy one,
>>but approximate.
>>
>>Charles.
>>
>>George Marrero wrote:
>>>>Yeah, I always render my projects as I go along in order to
>>conserve
>>>>CPU and in case the system crashes and I lose the .veg files... I
>>do
>>>>anticipate the Gods of SF to check this and other promiment bugs
>>>>before the next 'update'.
>>>>
>>>>And yes, I use W98SE at the moment............I going 2K
>>soon....and
>>>>then I'll try VA2a again just for s & gs, though I'm almost sure
>>the
>>>>bugs will persist until VA2b, which hopefully will have gone thru
a
>>>>fine-toothed comb prior to my slow 28.8k download.....God help us.
>>>>G
>>>>Aaron wrote:
>>>>
>>>>>>OK now you got me scared...I render constantly, I render fx to
>>save
>>>>>>cpu power, I render drumagog triggered tracks...I render groups
>>of
>>>>>>vocals together, and very rarely, I do render a mix on Vegas,
but
>>I
>>>>>>havent noticed thios porblem(I think)...although that would
>>explain
>>>>>>why sometimes I have to normalise a previously peaking at -0.3
>>>>>>file...hmmmm
>>>>>>
>>>>>>
>>>>>>EEEEK
>>>>>>

Glad to hear it. I removed VP1.0b long ago... So, I think there are
definitely issues to be dealt with with 2.0.

George Marrero wrote:
>>Charles: I have to say that the point is moot because, this is not
a
>>problem with VP1b.....Also, I check my total level out by using the
>>control panel on my Delta 66. I've yet to get any clipping. I
>>normalize all my waveforms to -.1db, mix, check levels and render.
>>Never had a problem doing it this way.....
>>George
>>
>>Charles de Montebello wrote:
>>>>There is definitely some funkiness with rendering in VV and VA
>>2.0a.
>>>>There is a known bug which causes double attenuation in a mixed
>>file
>>>>if you have Bus gain reduction with an insertable FX in the
chain.
>>>>This will be fixed in 2.0b (I hope). And as for the redering of
>>whole
>>>>projects... I may be somewhat off here but the problem is that
when
>>>>you render a multiple bus project, Vegas needs to figure out how
to
>>>>prevent the output file from completely clipping. There is no way
>>to
>>>>know if you have 4 busses routed to four outputs on your sound
card
>>>>to your external mixer, how that mix is set up externally.
>>>>Essentially when you have separate busses in Vegas, you are
telling
>>>>it that you want to mix elsewhere. If you want to mix internally,
>>you
>>>>basically need to mix to one bus to know what the results will
be.
>>>>This is why the master bus idea is essential - we need to be able
>>to
>>>>route sub busses to an assignable master bus which goes to ONE
>>>>output. So, the problem is, if you have 4 busses, how does Vegas
>>>>mix...? you have some serious summing going on so Vegas needs to
>>>>attenuate all the busses before summing them. I think right now
it
>>>>does some kind of equal weight attenuation of 6dB across all the
>>>>busses but the problem there is that the musical content of each
>>buss
>>>>isn't necessarily equally weited and the attenuation might affect
>>one
>>>>more than the other which results in the unpredictable mixes...
>>>>
>>>>Basically the only thing that can be done to really remedy this
is
>>to
>>>>have a master bus (which is coming, just don't expect it in a 2.0
>>>>update). Or, mix to one bus only. Or bounce each bus
individually,
>>>>put those mixes into new tracks and bus to one output and adjust
>>>>master levels. I'd love to hear other people's thoughts on this.
>>>>
>>>>And, Peter or anyone else, feel free to correct my bad
explanation
>>of
>>>>how mixing works/doesn't work in Vegas. I know it was a shoddy
one,
>>>>but approximate.
>>>>
>>>>Charles.
>>>>
>>>>George Marrero wrote:
>>>>>>Yeah, I always render my projects as I go along in order to
>>>>conserve
>>>>>>CPU and in case the system crashes and I lose the .veg files...
I
>>>>do
>>>>>>anticipate the Gods of SF to check this and other promiment
bugs
>>>>>>before the next 'update'.
>>>>>>
>>>>>>And yes, I use W98SE at the moment............I going 2K
>>>>soon....and
>>>>>>then I'll try VA2a again just for s & gs, though I'm almost
sure
>>>>the
>>>>>>bugs will persist until VA2b, which hopefully will have gone
thru
>>a
>>>>>>fine-toothed comb prior to my slow 28.8k download.....God help
us.
>>>>>>G
>>>>>>Aaron wrote:
>>>>>>
>>>>>>>>OK now you got me scared...I render constantly, I render fx
to
>>>>save
>>>>>>>>cpu power, I render drumagog triggered tracks...I render
groups
>>>>of
>>>>>>>>vocals together, and very rarely, I do render a mix on Vegas,
>>but
>>>>I
>>>>>>>>havent noticed thios porblem(I think)...although that would
>>>>explain
>>>>>>>>why sometimes I have to normalise a previously peaking at -
0.3
>>>>>>>>file...hmmmm
>>>>>>>>
>>>>>>>>
>>>>>>>>EEEEK
>>>>>>>>