[200] PopCorn MKV ReMuxer

[bldblu]

First thank you for this easy to use remuxer for the header compression issues BUT?

Im having 2 issues and am a W7 64 bit user

i took your advice and downloaded 32 bit mediainfo,and installed into remuxer directory,and it works fine until i right click explorer and then press mediainfo for checking my movies,and it wont talk to my 64 bit system

so the remuxer works with 32 bit mediainfo installed but mediainfo itself wont work with my movies

i then tried changing my permissions to have 32 bit mediainfo communicate with my 64 bit system,but to no avail

any workarounds for this,as your program really works well for the compression issues

thank you again

[HeartWare]

Only one thing comes to mind:

Try to uninstall the 32-bit version (but copy the 32-bit MediaInfo.DLL first to a backup directory), then install the 64-bit version, then copy the 32-bit .DLL file back into the ReMuxer directory.

[garp99]

Or perhaps installing the 32 bit version into sub-folder where ReMuxer is, and then install the 64 bit version
where you normally install programs, so that the 64bit version will assign right-click context menu for movies
to use the 64 bit version. And the 32 bit version only needs to be used by ReMuxer.

[Bryson]

This program does not work for me. Running Windows 7 64-bit. I managed to fix the problem by using mkvmerge and unselecting header compression. Here is the error and yes i've installed 32bit media info as was suggested in this thread:


mkvmerge v4.5.0 ('Speed of Light') built on Feb 1 2011 02:10:32
Error: The source file could not be opened successfully, or retrieving its size by seeking to the end did not work.

[MikeMcr]

(02-25-2011 06:20 PM)Bryson Wrote:  mkvmerge v4.5.0 ('Speed of Light') built on Feb 1 2011 02:10:32
Error: The source file could not be opened successfully, or retrieving its size by seeking to the end did not work.

Same error here on Windows 7 x64 SP1. I think this started since upgrading mkvmerge to 4.5.0.

However, it works fine from the MKVMerge GUI and all my batch files using the command line tool still work.

---

(02-25-2011 06:20 PM)Bryson Wrote:  mkvmerge v4.5.0 ('Speed of Light') built on Feb 1 2011 02:10:32
Error: The source file could not be opened successfully, or retrieving its size by seeking to the end did not work.

OK, I see the problem. The error message actually contains the full path and filename of the input file but all the backslash characters in the path are missing! That is why it cannot find the file.

What is removing the backslashes?

[HeartWare]

MKVMerge v4.5.0 most likely...

[MikeMcr]

(02-27-2011 03:40 PM)HeartWare Wrote:  MKVMerge v4.5.0 most likely...

I eventually discovered it only happens if the input file name is over a certain length. However, calling MKVMerge from the command prompt directly with the same parameters works fine.

Does your code work differently when the command line is over a certain length? I ask because when it works, there appears to be batch file created in the ReMuxer.TMP Temp folder with all the parameters directly passed to MKVMerge.

However, when it fails, the batch file created appears to reference another file with an INP extension. Is this the problem?

EDIT: If I edit the INP options file and swap each "\" in the path for "\\", it works. Seems to be treating "\" as an escape character.

[HeartWare]

(03-06-2011 05:41 PM)MikeMcr Wrote:  Does your code work differently when the command line is over a certain length?

Yes, it does. As you have determined, the program uses an external input file containing the parameters when the command line becomes too long to be safely passed on the command line.

(03-06-2011 05:41 PM)MikeMcr Wrote:  If I edit the INP options file and swap each "\" in the path for "\\", it works. Seems to be treating "\" as an escape character.

Yes, it does - which it shouldn't (previous versions didn't).

[porterx]

Heartware, great program. I love it. I have a feature request.

Could you add up/down arrows to the right pane so we could change audio channel order (like mkvmerge gui has) without leaving the main screen.

Thanks.

[temporarysmeg]

I'm getting the same path problems as previous posters were experiencing. I downgraded Mkvtoolnix to 4.5 from the latest and still got the problem. Reading above, it seems that was the version where the problems began for your program. Trust my luck to chose the earlier version were the problems started.

[HeartWare]

You'll have to stick to MKV Tools v4.4 until I release an update...

[temporarysmeg]

(11-01-2011 07:14 AM)HeartWare Wrote:  You'll have to stick to MKV Tools v4.4 until I release an update...

