Using the "Record offset" adjustment in the Audio prefs page does not permit you to ajust for the record offset?

Peter

why upgrade to V4? V3c is just fine (and the continuation of this kind of news - better yet, these responses from SF - is solidifying my disregard for V4).
Good luck Sony.

Why pay for a product that isn't working?
Wave classic works in V3 for me.

In addition, in my situation my softsynths use ASIO, and having two delta 1010's, I can use the MME in V3c AND record all my softsynths till the cows come home.

I'm having a tough time understanding why SF sets themselves up for failure and poor marks so easily. Things move at a turtles pace there - you're always two steps behind it seems. The answer should be "we'll fix this GLARING bug". Not, "oh, now use ASIO".

While you're at it, get a jump on things and make what SHOULD be - acid and Vegas SHOULD be one (others: spare me the "but I'm worried about bugs" bullshit...yeah yeah, and you might get cancer one day too. If V2 and V3 have shown anything...SF CAN do, but "WILL" they do is always the looming question).

JoeD

Using the "Record offset" adjustment in the Audio prefs page does not permit you to ajust for the record offset?

Not a solution in this case.

The recorded audio drifts out of sync by seemingly random amounts each time you start a new session using the Windows Classic Wave Driver.

Vegas 3 does not have this problem.

From what I can gather there are a couple of threads in this forum and one on the ACID forum about this exact same issue. But as yet no one from SF seems to have acknowledged that there is a problem.

It seems to be affecting anyone who does not (or can not) use ASIO drivers. That’s gotta be significant % of the SF user base.

JoeD;

The only reason I am keeping V4.0 is for the automation. Good for mixing. Like you I use ASIO with my soft synths and record them on VV3 with Classic Wave Drivers. However I need the automation of V4.

Maybe I should reinstall Nuendo!

Cheers

ouch

Yep. Ouch.

But I don't blame him. There's work to be done (in the fastest way possible)...then by all means install what's working and demand a refund.

Install Nuendo if it's proven working.

JoeD

I have had this track position problem also, and thought for sure it must have been something I was doing wrong. After all, it's one of the most basic things that shouldn't even remotely be a problem even in a Beta release!

I upgraded from v2 to v4 and have wasted so much time configuring and reconfiguring, crashing and restarting, and reading this forum desperately trying to convince myself that all these bugs are only a figment of my imagination. After all, not only did I pay for the software, but it is already up to release 4c! I trusted that it would be at least as solid as v2 for doing the same functions, but v4 so far has been a complete waste of my time and $. After buying Acid4 and dealing with all the crashing and bugs in that, now it's Vegas' turn.

And, before anyone tells me that this is "normal" for newly released software - BULL! I have been using computers for years and used many a buggy release, but at this stage of the game, there is no excuse for this low level of usability. BTW, I don't blame the developers. Typically in a corporate atmosphere, the marketing department demands features and creates timelines and release dates based on what they want to do, having no clue as to what is actually required to do it and how long it will take. And, they don't like missing their targets. There is tremendus pressure...

I will continue to use v2 until v4 is solid. I like the new features of v4, but I'm real sorry that I got wrapped up into paying to be a bug tester in my spare time!

I contacted Sofo support by email about this problem. Got a reply saying to do this, this, this, and this...... Like I haven't tried all these possibilities.

So I called by phone. Talked to someone who told me there is no problem, that it must be my setup (the one that is rock solid with all the other software I have including VV3, and that is configured strictly for audio).

So I gave up and decided to write Customer service VP. Will do on Monday. Last time I did I got a totally free upgrade!

I'll keep you posted.

yes I feel like a beta tester....if I was I couldn't complain..

I jumped from v2 to v4

and now my projects are in 4 there is no way to go back! I'm stuck!
Please fix for and release 4d quick!

SF was desperate for cash flow and V4 had to be released.......
If it was ready or not was an issue dominated by this factor

a few minor quibbles have to be expected, but major problems with no work arounds??!!

Because V4 was out there for a while as a free beta, I assumed things were sorted out.

My experience with other s/w is that a new version will work without major flaws, and at least will be in good shape by the first revision...

As yet, There is no word from sonic foundry as to whether this is an acknowledged bug or not, and when they are planning to fix it. Most frustrating.......

guys, what systems are you using (really detailed) to get these recording offset results?

I'm using an M-Audio Delta 1010, AMD Athlon XP 2400+ on an MSI N-Force2 motherboard with a Universal Audio UAD1.

Recording every day, and having no problems with drifting sync between tracks. The setup seems reasonably stable for me too aprt from the odd little thing.

It is odd that VV3 works for you and Vegas 4 doesn't but maybe if you all list your exact systems, we can find one common factor and Sonic Foundry can have a shot at fixing it.

I can understand why they wouldn't be able to fix it - as their systems probably work at least as well as mine.

Jason

We have acknowledged that users are having problems. We cannot repro these problems in house. As soon as we do, we will work on a fix.

We don't deny that users are having problems, we just can't fix something we can't reproduce.

Peter

