Vegas and P4 ( again)

PipelineAudio wrote on 8/8/2002, 2:12 AM
Still having some MAJOR problems. Here's the setup

pretty much the rme reference CD:

P4 2.4 ghz
ASUS P4 T-E mobo
TEAC CD burner
Western Digital JB 8 meg buffer UDMA 5 7200 RPM HD
2 X Seagate Barracuda UDMA 5 7200 RPM HD's
2 X RME Hammerfall 9652
Matrox G550
512 megs RAM
1x network card ( tried a few versions)
3 X RME ADI DS's
Winxp Pro, installed many different ways, tweaks, no tweaks, etc...

problems:

1: Freezing: Hitting play in vegas will about 2 out of 5 times, freeze up for around 15 to 30 seconds, then start playing. Hitting control alt delete shows in the cpu meter, a 100 % spike during the frozen time. I cant get this error to duplicate in wavelab. Also this error ONLY seems to happen ( so far ) when using the play button after a stop. Clicking on the timeline to start playback forward or backward in time seems to never make this freeze happen.

2 : Cursor position is wrong. This isnt always true, but usually hitting play shows the play cursor in the wrong place. Also whenever you hit play, the play cursor goes forward for a BRIEF time, then goes backwards( left) then starts playing in the correct direction, sometimes accompanied by a temporary skip

3 : Peak building error/crash. Sometimes using " open copy in audio editor " when I click back on vegas, it freezes while rebuilding peaks. Hitting cancel does NOTHING, except that sopmetimes it says " a background operation is in progress would you like to stop it ? " and if I hit yes, still no go, it keeps trying to build peaks, at 0%

4 : Mouse Wheel zoom. sometimes, it stops working, and if you exit vegas it will work again.Sometimes it stops working and even if you exit vegas it doesnt ever work again ( on that song ).

these problems are starting to become showstoppers, and are VERY bad news when they happen in front of clients. I am emailing RME to see if they have any new answers as well.

SF have you tried vegas with 2 rme 9652's?

problems 3 and 4 also happened with an older dual p3 system

Comments

a_v wrote on 8/8/2002, 3:54 AM
right now, the conflict lies between 2 of the 3:
the OS, Vegas, and the RME Drivers...

i would be curious to know if the problems your having would still exist with WIN2K...instead of XP...
that would at least eliminate the OS possibility...
i know, i know, its a bitch to reinstall all this crap, but at least you would have a definite answer as to where the conflict lies...

another solution to finding the culprit:
do you have another soundcard lying around? if not, go pick up a cheap soundblaster and see if the probs are still there....

since wavelab seems happy, your hardware would be my last guest (either a bad mb, memory, processor and so on...)









