NuMenu4u RC4 Build 1.3

[Zeul]

Hello
An updated build is now available:

Bug fix:
Finally found the error that was causing the zipping utility to fail
Critical update to script creation in scenarist 3.0 (dummy highlights were not being created to act as 'holders' for the real highlights)
Critical update to NTSC sub duration written into the script file for scenarist 2.6/7 (incorrect drop frame was being applied)
It has also become apparant that the menu subpics do not always have the stream ID's 0x20 & 21, the code has been changed to reflect this.
Alteration to the internal routines for recalculating the sst timecodes when minimum duration is specified.
A brand new Automate is now available also, which appears to address many of the problems.

http://www.numenu4u.com/NuMenu4u.zip
http://www.numenu4u.com/Automate.zip

Zeul

PS As with all our apps we recommend not naming folders with spaces in them!! so C:\test 1 should be C:\test_1 NB the underscore

[Geddons]

Thank you very much for this new release, I'm gonna test it and tell you what's up.

[Geddons]

Excellent, it works great now. There is still a serious bug : the program crashes when I decide to set a directory not empty. This is not really hard to "fix" it : I just have to delete all the files & folders and to retry but can you do something ? (And do you need crash logs ?)

[Tore]

It has also become apparant that the menu subpics do not always have the stream ID's 0x20 & 21, the code has been changed to reflect this.

Will this bugfix finally enable me to reencode Finding Nemo?
(I've think i sendt you the files you needed earlier this fall.)

[Zeul]

@Tore
I have just run it against the files you sent me, and scenarist reported no errors or warnings. I can't actually compile because I have no actual assets :D

Zeul

[wmansir]

Good news, it appears you have fixed the scenarist problem I was having with Shrek 2. I still have to fully test it but the process completed without any errors.

[Geddons]

Happy New Year Zeul and everybody ! :cool:

[jarthel]

.

[PhAtfiSh]

Zeul, i wonder if you could help me. Im using this version of your app on a pretty large menu (624Mb for VTS_02, 745Mb including VIDEO_TS).

But every time ive tried it, the video_ts vob was demuxed and encoded fine; but the vts_02 menu is never encoded, it just skips straight to building the scenarist script.

I did post this before but was a bit busy and only had a chance to look at it again now: So in referance to your reply to the previous post, i dont think the minimum frame duration is a problem. There are a number of larger (20 - 60 Mb) .m2v's in "NEW_M2V", along with a lot of smaller 100 - 1000 Kb ones.

It just seems not to encode for some reason, im not sure if its my error or your program doesnt like this dvd.

Thank you.

[Zeul]

check your pm

[Geddons]

Hi Zeul, I got another problem with recompressing my menus:

I try to reencode the menu of "Shaun of the dead" and it crashes in scenarist in build mode (so in the end of the process :( ).

Scenarist tells me I've got an AC3 audio file short of 7 frames than the video. How could I fix that ?

[Zeul]

Did you have Pad AC3 checked in the Audio options? To correct in scenarist just select the video part of the offending track and in duration reduce by 7 frames.

[Geddons]

Originally posted by Zeul
Did you have Pad AC3 checked in the Audio options? To correct in scenarist just select the video part of the offending track and in duration reduce by 7 frames.

If you are talking about the conversion from WAV to AC3 with Besweet, yes it is, like this picture tells you :


http://img93.exs.cx/img93/1676/numenu.jpg

I'm gonna test your tip, I'll keep you updated ;)

[Geddons]

Huum... I knew I wasn't really skilled with Scenarist and it confirmed my thoughts :D.

Zeul > I don't find in Scenarist (3.0) how to do what you told me. Could please explain me :( ?


Geddons.

[Zeul]

sure
Its pretty easy actually.
In track editor select the offending track.
Now click the video part.
The property browser should now show the video details.
If all it shows is main video play and streamnumber, then double click main video play
you will now see a duration field. Change this duration to xxx - 7 frames.
Dont forget that PAL is 25 frames, NTSC is 30 frames.
So (PAL) if duration is 00:00:41;14 change to 00:00:41;07
If you now look at the video part again, there will be a grey box at the end - this is the amount of frames you have removed :)

[Geddons]

Oh thanks :) , it worked... only on this track. Well it seems this DVD has got a very annoying menu, here is the next error:


Error This VOB has 72 fields (in track:VTS_2_003_t).
Error -- The preceding VOB in seamless connection must have equal to or more than 75 fields.
Error dvd_mux : DoMux Multiplexing Error
Error Terminated Multiplexing (ScenaristScript30_1-VTS_2_003_t_t.vob).
Error The preceding VOB in seamless connection is too short.
Error Multiplex is failed.
Error Multiplexing failed, Track "VTS_2_003_t"



The first one was on the VTS_2_001_t ... what could I do now ? :confused:

[Zeul]

hmmm...
Ok we think this might be an audio error, possibly caused by besweet??. A couple of things to try:
Remove the audio track and see if it muxes.
If there is a problem because it is seamless then change the seamless flag to non-seamless in the scenario.
You could also try JUST changing the seamless flag.

