Log in

View Full Version : NuMenu4u RC2 Build 7


Pages : [1] 2 3

Zeul
11th October 2004, 23:22
I am pleased to announce the release of NuMenu4u RC2

Changelog:

Bug Fixes:
Fix to the Temp_Settings error
Change to the para.lst for when Vsrip is run more than once.
Removes the Vsconv error
scanfolderforfilecopy routine replaced
Due to a scripting error on my part the threshold from DIF4U was never passed into the app.
Correction to the SoftEncode registry fix - Please rerun.
Fix whereby scenarist 2.6 would never be called
Fix to minimze to system tray - would restore itself after authoring / pause for script verification

Changes:
Alteration to the contrast conversion from VOB file to the scirpt (It was impossible to have a contrast of 0& for selection / action highlights)
To coincide with the new generation of menus, the normal display is now taken from the SST file (sometimes now <> 0%)
Complete change to the conversion rule for subs
Change to the bit allocation to determine if VOB is letterboxed from the IFO
Alteration to the way the check boxes in the treeview responded
Lots of code cleanup and optimizing
New e-mail debug, I didn't like the previous one; Now have a normal install once again

Additions:
Added ability to save the setting to use original assets (requires the save box also being checked)
Added the option to force a re-run of scenarist scan, for when new versions are installed - under Scenarist Tab
Added an additional check for incorrect cell commands in the IO caused by original author error - Removes the cell command error in Scenarist on compile

http://www.numenu4u.com/NuMenu4u.exe
Zeul

Zenak
12th October 2004, 00:58
Thank you very much for all the work you continue to put into this :-)

Angelus
12th October 2004, 01:03
Thanks Zeul for your hard work! I'll take a look at this.

Zeul
12th October 2004, 01:35
A small potential bug has been found. Please re download, RC2 Build 2

http://www.numenu4u.com/NuMenu4u.exe

Zeul

wfn1
12th October 2004, 02:43
Great job Zeul as always! I was really looking forward to this release. I did not get to try the b2 yet but as soon as I saw b1 I decided to redo my project I had problems with before (placeholder already exists error in scenarist). I installed NM on top of the RC1b2 that I had been using and it gave me the same exact error as before, also I went into the debug and again experienced an old error where it just scans and zips up all the directories on my C: drive with log files. The log screen says that it needs to archive 37 files which sounds about right but still I ended up with a C: drive zip which has alot more than 37 files :/

Anyway, to make the long story short I just uninstalled the program completely and purged all related items in my registry and reinstalled it. Also, while I was usually calling NM from DIF4U I decided to go and run NM and have it call DIF4U after the menus are done. Voila! it worked, the menus re-encoded and compiled fine and DIF4U was launched with /NOMENUFILES (even though DIF4U still launched NM to redo the menu after I started the demux?).

So now I'm pretty much a happy camper like I stated earlier I have yet to try b2.

Could you tell us what you changed in b2 over b1?

Thanks a million!

Sn8kbordin
12th October 2004, 09:14
the link is bad. Is it supposed to be the same one as in your signature?

The one in the signature works.

Dvd@Best
12th October 2004, 11:21
This was a rls i was waiting for u , u made my day zeul.
Very good work and keep it coming.

Regards

Fenix
12th October 2004, 22:14
Originally posted by Angelus
Thanks Zeul for your hard work! I'll take a look at this.

Hi Zeul,

Great application you have created ;)

Unfortunatly this last version give us un error upon exiting :

Run Time error 339

Component 'MSWINSCK.OCX' or one of it's dependencies not correctly registered : a file is missing or invalid


What could be causing this? The RC1 was without this error.

Regards,

Fenix
FJorgeR

PS: Keep up the excelent work ;)

D3s7
13th October 2004, 01:55
Another user posted this same issue yet it seems to be specific to some machines and not others

could you please tell us
1) what OS / version you are running (XP SP2 for example)
2) check the size / version of the mswinsck.ocx file (in the system32 dir)
mine is listed as : 6.1.97.82 and is 122KB in size

3) Try to re-register this com... at a cmd prompt type
regsvr32 c:\windows\system32\mswinsck.ocx

then try to rerun numenu

