Comments

Geoff_Wood wrote on 6/11/2003, 2:19 AM
What problems are you having that makes it 'unusable' ?

I'm on 4.0b which I find eminently usable.


geoff
rgdbv wrote on 6/11/2003, 7:52 AM
well, the main problem is my inability to record in sync. Asio drivers apparently work fine, but i don't have the option of Asio, I can only use my Windows drivers, which unfortunately are not working with the program at the moment. You can see more about this issue at this thread: http://www.sonicfoundry.com/forums/ShowMessage.asp?MessageID=189652&Page=2 . And I have seen that others have complaints about other isuues too. This is my main problem though.
Former user wrote on 6/11/2003, 8:01 AM
rgdbv,

I noticed you are using a Soundblaster Live and then blaming this problem on Vegas? If you ever expect to record properly - lose this card ASAP. This so-called problem (as you put it) has nothing to do with Vegas. SB cards are crap and are simply not designed for any recording environment.

Also - I hope you are recording at 48Khz instead of 44.1 since Soundblaster products do not conform to the 44.1k standard. This could be party of your problem but honestly if you are not using a pro-level card with Vegas...you can't expect pro-level results.

I use an M-Audio Delta 66 (not exactly the highest end card) and I have no trouble recording with any drivers (Windows Classic, ASIO) on Vegas 4.0c. There is nothing wrong with the software that I can see. And I use Vegas heavily daily for all kinds of client jobs.

Cuzin B
rgdbv wrote on 6/11/2003, 6:18 PM
There is nothing wrong with the Soundblaster, as evidinced by the fact I had no problem in Vegas 3.0. I understand that it's not a pro level card, but i have had no such troubles of this kind up to now. And to back-up my statement, here is one of numerous comments on the same problem from someone with a higher-end card:

"you guys are not alone. mine does the same thing. just upgraded to V4, recorded 8 tracks of drums. not only were all of the tracks offset but some where offset more than the others. good times aligning with the click track. i use a Delta 1010 and Layla 24 so when i switch to ASIO drivers i get to go down to 8 tracks. worked great in Vegas 3 though..."

Blaming it on the Soundblaster! Really, I'm almost offended :-)
craftech wrote on 6/11/2003, 6:49 PM
Hi,

I do mostly video, and I have VV2, VV3, and VV4. If I decide to do audio only work, which one do you recommend I use and why?

John
Cold wrote on 6/11/2003, 8:17 PM
VV3 for now, but VV4 probably in an update or two. Unless you don't mind working around a few bugs, VV3 seems more stable,but VV4 has better features.
Steve S.
Former user wrote on 6/11/2003, 10:38 PM
rgdbv,

If you are offended...you can always move back to Vegas 3.0 and stay with it. It will continue to work just as before with no penalty.

Also - just because an upgrade is available - why do you assume it's going to automatically work for you? We would all like to think that 99.9% of the time this is true. Maybe this time for you it is not. And the cause probably has nothing to do with the software. Maybe your rig needs an update.

This sort of thing happens all the time in the software biz. Bigger more complex apps require more horsepower, more RAM, more throughput. Never more of a factor than with music apps. IF you rig is not "music only" (As in no Office, no extras, no games) Nothing but the music apps you need - you are guaranteed problems at some point...maybe not today but some point. These forums are full of horror stories that always blame the software first and the Soundblaster later.

With Vegas - 4.0 has been the best update yet and trust me - I am doing nothing special over here. I have good gear...good drivers and good know-how.

Finally - regarding your cut and paste quote - I can't tell if this guy is using the Delta OR the Layla OR both...but here's a little real world for ya - I work at 2 other facilities with the Delta 1010 (latest drivers) and they are having NO problems. Again - just because you got the gear doesn't mean you know how to get it working right.

So what's the deal here? Many of us are running fine AND we are running the same software as you. But you are insisting that it MUST be the software with the problem...right? Couldn't be your setup or anything....?

And as far as your Soundblaster - this is a kids card for kids activities. No one will take your issues seriously if you insist on defending a 40 dollar card. You are always going to get 40 dollar results.

Finally - check your original thread:

http://www.sonicfoundry.com/forums/ShowMessage.asp?MessageID=189652&Page=2

and note that Peter from SF has chimed in with this:

"ASIO is the best solution and the reason why we added it to Vegas. It is consistent.
There is NO work around. Don't use Direct Sound in Vegas for recording. It is the worst choice in Vegas."

I agree. So get a real sound card or move back to 3.0.

Cuzin B
cosmo wrote on 6/12/2003, 3:42 PM
Vegas 4.0b works pretty good for me. And, I went through the Sound Blaster cards too before landing on an M-Audio Delta 410. I couldn't get the Sound Blaster cards to work at all. In fact, the SB tech support guy told me himself that "SB cards don't play well with other devices". When someone from tech support tells me that, I stay away from their products.

Since putting in the Delta 410 my rig runs really smooth. Only problem I still have is that in complicated mixes with many events and tracks, I get clicks, stuttering after like 3-4 minutes of non-stop playback. Pause...play and it's gone. Strange. Haven't had that one asnwered yet.

I vote lose the SB card...you never know. Go pick up a Turtle Beach Santa Cruz card and CompUSA and see if it works for you. There's some people around here who love that card. I think under $100...and if you get it at CompUSA and it doesn't work, you have 14 days to get all of your money back, no harm done -)
momo wrote on 6/12/2003, 4:46 PM
Agreed with CuznB and others - ditch the Blaster - I'm a recovered SBLive user meself, so I know of what I speak. Trust me - even if that didn't fix some of your issues (although I think it will, esp. if you get an ASIO compatible card), recording at 16bit and 48KHz isn't doing your projects any favours either.

