x264 development [Archive] - Page 33

Koti

13th February 2006, 05:13

Ok but you want open x264 avi file i virtual dub to split there is error message.

Correct, VirtualDub always show error message when I try to open x264 encoded AVI file. Error message:

"Couldn't locate decompressor for format H264(unknown). VirtualDub requires a Video for Windows(VFW)compatible codec to decompress video. Directshow codecs, such as those used by Windows Media Player, are not suitable".

http://forum.doom9.org/showthread.php?t=93572 <---- April 2005 :search:

celtic_druid

13th February 2006, 05:15

Actually I think you can go about as high as you want although really high values (30,000) would look like crap and if you go too high, then you end up back at 0. 250 or so is probably about as high as you would want to go. Guess it would depend on the source and bitrate though. A value of 250 will result in a lower size per quant than 0, so if the bitrate is low enough, then I guess a high value might pay off.

shon3i

13th February 2006, 12:42

Do you have an up-to-date build of ffdshow installed? If not so, you'll have to do this!
And after ffdshow is installed, go to START -> Programs -> "ffdshow" -> "VFW codec configuration" and enable "H.264" on the Decoder tab (you need to change value from "disabled" to "libavcodec")
This will work OK this work. I dont see this options before. btw on my machine have trouble with ffdshow. i used last build on x264.nl and try other builds but same problem in something memory leak. have someone other vfw decoder.

LoRd_MuldeR

13th February 2006, 16:38

OK this work. I dont see this options before. btw on my machine have trouble with ffdshow. i used last build on x264.nl and try other builds but same problem in something memory leak. have someone other vfw decoder.

I think ffdshow is what you will have to use, if you need to decode x264 content via VFW. One other way I can think of is this: Open the file with AviSynth and then frameserve it to VirtualDub. But then you still would need a decoder - ffdshow. Maybe the official "daily build" works better for you...

bob0r

13th February 2006, 16:42

I actually added those features to the build I included with my FairUse Wizard compile back in Dec or whenever.

I was just waiting to see if anyone would notice...

Where can this be downloaded, and why not add to x264 SVN? :)

celtic_druid

13th February 2006, 17:06

http://mirror05.x264.nl/celtic_druid/force.php?file=././fu2.2-setup.exe

Whenever I have done a FU build, I have updated all tools, codecs, etc. and since it includes x264vfw I added a few options to make it more uptodate.

Since I didn't want to encourage VfW use, I stopped uploading VfW builds some time back. Like I said, I was waiting to see if anyone would actually notice.

bob0r

13th February 2006, 17:11

Ahhhh no wonder, i never added you to files.x264.nl :D
Ill fix you an account on there later, mirror05 should only be used if files breaks down.

Hehehe, totally forgot about that path :p

Kostarum Rex Persia

13th February 2006, 17:19

celtic_druid, do you planning to compile your new build, based on recent builds from pengvado, with your new settings and stuff?

You have no excuse now, because bob0r will create a account for you on files.x264.nl:D

[edit] I just visited files.x264.nl, and I saw ready vfw patch for fast-p-skip( http://files.x264.nl/force.php?file=./x264_vfw_fast_pskip.diff ) But what about no-fast-p-skip patch?

ChronoCross

13th February 2006, 17:23

damnit C_D. don't update the vfw -_-. cause now we are gonna have about 100000000000 new threads figuring out problems with vfw and why it's output is damaged. which would be fine if it were the cli cause then it would be a big problem but now we have to waste time trying to figure out if these issues are just vfw or if it's cli.

I'm just kidding at you C_D it's fine I just hope people realize how stupid AVC in avi is. Kostarum Rex Persia however won't so I look forward to more annoying "when is this feature going to be implemented" threads.

celtic_druid

13th February 2006, 17:29

I think mirror05 has a nicer ring to it anyway. Next time I do a FU build, I will once again make sure that all included tools, codecs, etc. are upto date. Other than that I don't think I will be updating or releasing x264vfw builds.

My cli build is at revision 434 and r435 was just cosmetics.

Those who want AVC in avi can always use mencoder.

Edit: Looks like the FU source got updated Sunday, 12 February.
Edit2: Zip is still the same. Don't know why the date as changed.

Kostarum Rex Persia

13th February 2006, 17:38

I'm just kidding at you C_D it's fine I just hope people realize how stupid AVC in avi is. Kostarum Rex Persia however won't so I look forward to more annoying "when is this feature going to be implemented" threads.

Well, if you wanna to insult me, fine. Before that, I suggest to, once again, read forum rules, rule number 4. I never want to insult you, so I, certainly, never expect something like that from you, ChronoCross.

Sirber

13th February 2006, 18:08

Well, if you wanna to insult me, fine. Before that, I suggest to, once again, read forum rules, rule number 4. I never want to insult you, so I, certainly, never expect something like that from you, ChronoCross.It's not an insult, it's a guess on your next move ;)

