Log in

View Full Version : sex264 (updated almost daily by now)


Pages : 1 2 3 4 5 [6]

Koti
16th January 2005, 07:44
I have had the same error on ocassion in Vdub with x264. Something I have noticed though - If I retry the 2nd (errored) pass in job control by double clicking on it so the 2nd pass shows waiting and start it again, the 2nd pass will start with no error.

dvd_maniac
16th January 2005, 09:58
@ mezzanine

I've changed and old gui i made some months ago to support x264.
The gui is using avs2avi and other tools to encode dvd's. If anyone wants to test it send me a pv. Here is a screenshot.

Hi Mezzanine,

Is this the same tool that needs .NET framework? Where can I download this from?

Bluedan
16th January 2005, 19:46
Originally posted by mezzanine
[...] send me a pv.

I'd like to send you a PM if you do accept that instead. :D

Bluedan
16th January 2005, 22:00
Originally posted by len0x
Can someone tell me how does x246's one pass encoding comparing to XviD's one pass in terms of quantizers? They probably not the same, aren't they? (as range is 0-51 vs 1-31)

I kindly want to recal THIS question, because I am simply looking for an easy explanation, too, that I cannot find neither in the FAQs nor in far advanced places like this one here (http://www.vcodex.com/h264.html) which is much too technical for me - I have to admit.

akupenguin
16th January 2005, 22:26
From the MPlayer manpage:
The mapping is approximately H264QP = 12 + 6*log2(MPEGQP). For example, MPEG at QP=2 is equivalent to H.264 at QP=18.

len0x
18th January 2005, 18:06
Is it equivalence in size or quality?
In my small test I can see that size of XviD @ quant2 ~ size of x264 @ quant17...(which is indeed close to quant18)

akupenguin
18th January 2005, 19:42
Originally posted by len0x
Is it equivalence in size or quality?
It's equivalence in quantizer (or lambda for rate-distortion). Which tends to be somewhere between size and quality.

hworldjj
19th January 2005, 05:43
Originally posted by len0x
Is it equivalence in size or quality?
In my small test I can see that size of XviD @ quant2 ~ size of x264 @ quant17...(which is indeed close to quant18)

You can refer to Iain E G Richardson' paper about Transform and quantization in H.264. There is a talbe to map qp_index to qp_step from 1 .. 51.

Blue_MiSfit
19th January 2005, 08:19
Any possibility of adding a status window like XviD's? :) I love being able to monitor quantizer distribution and getting all those nice stats like max/min/avg i/p/b frame sizes etc...

It really sets XviD apart from the competition.

~misfit

Yong
25th January 2005, 11:47
The x264vfw revision105 version is wierd,
i can't access the x264vfw cofiguration window, or the "about" window,
need to clear the registry settings so i can access it...:eek:
I tried with VD1.6.3, VDMOD and TMPGEnc, all have the same problem...

Sirber
25th January 2005, 15:11
x264 fails on my HDTV test encode at 1280x720. AVS2AVI gives me a nasty exitCode :confused:

len0x
25th January 2005, 15:22
IMHO this thread needs to be closed and all discussion should go into main developent thread here: http://forum.doom9.org/showthread.php?s=&threadid=80910
(as bug reports get separated between these two threads - i.e. problem with rev 105&106 is already being discussed there).

bond
25th January 2005, 20:21
hm syskin might add things to sex264 that will not go directly to svn, so it might be good to leave this open (also for the vfw codec related issues)

len0x
25th January 2005, 21:58
Originally posted by bond
also for the vfw codec related issues

those are being discussed in the main thread anyway :)
Its just we have to make clear that general x264 bugs have to go to the other place, otherwise its getting hectic.

kilivipin
26th January 2005, 15:11
264th post!
I just noticed it in the forum list, and I couldn't resist.
I am really sorry.

garumphul
28th January 2005, 21:39
I download a codec to have a play (everybody else is playing, why can't I?), and there's a fundamental problem with the "dec" part. My little test encodes up nicely with the new Gordian Knot but... nothing wants to play it. What do I need to download other than the (incorrectly titled) x264 codec from Mr Druid?

MSlv
28th January 2005, 21:48
latest ffdshow maybe?

len0x
28th January 2005, 23:43
Which brings up another question: are there any plans to make a VFW x264 decoder? :)

Tommy Carrot
28th January 2005, 23:55
The x264 library doesn't support decoding, only encoding, so the codec would have to use external library for decoding, and afaik only libavcodec is capable for that, and including it would bloat the codec hugely. Using external decoder (ffdshow) is simpler.

garumphul
29th January 2005, 01:36
Well there you go then.

There's a fundamental problem with calling something a "codec" when it does not, in fact, "dec".

The word "codec" is, surprisingly enough, a contraction of the words "encoder" and "decoder". One would expect, therefore, that downloading a "codec" would enable the encoding *and* decoding of video. Or maybe I'm getting a bit literal in my old age.

If somebody had said to me "hey, here's a really great video encoder... just the encoder... no decoder... but a fabulous encoder", then I might have saved myself the effort of downloading it. What's the point?

It interests me not a jot to be able to encode a film in a lovely cutting-edge format if I can't *watch* the bloody thing to find out how good it is!

Call it what it is - it's an **encoder**, not a codec.

If I've done something blatantly wrong in installing a "codec" and expecting it to decode the file it encoded, then feel free to enlighten me with every ounce of sarcasm available to you.

virus
29th January 2005, 02:21
Originally posted by garumphul
Call it what it is - it's an **encoder**, not a codec.

If I've done something blatantly wrong in installing a "codec" and expecting it to decode the file it encoded, then feel free to enlighten me with every ounce of sarcasm available to you.
No need to. You seem already full of sarcasm, especially about work that other people are providing for free to you. Thanks for the lecture. It was not needed, but that's not important.

I'd like to encourage you to do the following steps:

1) open the Select Video Compression window in VDub
2) look into the list at the left
3) watch the name of the x264 codec listed there

Then I'd also like to encourage you to check the source code (http://developers.videolan.org/cgi-bin/viewcvs.cgi/trunk/?root=x264) for the file /x264/x264.c, line 511-514, which I report here:

static int Decode( x264_param_t *param, FILE *fh26l, FILE *fout )
{
fprintf( stderr, "decompressor not working (help is welcome)\n" );
return -1;


Finally, I'd like to point you at the project main page (http://videolan.org/x264.html), especially at the red warning printed just below the title:
BIG FAT WARNING: x264 is still in early development stage
Now, if you want to continue blaming other people for your lack of understanding of the forum rule #1, you're free to go on with your useless whining. But I don't think a moderator would tolerate that for so long. ;)

regards,
virus

MSlv
29th January 2005, 10:25
Is there any new build yet to come?

Arkoki
29th January 2005, 13:09
Hello,

The x264 library doesn't support decoding, only encoding, so the codec would have to use external library for decoding, and afaik only libavcodec is capable for that, and including it would bloat the codec hugely. Using external decoder (ffdshow) is simpler.

If you change the fourCC option in Sex264 to H264 (no, h264), you can use Nero Decoder too. Then, using external decoder (ffdshow or nero decoder) is simpler.

Thanks.