x264: declaring source widthxheight when needed

[looney]

I have troubles to properly declare widthxheight option on x264 cli input cause no matter how i wrote it, it became ignored and get

x264 [error]: Rawyuv input requires a resolution.

Which i get in first place when i started to look for a workaround

I tried and just exhaust all ideas

x264 .... -o test.h264 test.avs 448x240
x264 .... -o test.h264 test.avs [448x240]
x264 .... -o test.h264 test.avs -[448x240]
x264 .... -o test.h264 test.avs --[448x240]

[Dark Shikari]

That's because your input isn't raw YUV, its an Avisynth script, and therefore doesn't require a resolution.

Have you checked to see that your script has no errors?

[looney]

It loads ok in vdub so i assume it was ok. i opened it with DirectShowSource(1.mkv, fps=23.978) and fps must be declared (raw input) which is weird cause i opened lot of other mkv without that problem.

So there's no help with width x height option when .avs is the source?

[Dark Shikari]

It loads ok in vdub so i assume it was ok. i opened it with DirectShowSource(1.mkv, fps=23.978) and fps must be declared (raw input) which is weird cause i opened lot of other mkv without that problem.

So there's no help with width x height option when .avs is the source?Possible ideas:

1. Tried reinstalling Avisynth?
2. Are you trying to use a 64-bit build of Avisynth with 32-bit x264?

[looney]

Possible ideas:

1. Tried reinstalling Avisynth?
2. Are you trying to use a 64-bit build of Avisynth with 32-bit x264?

Well avisynth works fine, even with that test.avs in virtual dub. And x264 still works fine with other .avs files. I'm using saggitiare's build and avisynt 2.57. So there's no workaround at all to force x264 to work with that test.avs?

[Dark Shikari]

Well avisynth works fine, even with that test.avs in virtual dub. And x264 still works fine with other .avs files. I'm using saggitiare's build and avisynt 2.57. So there's no workaround at all to force x264 to work with that test.avs?If x264 works with other avs files but not that one, it suggests something is wrong with that avs file ;)

Or perhaps you aren't in the right folder/etc? That's the error it'll give if it can't find the file, too.

[looney]

If x264 works with other avs files but not that one, it suggests something is wrong with that avs file ;)

Or perhaps you aren't in the right folder/etc? That's the error it'll give if it can't find the file, too.

God damn ... I misspelled my options line (leaving --cqmfile blank). You know whats the case from the start and you fool me around :rofl: :p .... Well big tnx i probably lied fused for a few hours/days wondering whats happened never even to think about that something is wrong with copied y264 line.

I suggest you change that warning quickly to something more intuitive "you misspelled your input file fool", "m-m i'm still hungry", "waiting ....", "you can better than that" .... Well maybe something better and put it in array with random outcome to be produced.

Tnx.

[Dark Shikari]

God damn ... I misspelled my options line (leaving --cqmfile blank). You know whats the case from the start and you fool me around :rofl: :p .... Well big tnx i probably lied fused for a few hours/days wondering whats happened never even to think about that something is wrong with copied y264 line.

I suggest you change that warning quickly to something more intuitive "you misspelled your input file fool", "m-m i'm still hungry", "waiting ....", "you can better than that" .... Well maybe something better and put it in array with random outcome to be produced.

Tnx.I think what happened was that it thought that something else on your commandline was the name of the file, not "test.avs". :p