LibDriveIO release date?

[Silasqwerty]

Hello! Is there any release date planned for LibDriveIO? I've been waiting for it for a while so it can be used in other applications, but I haven't seen any news about it all recently. Does anyone know anything about that?

[st4evr]

This is the MakeMKV support forum and currently the MakeMKV software does support the Libredrive feature on supported drives. And that support is thoroughly discussed within this forum. Which was enabled (“released”) for said application quite some time ago.

So what exactly are you looking for?

What “release date” for “other applications” do you mean exactly?

Like some sort of integration between MakeMKV alongside another application? (E.g. VLC, PowerDVD, etc)

[MartyMcNuts]

Hello! Is there any release date planned for LibDriveIO? I've been waiting for it for a while so it can be used in other applications, but I haven't seen any news about it all recently. Does anyone know anything about that?

I believe that libdriveIO can be found in the source files for the Linux version of MakeMKV.

[Silasqwerty]

Hello! I do know that it is used in MakeMKV, but I mean the release of the full source code of that so it could be used in other projects! Also thank you for pointing out that the source is included for the Linux version! But as far as I can tell, it doesn't seem to be the complete library, just the "libDriveIo - MMC drive interrogation library" part.

[st4evr]

Hello! I do know that it is used in MakeMKV, but I mean the release of the full source code of that so it could be used in other projects! Also thank you for pointing out that the source is included for the Linux version! But as far as I can tell, it doesn't seem to be the complete library, just the "libDriveIo - MMC drive interrogation library" part.

No one officially ever promised anyone that there would be some “release date” of that to the public from the MakeMKV side. If someone told you this or promised it to you then they have flat out lied to you or are trolling you.

MakeMKV and all source code related to that software is owned by and is property of Mike and only he has the final decision to sell, license, borrow, or make it open/closed sourced. This includes how MakeMKV uses Libredrive to achieve said functionality and can be privately held by him for his own/sole business property/purposes.

If other developers wish to implement those same or similar types of features within their application in order to profit from said features and their software as well, then they have to figure it out within their own software development. Mike is not responsible for any of that.

A similar discussion took place here:

https://www.makemkv.com/forum/viewtopic ... ons#p96967

And I’ve witness it mentioned in support forums/websites of other development houses/companies for other software and the developers involved in those conversations for those apps either explicitly did not express interest, have no idea what it is, or never bother to respond. So, there is really nothing anyone here on this side of things can do about that.

[Silasqwerty]

I was just wondering when what Mike was referring to here: "LibreDrive functionality is implemented as part of open-source LibDriveIO library (at the time of this writing the library source code is not yet released)." would happen. I know that's all up to him to decide how he wants to do it, I just hope that that text is still accurate and that the full source code for that will be released

[RibShark]

No one officially ever promised anyone that there would be some “release date” of that to the public from the MakeMKV side. If someone told you this or promised it to you then they have flat out lied to you or are trolling you.

MakeMKV and all source code related to that software is owned by and is property of Mike and only he has the final decision to sell, license, borrow, or make it open/closed sourced. This includes how MakeMKV uses Libredrive to achieve said functionality and can be privately held by him for his own/sole business property/purposes.

Please kindly explain why this text exists in the payload MakeMKV sends the drive then:

Code: Select all

54 68 69 73  20 69 73 20  76 6f 6c 61  74 69 6c 65  This is volatile        28.2.80       
20 52 41 4d  2d 6f 6e 6c  79 20 6d 69  63 72 6f 63   RAM-only microc        28.2.96       
6f 64 65 20  66 6f 72 20  4c 69 62 72  65 44 72 69  ode for LibreDri        28.2.112      
76 65 20 62  79 20 4d 61  6b 65 4d 4b  56 20 2d 20  ve by MakeMKV -         28.2.128      
68 74 74 70  3a 2f 2f 77  77 77 2e 6d  61 6b 65 6d  http://www.makem        28.2.144      
6b 76 2e 63  6f 6d 2f 6c  69 62 72 65  64 72 69 76  kv.com/libredriv        28.2.160      
65 2f 0d 0a  43 6f 70 79  72 69 67 68  74 20 28 63  e/..Copyright (c        28.2.176      
29 20 4d 61  6b 65 4d 4b  56 20 74 65  61 6d 2c 20  ) MakeMKV team,         28.2.192      
61 6c 6c 20  72 69 67 68  74 73 20 72  65 73 65 72  all rights reser        28.2.208      
76 65 64 2e  0d 0a 46 6f  72 20 75 73  65 20 62 79  ved...For use by        28.2.224      
20 4c 47 50  4c 20 4c 69  62 44 72 69  76 65 49 6f   LGPL LibDriveIo        28.2.240      
20 6f 6e 6c  79 2e 0d 0a  0d 0a 0d 0a  0d 0a 0d 0a   only...........        28.2.256

Quite clearly this indicates that an open source (LGPL) LibDriveIo build will be available for use, even if the URL is not yet up.

[st4evr]

When MakeMKV got ahead of all other competitors in several areas of development a few of those competing developers made public that they reached out to MakeMKV requesting some sort of deal agreement to partner/use/license features used by MakeMKV and it was also made public by them that Mike explicitly refused. I will not say anymore as that is a sore subject to some, I believe primarily due to how “unprofessionally” it was all discussed/handled by certain people. But Google may provide some or all of those discussions if they are still out there. In the end this soured some aspects.

As it’s also mentioned above and previously discussed in this forum, there hasn’t been a cemented promise of an official release for any of this. Was it thought about? Probably. And if Mike has or will change his mind, that is entirely up to him to do so and he has every right to do so if he so wishes. But it does not mean anyone should have expectations or feel entitled that he needs to release his work to the public. Some of these features were implemented 3+ years ago (including the private internal beta testing that took place). Yet here we are.

Ultimately, Mike can elaborate as to why that text was added if he wishes and if it still bears any validity after all this time and all that has occurred since.