Yet again i'm unsatisfied with adobe product. If your software was free i could be even happy with this level of service. Since your products are one of the most expensive i expect them to be at least as good as free ones. How can You post link to free tool that does somenthing that part of software i bought for about $4000 SHOULD DO. This is shamefull.

Yet again i'm unsatisfied with adobe product. If your software was free i could be even happy with this level of service. Since your products are one of the most expensive i expect them to be at least as good as free ones. How can You post link to free tool that does somenthing that part of software i bought for about $4000 SHOULD DO. This is shamefull.

My car cost a lot of money but I can walk for free

I have both .web and .ogg working in Media Encoder. I simply followed Kevin's links and watched tutorials etc. I don't see the problem.

Adobe don't own those encoders and some of them can't be included in commercial products (due to licensing issues) so it's hard to blame Adobe for not including them. It's no different to them not including DNxHD and ProRes 'Built-In'. If you install the codecs you're likely to be able to use them in AME just like all the others.

I know AME can be enabled to export webm video, if you are using a Mac. In this case the quicktime filters provided by the webm project will do the job. I work with a PC, and I tried to achieve the same with the direct show filters from the webm project. But somehow this doesn't seem to work. I would appreciate help very much.

I remember that vp8/webm, ogg/vorbis, and ogg/threora are formats which are open source.

this may or may not be the issue. if there is an open source license attached to any/all of the formats, then you have to check the license first. then it's quite possible you will have to stick with miro for vp8/webm and ogg.

it is under the BSD 3-line license. the bsd license usually allows for commercial development, but you will have to look at the license to determine that, and I don't see it yet. in rthe colophon it said the theora bsd-like license doesn't restrict a 3rd party from implementing theora software (but it must support playback, even in the future according to wikipedia).

So let's keep our fingers crossed :-) In the meantime I tried a freeware encoder called XMedia Recode (http://www.xmedia-recode.de) which even does batch encoding. Still it would be very nice if there was an update for the Adobe Media Encoder incorporating webm!

Honestly the better option is for FireFox to support H.264 (and in the future, H.265) in the HTML tag. IE, Safari and Chrome already do. It's a shame the best browser doesn't support the best video codec. They've added it to the Android version, so there's no reason they can't add it for every version.

you have a point here. But the fact remains that under certain circumstances clients do require webm as an output format. I simply hope that adding the feature to the wish list and browsing the help forums will ultimately lead me to a solution.

that would make it a non-open-source browser if I understand right. h.264 is not licensed under an open source license. this is probably procisely the reason why open source browsers like webkit and firefox are using webm and theora, and non-open-source browsers want to use something where they don't have to be forced to reveal their source code, such as h.264 and other closed-license formats. I think you will see the dividing line now.

That is why Firefox doesn't include it by default in their primary browser. But it's just not a good enough reason, in my view. It's enabled on Firefox for Android. Like it or not, the licensed H.264 does provide the best quality/size ratio. Mozilla needs to get down off their high horse on this one and include support for all versions.

Or...come up with a better GPL'd codec (which is unlikely given the recent first round completion of the also licensed H.265 spec, which is sure to take over the near ubiquity of H.264 video on the web).

I would point out that ogg export exists in Audition CS6. If they can do it there, why can they not do it in AME? Most game engines use the ogg format and we need to able to convert many files in batch. I don't like the "free tools" because I find them untrustworthy (i.e. what else are they installing? I don't need ANOTHER toolbar on my browser.) My gripe right now is audio, not video. But I know I'll need web video support at some point.

WebM uses Vorbis for sound, but this plug-in can't actually write a seperate Ogg file. Now that I've gotten a little familiar with the Vorbis library, maybe it wouldn't be too tough to make a Premiere plug-in.

In fact, it was so quick I decided to add support for FLAC, as well, which is a lossless audio format by the same group. That might have been a mistake. It was much harder and in fact I never got it building properly on Windows. But for Mac users you've got FLAC support too.

Programmers, feel free to help solve the Windows issues, because this plug-in is open source. It's up here on GitHub.

linking problems are usually caused by not including the right libraries. in gcc, you look at the link error symbol names, and grep those in the lib directory. grep will list the library files that have symbols. GnuWin32: Files or MKS tools (for those who need a commercial package) can be had for those who need UNIX utilities like grep.

if there were other things that caused it, I forgot them because I haven't dealt with them in a while.

for example: for mingw-w64: assuming you are in the compiler's main directory,

Brendan, please put on hithub in a file (and reference here) or list here the errors you are getting. I will see what I can do. my compiler is mingw-w64 (not conducive to building *nixified sources), but the same general principle works with other compilers. the symbols exist as plaintext within the binary libraries.

also, the reason why audio might range that far (to -128, etc) is because it has a bias/offset - this is why audio is sometimes normalized and the dc offset (bias) removed (it's better to get the right levels in the first place, so there is no scaling involved!).

my understanding of flac is that it can use signed 8, 16, and 24-bit PCM. so see this, install a copy of sonar and then purchase and install the mp3 encoder. and then export audio.

The Ogg/FLAC plug-in is up there on GitHub. If you have Visual Studio, download the Adobe SDK and try to build. If you want use Ming, you'll have to set up your own build. The SDK examples all come with Visual Studio projects, so that's what I use.

Is there a way to export that with alpha/transparency? I've installed both the WebM and Theora (OGV) plugins from fnordware, and I've read that WebM supports transparency but none of my test renders have worked, and I'm not seeing any info on this. Any idea?