report back w/ results

Thanks

D3s7

edit: I just tried a few things and it appears that if I rename that ocx I get the same error... my guess is either it's not there for you OR there's an old version... i know both Zeul and myself are on Windows XP Service Pack 2

mvfarmer
13th October 2004, 07:21
I keep getting this error, i have tried reinstalling the program

Procedure Name: GetIFOParams
Module Name: NewCells

Error Number: 6
Error Description: Overflow
Error Source: Project1
Error Line: 0
Call Stack:
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
GetIFODetails --> ReplacementFile
StartNuMenu4u --> ExecuteProgram
go_Click --> MainForm

The log only shows this

13-10-2004 08:15:54 *Analysing IFOs

Any ideas?

Zeul
13th October 2004, 08:10
@mvfarmer
Please zip up all the ifo's and the logfile and send to me.

Turd_Ferguson
13th October 2004, 08:38
i'm getting the .ocx error message also. it pops up when i close nm4u. so i updated from XP pro SP1 to SP2. same problem. any ideas?

mvfarmer
13th October 2004, 09:16
Originally posted by Turd_Ferguson
i'm getting the .ocx error message also. it pops up when i close nm4u. so i updated from XP pro SP1 to SP2. same problem. any ideas?

I had that problem to, did this

3) Try to re-register this com... at a cmd prompt type
regsvr32 c:\windows\system32\mswinsck.ocx

Sn8kbordin
13th October 2004, 09:40
Originally posted by D3s7
Another user posted this same issue yet it seems to be specific to some machines and not others

could you please tell us
1) what OS / version you are running (XP SP2 for example)
2) check the size / version of the mswinsck.ocx file (in the system32 dir)
mine is listed as : 6.1.97.82 and is 122KB in size

3) Try to re-register this com... at a cmd prompt type
regsvr32 c:\windows\system32\mswinsck.ocx

then try to rerun numenu

report back w/ results

Thanks

D3s7

edit: I just tried a few things and it appears that if I rename that ocx I get the same error... my guess is either it's not there for you OR there's an old version... i know both Zeul and myself are on Windows XP Service Pack 2

I don't have that file and I get that error message when closing numenu4u. Also it doesn't save settings (CCE bitrate, and others) when I exit the numenu

Oh yeah: 1: Win XP SP2; 2&3: don't have that file

jel
13th October 2004, 11:15
when D3s7 said 'other user', he meant me :D
anyways...

machine 1: work pc - windows xp sp1
mswinsck.ocx was present but was an older version. updating (overwriting) with a newer version fixed all errors with NuMenu

machine 2: home pc - windows xp sp2
mswinsck.ocx was not present at all. installing in system folder rectified issues with errors upon closing program and debug window.

sorry zeul, i also received the error:
Procedure Name: GetIFOParams
Module Name: NewCells

Error Number: 6
Error Description: Overflow
Error Source: Project1
Error Line: 0

i wont send you the files as you already know this menu well :sly:

D3s7
13th October 2004, 15:41
Originally posted by Sn8kbordin
I don't have that file and I get that error message when closing numenu4u. Also it doesn't save settings (CCE bitrate, and others) when I exit the numenu

Oh yeah: 1: Win XP SP2; 2&3: don't have that file

well that's what we are saying.. you need that file in order not to get the error :)

probably why your settings aren't saved.. it's erroring out before it gets to save settings

Sn8kbordin
13th October 2004, 19:25
Will that file come with the numenu installer?

D3s7
13th October 2004, 19:32
Well... at the risk of stating the obvious, apparently not or we wouldn't be having this problem :)

Sn8kbordin
13th October 2004, 20:00
So should I wait for new release of numenu or find that file from somewhere?

D3s7
13th October 2004, 20:02
I'd say that's your call....

If it was me, I'd google that .ocx and see if you can find it

