Log in

View Full Version : (Runtime?)Error in NuMenu4u


cHiNgAcHg00k
11th October 2005, 15:49
When I try to reencode a menu I get the following error (wheter I use DIF4U or just NuMenu4u standalone (including recovery console)):

In version 2.0.18:
Procedure Name: Item
Module Name: CELL_DETAILS

Error Number: 5
Error Description: Invalid procedure call or argument
Error Source: ErrorHandler
Error Line: 8
Call Stack:
Item --> CELL_DETAILS
ProcessSST --> NewSUBS
StartNuMenu4u --> ExecuteProgram
go_Click --> MainForm



In version 2.0.23
Procedure Name: Item
Module Name: CELL_DETAILS

Error Number: 5
Error Description: Invalid procedure call or argument
Error Source: ErrorHandler
Error Line: 8
Call Stack:
Item --> CELL_DETAILS
ProcessSST --> NewSUBS

This is the first time I've ever seen such an error. This has happened on 2 different systems (one AMD and one Intel). Any suggestions?
Tried searching the forums but didn't find anything usefull....

Edit: Perhaps it's usefull to mention that the menu is located in the 24th VTS and that it's a dvd consisting of app. 70 VTS (a lot of small videos)

Zeul
11th October 2005, 19:31
I did find a problem that would cause this error if the first sub stream did not start at 0x20. Shoot me your e-mail and i will send the new build for you to try. (It corrected a very similar issue that someone else had).

cHiNgAcHg00k
11th October 2005, 20:30
You have a PM :)

And thanx!

cHiNgAcHg00k
12th October 2005, 16:10
Now I get an error in sonic scenarist when trying to compile the menues:

Error Still MPEG Video file is larger than Video buffer in DVD Spec("008_001.m2v" has 5757516 bytes).
Error Please reduce the bitrate in ProjectSettings or make the source still image simpler.
Error dvd_mux : DoMux Multiplexing Error
Error Terminated Multiplexing (ScenaristScript27_1.scn-VTS_24_008_001_t_t.vob).
Error Total bitrate is too HIGH. Please reduce the stream bitrate or the number of stream.
Error Multiplex is failed.
Info Multiplexing failed, Track<VTS_24_008_001_t>

Error MuxFromDB:MuxVTS failed
Error Multiplex failed
Error DVD files could not be created

I've used 3 pass VBR using CCE in NuMenu4u, so can't se why/how the bitrate of the above mentioned m2v file should be any higher than any of the rest of the files. Tried to manually encode the file in CCE using CBR of 3000 kbits and then replacing the "bad file" with the one I've encoded manually, but no good :( (Did the latter because I saw it mentioned here in the forums)

Any ideas? This is turning out to be a pain the *ss dvd :p

Zeul
12th October 2005, 19:29
hmm
This suggests that the video asset is NOT a still, whereas it was labelled as so. Please drop that asset into Scenarist and tell me what it reports.

cHiNgAcHg00k
12th October 2005, 19:52
Dropped the file 008_001.M2V into the data editor and this is what information window displays:

Info Accepted J:\Rel\D_VTS_24_0\NEW_M2V\008_001.M2V
Info 1 file(s) accepted, 0 file(s) rejected

If I click on the recently added file it says "video 008_001" and displays info about it's video attributes, but in the data that has been added by NuMenu4u it's named as a Encoded Still.

Tried to replace it with a Place Holder and then switch back to data, but when I do the latter I get the error saying "This is not image file. [path\to\.m2v file]".

If this reoply is insufficient please let me know what else you need to know.

Thanx in advance

Zeul
12th October 2005, 20:31
ok, can you send me the following, so i can see what went wrong:

frameserving folder
subtitle folder
All original IFOs
logs & scp

cHiNgAcHg00k
12th October 2005, 22:28
you have mail m8 :)

Zeul
13th October 2005, 09:04
i don't appear to have mail :(

cHiNgAcHg00k
13th October 2005, 12:23
Tried sending again, hope it works now... I sent the stuff in 2 mails, perhaps the previous attachment was too big (2 MB)

Zeul
17th October 2005, 09:25
I have the files now (Damned BT had spammed them. GRRRR). I see the problem the asset was flagged as a still by VobTest, even though it isn't. Time to find out why...

Zeul
31st October 2005, 10:51
As a follow up to this problem:
This is going to be far from easy to fix. We have isolated the problem to the original authoring. Certain flags have been set in the VOB file that are normally associated with Still images. This is why vobtest reported a Still image. We are looking at ways around this.

cHiNgAcHg00k
27th January 2006, 22:43
Been a while now and I was just wondering what the status of this subject was? Tried with the latest version of Numenu4u but it still fails.

Zeul
28th January 2006, 10:51
There isn't, unfortuanetly. The original had some authoring errors - which is fooling numenu / vobtest. This perhaps is going to be a disc that cannot be processed :(

cHiNgAcHg00k
28th January 2006, 20:26
Ok, well thanx for trying