or something like that.īaldrick could no doubt correct me if I'm wrong but I do recall at the time DVDFab seemed to be blurring the line between ripping and converting.
#Dvdfab decrypter freeware free#
The free DVD decrypter didn't expire for me but if I remember correctly it was located under the DVD converter menu or the video converter menu rather than under the DVD ripper menu where I expected it to be. Maybe it's changed again but I found it a bloated mess. I tried DVDFab not so long ago and quite disliked it. I work in IT and I've been a member here for years but I have no explanation at all for how I can't get this to work for me (and others here report the same thing) but Baldrick gets it to work for him. Nobody has ever explained what sort of magic you have to do to get this to remain free forever.
#Dvdfab decrypter freeware for free#
I am completely and utterly baffled at how Baldrick can still use DVDFab for free for DVD decryption because myself and others have reported installing it and the trial window started immediately and within 30 days we had to pay if we still wanted to use it. Not necessarily anything terribly expensive, just something a bit better than the stock cooler (assuming that's what you're running).Ĭan't say I'm surprised. If the CPU is getting too hot though and you encode video regaularly, it'd probably pay to invest in a better CPU cooler. I don't have anything over the top when it comes to CPU cooling and depending on the time of year (winter or summer) and how lazy I've been when it comes to cleaning the dust out of the CPU heatsink, my CPU's operating temperature probably varies by about 25 degrees when it's running flat out. How hot was the CPU getting and how are you monitoring the CPU temperature? They can get hot when running hard. Actually VirtualDub has a "speed limit" slider but I can't say I've ever used it. I don't know of any encoder GUIs which actually have a "slow down" function, but maybe someone else does. Low CPU usage generally means there's a bottleneck in the process, which is sometimes unavoidable (for example CPU intensive filtering which isn't multi-threaded) but generally the idea is to make maximum use of the CPU. Ironically, the usual goal is to achieve the highest possible CPU usage, which in turn equates to the fastest possible encoding time. I'll see how that goes this time through. This was bad for a number of reasons including processor heat up due to high usage. Old method tried for MKV was use MakeMKV to rip the whole disk and then bring into Handbrake to do encoding.
0 kommentar(er)
