Recherche avancée

Sur d’autres sites (7271)

• hey i need to download my coaching classes but they are using hls aes 128 bit encrypted streams. i downloaded m3u8 and all .ts files and found enc key

  19 mars 2023, par tinu one

  I downloaded all the .ts files using a python script but it is encrypted with aes 128.i found a encryption key (supposedly) under the network tab in developer options. I ran it through ffmpeg but got an error( invalid data found while processing ). I need these classes because they are going to remove it in may 2023. i am a noob to this and may have done step wrong. Please forgive me. I would deeply appreciate anyone who will help me find a solution to this problem. Thankyou.

  


  I downloaded all the .ts files and m3u8 file and put it inside a folder. I hosted the key file in localhost that I found under the preview tab of the network tab in developer options( it was named key/ after all and had characters which was not human readable. it also had the request URL similar to that inside the m3u8 file)because ffmpeg did not want to read the key file from my local pc. I edited the m3u8 file to access the key stored in local host and it read successfully. but it shows error( invalid data found while processing).

  


  encryption key from preview tab I found : Ø®¢Ù¦Aä [u
request url of the key : https://classes.brilliantpala.org/api/v2.5/video_contents/42475/key/

  


  unedited m3u8 file :

  


  #EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:19
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-KEY:METHOD=AES-128,URI="https://classes.brilliantpala.org/api/v2.4/encryption_key/40cd559c70c241699cfcda9072c4fb42/",IV=0x00000000000000000000000000000000
#EXTINF:11.680000,
video_0.ts
#EXTINF:10.000000,
video_1.ts
#EXTINF:10.000000,
etc etc..


  


  fetch("https://classes.brilliantpala.org/api/v2.5/video_contents/42475/key/", {
  "headers": {
    "accept": "*/*",
    "accept-language": "en-US,en;q=0.9",
    "sec-ch-ua": "\"Microsoft Edge\";v=\"111\", \"Not(A:Brand\";v=\"8\", \"Chromium\";v=\"111\"",
    "sec-ch-ua-mobile": "?0",
    "sec-ch-ua-platform": "\"Windows\"",
    "sec-fetch-dest": "empty",
    "sec-fetch-mode": "cors",
    "sec-fetch-site": "same-origin",
    "x-key": "5e5d8c5d0486a678ccd4935ecb9fa8a01b1db7327396184ab00b50573119e947"
  },
  "referrer": "https://classes.brilliantpala.org/courses/535/contents/42475/",
  "referrerPolicy": "strict-origin-when-cross-origin",
  "body": null,
  "method": "GET",
  "mode": "cors",
  "credentials": "include"
});```




  


• FFMPEG Failure - Extracting frames on large file

  25 avril 2018, par Marian Montagnino

  Calling the ffmpeg command :

  ffmpeg -y -ss "00:00:02" -i 5ccaea226acfc1b4b75ccd1a9f09512c.mxf -frames 30 -f image2 -vf "fps=1/1.25,scale='min(420,iw)':-1" video%04d.jpg

  Causes a failure :

  ffmpeg failed: ffmpeg version N-85692-g78a5fc4 Copyright (c) 2000-2017 the FFmpeg developers
  
  built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-11)
  
  configuration: --prefix=/tmp/gm-ffmpeg-1.0.4/BUILD/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/tmp/gm-ffmpeg-1.0.4/BUILD/ffmpeg_build/include --extra-ldflags=-L/tmp/gm-ffmpeg-1.0.4/BUILD/ffmpeg_build/lib --bindir=/tmp/gm-ffmpeg-1.0.4/BUILDROOT/gm-ffmpeg-1.0.4-1.el7.centos.x86_64/opt/graymeta/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  
  libavutil 55. 61.100 / 55. 61.100
  
  libavcodec 57. 93.100 / 57. 93.100
  
  libavformat 57. 72.101 / 57. 72.101
  
  libavdevice 57. 7.100 / 57. 7.100
  
  libavfilter 6. 87.100 / 6. 87.100
  
  libswscale 4. 7.101 / 4. 7.101
  
  libswresample 2. 8.100 / 2. 8.100
  
  libpostproc 54. 6.100 / 54. 6.100
  
  [mxf @ 0x2c6da60] broken or empty index
  
  Input #0, mxf, from '/alloc/5ccaea226acfc1b4b75ccd1a9f09512c.mxf':
  
  Metadata:
  
  uid : 27b07007-2dc8-4305-a78a-81a612d78b94
  
  generation_uid : ef5ae870-4075-4513-ea1f-39c0ed197267
  
  company_name : Colorfront
  
  product_name : Transkoder
  
  product_uid : 3a4fe380-0d01-11e4-869f-3cd92b5c1dfc
  
  product_version : 2.7.3.20150121
  
  application_platform: Microsoft Windows 7 Professional Service Pack 1 (Build 7601)
  
  modification_date: 2016-09-09T11:29:39.000000Z
  
  material_package_umid: 0x060A2B340101010501010F20130000008991E1DCEA584837149E72E7F9F0E09D
  
  timecode : 00:00:17;12
  
  Duration: 00:11:58.92, start: 0.000000, bitrate: 150802 kb/s
  
  Stream #0:0: Video: jpeg2000, yuv422p10le(progressive), 3840x2160, SAR 1:1 DAR 16:9, 59.94 fps, 59.94 tbr, 59.94 tbn, 59.94 tbc
  
  Metadata:
  
  file_package_umid: 0x060A2B340101010501010F2013000000F8B3B48BE8044408DDD6303A6D43F566
  
  track_name : Picture
  
  Stream mapping:
  
  Stream #0:0 -> #0:0 (jpeg2000 (native) -> mjpeg (native))
  
  Press [q] to stop, [?] for help
  
  : signal: killed

  I’m not sure how to interpret this error message and why it actually failed. This file is about 90GB large and shot in 4K resolution but 11 seconds long.

• FFMPEG encoding 16bit video data results in 10bit

  12 mars 2023, par Jl arto

  I want to compress a depth map that has 16 bits of information per pixel. In general, such depth maps can be stored in different ways, e.g. p016le, gray16le, yuv420p16le, yuv444p16le, ... but for simplicity, let's assume the depth map is a yuv420p16le (where the y-channel contains the depth).

  


  For some reason when encoding with hevc_nvenc (I use an NVIDIA GTX 1660 Ti GPU), ffmpeg (the command line tool) changes the pixel format to a 10 or 12 bit variant (p010le, gray12le, yuv420p10le, yuv444p12le, ...), but I would like to keep the full 16 bits, since this affects the quality of the depth stored.

  


  For example :

  


  ffmpeg.exe -s:v 1920x1080 -r 30 -pix_fmt yuv420p16le -i depth_yuv420p16le.yuv -c:v hevc_nvenc -pix_fmt yuv444p16le output.mp4


  


  If I use ffprobe on the output.mp4, it tells me that the underlying pixel format is actually yuv444p10le. (Decoding and looking at the raw pixel data, I can confirm that the precision has decreased from 16 bits to 10 bits).

  


  I hope 16 bit compression is possible, since according to

  


  ffmpeg -h encoder=hevc_nvenc


  


  the supported pixel formats are :

  


  hevc_nvenc: yuv420p nv12 p010le yuv444p p016le yuv444p16le bgr0 rgb0 cuda d3d11


  


  But p016le results in a p010le output, and yuv444p16le in yuv444p10le.

  


  Does anyone know where the problem could lie ? Should I re-install ffmpeg (version 4.3.2-2021-02-27-essentials_build-www.gyan.dev) ? Is it because of Windows 10 having limited encoding/decoding capabilities ? Will buying the HEVC Video Extensions help solve this problem ?

  


  Additional info : using libx256 does not look like it will work for this purpose, since the supported pixel formats are :

  


  libx256 : yuv420p yuvj420p yuv422p yuvj422p yuv444p yuvj444p gbrp yuv420p10le yuv422p10le yuv444p10le gbrp10le yuv420p12le yuv422p12le yuv444p12le gbrp12le gray gray10le gray12le


  


  Any help would be greatly appreciated.