Sn8kbordin
13th October 2004, 20:42
I downloaded that file but now I get the same error as mvfarmer :(

Zeul
13th October 2004, 21:42
NuMenu4u RC2 Build 3 released

This corrects the Overflow error and installs/registers the MSWINSCK.OCX. I was under the impression that this file was pre-installed in the OS. My mistake.

Zeul

Fenix
13th October 2004, 22:07
Originally posted by D3s7
Another user posted this same issue yet it seems to be specific to some machines and not others

could you please tell us
1) what OS / version you are running (XP SP2 for example)
2) check the size / version of the mswinsck.ocx file (in the system32 dir)
mine is listed as : 6.1.97.82 and is 122KB in size

3) Try to re-register this com... at a cmd prompt type
regsvr32 c:\windows\system32\mswinsck.ocx

then try to rerun numenu

report back w/ results

Thanks

D3s7

edit: I just tried a few things and it appears that if I rename that ocx I get the same error... my guess is either it's not there for you OR there's an old version... i know both Zeul and myself are on Windows XP Service Pack 2


Yep you are right

I Have Windows XP Sp2 and the file is missing :(
Do you know why is it missing in some machines?

Regards,

FJorgeR.

PS:It's strange , the code really had some new changes because the other version didn't needed that ocx file.

Turd_Ferguson
13th October 2004, 22:26
good old google...
got the .ocx file and entered "regsvr32 c:\windows\system32\mswinsck.ocx" in the run box. Numenu4uRC2B2 works fine now.

however, it still has problems creating buttons for all the menus on my DVDs with several episodes on them. NM4M always makes everything else correctly, even the buttons on the menu for the first episode on the DVD. but the menus for the second episode and on have no buttons. i will try to send Zeul the ifo's and log.

Episodio1
13th October 2004, 23:11
I fixed the OCX error as posted above.

Ive still got the same OVERFLOW error with RC2 (builds 2 and 3).


_

Zeul
13th October 2004, 23:51
Episodio1
Not very helpful. Please be more specific, what is the error message that is thrown?

seewen
14th October 2004, 00:07
Same problem as the previous build:

NuMenu4u Rc2 b3 always load PREVIOUS movie path when it launch Scenarist.
All works well if I stay in front of the computer and modify the path in scenarist (set to "automatic import,build,close") after the "folder not found" error.

So if my 1st PATH is C:\1st_movie\, when I launch the 2nd (with the path C:\2nd_movie\), scenarist/numenu tries to open C:\1st_movie\script.SCP.

And with the 3rd movie (C:\3rd_Movie\), numenu/scenarist tries to open C:\2nd_movie\script.SCP. Etc..

(All those "previous" path doesn't exist anymore. I delete them before I launch NuMenu )
(NuMenu/Scenarist use the correct PATH to save the *.scn script)

Bye

seewen
14th October 2004, 00:13
And there is an other problem, that exist since a few builds.
(I already reported it once).

In "numenu"->"settings"->"Avisynth", I changed the "Processing Interlaced" to

TomsMoComp(-1,5,1)


Then in "numenu"->"settings"->"Avisynth" I check "Deinterlace Script". Then I launch the process (always from NuMenu4u, never from DIF4U)
But NuMenu (ALWAYS) use this script

LoadPlugin("C:\media\NuMenu4U\new.dvd2avi\mpeg2dec3dg.dll")
Mpeg2Source("M:\DAWN_OF_THE_DEAD\BIG3\D_VTS_01_0\FRAMESERVING\004.d2v" ,Idct=5)
LoadPlugin("C:\media\NuMenu4U\new.avs\decomb.dll")
FieldDeinterlace()
ConvertToYUY2(interlaced=true)


As you can see NuMenu4u makes 2 stranges things:
1) NuMenu4u doesn't use MY "Processing Interlaced" script. It use an HARDCODED one (beccause I replaced decomb/fielddeinterlace with Tomsmocomp).
Like I said, this bug exist since a long time.
(I don't have any instance of "FieldDeinterlace" in NuMenu settings. Not in any scripts. That's the proof NuMenu use HardCoded settings instead of "Process Interlaced" ones).

2) NuMenu4u use the footer "ConvertToYUY2(interlaced=true)". Which is the footer for interlaced material.
But as I said, I checked "Deinterlace Script". So the footer "footer (Progressive)" Should be used.


Bye

P.S.
(I modified the Header/Footer (deleted audio script), and NuMenu4u use the new values correctly)

