Ochi

@Bleuzen Could you provide details about each of the resulting files, for example using a tool like "mediainfo"? I wonder if there are unintended technical differences like e.g. chroma subsampling...

> The encoder implementations are different, but nothing should have been touched in relation to the bitrate regulation. That's likely just a pre-existing difference between the ffmpeg and texture encoders....

Hello, can you provide a (minimal) list of actions starting from a fresh scene list that lead to such a crash? That would probably help to pinpoint the cause. EDIT:...

Please see pull request #5. The issue is that the "`newSceneNames.size() == sceneNames.size()`" case in `handle_scene_list_changed` assumes that the scene list has actually changed. However, this is not necessarily the...

I'm also experiencing the "wrong bits/per/pixel" error with current versions of ffmpeg and vid.stab (ffmpeg 3.3.1, vid.stab 1.1). It seems to occur when using **YUV444** video in my case. In...

@kkartaltepe I tried building a Flatpak from master today with the "WA_PaintOnScreen" part removed as you suggested. At first sight, it works nicely for me under Wayland (KDE 6.2.1), including...

I was able to reproduce the write errors pretty easily on Arch Linux with kernels 6.6.56 (LTS) and 6.11.3 with zfs 2.3.0 rc1 (commit 3a9fca901b) even on a single, non-mirrored...

So, I tried to find a commit which worked at some point on the master branch, but I wasn't able to find a good commit so far. The 2.2 branch...

Thank you for your reply. I tested some combinations with zfs 2.3.0 rc1, and zfs_vdev_disk_classic does indeed make a difference in the amount of errors. Also, I was only able...

I re-tested with zfs 2.2.6 quickly just to make sure, and I'm not able to reproduce the issue there with 4K sectors (on a freshly created pool, as with all...