-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-working audio/video formats #84
Comments
There are several codec options still in there that don't work. Just discovered that the vorbis audio codec option doesn't work as well (needs to be "libvorbis"). vp7 (vp8 and 9 as well?) only works as decoder, not as encoder. @humdinger: can you maybe rename the issue to be more general, something like: audio and video codec options that don't work. Then we can collect the info about not working options here and discuss which ones to remove and add. |
All video encoders except vp7 seem to work and only the vorbis audio encoder doesn't. |
@humdingerb : I've worked on some code that fetches the valid options for container formats, video, and audio encoders directly from ffmpeg. Works great, the problem is the sheer number of options. If I remember correctly it returns about 60 container formats, 80 video formats and a few less audio formats. Far too many to conveniently access from a normal dropdown menu. |
Yeah. Here's the output of -codecs and -formats: I don't think we can handle that amount of codecs/formats with a GUI. I'd say we include the most common ones and let the niche users adjust the command line manually. Here is my suggestion which codecs/containers to include. Mind you, that's just from going through those lists and guessing which ones make sense (and at least need to support 'encoding'). It'll need testing if those actually work (possibly also by trying to play them back under Linux and Windows). Also, feel free to include ones I missed or remove any that are actually not popular...
|
So, I checked all our container/video/audio combinations. Maybe @andimachovec would like to look into that... :) General:
-> even adding '-strict -2' needs a bitrate >= 320 kbits
Video+Audio Containers:
Audio-only Conainer:
|
Sure, here we go ;-)
The "-strict -2" is no problem we could just add it to the format specifier in the video codecs vector. Not much we can do about the bitrate limitation at the moment. But I think isn´t really a very common codec so we can easily remove it from the menu if it is a problem.
Not sure about this. I noticed that Mediaplayer displays a still image when playing these files, but ffprobe only shows an audio stream, no video. Also if I play them on Linux (tested with Celluloid and VLC) there´s no video or image at all, only The incompatibility stuff between container formats and certain codecs is expected. Not every container works with every codec. I´m already working on a solution, each container format entry gets it´s list of supported codecs. I thought it would be OK to include this into the next release, but if you think it should go into the upcoming release I think I can get it ready within the week. |
I suppose it needs something similar to your planned audio/video/container capabilities. If the DTS codec is selected, the <320kbits menu items of the bitrate popup need to be disabled and - if a >=320kbits bitrate wasn't already set - set 320kbits.
Ha, now that you say that! I saved all those converted file in the same folder and the same name, just with a different extension. It appears, similarly to how additional subtitle .srt files work, MediaPlayer shows a similarly named video file, when asked to play back the audio-only file.
Yeah, that's fine. Let's save some features for the next release. :) |
Yep. We can introduce fields for minimum and maximum bitrate quite easily.
Let's keep it, and add the needed "-strict -2". So it can at least be used, as long as the user figures out the minimum bitrate.
Yeah, same here. Can you confirm that your files are audio only? (ffprobe output, playback on different video player / OS) |
They definitely are audio only. After moving them out of the folder with the similarly named video files, they are played back as audio-only. The much smaller file size is a dead give-away, too... :) |
OK, created #97 to add "-strict -2". |
From further up:
@andimachovec: what do you think use pcm_s16be instead? |
I have no idea to be honest :-) |
If you don't learn anything else, I'd say we go "big endian" as that's needed for the mpeg container. We should avoid adding too many niche options, as that would confuse the regular user. We cannot even provide a fraction of the available codecs in the GUI, and advanced users can always edit the provided commandline. |
No news here. There's quite a few of different PCM formats used in WAV files. I can't tell which one is peferrable over the other. |
There are several 16bit PCM options available. "Big endian" is expected by the MPG container, so it makes sense to use that version of PCM audio. See #84
Choosing "vp7" as video format fails the encoding. Should we remove it from the options?
The text was updated successfully, but these errors were encountered: