Run-time 13 error Type mismatch

[iparout]

Hi.

I'm following the latest big3 guide here at the site and I have come up to a pretty common (as it seems error).

Before DIF4U demuxes the VTS streams, NM4U loads and at the same time BatchCCE loads and performs 5 pass encodings of several streams (I am not familiar with the process so I don't know what this is). But anyways, after BatchCCE finishes encoding the streams, and before NM4U shuts down, I get a Run-time 13 Type mismatch error, probably from NM4U.

I did a search and found out that this is a common problem, however the last post I found was 1 month old so I would like to ask if anything has been done to cope with the problem.

Questions :

1) If I click on OK, then the error window vanishes and DIF4U continues doing its job flawlessly (demuxing streams with DVD Decrypter). So I am wondering, are there gonna be any potential errors in the final movie if I just click OK on the error and let the process continue normally ?

2) I followed jel's instructions at another thread, where he said :

'global options' > 'Re encode Menus using NuMenu4u Before demuxing' is NOT selected.
'global options' > 'post processing' > 'Do Not Copy Menu Files' is NOT selected
'global options' > 'post processing' > 'Create Video_TS using unused VTSes' IS selected.
'global options' > 'Create Debug Log' IS selected.

Well, I'm glad to find out that the problem doesn't come up anymore (at least not yet), however I am wondering, what's the drawback of putting NM4U out of the scene in this stage, in order to avoid the run-time error ? What am I losing compared to if I used NM4U normally ?

And last but not least, what are you suggesting I should do ? Press OK on the error window and let the process continue or disable NM4U as jel described above ?

Thanks in advance.

[D3s7]

Chances are the problem will occur no matter what order you do numenu...

No... i doubt the script will come out correct - however, Zeul is currently working on fixes/changes so I'm sure this is one of the items he has addressed.

By Not using numenu, you potentially could lose space that could be used for the main menu, however loss of a few bytes would be better then a non-functional menu :)

I'd suggest seeing how large your menus are and if not too bad, redo the rip w/out numenu at this time... Or wait till the next build is released

[D3s7]

Chances are the problem will occur no matter what order you do numenu...

No... i doubt the script will come out correct - however, Zeul is currently working on fixes/changes so I'm sure this is one of the items he has addressed.

By Not using numenu, you potentially could lose space that could be used for the main menu, however loss of a few bytes would be better then a non-functional menu :)

I'd suggest seeing how large your menus are and if not too bad, redo the rip w/out numenu at this time... Or wait till the next build is released

[iparout]

Originally posted by D3s7
Chances are the problem will occur no matter what order you do numenu...

No... i doubt the script will come out correct - however, Zeul is currently working on fixes/changes so I'm sure this is one of the items he has addressed.

By Not using numenu, you potentially could lose space that could be used for the main menu, however loss of a few bytes would be better then a non-functional menu :)

I'd suggest seeing how large your menus are and if not too bad, redo the rip w/out numenu at this time... Or wait till the next build is released

Well, in order to redo the rip without numenu as you're suggesting, all I have to do is follow jel's advice as quoted on my first post, right ? If I do so, does this mean that I'll have no menus in the output DVD+R ? Or will everything work fine, apart from the fact that the menus would be bigger in size than the ones numenu would have created ?

Sorry if this question sounds stupid, it's my first rip ever...:)

And BTW, where can I see how large the menus I am currently using are ? Which files are the menus ?

Thanks once again.

[D3s7]

Menus are any vob that's *_0.VOB and the VIDEO_TS.VOB file

well I'm not sure what Jel suggested so I can't answer that question however, I'd recommend deleting the rip folder and disabling the "Re-encode menus first" option and make sure the "Don't copy menu files" is not checked

Then proceed as normal without numenu

[iparout]

Originally posted by D3s7
Menus are any vob that's *_0.VOB and the VIDEO_TS.VOB file

well I'm not sure what Jel suggested so I can't answer that question however, I'd recommend deleting the rip folder and disabling the "Re-encode menus first" option and make sure the "Don't copy menu files" is not checked

Then proceed as normal without numenu

Well, what jel suggested is quoted in my first post... :D lol

'global options' > 'Re encode Menus using NuMenu4u Before demuxing' is NOT selected.
'global options' > 'post processing' > 'Do Not Copy Menu Files' is NOT selected
'global options' > 'post processing' > 'Create Video_TS using unused VTSes' IS selected.
'global options' > 'Create Debug Log' IS selected.

So I guess it's the same to what you suggested.

Well, I already did that and I'm now in the middle of my 1st CCE pass... I'm keeping my fingers crossed and hope that everything will turn out fine.

[iparout]

I tried another movie and again I got the same problem with NM4U.

At first I get the following error :

Number: 53
Description: File not found

EXE Name: NuMenu4U
EXE Path: E:\DVD+R\NuMenu4U
EXE Version: Version 1.4.7

Call Stack (lowest level first)

AudioProcess::CheckAudioSource (line 22)

and when I hit OK, another error pops up :

Number: 13
Description: Type mismatch

EXE Name: NuMenu4U
EXE Path: E:\DVD+R\NuMenu4U
EXE Version: Version 1.4.7

Call Stack (lowest level first)

Scenarist_Build::GenerateAudioData (line 26)

I don't know what has happened, however, out of 2 movies I have 0 success with NM4U. I'll take NM4U out of the process again, but hopefully the coders will fix this problem cause it seems such a useful tool for everyone...

BTW, if you have any idea why the errors I fore-mentioned appear, please do tell me...

Thanks in advance.

P.S. : The movie is Terminator 2, region 2 version, which has DTS audio. I'm also using Scenarist 3.

[iparout]

I was wondering if there are any news on this matter. Have those bugs been sorted out ? Or at least, have they been aknowledged be the cders of the program ?

What can I do to sort them out ? Or should I just wait for a new build to arrive ?

Numenu is a very usefull tool that can save lots of space and improve quality of the main movie, however it looks like those bugs have made it rather impossible to use...

Any comments are welcome.

[D3s7]

I believe Zeul has sorted many of these out and is testing his new builds to verify.

Generally speaking when you get these types of errors there isn't much you can do to change/fix the outcome and waiting for a new build is the best bet.

Also, you might get a little quicker response/updates if you post in the "Numenu" thread. That way this will help others too if they are having the same issues

[iparout]

Originally posted by D3s7
I believe Zeul has sorted many of these out and is testing his new builds to verify.

Generally speaking when you get these types of errors there isn't much you can do to change/fix the outcome and waiting for a new build is the best bet.

Also, you might get a little quicker response/updates if you post in the "Numenu" thread. That way this will help others too if they are having the same issues

I see. I'll be waiting for a new version then. Thanks a lot.