Posts: 2
Threads: 1
Joined: Jun 2020
Hey Gunther & community,
I use LRTimelapse for quiet a while, but somehow encoding H265 broke on my OSX some day between February and Mai. Till Feb I was happily converting to h265 to store my timelapses in highest quality for later use in projects.
I suddenly get very weird output when rendering h265 videos, even when using to the very same settings or trying completely random combinations. The output is always broken in the same way.
The new h265 videos are broken by:
* Show a proper thumbnail in finder/preview (https://imgur.com/a/XPRnHWW - The green bars move depending on the fps)
* Do not run in Quicktime
* VLC gets some frames, then stars lagging and showing a lot of visual fragments
* Final Cut Pro has the same issues as finder/quicktime
All of these are working fine in older h265 videos.
They work fine with:
* Adobe Premiere Pro 2020 can open it
* Youtube manages to eat the files: https://www.youtube.com/watch?v=JFQHy_28AEE && https://www.youtube.com/watch?v=rjrEKwua9fU
Here is a diff of the ffprobe outputs of a working and broken file. Both shot with the same Canon Alpha 6000, processed the same way I am used to.
https://www.diffchecker.com/UQf4OE8E
I tried multiple versions of ffmpeg, upgrading it via brew, using a custom compiles on and downloaded binaries from the website. Always the same issue with Apple Software & VLC.
Any advice on what I could try would be very helpful. Is there a way to get the ffmpeg command LRTimelapse will execute? So I could fiddle around with the config. I have working h265 conversion via ffmpeg running properly in my open source projects on the very same machine (Unrelated to timelapse ^^)
Till this is fixed, I am stuck with a huge amount of data from 2 trips as I can't process the timelapses and store them in an acceptable Quality/Size ratio. (Prores is simple to huge and mjpeg crashed final cut ¯\_(ツ)_/¯ )
Thanks a bunch,
Benedikt
I use LRTimelapse for quiet a while, but somehow encoding H265 broke on my OSX some day between February and Mai. Till Feb I was happily converting to h265 to store my timelapses in highest quality for later use in projects.
I suddenly get very weird output when rendering h265 videos, even when using to the very same settings or trying completely random combinations. The output is always broken in the same way.
The new h265 videos are broken by:
* Show a proper thumbnail in finder/preview (https://imgur.com/a/XPRnHWW - The green bars move depending on the fps)
* Do not run in Quicktime
* VLC gets some frames, then stars lagging and showing a lot of visual fragments
* Final Cut Pro has the same issues as finder/quicktime
All of these are working fine in older h265 videos.
They work fine with:
* Adobe Premiere Pro 2020 can open it
* Youtube manages to eat the files: https://www.youtube.com/watch?v=JFQHy_28AEE && https://www.youtube.com/watch?v=rjrEKwua9fU
Here is a diff of the ffprobe outputs of a working and broken file. Both shot with the same Canon Alpha 6000, processed the same way I am used to.
https://www.diffchecker.com/UQf4OE8E
I tried multiple versions of ffmpeg, upgrading it via brew, using a custom compiles on and downloaded binaries from the website. Always the same issue with Apple Software & VLC.
Any advice on what I could try would be very helpful. Is there a way to get the ffmpeg command LRTimelapse will execute? So I could fiddle around with the config. I have working h265 conversion via ffmpeg running properly in my open source projects on the very same machine (Unrelated to timelapse ^^)
Till this is fixed, I am stuck with a huge amount of data from 2 trips as I can't process the timelapses and store them in an acceptable Quality/Size ratio. (Prores is simple to huge and mjpeg crashed final cut ¯\_(ツ)_/¯ )
Thanks a bunch,
Benedikt