blazing saddles

[kahasm]

(version 1.9.1)

it ripped successfully however, when i started playback, i was not getting full motion video, i was getting still frames. the sound was perfect though, no skipping or stuttering. i don't have a error report to post since none was given on a successful rip.

i have tried to rip the dvd version of this movie with less success. it just will not rip at all. gives multiple errors and freezes. so i just bought the bluray which was better but not watchable

[Woodstock]

What are you playing it back with? What you describe is like a player that cannot keep up with the bandwidth necessary to play BD video, so it does the best it can. In those cases, video is the first thing that "fails".

Is the MKV file local, or on a network?

Without logs from the rip, it is impossible to say if there was something in the rip that raises questions. The FAQ in my signature covers how to get the debug logs. You can't post them as an attachment here, but you CAN post their text in a message, so long as they're less than 60K.

[kahasm]

i am using the same program i watch blu-rays on, Nero Media. which to date I play all BDs on, especially all those ripped with MKV ( nero plays back MKV perfectly). I have never seen this issue with any other BD rip except blazing saddles. I have purchased different versions and types (DVD and BD) to zero success. It will rip but no playback. it looks like still frames every time. I have included a rip log, since it ripped and did not fail.

it is not on a network.

with each new upgrade to MKV I try to do a successful rip/playback of blazzing saddles and have yet to succeed.

I have attempted to attach the debug file but each time I press "add the file" it logs me out and opens a 2nd window to upload)
below is the debug file from the rip:
Debug log started at Wed Nov 02 08:32:23 2016 , written by MakeMKV v1.10.2 win(x64-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.10.2 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\kaz/MakeMKV_log.txt
003007:0000 Using direct disc access mode
001003:0020 DEBUG: Code 0 at =%g!?G'y&Z6L_l:121262164
001003:0020 DEBUG: Code 0 at kT>t1wI4Z_k1)PDu:213136148
DEBUG: Code 2147483648 at 0u9(N<b_y+%!2_CG:121265315
DAFD=PAAAADAAAAEABDQkEEwEBAQ==
DCE=QnS6kra6/wnVsxSqn/Ob5tBnlqh0kAX6flBumGeqpJmdITQMuPShSNsuA/iPA2chbLkWFcaUnyrBdGUTlyUHpmg1AgjiA+nceGxMHsjXLzI3yArQLhh5QLmjWt5ouFsYia0P9ly0Dq1cVe8BcI0MtQmXc+BmjmjqQA==
DCE=IOc2o+sY2lXD9Io0WiljOaiQQCcgK/IH+1NDDmqx0HhsrYJjM40FqvbIz8xE/OL9BZudX25ks+oHbqXdpTjKKGxax080yWutzje/vq2m38EYBDUPFhNmNFmDTDwg2OpHTxJEkC7FmpEBbK3roR7cX6o6xT1k38Z3Pg==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DISCID=6B0DE82922A19C4533417BA44A887EE9E78AA723
003307:0000 File 00003.mpls was added as title #0
003025:0000 Title #00001.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003025:0000 Title #00005.m2ts has length of 23 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003025:0000 Title #00006.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
003307:0000 File 00008.m2ts was added as title #1
003307:0000 File 00009.m2ts was added as title #2
003307:0000 File 00010.m2ts was added as title #3
003307:0000 File 00011.m2ts was added as title #4
003307:0000 File 00012.m2ts was added as title #5
003025:0000 Title #00014.m2ts has length of 12 seconds which is less than minimum title length of 120 seconds and was therefore skipped
005011:0000 Operation successfully completed
005014:0000 Saving 1 titles into directory G:/MKV-NEW/Blazing Saddles
005005:0080 1 titles saved
005036:0104 Copy complete. 1 titles saved.
Application exited at Wed Nov 02 08:46:06 2016

[Woodstock]

Are you trying to play the movie from the MKV file, or by using MakeMKV as a streaming source?

If you're using MakeMKV as a streaming source, you probably need to reduce the read buffer size in Preferences->IO. If it is too large, the drive will start to spin down before the next "chunk" is read into the buffer.

Your log shows that the rip completed; is the MKV file in "G:/MKV-NEW/Blazing Saddles" playable?

[yorgo]

I may have experienced this a couple times in the past as well, once after ripping a blu-ray directly to MKV and once converting a BD folder structure file to MKV (neither were Blazing Saddles). The MKV file plays back what appears to be only a few frames every second, giving the movie the feel of playing back quick "snapshots" rather than the fluid movement of all frames. It happened while using VLC, MPC-HD, and to a streaming media player.

I re-ripped and one of them played fine after. The other required swapping out the disc which then ripped fine. If you've tried using different versions of MakeMKV and swapped discs, you may want to try a different BD drive. Then try swapping the disc again. Other than that, I'm at a loss, sorry...