Zeul
14th October 2004, 00:21
seewen
You say that movie1 is called into the scenarist path, when you are doing movie2. Are you sorta batch processing? Do you close nm4u before starting the 2nd movie?

seewen
14th October 2004, 00:21
And is it only me, or is it impossible to save settings with this new build ?

Everytime I restart NuMenu4u, all settings (but Avisynth's scripts) are lost.

D3s7
14th October 2004, 00:22
In regards your first of two posts, this is not a bug w/ numenu but a timing issue in automate_scenarist.... are you using Scenarist 3.0? - that is important to note

Originally posted by seewen
And there is an other problem, that exist since a few builds.
(I already reported it once).


Then there is no need to report it again... if you didn't see it in a list of "fixed" items and or specifically addressed.. once is enough anymore is just annoying


Like I said, this bug exist since a long time.


There is no reason to say this.. if it exists and you reported it once then that's enough.....

Try uninstalling and making sure you registry key is deleted.. then reinstall... as many other users have pointed out this sometimes resolves their problems that involve the registry..

seewen
14th October 2004, 00:24
Originally posted by Zeul
seewen
You say that movie1 is called into the scenarist path, when you are doing movie2. Are you sorta batch processing? Do you close nm4u before starting the 2nd movie?

No batch processing.

I close Numenu4u (and then all the DIF4U/Reauthorist/Scenarist process for the rest of the DVD) before starting 2nd movie

(Usually I make the next DVD 1/2 days later.)

seewen
14th October 2004, 00:28
Originally posted by D3s7 Then there is no need to report it again... if you didn't see it in a list of "fixed" items and or specifically addressed.. once is enough anymore is just annoying

Sorry. I thought maybe you didn't saw it when I posted it 1st time.



There is no reason to say this.. if it exists and you reported it once then that's enough.....

Re-Sorry.
I didn't mean to be inpolite. I just wanted to tell you, in case you missed it, that an other post, maybe longer/more complete, about this subject exist.


Try uninstalling and making sure you registry key is deleted.. then reinstall... as many other users have pointed out this sometimes resolves their problems that involve the registry..

I'm trying now.

D3s7
14th October 2004, 00:52
NP... sometimes we forget... sometimes we remember and just haven't got to it :)

I'm attempting to figure out why automate_scenarist has that timing issue... only seems to happen with Scenarist 3.0 too....

Episodio1
14th October 2004, 00:57
"Please be more specific, what is the error message that is thrown?"



Procedure Name: GetIFOParams
Module Name: NewCells

Error Number: 6
Error Description: Overflow
Error Source: Project1
Error Line: 0
Call Stack:
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
...
...
...



And it doesnt save my settings either.

_

wfn1
14th October 2004, 06:30
B3 does not save any of my settings even though the "Save settings" is checked in "Defaults"

Sn8kbordin
14th October 2004, 09:22
Originally posted by D3s7
Try uninstalling and making sure you registry key is deleted.. then reinstall... as many other users have pointed out this sometimes resolves their problems that involve the registry.. [/B]

How do I delete registry key made by numenu4u or what are they (in the registry)? Maybe this will help with the problem below

Also numenu B3 doesn't save settings and somehow the menu .m2v's made by CCE end up missing before Scenarist is importing the script.
WHen numeny tries to import script into Scenarist 2.6 it can't compile cuz of missing 65 .m2v's.

seewen
14th October 2004, 21:37
Yes I've forgotten to say that I have Scenarist 3.0 (3.0.0.96484).
(I've also WinXP SP2.)

I tried to delete the registry keys of Numenu (deleted quite all references to NuMenu4u with regedit) before reinstalling.
But it didn't solves the problems.

D3s7
14th October 2004, 21:41
yep... i'm working to resolve that problem w/ scenarist and should be posting a newer automate_scenarist laster tonight

Zeul discovered a slight problem that was causing settings not to be saved so everyone please bare w/ him till he finishes testing and a few other changes

seewen
14th October 2004, 22:04
There's a way to save settings:
- Set Numenu settings as you want
- Launch NuMenu (without closing it before, of course).

You don't need to wait till the process is complete. You can even close NuMenu4u with the task manager.

And the settings will be saved.

OmegaZero
15th October 2004, 06:56
Finding Nemo also brings this error with build 3:
(VTS01 encodes flawlessly, VTS09 is the problem here)


Procedure Name: Item
Module Name: VTS

Error Number: 9
Error Description: Subscript out of range
Error Source: ErrorHandler
Error Line: 5
Call Stack:
Item --> VTS
EnableDemuxing --> ExecuteProgram
DummyScan --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
NewCheckPalette --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
Compare_Codes --> Commands
Hex2Command --> Commands
Compare_Codes --> Commands
Hex2Command --> Commands
Hex2Command --> Commands
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
priv_LangCodeToLangName --> CLsDVD
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
ByteHandle --> GlobalFunctions
GetIFOParams --> NewCells
GetIFODetails --> ReplacementFile
StartNuMenu4u --> ExecuteProgram
go_Click --> MainForm

mvfarmer
15th October 2004, 09:44
Hi Zeul

Just want to tell you that the error i had whit Besweet is no more :)
It ran trough the dvd whit no problem.

Zeul
15th October 2004, 23:08
OmegaZero
Can i have the log. Use the debug screen - point to the working dir eg c:\nm4u\nemo, and let it zip up all the files i need.

The log and IFOs are the most important

thanks

Sn8kbordin
16th October 2004, 09:08
When trying to import script made b y numenu into Scenarist, it can't compile it cuz whatever CCE encoded (not everything but most) is not in "new_m2v" folder. That's with Star Wars IV A New Hope DVD

seewen
16th October 2004, 23:22
I just copied Van Helsing (Zone 2). And all went perfect.

The Menu is "Progressive" according to my eyes. But DVD2AVI (aka DGIndex) say it's "interlaced".
This happend really often with Zone 2 DVD.

So is their a way to tell NuMenu to use progressive settings, for CCE, even if DVD2AVi report interlaced ? (I know you can choose "verify script". But I mean automated).

I know there's a way to choose Scan = Zig-Zag (choose "field order"=TFF). But I think their's nothing to do the same for "progressive frame flag"

OmegaZero
17th October 2004, 01:10
Originally posted by Zeul
OmegaZero
Can i have the log. Use the debug screen - point to the working dir eg c:\nm4u\nemo, and let it zip up all the files i need.

The log and IFOs are the most important

thanks

Alright. I'll try running it again on Finding Nemo as well as some other movies that have huge Menu's that I've always had issues with earlier.

*EDIT: Sent you the zip Zeul*

Sn8kbordin
18th October 2004, 05:42
I tried backing up "Walking Tall" today, and I had these Scenarist errors from doing the menu by numenu RC3
Info
Info Creating DVD Files
Error No.4 pre-command error at PGC"VID_en_P_4", "VideoManager" (JumpSS or CallSS destination is Angle Menu PGC, but it does not exist)
Error No.6 pre-command error at PGC"VID_en_P_4", "VideoManager" (JumpSS or CallSS destination is Angle Menu PGC, but it does not exist)
Error No.7 pre-command error at PGC"VID_en_P_4", "VideoManager" (JumpSS or CallSS destination is Angle Menu PGC, but it does not exist)
Error No.9 pre-command error at PGC"VID_en_P_4", "VideoManager" (JumpSS or CallSS destination is Root Menu PGC, but it does not exist)
Error No.1 pre-command error at PGC"VID_en_P_8", "VideoManager" (JumpSS or CallSS destination is Angle Menu PGC, but it does not exist)
Error PreCheck From DB failed
Error DVD files could not be created

Whats seems to be wrong here or what can I do to compile the menu?

D3s7
18th October 2004, 16:17
I would suggest using the debug utility that Zeul added into numenu which will send him all the info he needs to troubleshoot the problem

Zeul
18th October 2004, 17:56
Sn8kbordin
I need the files ASAP, I have a rls pending.

Sn8kbordin
18th October 2004, 20:28
Originally posted by Zeul
Sn8kbordin
I need the files ASAP, I have a rls pending.

I tired using debug thingy, but it said max file sizew exceeded and the zip file just had all the .txt files from my C: drive and none from the DVD i was working on. What files do you need?