SF - What is going on with ASF support???!!!!!

PsycMan wrote on 2/15/2003, 6:56 PM
I have owned each version Vegas Video since it's introduction. I use VV to work on video art, but my primary use is for making my living - on A/V material that I deliver to a worldwide audience in the ASF format, for it's quality/compatibility. I was 'about' to upgrade to VV4+DVD and just realized that there is apparently way to render to an ASF file. With VV3 I was able to do this creating templates within VV2 (which I must say was a hassle but at least possible) but it seems like this is no longer possible...?? SF - Help me out here. Is this the case? If so, I'll be totally irritated - Why would you REMOVE a feature in an upgrade!???!!!
Should I be looking for other apps??
Remember - your best customers are already users... let's see this in an update real soon!

Comments

Cheesehole wrote on 2/16/2003, 7:46 AM
I feel your pain PsycMan. and I know a lot of people are in the same boat.

Microsoft may have created this situation, but we developers are always bending over backwards (or just bending over) to make sure Microsoft's laziness doesn't affect our customers. The point is, we are competing out here, and all we care about is giving our customers the best we can. The last thing we need is for our development tools to exacerbate this problem.

PsycMan, you make a good point... dropping the one feature that we really need is a slap in the face to those of us who came in early (way back with Vegas 2). We're the ones who spread the word in the face of all that snobbery from the Avid/Premiere crowd. And I personally have spent hundreds of hours on this forum over the past 3 years so you would think that Sonic Foundry would think really hard before removing delivery formats from their upgrades.

We probably won't get a response from SoFo until Monday morning. I'm still holding out hope that this was an oversight and something will be done to address the problem. One thing I can say about Sonic Foundry is they take great pains to keep their long time users happy.

If I may ask, what kind of work are you doing with ASF files? I'm creating training interfaces for CD-ROM and Web delivery, mostly CD. My philosophy is to make them as easy and convenient as possible for the end user. "Stick it in and play"

Nothing can touch ASF as a delivery format in that regard. Anyone with Win98, Win2k, WinMe, WinXP and above can "stick it in and play" without installing anything. that covers a lot of people!

- Ben
Cheesehole wrote on 2/19/2003, 7:50 AM
CLARIFICATION: ASF means Windows Media 6.4 codecs

Microsoft changed the extensions to WMV/WMA when they moved up to Windows Media 7.

I was really hoping to hear from someone at Sonic Foundry. would it help if I posted test files to prove that Vegas 2 is superior to Vegas 4 when it comes to rendering WMP 6.4 compatible files? I realize this may be confusing to some people and I will happily spend time proving my case. I've already spent a day testing Vegas 4's encoder trying to get a decent file out of it.

I just can't see the logic in compromising quality. You guys opened this can of worms by including a really good encoder with Vegas 2. now you exclude the feature that drew some of us to the product in the first place? where's the logic?!
watson wrote on 2/19/2003, 9:16 AM
What kind of training work are you doing. I'm using MMB and mpeg-1 I have it down to a science now and can get pretty good quality.
No complaints anyway.
I'm not arguing a case just curious.
Thank you.
W
Cheesehole wrote on 2/19/2003, 10:36 AM
>>>What kind of training work are you doing. I'm using MMB and mpeg-1 I have it down to a science now and can get pretty good quality.

thanks for replying. I do corporate training videos and deliver them in a javascript based interface with lots of navigation features, synchronized transcript, slides, table of contents... kind of like what Sonic Foundry offers in their Mediasite product but a lot more sophisticated and customized for each customer's needs.

I have tried the mpeg-1 route, but there are a few disadvantages I haven't been able to work around. if you have workarounds for these issues and you could post your techniques I'd like to try them.

with MPEG-1 video on a Windows Media 6.4 player I have audio sync problems especially after using the seek bar. lip sync is a major issue and it would really turn off our customers if we delivered a product that was prone to that. WM6.4 MPEG-4 V3 (the codec that came with VV2) doesn't have that issue at all.

with MPEG-1 I can't get up to the video quality level of MPEG-4 v3 at low bitrates. often we have to fit a lot of content on a CDROM And MPEG-1 doesn't cut it.

with MPEG-1 I can't do streaming over the web at low bitrates for dialup users. WM6.4 MPEG-4 v3 is a very capable streaming format.

so I have been down that road, but found WM6.4 to be more reliable, higher quality, and more capable (in a Windows environment) than MPEG-1. the technology of MPEG-4 v3 is just way ahead.

I appreciate the suggestion though. I very much want to find a solution in Vegas 4, but the best one would be to simply enable the old WM6.4 encoder that came with VV2.

I have discussed this issue on the Microsoft Windows Media news groups and no one has been able to provide a substitute for the old encoder. they tell you to go find the ancient Windows Media 4.1 encoder which is the last Microsoft encoder that can make correct WM6.4 files. so Microsoft has abandoned the 6.4 people, which include anyone on Win98 and Win2000 who haven't upgraded their player (there are plenty of reasons not to).

