The following warnings occurred: | ||||||||||||||||||||||||||||||||||||||||||
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
|
[HELP] Changing Video Container takes up way too much disk space? - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [HELP] Changing Video Container takes up way too much disk space? (/thread-1030.html) |
Changing Video Container takes up way too much disk space? - BlockABoots - 07.06.2019 So i have an mkv file i want to convert to mp4, the file in question is 150GB big and i had over 250GB of free disc space on the designated harddrive, but i notice that the process crashed due to running out of disk space!. The log for the process looked like this Current defaultOutputPath: is empty! Its seems that Hybrid is creating the video 3 times over?, 6_44_00_8110_01, 6_44_00_8110_02 and 6_44_00_8110_03. is this normal behaviour?? RE: Changing Video Container takes up way too much disk space? - Selur - 07.06.2019 Yes, it's normal that using Hybrid you run out of space to do what you want. What Hybrid does when remuxing: a. extract all raw streams b. remux them to the target container So what happen is your extracted raw streams are probably ~149GB and during muxing a ~150GB file is created. So it would take at least 300 GB of free space to do the remuxing. If you want don't have the space and your streams are already mp4 compatible use for example ffmpeg with something like: "path to ffmpeg" -i "Path to your input file" -c copy -map 0:0 -map 0:2 "path to your output" -> Hybrid isn't the right to do what you want with your space restrictions. Cu Selur |