(you are recording at 48 KHz, right? 'Cause if you're not, on that card, you're just asking for trouble - I've not read your other posts, so forgive me if you've covered this already).

For me, going 24/96 was like finding a new and REALLY useful religion (bad metaphor, but I hope you catch my drift). Boosting the quality of the output inevitably improves the quality of the input, at least that was the case for me. As grampy always said, "you're only as good as your gear..."

momo



PipelineAudio wrote on 6/12/2003, 5:40 PM
just curious guys, which card do you think SF would use to insure the compatiability with the maximum number of systems out there?

and no I dont own a soundblaster
drbam wrote on 6/12/2003, 5:47 PM
>>just curious guys, which card do you think SF would use to insure the compatiability with the maximum number of systems out there?<<

Its my impression that Echo has been mentioned more than anything else. I could be wrong of course. . . ;-)

drbam
Former user wrote on 6/12/2003, 6:45 PM
I am sure SF is working fairly close with M-Audio as well...
drbam wrote on 6/12/2003, 8:17 PM
>>I am sure SF is working fairly close with M-Audio as well... <<

Unfortunately this is not the case at all! Apparently M-Audio doesn't give a sh*t about working with SOFO (and perhaps others as well). Take a look at Peter's post on the current Vegas-UAD thread. Knowing this, unless I absolutely cannot live without it, I'm definitely not purchasing any of M-Audio's stuff.

drbam
Former user wrote on 6/12/2003, 8:37 PM
drbam,

Well okay then. I stand corrected. Never have had a problem with my M-Audio stuff interfacing with any SF app. It works every time all the time Lucky me?

Cuzin B
rgdbv wrote on 6/12/2003, 9:04 PM
Thanks for your suggestions guys. Obviously I am aware that a Soundblaster is not the way to go, and I am working on getting a new card. But the point remains however, that the bug is in the app, not the card. If the card works with Vegas 3.0, and not Vegas 4.0, that is what you would naturally assume anyway, wouldn't you?
MyST wrote on 6/12/2003, 9:13 PM
You could also assume that the newer apps are going to be harder on our hardware. We want the extra features, but we still want to run them on our pentium 166.
I think gamers are more willing to accept that they're going to have to upgrade their PC if they want to play the newest games.
The newest upgrade for my CAD software now recommends a more powerful processor compared to the version we bought just months ago. Is that a "bug" in the software itself? I don't think so.

M
rgdbv wrote on 6/12/2003, 9:21 PM
I also don't know why everyone is assuming that it is my system, or my configuration, when there are plenty of other people complaining about the exact same problem, with all different systems, and configurations. Also, even if Sonic Foundry reccomend that you use ASIO, they have included support for Windows Drivers, so I expect them to work.
Former user wrote on 6/12/2003, 9:45 PM
rgdbv,

We are assuming it's your system because you said Soundblaster. You can color this anyway you want but getting that card out of the way is your first solid step at least troubleshooting this properly.

If this is such a major problem for so many (as you say) - why hasn't SF come to the table and simply said "Okay fair enough - bug detected...a fix is in the queue". I mean - the guys at SF take pretty good care of us, don't ya think? They read the forums...they know what's going on....they have definitely seen this thread and no one has jumped in. Hmmmm....wonder why....

If so many others are not having any problems at all (myself included) - is it really fair to blame the software?

Finally - the Windows drivers included with Vegas work fine for me. So do the ASIO.

Your fix for this will be something you have not revealed yet. How about offering up some other specs on your box (sorry if you listed this elsewhere)

Cuzin B
imac wrote on 6/12/2003, 10:47 PM
I have problems, I have a well spec'd PC, and two different and decent sound cards.
The system is not even romotely stressed to exhibit all the behaviour that wasn't evident in my previous version..

It is right to change the SB (borrow something else) to eliminate that as a cause, but isn't it obvious there is a Vegas problem here?
rgdbv wrote on 6/12/2003, 10:49 PM
Exactly. I wish you would stop assuming it is my PC, just because you are not having the same problem. Take a look at the "latency" thread, and you will see all the others with the same complaint.
Former user wrote on 6/12/2003, 10:53 PM
rgdbv,

Well - I wish you would stop assuming it's a "bug" just because you are having a problem. Take a look at about 1000 threads on this board from people who have no problems.
rgdbv wrote on 6/12/2003, 10:55 PM
I know the card needs to be changed, I am not trying to say that it is a pro card or something. But, if I was using the same card, and the same system in Vegas 3.0, and having no problem, and now I am using Vegas 4.0 with the same card and the same system, and having a major problem, logic tells us that the problem is in the program, and not the system or the card. But perhaps this is a form of logic you are unaquainted with.
rgdbv wrote on 6/12/2003, 10:59 PM
Besides, you seem to be missing the point. The problem is with the Windows drivers, and I assume you are using ASIO. That's why you are having no problem. The problem only occurs when you use Windows drivers.
imac wrote on 6/12/2003, 11:08 PM
but if everything is exactly the same - the only thing thats changed is the Vegas version...works fine with one version, not the other.....it does point to the Vegas s/w as the most likely culprit


that is the nature of bugs, that certain conditions, combinations, reveal problems that escape initial testing on the compatible systems

the '1000s' of happy users are the lucky ones