NuMenu4u.2.0.25

[Master Yoda]

I was wondering if there was any plans to add a option that lets you replace the video footage in a menu file with stills??? im backing a dvd up that has some useless footage in video_ts.vob, its not fake/dummy footage as numenu does'nt strip it out but ive checked and i dont see it come up anywhere on the dvd. Replacing the footage with stills could drop it down to less than 5mb or so, at the mo its about 200mb.

[Zeul]

In the VIP version, you can manually remove specific vobids from the VTS. So if it wasting space, and is selected to be removed, then a still is put there instead, and the still time changed to 0. So the still is played (if in fact it is used), but for 1 frame duration only.

[tijgert]

Great to see al those updates rolling by.

I haven't been Numenuing for a while now and suddenly when I try to I get a run-time error '13', type mismatch.

I'm running out of clues fast, what is causing this?

Found it: DVDDecrypter was missing.. DOH!

[Zeul]

at what stage? as always send me the appropriate files (logs, subtitle & frameserving folder & ALL the original IFOs)

[Mr. Monte]

Is there a How-To guide on using this anywhere ?

TIA

[jel]

@ Mr. Monte
using numenu4u?

well apart from the comprehensive help document that comes with the program, you can also see the recently updated guide for details:fully revamped big 3 guide as featured in the doom9 news (http://www.doom9.org/index.html?/mpg/big3-scenaid.htm)
;)

hth
j

[Mr. Monte]

jel,

Thanks for your input (spanking) :) . I will now pull up my pants.

[Grafdude]

Why do I always get this error when I start the program:

Procedure Name: GetIfoLanguages
Module Name: Test

Error Number: 75
Error Description: Path/File access error
Error Source: Project1
Error Line: 0
Call Stack:
GetIfoLanguages --> Test
LoadTreeView --> Test
ReLoadMenus --> Test
combo1_Click --> MainForm
sListAllDrives --> GlobalFunctions
Form_Activate --> MainForm

When I click ok, the program shuts down, I can't even use it! I reinstalled it with the same error not matter what

[Zeul]

i dunno. No one else, so what is different with your system i wonder. Are you trying to do a disc in the drive, a mounted iso or a folder?

Shoot me your e-mail so i can send a build with extra logging.

[Angelus]

I've ran into a problem when trying to do the menu on the movie "Crash". I've used the latest NuMenu4u and everything completed successfully but the menu is encoded in full screen, rather than widescreen as in the source menu. Just as a check, I checked the d2v files for a couple of them and they have the correct 16:9 aspect ratio set, and the avs files seem to be ok too. It's just that the resulting m2v files after the encoding are in fullscreen. Any ideas?

[Zeul]

@Angelus
Do you have 'Parse video streams to confirm 16:9" enabled (under encoder options) ?

[Angelus]

No I left it to the recommended setting "process all video assets to match attributes" under the encoding options. I'm not sure what I had it set on before because I just installed the latest numenu4u yesterday.

[Zeul]

Make sure that 'Parse video stream to ensure 16:9' and 'process all assets to match attributes' are BOTH turned on; and retry please.

[Angelus]

Thanks Zeul, I checked those options and now the menu is fine.

[Zeul]

Excellent

[bennynihon]

HI Zeul,

I'm using NuMenu4U (the latest version) for the first time, and after setting everything up and clicking "Start", I get an Error 13.

Procedure Name: BeginRoutines
Module Name: MainForm

Error Number: 13
Error Description: Type mismatch
Error Source: Project1
Error Line: 0
Call Stack:
DisplayVerInfo --> GlobalFunctions
BeginRoutines --> MainForm


Anything common that could cause this? Anything else you'd like me to send to narrow down the cause of the problem?

Thanks.

[Zeul]

Is dvddecrypter installed? The only thing i can see is if it wasn't installed then an error would be thrown (I have corrected this now).

[bennynihon]

Is dvddecrypter installed? The only thing i can see is if it wasn't installed then an error would be thrown (I have corrected this now).

Thanks Zeul. That was the problem, even though I was using file mode (and provided a VIDEO_TS path).

[detonate]

Hi. I'm a new user. I get this error everytime I start up Numenu4u:

