No picture playing ProRes files

[dhl]

Hi,

I'm trying to play videos encoded with Apple ProRes 4444 and ProRes HQ and only get sound, no picture.

Everything works fine with HEVC and h.264, only ProRes is broken.

ProRes worked fine in VLC before. Any solutions?

Thanks for your help!

[Lotesdelere]

Please open Tools -> Messages (set Verbosity to 2) before you start the playback, and then paste the full resulting log here or on Pastebin.com if it's too long.

Also upload a short sample of your original problematic file to Zippyshare.com or to WeTransfer.com and then post the link to the file here.
https://www.zippyshare.com
https://wetransfer.com

If needed cut it with DGsplit and read here about how to do it:
https://forum.videolan.org/viewtopic.ph ... 35#p193335
200 MB max should be enough.

[InayathAtp8]

Dolby vision videos not playing... Other players working fine.. But vlc not playing properly everything green and pink colour

[dhl]

Please open Tools -> Messages (set Verbosity to 2) before you start the playback, and then paste the full resulting log here or on Pastebin.com if it's too long.

Also upload a short sample of your original problematic file to Zippyshare.com or to WeTransfer.com and then post the link to the file here.
https://www.zippyshare.com
https://wetransfer.com

If needed cut it with DGsplit and read here about how to do it:
https://forum.videolan.org/viewtopic.ph ... 35#p193335
200 MB max should be enough.

More info – The file that's failing is a ProRes master of an 83-minute feature film that's ~130Gb. I ran a test with a small 1.5Gb sample and it played fine so it looks like the problem is related to file size.

Here are my logs (btw, Pastebin.com thinks this has "offensive content" and will hide the post. I used justpaste.it instead.

https://justpaste.it/9ozsg

At line 269 there's an error:

main error: buffer deadlock prevented

I think that may be where the problem is occurring. Any thoughts?

Thanks for your help!

--David

[Lotesdelere]

As requested, we also need a sample file.

[dhl]

As requested, we also need a sample file.

Here's a sample file:

https://www60.zippyshare.com/v/POrkzJhW/file.html

This small file plays back fine. The file with the playback problem is much larger (475Gb). Both files were exported in the same way from the same timeline.

Let me know if you need anything else.

Thank you!

[umxprime]

As requested, we also need a sample file.

Here's a sample file:

https://www60.zippyshare.com/v/POrkzJhW/file.html

This small file plays back fine. The file with the playback problem is much larger (475Gb). Both files were exported in the same way from the same timeline.

Let me know if you need anything else.

Thank you!

We can't investigate an issue with a sample file where there's no problem.
Please share a problematic sample file.
Thanks

[InTheWings]

If you have a way to move headers at start of file (fast start)
and then truncate after a few megabytes, that would still be a valid sample

[InTheWings]

Otherwise you can also zerofill inside the mdat section after few MB and compress the whole easily

[dhl]

We can't investigate an issue with a sample file where there's no problem.
Please share a problematic sample file.
Thanks

If you have a way to move headers at start of file (fast start)
and then truncate after a few megabytes, that would still be a valid sample

Otherwise you can also zerofill inside the mdat section after few MB and compress the whole easily

I'm happy post a problematic file to Google drive for you to download.

The problem only happens with large files. If someone wants to step me the the process of filling a 150Gb file with zeros for compression, I'll do that but it's much easier for me to simply render a test and upload it.

[InTheWings]

take the 150GB file (or maybe happens with less ?) and get its size in MB
Compute X being total size in MB minus 4 or 5
in console:

extract the first 4MB:
dd if=source.mov of=head bs=1M count=4

extract the last "total size - X MB"
dd if=source.mov of=tail bs=1M skip=X

Then we should be able to rebuild a file with X and those 2 files

[dhl]

take the 150GB file (or maybe happens with less ?) and get its size in MB
Compute X being total size in MB minus 4 or 5
in console:

extract the first 4MB:
dd if=source.mov of=head bs=1M count=4

extract the last "total size - X MB"
dd if=source.mov of=tail bs=1M skip=X

Then we should be able to rebuild a file with X and those 2 files

I'm using macOS. Will this method work in Terminal?

Thanks!

[umxprime]

You may try to use split instead

Code: Select all

split -b <chunk_size> <input_file> <output_file_pattern>

Exemple:

Code: Select all

split -b 200M Movie.mp4 Movie.mp4.

It will output in current working directory 200MB sized chunks named Movie.mp4.01, Movie.mp4.02, Movie.mp4.04, etc...

Code: Select all

SPLIT(1) General Commands Manual SPLIT(1) NAME split – split a file into pieces SYNOPSIS split -d [-l line_count] [-a suffix_length] [file [prefix]] split -d -b byte_count[K|k|M|m|G|g] [-a suffix_length] [file [prefix]] split -d -n chunk_count [-a suffix_length] [file [prefix]] split -d -p pattern [-a suffix_length] [file [prefix]] DESCRIPTION The split utility reads the given file and breaks it up into files of 1000 lines each (if no options are specified), leaving the file unchanged. If file is a single dash (‘-’) or absent, split reads from the standard input. The options are as follows: -a suffix_length Use suffix_length letters to form the suffix of the file name. -b byte_count[K|k|M|m|G|g] Create split files byte_count bytes in length. If k or K is appended to the number, the file is split into byte_count kilobyte pieces. If m or M is appended to the number, the file is split into byte_count megabyte pieces. If g or G is appended to the number, the file is split into byte_count gigabyte pieces. -d Use a numeric suffix instead of a alphabetic suffix. -l line_count Create split files line_count lines in length. -n chunk_count Split file into chunk_count smaller files. The first n - 1 files will be of size (size of file / chunk_count ) and the last file will contain the remaining bytes. -p pattern The file is split whenever an input line matches pattern, which is interpreted as an extended regular expression. The matching line will be the first line of the next output file. This option is incompatible with the -b and -l options. If additional arguments are specified, the first is used as the name of the input file which is to be split. If a second additional argument is specified, it is used as a prefix for the names of the files into which the file is split. In this case, each file into which the file is split is named by the prefix followed by a lexically ordered suffix using suffix_length characters in the range “a-z”. If -a is not specified, two letters are used as the suffix. If the prefix argument is not specified, the file is split into lexically ordered files named with the prefix “x” and with suffixes as above. ENVIRONMENT The LANG, LC_ALL, LC_CTYPE and LC_COLLATE environment variables affect the execution of split as described in environ(7). EXIT STATUS The split utility exits 0 on success, and >0 if an error occurs. EXAMPLES Split input into as many files as needed, so that each file contains at most 2 lines: $ echo -e "first line\nsecond line\nthird line\nforth line" | split -l2 Split input in chunks of 10 bytes using numeric prefixes for file names. This generates two files of 10 bytes (x00 and x01) and a third file (x02) with the remaining 2 bytes: $ echo -e "This is 22 bytes long" | split -d -b10 Split input generating 6 files: echo -e "This is 22 bytes long" | split -n 6 Split input creating a new file every time a line matches the regular expression for a “t” followed by either “a” or “u” thus creating two files: $ echo -e "stack\nstock\nstuck\nanother line" | split -p 't[au]' SEE ALSO csplit(1), re_format(7) STANDARDS The split utility conforms to IEEE Std 1003.1-2001 (“POSIX.1”). HISTORY A split command appeared in Version 3 AT&T UNIX. BUGS The maximum line length for matching patterns is 65536. macOS 12.6 May 9, 2013 macOS 12.6