let us know

[Trahald]

Working great so far.. the new automate helped alot.. and script imported and compiled no errors... great work zuel

[nick101181]

I'm trying this out and I'm getting an error after dvddecrypter demuxs
it says

Procedure Name: ReadD2VFile
Module Name: AssetProcess

Error Number: 53
Error Description: File not found
Error Source: Project1
Error Line: 13
Call Stack:
ReadD2VFile --> AssetProcess
ProcessVideo --> AssetProcess
NewDVD2AVIProc --> AssetProcess
StartNuMenu4u --> ExecuteProgram
go_Click --> MainForm

How Do I fix this. What I'm currently try to do is convert a pal menu to ntsc. I use daemon tools to load the iso in a virtual drive. Then I use numenu4u and select video_ts and the VTS_01_0.vob and I check the pal to ntsc settings. It runs for a few seconds then I get this error. How do I fix this. I have almost every video encoding tool imaginable so I'm not missing dvd2avi or anything like it's complaining about. thanks

[Zeul]

Use the debug feature please to send me the relevant files please.

[zamarky1]

Hiya

which versions of CCE does NuMenu4u work with ?

I only have 2.50. Can it work with this ?

Thanks

Mark

[Zeul]

the present release does not, however i am in final testing of a new build that does :)

[zamarky1]

Hiya Zeul

thanks for your reply.

Well i'll sit and wait for that. I would really like to have a crack at Numenu4u.

Thnks


Mark

[Zeul]

ok testers :)
A new build for testing. NB consider this an alpha release, so i appreciate all comments :D hence a release in this thread.

I have added support for CCE Basic, CCE 2.7+, Procoder (via eclpro), Quenc. There are also several bug fixes. Most notable incorrectly naming some assets as No_Encode and on an NTSC->PAL conversion with WAV audio the audio wasn't processed correctly.

From now on you now need to specify the CCE Executable NOT the ecl file. Depending on the version chosen will dictate whether eclcce is used or not. If so, then i now write the eclcce.ini automatically. However, for Procoder you must specify the EclPro.exe file NOT Procoder.exe itself. These new parts are now under the encoding tab.

Also i now also use Trahalds revpulldpown.exe file for pulldown. Please paste this into the install dir.

Rename the executable to NuMenu4u.exe

http://www.numenu4u.com/NuMenu4u.RC4.2.0.zip
http://www.numenu4u.com/revpulldown.exe

good luck :p

[jel]

zeul,

great work as always :D
i know there will be many procoder/quenc users who will be very happy with this latest addition.

wanted to quickly point out to any users unfamiliar with eclpro, that it is a utility written by robot1. information and download can be found in this thread: EclPro (http://forum.doom9.org/showthread.php?s=&threadid=83334&highlight=eclpro)

keep on rockin like a compressed mineral thingy

j

[Geddons]

Thx Zeul, I'm going to test it on my next projects. I have no one at this moment but I'll keep you updated :).

[robot1]

Originally posted by Zeul
ok testers :)
A new build for testing. NB consider this an alpha release, so i appreciate all comments :D hence a release in this thread.

I have added support for CCE Basic, CCE 2.7+, Procoder (via eclpro), Quenc. There are also several bug fixes. Most notable incorrectly naming some assets as No_Encode and on an NTSC->PAL conversion with WAV audio the audio wasn't processed correctly.
I will test ProCoder ASAP, and will report back.
I used ProCoder also in previous versions, renaming ECLPro to ECLCCE, but I often had to modify something in Scenarist, for the lack of the chapter import in ProCoder.
Have you divided the encoding by cells?

Anyway your app is great (and I use it always, even for my backups done with DVD-RB)

[Zeul]

robot1
yeah i split the vob into cells for encoding via avisynth (trim) then join them back again. same procedure for cce basic and quenc.
I am also adding some functionality for ReBuilder users :D

[robot1]

Perfect.
:)

[robot1]

I've done a couple of tests of NuMenu4U with ProCoder.
Results are perfect - great job.
Anyway, I've a suggestion/request.
I always use NuMenu4U in OPV mode, and probably it's the best way to use with ProCoder.
ProCoder 2 has a sort of OPV mode (CQ mode in ProCoder), with a different scale from CCE (0.00-1.00, 1.00 is the best value)
In ECLPro I take the Q_factor from CCE and change in the scale of ProCoder... but results aren't so good:
values over 15 give really bad results.
Is it possible for you to show in the Q_Factor dropdown values from 1 to 19 (step 1) instead 10-100 (step 5) when the encoder is ProCoder?

If you need other details for ECLPro integration, feel free to PM me.

[Zeul]

robot1
How about a seperate dropdown for procoder exclusively? If procoder is selected then I will pass this value instead of the Q value if One Pass VBR is selected.

[robot1]

Yes, fine.
Keeping the interface simple is difficult with so many encoders!
;)