The metronome bug is the only one that annoys me so far.

ibid
B.

>>The metronome bug is the only one that annoys me so far. <<

Please elaborate. I don't recall the discussion about this.

Thanks,

drbam

I reported the bug to SF and they acknowledge it now. The next update may contain the fix.

The old thread: http://www.sonicfoundry.com/forums/ShowMessage.asp?ForumID=19&MessageID=206986

Doug

Same here with the metronome bug. I have to do the workaround every time I track new tracks to a project. Only takes a few seconds but its annoying.

I have two Delta cards running asio without a problem now. Had to get the right settings in the M-Audio control panel. Major one was to run cards as indepenent rather than multiple card sync. That seemed to do the trick for me.

I was using V3 to do a batch of vinyl to CD transfers and after doing a number of edits and wondering why the heck it wasn't working like I wanted, I realized I didn't have the ripple edit features in V4 that I am now used to. I went ahead and transferred it all over to V4. I pretty much have moved everything that I was working on in V3 to V4 without incident.

Other than that, on both audio and video sides I haven't had any bugs bite lately.

Might be time to move on over Joe and let us know how it works for you with the two Deltas.

I'll try the demo (**but most of the time, I need more than just a demo with something like this, V3 is my main tracker of choice).

But I WILL be using MME drivers (for a reason), and do need to use the metronome with some groups from time to time.
The workaround kinda blows - will this be getting fixed (sf?).

Are the delta MME drivers working EXACTLY as I use them in V4?
It MUST be this way before I move.
Is this the case? (SF?)

I'm not sure that I'll move to V4 now...although I want to and I have a period of time now (vacay) where it would be ideal to switch.

Who here is using V4 with maudio MME drivers? Please check in.

thanks,
JoeD

Again, why not just try the demo.

Installing V4 does not affect VV3 in any way. Just make sure you only open *copies* of VV3 VEGs.


geoff

I use V4 for at least 8 hours a day with maudio delta 1010, latest drivers in both WCD and ASIO modes. I have absolutely no problems that hinder my workflow. OCCASIONALLY, when switching recording ports in armed tracks in ASIO mode, VEGAS freezes on me, but that's ASIO. I've never had that happen in WCD mode. 4.0d is incredibly stable for me. I wouldn't dream of still using 3.0 becuase of all the new editing and audio features of 4.0

>>I wouldn't dream of still using 3.0 becuase of all the new editing and audio features of 4.0 <<

Are you experiencing the disappearing track issue (after recording) as described in another current thread?

Thanks,

drbam

well.... yes - sometimes - but what I discovered was that after hitting stop on the recording, if the event disappeard, I could still find it in the Media Pool. I would just drag it into the project from there.

Have you ever check to see if the recorded file was in the media pool after you "lost" it?

>>Have you ever check to see if the recorded file was in the media pool after you "lost" it? <<