Thanks for replying.

I have a suggestion for improvements to the program.

Having to install MKVToonix and MediaInfo is currently a big problem because of the problems newer versions of mkvmerge cause. It means people cannot have installed a newer version than 4.4.0.

I therefore think it would be better if ReMuxer first looked into it's program directory for mkvmerge.exe, mkvinfo.exe and mediainfo.dll and if they are found, they are selected to be used in the mkvmerge drop down list selection. This would get around the problems with having newer versions than 4.4 installed. It would also make it easier to use the program IMO. I have uninstalled mkvtoolnix and ReMuxer is still listing the version in the drop down list that was installed even though it is now unavailable.

Instead of functioning I get an access violation error the same as a previous member posted, "access violation at address 005B921E" in module 'ReMuxer.exe'. Write of address 00000529.". I thought that this was because I didn't have mkvtoolnix installed. However after installing mkvtoolnix and MediaInfo, I am still getting the same error. All versions are x86 as I use Windows XP Pro x86. Strangely, copying the mediainfo.dll to the ReMuxer program directory and it now works. Why does the MediaInfo.dll need to be in the program directory and mkvmerge / mkvinfo not picked up in the program directory?

Is there any way for you to use mediainfo.dll and mkvmerge.exe / mkvinfo.exe with them locally in the program directory rather than having to have them installed? As it is ATM it complicates things. If these could be used without having them installed, it would make it far easier. Just a case of having simple instructions to put mediainfo.dll, mkvmerge.exe and mkvinfo.exe in the program directory. A help button or a text file with the program would make it much easier.

This should also solve problems with x64 systems.

[MikeMcr]

A warning that MKVMerge version 5.2.0 and later won't work with MKV ReMuxer. You get missing ID errors. The cause seems to be this change:

Quote:2011-12-11 Moritz Bunkus <moritz@bunkus.org>

* mkvmerge: bug fix: Changed how mkvmerge assigns IDs to tracks in
source files for Matroska and MP4 files. That way files whose
headers contain the same ID for multiple tracks will work
correctly. Fix for bug 681.

This means the IDs passed in by MKV Remuxer no longer matches the ones displayed if you load the file into mmg.exe.

[HeartWare]

Do you have an example of such a file so that I can investigate?

[MikeMcr]

(12-22-2011 08:03 AM)HeartWare Wrote:  Do you have an example of such a file so that I can investigate?

It seems to happen for all files I have tried. Here are examples from a working MKVMerge 5.0.1:

Code:

mkvmerge.exe -o M:\Output\Test.mkv --compression 1:none --default-track 1:yes --compression 2:none --default-track 2:yes M:\Input\Test.mkv --track-order 0:1,0:2

mkvmerge v5.0.1 ('Es ist Sommer') built on Oct  9 2011 11:55:43
'M:\Input\Test.mkv': Using the Matroska demultiplexer.
'M:\Input\Test.mkv' track 1: Using the MPEG-4 part 10 (AVC) video output module.
'M:\Input\Test.mkv' track 2: Using the AC3 output module.
The file 'M:\Output\Test.mkv' has been opened for writing.

This is from the "broken" 5.2.0:

Code:

mkvmerge.exe -o M:\Output\Test.mkv --compression 1:none --default-track 1:yes --compression 2:none --default-track 2:yes M:\Input\Test.mkv --track-order 0:1,0:2

mkvmerge v5.2.0 ('I can't explain') built on Dec 18 2011 18:12:03
'M:\Input\Test.mkv': Using the demultiplexer for the format 'Matroska'.
'M:\Input\Test.mkv' track 0: Using the output module for the format 'AVC/h.264'.
'M:\Input\Test.mkv' track 1: Using the output module for the format 'AC3'.
Warning: 'M:\Input\Test.mkv': A track with the ID 2 was requested but not found in the file. The corresponding option will be ignored.
The file 'M:\Output\Test.mkv' has been opened for writing.

That warning results in an error. Notice the difference is version 5.2.0 numbers the tracks starting at 0 instead of 1.

Looks like this has been reported as a bug in MKVExtract but it isn't clear to me if the fix will be to MKVMerge or MKVExtract. Hopefully the former.

https://www.bunkus.org/bugzilla/show_bug.cgi?id=689