Asus mobo
PIV 2.53
1G 2600DDR Ram
Waveterminal 192M with latest driver 4.0 (reserved and not sahred IRQ)
GeForce 2 MX/MMX 400 vido card
Maxtor 7200 ATA 133 system drive 30G
Maxtor 7200 ATA 133 audio dedicated drive
No messanger, no internet, no virus scanner
Nothing in msconfig (except msg32.exe - for GSIF driver for Gigstudio)
USB disabled in BIOS
Printer port disabled in BIOS

With the exeption of V4.o problem while recording with classic wave driver, the system is rock solid. No crashes, no freezes for weeks and weeks.

is NOONE running a machine with more than 10 channels? I would love to hear from others doing 24 or more at a time

Hi Peter,
I think you have a Card Deluxe in your testing configurations. I have noticed the latency "bug" or "issue" myself with Vegas 4.0 with this card, maybe it may help you get some traction on this issue. I used to use Windows Classic Wave driver exclusively in Vegas Video 3.0 and it worked great.
To test the latency, I recorded the output of Vegas (a single track) to a new track and measured the offset.
When I used the Windows Classic Wave drivers for the Card Deluxe I saw an large, unusable latency/delay between the source track and the recorded track. 10s of millisends. If I then switched to ASIO mode I was able to get very low latencies (or offsets between the source and recorded tracks) of about 3-4 msecs.
For the Windows Classic Wave drivers I systematically adjusted all of the Audio parameters that are made available to the user through Vegas and none of them compensated or fixed the problem. I'm now using ASIO exclusively and it's working fine. Don't know what happened between version 3 and 4 that would make Windows Classic mode unacceptable. Please let me know if I can help more.

bgc
(I'm the rimbaud234 in the beta group if you want to contact me directly for more feedback / help on trying to repro this.)

******To test the latency, I recorded the output of Vegas (a single track) to a new track and measured the offset.
When I used the Windows Classic Wave drivers for the Card Deluxe I saw an large, unusable latency/delay between the source track and the recorded track. 10s of millisends. If I then switched to ASIO mode I was able to get very low latencies (or offsets between the source and recorded tracks) of about 3-4 msecs.******

Again, someone's talking about monitoring latency.....

SARI's issue is NOT monitoring latency, it is a timeline track alignment issue that places the recorded track "out-of-time" with the rest of his timeline.

Sari,

Please define your system's IDE map (I.E. primary IDE master/slave & secondary IDE master/slave)

Also, if you have partitions define that.

Are you booting your OS from the primary drive and does the application live on that drive?

Are you writing and reading tracks from the same drive your OS lives on?

The reason I ask is because I found that with V4, I was unable to successfully (without glitches) record/playback tracks off of my SCSI drive when I was NOT booting to it.

I've noticed you call your second Maxtor an "Audio-Dedicated" drive...

I would suggest that anyone here who is experiencing problems with V4 try the following DAW techniques:

1. If booting to an IDE drive, make sure that it is the Master on your Primary IDE.
2. Install V4 (or whatever recording application you are using) on the same drive you boot to.
3. Make all of your media files (when working with them) live on the same drive you boot to and that your application runs from. In other words; make sure you're recording to your primary drive and that the recorded files which are being played back are on that drive as well. Also make sure you've installed V4 on the same drive.

This will (almost) eliminate the use of system resources for internal communications/bussing requests that could potentially interfere with the stable transfer of data. These interferances can also occur if it is the same drive as the OS, but a different partition.

Different sound cards can require different system resources/bussing requests and this may be why some of us are seeing different results than others.

Back to basics ... and ...You may already be doing this.... maybe not....

...But ....Maybe it will help.

:)

>>3. Make all of your media files (when working with them) live on the same drive you boot to and that your application runs from. In other words; make sure your recording to your primary drive and that the recorded files which are being played back are on that drive as well. Also make sure you've installed V4 on the same drive.>>

This is contrary to everything I've heard or read. I've been under the assumption that the data files should be on a secondary drive from the OS and apps. Please explain.

Thanks,

drbam

tmrpro - I am not talking about monitoring latency. I am talking about recording latency. I understand the difference.

OK Brett,

Explain to me so I can better understand your method of testing latency.

****** "To test the latency, I recorded the output of Vegas (a single track) to a new track and measured the offset." ******

Because as I understand what you have described as your method of testing latency, you are recording a latent reproduction (if the source is "input monitor" of the repro track) and you are recording the program's output of a single track.

That means that the track you are testing your latency on is a timeline recorded track of another track's latent monitoring.

Help me understand your method, because it doesn't add up for me.

Are you trying to tell me that there is input latency? Do we have to manually adjust our tracks based on V4's inability to offset and place the track to its correct timeline position?

This would be ridiculous.

Vegas and Acid together - dare to dream. I guess going back to Vegas 3 is the only solution and just check back every now and then for the miracle patch for Vegas 4.

Hey tmrpro;

Here is my drives steup.

Master on IDE 1 - Partitioned C:Boot and Windows only, D:Programs E:page file and temporary files
Slave on IDE 1 - DVD drive

Master on IDE 2 - Not partitioned F: only audio data
Slave on IDE 2 - CD Burner

Always worked fine for me on all my systems. But ready to learn and change if it makes my work better.

BTW when I started multitrack recording, long long time ago, multitrack meant 4 tracks!