Record gif issue after 5.0.0- (filter-fifo?)

First noticed when updated to 5.0.1, but didn’t have time to investigate, so returned to 5.0.0 and issue was resolved. Updated today to 5.1.M1 and problem reappeared. In a nutshell I don’t get the .gif file from this DSL rule past 5.0.0.

rule Driveway_camera Zooz39 motion.txt (637 Bytes)

I ran the IP camera log in trace and I think the relevant section is this (filter not found?

IPcameratrace.txt (11.6 KB).

I’m back on 5.0.0. Did not put in the 5.1.M1 topic because it happened earlier. Working trace on 5.0.0

IPcameratrace2.txt (4.4 KB)

I had the same issue, couldn’t solve it. :innocent:

1 Like

Based on @sihui comment I added some information on the docker container

Working;

javaVersion: 21.0.8
javaVendor: Eclipse Adoptium
javaVendorVersion: Temurin-21.0.8+9
osName: Linux
osVersion: 6.1.0-rpi8-rpi-2712

Not working;

javaVersion: 21.0.8
javaVendor: Debian
osName: Linux
osVersion: 6.6.20+rpt-rpi-v8

On the base Rpi5, no java, but

Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-rpi8-rpi-2712

EDIT: Also all I have for options is

MJPEG Options -q:v 5 -r 2 -vf scale=640:-2 -update 1

Rather than revert back again to 5.0.0 after failing with different ffmpeg options, I decided to use an AI suggestion that is close to fifo, but doesn’t use it. The gifs seem comparable but are a little smaller byte-wise. I guess I’ll call this a solution since I’m tired of messing with it.

GIF Out Options

-r 2 -filter_complex scale=480:-2:flags=lanczos,setpts=0.5*PTS,split[o1][o2];[o1]palettegen=max_colors=128:stats_mode=diff[p];[o2][p]paletteuse=dither=bayer:bayer_scale=3

1 Like

@matt1, could you please make this a default for the “GIF Out Options” for the IPCamera binding?
This is still an issue on openHAB 5.1.0 Snapshot #4852
Thx :smiling_face_with_three_hearts:

I created a PR here:

https://github.com/openhab/openhab-addons/pull/19514

This is only the default value so you can change it easily enough, however I agree the default should change to help new users out so thanks for pointing it out. I have not done a deep dive on the changes between them but scale=480:-2 will give a different output and will be the reason for the difference in the bytes of the file.

1 Like