NuMenu4U bug

[PurpleMan]

Using latest version, when numenu4u starts encoding, all the
jobs (except for stills) on the ECL queue are 240 frames, and not their actual length.

Anyone experienced that?

[Zeul]

really
not found this myself. can you send me the relevant files as usual to investigate.
thanks

[PurpleMan]

Which files would those be?

worth mentioning - this only happens with DIF 1.4.7 (vip version)
and not with the public 1.4.0.

NuMenu4U basically creates an .ECL in which it sets

frame_last=240
and
encode_last=240

In the "waiting for you to check the AVS scripts, click OK to start encoding" thingie, I just have to edit the .ecl myself and enter the correct number of frames by opening the avs's and checking.

Best Regards,
PurpleMan

[Zeul]

i need the entire frameserving folder, vob file from the subtitle folder and ALL the ifos (all this is in the sticky)
Very strange how the dif4u version has a bearing.

[PurpleMan]

I have found that the bug happens only if I open the avs editor and remove the FieldDeintlerace() line from the NTSC processing.

Best regards,
PurpleMan.

[D3s7]

my guess is then the AVS's are incorrect and the length it's seeing is the "invalid avs" error message

try playing one of your AVS's and see if you get that message

[PurpleMan]

the avs's are fine. removing fielddeinterlace does not change the number of frames or the framerate.

the avs's open great in vdub
and it's only a coincidance that it only encodes the first 240 frames and that avisynth script errors produce 240 frames.

I double-checked.

[Zeul]

@purpleman
Still waiting for those files...

[wmansir]

Hey, I'm bumping this old thread because I encountered the same bug. The .avs are fine, but all the .ecl scripts are limited to encoding 240 frames.

I'm using NuMenu directly, version 2.0.19.

I can send you the files if you still need them Zeul. Judging from the log NuMenu is getting the Avs Error message (240 frames, 24fps) instead of the video it should, with certian scripts.

A little trial and error shows it only happens when the Decomb plugin is loaded, but not called. However, when I open any of these .avs files myself they work fine.

WORKS:
import("C:\Program Files\NuMenu4U\new.avs\addaudio.avs")
LoadPlugin("C:\Program Files\NuMenu4U\new.dvd2avi\mpeg2dec3dg.dll")
Mpeg2Source("E:\CHASEAMY\D_VTS_05_0\FRAMESERVING\001.d2v" ,Idct=0)
LoadPlugin("C:\Program Files\NuMenu4U\new.avs\decomb.dll")
FieldDeinterlace()
AddAudio()
ConvertToYUY2()
#Completed - DO NOT ALTER THIS LINE!!!!!!


DOESN'T WORK:
import("C:\Program Files\NuMenu4U\new.avs\addaudio.avs")
LoadPlugin("C:\Program Files\NuMenu4U\new.dvd2avi\mpeg2dec3dg.dll")
Mpeg2Source("E:\CHASEAMY2\D_VTS_05_0\FRAMESERVING\001.d2v" ,Idct=0)
LoadPlugin("C:\Program Files\NuMenu4U\new.avs\decomb.dll")

AddAudio()
ConvertToYUY2(interlaced=true)
#Completed - DO NOT ALTER THIS LINE!!!!!!


DOESN"T WORK:
import("C:\Program Files\NuMenu4U\new.avs\addaudio.avs")
LoadPlugin("C:\Program Files\NuMenu4U\new.dvd2avi\mpeg2dec3dg.dll")
Mpeg2Source("E:\CHASEAMY3\D_VTS_05_0\FRAMESERVING\001.d2v" ,Idct=0)
LoadPlugin("C:\Program Files\NuMenu4U\new.avs\decomb.dll")
#FieldDeinterlace()
AddAudio()
ConvertToYUY2()
#Completed - DO NOT ALTER THIS LINE!!!!!!


WORKS:
import("C:\Program Files\NuMenu4U\new.avs\addaudio.avs")
LoadPlugin("C:\Program Files\NuMenu4U\new.dvd2avi\mpeg2dec3dg.dll")
Mpeg2Source("E:\CHASEAMY4\D_VTS_05_0\FRAMESERVING\001.d2v" ,Idct=0)

AddAudio()
ConvertToYUY2(interlaced=true)
#Completed - DO NOT ALTER THIS LINE!!!!!!

[Zeul]

Strange
At no point in my code do i remove the fielddeinterlace() part of the script. If this has been manually removed then decomb should be commented out also. I guess i should put a check in the code to not write decomb if fielddinterlace() is not present. My concern with this is that if another deinterlacer was being used then decomb would still be needed, but the parser would then comment out decomb.

[wmansir]

I'm not sure how you load and check the video, but I should clarify that I changed these scripts in the Avs Script editor in NuMenu. The first one is the default NTSC/Interlaced script, the second I just deleted the FD() line, the third I commented it out, and in the final one I deleted it and the LoadPlugin line too (so the NTSC/Interlaced box was empty).

I didn't touch any of the scripts manually, and didn't have 'pause for script verification' activated either.

[Zeul]

I'm not sure we are on the same wavelength here. If you altered the avs scripts and thereby created a corrupt avs in the editor, i wouldn't class that as a numenu bug, more user error ;) If i understand you correctly using the scripts provided by numenu doesn't result in an error.
As i said earlier i can perform a sanity check for decomb/fd combination

[wmansir]

I did alter the scripts from the NuMenu defaults in the NuMenu avs editor, but the scripts are not corrupt. The .avs videos can be opened in Vdub, CCE, ProCoder, etc. The problem is that the .ecl files are not created by NuMenu with the right properties for the video, so they are not encoded correctly.

Perhaps the miscommunication is because I don't know how NuMenu gets the frame count/framerate/etc from the .avs videos. I assumed NuMenu created the .avs scripts and then opened them much like a media player and retrieved the properties. In that case the bug is that the scripts are valid, but for some reason when NuMenu opens them they result in an avs video error message and NuMenu records the error message's properties (240 frames, 24fps) instead of the real video properties.

[Zeul]

ok i replicated the problem
The avs file is read with avifileproperties - this returns 240frames / 24fps
The properties given result in the cce params.
Not sure how to correct this. i can check for the error params ok, but then what? Issue an error msg, revert to a "default in case of error script".??

edit: In fact i will do exactly that, revert back to the original avs scripts. That may mean that an asset that was interlaced being encoded as progressive and ivtc not being used - but that is better than the errors you have found.

[Zeul]

ok done that works - if avifineinfo returns 240f and 24fps then the default script is written over the avs file, and avifileinfo rerun to determine the fps and framecount. The default script will stay

[Zeul]

On further analysis the cause was that the avs scripts are not finished when avifileinfo is called. ConvertToYUY2 and addaudio() is added later. This is going to require a change of procedure. grrr

edit:
Rewrote the routines and all works fine now. On further thinking i realised i was checking for a return of 24fps also, so it is possible that some ntsc stuff was coded as 23.976 when it shouldn't have been.