FFMPEG is used for decoding compatibility. GPU decode acceleration is always the priority; however, some codecs are not completed on the GPU, so FFMPEG is used to allow decoding of some formats on the CPU. Encoding is always performed with ETI's GPU encoder technology.
I see you are using FFMPEG in badaboom. Why is it there?Submitted by Eli on Mon, 08/11/2008 - 11:24 |
avi
Is .avi support back in the latest beta?
Support for more input files!
Since you are already using ffmpeg why not use it to support a lot more input files?
At the moment it seems badaboom can only transcode very few input audio and video codecs.
Is there any reason why it can't use the full spectrum of supported files by ffmpeg
(which as we know supports almost anything you throw at it)?
Or how about using other open source software like mencoder and mplayer to get more support for all kinds of input files?
For example badaboom stops working when I try to let it transcode a x264/vorbis matroska file.
It is then closed by windows.
As a company selling their
As a company selling their product we have to be more conscious of using other companies patents/licences which reflect file formats.
Thanks
Aren't x264, vorbis and
Aren't x264, vorbis and matroska and many other codecs and containers open source?
Regardless of that, do you plan to support a wider range of input formats for the future?
Re: Aren't x264, vorbis and
The containers are open source but the codecs used inside the containers are often not open source. And yes, we will support a wider range of input formats in the future.
My take on this...
That's good to hear. As a user this is my take: I have the codecs on my system to support decoding of a variety of formats. Not being able to deal with (for example) HUFFYUV AVI is pretty much a deal breaker for me as it is the intermediate codec I use for a lot of my transcoding.
Perf of the app was good. I was impressed to see it consume 1080i from a TS file and deinterlace and scale to 720p h.264 /w CABAC at better than real time. The deinterlacing was pretty spotty though.
Having to disable SLI was annoying.
bottom line: It's not robust enough for me to feel motivated to purchase both in terms of containers and codecs supported and tweakability.