Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
My word, this guide could do with some far better language.Feel free to post any changes you want here or PM them to me... actually, you are a mod
feel free to apply them to the OP.
It has nothing to do with the resolution of the display, it has to do with the dot pitch (that is, the size of each pixel with respect to your eye).Huh
with High Resolution you could get away with Higher CRF valueThat's not very wise IMO.
i learned that for 720p output i could also give it a CRF value of 29 or 30 especially on anime but still the quality looks goodQuality is subjective -- I would say it is going to look like complete crap, anime or otherwise.
Can someone explain the benefits of the 10 bit depth?Better compression/quality at the same bitrate. It is also helpful with preventing artifacts like banding.
Will it cause issue swith VLC or WD HD Live Media Player?Yes, neither will play it (yet). FFmpeg is getting a 10-bit decoder soon; however, which will allow VLC to play 10-bit files.
Will there be a 8-bit & 10-bit seperate build for now on, or a cmdline switch in the future?It will likely stay a separate build given how fundamentally different 10-bit is from 8-bit. (Correct me if I'm wrong)
is there aswitch I can use with the presets to enable it?Nope, just grab a 10-bit build. Good luck finding one
For example, due to the recent MPEG-LA thing, one poster commented that if he's going to talk about licensing, then he should practice what he preach by licensing from Bandai the right to use the "Spike Spigel" character in his DGIndex page. Two hours later that post was gone, deleted by him perhaps. Of course, Spike Speigel on his DGIndex page is now replaced by pictures of leaves.Of all the stuff he does, things like that bother me the most -- very deceptive that one.
That be the one,how are you?In that case, welcome to Doom10!
Can I copy this "quote" and put it in the cmdSure can, but as Desbreko said, you'll need to locate x264.exe.
(thanks kemuri_9!), no need for avisynth).x264 --preset slower --tune film --crf 18 --level 41 --output "C:\EncodedMovies\EncodedVideo.mkv" "C:\Blurays\00001.m2ts"--preset can be anything from
If I set a GOP of 30 and 3 or 2, it will give me a buffer underflow error, so I think the GOP has to stay low.A shorter GOP should be a slightly worse for VBV, so I highly doubt that is the cause. BTW - Are those buffer/maxrate values for DVD or something, Blu-Ray can handle a much larger maxrate and a slightly larger buffer.
Any suggestions? Also, how can I compile with ffms, lavf and mp4 support? An addition to the guide would be nice.Lavf and mp4 should be in there. As for ffms, I haven't had the time (or knowledge
) to get that figured out yet.
@LinyxI had that part right, but it wouldn't work because I didn't have it pointed to the correct location.
The above command is working on mine, and I've successfully cross-compiled x264. Did you forget to include the dash after mingw32? It should be --cross-prefix=x86_64-pc-mingw32-
You must point "/mingw" to "/path/to/cross-mingw.gcc442.generic.20091019" (not to "/path/to/cross-mingw.gcc442.generic.20091019/x86_64-pc-mingw32"!)Thanks a ton everyone for helping a noob out.
Thank You!!Code: [Select]./configure --cross-prefix=x86_64-pc-mingw32- --host=x86_64-pc-mingw32
yes, because the x86_64 target mingw is essentially a cross compiler from win32.Awesome, thanks again! I will install it on this PC and try again to see if I get better results.
(cross compilers mean they target something other than what the host is capable of)
@Linyx: Any chance of adding instructions for compiling for 64-bit? I read Komisar's instructions but they are way over my head. But his MingW build seems to be for 64-bit compiling in general, not just x264.Yes, I actually started that a day or so before your post.
TDM's GCC is a bit out of date, since the latest stable version is 4.4.2. I would suggest adding a link to Komisar's GCC builds for MinGW which are up-to-date.I apologize for not getting this information in the guide. I am going to be busy for the next few days, but then I will review this thread and update all of the relevant information (and add some info about automake and autoconf.
You forgot to add autoconf and automake to your list.
P.S.: AFAIK GCC 3.x.x isn't the recommended version anymore.
1 make "Doom10 Forum" at top of page clickable, take me to root forum"Home" and "Doom10 Forum: Digital Video Discussion" do just that...
When installing TDM's MinGW, I can't seem to install GCC 3.4.5 as recommended (always 404), and the only other option is 4.4.1. What to do?I think 4.4.1 will work fine.
Why patch AFTER configuring?Because I'm a noob, and didn't think of that. Fixed now, thanks for pointing it out.
git clone git://git.videolan.org/x264.git "C:/path/to/x264folder"patch -p1 < "Patch name goes here.diff"cd "/path/to/downloaded/git"Then./configureAnd lastlymake fprofiled VIDS="/path/to/downloadedYUV/file"See here for more on the commandline usage. After a few minutes, x264.exe will be compiled and placed in your x264 Git folder. ./configure --cross-prefix=x86_64-w64-mingw32- --host=x86_64-pc-mingw32The rest is the same as for 32 Bit. Do note; however, that you cannot use fprofiled on a 32 Bit system -- Windows obviously cannot execute a 64 bit application in a 32 bit environment. make clean then use the above instructions.