Recherche avancée

Sur d’autres sites (4871)

• How to decrypt AES 128 encrypted HLS stream when URI for key is "k/timestamp"

  25 janvier 2021, par Wilfred Almeida

  I have downloaded 1784 .ts files and they are AES 128 encrypted.

  


  The .m3u8 file has #EXT-X-KEY:METHOD=AES-128,URI="k/timestamp",IV=0x496daa1c6914000e408c65cead91fc29 which I guess indicates that the key must be in a file named timestamp. I got the "timestamp" file and now I want to decrypt.

  


  I tried replacing the URI with URI="file:timestamp" with all the .ts, the .m3u8 and the timestamp file all in same directory and ran the ffmpeg command

  


  ffmpeg -allowed_extensions ALL -protocol_whitelist file,tcp,crypto,http,https  -i playlist.m3u8 -c copy op.mp4

  


  but got the errors Error when loading first segment 'hls_350k_000.ts'                                  playlist.m3u8: Invalid data found when processing input even though it opened the file successfully.

  


  I tried specifying the URI as URI="http://localhost/mydir/timestamp" but got the same error as specified above. I had all .ts,.m3u8,"timestamp" file in XAMPP's htdocs folder.

  


  When I open the "timestamp" file in browser's inspect->Network->Click on file->preview, I see weird text like kf¯2“.ú¸“Á•ª   Bn5ydr/x$.9+cgKC!<ßû¢ÌNñ®jûŸŸ and it changes everytime I refresh the site.

  


  I specified the link of the file in URI and tried, same error.

  


  I tried specifying .key extension to the "timestamp" file, same error.

  


  I downloaded the "timestamp" file by entering its URL into browser which I got from inspect->Network->Click on file->Headers, I didn't download it as HAR or other stuff.

  


  I tried playing the .m3u8 file in chrome using chrome by using Native HLS Playback extension with files hosted using XAMPP but it doesn't play, video player shows loading and the chrome's console has following errors

  


  (anonymous) @ player.js:57
player.js:11 trying to recover from media Error ...
handleMediaError @ player.js:11
hls.0.12.4.min.js:1 Uncaught (in promise) DOMException: The play() request was interrupted by a new load request.
player.js:57 Player error: mediaError - fragParsingError
(anonymous) @ player.js:57
player.js:17 trying to swap Audio Codec and recover from media Error ...
handleMediaError @ player.js:17
player.js:57 Player error: mediaError - fragParsingError
(anonymous) @ player.js:57
player.js:22 cannot recover, last media error recovery failed ...
handleMediaError @ player.js:22
DevTools failed to load SourceMap: Could not load content for chrome-extension://emnphkkblegpebimobpbekeedfgemhof/hlsjs/hls.min.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME


  


  I tried combining the .ts files using ffmpeg but got the same errors specified above.

  


  How do I decrypt the files and combine them into a single vlc playable file ?

  


• Getting this error using ffmpeg concat in ReactNative "concat imposible to open"

  2 février 2021, par Josip Bogdan

  Hy, I am trying to concat multyple video using ffmpeg concat, testing on samsung j76, android version 8.1.0

  


  const textFile = await (await writeTextFileWithAllVideoFiles(filePaths))  
const outputPath = Platform.OS === 'ios' ? `${RNFS.DocumentDirectoryPath}/video-1.mp4` : `${RNFS.DocumentDirectoryPath}/video-1.mp4`
console.log(`-f concat -safe 0 -i ${textFile} -c copy ${outputPath}`)
const result = await RNFFmpeg.execute(`-f concat -safe 0 -i ${textFile} -c copy ${outputPath}`)


  


  And here is how I create the txt file

  


  const writeTextFileWithAllVideoFiles = async (filePaths) => {
var RNFS = require('react-native-fs');
var path = RNFS.DocumentDirectoryPath + '/videoList.txt';

var fileContent = ''
console.log("fileplay1");
filePaths.forEach(path => {
   fileContent += 'file ' + '\'' + path.substring(8) + '\'' + '\r\n'
});
console.log(fileContent);
return RNFS.writeFile(path, fileContent, 'utf8')
.then((success) => {
   console.log(path)
   if (RNFS.exists(path))
      console.log('FILE WRITTEN!')
   return path
})
.catch((err) => {
    console.log(err.message)
    return err.message
});  
}


  


  This is my console log output

  


  file 'data/user/0/com.videoeditorapp/cache/Camera/f27579d2-1488-4a59-8a9d-7a4e7b6fe716.mp4'
