NuMenu4u.2.0.25

[TuRiSOft]

Originally posted by Zeul
@TuRiSOft
If the problem persists with the new muxman build (14e) then please send me the log file.

The problem persists , log file sent!!!

[mvfarmer]

I use DVDdecrypter 3.5.4.0, newest version.

Indstalled PGCdemux like you said, and opend the files from VIDEO_TS, istead of the iso,
The log said Demuxing whit PGCDemux, so that part was ok, but it's the same thing, it's like the file it tries to open is not there :(

Do you want the new files sent?, probably the same as the first.


Just tried playing the menu in power dvd, and it seems to play right, but still... it's not good to have an error come up in the middle of the process :)

[Zeul]

@mvfarmer
this seems a bit unorothodox, but, can you open the original vob file in vobedit and check that cells with vobid >255 exist

[mvfarmer]

ok, here goes.... (not good whit this program :) )
i open VTS_01_0.VOB (Menu) in vobedit.
On the left side there is a long list,

192572 [Navigation Pack] [VOB: 37] [CELL: 1], 0012
192573 [Video Pack] [GOP] [I], 07ec
192574 [Video Pack], 07ec
192575 [Video Pack], 07ec
192576 [Video Pack], 017e
this is the last 5 lines on the left side.

Is this the one you mean?:
192572 [Navigation Pack] [VOB: 37] [CELL: 1], 0012

because then i don't think there is more then 255 of them

addet a snapshot

don't no if the attachment worked, here is a link to the image
http://biology.au.dk/~biomv/vobedit.gif

[Zeul]

this is strange. according to the ifo there are 549

[influenza]

have been trying the latest numenu with muxman and I must say that it works really well. Much faster and less error prone than with scenarist. Nice work :)

[mpucoder]

VobID can be as great as 32767.

[Oruku Saki]

@Zeul - You were right about dif4u - I upgraded to 1.4.7 and have had no problems with cce passes since

[Sjõbbe]

It works fine with win 2003 now.
Sry if Im late. =)

[gemon]

@zeul about single pass
zeul, if u remember it is the same problem i told u in the 'the incredibles' thread (apart from the other difficulties of this specific dvdr)

looking forward to try your new build to see if this solves anything :)

Gemon

[Master Yoda]

I just done the menu for layer cake which is 16.9 but the new menu created is 4.3.

Im using the latest numenu

[Zeul]

can you send me the original IFO , new IFO and logfile please.
I suspect that the menu is encoded at 4:3 pan-scan, but the original is 16:9
Need to find out why
Thanks

[Master Yoda]

Well i deleted it, but i'll run it again so i can get the ifo thats created from numenu and i'll send you it along with the original.

[TuRiSOft]

Hey Zeul , any chanche we can use HC with your app?

I'm continuing to have troubles on using MuxMan as Muxing app. I must use Scenarist instead and I'd like to use all freeware applications!!!


Bye and Thanks!!!!

[Zeul]

I am looking into HC as we speak. What issues are you having with muxman?

[TuRiSOft]

If I use muxman for authoring I never get a working title. I tried to open MuxMan authored titles in PGCEdit and it gives me an error. Sometimes Numenu pops up an error just after the remuxing phase (when adding back the command infos to the VOB) . I'm using 2.0.11 with 0.14e.

[Zeul]

can you send me the log, original ifo & authored ifo

[Zeul]

Master Yoda
The menu is indeed 4:3 pan-scan according to the IFO. If you drop the original mpv into scenarist it should report 4:3 pan-scan. If you drop the new mpv in 4:3 pan-scan should also show.
Please advise.

[Master Yoda]

I never actually check the ifo i check, i just opened the menu vob in dvd2avidg.exe and that showed up the video footage ar as 16.9 and so did bitrate veiwer, but the newly encoded footage ar is 4.3

[Zeul]

I take it all the buttons are misaligned then. What concerns me here, is that the IFO definately suggests a 4:3 with pan-scan encode. This is the normal. To clarify:
If the IFO says 16:9 with automatic display to pan-scan, then the video is actually encoded as 4:3 pan-scan flag enabled.
If the IFO saya 16:9 with automatic display to letter, then the video is a true 16:9 aspect.
The only other variation is if the IFO says 16:9 and both pan-scan and letter are flagged. This suggests a 16:9 pan-scan encode.

