The VideoLAN Forums

I found what appears to be a bug using the next frame functionality. I can reproduce it two ways, the first is through code where I simply load a video and call libvlc_media_player_next_frame multiple times, eventually I see VLC output the message "EOF Reached" and libvlc_media_player_next_frame will no longer give me new frames. The other is using the VLC player itself, I load a video, pause it and hold the 'e' key down and watch the messages in the message output view. Here I also get the "EOF Reached" and the video will no longer work. In both cases the "EOF" is not at the actual end of the file, I have tried different video formats, an mp4 and a webm; happens regardless of the format.

I have tested with the latest code from git as well as the current version on videolan.org's homepage.

Does anyone know a work around or how to fix this?

Thanks!

There must be a reason why VLC thinks EOF happened, e.g. the file is incomplete, or the server hung up or whatever.

Both files are local and play through to the end just fine if I simply play them without frame stepping. Can you try it on your end? Load VLC and a local file, pause the video, open the message window and then hold down 'e'. It may take a while but eventually you should see the EOF message. If it does not happen for you then please let me know what type of video you used.

Thanks.

Can anyone else duplicate this? If not then I'd like to figure out what is wrong with my setup.

Thanks.

You claimed that it affects VLC too, not just your app, so it seems you answered your own question.

I agree, but maybe it is my media that is causing so I wanted to determine if there are some variables that cause it to happen or not. What is the best way to go about getting an issue fixed?

Thanks.

Generally, sending a patch against vlc.git to the vlc-devel mailing list.