Page 1 of 1

VLC 2.2.0 - HD/MKV - Stuttering and Lagging

Posted: 19 Mar 2015 19:52
by ARES_GOD
So version 2.2.0 has problems playing HD/MKV files, i downgraded to 2.1.5 wich has no problems, is there a fix to be able to play properly HD/MKV files on 2.2.0 because i like the new functions it has and i want VLC to always be updated but since i play a lot of HD/MKV files i had to switch back to 2.1.5, Thanks

Re: VLC 2.2.0 - HD/MKV - Stuttering and Lagging

Posted: 20 Mar 2015 00:40
by bensmith
There is a well known and discussed issue of problems with 2.2.0 attempting to play MKV files stored on external media or on the local network, or NAS drive. Its been discussed in several other threads.

https://forum.videolan.org/viewtopic.php?f=14&t=124873
https://forum.videolan.org/viewtopic.php?f=14&t=124525
https://forum.videolan.org/viewtopic.php?f=14&t=124487
https://forum.videolan.org/viewtopic.php?f=14&t=124431

If you are experiencing this issue, the suggested workaround is to use the following nightly build that appears to fix the issue of playing an MKV file within VLC that is stored on the network or on an external drive.
http://nightlies.videolan.org/build/win ... 0304-0202/

It is reported that this issue will be fixed in the 2.2.1 release.

Re: VLC 2.2.0 - HD/MKV - Stuttering and Lagging

Posted: 20 Mar 2015 05:50
by ARES_GOD
There is a well known and discussed issue of problems with 2.2.0 attempting to play MKV files stored on external media or on the local network, or NAS drive. Its been discussed in several other threads.

https://forum.videolan.org/viewtopic.php?f=14&t=124873
https://forum.videolan.org/viewtopic.php?f=14&t=124525
https://forum.videolan.org/viewtopic.php?f=14&t=124487
https://forum.videolan.org/viewtopic.php?f=14&t=124431

If you are experiencing this issue, the suggested workaround is to use the following nightly build that appears to fix the issue of playing an MKV file within VLC that is stored on the network or on an external drive.
http://nightlies.videolan.org/build/win ... 0304-0202/

It is reported that this issue will be fixed in the 2.2.1 release.
Thanks