This i believe is only the 2nd time a post like this has been reported, so...
Either the IFO is incorrect/badly authored OR my understanding is off. BTW D3s7 uses the same principles for scenaid.

As dvd2avi doesn't show the pan-scan flag, please as I asked earlier drop the original into scenarist and post what it says.

Mpucoder if you read this perhaps you can confirm or deny.
Thanks

edit:
Just tried every combo in scenarist.
a 4:3 pan-scan encode with displaymode set pan & letter gives an IFO with AR=16.9 and pan flag & letter flag set
a 4:3 pan-scan encode with displaymode set to pan only gives an IFO with AR=16:9 and pan flag only set
a 16:9 encode (with or w/out pan flag) with displaymode of letter (only available choice) gives an IFO with AR=16:9 and letter flag set

SO..
with you IFO the video is 4:3 pan-scan encoded OR the IFO is fubar

[TuRiSOft]

Here are all errors I get after authoring with MuxMan and chek with PgcEdit or IfoEdit :

http://imagecash.servepics.com/preview/43741.jpg (http://imagecash.servepics.com/view.php?file=43741&owner=TuRiSOft)
http://imagecash.servepics.com/preview/43743.jpg (http://imagecash.servepics.com/view.php?file=43743&owner=TuRiSOft)
http://imagecash.servepics.com/preview/43745.jpg (http://imagecash.servepics.com/view.php?file=43745&owner=TuRiSOft)
http://imagecash.servepics.com/preview/43747.jpg (http://imagecash.servepics.com/view.php?file=43747&owner=TuRiSOft)
http://imagecash.servepics.com/preview/43749.jpg (http://imagecash.servepics.com/view.php?file=43749&owner=TuRiSOft)
http://imagecash.servepics.com/preview/43758.jpg (http://imagecash.servepics.com/view.php?file=43758&owner=TuRiSOft)

@Zeul
Log , authored and original IFO in your mailbox!!!

[mpucoder]

@Zeul - correct, panscan video should show 4:3 DAR, and have panscan headers. I'd like a copy of the authored ifo, too.

[Zeul]

@mpucoder
Out of interest what will the standalone do when the actual video doesn't match what the IFO says, which appears to be Master Yoda's problem?

@Turisoft
I can see the problem with the files you sent me, NuMenu didn't update the video_ts.ifo correctly. This is the reason for the errors

@Master Yoda
Have you done as suggested?

[Master Yoda]

I check the ifo and it says 16:9 (pan & scan) but i have'nt done as suggested yet, have'nt had the chance.

UPDATE...

I just dropped the first original m2v's from the menu into data in scenarist,i click on the file up in the top section and then at the bottom centre of the screen it says..

Encode Type MPEG2
Size 720 x 576
Aspect Ratio 16:9

If i then dropped the same file but the new encode from numenu the aspect ratio changes to say 4:3(pan-scan)

[TuRiSOft]

Originally posted by Zeul
@Turisoft
I can see the problem with the files you sent me, NuMenu didn't update the video_ts.ifo correctly. This is the reason for the errors

And now what can I do ? Is it happening only to me ? And if so what is the reason why?

[mpucoder]

@Master Yoda and Zeul: To many authoring programs 16:9 and 4:3(panscan) are equivalent (MuxMan included). Both are anamorphic. The difference is the 4:3(panscan) file contains the proper headers for panscan. Without the headers the player will show the horizontally centered 540 pixels per line. Players use the ifo values, as mpeg-2, at the time DVD was developed, did not support multiple AR or display modes (mpeg-2 has since been extended to support multiple display windows). Changing 16:9 to 4:3(panscan) is a simple matter of adding some headers and changing the DAR, no encoding is needed.

[Zeul]

@Turisoft
I am in the process of determinimg the cause of the update error. You also processed VTS_03, the ifo which was correctly updated. So for the moment either only do VTS_03 or put the project on hold for a couple of days until I fix the problem. NB If you use Scenarist the updating is different so the problem will go away.

@Mpucoder
Thanks for the clear explanation. So it seems that Master Yodas IFO is correct. Which leaves the question. If 4:3PS and 16:9 can both be shown in the IFO as AR 16:9 with pan flag set, then I cannot use the IFO as the source information. This means additional parsing of the actual m2v is going to be needed to get the actual encode method (4:3 pan or 16:9) :rolleyes:

