Problem with x264

[UsuiEien]

Hello, this week, I have had this problem: http://puu.sh/2T4RV.png

This program can't start because nvcuda.dll is missing.
Try reinstalling in order to fix this problem.

I am trying to encode with x264 (10 bits), but I get that error, and my graphic card is AMD Radeon HD 6750M

But with nvcuda.dll installed, I get this error:

http://puu.sh/2T7GW.png

It can't be found the entry point for cuMemcpy3DAsync procedure in dinamic links' library nvcuda.dll

May somebody help me?
pls

[Blue_MiSfit]

This looks like an issue with your AviSynth script, not x264.

[LoRd_MuldeR]

Do you get the same error if you just run:
x264.exe --version

:confused:

If not, then please show your Avisynth scrip to us!

[UsuiEien]

I have already tested with other versions of the x264 and gives me the same error, here is my script of the Avisynth:

FFVideosource("G:\BDMV Steins\BDMV\[BDMV][110622]STEINS;GATE 001\BDMV\STREAM\00013.mkv")
Trim(0, 15201) ++ Trim(17358, 31910) ++ Trim(34068, 34451)
flash3kyuu_deband(grainY=22,grainc=22,range=18)
Spline36Resize(1280,720)

[LoRd_MuldeR]

You didn't answer the question.

Does this problem happen if you just run x264.exe, e.g. if you enter "x264.exe --version", or does it only happen when you try loading your Avisynth script ???

In the latter case, I highly recommend you remove all Avisynth plug-in's from your Avisynth "plugins" folder. Then only load these, explicitely in your script with LoadPlugin(), that you really need.

More often than not "strange" Avisynth issues are caused by leftover plugin DLL's in your "plugins" folder. You usually find the plugins folder at:
C:\Program Files (x86)\AviSynth 2.x\plugins

Also, I have no idea what flash3kyuu_deband() does. Any chance it is a CUDA-specific filter? Anyway, try kicking that one out, for the moment, and see if it changes anything...

[the_weirdo]

Also, I have no idea what flash3kyuu_deband() does. Any chance it is a CUDA-specific filter? Anyway, try kicking that one out, for the moment, and see if it changes anything...

flash3kyuu_deband (http://forum.doom9.org/showthread.php?t=161411) is a debanding filter. It doesn't use CUDA.

[LoRd_MuldeR]

flash3kyuu_deband (http://forum.doom9.org/showthread.php?t=161411) is a debanding filter. It doesn't use CUDA.

Which is another hint that he has some problematic Avisynth plugin lying in his "plugins" folder...

The only other reason that comes to my mind would be that he is using one of the newer OpenCL-enabled builds of x264 and has installed an NVidia OpenCL DLL for whatever reason.

(I know OpenCL is not CUDA, but it's quite possible the OpenCL DLL provided by the NVidia driver depends on other NVidia/CUDA-specific DLL's)

[sneaker_ger]

So, the last one without OpenCL was this one (http://mirror01.x264.nl/x264/32bit/8bit_depth/revision2273/x264.exe)?
Either that, try to get OpenCL to work, wait for the next x264 version or try the dummy dll? Would Windows try to load the dummy dll first if put into the same directory or would it load the one in the system folder?

[Groucho2004]

Which is another hint that he has some problematic Avisynth plugin lying in his "plugins" folder...
This:
I have already tested with other versions of the x264 and gives me the same error
would indicate that your assumption is correct.

[Atak_Snajpera]

from my experience dll put in the same directory as exe has higher priority than the same dll in system folder. The same trick use all fxaa/smaa injectors for 3d applications/games.

[UsuiEien]

In the latter case, I highly recommend you remove all Avisynth plug-in's from your Avisynth "plugins" folder. Then only load these, explicitely in your script with LoadPlugin(), that you really need.


Thanks everyone for your help. My problem no longer exists, thanks a lot.