Recherche avancée

Sur d’autres sites (12105)

• Why does Apple support H.265 playback, but not when using HLS ? [closed]

  13 mars, par clark wu

  Apple devices (iPhone, iPad, macOS Safari) can natively play H.265 (HEVC) videos in .mp4 or .mov format. However, when I try to convert the same video to HLS, it fails to play. Here’s what I tested :

  


  Test Cases

  


  ✅ Directly playing H.265 .mp4 → Works fine

  


  ❌ H.265 + Opus → HLS (fMP4) → Fails

  


  ❌ H.265 + AAC → HLS (TS) → Fails

  


  ✅ H.264 + Opus → HLS fMP4 → Works fine (video + audio)

  


  ✅ H.264 + Opus → HLS TS → Video plays, but no audio

  


  ❌ H.265 + AAC → HLS fMP4 → Doesn’t play at all

  


  FFmpeg Commands Used

  


  1️⃣ H.265 + Opus (fMP4 segments)

  


  ffmpeg -i input.mp4 -c:v copy -c:a copy -hls_segment_type fmp4 -hls_time 10 -hls_list_size 0 -hls_flags independent_segments output.m3u8


  


  2️⃣ H.265 + AAC (TS segments)

  


  ffmpeg -i input.mp4 -c:v copy -c:a copy -hls_time 10 -hls_list_size 0 -hls_flags independent_segments output.m3u8


  


  Playback Attempts

  


  Vidstack.js player (Fails)

  


  Several online M3U8 players (All fail)

  


  Key Questions

  


  Why does Apple support H.265 in MP4 but not in HLS ?

  


  Is this an HLS specification limitation ?

  


  Does the audio codec (Opus / AAC) affect playback ?

  


  Does HLS require a specific HEVC profile/level ?

  


  Is HLS only compatible with AVC, not HEVC ?

  


  Looking for Answers

  


  Has anyone successfully played H.265 + HLS on Apple devices ?

  


  Are there any official Apple HLS specifications regarding HEVC support ?

  


  Possible workarounds or alternative solutions ?

  


  Would appreciate any insights or help from the community ! Thanks !

  


• sws_scale screws up last pixel row in smaller x264 mp4 encoding

  23 juillet 2012, par TheSHEEEP

  I am muxing pictures in the PIX_FMT_ARGB format into an mp4 video.

  All of it works well, except that the last pixel row of the outgoing image is screwed up, in most cases the last row is completely black, sometimes there are other colors, it seems somehow dependant on the machine it runs on.

  I am absolutely sure that the error must be in sws_scale, as I am saving the images before and after the scaling. The input images do not have the error, but after the sws_scale() I save the yuv image and the error is apparent.

  Here is an example :

  Original

  

  Yuvfile (after sws_scale)

  

  At the bottom of the Yuvfile, you will see the black row.

  This is how I do the scaling (it is after the official ffmpeg examples, more or less) :

  static int sws_flags = SWS_FAST_BILINEAR | SWS_ACCURATE_RND;
  
  
  
  if (img_convert_ctx == NULL)
  
  {
  
     img_convert_ctx = sws_getContext( srcWidth, srcHeight,
  
             PIX_FMT_ARGB,
  
             codecContext->width, codecContext->height,
  
             codecContext->pix_fmt,
  
             sws_flags, NULL, NULL, NULL );
  
     if (img_convert_ctx == NULL)
  
     {
  
        av_log(c, AV_LOG_ERROR, "%s","Cannot initialize the conversion context\n");
  
        exit(1);
  
     }
  
  }
  
  fill_image(tmp_picture, pic, pic_size, frame_count, ptr->srcWidth, ptr->srcHeight );
  
  
  
  sws_scale(img_convert_ctx, tmp_picture->data, tmp_picture->linesize,
  
          0, srcHeight, picture->data, picture->linesize);

  I also tried a number of different SWS_ flags, but all yield the same result.

  Could this be a bug in sws_scale or am I doing something wrong ? I am using the latest version of the ffmpeg libraries.

• Piwik 2 reaches end of life soon (December 2017), update now !

  7 décembre 2017, par Piwik Core Team — Community

  In less than three weeks, Piwik 2 will be no longer supported. This means that no further (security) updates will be released for this version. As per our Long Term Support announcement, Piwik 2.X is supported for 12 months after the initial release of Piwik 3.0.0 which was on December 18th 2016. Therefore, Piwik 2 will no longer receive any updates after December 18th 2017.

  It has been almost a year since we released Piwik 3 and we highly recommend updating to Piwik 3 ASAP. The major new release came with a new UI, performance and security improvements. If you are still on Piwik 2, the security improvements alone should be worth updating your Piwik to Piwik 3 now. We cannot recommend this enough.

  The update to Piwik 3 should be smooth, but may take a while depending on the amount of data you have.

  • If you have any problem with the update, feel free to get in touch with us, or ask in the forums.
  • If you are currently using Piwik self-hosted and would like to be upgraded, plus your Piwik managed in the official Cloud-hosted service, contact InnoCraft Cloud and they will migrate your database.

  At Piwik and InnoCraft, the company of the makers of Piwik, we have seen many thousands of Piwik installations upgraded over the past year and look forward to an exciting future for Piwik 3 and beyond !