Difference between Vegas Pro and Audio?

karlc wrote on 8/8/2000, 11:47 AM

Look in message 2194 on this forum. As far as I can tell, Charle de
Montebello did good job of illuminating some of the major differences
between VP AND the audio portion of VV from a user perspective. I
printed out this message and stuck a copy in our control room
documentation binder for reference purposes.

We purchased the upgrade to VV and are still tying to get it to run
as solidly as VP did on our Win98 DAW, not much luck so far. In all
fairness, no one else seems to be having problems to the extent we
are.

Actually, we've now focused our attention on gearing up Win2K on a
Dual PIII 550 that fell in our lap. We've already loaded the OS and
Vegas Video on the box, but don't have a sound card installed yet ...
we have a Soundscape Mixtreme package on order, partially based on
Aaron's experience with the card and DA-88's and the fact that our
MOTU 2408 is basically worthless with the latest in industrial grade
operating systems, along with a Seagate ST318404LW 18 GB 10,000RPM
SCSI Drive and A19160 Controller Card.

On that note, I talked to Matrox this morning and according to them
their latest beta drivers (5.11) for a G400 Dual Head should be solid
on Win2k ... any DH users tried them yet?

It remains to be seen whether all these pieces will co-exist and make
us as happy, or give us as much return on investment, as Vegas Pro
has this past year.

Vegas Pro was the most solid audio software program I've run in 20
years of computing .... hope you have the same luck with Vegas Audio.

FWIW

KAC ...

Dave Wallingford wrote:
>>Hello all, and thank you for the helpful answers to my
>>previous questions.
>>I can't seem to find a page where the differences between
>>Vegas Pro and Vegas Audio are outlined. Does such a page
>>exist? Has anyone purchased the upgrade? If so, what are
>>the biggest differences you can find?
>>Thanks!
>>-Dave

PipelineAudio wrote on 8/8/2000, 1:52 PM

Karl Caillouet wrote:
>>On that note, I talked to Matrox this morning and according to them
>>their latest beta drivers (5.11) for a G400 Dual Head should be
solid
>>on Win2k

Alright!
good bye two video cards, good bye wasted IRQ
good bye wasted PCI slot

karlc wrote on 8/8/2000, 2:21 PM

Aaron,

Whoa ... don't get too excited ... the drivers are still *beta* and I
just wanted to use the 32 MB DH card from our old 98 workstation with
*one* monitor on the new W2K workstation ... I am not even sure that
two monitors are supported under Win2K the same way they were under
Win98?

To find out for sure, Matrox has a new support forum and the software
is fast, as is their response ... you have to register to post, but
there is some good information on there.

Might want to check it out before you throw away your two video
cards. :)

KAC ...

Aaron Carey wrote:
>>
>>
>>Karl Caillouet wrote:
>>>>On that note, I talked to Matrox this morning and according to
them
>>>>their latest beta drivers (5.11) for a G400 Dual Head should be
>>solid
>>>>on Win2k
>>
>>
>>Alright!
>>good bye two video cards, good bye wasted IRQ
>>good bye wasted PCI slot

darr wrote on 8/13/2000, 3:00 PM

What kind of video card do you have?

Carl German wrote:
>>VEGAS caused an invalid page fault in
>>module VEGASK.DLL at 015f:00633e9c.
>>Registers:
>>EAX=056cfdea CS=015f EIP=00633e9c EFLGS=00010212
>>EBX=056afd6c SS=0167 ESP=0293fe48 EBP=00c1e690
>>ECX=02257fdc DS=0167 ESI=00c1e690 FS=35df
>>EDX=00010040 ES=0167 EDI=00008020 GS=2d56
>>Bytes at CS:EIP:
>>0f bf 30 89 74 24 10 83 e8 02 db 44 24 10 83 e9
>>Stack dump:
>>00c1e690 00635122 02217ee0 056afd6c 00010040 3f800000
>>ff5d40a5 022c2194 004d9922 009104ae 02217ee0 00c1e690
>>056afd6c 00008020 3f800000 024cf0dc
>>
>>This is what comes up every time I hit play.
>>I have the update... I've tried uninstalling and re
>>installing several times... I've ask tech support and none
>>of the solutions work. Has anyone else had this problem?
>>Please help!
>> Carl
>>

cgerman wrote on 8/13/2000, 8:57 PM

David W. Ruby wrote:
>>What kind of video card do you have?
>>
I have a Pionex Computer, I'm not really sure! Why... does it matter?
I am sure it's not a very good one. I mean, it's not a hotrod deluxe
card. Should I check my hardware settings?

darr wrote on 8/13/2000, 10:47 PM

I just remember having probs as such with a videocard and a prob with
homeclick software for networking.
Is this the most current software for vegas?
I had to reinstall everything over to get the prob out.Are you using
win 98 second edition?
If anything get a matrox video card.They have it where you can turn
off pci bus retries which can kill a good take!
Never heard of the computer.
You might try to reinstall the vidcard.make sure latest drivers.
Other than that call in the morn and talk to kelly in tech support.
Sorry i was no direct answer.It will get worked out!!Hang in there!:-)
Carl German wrote:
>>
>>
>>David W. Ruby wrote:
>>>>What kind of video card do you have?
>>>>
>>I have a Pionex Computer, I'm not really sure! Why... does it
matter?
>>I am sure it's not a very good one. I mean, it's not a hotrod
deluxe
>>card. Should I check my hardware settings?

Ron Lucas wrote on 8/14/2000, 7:46 AM

I haven't seen this before, but I'm one of those guys who likes to
make sure everything is up to date. Do you have Microsoft's latest
DirectX7a installed. It's been out for a while, but you never know.
It could address some sound or video driver issues.

Ron

