NuMenu4u.RC3.Build.1

[Zeul]

New Release:

Enhancements:

Added ability to add silence to audio streams, so that they equal video length; required for seamless cells (Audio Tab)
Complete new Automate_Scenarist from myself and D3s7, which includes a visible LOG file.
To enable the showing of the LOG in Automate see the new option in Scenarist Tab


Bug Fixes:

On one occasion there was an overflow in the IFO creation - corrected
Some PGCs were mistakenly labelled as Dummy, so no cells created in Scenarist Layout - corrected
Finally found the bug that was causing pulldown to not be run (very occasionally). Reason - spaces in the folder names, code altered to reflect this.

download Numenu4u and Automate bundle:

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

Zeul

[Zeul]

Accidently uploaded the wrong build of automate. Please redownload.

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

[eriksen76]

Fantastic work Zeul, just tested the latest build and the new Automate_Scenarist which works perfectly for me. As you might remember I had tons of probs which is now solved.

It compiles, closes and continues with numenu, then finishing.

Good job

/Julius

[Pike007]

I agree, excellent work. I was having problems with Automate_Scenarist hanging after import, but works without a problem now. Very nice.

[Zeul]

:)

[fdnyems]

Zeul,
Great gob to the new release of numenu4u. I'm having a weird problem that I wonder if you can help me with though. I was having a problem on my one comp where it was giving me problems importing,compiling, and closing. Thanks to your new release it works beautiful with no problem. But on my second computer I keep getting and error message that pops up saying Scenarist "Not exist restore directory ()" with a box that your supposed to click ok on. I did everything the same in installing as the other one on my other computer with no problems to report. I wonder if I missed something along the way. Thanks in advance and again great job on the new version.

P.S. - After I push the Ok button twice for the error message I gave above it bring me to another error messase saying : Unable to resolve BUTTON "Error-Unable to resolve ok button, press ok button; then ok to proceed". After I push the ok button I get the Scenarist screen in which where it takes me to the create new scenario from script screen.

[D3s7]

Your using Scenarist 3.0 I'd bet

try this: make sure you don't have any cd's in your cdrom drives when starting the import

we've noticed a timing problem that scenarist 3.0 scans your cdroms when you click the "import" button - if it has to spin them up, there's a HUGE delay.... we thought we had a work around but apparently not 100%

your other option is to manually find the script and put in a scenario name then click the "ok" on import and "ok" on automate

it should proceed as normal then

[fdnyems]

D3s7,
I noticed the same problem going on now with my other computer too now wiht the same problem mentioned above. I'm wondering since I am using daemon tools to use my .iso file with doitfast4u if in numenu4u when it's trying to go into the root directory maybe that's why i am getting the problems. I'll try and switch it from root directory to my documents and see if I still get the same reaction.

[D3s7]

I've only seen the issue come up when you have a cd/dvd in a real drive..... however i guess daemon tools could be doing something wierd.. please let us know yoru findings

[fdnyems]

This is the info that I am getting :

* Scenarist Version in use : 3.0
* Scenartist Path is : C:\Program Files...etc
* Searching project manager window
* Project Manager window found; Handle = 18088626
* Pressing IMPORT button
* Searching for Creat New Scenario from Script window
* Create New Scenario From Script window found; Handle = 18154162
* Script file sucessfully added
* ScenarioFile successfully added
* Ready to activate Scenarist import
* Importing

This is when I come up with the error messages :

1. Scenarist "Not exist restore directory ()"
2. Unable to resolve BUTTON "Error-Unable to resolve ok button, press ok button; then ok to proceed".

I think I found the problem with it though. For some reason when inforting the script it is looking in the old folder instead of the new one for example :

I backed up a copy of my Walking Tall, when I tried to do a backup of my Remember The Titans in the "Create New Scenario From Script" window is shows me that it's looking for the script file in "D:\Walking_Tall" where I did that backup at but it's putting the "Scenario File" in the write spot where it is supposed to be "D:\Remember_The_Titans\Batch1\ScenaristScript30_1.scn".

That's why i'm getting the error message because when I point the "Create New Scenario From Script" to it's propoer position "D:\Remember_The_Titans\Batch1\ScenaristScript30_1" it works perfectly.

I don't know why it's looking in the old directory instead of the new one.

[D3s7]

Well it's not.. it's a common misunderstanding is that it's looking in the "wrong" directory..

The problem is, Scenarist remembers the last directory used.. which is why your seeing theimport dir from your last import..

Scenarist automate is attempting to fill that info out butfor some reason w/ Scenarist 3.0 there's that delay I was referring to which causes the wrong fields to fill out or no fields at all.. now why your seeing it I'm not sure...

What you could do to help us is open your task manager and watch the processes at the point automate clicks import and/or if you manually do it, some process is going to kick off for a second (or up to 30 ason my machine at times)... On mymachine it's IATAPI and while that's running scenarist hesitates... apparently it's something different on yourmachine..

