Quantcast
Channel: FFmpeg: Ticket #1529: easier access to (ex: libx264) presets available
Browsing latest articles
Browse All 18 View Live

Article 5

Ok that makes sense (changing the error message to say "Possible internal tunes" might still be a small improvement. Patch looks great. Thanks for doing that! -roger-

View Article



Article 4

Replying to rogerdpack: Since there are some "file based" presets that aren't listed (​https://github.com/FFmpeg/FFmpeg/tree/master/presets ) the output text might be better served as "Possible tunes...

View Article

Article 3

Thanks this is great! A few minor additions that might be helpful: Since there are some "file based" presets that aren't listed (​https://github.com/FFmpeg/FFmpeg/tree/master/presets ) the output text...

View Article

status, component changed; resolution set

status changed from new to closedresolution set to fixedcomponent changed from undetermined to avcodec Afaict, this was fixed by Nicolas, please reopen if the solution is insufficient.

View Article

Article 1

In the laetst Git version, setting an invalid preset or tune will print the list:[libx264 @ 0x99fea0] Error setting preset/tune help/(null). [libx264 @ 0x99fea0] Possible presets: ultrafast superfast...

View Article


priority, version changed; keywords set

keywordsx264 addedpriority changed from normal to wishversion changed from unspecified to git-master

View Article
Browsing latest articles
Browse All 18 View Live




Latest Images