nice system...

Pipeline - heard of SX?

Pipeline, I come to this dance a little late, so forgive me if you've tried this or if it's too easy a suggestion. I figure, by now you're ready for any and all suggestions.
Did you try re-downloading VV3 and installing, or are you always re-installing the same download.
Sorry if this sounds lame...just trying to help.

M

george, I got a chance to run a MOTU 2408 (old one not MK2) on the older system from all the previous posts, and it didnt have this problem either. Same as soundblaster and soundscape mixtreme.

BUT

the RME has no trouble in any of the other apps

runs fine in sx

however, sx and other cubendos just arent capable of the speed of audio editing I need

feature wise cubendo completely KILLS vegas in every respect, but the amount of keystrokes and difficulty in moving and corssfading waveforms makes it impossible to use in my situation.

me and a friend are gonna count keystrokes and mouse clicks in a simple editing move in vegas and cubendo. I bet it will be an exponential difference

Myst, Im on the second PC system and about the 50th or so reinstall. But doesnt hurt to ask

using microsoft sound mapper, there are no freezes, however I give up 54 inputs and outputs doing this

so where is the fault now ?

Probably the RME audio driver then.

Works going through the mapper, but problems when choosing the MME drivers.

i know RME has a great name, but that driver is killing you I would bet.
More likely conflicting with another piece of hardware or it's driver.

Are you sure you tested WITHOUT making any DAW streamlining changes in XP (changing of services)?
What is disabled in bios (Com ports, usb, etc...). I still havn't seen an IRQ listing in device manager, list of all hardware and the slots they reside in (everything). You're at that point where you should be listing this stuff.

Nobody should be having this problem for this long.
This is ridiculous. I'm almost tempted to have you send me this box and I'll fix it for you and end all this if you want.
This one is a bitch to rule out without having someone taking a look at it.

How do you KNOW the RME driver isn't at fault? Cause they told you so? That's the extent of that?

How do you know V3 doesn't have any issues with the RME driver? Cause they told you so?

JoeD

See what I mean?

"Are you sure you tested WITHOUT making any DAW streamlining changes in XP (changing of services)?"

yup, many times this is probably nearly the 50th install

"What is disabled in bios (Com ports, usb, etc...). "

this is the second and totally different motherboard now
Ive tried every combo of bios on and offs you can think of(unless there are secret hidden ones, which may be )

"I still havn't seen an IRQ listing in device manager, list of all hardware and the slots they reside in (everything). You're at that point where you should be listing this stuff."

You havent seen any because I change them 5 or 6 times a week trying with acpi and without, forcing IRQ's and Not Forcing IRQ's, sharing and unsharing, steering and no steering

"How do you KNOW the RME driver isn't at fault? Cause they told you so? That's the extent of that?"

I dont know

"How do you know V3 doesn't have any issues with the RME driver? Cause they told you so?"

I dont know

here's the gist of it at this point:

1) SF says they have one working, using hardware that is not available to the public

2) It works fine on P3 machines. I have tried it on mine and charlesdem and others have it working on theirs

3) I am on a toally new mobo and CPU, the intel D850EMV2 mobo and a 533 2.53 P4. The ASUS P4T-E/ 400FSB 2.4 P4 did the EXACT same thing

4) Both combos work PERFECT with the following apps: Samplitude, Sonar, Cubase SX(both asio and MME), Nuendo 1.51 ( both ASIO and MME ), and wavelab

5) Using "microsoft sound mapper" as the device type in Vegas causes no problems, switching to " windows classic wave driver" causes the freezes

6) an SB clone and a soundscape mixtreme both work fine on the old combo, havent tried with this one yet

7) after hitting play a few times task manager will show " vegas30.exe" jumping up to 99 CPU and the PC will freeze up for 10 to 30 seconds

8) I have tried matrox g550 , matrox g400, Geforce 2, and Voodoo 5 video cards

<<after hitting play a few times task manager will show " vegas30.exe" jumping up to 99 CPU and the PC will freeze up for 10 to 30 seconds>>

I still say it's your RME driver (which in turn means the hardware too), but man, I gotta tell ya...I have many clients that have P4s and RME gear running fine.

**SF - WHY DON'T YOU DO A QUICK REPRO FOR THIS MAN USING A SIMILAR P4? You have the audio card now. You mean to tell me you guys can't find one P4 like his over there?
F-ing lazy.

- Tell me about the hard drives you have, CD's/cd-rs, and their connection in the chain.

- Well, get back to simplicity. Pull all cards except the video and RME.
In BIOS, do a "setup defaults". Then change the COM ports to disabled, LPT do disabled. Set PNP to no. Don't use ACPI

Note your IRQ's in dev mangler and list.

I seriously don't think you needed a whole new system.
something else is wrong

email me at joed@joedoriamusic.com btw

Joe, Im gonna reinstall the OS again the way you said. Should I disable the onboard sound on this new MOBO ?

should I instal the intel motherboard drivers?

Yes, of course disable onboard sounds - always, avoid the application accelerator...but do install the latest .inf patch for your mobo.

disable com ports, and LPT if you don't have a printer.

Only have the HD's/cdr, video card, and RME's at first install.
Hit "F5" when asked to install 3rd party drivers (begginning of install), then choose "standard PC" from the list when you see it.

How have you been installing it btw?

JoeD

Ive tried all different installs every which way but sunday


anyhow heres the update
this time Im adding and modding piece by piece

everything is going fine, network, video, turning off the animated puppydogs, etc...
until I made the quicklaunch toolbar visible...now SOMETIMES when I first open vegas, the first time I hit play it freezes as it used to, but then wont freeze after that

not sure what to do next

ok restored back to an earlier point...worked fine until I changed internal preferences to make linear fades...after that it would freeze 4 out of 10 upon hitting play at startup...changed it back to slow fade and no freezes so far
havent unlocked the taskbar or shown the quicklaunch tho

never mind it froze even with slow corssfades

jeez louise no hope

Just a thought - try removing all DX plugins, Wrappers, and any other audio software installed. Then run Vegas using only stock native Vegas plugins on the tracks.

Then add plugs / apps until it dies. The problem may be a bit of rogue code.

Also, when using XP, if you can try avoiding using the manufacturers drivers, and use microsoft's certified drivers instead.

Try using Windows without any updates at all, and add them gradually.

You must be tearing your hair out.

this latest install is fresh with niothing...just the soundcard drivers at first NO plugs