Opened 8 years ago
Closed 2 years ago
#7304 closed defect (invalid)
Quicktime Player cannot trim H265 movie
| Reported by: | GabrielZ | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | undetermined |
| Version: | unspecified | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
Summary of the bug: a movie that I converted using ffmpeg cannot be trimmed with Quicktime Player on Mac (macOS 10.13.5). It gives me the error message "operation cannot be completed". Playing the movie in QuickTime Player works fine.
How to reproduce:
% ffmpeg -loglevel error -hide_banner -nostats -nostdin -i input -map 0 -c:s copy -map_metadata 0 -map_metadata:s:v 0:s:v -dn -map_metadata:s:a 0:s:a -c:a aac -b:a 128k -codec:v hevc -tag:v hvc1 -preset faster -crf 25 -profile:v main -x265-params "me=umh:subme=5:ref=4:aq-mode=2:aq-strength=1.0:psy-rd=2.0:psy-rdoq=1.0:rd=6:log-level=1" -f mp4 output ffmpeg version: N-91200-g1616b1be5a-tessus built on macOS 10.13.5 , built with Apple LLVM version 9.1.0 (clang-902.0.39.1)
An example, where clipping using Quicktime Player fails, can be found here:
https://www.dropbox.com/s/jxg1n05smgxyvuq/Funny_Girl.mp4?dl=0
Just load the video in Quicktime Player, trim it anywhere, then try to save it.
If you check the system log file, you will find only one error message
"assertion failed: 17F77: libxpc.dylib + 75093" , but that seems unrelated to the problem here, because it occurs with other videos, too, where clipping works fine.
I have other videos that I converted exactly the same way where clipping with QuickTime Player works fine.
Change History (5)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Did you already report this issue to Apple?
Why are you reporting it here?
Please understand that all reports on this bug tracker using -loglevel error -hide_banner are invalid.
comment:3 by , 8 years ago
Yes, I did report a bug to Apple. But it is not clear to me, where the bug is.
I understand about the loglevel. If I can, I would like to amend my bug report with new case: i have converted a file again.Ihave put the original and the converted one on Dropbox.
here is the ffmpeg command line:
ffmpeg -nostats -nostdin -i A_Matter_h264.mp4 -map 0 -c:copy -map_metadata 0 -map_metadata:s:v 0:s:v -dn -map_metadata:s:a 0:s:a -c:a aac -b:a 128k -codec:v hevc -tag:v hvc1 -preset faster -crf 25 -profile:v main -x265-params "me=umh:subme=5:ref=4:aq-mode=2:aq-strength=1.0:psy-rd=2.0:psy-rdoq=1.0:rd=6:log-level=1" -t 10 -f mp4 A_Matter_hevc.mp4
Here is the output of the command :
ffmpeg version N-91200-g1616b1be5a-tessus Copyright (c) 2000-2018 the FFmpeg developers
built with Apple LLVM version 9.1.0 (clang-902.0.39.1)
configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3 --pkg-config-flags=--static --disable-ffplay
libavutil 56. 18.102 / 56. 18.102
libavcodec 58. 19.104 / 58. 19.104
libavformat 58. 17.100 / 58. 17.100
libavdevice 58. 4.100 / 58. 4.100
libavfilter 7. 24.100 / 7. 24.100
libswscale 5. 2.100 / 5. 2.100
libswresample 3. 2.100 / 3. 2.100
libpostproc 55. 2.100 / 55. 2.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'A_Matter_h264.mp4':
Metadata:
major_brand : mp42
minor_version : 512
compatible_brands: isomiso2avc1mp41
creation_time : 2018-06-22T19:10:54.000000Z
encoder : HandBrake 1.1.1 2018061800
Duration: 01:39:58.59, start: 0.000000, bitrate: 1420 kb/s
Chapter #0:0: start 0.000000, end 5997.400000
Metadata:
title : Chapter 1
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, smpte170m/bt470bg/bt709), 698x572 [SAR 16:15 DAR 2792:2145], 1244 kb/s, 25 fps, 25 tbr, 90k tbn, 180k tbc (default)
Metadata:
creation_time : 2018-06-22T19:10:54.000000Z
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 169 kb/s (default)
Metadata:
creation_time : 2018-06-22T19:10:54.000000Z
handler_name : Stereo
Stream #0:2(eng): Data: bin_data (text / 0x74786574)
Metadata:
creation_time : 2018-06-22T19:10:54.000000Z
handler_name : SubtitleHandler
Stream mapping:
Stream #0:0 -> #0:0 (h264 (native) -> hevc (libx265))
Stream #0:1 -> #0:1 (aac (native) -> aac (native))
x265 [warning]: Source height < 720p; disabling lookahead-slices
Output #0, mp4, to 'A_Matter_hevc.mp4':
Metadata:
major_brand : mp42
minor_version : 512
compatible_brands: isomiso2avc1mp41
creation_time : 2018-06-22T19:10:54.000000Z
encoder : Lavf58.17.100
Chapter #0:0: start 0.000000, end 10.000000
Metadata:
title : Chapter 1
Stream #0:0(und): Video: hevc (libx265) (hvc1 / 0x31637668), yuv420p, 698x572 [SAR 16:15 DAR 2792:2145], q=2-31, 25 fps, 12800 tbn, 25 tbc (default)
Metadata:
creation_time : 2018-06-22T19:10:54.000000Z
handler_name : VideoHandler
encoder : Lavc58.19.104 libx265
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default)
Metadata:
creation_time : 2018-06-22T19:10:54.000000Z
handler_name : Stereo
encoder : Lavc58.19.104 aac
frame= 250 fps= 36 q=-0.0 Lsize= 494kB time=00:00:10.00 bitrate= 404.3kbits/s speed=1.43x
video:324kB audio:158kB subtitle:0kB other streams:0kB global headers:2kB muxing overhead: 2.347609%
[aac @ 0x7fde51811a00] Qavg: 6034.060
The link to the input file: https://www.dropbox.com/s/qqka2o3q8fgcugh/A_Matter_h264.mp4?dl=0
The link to the output file: https://www.dropbox.com/s/i9vw9sajfbgoqnd/A_Matter_hevc.mp4?dl=0
comment:4 by , 8 years ago
Have you tried with different audio codec?
I'm experiencing issues with AAC
comment:5 by , 2 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Closing due to inactivity >6 years. Also, issue might be related to a different product and ffmpeg has much newer version now to try. Thank you.



PS: some videos exhibit the problem described above, some don't - I have not found a pattern yet. I converted all of them, IIRC, with exactly the same ffmpeg command line options.