(380) Invalid Property Value

Procedure Name: sListAllDrives
Module Name: GlobalFunctions

Error Number: 380
Error Description: Invalid property value
Error Source: Project1
Error Line: 42
Call Stack:
sListAllDrives --> GlobalFunctions
Form_Activate --> MainForm

Anyone know why?

[Zeul]

That occurs when there is an unusual setup of the drives. What are your drive configurations? ie c,d etc

[detonate]

Ok I got it fixed. Sorry about that. Daemon tools went wack on me after I unloaded drives.

I have another question though. When running the process of doitfast4u, it runs numenu4u and my cce starts loading, however I get popups of the quality settings to use (i use natural and apply). Is that normal or suppose to be automated? After it's done running cce, it asks me to save changes. Is there anyway to just have it run pass all this without prompting me?

[Zeul]

CCE should be running in the background. What build are you using, the exact version is needed.

[SDragoon]

I recently got the VIP version of NuMenu4u and gave it my first try. So far, I have been unsuccessful.

I am using NM4u 2.0.23. Everytime I try to encode using file method 2, 3, or 4, the program either crashes or gives an error along the lines of "Something went wrong". This always happens after the encoding step.

I am using Muxman, and I have tried with different combos of Muxman 1.4g or 1.6_01, QuEnc or HC (I do not have CCE), AviSynth 2.5.6 or 2.5.5, and either using a directory or mounted ISO as the source. I just cannot get it to work.

Any suggestions?

[Zeul]

The problems you have experienced are very rare. You are using muxman .014g - make sure you have selected the correct muxman version in the VIP settings. What version of HC are you using? To confirm that the settings are correct, set to use original assets (under encoder options) - this will stop the encoding to rule that out as a problem. 'Something went wrong' indicates a muxman error - which is very rare. post the muxman.log file

[TJeR]

The problems you have experienced are very rare. ....... 'Something went wrong' indicates a muxman error - which is very rare. post the muxman.log file

not to be insolent.... but I saw this error so many time I rarely use muxman now..... I am just sorry I never reported it ... but I still love numenu ..... :D and a little scenaid to ...

[Zeul]

Please elaborate - I cannot fix a problem if i don't know about it ;)

[TJeR]

Well the problem is in the middle... to be more explicit, If I just let numenu do everything demux, encode and reauthor everything is fine, but, for example, If I don,t like the result and I wish to increase the bitrate in one or more video, than muxman fails, this appen with scenaid to.

regards

[Zeul]

the bitrate is calculated to be the maximum allowed when the audio is taken into account. Tme max allowed for vide and audio is 9800. So if the audio was 448 then the video max would be 9352. To improve the video adjust the average bitrate NOT the max. This can be done easily by entering the encoder options screen and alter the average bitrate. If you are re-running numenu then just reopen the recovery.log (see the help file) and that will start numenu from the encoding point again - with the new bitrate.

[influenza]

I always use muxman and I hardly ever have problems. Not the last few months at least.

[TJeR]

Well of course I dont change the maximum bitrate but just the avarage. If I modify the avarage bitrate from numenu setting, and numenu applies this setting for any video, everything works fine, but if I just re-encode separetly some video with a different avarage bitrate muxman is not able to recreate the vobs and everything.
To do that I always do a first complete numenu run, than I check the quality of any single video, reencode some with a diffrent bitrate (this is the only thing that really change aspect ratio and other things are the same, than run numenu again, use the recovery function to do muxman job only, and than it fails ..... something with scenaid... again alwys, at the first run muxman does its job perfectly. it is when a try to remux again that it fails....

[influenza]

the logs would be usefull as zeul already suggested.
Maybe muxman just rejects your assets since they are changed comapred to the first run.

[Zeul]

TJeR
An unorthadox approach, but no reason why it should fail. I suspect that the 'new' asset differs from the others somehow. post the cce.ecl that numenu created, the ecl from your new encode, and the muxman error log.

[SDragoon]

Well, I got everything to work after a full uninstall/reinstall including AviSynth.

The only thing I did differently upon setting the program up again is not placing PgcDemux into the install directory. I'm trying to do some testing to make sure that was the only difference.

[Zeul]

I'd be very interested to know what you find.

[TJeR]

TJeR
An unorthadox approach, but no reason why it should fail. I suspect that the 'new' asset differs from the others somehow. post the cce.ecl that numenu created, the ecl from your new encode, and the muxman error log.

I tested the my procedures against muxman again, with several DVDs with diffrent menu type, everything worked Ok.... I couldn' reproduce the error that let me abbaondon muxman a couple of month ago.... maybe I was just doing something wrong and give it up too early....

I am really happy I was wrong :)