Carl German wrote:
>>VEGAS caused an invalid page fault in
>>module VEGASK.DLL at 015f:00633e9c.
>>Registers:
>>EAX=056cfdea CS=015f EIP=00633e9c EFLGS=00010212
>>EBX=056afd6c SS=0167 ESP=0293fe48 EBP=00c1e690
>>ECX=02257fdc DS=0167 ESI=00c1e690 FS=35df
>>EDX=00010040 ES=0167 EDI=00008020 GS=2d56
>>Bytes at CS:EIP:
>>0f bf 30 89 74 24 10 83 e8 02 db 44 24 10 83 e9
>>Stack dump:
>>00c1e690 00635122 02217ee0 056afd6c 00010040 3f800000
>>ff5d40a5 022c2194 004d9922 009104ae 02217ee0 00c1e690
>>056afd6c 00008020 3f800000 024cf0dc
>>
>>This is what comes up every time I hit play.
>>I have the update... I've tried uninstalling and re
>>installing several times... I've ask tech support and none
>>of the solutions work. Has anyone else had this problem?
>>Please help!
>> Carl
>>

JimT wrote on 8/14/2000, 10:15 AM

Carl German wrote:
>>VEGAS caused an invalid page fault in
>>module VEGASK.DLL at 015f:00633e9c.
>>Registers:
>>EAX=056cfdea CS=015f EIP=00633e9c EFLGS=00010212
>>EBX=056afd6c SS=0167 ESP=0293fe48 EBP=00c1e690
>>ECX=02257fdc DS=0167 ESI=00c1e690 FS=35df
>>EDX=00010040 ES=0167 EDI=00008020 GS=2d56
>>Bytes at CS:EIP:
>>0f bf 30 89 74 24 10 83 e8 02 db 44 24 10 83 e9
>>Stack dump:
>>00c1e690 00635122 02217ee0 056afd6c 00010040 3f800000
>>ff5d40a5 022c2194 004d9922 009104ae 02217ee0 00c1e690
>>056afd6c 00008020 3f800000 024cf0dc
>>
>>This is what comes up every time I hit play.
>>I have the update... I've tried uninstalling and re
>>installing several times... I've ask tech support and none
>>of the solutions work. Has anyone else had this problem?
>>Please help!
>> Carl
>>

I'm experiencing similar problems...only I can't even load projects
in without getting an error. The odd part about it is that other
audio programs behave just fine. I'm 90% sure it's a video card
issue. Here's the error I get:

VEGAS caused a general protection fault
in module VGA.DRV at 0002:00001423.
Registers:
EAX=00000000 CS=0347 EIP=00001423 EFLGS=00000246
EBX=00000000 SS=40bf ESP=00007bd0 EBP=00007c96
ECX=00960000 DS=0000 ESI=00000002 FS=3c87
EDX=0001ffff ES=0397 EDI=00000000 GS=0000
Bytes at CS:EIP:
66 8b 9f 96 00 66 89 5e 88 66 33 c0 57 26 8b 0e
Stack dump:
00001256 00000000 00000010 00000000 00950000 1a9affff 01070000
000009c4 09ba0702 07080000 00001a9a 093f0007 00007c96 00007cc4
00007cfa 0002504d

cgerman wrote on 8/15/2000, 12:30 AM

Ron Lucas wrote:
>>I haven't seen this before, but I'm one of those guys who likes to
>>make sure everything is up to date. Do you have Microsoft's latest
>>DirectX7a installed. It's been out for a while, but you never
know.
>>It could address some sound or video driver issues.
>>
>>Ron
Just installed 7.0a.... nothing has changed. Same error message.
I sure wish someone from SF would chime in on this one. I know that
they can't address every problem on every computer, but a little
nudge in the right direction would be greatly appreciated.

JohanAlthoff wrote on 8/15/2000, 8:13 AM

Here's my $2 on solving crashes.

First of all: Always call tech support. Even the weirdest bugs or
crashes might be known to the developers, and if they are, updates
are seldom far away. (Note that this forum is a user's forum, and is
not the optimal channel for tech support.)

When you get a PROGRAM crash in Windows, you should check the
following:

1: Conflicting software. mIRC can crash Logic, Photoshop lower
network performance, and Real Player may interfere with Desktop
Ghost. The reasons are seldom logical or derivative; Some coders or
library authors simply take shortcuts that are not "clean", and
hence, you get program conflicts. Solution? Kill everything else when
running audio apps. Especially shareware programs.

2: Plugins. I know for a fact that bad plugins can crash e.g. Vegas.
Try the same operation in Wavelab or Soundforge. If they also behave
strangely, you've got a bad plugin.

Now, if you get SYSTEM crashes, the reasons might be more severe. You
might want to check this:

1: Hardware drivers. Always, always, always make sure you're using
the latest (non-beta) drivers.

2: DirectX version. Very important. The later the better.

3: Peripherials. Scanners, webcams, secondary graphics cards. These
are all possible problem sources. Try disconnecting or uninstalling
them until only the essentials remain.

4: Broken hardware. Replace the soundcard or graphics card with
another and try again. If it works, your hardware might be faulty.

Good luck!

.
.johan althoff
.sound designer
.o3 games
www.outforce.com
.

Carl German wrote:
>>
>>
>>Ron Lucas wrote:
>>>>I haven't seen this before, but I'm one of those guys who likes
to
>>>>make sure everything is up to date. Do you have Microsoft's
latest
>>>>DirectX7a installed. It's been out for a while, but you never
>>know.
>>>>It could address some sound or video driver issues.
>>>>
>>>>Ron
>> Just installed 7.0a.... nothing has changed. Same error message.
>> I sure wish someone from SF would chime in on this one. I know
that
>>they can't address every problem on every computer, but a little
>>nudge in the right direction would be greatly appreciated.