ChronoCross

13th February 2006, 18:15

It's not an insult, it's a guess on your next move ;)

exactly. if I wanted to insult you I would have done so. plus it wasn't just aimed at you I just happened to have used you as an example since your the leader of the we need vfw movement.

bob0r

13th February 2006, 20:15

I think if x264 developers allow VFW, when it does not create bugs outside VFW, and pengvado allows it obviously, then i see no problem in developing, testing and posting about VFW.
If people want it, why not?

A seperate x264-vfw-development thread ofcourse would prefered, so VFW haters don't have to read it, and requests/bugs/questions can be placed without starting a flame war each time.

MeGUI style threads would be recommended (bug/feature requests/help-manual-questions).

But only if x264-VFW is being seriously developed.

Celtric_druid certainly has the skills to develope VFW, but has no time or is not motivated to do so.

Sharktooh also has the skills, but he can't figure out if he's a girl or a boy (no seriously, health problems prevent him from being active on any level)

Dan "Genesys" Nelson can update certain options also, but to quote him:
"whatever features translate into checkboxes or other simple UI objects, I can do :)"

So, motivation by both user and developer is key issue here, i like VFW, i bug test it and share my thoughts on it, but x264.exe (+ a gui if you must) is simply perfect, each option explained and clear.

Its true any gui(or vfw) can indeed bind options, like mixed-refs can only be used when you have 2 or more reference frames, this makes you learn the options better, for the best result.

One-Click tools will come/are available anyway, so or you just use a program as is, or you fully try to understand its options and make the best of it.

Kostarum Rex Persia

13th February 2006, 20:17

Well, ok then, ChronoCross. I am not a leader, and other peoples wanted and asked for updating vfw, not just I. For example, DeathTheSheep.

Kostarum Rex Persia

13th February 2006, 20:22

SeeMoreDigital

13th February 2006, 20:30

That's wonderful idea, bob0r. Let create separate x264-vfw-development thread. Of course, like MeGUI, and vfw would get thread " Feature requests ", " x264 vfw bug reporting ".

Doom9, what do you think about bob0r suggestion?It sounds quite sensible to me!

Sirber

13th February 2006, 20:31

Well, ok then, ChronoCross. I am not a leader, and other peoples wanted and asked for updating vfw, not just I. For example, DeathTheSheep.The only one beside you ;)

Kostarum Rex Persia

13th February 2006, 20:36

Well, they are hiding. vfw respecters are quite numerous here, but most of them don't talk about it.

LoRd_MuldeR

13th February 2006, 20:48

Well, they are hiding. vfw respecters are quite numerous here, but most of them don't talk about it.

I'm here too :D

shon3i

13th February 2006, 20:58

I think ffdshow is what you will have to use, if you need to decode x264 content via VFW. One other way I can think of is this: Open the file with AviSynth and then frameserve it to VirtualDub. But then you still would need a decoder - ffdshow. Maybe the official "daily build" works better for you...And what is hapen if i won't recompress video. I tell you that i can using ffdshow beacouse is not working in some reason. I can open any file in virtualdub via avisynth but i must recompress video.

Let create separate x264-vfw-development thread That was be cool

LoRd_MuldeR

13th February 2006, 21:06

That's wonderful idea, bob0r. Let create separate x264-vfw-development thread.