file 'data/user/0/com.videoeditorapp/cache/Camera/58130175-bd20-4002-9629-070d0cdd18ac.mp4'

[Tue Feb 02 2021 16:30:45.375]  LOG      /data/user/0/com.videoeditorapp/files/videoList.txt
[Tue Feb 02 2021 16:30:45.376]  LOG      FILE WRITTEN!
[Tue Feb 02 2021 16:30:45.376]  LOG      -f concat -safe 0 -i /data/user/0/com.videoeditorapp/files/videoList.txt -c copy /data/user/0/com.videoeditorapp/files/video-1.mp4
[Tue Feb 02 2021 16:30:45.376]  LOG      [concat @ 0xe2b22000] Impossible to open '/data/user/0/com.videoeditorapp/files/data/user/0/com.videoeditorapp/cache/Camera/f27579d2-1488-4a59-8a9d-7a4e7b6fe716.mp4'
[Tue Feb 02 2021 16:30:45.377]  LOG      /data/user/0/com.videoeditorapp/files/videoList.txt: No such file or directory


  


  And the txt file is not on my android device
My manifest is like this

  


  &#xA;  &#xA;      &#xA;&#xA;<application></application>&#xA;

  


• Basic "pass-through" use of FFmpegReader/FFmpegWriter in scikit-video

  6 février 2021, par JonathanZ supports MonicaC

  I am starting to use scikit-video and am having trouble writing files. I have reduced the problem to the simplest possible example

  


  vid_file = "6710185719062326259_stamp_25pct.mp4"
output_file = "out_temp3.mp4"
reader = skvideo.io.FFmpegReader(vid_file)
writer = skvideo.io.FFmpegWriter(output_file)
for frame in reader.nextFrame():
        writer.writeFrame(frame)
writer.close()


  


  I'm playing the files in VLC, and the vid_file is valid but the output file, though playable, is mostly big green blocks (though I can discern some details from the original video in it).

  


  My goal, or course, is to do "interesting" manipulations of the frame before I write it out, but I need to get the "no modifications" version working correctly first. I'm also going to be using this on large files, so the vread/vwrite functions that process an entire file at once are not appropriate.

  


  I'm guessing I need to set the appropriate values in the outputdict parameter for the FFmpegWriter, but there are so many that I don't know where to start. I have tried

  


  writer = skvideo.io.FFmpegWriter(output_file, outputdict={'-crf': '0', '-pix_fmt': 'rgb24'})


  


  (-crf 0 to suppress any compression, -pixfmt rgb24 as that's what FFmpegReader says it delivers by default, but these don't work either.

  


  Any ideas on how to make this work ?

  


  Here's the skvideo.io.ffprobe video information for the input file.

  


  {
    "@index": "0",
    "@codec_name": "h264",
    "@codec_long_name": "H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10",
    "@profile": "High",
    "@codec_type": "video",
    "@codec_time_base": "1/30",
    "@codec_tag_string": "avc1",
    "@codec_tag": "0x31637661",
    "@width": "480",
    "@height": "270",
    "@coded_width": "480",
    "@coded_height": "272",
    "@has_b_frames": "2",
    "@pix_fmt": "yuv420p",
    "@level": "21",
    "@chroma_location": "left",
    "@refs": "1",
    "@is_avc": "true",
    "@nal_length_size": "4",
    "@r_frame_rate": "15/1",
    "@avg_frame_rate": "15/1",
    "@time_base": "1/15360",
    "@start_pts": "0",
    "@start_time": "0.000000",
    "@duration_ts": "122880",
    "@duration": "8.000000",
    "@bit_rate": "183806",
    "@bits_per_raw_sample": "8",
    "@nb_frames": "120",
    "disposition": {
        "@default": "1",
        "@dub": "0",
        "@original": "0",
        "@comment": "0",
        "@lyrics": "0",
        "@karaoke": "0",
        "@forced": "0",
        "@hearing_impaired": "0",
        "@visual_impaired": "0",
        "@clean_effects": "0",
        "@attached_pic": "0",
        "@timed_thumbnails": "0"
    },
    "tag": [
        {
            "@key": "language",
            "@value": "und"
        },
        {
            "@key": "handler_name",
            "@value": "VideoHandler"
        }
    ]
}


  


  I will mention that when I ffprobe the output file the only differences I see are 1) the timing data is different, which isn't surprising, and 2) the output file has

  


      "@has_b_frames": "0",
    "@pix_fmt": "yuv444p",


  


  I'm pretty confident the reader is working okay, because if I write out the data with

  


  skimage.io.imsave('x.png', frame,  check_contrast=False)


  


  it looks good.