Comments

Former user wrote on 6/13/2003, 6:55 AM
rgdbv,

I am clear on your point. Obviously something has changed in the Windows Classic drivers that is now giving you a hassle. If SF changed the way they work to accomplish something else in 4.0c, that's their right. However - just because they worked in 3.0 and now work for most of us in 4.0 and a small minority is having issues - does not mean it's a bug! Maybe it's progress...maybe your hardware has finally passed it's prime...maybe SF intended the Windows drivers to work the way they do.

Until someone like Peter or another SF employee close to this chimes in and gives you the real scoop (if there is one)...I really don't want to argue with you. Just trying to offer some perspective from a user who is working fine...and trying to show you how I got there.

Cheers,

Cuzin B

Former user wrote on 6/13/2003, 6:56 AM
imac,

What's your rig and what troubles are you having? Lay out some specs so we can check it out.

Cheers,

Cuzin B
criticaljames wrote on 6/13/2003, 4:47 PM
i use both, but you can only have ASIO drivers working for one or the other at once, not both at the same time, at least as far as i can tell.
rgdbv wrote on 6/13/2003, 5:52 PM
Well, we've now got word from peter that Sonic Foundry have recognized that users are having a problem, and they are trying, so far unsuccessfully, to reproduce the problem on their machines.
H2000 wrote on 6/13/2003, 6:25 PM
I agree with you that people shouldn't immediately assume something is a bug when they have a problem. I'm probably an example of the opposite. I thought for sure this problem must have been something that I screwed up - until I saw all the others with the same problem. This guy's setup worked fine before and now it doesn't. Sure, it could be his system or his soundcard. And yes, SF does have the right to change exclusively to ASIO recording if they wish. But, it's a nice way to mess with existing customers when, for all these years they have supported nothing but Windows drivers, and now suddenly "they're the worst possible" solution to record in Vegas.

I gotta tell you, I think you're off the mark with this one. Maybe you and all the other people who are not experiencing this problem are using mostly ASIO, and therefore do not have a problem. For one, the track offset is not consistent, and sometimes is correct. Maybe you did a small test using Classic Wave Drivers, decided there was no problem, then switched back to ASIO. Or, maybe it is a system related thing, and your system has no problems. But, I have a great system that I built myself and have been using for 1 1/2 years, including a Delta44 soundcard - pretty much the same as yours, and I have experienced this offset problem.

As far as using ASIO: generally, I have no problem with it. But, there are situations where I would like to use the Classic Wave drivers. For example, I like to load a soft synth into a standalone VSTi host with ASIO on two of my M-Audio outputs. Then I can use the Wave drivers in Vegas and record the VSTi directly from the Delta Mixer outputs. Yes, there is a very small latency offset this way, but it works great and I would like to continue doing it.

If it can't be fixed, so be it. I will just have to find another way to work, but I'm not happy about it.


Athlon 1700+
MSI K7T Turbo2
512M pc133 ram
(3) 7200rpm drives
Windows 2000 SP3
M-Audio Delta 44 - latest drivers
Former user wrote on 6/13/2003, 6:57 PM
H2000,

Good response. Well thought out and well written. I hope SF can comment one way or the other on this so we can get past it.

Cuzin B
JoeD wrote on 6/13/2003, 7:47 PM
<<If SF changed the way they work to accomplish something else in 4.0c, that's their right>>

CuzinB,

Listen to yourself. When you're through sucking the sf c**k let us know.
What are you? Completely delerious?

Same hardware, no problem with v3 mme
same hardware, problems with v4 mme

Wake up and stop with the road block defenses (defense for SF "rights" to screw with a once working scenario).
I know I won't be choosing to use ASIO for tracking in vegas - so if they want my business in buying V4, it's gonna have to be fixed.

rgdbv,
It is YOUR "right" to demand a f'ing refund. Ask them if you can take advantage of the price you paid for V4 WHEN THEY FIX IT.

This is V4"c" for christs sake. I'm all for going gung-ho, pro sf when everything is finally working. Until then, THEY ARE GOING TO HEAR IT FROM THOSE WHO ARE HAVING PROBLEMS (as is such with any software application).

Joed
Former user wrote on 6/14/2003, 8:12 AM
JoeD,

Ahh - summer and a rare classic appearance by that jewel of the SF forums.

Man...I had thought you finally got some benefit from your anger management lessons...I was actually reviewing a few of your recent posts and thought "Wow - he is really coming along"...and then...he loses it...he snaps!

Go to your "happy place", and make sure to take your copy of VV 3 with you. Take care.
The_Voice wrote on 6/15/2003, 2:52 AM
Due to problems with latency I have found a "fix" that works for me... that is when you first fire up VV4 go in and change the latency to a setting that is LOWER than what you actually are going to use....and drivers to what you wish...
then shut down VV4...
then fire up VV4 and reset the latency timing once again to what you actually want it to be ..
then, accept it and go on with what you are doing, the fix will work for THAT SESSION ONLY - I do not know why it won't save, but this works every time for me..

I use a Delta 1010 and the newest Beta drivers... I spent many a late night cussing both VV4 and M-Audio over this problem, when I realized that this worked it became a staple in my arsenal.

SF needs to address this issue... not the card as the card works well with other programs and is extremely well at holding latency in both ASIO and Win Drivers in 16/44.1, 16/48, 24/48, 24/96 and anything else you can throw at it.

Yes, folks I have even fixed the problem using an SB Live (16/44.1).

For the other latency thread I would hiope you can use and apply this, it just might work for you.

JoeD wrote on 6/15/2003, 4:26 PM
Ahhh, the trying to be clever and funny CuzinB who can't quite deal with the fact that brown nosing with SF (??..for some freaky reason) provides zero benefit.

Try this then: "shuddup, and stop arguing with him if YOU'RE not seeing problems. Let those who are post here with SF"

JD
imac wrote on 6/15/2003, 4:34 PM
I always use asio, with this problem I don't see the difference between asio and classic drivers, they both don't work, its just when using asio the latency is obviously so small you may not immediately notice it is delayed unless you are recording a timing critical source.
The random extra long delay is very obvious.
I send a one sample click out and record back in to test delays. In the past it proved the correction was working fine. Now it doesn't.
I use Soundscape mixtreme's and Dakota+montana. They both work fine with their buffers set to 64, but I feel more comfortable at 256.

Sure I'm using VIA (love it or hate it!) is this the common denominator?
I chose this (KT400) only after testing it carefully with V3 to be sure it was fine.
I recently changed the cpu from an XP2400 to a 2700, of course that did not effect anything...