They will close and delete it one minute after it is created :(

Sirber

13th February 2006, 21:06

They will close and delete it one minute after it is created :(For your own good ;)

LoRd_MuldeR

13th February 2006, 21:07

And what is hapen if i won't recompress video. I tell you that i can using ffdshow beacouse is not working in some reason. I can open any file in virtualdub via avisynth but i must recompress video.

I think you'll have to get ffdshow working.
What exactly is the problem? And what builds did you test so far?
Did you try a clean(!) re-install of the official "daily build" ???

valipod

13th February 2006, 21:12

I searched the entire MPEG-4 AVC forum for keyword 29.970 and then only for 29, nothing. I figure there must be a bug in the search, nevertheless I didn't find a post regarding my problem.

I have a movie 29.970 FPS, I open the AVS (in VirtualDubMod), it shows 29.970 FPS. I encode it with MeGui x264, and the resulted .264 i convert to AVI with the x264 AVC2AVI embedded in the x264 Full Package. The problem is, the resulted AVI is 25 FPS!!! And 20% longer (seconds), of course. I am of course missing something here, but what?

The same AVS encoded via VfW in VirtualDub produces a correct 29.970 FPS AVI.

LoRd_MuldeR

13th February 2006, 21:14

shon3i

13th February 2006, 21:21

I think you'll have to get ffdshow working. I can menage this beacouse my windows is crasheed and i have no time to reinstall it. So i using lastest build from x264.nl i think is 21/12/2005 gcc sse i olso tried some build from free-codecs.com but nothing hapen.

valipod

13th February 2006, 21:26

Can't you change the Framerate of the AVI in VirtualDub and set it to the correct value? Just use direct-stream-copy for audio and video.

Well, I did that now, and it works (thanks). But let's call this a "workaround". Is this a bug in the CLI or in the AVC2AVI converter?

LoRd_MuldeR

13th February 2006, 21:27

I can menage this beacouse my windows is crasheed and i have no time to reinstall it. So i using lastest build from x264.nl i think is 21/12/2005 gcc sse i olso tried some build from free-codecs.com but nothing hapen.

Give this one a try:
http://ffdshow.sourceforge.net/tikiwiki/tiki-index.php?page=Getting+ffdshow

shon3i

13th February 2006, 21:37

Give this one a try:
http://ffdshow.sourceforge.net/tikiw...etting+ffdshowI try later thanks for all help

valipod

13th February 2006, 21:45

Is there a way I could find out what framerate the intermediate .264 file is? Because I am pretty sure the bug is in the AVC2AVI converter.

Dayvon

13th February 2006, 21:48

Is there a way I could find out what framerate the intermediate .264 file is? Because I am pretty sure the bug is in the AVC2AVI converter.
It probably is AVC2AVI because MP4 files default to 25 fps unless label otherwise. Are you rendering to a RAW .264 stream? Because if you are rendering to MP4, you more than most likely will have this problem.

shon3i

13th February 2006, 21:57

Is there a way I could find out what framerate the intermediate .264 file is? Because I am pretty sure the bug is in the AVC2AVI converter.
You must use avc2avi comandline and add -f or -fs switch i dont now at the moment use avc2avi -h for help
ex. myfile.264 -f 25 myfile.avi

valipod

13th February 2006, 22:01

It probably is AVC2AVI because MP4 files default to 25 fps unless label otherwise. Are you rendering to a RAW .264 stream? Because if you are rendering to MP4, you more than most likely will have this problem.

I created a RAW .264 stream from a 29.97 FPS AVS. And I converted the RAW .264 to avi, where I could observe the 25 FPS.

I tried now the AVC2AVI -h, it says there it defaults to 25 FPS. Still, since the source is 29.97, it should keep that, not expect a parameter from me, or default to something else. Or is there no FPS information in the .264 RAW stream?

shon3i

13th February 2006, 22:02

I created a RAW .264 stream from a 29.97 FPS AVS. And I converted the RAW .264 to avi, where I could observe the 25 FPS.
Look my uper post but here is example for you avc2avi myfile.264 -fs 29.976 myfile.avi

SeeMoreDigital

13th February 2006, 22:06

Is there a GUI for avc2avi.exe?

valipod

13th February 2006, 22:07

Look my uper post but here is example for you avc2avi myfile.264 -fs 29.976 myfile.avi.

I figured out the sintax, even if there is no avc2avi /? (and -h instead :)) The issue now was only to discover where bug is, in the CLI or in the AVC2AVI. I tend to think is the AVC2AVI, with that defaulting to 25FPS. And again, is there no FPS information in the RAW .264 stream?

valipod

13th February 2006, 22:13

Is there a GUI for avc2avi.exe?

:) There is AVC2AVI_GUI from the x264 full package, which offers the smallest of functionalty, that is "browse for input" and "Mux".

shon3i

13th February 2006, 22:16

And again, is there no FPS information in the RAW .264 stream?I know that but if you want convert .264->AVI default fps from avc2avi.exe is 25, using -fs or -f switch you can corect that. You can't use avc2avi gui beacouse there is not option to change fps. Use run and type cmd, then go to dir where is located avc2avi.exe not gui exe. type avc2avi.exe you should be get all switches. I have avc2avi.exe from lastest sharktooth build 408.

valipod

13th February 2006, 22:23