My question is, why is Sonic Foundry also abandoning this format? they have not provided an upgrade path for the people who came into VV2 for its capabilities to create this media. no one at the time would ever have suspected that subsequent versions of Vegas would not include this capability. is this a genuine case of misunderstanding? if so, would Sonic Foundry take the time to verify my case if I post some test files? all I want is to use the old 6.4 encoder in Vegas 4. thanks.
formations wrote on 2/19/2003, 3:12 PM
I don't understand why you would need to use ASF files.

Windows Media Player version 6.4 plays WMV files just fine, all the way up to version 8 of the Codec. It also has the on demand download of the codec, so users who have MP6.4 and don't have the 8 codecs will be asked if they want to install them (a 700k download).

So given this, you could use WMV files, or ASX files, and cover all your 6.4 user base...on 98, NT4.0 and Win2k.

Am I missing something?
Cheesehole wrote on 2/19/2003, 5:09 PM
I suspected that understanding was at the root of this problem. Thanks for asking... :)

>>>Windows Media Player version 6.4 plays WMV files just fine, all the way up to version 8 of the Codec.

When using codecs beyond the stock 6.4 ones, the following performance problems plague the 6.4 player:

1. slower startup time
- WM6.4 files begin immediately
- there is a delay when using WM7+ files

2. slower random access time
- WM6.4 files seek almost immediately
- a "buffer time" is introduced when using WM7+ codecs

no combination of WM7+ encoder settings will alleviate those two performance issues. considering the informational aspect of the content I am providing, and the many navigational features included in my interface, many users will want to jump around to zero-in on the content they want. a responsive interface is much nicer to deal with than one that is constantly hesitating.

>>>It also has the on demand download of the codec, so users who have MP6.4 and don't have the 8 codecs will be asked if they want to install them (a 700k download).

a very useful feature if you are on the internet. but not very helpful if you are on a laptop at a customer site. some of my target audience are field technicians who may not be online when they pop in one of my CD's. many people like to take the training while traveling (on a plane for example), and wouldn't be online either.

distributing the standalone codec package is an option, but that requires an additional installation by the end user, thereby breaking the "stick it in and play" rule. Microsoft also requires me to sign a license agreement to redistribute the codec pack.

this additional headache is not welcome by me or my customers, especially considering that the responsiveness they are used to will be compromised on top of the additional install (see above) unless the end user takes the further step of installing a more recent player (wmp9 for example). if you want a taste of some of the system problems you might encounter by upgrading the player, go check out microsoft.public.windowsmedia.player on usenet, not to mention that some people prefer the simplicity and non-commercial look and feel of the WM6.4 player.

>>>So given this, you could use WMV files, or ASX files, and cover all your 6.4 user base...on 98, NT4.0 and Win2k.
Am I missing something?

compromising performance and ease of use for my customers is not a smart business move.

I'm sure most of us are happy to upgrade our players, but we are also video developers. I personally love the quality, features and performance of the new codecs and players, and have used them in a couple of my products when called for, but not everyone is a pc video fanatic. the features of the new codecs and players simply don't really benefit my target audience. I respect my customers and will not force new software on them when it isn't necessary.

it may be difficult for most people to test my assertions given the scarcity of encoders for WM6.4 so I will post test files and hopefully someone with a WMP6.4 player can verify what I am saying.
watson wrote on 2/19/2003, 5:32 PM
I have never had a lip sync problem with Mpeg-1.
I create all the navigation with Multi Media builder scripts. Check out the Demo at www.mediachance.com

Streaming is another story.
I never have a video running over 5-7 minutes though. I break it all up in segments.

The MMB overhead is light.

It sounds like you have a system that works for you and I feel your pain, having to re-gear your methods.
Regards,
W
Cheesehole wrote on 2/19/2003, 6:29 PM
>>>I have never had a lip sync problem with Mpeg-1.

it doesn't happen on all system configurations. it depends on the sound card among other things. and it doesn't usually happen unless you seek deep into the file, so it would probably not be a problem on short media files, but my presentations are usually 45m to 2h in length. it's one of those things where I've seen it happen enough times to know it's not reliable. maybe I'm over cautious, but sometimes that pays. yes I could segment the file into tiny chunks, but that would cause a hiccup every once in a while during the presentation when the new segment is queued up, plus it's more work to prepare the media.

>>>I create all the navigation with Multi Media builder scripts. Check out the Demo at www.mediachance.com

cool I just checked it out. I use Autoplay Menu Studio for my front end loaders, but it is expensive! it's kind of a pain sometimes too.

>>>It sounds like you have a system that works for you and I feel your pain, having to re-gear your methods.

I was really hoping to take advantage of scripting in Vegas 4. (and all the other cool features) it looks like I'll have to have VV2, VV3, and VV4 installed on my box so I can cover my bases! if only that old WM6.4 encoder would work in Vegas 4 I could simplify things so much.

as for re-gearing, if there was another solution that was at least as good as my current one, I'd be there in a second. then again, in this industry the tried and true methods are the most valuable.

regards...