No, because I have yet to install Vegas 4 due to the seemingly endless string of bug reports (I've owned it for several months). The "lost file" issue hasn't occured in Veg 3 (I haven't experienced it) and I'm simply not interested in hassling with these workarounds that obviously should not be necessary. By definition, the use of a "workaround" means something is broken. IMO, SOFO has had way more than sufficient time to fix Vegas 4. Its already futher down the road with updates than Vegas 3 even got and its still not where it should be. Having recorded files disappear is ludicrous at this stage of its development. I could understand this happening in the first version of Vegas - not now. I'm actually starting to feel like and agree with JoeD about this stuff! If I weren't so attached to the UI in Vegas, I'd probably be looking at other apps. ;-O

Frustrated,

drbam

Ok...

We are doing this, but just a reminder to keep on the subject of outstanding v4 issues.

so far we have:

- metronome bug (somewhat important to my use)

- MME driver usage in V4 - ??? (still need to hear more from MME v4 users and SF). Yes, I'll try the demo soon.

- occasional disappearing recorded files (or missing drawn waveforms actually)

Sorry, I'm just making the checklist so we can weigh the decisions better.
So far based on the above, I'm not moving to V4 just yet (dang, but maybe SF will do a patchup very soon to catch these outstanding issues).

JD

drbam,
>>Have you ever check to see if the recorded file was in the media pool >after you "lost" it? <<

>No, because I have yet to install Vegas 4 due to the seemingly endless >string of bug reports

Dr, you have bug reports numbers and severity a little out out scale with reality.

For me V4 has always been better than VV3, and certainly nothing that ever prevented a satisfactory final product (only bug that affected me was accasionaly clicks in live playback, not reflected in actual data) which is now wholly fixed.

If you waited until there were no bugs in all software before installing, your hard drive would have one hell of a lot of free space.

Do yourself a favour, install (yes, alongside VV3) and see if there actually are any bugs that affect you. There are maybe half a dozen people here re[orting problems, which implies many hundreds (thousands ?) who are not. As is the case with all (?) SF software, you can install different versions *without* any cross-effect.

geoff

seriously, if you've got it, use it. It can't hurt to have it alongside 3.0.

Christ...

reminder - please keep your personal feelings on others out of "this one thread" (AS WAS ASKED). The others are simply updating with info on what is wrong AS WAS ASKED - and I thank them for it.

I'm able to check out the other threads dealing with the current bugs just fine (eg - disappearing waveforms, etc)

Nothing against anybody in this thread.

I personally won't be using ASIO - ever - for v4. I want to hear from those using MME drivers now.

I listed the key outstanding problems as they were listed AND THEY WILL AFFECT ME.
No need to install V4 until they're fixed (and I do believe\hope SF will fix these).

No need for fu*ked up workarounds with a metronome when V3 has a working one.
No need to go any further until I get clarification that MME is working just as it does in V3 from current users using MME drivers.
No need to go any further ESPECIALLY if some report missing drawn waveforms.
The additions, however cool to you guys, do NOT outweigh the basic functionality needs for me.

Please remember that I just want to see one thread where we list the facts and that's it.
No stories on how you're doing, who you hate, who's recording studio you namedrop....just info on V4 on where it is now.

We were doing pretty well there for a bit.
Think we can do this?

thanks,
JD

Charles - you ARE using the MME drivers in V4 with your delta 1010 without a hiccup?

JD

Since problems people experience appear to be system dependent many times I would suggest the best way to find out if V4 is right for you is to install it, use if for a few hours, or a day, on a non-critical project and use this test to determine whether the application is appropriate for you.

JoeD
>I listed the key outstanding problems as they were listed AND THEY WILL >AFFECT ME.
>No need to install V4 until they're fixed (and I do believe\hope SF will fix >these).

The bugs reported do not affect everybody . The only way to find if they will affect you is to *suck it and see*. It should take less than 20 minutes, and will have no effect on your existing VV3 install, unless you open a VV3 file and resave it from V4.

geoff

Yeah, i'm trying it this monday (demo).

I wanted to hear from you users choosing MME in V4 beforehand. Hear from current users who responded with other issues they have.

JD

Joe -
Yes, I have no problems with WCD drivers in Vegas 4 with the 1010. The only reason I ever switch to ASIO is if I'm recording and I want to be able to keep tracks armed and do a lot of playback (not recording) to play stuff for a client. For some reason in WCD mode, whern you have tracks armed, playback can be a little hiccuppy (maybe Peter Haller can say why). So I just switch to ASIO at those times. It's possible I just have to tweak a buffer setting or something, but I'm too lazy to play around with those settings. I just want it to work. :)

But seriously, other than when tracks are armed during playback, I have NO problems with WCD drivers.

Charles...dude....

You realize what you've said? I'm hoping this was worded wrong.

It's a DAW.
You are supposed to be able to overdub (tracks armed for REC, over existing tracks).

Yes I hope Peter will elaborate on why things "get sluggish" with the MME drivcer use causing you to switch to the ASIO drivers.

I guess if I ONLY recorded jazz\blues (rarely a overdub needed) ....naw....
there's no reason why it shouldn't be functioning as well (if not better) than V3.

I'm staying with V3 and moving on to another app if nothing is done about this.

JD

ASIO and WCD both work fine for me.
Try the app, stick with V3 or move on. I think you've gotten all your going to get from the thread.