I know that but if you want convert .264->AVI default fps from avc2avi.exe is 25, using -fs or -f switch you can corect that. You can't use avc2avi gui beacouse there is not option to change fps. Use run and type cmd, then go to dir where is located avc2avi.exe not gui exe. type avc2avi.exe you should be get all switches. I have avc2avi.exe from lastest sharktooth build 408.

Actually I was asking. Is there no FPS information in the raw .264 stream? It seems like it isn't.

I have always tried the /? switch whenever I needed help from a commandline exe. Didn't work here. So I figured there's no help offered. I have now tried the -h switch (mentioned here a few posts up) and I got the options. Thanx.

akupenguin

13th February 2006, 22:51

Actually I was asking. Is there no FPS information in the raw .264 stream? It seems like it isn't.
There is. avc2avi just ignores it.

fuxor123

14th February 2006, 02:13

I encoded some transport streams lately on hte hg-slow settings with megui and couple of times there's some pixelation while a scene changes in the encoded file. The bitrate I used was around 4200kbs. It didn't seem to matter though if it was in a fast or slow moving part of the movie. Just from times to times in a scene change.
Is there any chance of avoiding such an effect in future encodings?

Kostarum Rex Persia

14th February 2006, 02:18

OK, guys, raw streams aren't my field, so...

Let's get back on introduce separate threads about VFW development, like Bobrow suggested earlier yesterday on page 82, I think.

Doom9, you didn't answer me anything about new threads. What do you think about opening separate VFW threads, " X VFW development", " X VFW error reporting ", and " X feature requests " ?

Can Bob0r or someone else start these threads, please? :)

asdfsauce

14th February 2006, 06:12

Profiles for VFW would be nice. :scared:

ChronoCross

14th February 2006, 07:38

As you can see I have made two new topics for you vfw people. Don't make a development thread because it's not needed. The development can be done in the feature request thread as that's probably where the updates on developer progress will go.

For you cli people eager for a new custom build I have made the following

Custom x264 Builds with patches. (http://chronocrossdev.com/apps/x264)

I updated sharktooths patches...well all except the one with vfw in the title of the .diff. I also removed the Signature.diff vfw changes. If you encounter any problems let me know and I'll see if I can narrow it down.

Sharktooth

14th February 2006, 11:19

Is there a GUI for avc2avi.exe?
http://files.x264.nl/Sharktooth/utils/avc2avi_rev267+gui.7z
requires .NET 2.0, it muxes the file in the same dir as source and uses the same filename (except the extension that will be .avi).
just let me know if you need more functionalities (well there isnt much to do but...) and i will add them when i will be able to re-start coding.
i was thinking to add fps, batch muxing and maybe splitting (but it requires another prog).

SeeMoreDigital

14th February 2006, 12:21

http://files.x264.nl/force.php?file=./Sharktooth/utils/avc2avi_rev267+gui.7z
requires .NET 2.0, it muxes the file in the same dir as source and uses the same filename (except the extension that will be .avi).
just let me know if you need more functionalities (well there isnt much to do but...) and i will add them when i will be able to re-start coding.
i was thinking to add fps, batch muxing and maybe splitting (but it requires another prog).Thanks Sharktooth,

I downloaded the x264 Standard R408 package yesterday :D

I wanted to see how well it worked muxing raw ".h264" streams that had been extracted using YAMB.

The thing I noticed straight away is that the ".h264" file extension is not listed, only the ".264" file extension... Although the muxing worked fine :)

Support for specifying the required FPS would be the most useful implementation at the moment, I think.

Hope you start feeling a little better soon.... Speaking as somebody who was forced into giving up full-time work due to a chronic illness (and had to re-build my immune system from scratch), I sympathise with you....

Cheers

Doom9

14th February 2006, 12:32

It's not really an x264 development issue but it's rather technical: Recently, a number of megui users ran into x264.exe aborting the first pass without notice, and then the the second pass would abort immediately with a message about a mismatch of number of frames between the source and the statsfile. However, megui never gets those error messages. Even though I redirect both stdout and stderr of x264.exe, and make sure I keep reading from both as long as neither reports null (that goes beyond the process reporting it has exited), megui can never pick up those messages. I used to have the same issue with encraw but when I changed the code to keep reading beyond the process.Exited event until attempting to read from stdout and stderr just reports null, I managed to catch all the lines from encraw. I'm wondering if anybody has an idea why this doesn't work for x264.exe and what there is fundamentally different from x264 exiting immediately with an an error like the mentioned one, and other errors (like unsupported commandline option.. those are picked up just fine).