www.makemkv.com

I have spoken to Mike about this via PM's and am currently waiting to hear back. Fingers crossed it'll get sorted soon!

crowfax wrote:I have spoken to Mike about this via PM's and am currently waiting to hear back. Fingers crossed it'll get sorted soon!

Glad to hear it. FWIW, rolling back to 1.6.8 solved the issue completely. No amount of re-installing anything fixed it this time.

BlackDragon24 wrote:Glad to hear it. FWIW, rolling back to 1.6.8 solved the issue completely. No amount of re-installing anything fixed it this time.

I'm using the "workaround" posted earlier in the thread. Replacing the the multiplexing DLL's in 1.6.10 with the ones from 1.6.8. It's worked perfectly so far. I'm sure Mike will get everything ironed out soon.

Revision history

• MakeMKV v1.6.9
• New MKV multiplexing engine

Never touch a running system...

@freshprince 2002

Hi!

Never touch a running system...

This is a program actively in beta testing. Of course there will be further changes, based on observed new problems and/or needs and/or additions and/or deletions, whether or not a current version "runs"...

Same issue here. Typically I rip just the main video and HD audio track. Just tried it (using .10) with "True Grit" and got exactly the symptom that others here are reporting. The MKV "looks fine" and plays back fine, but if you try to seek, it locks the media player (and does a fantastic amount of disk/network IO; seems like it's trying to seek by reading all the bits between where I'm am in the movie and where I'm seeking to).

I have not tried rolling back MakeMKV or the DLLs, this is a default upgrade install of .10 (on top of .9, IIRC).

Same here. Seek problems with Bruce Almighty ripped with 1.6.10


mkvalidator says:

Bruce Almighty.mkv" ERR066: The SeekPoint at 99 references an unknown Cues at 0
file created with libmakemkv v1.6.10 (1.2.0/1.1.0) win(x64-release) /
MakeMKV v1.6.10 win(x64-release)

EDIT:
Problem is ONLY with 1.6.10. Version 1.6.8 is working without (seeking) erros.

+1 chronicles of narnia: prince caspian (blu-ray)

I'm hoping to see some movement on this issue soon. We shall see!

This should be fixed in about a week.

That's great news.

Hi mike,

besides BD ripping, I am using MakeMKV as the tool to remux AVCHD Lite produced by hugely popular Panasonic DMC-TZ7 to MKV container.
MakeMKV is the ONLY tool I am aware of, being able to produce fully functional (also smooth seek) MKV file from this camera.
I tried around 10 different solutions but they all fail on seek (MKV plays very choppy after seek)
So MakeMKV was my "holy grail" ..... till version 1.6.9/1.6.10 arrived.
With 1.6.9/1.6.10, the produced files are not smooth-seekable any more.
Happily, the trick of replacing libmakemkv.dll file(s) from 1.6.8 helped also in this rare case.
All working correctly again !

I supect, this issue is somehow related to mkvmerge core developments.

Thank you for unique, fantastic tool !!!

I wish you to to advertise also MakeMKV ability to remux AVCHD Lite to fully working MKV!
As far as I know, MakeMKV is the only working solution for this task.

All the best,
AndresVR

Please try this http://www.makemkv.com/forum2/viewtopic.php?f=1&t=3772

setarip_old wrote:@freshprince 2002

Hi!

Never touch a running system...

This is a program actively in beta testing. Of course there will be further changes, based on observed new problems and/or needs and/or additions and/or deletions, whether or not a current version "runs"...

So why got the MKV Engine changed? What was the problem with the old one?
And if there's a known problem with the new engine FOR A MONTH, why is there still no release with the old working engine (for compensation) and there are more pointless experiments with the new engine (v1.6.11)?

And why am i getting a message now, that 1.6.8 is too old and I'm forced to install the new NOT WORKING version? THIS SUCKS!
I want to use the Version that I like, not which one the developer wants me to use!
Not even MS forces their stuff like that!

freshprince2002 wrote:So why got the MKV Engine changed? What was the problem with the old one?
And if there's a known problem with the new engine FOR A MONTH, why is there still no release with the old working engine (for compensation) and there are more pointless experiments with the new engine (v1.6.11)?

And why am i getting a message now, that 1.6.8 is too old and I'm forced to install the new NOT WORKING version? THIS SUCKS!
I want to use the Version that I like, not which one the developer wants me to use!
Not even MS forces their stuff like that!

The software is free. And in beta. Jeez. Bitch enough and the developer may call it quits.