Feature request: Playback of HD video encoded in FFV1.3

Currently, VLC can not be used to playback HD video encoded in FFV1:

• FFV1.3 can't be played back due to regression (see issue #8691 (closed))
• FFV1.1 playback is not multithreaded

Using FFmpeg's "ffplay", it is possible to playback full-HD even in FFV1.1, because it's utilizing the whole CPU. Playing the same file in VLC 2.1.0 only displays a somewhat frozen image :(

It would be great if that would be possible with VLC, too. Thank you very much.

added Severity::normal Type::feature + 1 deleted label

changed milestone to %Bugs paradize

What are the logs?

added Component::Decoders label and removed 1 deleted label

Log of playing back an FFV1.3 file in VLC (2.0.8-0ubuntu0.12.04.1, 64bit)

Added attachment:

• ffv1_level3-vlc_208.log

Original author: ^rooker

When the video encoded as FFV1.3 is opened in VLC v2.0.8 (Ubuntu 12.04.1), the following message is displayed:

No suitable decoder module:
VLC does not support the audio or video format "FFV1". Unfortunately there is no way for you to fix this.

I can post the v2.1.0 logs tomorrow, when I have access to the Windows machine.

Original author: ^rooker

When opening the same video, encoded in FFV1.1, no error is displayed, but due to single-threaded decoding of FFV1.1, the video playback stutters so severely that it actually only displays single images with long pauses in between, or upon seeking.

Original author: ^rooker

Log of playing back an FFV1.1 file in VLC (2.0.8-0ubuntu0.12.04.1, 64bit)

Added attachment:

• ffv1_level1-vlc_208.log

Original author: ^rooker

Please share a file.

changed title from Feature request: Playback of HD video encoded in FFV1 to Feature request: Playback of HD video encoded in FFV1.3

#8691 (closed) is now closed.

This will be fixed for 2.1.3

added Status::fixed label

changed milestone to %2.1.3

closed

Thanks for fixing this. I guess you don't need a file now anymore?

Original author: ^rooker

I do need the file.

Well, it's up: if you want to be sure that it won't break on every other version of VLC, you'd better give the file.

Clear. Just to clarify: You've changed the title to regard only FFV1.3 now, but I would have 2 relevant files: FFV1 version 1 and version 3. They're generated from SVT's "park joy" 1080p and have around 880 MB each.

Should I upload them, or would you prefer to generate them yourself?

Original author: ^rooker

Commandline for generating the files with recent FFmpeg version:

1. FFV1 version 1: ffmpeg -i park_joy_1080p50.y4m -y -threads 8 -an -g 1 -c:v ffv1 -level 1 -coder 1 -context 1 ffv1.1-libavcodec_ffmpeg.avi

2. FFV1 version 3: ffmpeg -i park_joy_1080p50.y4m -y -threads 8 -an -g 1 -c:v ffv1 -level 3 -coder 1 -context 1 -slices 16 -slicecrc 0 ffv1.3-libavcodec_ffmpeg.avi

Original author: ^rooker

I won't generate them, this is quite clear. For many obvious and non-obvious reasons.

http://streams.videolan.org/upload/

Understood. Just thought I'd ask, because sometimes it is preferred to be able to generate a test-source rather than relying on certain files (e.g. FFmpeg FATE).

I'll upload them. No problem. btw: is there an FTP upload possibility? I'm a bit scared to upload 1.6 GiB over HTML...

Original author: ^rooker

ftp://streams.videolan.org/incoming

And maybe you should cut the files. We don't need 800MB to test.

I have now used a different file, reduced the duration and condensed it down to 145 MB each.

I've uploaded ffv1-version3 file to the FTP, but had a connection problem with the ffv1-version 1 file. I had to rename it then, but also the renamed file got interrupted and I didn't want to leave another broken "leftover" on your servers.

Anyway, the files are available here: speed_bag_1080p-ffv1_version1.avi speed_bag_1080p-ffv1_version3.avi

I hope that's okay like that?

Original author: ^rooker

added Version::3.0.x label and removed 1 deleted label