Posts: 17
Threads: 5
Joined: May 2017
There seems to be a bug in how the h265 exports are done with ffmpeg.
I was concerned why files exported from LRTimelapse didn't show up in quickview or quicktime. They are mov files so you would expect compatibility.
I then did some searching online and found this:
https://discussions.apple.com/thread/8091782
Basically, apple expects a different tag for HEVC than other people use. "Handbrake tags h.265 files as 'hev1', while High Sierra recognizes only 'hvc1'."
I used exiftool to inspect the file that had been output from LRTimelapse:
...
Compressor ID : hev1
Vendor ID : FFmpeg
...
I tried the suggested fix on the forum.
ffmpeg -i input.mov -vcodec copy -acodec copy -tag:v hvc1 output.mov
That allowed osx to see the movie file as I would have initially expected.
Please fix the output command to add this hvc1 tag so that the movies can be natively identified by osx/quicktime/whateverlib.
Other info:
OSX: 10.14.1
Model Name: MacBook Pro
Model Identifier: MacBookPro15,1
Processor Name: Intel Core i9
Processor Speed: 2.9 GHz
I was concerned why files exported from LRTimelapse didn't show up in quickview or quicktime. They are mov files so you would expect compatibility.
I then did some searching online and found this:
https://discussions.apple.com/thread/8091782
Basically, apple expects a different tag for HEVC than other people use. "Handbrake tags h.265 files as 'hev1', while High Sierra recognizes only 'hvc1'."
I used exiftool to inspect the file that had been output from LRTimelapse:
...
Compressor ID : hev1
Vendor ID : FFmpeg
...
I tried the suggested fix on the forum.
ffmpeg -i input.mov -vcodec copy -acodec copy -tag:v hvc1 output.mov
That allowed osx to see the movie file as I would have initially expected.
Please fix the output command to add this hvc1 tag so that the movies can be natively identified by osx/quicktime/whateverlib.
Other info:
OSX: 10.14.1
Model Name: MacBook Pro
Model Identifier: MacBookPro15,1
Processor Name: Intel Core i9
Processor Speed: 2.9 GHz