View Full Version : x264 development
MSlv
17th April 2005, 17:38
About b-frames.
When using them, BSPlayer refuses to play the file and gives me this error message:
"List index out of bounds (0)"
Also, the same file acts strange in videolan. It shows artefacts like this:
http://img64.echo.cx/img64/9279/x264bfrvlc9bm.th.jpg (http://img64.echo.cx/my.php?image=x264bfrvlc9bm.jpg)
Same file plays fine in Media Player Classic.
Mug Funky
18th April 2005, 04:01
yet offer manual control where desired, including some cool combing artifact cleanup features that no one has done yet, AFAIK
this sounds interesting!
another thing i'd really love to see is a "segment re-encode" feature (maybe this is best suited to Virtualdub's interface?).
ie. you watch the movie, and note all the crappy bits. you then set I-frame (or IDR frame for AVC, i suppose) in and out points, and re-encode the bad part using the same GOP structure.
i know DVDMaestro offers this (and it's reeeeally nice to use if you've got the Spruce MPX3000 encoder card plugged in - seamless integration with the authoring app). it'd be good to see this built into an mpeg-4 solution - this would mean if your encode is undersized, it's not a problem. it also means if you're using a not-so-good encoder (WMV? Divx 3?) you can still get nice encodes if you re-do enough segments (this is exactly what the feature is for in Maestro - mpeg-2 isn't the best codec, and sometimes a client just wants so much video on a disc that the bitrates go way down).
well, this is also a pipe dream, but i'm sure lots of tweekers would find it useful (the kind who use YATTA for instance :))
Stacey Melissa
19th April 2005, 04:08
I hadn't heard of YATTA before. Judging from its description, it sounds like it gets about halfway there for what I was wanting to do to clean up combing artifacts. I'll have to check it out. Thanks. :)
And since you mention setting IDR frames... part of my pipe dream includes the ability to force IDR frames at specified frames. This would be used in combination with the Nero-style chapters that have been recently integrated into mp4box. Chapter seeking would be very fast if the chapter is always set on an IDR frame. Anyway, that would be something nice to have built into x264, although not essential.
And another cool feature to have in x264 would be the ability to use different deblocking strengths for different zones. Maybe that was already planned anyway? I think I've done maybe 30 or 40 encodes of Matrix3, and no matter what x264 parameters I set, I can't get rid of that damn horrendous blocking behind Merv on his balcony. But if I could jack up the deblocking strength to, say, 6, just for that scene, then I'd consider that progress. :D That would at least be one possibility for improving such troublesome scenes. Other possibilities all have to do with fancy AVS wizardry, so I suppose I'll save 'em for another thread. :p
Doom9
19th April 2005, 09:17
part of my pipe dream includes the ability to force IDR frames at specified frames. This would be used in combination with the Nero-style chapters that have been recently integrated into mp4box.Is that really necessary? After all, if the playback filter cooperates, you can easily jump to any given frame regardless of its frame type.
Stacey Melissa
19th April 2005, 18:16
Of course it's not necessary. It's part of my pipe dream! :p
What it would help with is just making chapter seeking more responsive.
virus
21st April 2005, 23:53
some problems here when using b-refs with revision 215... but that's likely a skipping issue so probably a long-standing one. Very weird artifacts due to exaggerate skipping, or maybe some probs with direct mode + brefs, dunno. Anyway, cmdline:
x264 -m 3 -b 3 --b-pyramid --frames 300 -q 27 -o x264-r215-brefs.mp4 ~/mplayer/main/test-2.avs
The result is available here (http://www.webalice.it/riccardo.stievano/video_stuff/x264-r215-brefs.mp4) (627 KB). Look at frames 200 and following. The mess on the woman's face is evident. Frame 230 (according to MPlayer's numbering, ffdshow's may differ) seems the worse.
I got a report (thanks to AlexW) that even decoding with JM the artifacts are there, so it's definitely an encoding issue. The quantizer of bvops is 28-29 here so nothing exceptionally low; not enough to justify such problems, at least. Similar problems happen (maybe even worse) when using -m 5 so it's not directly related to the ME type.
bond
21st April 2005, 23:58
Originally posted by virus
[B]some problems here when using b-refs with revision 215... but that's likely a skipping issue so probably a long-standing one. Very weird artifacts due to exaggerate skipping, or maybe some probs with direct mode + brefs, dunno.i can confirm that i get the same problem :scared:
i saw that especially with -q 20 -b 5 --b-bias 100 --b-pyramid
btw the new --progress option rocks! would be cool if it gets enabled by default :)
akupenguin
22nd April 2005, 05:10
Originally posted by virus
some problems here when using b-refs with revision 215... but that's likely a skipping issue so probably a long-standing one. Very weird artifacts due to exaggerate skipping, or maybe some probs with direct mode + brefs, dunno.
Fixed. The encoding was correct. Only the header was wrong. Old references are forgotten in encoding order, not in order of display timestamp. So when references are reordered (pyramid), having a bigger DPB than expected can change the meaning of "L0 ref 1" to mean something other than what the encoder thought. I didn't notice because only the oldest ref is affected => not very many MBs in B-frames at frameref=8 or 16.
rushin_911
28th April 2005, 16:39
feature request: Choosing SAR values from the vfw version...
(I know I've asked that before in this same thread, but I hadn't mentioned the vfw version specifically and at the time this feature had already been introduced in the CLI version)
Yong
28th April 2005, 18:06
Why don'y use the CLI x264 encoder?
It isn't hard to use than vfw and more up-to-date imho.
But still i hope x264 devs or other contributors can update this vfw:)
@rushin_911:
You can transmuxing the video to MKV and changing the D/SAR via MKVtoonix.;)
I've tried with MKVToolnix, the D/SAR is ignore by ffdsohw(or haali matroska splitter?)...:rolleyes:
Only MPlayer is respect the MKV D/SAR value.
EDIT: nasty typo...
Sirber
28th April 2005, 18:26
I'm thinking about adding CLI in RealAnime, instead of only using the VFW one. Since it supports AVS, it will be easy to implement.
rushin_911
29th April 2005, 11:56
Originally posted by Yong
Why don'y use the CLI x264 encoder?
It isn't hard to use than vfw and more up-to-date imho.
But still i hope x264 devs or other contributors can update this vfw:)
@rushin_911:
You can transmuxing the video to MKV and changing the D/SAR via MKVtoonix.;)
I've tried with MKVToolnix, the D/SAR is ignore by ffdsohw(or haali matroska splitter?)...:rolleyes:
Only MPlayer is respect the MKV D/SAR value.
EDIT: nasty typo...
Well the reason for not using the CLI version is that Iīm not very familiar with the command line environment...
As for the MKVtoolnix I already use the DAR values from it when muxing into MKV, unfortunatly though itīs, as you have stated, ignored by ffdshow even when enabling overlay and also ignored by Media Player Classic (my player of preference)...
My request for the SAR values to be visible in the VFW however are for when I mux the media files created into the MP4 format.
Yong
29th April 2005, 13:06
@rushin_911:
@echo off
IF '%1'=='' GOTO EOF
title X264 Encoder
start /belownormal /b /w X264 -p 1 --stats "%userprofile%\desktop\X264[%~n1].log" -o nul: %1 --progress
start /belownormal /b /w X264 -p 2 --stats "%userprofile%\desktop\X264[%~n1].log" -o "%userprofile%\desktop\%~n1.mp4" %1 --progress
pause
:EOF
save the above code to "x264.bat"
u can try to add other cli option if u need like, --b-pyramid, --weightb and --subme 5.
can anyone play those video clip normally from VSoft's h264 free video clips download section?
http://www.vsofts.com/h264/videoclips.html
Mplayer and ffdshow hang when playing those CIF and D1 video clips...
(becareful, my computer almost freeeeeeze when playing with ffdshow :rolleyes: )
Second, i think there may be a problem in x264 encoders
, when playing x264 encodeds with libavcodec in grayscale mode,
mplayer and ffdshow both show some random big green blocks when playing(extra, flashing green in mplayer),
but HD video clip from apple website doesn't have this kind of problem...
stupid typo again...
Ok, finally i found some playable clips from LEAD h264 free video clips (http://www.leadcodecs.com/Download/H264-Videos.htm) , forget the buggy VSS video clips :D
dude051
1st May 2005, 06:47
Can anyone help tell me which values in the VFW are relative to the CLI values? I can pick out all but two, b-frames reduction % and bitrate variability %. I encode mainly Anime, and want to jump to the CLI version to have some of the newer options. My current setup im working with looks like:
@echo off
start /belownormal /b /w x264 -I 300 -i 30 -b 2 -A all -w --b-pyramid --no-chroma-me -p 1 --stats "X264[%~n1].log" -o nul: %1
--progress encode.avs
start /belownormal /b /w x264 --merange 32 -I 300 -i 30 -b 2 -f 1:0 -B 1453 -r 8 -A all -w --me esa --b-pyramid --chroma-qp-offset 2 -p 2
--stats "X264[%~n1].log" -o "encode.mp4" %1 --progress encode.avs
I've heard setting a constant quant as apose to constant bitrate is better, how would i go about guessing one close to my desired bitrate? Also... in the VFW version, does checking "fast firstpass" disable most non-needed cpu intensive things like -A , --me? And im not too sure how different h.264 works compared to XviD, but would it ever be possible to create custom matricies for x264? Although x264's quality vs. noise is alot more impressive than the older codecs, I would like to be able to work on the nasty DCT blocks that show up. Setting the deblocking filter high does not help with this.. as it helps to prevent blocks from already existing blocks. I want to try and help blocks that occur from large flat dark/low contrast areas (such as in most anime). I've searched as much on these questions as much as I wanted to... but its getting late heh.
Thanx in advance...
but would it ever be possible to create custom matricies for x264?Not until x264 supports the AVC high profile. If you have a look at bond's excellent sticky:
http://forum.doom9.org/showthread.php?s=&threadid=73022 you'll see that the AVC Main profile does not support custom quantizer matrices.
Sagittaire
1st May 2005, 12:05
good quality with good speed
x264.exe --bframe 2 --ref 5 --pass 1 --stats "x264_stat.log" --qcomp 0.75 --ipratio 1.10 --pbratio 1.30 --analyse "all" --weightb --progress -o x264-HDTV.mp4 HDTV.avs
x264.exe --bframe 2 --ref 5 --bitrate 2500 --pass 3 --stats "x264_stat.log" --qcomp 0.75 --ipratio 1.10 --pbratio 1.30 --analyse "all" --weightb --progress -o x264-HDTV.mp4 HDTV.avs
x264.exe --bframe 2 --ref 5 --bitrate 2500 --pass 2 --stats "x264_stat.log" --qcomp 0.75 --ipratio 1.10 --pbratio 1.30 --analyse "all" --weightb --progress -o x264-HDTV.mp4 HDTV.avs
"esa" is too slow and quality improuvement is really small
bpyramid don't improve quality and playback is not good
Originally posted by Sagittaire
...bpyramid don't improve quality and playback is not good
Should i say you are kiddding?:rolleyes:
no b pyramid:
x264 [info]: PSNR Mean Y:42.93 U:46.83 V:46.70 Avg:43.66 Global:41.87 kb/s:604.7
b pyramid:
x264 [info]: PSNR Mean Y:42.56 U:46.74 V:46.66 Avg:43.30 Global:42.00 kb/s:601.0
EDIT: So far i haven't encountered any playback problem with b-pyramid...
Originally posted by Yong
Ok, finally i found some playable clips from LEAD h264 free video clips (http://www.leadcodecs.com/Download/H264-Videos.htm) omg, what files are these...
- they use wav audio (good for the bandwidth...)
- they place avc in a bastard version of the .ogm format (not listed as video stream)
- they give the .ogm files the .avi extension
- they dont seem to like p-frames, as their streams mainly use b-frames and a few i-frames
funky :D
Originally posted by bond
omg, what files are these...
- they use wav audio (good for the bandwidth...)
yep, uncompressed 1411 kb/s PCM, they are stup1d...
- they place avc in a bastard version of the .ogm format (not listed as video stream)
- they give the .ogm files the .avi extension
OGM? Are you sure?
i see the "RIFF" in the top of file
- they dont seem to like p-frames, as their streams mainly use b-frames and a few i-frames
funky :D
Sure:D
Hey Bond, can u play the free VSS h264 video clips normally?
in my test, mplayer and ffdshow both crashed when playing:devil:
Originally posted by Yong
OGM? Are you sure?
i see the "RIFF" in the top of filethe whatbox samples are avi, the others are ogm
Hey Bond, can u play the free VSS h264 video clips normally? the vss clips use an illegal packing of b-frames, which only their own decoder supports
Originally posted by bond
the whatbox samples are avi, the others are ogm
i think we should rename the *.OGM to *.OMG(oh my god):D
the vss clips use an illegal packing of b-frames, which only their own decoder supports
wtf?
SHIFT-DELETE the VSS h264 video clip:sly:
Originally posted by Yong
@rushin_911:
@echo off
IF '%1'=='' GOTO EOF
title X264 Encoder
start /belownormal /b /w X264 -p 1 --stats "%userprofile%\desktop\X264[%~n1].log" -o nul: %1 --progress
start /belownormal /b /w X264 -p 2 --stats "%userprofile%\desktop\X264[%~n1].log" -o "%userprofile%\desktop\%~n1.mp4" %1 --progress
pause
:EOF
save the above code to "x264.bat"
u can try to add other cli option if u need like, --b-pyramid, --weightb and --subme 5.
A few questions from a commandline noob :) :
- -o nul: : what is this doing? I hope it makes encoding faster
- %1 : is this for a avisynth input? :rolleyes: Can I start the skript somehow just with making an avisynth-skript and start this skript :confused:;)
Thanks for you help.
Tommy Carrot
2nd May 2005, 15:32
Originally posted by JoeBG
A few questions from a commandline noob :) :
- -o nul: : what is this doing? I hope it makes encoding faster It means it doesn't create output file in the first pass.
- %1 : is this for a avisynth input? %x (x can be 1-9) is external parameter for the batch file, in this case the input filename.
Originally posted by Tommy Carrot
It means it doesn't create output file in the first pass.
This is really helpful, many thanks :)
Originally posted by Tommy Carrot
%x (x can be 1-9) is external parameter for the batch file, in this case the input filename.
How can I use this? To make an example: I have my avisynthskript and I want to use the batchfile for creating an output with the same name like the avisynthskript. Can do this? And how does it work?
Sorry for bagging you :(
Tommy Carrot
2nd May 2005, 18:56
Originally posted by JoeBG
How can I use this? To make an example: I have my avisynthskript and I want to use the batchfile for creating an output with the same name like the avisynthskript. Can do this? And how does it work?
The most simple way is if you give the same parameter to the input and output field. Using the previously posted batchfile, this would be like this:
@echo off
IF '%1'=='' GOTO EOF
title X264 Encoder
start /belownormal /b /w X264 -p 1 --stats %1.log -o nul: %1.avs --progress
start /belownormal /b /w X264 -p 2 --stats %1.log -o %1.mp4 %1.avs --progress
pause
:EOF
The only problem is that this way you must specify the input name without the extension, for example with "plan 9 from outer space.avs" the command line is:
x264.bat "plan 9 from outer space"
without the avs extension.
dude051
2nd May 2005, 19:07
A more useful bat file in my opinion, lets you set input, output, stats log file and bitrate. Here's what I use.
@echo off
start /belownormal /b /w x264 -p 1 --stats %3 -o nul: --progress %1
start /belownormal /b /w x264 -B %4 -p 2 --stats %3 -o %2 --progress %1
Using it is simple, just use the command
start x264.bat AVS_Name.avs Output_Name.mp4 Stats_Log.log ##bitrate##
And you should include the .avs extension... you only place quotes ("") around the name if the name includes any spaces. To simplify, keeps your naming down to one word or replace spaces with underscores ( _ ).
@ dude051 & Tommy
This is impossible to use for people without DOS knowledge. Open questions are:
@ Tommy
How to start the batchfile. I can create the *.bat and I can save it but noone would ever explain to use it because DOS knowledge seems to be pre-condition. People without DOS knowledge canīt use x264. But I really would like to :)
@ dude051
Originally posted by dude051
Using it is simple, just use the command
start x264.bat AVS_Name.avs Output_Name.mp4 Stats_Log.log ##bitrate##
This is really not fair without instruction to use. But itīs nice that you tell us that you can do this :)
@ All
My question is not o.k in this threat here, but I hoped for help. So forget about it. :)
dude051
2nd May 2005, 20:01
all you do is create a bat file, in your favorite text editor. Save it as .bat. Bat files are executable, so all you have to do is double click and it will run the commands within it in a DOS window for you. You can either goto Start> Run > Type : cmd , and then type the commands by hand, or make a couple of bat files to do it all for you. Simply enough, place the first set of codes to execute X264.exe in one bat file:
@echo off
start /belownormal /b /w x264 -p 1 --stats %3 -o nul: --progress %1
start /belownormal /b /w x264 -B %4 -p 2 --stats %3 -o %2 --progress %1
Save this as x264.bat
Then create another bat file, with the second set of code:
@echo off
start x264.bat AVS_Name.avs Output_Name.mp4 Stats_Log.log 1000
Bitrate is the last value and is set in Kbps. Save this as encode.bat
Then all you need to do is run encode.bat ( by double clicking it) and it will execute X264 with the commands from x264.bat.
The available commands to X264 can be gotten from running the -h flag... but here:
x264 core:23 svn-215M
Syntax: x264 [options] -o outfile infile [widthxheight]
Infile can be raw YUV 4:2:0 (in which case resolution is required),
or AVI or Avisynth if compiled with AVIS support (yes).
Outfile type is selected by filename:
.264 -> Raw bytestream
.mp4 -> MP4 if compiled with GPAC support (yes)
Options:
-h, --help Print this help
-I, --keyint <integer> Maximum GOP size [250]
-i, --min-keyint <integer> Minimum GOP size [25]
--scenecut <integer> How aggressively to insert extra I-frames [40]
-b, --bframe <integer> Number of B-frames between I and P [0]
--no-b-adapt Disable adaptive B-frame decision
--b-bias <integer> Influences how often B-frames are used [0]
--b-pyramid Keep some B-frames as references
--no-cabac Disable CABAC
-r, --ref <integer> Number of reference frames [1]
--nf Disable loop filter
-f, --filter <alpha:beta> Loop filter AlphaC0 and Beta parameters [0:0]
-q, --qp <integer> Set QP [26]
-B, --bitrate <integer> Set bitrate
--qpmin <integer> Set min QP [0]
--qpmax <integer> Set max QP [51]
--qpstep <integer> Set max QP step [4]
--rcsens <integer> CBR ratecontrol sensitivity [10]
--rcbuf <integer> Size of VBV buffer [0]
--rcinitbuf <integer> Initial VBV buffer occupancy [0]
--ipratio <float> QP factor between I and P [1.40]
--pbratio <float> QP factor between P and B [1.30]
--chroma-qp-offset <integer> QP difference between chroma and luma [0]
-p, --pass <1|2|3> Enable multipass ratecontrol:
- 1: First pass, creates stats file
- 2: Last pass, does not overwrite stats file
- 3: Nth pass, overwrites stats file
--stats <string> Filename for 2 pass stats ["x264_2pass.log"]
--rceq <string> Ratecontrol equation ["blurCplx^(1-qComp)"]
--qcomp <float> QP curve compression: 0.0 => CBR, 1.0 => CQP [0.60]
--cplxblur <float> Reduce fluctuations in QP (before curve compression) [20.0]
--qblur <float> Reduce fluctuations in QP (after curve compression) [0.5]
-A, --analyse <string> Analyse options: ["i4x4,p8x8,b8x8"]
- i4x4
- p8x8, p4x4, b8x8
- none, all
--direct <string> Direct MV prediction mode ["temporal"]
- none, spatial, temporal
-w, --weightb Weighted prediction for B-frames
--me <string> Integer pixel motion estimation method ["hex"]
- dia: diamond search, radius 1 (fast)
- hex: hexagonal search, radius 2
- esa: exhaustive search algorithm (slow)
--merange <integer> Maximum motion vector search range [16]
-m, --subme <integer> Subpixel motion estimation quality: 1=fast, 5=best. [5]
--no-chroma-me Ignore chroma in motion estimation
--level <integer> Specify level (as defined by Annex A)
--sar width:height Specify Sample Aspect Ratio
--fps <float|rational> Specify framerate
--frames <integer> Maximum number of frames to encode
-o, --output Specify output file
--no-asm Disable all CPU optimizations
--no-psnr Disable PSNR computation
--quiet Quiet Mode
-v, --verbose Print stats for each frame
--progress Show a progress indicator while encoding
--aud Use access unit delimiters
You then just add these flags (things with - or -- by them) along with their associated value by adding/changing them in the first bat file, x264.bat. An example would be close to:
start /belownormal /b /w x264 -I 300 -i 30 -b 2 -B %4 -w --b-pyramid -p 2 --stats %3 -o %2 --progress
If you are this scared about using the command line, then I suggest you use the VFW version via VirtualDub or something. This CLI version is a bit more advanced... but is not too complicated once you work with it.
I have to ask.. why waste time with batchfiles when MeGUI offers you all x264 options, more codecs, more output options, more automatism, jobs, profiles, etc? A lot of the complexity in MeGUI stems from the fact that I try to cater to an advanced audience that could handle batchfiles and such, but why bother with it if you have a GUI tool that can do a lot more?
dude051
2nd May 2005, 22:16
I actualy have nothing against MeGUI, but I was looking into the CLI version of x264 specifically because I was having errors in vdub with some random crashes. No more crashes or memory leaks since i started with the CLI version. I recently haven't had the time yet to look into MeGUI. Looking into it now actualy and im gonna give it a try.
Thanx :sly:
Edit:
I have to give ya the extreme credit, MeGUI is the holy grail... great stuff! I love it so far.
Later
Originally posted by Doom9
I have to ask.. why waste time with batchfiles when MeGUI offers you all x264 options...
A few months ago I asked for my first commandline (mp4box) in the german doom9. The answer was: go to "VHS" (which is a kind of school for adults).
Since then I want to learn more about this. :) And MeGUI is the best!!!
I'm getting a bunch of
x264 [error]: Error: 2pass curve failed to converge
x264 [error]: target: 1450.00 kbit/s, got: 1387.39 kbit/s, avg QP: 10.0023reported from various MeGUI users.. I was wondering, would it be possible to have an option that automatically lowers the min QP in such a case (or start encoding anyway and just dump a warning rather than exit)?
akupenguin
3rd May 2005, 09:35
Done. It will still complain, but produce undersized encodes instead of aborting. (If you want the min to be automatically set... just use qp_min=0.)
x264 [error]: Error: 2pass curve failed to converge
x264 [error]: target: 1450.00 kbit/s, got: 1387.39 kbit/s, avg QP: 10.0023
IIRC i only get this kind of warning if transcode WMV without -fps xx options in Mencoder.
The default -fps value for WMV in mencoder is 1000fps:rolleyes:
Chainmax
3rd May 2005, 16:53
So, does MeGUI allow for access to all of x264 CLI's options? I find x264 CLI a bit daunting after looking at Saggitaire's example batch files and would love something more simplified.
rushin_911
3rd May 2005, 19:57
Originally posted by Yong
@rushin_911:
@echo off
IF '%1'=='' GOTO EOF
title X264 Encoder
start /belownormal /b /w X264 -p 1 --stats "%userprofile%\desktop\X264[%~n1].log" -o nul: %1 --progress
start /belownormal /b /w X264 -p 2 --stats "%userprofile%\desktop\X264[%~n1].log" -o "%userprofile%\desktop\%~n1.mp4" %1 --progress
pause
:EOF
save the above code to "x264.bat"
u can try to add other cli option if u need like, --b-pyramid, --weightb and --subme 5.
Hey Yong... Thank you for this :) (sorry for my late response)
does MeGUI allow for access to all of x264 CLI's options?No, there are a few missing (not exposed in mencoder) but I'm pretty sure you won't miss any of them. You really don't need stuff like level, debug, psnr, etc.
@aku: I noted something else.. if you give x264 an empty stats file, it'll throw a curve convergence error.. shouldn't this rather be a "your stats file is invalid"?
Sagittaire
11th May 2005, 21:28
and RDO patch ... ???
Neo Neko
12th May 2005, 03:33
Originally posted by Doom9
No, there are a few missing (not exposed in mencoder) but I'm pretty sure you won't miss any of them. You really don't need stuff like level, debug, psnr, etc.
If you get time could you add controls on the interface for the -aspect switch in mencoder. Sure I can just paste it in via the comandline builder. But it would IMO make an already excelent tool just a bit better. ;)
baer999
12th May 2005, 17:47
Wow I thought the developing is stopped, but now there are a few more versions, my question is:
+ Won a bunch of cycles by not trusting gcc about inlining and
unrolling properly
(about 17% faster globally)
What is 17% faster ? The encoding ? Because i don't know whats is meant by globally :)
akupenguin
12th May 2005, 17:56
What does x264 do other than encode? "globally" is benchmarking the whole program, as opposed to listing the speed improvements of one subroutine.
JoeBG
12th May 2005, 18:05
Originally posted by baer999
Wow I thought the developing is stopped, ...
A nightmare.....:rolleyes:
@ akupenguin
I hope youīre ok? Everything ok with you and your family? :sly:
Doom9
12th May 2005, 19:03
If you get time could you add controls on the interface for the -aspect switch in mencoder. Sure I can just paste it in via the comandline builder.I'll put it into the (already long) todo list. Can't promise it will be in the next version as there is quite a bit of new stuff scheduled already.
JoeBG
13th May 2005, 15:26
What makes "--seek" and how do I use it?
Edit:
Itīs for stopping the encoding, sorry, I was too fast with this post :(
Kurtnoise
18th May 2005, 09:53
Does the --vizualize command work only on Linux/Unix systems ?
I try to compile x264 on win32 platform with some X11 headers but without success...
Sharktooth
18th May 2005, 10:15
*nix only :(
Kurtnoise
18th May 2005, 11:19
shame yeah...maybe someone can try with a cross-compile ?
bill_baroud
18th May 2005, 12:40
well if you need a X11 client, you're somewhat screwed on windows... i think i remember something about one, but it wasn't free iirc.
Originally posted by bill_baroud
well if you need a X11 client, you're somewhat screwed on windows... i think i remember something about one, but it wasn't free iirc.
Actually you need an X server (applications are clients) and the free and Open Source Cygwin environment has X.org, see http://x.cygwin.com/
You'll just need to figure out how to compile x264 under Cygwin so that it finds the X headers and libraries.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.