SonyEPM wrote on 8/8/2002, 9:10 AM
Pipe, something is terribly wrong with your new system. You have a combination of severe problems that nobody else is having, (or if they are, they aren't telling SF).
Do you have a standby machine you can fire up, maybe load the rme stuff in that?
PipelineAudio wrote on 8/8/2002, 11:40 AM
problem 3 also happened with an older dual p3 700 mhz system. The soundcard back then was a Soundscape mixtreme.

So did problem number 4

can I send you a mix and see if theres some internal paramater that is killing the mouse?

Also have you tried vegas with any RME gear?
I am gonna pull out one of the cards and see what happens then
JoeD wrote on 8/8/2002, 12:53 PM
Sf rep is right...something is wrong.

I gotta tell ya, if you want to do things right...you should start over.
But when you do - start with only the HD's and video card.
Know which pci slots share IRQs - you want to avoid sharing as much as possible (there should be a default chart in your mobo manual). "Usually" the PCI slot 1 will be sharing with the AGP slot - check for this and avoid cards in slot 1 if so.

Disable both COMS (and LPT if you don't need a printer).
Set CDburner as slave on IDE ch 2 (and it gets the middle connector of ide cable), and the others up accordingly.

test thoroughly.

Then add soundcard

test

add NIC

test

this way you may find your culprit.
then start disabling unnecessary startup items (start - run - "msconfig"/startup tab)

test

THEN MAKE xp TWEAKS - test with each change.

Sometimes video card drivers and lans can be your problem source - keep in mind the newest sometimes isn't the best.


JoeD
PipelineAudio wrote on 8/8/2002, 1:39 PM
Thanks JoeD

The thing is, I have reinstalled over and over, first using RME's reccomendations, then Opus2000's of apogee, then using George of Xvision's reccomendations. The trouble is, none of these guys use vegas.

Problems three and four happened before on a totally different system

These problems occur with or without the LAN card

I have also tried, based on Nuendo user's advice, forcing the two RME cards onto one IRQ, and then on another's advice, using IRQ 3 and IRQ 5 for them

I am today going to try it with just one card.

Is there a way to tell if theres a memory stick bad? or a bad Mobo ?

My BIG question, is, has anyone used this app with 2 rme 9652's?

Today I will fdisk the whole sucker again, and like you say, start with just the video and HD, then the ONE sound card

SF, can you ask RME for some cards to test?
SonyEPM wrote on 8/8/2002, 2:01 PM
I know of at least 3 users of V3.0c+RME who are not having any of the problems you list, and I am almost certain it is not a direct conflict with Vegas and RME.

Ramallo, Scoria MM, Thomas31, MDgeorge64...all of these posters have the 9652, so I'm hoping they might chime in with some advice.
PipelineAudio wrote on 8/8/2002, 3:06 PM
I hope so!
Ramallo, you out there? Are you running one or two of these things?

Do you think it would be a good idea to set AD1 #1 as master and daisy chain the word clock out of it into the two other ADI's and then to the 2 9652's ?

Sonic EPM, what about the mouse wheel thing?

that MUST be a vegas thing as it does it on some files and not others right?
Can I send you a mix?
ScoriaMM wrote on 8/8/2002, 3:20 PM
>>I know of at least 3 users of V3.0c+RME who are not having any of the problems you list, and I am almost certain it is not a direct conflict with Vegas and RME.<<

I do run a RME 9652 setup, however only one of them. I can say that I have recently run all 24 channels into the card using 24bit, 44.1khz and had no problems with that, or the play back of those tracks. I was able to play those 24 and record another 8 over the course of the project and still had no problems.

I did notice Pipeline, that in the RME forum people had been complaining about the Matrox 550/450 cards in their machines. Im running a dual port Nvidia Geforce4 460MX with two monitors, and like I said, no problems. You may want to stick in a cheap Nvidia card and see what happens. (return it if it doesn't help you out?)

I highly doubt that its a RAM problem, as Windows tends to get corrupted very fast when this happens. If you would like to check it out anyways, e-mail me and I can give you a wonderful tool that will check your RAM bit for bit in 12 different tests.

I have never had a problem with the cursor moving around or pausing like you describe.

I *have* had weird issues with the zoom on a scroll mouse, but as you said, its very unpredictable (as in a per project basis).

-Matt
PipelineAudio wrote on 8/8/2002, 3:23 PM
Thanks a TON!

I got a geforce 2 in another PC and Ill try it out. Silly me went and bought all the stuff RME reccomends, like the g550
PipelineAudio wrote on 8/8/2002, 4:33 PM
OK pulled one 9652 out, and still freezing.

Anyone using these things, Ramallo or Scenaria, PLEASE let me know your setup, and setTINGS.... PLEASE!
PipelineAudio wrote on 8/8/2002, 5:03 PM
forgot to add

Sometimes when using waves fx ( c4) on the buss fx, the effect acts as though its bypassed, not doing anything, nothing showing on the meters. Restarting vegas makes it work again ( for a while)
ScoriaMM wrote on 8/8/2002, 6:36 PM
>>OK pulled one 9652 out, and still freezing.
Anyone using these things, Ramallo or Scenaria, PLEASE let me know your setup, and setTINGS.... PLEASE!<<

Ack.

I'm assuming you tried the Nvidia card as well?

Im not really doing anything different with my setup. I have a dual PIII 850 on a SuperMicro board with a gig of ram, and several Seagate 7200rpm drives. I have the dual port Nvidia card for video, the Hammerfall (on IRQ 3) and a 3Com NIC.

In the BIOS I have all COM ports shut off, the LPT port off, and USB disabled (I don't need any of those). Depending on that particular ASUS board, you'll probably want to disable any onboard audio, turn off the "Anti-Virus" checking thing, get rid of any Wake On Lan stuff, and look in the manual to see what PCI slots share IRQ's with what. I have another Asus system, and have setup several others, PCI slot 2 is usually by itself (second down from AGP).

Im also using WindowsXP Pro, with the Visual Theme's disabled, Remote Access disabled, Auto-Updating disabled, and the Hibernation mode disabled. All screen savers turned off, and under powersave settings, both monitor and hard disks are set to always on.

If you've got a VIA chipset, make sure you've got the latest updates there. Check your hard disk controllers in the device manager... right click on both Primary and Secondary controllers and go to Properties and the Advanced tab. Make sure its set to "DMA if available" and the current mode should be Ultra DMA Mode 5 or 4 depending on your disks.

I cant really think of anything else setup wise. If you do all these things and are still seeing odd things happening, you're looking at some sort of hardware problem most likely. Assuming you've tried a different video card, you're down to CPU, RAM, and Motherboard left to cause problems. Are you overclocking your CPU? I know JoeD has been able to do that very well, but for trouble shooting stop that to test. I would find a friend with a P4 system (you dont need another 2.4ghz) and swap the processor. Does is still cause problems? If so, swap out the RAM. Still problems? Then you've pretty much nailed it down to the Motherboard.

-Matt
PipelineAudio wrote on 8/8/2002, 6:51 PM
What do you have your sync ref set to ?

Did all the normal tweaks, havent tried the vid card yet ,but thats next
ScoriaMM wrote on 8/8/2002, 7:06 PM
>>What do you have your sync ref set to ?<<

Im using two Tango24 converter units right now, and a Focusrite Octopre. I have Tango24A setup as master. RME slaves off of that.

>>Did all the normal tweaks, havent tried the vid card yet ,but thats next<<

Deffinately try that.
JoeD wrote on 8/8/2002, 7:30 PM
just download DOCMEM to test ram....

but that isn't the problem.

I think it's"

- video card drivers
- cards not sharing well (try and not use sharing PCI slots for your soundcard and video)
- type of rme driver
- setup vegas to use the MME drivers for the RME cards as usual

JoeD
JoeD wrote on 8/8/2002, 7:37 PM
hold it.

Man, something is really wrong...so you're gonna have to describe in detail:

- steps to freezing (exact)
- tweaks you made (yep, all of 'em) in winxp (this could be the culprit right there).
** you want system restore on all drives disabled after successful operation
- HD/cd-r order (are you SURE the jumpers are set correctly?)
- all BIOS setup info (you might have some incorrect bios settings)
- Is this an overclock? Got the right cooling? setup correct for an OC? Tried it at regular cpu speed?

did you:
- disable both coms
- lpt
- Install latest via 4in1 right after successful xp installation (if using a via board)
- do you see any problem hardware in device manager?

Also, check the ram using DOCMEM (full tests)...could very well be the problem - although it's rare.

Lastly, if push comes to shove, may want to think about the abit BG7 as your mobo - it's a solid performer.

joeD
PipelineAudio wrote on 8/8/2002, 10:27 PM
ok I put in a geforce. same problem still

did all the tweaks at www.musicxp.net

also http://forum.nuendo.com/forum/Forum3/HTML/001099.html

http://forum.nuendo.com/forum/Forum3/HTML/001132.html

http://forum.nuendo.com/forum/Forum3/HTML/001074.html

and many more setups...
OS has been installed prolly 15 times now

also tried it bone stock
PipelineAudio wrote on 8/8/2002, 10:58 PM
tried the docmem test
everything is fine with the memory, according to this

I wonder though, even though it says its ok, could I have the "dummy" sticks in wrong ?
a_v wrote on 8/9/2002, 12:26 PM
pipe:

i think JoeD and Sonic are right...you are having some major hardware problem. Initially, that was my last guess, since Wavelab runs fine for you. But not all software uses the given system the same way so with that in mind, go get another MB...get a MB suggested by Sonic or RME or even perhaps the one posted above.

on a side note,
since point 3 and 4 seems universal for you, are you running dx~plugin packages? if so, which brands? For me, DSP and Waves plugs would cause some unexplainable cursor issues, like the cursor backing up to get to the point where it left off. It didnt cause any problems, just a sort of strange behavior.....for me, if some of those particular plugs are not running, everything is cool.
PipelineAudio wrote on 8/9/2002, 2:06 PM
I'd like to hear about the mouse wheel zooming thing as it MUST be a vegas problem. I can send a mix
PipelineAudio wrote on 8/9/2002, 3:39 PM
OK, I put in a SB clone and took out the RME's


works GREAT!!!! except the problems 3 and 4, which most likely have nothing to do with my system, but rather, vegas

I wonder if these cards are bad or just set up wrong somehow?

They have the w52 chip, thats the windows one right?
PipelineAudio wrote on 8/9/2002, 6:33 PM
Could anyone who has an rme 9652 running succesfully, in winxp pro, with vegas, specifically using the spdif I/O with no problems, please post their EXACT settings in the RME Digi Settings app?

Also their specific audio settings in vegas?

Even better if they are using a P4 and Asus p4t-e as rme reccomends?
a_v wrote on 8/11/2002, 12:13 AM
hey pipe..

glad to hear your narrowing it down. So it was the soundcard... i knew it had to be one of the three.

You said Wavelab had no probs with the 2 RMEs that you have. Did you spend a lot of time with Wavelab to make sure?

Do you know for SURE that RME has the tested the following:
XP, Vegas 3.0 (with latest update), and the RME drivers using all the functionality of the card?
Do you know of anybody with this setup for sure?

Also, have you tried anything else on that card besides SPDIF?

by the way, did you ever try win2k instead of XP? that would be the nail in the coffin. if win2k behaves the same way as XP, then there is a conflict between Vegas and the RME drivers. Period.

In regards to point 1, when i hit the space bar, i usually get a brief pause, but thats normal, as everything is caching....normal should be a half second to 3 seconds depending on how much stuff you have going on. Also, the cursor sometimes for me acts flaky like that but it doesent result in bad mixes, edits or system/software freezes. It always happens if i have lots of plugs going on. Ive noticed this behavior since vegas 1.0.
PipelineAudio wrote on 8/12/2002, 1:08 AM
"You said Wavelab had no probs with the 2 RMEs that you have. Did you spend a lot of time with Wavelab to make sure?
"

yup

"Do you know for SURE that RME has the tested the following:
XP, Vegas 3.0 (with latest update), and the RME drivers using all the functionality of the card?"

I highly doubt it , and I cant get SF to answer me whether SF has tried it, big surprise

"Do you know of anybody with this setup for sure?"

Everytime you post a setup a hundred guys pop up and say, " I have that exactly and it works fine, you must be a tard"
People in here claim to be using the rme stuff fine. Not as extensively as I do, but even when I set mine up like theirs, I have problems.

I have asked them to post their EXACT settings....we'll see

"Also, have you tried anything else on that card besides SPDIF?"
Yes, including 24 tracks in and out at 96khz 24 bit

these other i/o's make their own troubles which I wont get into right now, but thats for next time

"by the way, did you ever try win2k instead of XP? that would be the nail in the coffin. if win2k behaves the same way as XP, then there is a conflict between Vegas and the RME drivers. Period. "

Not yet...I should

"In regards to point 1, when i hit the space bar, i usually get a brief pause, but thats normal, as everything is caching....normal should be a half second to 3 seconds depending on how much stuff you have going on. Also, the cursor sometimes for me acts flaky like that but it doesent result in bad mixes, edits or system/software freezes. It always happens if i have lots of plugs going on. Ive noticed this behavior since vegas 1.0."

I gotta try a mix with no plugs and se what happens regarding the goofy cursor line. I have had weird problems on and off since Vegas' beta days, but this is new to me.
Before I used soundscape cards which were top notch. I now have to use RME's since the majority of hi res AD/DA converters now use the accursed " double wire/smux " crap