|
I use MakeMKV [^]
Using the Backup feature will create an ISO from a DVD or will decrypt a Blu-Ray to files that can be made into an ISO (using some files -> ISO tool: I use Virtual CD for that).
Or it can create mkv files from the individual videos on the DVD/Blu-ray. Like, for a movie disc, the main feature, the previews, the special features, etc. etc. etc.
I think the paid version is $30 or $35 (I'm at work and the site is blocked here)
|
|
|
|
|
+1 for MakeMKV. It appears to me to do zero transcoding, unlike some other ripping tools. This makes it relatively fast, and you get quality identical to the original source.
|
|
|
|
|
I"ve been using DVDFab for years. The US version is a bit crippled but they have versions for other countries that don't have DMCA.
|
|
|
|
|
I've used their Mac version for years. It works great. They'll keep offering you upgrades but I'll bet you never need one.
|
|
|
|
|
@DaveAuld
Have as good a day as you can, considering everything else that is going on in your life at the moment. ![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Cheers Griff,
Another lazy day in the hotel, might go for a walk to the Royal Plaza mall which is just along the road and see if there is anything in the computer shop worth buying.
Treated myself to a new phone yesterday as the one I use in Qatar was on its last legs. New one to replace my UK/Cyprus one, which itself will move to the Qatar one. It's like handing down things between siblings. Make it last longer!
|
|
|
|
|
Ouch! A hotel in a dry country for your 50th and Christmas with your family 7,000Km away? Fun ...
I assume that airlines won't touch you until you are certified fit to fly? That's about 10-21 days for a small one, isn't it?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I have access to booze should I want it, but think its too early for that since the event!
The neurologists at both medical centres and company medical team have basically agreed a short 3 hour flight to Cyprus should be fine after 14 days from the event. So probably get back to Cyprus the same day my wife and youngest return from UK.
Thing is, the airlines probably have no way of knowing, I guess it is just the 'risk' of something happening, I could go book a flight, walk out the hotel, jump on the plane and no one would be any wiser.
|
|
|
|
|
Yeah, you could ... but the risk of DVT / PE goes up quite a bit and it's likely not a good idea to risk it too early.
(My friend Jan had her stroke - a big one - eight years ago, so I know some of this stuff. She's still hard to understand, but her speech is steadily getting better.)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Happy Birthday Dave and many more.
PartsBin an Electronics Part Organizer - An updated version available!
JaxCoder.com
|
|
|
|
|
Happy Birthday!!!
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Happ birthday, and speedy recovery!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Happy Birthday Dave.
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
I need to copy current data into new Excel template, which is password protected and I don't have password.
then I googled and learned a new trick to remove this password. it is a surprise to me ...
diligent hands rule....
|
|
|
|
|
Congratulations on your new job writing clickbait headlines for tabloid newspaper websites. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
my sharing is purely technical 
diligent hands rule....
|
|
|
|
|
To close out the discussion on the uses of malloc and calloc
pseudo code
char *zs;
int MEM_WANTED = 0; // can also use #define same results
int unit_size_bytes = 8;
zs = (char*)malloc( MEM_WANTED );
zs = (char*)calloc( MEM_WANTED, unit_size_bytes );
Tests:
zs will not return NULL meaning malloc or calloc has not failed to allocate memory but will return a pointer to an undefined value.
Lesson:
If one uses malloc and/or calloc then one should first test that memory size and unit size (in case of calloc) being requested are not zero, to guarantee the call produces a proper error condition (NULL).
Note:
Tested results using GNU GCC and Visual Studio compilers.
if MEM_WANTED < 0, malloc and calloc return NULL, an expected result
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
jmaida wrote: Lesson:
If one uses malloc and/or calloc then one should first test that memory size and unit size (in case of calloc) being requested are not zero, to guarantee the call produces a proper error condition (NULL).
I disagree. The lesson is that you should read and understand the C standard. Specifically:
Quote: 7.20.3 If the size of the space requested is zero, the behavior is implementation defined: either a null pointer is returned, or the behavior is as if the size were some nonzero value, except that the returned pointer shall not be used to access an object.
Note that returning NULL for malloc(0) still requires you to know what the requested size was. malloc() and friends do return NULL if memory can not be assigned, in which case errno is set to ENOMEM. So if you get NULL back from malloc(), and you don't know the requested memory size, you need to check the value of errno. Furthermore, you also need to know that errno was not ENOMEM before you make the malloc() call, since successful library calls do not modify errno. As I understand it, calling malloc(0) is not an error, so will always succeed and therefore not change the value of errno.
Keep Calm and Carry On
|
|
|
|
|
reading the standard is not the same as the actual performance. BEWARE!
Standards are meant to broken, like rules.
My advise still holds regardless. Protect yourself.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
jmaida wrote: Standards are meant to broken
I'll get a court order to have you not come near my code ever again.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I would expand the order to include a ban on working in any engineering, engineering-related, or even a profession with agreed Best Practices. I don't want a person with such an attitude in charge of anything that could affect my life.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Not my attitude. The compiler attitude. It's the problem.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
The compiler does exactly what the standard says it should do.
You expecting the compiler to do what YOU want instead of what the standard says is the problem.
|
|
|
|
|
I understand.
I am not expecting compiler to do something it is not programmed to do.
I have bumped into compiler issues for years, especially optimizing features.
Sometimes they change and you have to adapt.
I was just taking issue with the malloc(0) return.
But, I have a way around.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Bruno van Dooren wrote: The compiler does exactly what the standard says it should do.
lol.
Err...no that is not in fact true.
Compilers are written by people. People make mistakes. People have opinions and those can end up impacting how they code something.
That applies to the users also. Even someone who has written compilers might make a mistake in interpreting a specification and then applying that to some code based on a compiler. And most programmers have not written compilers (or at most wrote a toy one in college.)
And on top of that there can be other problems.
1. The 'standard' specification did not in fact go through an actual specification standards process. (Last time I checked the Java Language standard had the exact same bugs that the very first standard did.)
2. Rigorous standards processes allow for reporting problems and ambiguities and they get used. But not all problems are resolved. And without going through (and finding) a lot of that material one is unlikely to know what happened with that.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
