search

socallinuxexpo / scale-av-cutter

A webapp to streamline the cutting of full-day room streams into individual talks
Do What The F*ck You Want To Public License
4 stars 1 forks source link

strange message on thumbnail creation #59

Open ldang opened 4 months ago

ldang commented 4 months ago

split.py - weird message on thumbnail creation

[swscaler @ 0xef5809c0] deprecated pixel format used, make sure you did set range correctly
Output #0, image2, to 'workdir/Ballroom-C-Sunday/10-Years-Of-Open-Source-Funding-Trends-A-Deep-Dive.jpg':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf60.22.101
  Stream #0:0(und): Video: mjpeg, yuvj420p(pc, unknown/bt709/bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 30 fps, 30 tbn (default)
      Metadata:
        handler_name    : ISO Media file produced by Google Inc.
        vendor_id       : [0][0][0][0]
        encoder         : Lavc60.40.100 mjpeg
      Side data:
        cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
[image2 @ 0xe18d480] The specified filename 'workdir/Ballroom-C-Sunday/10-Years-Of-Open-Source-Funding-Trends-A-Deep-Dive.jpg' does not contain an image sequence pattern or a pattern is invalid.                                            
[image2 @ 0xe18d480] Use a pattern such as %03d for an image sequence or use the -update option (with -frames:v 1 if needed) to write a single image.

This would imply that we're not quite using the right command to generate a single image, even though it's doing it for us.

NOTE: I had to hack split.py to generate jpeg instead of png because of #58

ldang commented 3 months ago

Found the Stack Overflow for it https://superuser.com/questions/1792249/ffmpeg-suppress-warning-when-writing-to-a-single-image

And here is an example: ffmpeg -y -ss 44 -i Enterprise-Automation-with-AWX-upstream-for-Ansible-Automation-Platform-.mp4 -update true -frames:v 1 blah.jpg

destevae commented 2 months ago

Did some research on this message and people are saying that it's just a warning message instead of an error that we don't need to worry about. It happens when ffmpeg creates JPEG images, it chooses a different pixel format with a different pixel range which creates this message.

@ldang I can add a parameter to the ffmpeg create thumbnail function that suppresses warnings like these so we don't see it anymore. If not, we can also just leave it be. Let me know what you think.

Stack exchange link