it only appears to happen for me if I have a CD in the drive when I click the "Import" button on the main screen in scenarist...

[fdnyems]

So your saying if that delay dosen't happen with Scenarist version 2.7? It weird because I didn't have a disk in either of my drives either. but will see what I can try and find out to help you.

[D3s7]

correct.. the delay doesn't seem to happen in 2.x only 3.x

[FreaQ]

Great job Zeul.
I am testing the new build right now. It works great so far. But I am wondering, what happend to the function to resize the menus to half-d1?
Will it be integrated again or did you give it up?

Greetings FreaQ

[Zeul]

Resizing of the video should now be done via avisynth instead of using the internal CCE settings. The results will be much better. I never do it myself, but I would think something like:

LancosResize(360, 240) # could use this to go from 720*480

This is only a guess mind :D

[FreaQ]

I tried to resize the video with AviSynth.
In case that I am a PAL-User, I tried this one out:

Crop(8,0,-8,0)
BicubicResize(352,576,0,0.5)

Worked so far everytime on "normal" video.
When I use it with NuMenu the video will be resized, but Scenarist compiles it as 720*576. And so looks the menu wehen playing. I have tried to change the IFO. But nothing changed on playing. So i checked the VOBs. And there is the fault. The VOBs are all 720*576. And so I have big black borders left and right and the actual menu is 352*576.

[jarthel]

my mistake

[FreaQ]

Ok it was all my mistake. I messed it up, because the menus were interlaced. Doh! :rolleyes:

[abyss]

Great job, Zeul, thanks a lot for fixing problem with dummy files.

Still with the same movie (LOTR FotR SEE CD2) I've encountered with 2 another problems:

1. NM4U incorectly detects aspect ratio of demuxed menu videos, i.e. it always sets aspect ratio to 4:3 (Pan-scan) though there are some video clips with aspect ratio of 16:9. Due to this, Scenarist reports an error while importing script:

The aspect ratio of MPEG video file "***.m2v" has changed.

2. Why NM4U doesn't recreate First Play PGC commands and only puts there "JumpTT VTS1", though originally there were other commands in First Play PGC?

[eriksen76]

Originally posted by abyss
Great job, Zeul, thanks a lot for fixing problem with dummy files.

Still with the same movie (LOTR FotR SEE CD2) I've encountered with 2 another problems:

1. NM4U incorectly detects aspect ratio of demuxed menu videos, i.e. it always sets aspect ratio to 4:3 (Pan-scan) though there are some video clips with aspect ratio of 16:9. Due to this, Scenarist reports an error while importing script:

The aspect ratio of MPEG video file "***.m2v" has changed.

2. Why NM4U doesn't recreate First Play PGC commands and only puts there "JumpTT VTS1", though originally there were other commands in First Play PGC?

I did LOTR FOTR SEE with no errors at all. Both DVD1 and DVD2.

Actually I did not examine the final output in other ways but playback on my standalone. But I can't see any errors at all and its fully functional.

I had some bugs in the beginning caused by pre-processing (removing som non-needed commentaries menus). But doing the compression with no pre-processing at all it worked. Then I stripped afterwards.

EDIT: I just checked the compressed "VTS_01_0" (menu vob) and dvd2avi detects it as 4:3 (both dvd1 and dvd2). Haven't got the orginal movie any longer so I'm not able to see if this was the orginal aspect ratio. I only kept the chapter indexes so if you're having problems with the other menu's you might be right, but I can not confirm this.

I just checked the menus of Return Of The King as well, and the menus here are 4:3 as well.

But most important, it works like a charm, for me at least.

/Julius

[jel]

eriksen76
thankyou for your feedback but could you please edit your post to remove the rule vioaltion references. we do not discuss release groups in this forum.
thanks
j

[eriksen76]

I am very sorry about it, my mistake.

Message has been edited properly.

/Julius

[jel]

no worries mate.
thanks
j

[abyss]

Originally posted by eriksen76
I did LOTR FOTR SEE with no errors at all. Both DVD1 and DVD2.

Actually I did not examine the final output in other ways but playback on my standalone. But I can't see any errors at all and its fully functional.

I had some bugs in the beginning caused by pre-processing (removing som non-needed commentaries menus). But doing the compression with no pre-processing at all it worked. Then I stripped afterwards.

EDIT: I just checked the compressed "VTS_01_0" (menu vob) and dvd2avi detects it as 4:3 (both dvd1 and dvd2). Haven't got the orginal movie any longer so I'm not able to see if this was the orginal aspect ratio. I only kept the chapter indexes so if you're having problems with the other menu's you might be right, but I can not confirm this.

I just checked the menus of Return Of The King as well, and the menus here are 4:3 as well.

