HD encoding issues

[Dogway]

My post in another thread went absolutly ignored, and although it might be a simple question I thought it was important to other people as well.

My source is 1080 24p, and when I try to encode for Bluray compliant I get a libgfl201.dll error. In x264CLI and Megui both. It doesnt cancel anything and continue encoding but as 12/1fps 1920x2160i.

-Do I need to install any special version of x264?

-And a totally different question, are there important flags I must take special care when encoding non-compliant HD (as opposed to SD) ?

[Biggiesized]

What's your command line?

[Inspector.Gadget]

MeGUI, x264, Avisynth, and at least the most common Avisynth plugins do not depend at all on that DLL (I don't even have the DLL on my system). You have some other problem on your PC and I would bet on it being related to malware.

[Dogway]

It's not much about the command line, because the Megui BD profile does the same. I dont know if its malware, I have AVG Free and oftenly run Trojan Remover.

PD: I just passed ComboFix and everything is the same. So if it's a trojan I dont know what else to do, if else I ask you guys.

[Inspector.Gadget]

Post the full text of the error message here. You can get it by using Ctrl+C when the error message window is active (in focus).

[Dogway]

oh good tip.

---------------------------
x264-1745.exe - No se puede encontrar el componente
---------------------------
Error al iniciar la aplicación porque no se encontró libgfl201.dll. La reinstalación de la aplicación puede solucionar el problema.
---------------------------
Aceptar
---------------------------

its spanish : /
Well it basically says:
x264-1745.exe - couldn't find the component.
error on application run due to unfound libgfl201.dll. Resetup of the application can solve the problem.

I tried with my old x264-1570.exe and a new 1745 build too.

This is my script:
ImageReader("C:\Master PNG %04d.png", start=1748, end=1800, fps=30)
converttoyv12
SMDegrain(tr=3, thSAD=200,blksize=4,overlap=2)
GradFun2DBmod(thr=2.5,thrC=1.2,str=1.2,strC=0.0,radius=3,range=3,mode=3,temp=0,mask=false)
TDecimate(cycleR=1)

And this is my bat:
x264-1745.exe --bitrate 20000 --preset veryslow --tune film --fps 24000/1001 --weightp 0 --bframes 3 --nal-hrd vbr --vbv-maxrate 40000 --vbv-bufsize 30000 --level 4.1 --subme 9 --trellis 1 --merange 28 --keyint 24 --b-pyramid strict --slices 4 --aud --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --no-mbtree --sar 1:1 --pass 2 -o "outfile.264" "01.avs"

But it happens in Megui BD default profile too, always at the start of every pass.

Anyhow it finishes encoding, but if I resize my script to SD, is ok, if I leave it HD it detects it interlaced.

[Inspector.Gadget]

Unregister the dll by finding all entries listing libgfl201.dll in the registry and then using regsvr -u libgfl201.dll from the command line in the directory it is supposed to reside in. If you're on a 64-bit system using x264 32-bits, you will need to use regsvr32 instead.

I still believe that you have malware or are suffering from bad registry entries from a previous infection.

[Dogway]

I will try that and some testings with regular encodings too.

ComboFix is supposed to be one of the strongest malware removals, and barely found nothing. Even it's not 2 months since I reformatted the system. Let's do some checkings.

PD: No libgfl201.dll on registry.

[Inspector.Gadget]

Who's x264 build are you using? Try using the latest from MeGUI autoupdate. The other possibility is that somebody is linking those builds you use currently to an oddly named dll.

[Dogway]

I always dl them from x264.nl (I think its named).

It looks like normal (non compliant sources) also detects it and SD (old projects) too.

It mostly looks like malware as you said... lets see what can I find for it surfing the net, at the cost of getting more malware : /

PD: Non the less, it finishes the encoding. So any tip for the other 2 questions?

[Sharktooth]

use the x264 build that comes with megui.
the latest 1745 is included in the development version, so switch to that in the options and let megui auto-update.

[Dogway]

Its the same, I chosed the 1080p24 profile and it still encodes 12/1fps 1920x2160i.

[Inspector.Gadget]

Hmmm...on the subject of Malware, have you ever had SUPER installed?

[poisondeathray]

if your source is 24p , why do you use fps=30 for the imagereader source filter, then use tdecimate later?

when you preview your avs script, add info() to the end, and what does it report for the fps and dimensions ?

what if you feed that avs script to a different encoder, e.g. xvid encraw in megui , or xvid vfw in vdub ?

[Dogway]

xvid on megui, no problem. Although it warns me about 1080 not being mod16 (that might be the cause with x264?)
info() report is good too.

my source is 30fps, and Im doing dirty converting it to 24 this way. I will try to avoid other routines (motion compensation) which produces artifacts.

@Inspector.Gadget: Yes I had it before.

[Inspector.Gadget]

Yes I had it before.

SUPER has (predictably) messed up your Avisynth installation and probably left your registry littered with crap. This has been known behavior from SUPER for at least a year. Check whether re-installing Avisynth helps; also try uninstalling Avisynth and deleting the directory, deleting any registry entries that point to the plugin directory, and re-installing Avisynth. SUPER is also known to modify files in your System32 directory, so hopefully nothing there is permanently broken. You may need to re-install Windows. SUPER is malware.

[Dogway]

SUPER is malware.
That's why you never know... I installed it once when I had serious malware infection, but after solved I even deleted that software setup file. Never trusted it at all...

I reinstalled avisynth a few days back (the error was already present) so I will try to do some heavy reinstall by tomorrow. If you think that might be the cause for the interlacing encoding mess.

[Dogway]

-The trigger for the libgfl201.dll error was the importuncompressedfile.dll filter, which I will use to export to png files from cineon.
-Yes, I have 3 filters that switch encoding the expected 24p to 12i. Seesaw, dfttestMC and Exblend. Edit: They were activating mt_masktools-26.dll which was the main guilt, because it's was made for 2.5.6. I deleted it and kept mt_masktools-25.dll. Now everything is fine.

@Inspector.Gadget: Thanks for the help in any case.

-Still Im curious about encoding non-compliant HD. Is it the same as SD, or do I need to set vbv flags or so? target is PC playback.

Autoanswer:
I ended up with this, good quality and wide compatibility
x264.exe --level 4.1 --preset veryslow --tune film --pass 2 --bitrate 5000 --deblock 1:0:0 --stats ".stats" --keyint 240 --min-keyint 24 --ref 9 --rc-lookahead 40 --vbv-bufsize 24000 --vbv-maxrate 24000 --output "output.mp4" "source.avs"

[nm]

-Still Im curious about encoding non-compliant HD. Is it the same as SD, or do I need to set vbv flags or so? target is PC playback.

If you are only targeting software decoders on multi-core machines, there's no need to set VBV or anything special.

But what if you decide one day that it would be nice to use the hardware decoder in your GPU for energy-efficient playback? Depending on the GPU model, you could have problems in some sequences without L4.1-compliant VBV settings.

[Dogway]

OK it wasn't mt_masktools-26.dll alone it seems, as I stated Seesaw, dfttestMC and Exblend were also guilty, as for Exblend it's a plugin, so it is by itself the reason, for Seesaw I had added some extra lines to help myself understand better the parameters, I tried deleting them, and Seesaw didnt give further problems, then I tried to delete some commented lines as well on dfttestMC (http://forum.doom9.org/showthread.php?p=1295788#post1295788) and it didnt work. Does someone has any clue what's happening between autoloading .avsi's structure and x264?