Depreciation Calculator. If you are looking for an affordable fixed asset depreciation program that calculates depreciation using both tax and GAAP (financial statement) depreciation methods and produces easy to read depreciation schedules, then our Depreciation Calculator software is an excellent choice. Other depreciation programs have a.
Update: This was originally written back in Feb 2016, and the libraries I supplied back then are now too old for newer versions of HandBrake and likely won’t work or will have issues. I built a new Mac version on July 3rd 2017 which is below, and fortunately there are now good alternate options for Windows/Linux. Details as follows:.
If using Windows, under the Windows section below I have a link to the Handbrake forums where they provide updated libraries. The 10-bit-only CLI version I have linked in the Windows section should work too, but it’s old. If using Linux, Stephen Smith was kind enough to mention in the comments that the x265 libraries are now available on Ubuntu ( apt-get install libx265-dev ).
Use that (don’t follow the rest of the instructions in the Linux section). I suspect other distros have variants available, and there’s also the Fedora repo listed in the Linux section. If using Mac OS, the original (2016) and newer (2017) 10-bit-only builds should work. I wouldn’t suggest using the.dylib option, as those.dylibs are from the original write-up and quite old now. The original write-up is still below, but keep the above in mind. I recently got a Tronsmart Vega S95 (media player) which claimed to support 10-bit HEVC encodes. Unfortunately, I didn’t have any 10-bit encodes on hand to test out those claims with!
Short version is that I wanted to get 10-bit encoding working with HandBrake on OS X. Long version ends with figuring it out on Linux and Windows too because I figured it’d be helpful for people who don’t have 3 OS’s to swap between. These are the results: Before somebody decides to encode their entire library in 12-bit HEVC and ends up utterly disappointed, once you’ve grabbed whatever info/files you want for your OS, scroll down waaaaaay to the end and have a read. Okay, so one at a time, here we go Mac OS X You basically have 2 options here:. A separate 10-bit version (which I’ve included in the writeup) that you can run beside your current HandBrake install.
Use the “nightly” HandBrake, and manually install some library files (which I’ve included at the end). Option 1 I compiled a 10-bit version (both x264 and x265). Just download it, unzip, throw it in your Applications folder if you want, and run it (the same way you’d run your current version).
A few notes on it:. It’s the easiest/cleanest option.
If you decide to get rid of it, uninstalling is as simple as dragging to the trash. It’s ONLY 10-bit. So don’t go un-installing your current version. For x264 encodes, you must change the Profile to “high10” (not auto), or the encode will instantly fail. Don’t “check for updates” or anything, because if it actually finds an update, it’ll be from the HandBrake website (and for the standard 8-bit version most likely). The 2016 version was built on “El Capitan” (OS X 10.11.3), and 2017 version on Sierra. I didn’t muddle through things to see what the minimum OS version was set.
So if you’re using an older version of OS X, it may or may not work, but feel free to leave a comment if you try. If you’re interested, you can grab it here: — Option 2 I compiled some x264 and x265 libraries for 8/10/12-bit support that will work with the latest “nightly” version of HandBrake.
You can grab it from the main HandBrake website at: ( note: you are after the result that does not have “CLI” in the file name) Get it installed (you can sit it beside your regular version if you want). Next, you have to download the libraries I’ve packaged together: Unzip the handbrake-libs-mac.zip file and you should have a new folder called “handbrake-libs-mac”, with contents that look like this: Those are the library files that you need to install on your system. For HandBrake to see them, they have to go in the /usr/local/lib/ folder, which is hidden from the Finder by default. If you’re comfortable in the terminal, a sudo cp will likely do it.
Otherwise, you can tell Finder to manually go to the correct folder by opening a new Finder window and clicking “ Go” from the top menu, then “ Go To Folder“. A few images below to help ( click for larger versions): Basically, drag the libraries you downloaded into the /usr/local/lib/ folder and you should be good to go! Note that technically you only need to copy the 3 that have a “10” or “12” in the filename if you’re using the HandBrake nightly build (since it already contains the standard 8-bit versions built-in), but it shouldn’t hurt anything to just copy them all.
Now open up HandBrake (or exit/restart if it was running). You should now have access to 8/10-bit versions of x264 and 8/10/12-bit versions of x265! A few notes:. 10-bit x265 might immediately crash on the slowest settings (slow, veryslow, etc). The separate 10-bit-only version I compiled above doesn’t seem to suffer from this issue, so you may want to use that if you’re doing x265 10-bit at those speeds. On my machine, the x264 10-bit version was often coming up as the default selection.
If you’re in the habit of just assuming x264 8-bit is the default, make sure you double-check before you hit encode!. At some point, there will undoubtedly be new versions of x264 and x265. When that happens, the ones you installed will be a bit dated, so keep that in mind. They don’t auto-update or anything. — — Linux A quick note for Fedora/RHEL users has a HandBrake repo and they now have the 8/10/12-bit stuff enabled there.
I strongly suggest just adding their repo if you’re on one of those distros. These instructions are primarily for Ubuntu, though other similar (debian-based) distros should work. Non-debian-based distros should be doable if you can locate a program that converts.deb packages to whatever you need (for example, is common for converting from.deb to.rpm). Anyway, let’s get on to it. Step 1 – Grab/Install the Latest Nightlies If you’re using a supported version of Ubuntu, follow the instructions for installing the PPA at:.
Basically, the commands (if you’re both lazy and trusting) are: sudo add-apt-repository ppa:stebbins/handbrake-git-snapshots sudo apt-get update sudo apt-get install handbrake-gtk If NOT on Ubuntu but are on another Debian-based distro, you can still manually download one of the packages in.deb format and install it. Head to:, expand one of the down arrows – generally the top arrow if you’re on a fairly recent version of your distro, and grab the.deb that includes “gtk” in the file name (the “amd64” variant for 64-bit). Incidentally, this is also what you’d do if on a non-debian-based distro and were using a package converter. Then try and install the package – if you don’t have a built-in package manager, you can usually do it from the command line with sudo dpkg -i theFileName.deb Okay, let’s assume you got it installed, and it runs (just type “ghb” in a Terminal if it doesn’t show up with your applications). — Step 2 – Install the 10/12-bit Libraries I’ve built the libraries for linux, and you can grab them here: Extract them, and you should have 5.so files, somewhat similar to the earlier Mac screenshot.
Now you just have to copy them to your library. For Ubuntu, your library location is usually: /usr/lib/x8664-linux-gnu/. For Fedora, your library location is usually: /lib64/. For others, you’ll probably have to look around. It could be one of the 2 shown above, but you’re best to check first. Chances are if you run across a location that has “lib” in the directory structure and contains a zillion.so files, you’ve found the right place. The file managers in Linux have a tendency to refuse access to root folders rather than asking for privilege escalation, so chance are you’ll have to copy from a terminal/shell window.
Fire up “Terminal” or something similar, and navigate to the location you unzipped the 5 files. Do a quick “ls” to make sure you’re in the right place. For example: cd /Downloads/handbrake-libs-linux/ ls -l (should show the 5.so files if you’re in the right place) Next, you’ll have to copy them to the library location mentioned above. As an example: # For Ubuntu: sudo cp -n libx26. /usr/lib/x8664-linux-gnu/ # For Fedora: sudo cp -n libx26. /lib64/ (the “-n” means no-clobber – it won’t overwrite existing files).
Assuming that was successful, try firing up HandBrake. Hopefully you’ll have all the x264 and x265 options available now! — A few notes:. Similar to the Mac instructions, you don’t actually need to install all 5.so files.
You only really need the 3 with “10” and “12” in the file names since HandBrake already will have taken care of the standard 8-bit versions. This is a bit of a “dirty” way to put the.so files in the library directory, so remember that you put them there. Usually, the system’s package manager has some idea about which packages are throwing what in there, but since you’re brute-force-copying, that might throw a wrench into things down the line. If you’re comfortable with sym-linking, a slightly cleaner way to do this would be to add version numbers to each of the files (.so.148) and symlink to.so, which is what most packages do to help keep things at least somewhat organized. I didn’t include any pre-built versions (just the libraries) – it just caused too many dependency headaches on fresh systems if HandBrake wasn’t installed at some point anyway. It also depended on the x264 library being installed anyway.
If somebody really needs the binary, ask in the comments and if I haven’t wiped the VM yet, I’ll see what I can do. — — Windows — Update: It looks like the Handbrake devs have Windows DLL’s available that you can simply use with the current nightlies for 10-bit support (x264 and x265) and 12-bit support (x265). The page on their forum that carries them is:.
I haven’t tried them myself, but would imagine they just get plopped into your Handbrake directory. You need to use the nightly version of Handbrake though ( ). In the event that the links end up broken at some point in the future (or you don’t have 7zip installed), I rezipped them (.zip format) and you can grab local copies from here: (x26 4 10-bit) (x26 5 10-bit) (x26 5 12-bit) Those DLL’s are probably the best solution for the vast majority of situations. Feel free to leave a comment whether it works seamlessly for you, or if you hit issues. Note that Lazarus also came across a GUI solution in the comments below which you can jump to here:. The remainder of my original write-up is below anyway in case you’re curious, are doing something a little different, or are looking for the CLI bit — Visual Studio hates me (and now I hate it back), so I was only able to get the CLI version done. I did build the libraries for the GUI version, but we’ll just do the CLI bit now and talk more about the GUI stuff later.
The 10-bit CLI version I built can be grabbed from here: Extract it, and you should have a HandBrakeCLI-10bit.exe program that can be run from the command prompt. It supports both 10-bit x264, and 10-bit x265.
It also ONLY supports those x264/x265 variants, so if you’re using the standard 8-bit CLI, you’ll still want to keep it around. It’s critical that when using it, you specify the encoder-profile. For example: HandBrakeCLI-10bit.exe -i inputVideo.mp4 -o newVideo.mp4 -e x26410bit -encoder-profile high10 HandBrakeCLI-10bit.exe -i inputVideo.mp4 -o newVideo.mp4 -e x26510bit -encoder-profile main10 The important bits are: -e x26 4-10bit –encoder-profile high10 (for x264 10-bit) -e x26 5-10bit –encoder-profile main10 (for x265 10-bit) if you don’t include the encoder profile, it will.fail. As to the rest, if you’re new to using the CLI, you’re best to browse through the guide at: Alternately you can type “ HandBrakeCLI-10bit.exe –help” to see the options, but it’ll completely fill your screen. You can save all that text to a file instead to read with Notepad later with “ HandBrakeCLI-10bit.exe –help hb-help.txt” — The GUI bit on Windows As I alluded to earlier, I did get libraries made up for the Windows GUI version.
Unfortunately, they didn’t seem to work with the current nightly version (it reads them, but doesn’t display the additional x264/x265 options). I’m guessing either:. The nightly build from Feb 13th missed the patch (from the same day) that enabled 10/12-bit DLL support in the Windows GUI (hopefully). Something built wrong on my end (hopefully not). Due to the Visual Studio hatred mentioned previously, I haven’t tried building the GUI myself from the patched source yet. In any case, if you’re building from source yourself or are quicker at finding the new nightly than I am, the 8/10/12-bit x264/x265 libraries that I built can be downloaded from here: They go in the same directory as the HandBrake Nightly.
Usually this is C: Program Files HandBrake Nightly. For reference, the nightly I tried (unsuccessfully) was HandBrake- b7cb7d6x8664-WinGUI.exe. Only try these libraries on a newer version. Keep in mind that because adding libraries to the Windows version would be remarkably clean compared to linux/mac (they could just be included with the program files on Windows!), it’s within the realm of possibility that the HandBrake devs might just add the libraries to the install itself at some point. — — A Note on HandBrake and 10-bit Encodes At the beginning I mentioned that it might be a good idea to scroll waaaaay down before someone goes off and encodes their entire library at 12-bit HEVC. There are a number of reasons NOT to encode via 10-bit and 12-bit in HandBrake.
It’s worth mentioning that the builds/libraries above should be considered somewhat “experimental”. It’s within the realm of possibility that something won’t work correctly (or at all). Don’t be quick to blame HandBrake or x264/x265 if you’re running into issues – I could have very well missed something when compiling. If you copied the libs on Mac or Linux, be sure you’ve got some idea as to where you stuck the libraries too, just in case they conflict with something and/or you want to remove them later.
Why NOT to use 10-bit and 12-bit First of all, HandBrake’s entire toolchain is set up for 8-bit 4:2:0. Basically that means if you have a source that’s 10-bit 4:4:4, by the time HandBrake spits it out at the end, it’s probably going to have been reduced to 8-bit 4:2:0. There’s not a whole lot you can do about that, and there aren’t any simple “switches” that the developers can really flip either. They may be able to migrate over time if they want to go that route, but it’s a.really. large code-base that relies on a lot of external tools they don’t necessarily have a lot of control over. The next problem is that device support is minimal at best.
For x264, you’ll have a hard time finding a phone/tablet/device that’ll play 10-bit video. Often, devices that.try.
to decode it in hardware will have the colour palette looking super-saturated. You’re generally limited to computer playback. For x265 (HEVC), it wasn’t until the end of 2015 that devices started trickling out that could handle 10-bit.
There’s also a wonky situation going on with some of the latest stuff where you get devices that claim 10-bit HEVC and 4K display, but in actuality can either do 10-bit at lower resolutions (1080p), or 8-bit at 4K. Really, unless you’ve literally upgraded all the phones, tablets, and media players in your household within the last few months, chances are that moving to 10-bit encodes is going to leave some of your devices out. There’s also the time issue. 10 and 12-bit encodes tend to take longer (in test encodes while building the stuff above, a 10-bit x264 encode also sucked up a surprising amount of RAM).
Really, you’re “paying” a lot (time, device support, etc), with not a whole lot in return. That being said Pros to 10-bit? Efficiency and Banding?
10-bit x264 has been common in the anime community for quite some time due to a reduction in banding. I haven’t heard whether the same is supposed to hold true for x265 10-bit (I’m not sure why it wouldn’t), so I’ll leave you to do your own research and draw your own conclusions there. There’s also a notion that 10-bit is more efficient (even with an 8 bit source), probably as a result of the document here:. — There may be good cases for using 10/12-bit, but at the same time, it’s not something that comes “free” and it’s a little tough to quantify. My best advice would be to run your own test encodes back-to-back and decide for yourself. Hopefully the libraries above will help you do just that 🙂. Hey Toxic, For x265, there are some brief instructions.
If I remember correctly, the general process (while following the steps in the link) was something like this: For Linux, basically once the dependencies are dealt with, it’s a matter of running the shell script – build for 8-bit, pull your.so out, make clean, build for 10-bit, pull your.so out, make clean, etc. OSX was really similar except that you have to manually download and install yasm & cmake first. CMake comes as a GUI program, but has a drop-down option which shows how to add it to the path. Windows was a little more tricky. It’s built on Linux via MinGW.
I didn’t have luck with MinGW from the Ubuntu repo when I was working on the HB binaries, so I manually built that one from source following the one used in the HB guide (the source may be a it on the older side) and just used that one when attempting the libraries. Once everything is in place, to build the libraries, there’s a shell script at x2651.9/build/msys/ which will probably handle that I actually missed it at the time so I ended up creating a script that dumped all the settings in as cmake options – it’s quite possible that if the libraries I built don’t work, just running the included script.will. — For x264, I don’t recall things being drastically unexpected on Linux or OSX – a “./configure” where I manually plugged in configure options (–bit-depth=10 –chroma-format=420, etc). For the windows build, I just now skimmed through some of the scripts I had thrown together and I believe I used something like: #!/bin/bash export PATH=/mingw/bin:$PATH./configure -bit-depth=10 -chroma-format=420 -enable-shared -enable-static -disable-cli -host=x8664-w64-mingw32 -cross-prefix=x8664-w64-mingw32- — I know that’s not a complete guide by any means, and being done from memory might be even less reliable. Depending on what you’re building for, hopefully it’s enough to get you started. One thing I ran out of time to experiment with (but might be worth exploring) was seeing if the multilib.sh builds would work – the immediate benefit there would be that you’d only have 1 library to deal with if it.did.
work. A possible benefit further down the line would be that if it can be statically linked to a HB build (not sure), maybe it could even be embedded into a HB build (though to fire off a script, it may not be as easy as a contrib/x265/module.defs edit). — Anyway, hope something in there helps! Windows, Mac, or Linux? The Mac/Linux variants should hopefully still be working, but when I wrote this up the Windows GUI variant at the time didn’t have the code to expose the options so I wasn’t able to test the libraries out on it (hence the provided CLI version since it was my only option for Windows at the time). Try removing the libraries and see if the 10 minute delay goes away (I suspect it will). Alternately you could try just using 1 library at a time to see if specific one(s) work/don’t.
Let me know which OS you’re working with and if I get some time I’ll try to poke around some more. Hey Jon, The FDK codec (which provided HE-AAC for Windows/Linux versions of HandBrake) has been dropped from recent binary versions of HandBrake due to license issues. Options if you really need HE-AAC:.
Compile from source and use “–enable-fdk-aac” (or edit make/configure.py and change the default setting). Use the Mac OS X version of HandBrake (which uses Apple’s AAC and HE-AAC encoder and didn’t need/use FDK anyway). If you don’t need to use the 10-bit libraries and just really need HE-AAC, you could search around for an older version of HandBrake, including any nightly builds from before Feb 10/2016. Everyone’s technically supposed to stop distributing versions. I figured out a workaround to your Windows GUI problem. Or rather stumbled on it by accident.
If your release version of Handbrake has main10 as an option, select it and create a user preset called x265 10bit or something. (note, though it shows main10 as an option in my release version of Handbrake, it does not actually encode in 10bit if I select it, it still comes out 8 bit. It seems the option was put there before it was actually functioning). After creating this preset, I opened your handbrake-cli-10bit-windows.zip from above, renamed it to HandBrakeCLI.exe and just copied that into the Program Files/Handbrake over the existing version. When you open handbrake there is no option to select the profile like you say, UNTIL I click on my x265 10bit user preset then that option appears.
This is probably not how it is supposed to work, but the final video encode is 10bit according to mediainfo so it seems to work just fine. (thank you SO much for sharing this file. I spent two days trying to figure out how to get 10bit x265 encoding using ANY software and this was finally my best option. I just got a Nvidia ShieldTV and its replacing my htpc and it has x265 10bit decoding support so I want to finally get around to archiving all my anime dvd’s before they start dying, some are already giving errors, yikes!).
I had been trying to figure out how to get rid of the gradient banding on things like a dark sky due to the 8 bit limited color range and this trick has done the job beyond expectations. No more artifacts even at RF18 in Handbrake 0.10.5 and on the Ultrafast preset!
I tried the nightly build with the 10bit dll pack but encoding took twice as long and resulted in much bigger file sizes with no visible improvements. I also tried encoding in 12bit but the resulting file was just a green screen. Many thanks to you for sharing this solution and to Matt for his hard work providing this wonderful resource. Cheers from Osaka, Japan! i7 4770 16GB GTX970 Windows 10 64bits.
Sorry, goofed on the 2nd screenshot. The text (and 1st screenshot) should be accurate: /usr/local/lib. Note that /usr is hidden by default, hence the need to manually head there via “Finder Menu / Go / Go to folder”. I’m on El Capitan also, but if /usr/local/lib doesn’t exist on your machine, you could always try creating it (hopefully /usr/local already exists), toss them in, and see if that works. If not, you can try sticking them in /usr/lib and give that a try it’s the system-wide lib folder. Unfortunately, you’ll probably run into an SIP (System Integrity Protection) error unless you’ve disabled SIP it protects everything in /usr with the only exception being /usr/local. You may also need to change the ownership of the files to root+wheel once they’re in /usr/lib/ for this option to work.
So this option has the potential to get really messy quite possibly more messy than you’re willing to deal with. If even.that. doesn’t get you some progress, browse around /usr/local and see if there’s another location that’s full of.dylib files and you might get lucky by tossing them in there. As a last resort, you could try adding them to a path folder (type “echo $PATH” in terminal to see which directories are included in the system path), but I don’t know if the paths are included when searching for library files so unsure whether that’ll work.
I know it’s a lot of trial-and-error, but hopefully something there helps. If you trial-and-error something that doesn’t work, it’s probably worth undoing the change to keep your system from getting all cluttered with files all over the place.
Keep in mind I’ve also got the 10bit-only version of HB linked up there for download which is a couple months dated now, but is always an option if all else fails since the 10-bit libs are built into the binary and it doesn’t require the separate.dylib files at all. As a novice, less than a year at this, I have this question.
In August 2016 Windows broke x264 for usb devices in favor of yum so their APPS would be more efficient. There are work arounds. I know it broke my ability to watch live TV on my USB Hauppauge TV tuner until I did the registry hack.
However things recorded ok. I think the biggest media reports are emphasizing how Windows broke webcams but it goes farther than that. Is x264 dead now that Windows decided to break USB devices and should we start going in a different direction when we transcode/reencode/convert? I don’t know what the long term implications are. I know your site has helped me save quality and reduce the size of my recorded TS streams using Handbrake. I use HandbrakeCLI and a post processing batch script in NextPVR for my video “jukebox” and watch on Roku and other DLNA’s appliances. I just got comfortable with Handbrake even have my patch script change the HandbrakeCLI commands based on HD and SD channels to improve quality.
Depreciation Software Programs
I don’t use the PC much to watch TV, so this concern may be nothing. I am considering leaving Windows on my PVR box but I am comfortable with NPVR as my backend and frontend. Hey Paul, I actually hadn’t heard about that Windows issue until you brought it up. The first news article I came up with was (for anyone else following). I wouldn’t worry about it having long-term implications for x264.
It looks as though it’s more of an app-breaking change that they made – the app used to access the webcam/etc via H264 would now have to be rewritten to access the decoded stream via the OS instead (and the OS then does the H264 decoding itself). I think trying to.force. the OS to be the middleman here was probably a silly decision on Microsoft’s part, but hey, I suppose they can do what they want. It sounds like they’ve been promising a “fix” for some time so maybe we’ll see that come to pass one day.
All that said, H264 (and by extension, x264) is probably one the most widely used formats today, and really isn’t at risk of being killed off by any 1 company. I’m sure it’ll be.depreciated. one day (superseeded by HEVC/H265/x265 and/or VP9 and whatever comes after), but forcibly killing it off before it’s time would probably take nothing less than an industry-wide effort (along with a compelling reason to actually do so). I agree forcing the OS to be the middleman of other applications is not a good thing. I like multiple applications sharing the decoding at the same time but I think they should do it across the board, at least most widely used codec. I’ve read many complaints by industry engineers on how this has broken their applications.
Interestingly, Microsoft has an alternative application solution to each broken app and it’s usually one of theirs. I am glad 264 is here to stay for a while. Sorry to sideline this post but since it was dealing with the new codecs (x265) I thought it was the best one to bring it up on. Thanks again. The x265 (and x264) encoders in HandBrake are software-based encoders. Thus, they’ll run on just about anything from Skylake to the 10-year old Core2Duo processors.
They’ll also run on ARM based devices, numerous AMD processors, even older Intel processors than I’ve mentioned, etc. Basically, they’ll work on anything that compiles the code.
So yes, you can certainly encode 10-bit HEVC on a Skylake. Chances are that every computer in your household will do it – older ones might be painfully slow at it, but it’ll work just fine.
The hardware-based encode/decode support that’s supposedly coming in Kaby Lake is basically a separate HEVC encoder/decoder integrated on the chip – it’s a different encoder, and thus encode results will likely be quite different from the results you’d get using x265. If history is any indication, it’ll probably be extremely fast and use very little CPU power, but the tradeoff is that size/quality will probably be worse than with x265. Note that even though the 10-bit HEVC encode/decode in Kaby is hardware-based, software will still have to be written/modified to actually.utilize. it – it’s not something that you’d just automatically benefit from on Day 1. VLC and other media players will probably add code at some point to utilize the hardware decoding feature. On the encoding end, it’ll probably pop up in some of the video editing tools at some point. If the HandBrake devs decide to utilize it, it’ll likely be a separate option from x265 and might be OS-specific (similar to how H264 QuickSync is only available as an encoder option in Windows builds).
Depreciation Software Free
Hope that helps! First of all thank you for this article and all the effort! I played around with your Handbreak 10bit macbuild ( ) and have some interesting results. Encodeding a h265, 10bit file with ultrafast preset (Constand Quality – RF 20) yields to a much smaller file then the “twin” with medium preset (still Constant Quality – RF20). I used one of my old Babylone 5 DVDs (Voices in the dark) – original size 3.32 GB (anyway the exact filesizes do not realy matter) Ultrafast file: 361.6 MB Medium: 523.7 MB The ultrafast file visually looks much worse then the medium one, even so both use the same Quality setting (in fact all settings except the preset setting are the same). Just to let you know. Of course if you have any idea about it feedback is welcome 😉.
It currently doesn’t seem to be officially supported, but whether that means “no client support & won’t work”, or means “client support – might work but unsupported” I don’t know. Shouldn’t be any harm in giving it a try though If on Windows, grab the DLL’s from the forum link in the write-up – if it works, great.
If it doesn’t, just delete the DLLs. If on Ubuntu, “sudo apt-get install libx265-dev”. If on MacOS I don’t know if there’s anything currently available besides my (rather old) 10-bit-only build. I’m guessing toolchain limitations still exclude doing this via HandBrake (someone can correct me if I’m wrong). If you’re willing to use ffmpeg CLI and are using x264, I believe it can be done via “-profile:v high422” or “-profile:v high444”. Unsure if 422/444 are available for x265 in ffmpeg yet, but if you wanted to pump it through the x265 CLI I.think.
it would be something like: “–profile main444-10 –input-csp i444” (change the 10 to 8/10/12 depending on bits, and 444 to 422 where applicable). There may be easier/better options out there, or someone might have a full encode string or toolchain process they use and know works. Hopefully someone can chime in if so. If not, maybe the above will help you get started.
Haven’t read all comments, but HandBrake does not do real 10bit encodings right now, even not with nightly builds and x265main10.dll. The resulting file is 10bit, right, but it’s only dithered 8bit from 10bit Canopus HQX for example since the internal bottleneck seems 8bit. I found a FFmpeg build that has real x265/main10 inside that does real 10bit I can verify in EDIUS/10bit monitor connected to a BMD IP4K using a synthetic greyramp.
FFmpeg has smooth gradient, HandBrake only shows 8bit dither even using the x265main10.dll. Unluckily that FFmpeg build is quite old (x265 v2.0). 39 Dollar Glasses (review).
Goggles4u (review). GlassesUSA (detailed info). EyeBuyDirect (review). Zenni Optical (review). GlassesShop (review).
Frames Direct (detailed info). Optical4less (review). Coastal (review). Global Eyeglasses (review). SelectSpecs (review). Eyeglass Direct (review). GreatEyeglasses (review).
Choice Eyewear (detailed info). MyGlasses (detailed info). Eyeglass Factory Outlet (review). Other Retailers. The Retailer Graveyard. Challenging Tower Defense.
Windows, Mac, and Linux. Available on Steam.