[TuRiSOft]

Originally posted by Zeul
@Turisoft
I am in the process of determinimg the cause of the update error. You also processed VTS_03, the ifo which was correctly updated. So for the moment either only do VTS_03 or put the project on hold for a couple of days until I fix the problem. NB If you use Scenarist the updating is different so the problem will go away.

I was suspecting this , but I've not tried to uncheck video_TS.VOB re-encode. I will try it later.

[EnDeR_PL]

why when i encoding menu i can only set animation bitrate, but static menu always have 7500b.

[Zeul]

Because a still encodes very poorly with less than 7500. I may actually increase this level, as CCE still gives slightly blocky encodes. There is absolutely no point in VBR for a still - there is only 1 frame.

[k-c-ksum]

its as if some of the m2v files havent been encoded. Scenarist sets them as place holders. Any ideas?

[Zeul]

what were you using for encoding? Any errors thrown during encoding? Send me the log.

[TuRiSOft]

@Zeul

Any news about issues I told you (VIDEO_TS.IFO incorrect when using MuxMan for Re-Muxing)?
I can confirm there is no problem using Scenarist on the same title (neither using MuxMan and deselecting VIDEO_TS from the list of VTSs to reauthor)!!!
Can this issue be related to the kind of encoding I use (CCE OPV , Q=30 , Avisynth filters added to the script : UNDOT () - DEEN () - MipSmooth (preset="movieHQ") ) ?

[Zeul]

@Turisoft
There was a serious problem with the IFO generator for Video_ts.ifo if some of the tables didn't exist in the original. This has now been corrected and a fix is due any day.

[k-c-ksum]

Originally posted by k-c-ksum
its as if some of the m2v files havent been encoded. Scenarist sets them as place holders. Any ideas?


must have been somthing running in the background.

Logged off closed down virus soft/firewalls etc and tried again. Worked like a charm. The DVD in question was The Simpsons s5 disk1.

[Zeul]

What is the ecl threshold (under encoder tab), its possible there were too many files being loaded into CCE. Try lowering the number of assets to encode in the ecl.

[Zeul]

Updated build to 2.0.12

[TuRiSOft]

I can confirm : NOW IT WORKS !!!

[Zeul]

:D

[TJeR]

Thanks for fixing this ODD poblem with subs in the last release ;)

1 request a couple of version ago there was a feature to preeview vob's content and eventually stripp unneeded, is it possiblie o have this function back for scenerist user to?

thanks again

[D3s7]

that feature has been there for a long time now..

[TJeR]

Uhmm... Ok... now I see it...under VIP area, if the author thinks it should be avalaible for VIPS only it is perfect to me to...

Regards

[Zeul]

New build released 2.0.13

[MaDxCrEaM]

Having a problem trying to use Quenc. I have no problems using CCE. I get this error with Quenc when it tries to start it:

Procedure Name: AddTrim
Module Name: ExecuteProgram

Error Number: 53
Error Description: File not found
Error Source: Project1
Error Line: 7
Call Stack:
AddTrim --> ExecuteProgram
EnableQuenc --> ExecuteProgram
EnableVideoEncoding --> ExecuteProgram
StartNuMenu4u --> ExecuteProgram
go_Click --> MainForm

I seem to see no one else having any problems, so not sure what is different from using CCE than Quenc. I point it to where Quenc is just like I do with CCE. Thanks for any help.

[Zeul]

That suggests it couldn't open the AVS file.
Can you send me the frameserving folder & the NuMenu4u.log

[MaDxCrEaM]

Just curious if you got my email attachment okay second time around Zeul? Thanks.

[Zeul]

all received, and am checking now

[MaDxCrEaM]

Thanks for your time Zeul. It is working perfect now.

[MaDxCrEaM]

@Zeul, hey I also tried ProCoder 2 version 2.04.02.00 and am getting some errors. It encodes fine, but during the encode; seems to be maybe the short segments; procoder pops up and says that the temp file it is trying to write already exists. All I do is wait like 5 seconds, keep the same name then it's fine. Not sure if it's all happening too fast and the temp file isn't getting deleted fast enough (if it gets deleted or renamed as I am not sure what it does). I never tried any earlier version of procoder 2.

[Zeul]

The temp file is created by eclpro - what version are you using?