#6912 closed defect (invalid)
macOS - h264_videotoolbox encoder gives "No device available for encoder" warning
| Reported by: | alexpigment | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | undetermined |
| Version: | unspecified | Keywords: | |
| Cc: | ffmpeg@tmm1.net | Blocked By: | |
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
Summary of the bug:
When encoding with the h264_videotoolbox encoder on macOS, a warning is given that says "No device available for encoder (device type videotoolbox for codec h264_videotoolbox)". Since this message is confusing to users and potentially sounds like a software fallback is being used or something isn't configured correctly, it should be removed. Issue is similar to #6492.
How to reproduce:
% ffmpeg -f lavfi -i smptebars=size=1280x720:rate=30 -c:v h264_videotoolbox -color_range jpeg -pix_fmt nv12 -t 5 output.mp4
Confirmed on Macbook with Intel Core M CPU ; integrated GPU.
ffmpeg 3.4.1
built on 2017-12-11
Change History (6)
comment:1 by , 7 years ago
| Component: | ffmpeg → undetermined |
|---|---|
| Keywords: | macOS warning quick sync qsv removed |
follow-up: 5 comment:2 by , 7 years ago
I followed the pre-defined guide for logging this issue, and spent quite a bit of time narrowing down the issue for you. I'm not sure why you would take the time to respond to me that my ticket is not valid, when you could have spent less time simply copying and pasting the code under "How to reproduce" and verified that all relevant details have been included.
comment:3 by , 7 years ago
| Cc: | added |
|---|
I just tried ffmpeg master from the git repo and don't see this warning. So I believe this issue has already been fixed.
comment:4 by , 7 years ago
| Keywords: | videotoolbox removed |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
| Version: | 3.4 → unspecified |
comment:5 by , 7 years ago
Replying to alexpigment:
I followed the pre-defined guide for logging this issue
This does not sound correct to me.
and spent quite a bit of time narrowing down the issue for you.
Experience shows that this is not a good idea: Either you understand the issue, in this case send a patch fixing the bug to the FFmpeg development mailing list, do not open a ticket. Or you are unable to fix the issue, then please provide (only) the necessary information, don't try to narrow down the issue.
I'm not sure why you would take the time to respond to me that my ticket is not valid, when you could have spent less time simply copying and pasting the code under "How to reproduce" and verified that all relevant details have been included.
You forgot the tenth commandment...
comment:6 by , 7 years ago
I confirmed the issue no longer occurs after updating to the newest macOS and building with --HEAD via brew. I'm not sure which of these two factors was at play, but I'm guessing this was addressed very recently. Apologies for the unnecessary opening/closing of an issue.
Please test current FFmpeg git head and provide the command line you tested together with the complete, uncut console output to make this a valid ticket.