Script errors in x264

[peve]

Hi,

my first post here, even though I've been reading for a couple of years. I tried to do my homework first by using Google and forum search, but I'm really stuck.

I'm not sure if this is more of a x264 issue, but I think it's a rather general topic:

What do I do if a script works in every application I try it with, and only the program I want to use to encode fails?

I have a rather simple script ...

DirectShowSource("C:\Snake.VOB",fps=29.97000002997,audio=false)
tfm(order=1).tdecimate()
crop( 8, 50, -4, -52)

BiCubicResize(704, 384)
mergechroma(blur(1.3)) # Little Noise

which runs fine in Windows Media Player or VirtualDub, but x264 always exists with

avis [error]: unsupported input format (DIB )
x264 [error]: could not open input file 'C:\snake.avs'

According to VirtualDub, the script itself returns YV12; I searched the forum here and found that the DIB format is most likely caused by an error mesage from Avisynth, embedded in a video stream - but since all other applications I tried run just fine, I can't reproduce the error.

Any ideas? I searched for terms like "Avisynth log", but could not find any helpful results ...

Thanks a lot
Peve

[nullstuff]

...I really don't know why you don't get the error even playing the avs, anyway try this script:try
{
DirectShowSource("C:\Snake.VOB",fps=29.97000002997,audio=false)
tfm(order=1).tdecimate()
crop( 8, 50, -4, -52)

BiCubicResize(704, 384)
mergechroma(blur(1.3)) # Little Noise
}
catch(err_msg)
{
messageclip(err_msg).converttoyv12()
}...in case of error, it will generate an error clip in YV12 format and x264 should be able to encode it. then you'll see...

-- nullstuff

[peve]

nullstuff,

thanks so much, that was very helpful :)

However, now I can't figure out why this error occus - again, only in x264, not in Media Player or VirtualDub. I even tried making a second AVS script, importing the first one with DirectShowSource or AVISource, same result:

DirectShowSource: RenderFile, the filter graph manager won't talk to me

[Pitbull_Raven]

nullstuff,

thanks so much, that was very helpful :)

However, now I can't figure out why this error occus - again, only in x264, not in Media Player or VirtualDub. I even tried making a second AVS script, importing the first one with DirectShowSource or AVISource, same result:

DirectShowSource: RenderFile, the filter graph manager won't talk to me

Did you ever find a way around this? I can't get avs to open up my MKV's. I get the same error.

[peve]

Nope, I gave up after a few hours of trying and bought a TViX 5100, which plays the MKVs I wanted to convert just fine :)

I have the same issue when trying to open .mpg with DirectShowSource as well, by the way.

[themostestultimategenius]

Try using DGIndex for MPGs and VOBs. You can get it on neuron2's site.

http://neuron2.net

[Pitbull_Raven]

Try using DGIndex for MPGs and VOBs. You can get it on neuron2's site.

http://neuron2.net

Thanks. But my issue is that I am trying to convert an MKV to MP4 and I can neither create the avs or encode the ac3 audio. The audio is easy enough to handle but I can't figure out for the life of me why I can't load up the MKV to the AVS Script Creator. I keep getting that damned error message.:mad:

[squid_80]

Possibly directshowsource is using ffdshow to decode, and it doesn't have x264.exe on it's whitelist/does have it on the blacklist.

Open ffdshow's video decoder configuration, choose directshow control from the left menu and see if there's a tick in the "Don't use ffdshow in:" or "Use ffdshow only in:" boxes.

[foxyshadis]

It'd probably be simpler all around to just use ffmpegsource, though.

[Adub]

I would try ffmpegsource, as foxyshadis said. I never really got mkv input to work via directshowsource, but ffmpegsource works fine.


Oh, and peve, the best way to open a .mpg or .vob file is to use DGindex. It is faster, and guaranteed to work.

[peve]

Try using DGIndex for MPGs and VOBs.

Oh, I know DGIndex and am using it - just wanted to point to another example that does not work.

I should have been more precise, but I was leaching Internet from some open WLAN somewhere in India at fifty bytes a second and a 2000ms ping to Europe, so I kept my response as short as possible.

Cheers
Peve