But most important, it works like a charm, for me at least.

/Julius

eriksen76, thank you for your reply. I find it strange too that only 2 clips have diferent aspect ratio (16:9), one of then in VIDEO_TS, another - in VTS_01_0. Maybe the reason is that I'm using Scandinavian DVD version... But anyway, for some reason NuMenu4U ignores different aspect ratio and forces Scenarist to import it as 4:3 (Pan-Scan), though DVD2AVI corectly recognise aspect ratio of those clips.

[eriksen76]

Originally posted by abyss
eriksen76, thank you for your reply. I find it strange too that only 2 clips have diferent aspect ratio (16:9), one of then in VIDEO_TS, another - in VTS_01_0. Maybe the reason is that I'm using Scandinavian DVD version... But anyway, for some reason NuMenu4U ignores different aspect ratio and forces Scenarist to import it as 4:3 (Pan-Scan), though DVD2AVI corectly recognise aspect ratio of those clips.

I haven't examined the video_ts file. And I only ran the whole vob through dvd2avi, so if it starts with showing 4:3 and a 16:9 part occours dvd2avi might not change it to this. I did not open the demuxed vobs, only the whole file.

I did the scandinavian version as well

Did it work for you or not? I might have the same "problem" as you then, but I did not see it.

Any way I can't see the big deal about it, it works nicely.

/Julius

[abyss]

No, DVD2AVI detects when part of the vob is in another aspect ratio and shows it when it happens. I also ran whole vob file and saw it. And yes, it's not a big problem, and it is not a matter of some particular DVD, I just tried to point out that NuMenu4U ignores different aspect ratio of some clips and forces them to be imported in Scenarist as 4:3 (Pan-Scan). And what about commands in First Play PGC? It doesn't mean that I cannot recreate them by myself. I'm just curious why this procedure was not implemented, when recreation of commands in other menu PGCs works like a charm...

[Zeul]

@abyss
The problem here with AR is that scenarist doesn't allow different aspect ratios in the same VTS (in fact this is a DVD specification), however, if the original is like this, then it was an original authoring error. If the asset was re-encoded then there will be no problems, however if the original was used (for example stills) then the error will occur. Now here is the difficulty I could force a re-encode of the affected assets BUT if there were subs / buttons then these *could* be affected. At present I can't think of a way around it, but I am open to offers. I suppose I could offer this as an option.

With regard to the First Play PGC , there is no point in recreating this - I don't touch this in the IFO. IF i were to recreate it, then potentially additional PGCs would need to be created, just increasing the import time. ie if the first play was NOT the root menu and a title PGC (like a trailer) then this PGC would have to be created to stop a compile error.

[abyss]

Zeul, thank you very much for clarifying situation. Yes, I was trying to use original assets and, as you said, it seems it was an original authoring error. Those videos do not contain buttons, they are just transition videos which are shown when you go from one menu to another. I didn't know about this DVD specification and requirement, and thought that this was a problem of NM4U and it should be pointed out. I don't think there is a necessity to make changes into program for such rare out of specs cases. Despite this error Scenarist has imported those video clips and regards them as 4:3 (Pan-Scan). But interesting thing was that Scenarist imported script successfully when in script I changed AR of those two video clips to correct values (16:9). Scenarist imported this script without any complaints. Maybe that could be a solution? I'm using Scenarist 3.0, don't know how in this situation behaves older Scenarist versions.

[Zeul]

After you changed the script did it compile without error?

[eriksen76]

I did not change anything, and I had a successful compile with version 2.7

/Julius

[abyss]

Originally posted by Zeul
After you changed the script did it compile without error?

No, Scenarist refuses to compile and complaints about this AR stuff... Sorry for not checking it out before posting. What if NM4U could warn user about this incompatibility in such cases if he selects no reencoding? Though anyway forcing to import video clips with different AR as having AR of 4:3 (Pan-Scan) works very well. Just I think that those errors in Scenarist may confuse other users as well. What do you think?

[morgensonne]

When i try to start NuMenuU i get 3 error messages:

#1: [title]vbalProg [message]Run-time error '11': division by zero
#2: [title]vbalProg [message]Run-time error '440': Automation error
#2: [title]NuMenu4u [message]Run-time error '440': Automation error

I installed the newest Build and have Windows Xp Prof. SP2. Can somebody help?

Ciao

[D3s7]

reinstall the visual basic runtime files (available on MS's website)

sounds like your missing something

[morgensonne]

okay i installed the Visual Basic Runtime Module Version 6.0 and the Service Pack 5 for Visual Basic BUT always get the same errors when trying to start the program.

[Zeul]

I assume you are trying to install the full package?
Have you tried reinstalling?

[Zeul]

thread closed.
Please see http://forum.doom9.org/showthread.php?s=&threadid=86243