[Zeul]

:thanks:

[TuRiSOft]

I got a problem when using PGCDemux to process input folder : it says vid/cid not found. Same DVD (mounted ISO) processed with Decrypter works flawlessly. Error in the command-line parameter ? How can I check ? Is there something I can do to help anymore ? Thanks !!!

[Zeul]

You need the latest version of PGcdemux, released a couple of weeks ago. It corrects this specific issue.

See this thread:

http://forum.doom9.org/showthread.php?p=743946#post743946

[TuRiSOft]

Thanks for the hint , will give it a try !!!!

[wfn1]

Zeul,

Received the "something went wrong" error while doing R1 of "The Work of Director Mark Romanek", report files sent. The menu is almost 700MB.

[Zeul]

Looks like muxman failed on vobid #7 due to excessive bitrate. There is a chance that the audio for that vobid is not the same as the rest (256). If it were more or the video spiked above the max set (9544) then that might cause the error. Try re-encoding that video segment with a lower max and then use recovery console to start from the mux stage.

[wfn1]

I'll give it another shot tonight.

I do have "DVD-Compliant" checked in NM4U under encoder settings because I had similar issues on other DVDs. Muxman actually reported those as excessive bitrate errors in the past and checking that DVD-compliant box took care of the issues before but apparently not this time.

[wfn1]

Zeul,
set the max to 8500 and still got the error, you want files?

[Zeul]

I'm not sure on this one. The mxp file is fine, so it must be an asset problem. As a test try this:

in the mxp file for vobid#7 remove the audio play information. Run the recovery console again, BUT under Recovery options there is a setting 'Disable muxman script creation'. Run the recovery console from muxing again, but this time numenu will not create any new scripts. If the error is not now present then there is definatley a problem with either the video or audio bitrates. As a sidenote, try dropping the video & audio into muxman manually and see what happens with a mux - with all the default values.

[wfn1]

Zeul,
When I dropped the bitrate to 8500, the asset that errored out was actually #8. So #7 goes through now. If I do video and audio for #8 manually in muxman it gives me the excessive bitrate error. If I do video by itself it goes through fine. What I can't understand is why it was asset #7 and now it's 8. Thanks.

[Zeul]

It suggests that there were several files that were a problem. Numenu checks each mux in order, so, if #7 failed we wouldn't know whether #8 was a problem or not. I don't understand why the max bitrate should be dropped that low though.
Are you using CCE? I have heard that sometimes CCE spikes above the max given.

[influenza]

What cce/muxman versions are we talking about?

[Zeul]

New Build Available

[HolyChain]

Hi there!

I'm currently having trouble with NuMenu4U. On various R2 DVDs (different protection types) the programm errors out when starting the Muxman process (current free version).

Error message is "Something went wrong. Aborting". As mentioned a few post earlier, i'm aware, that this is some kind of Muxman error. I re-installed all tools, but i didn't cure the problem. The strange thing is, that NuMenu4U was working for quite some time without any problems. I'm attaching the muxman.log file of the mxp file, where the error occurs, so that maybe this error can be sorted out. The disc is the R2 Version of "Fistful of Dollars".

Little update: i tried it again without stripping any assets and it did work without problems.

Anyway: great tool and thanks for all the work, that is put into it.

Greetings from Germany

Marc

[D3s7]

Bytes remaining in buffer = 0.
17:32:44 End multiplex.
Reference to non-existant scene "VTS1_014_Scene_002" from PGC "DummyPGC"

that's your problem..... Zeul will have to look at the ifo's and the script

you will need to send him the debug .zip file that can be created in numenu