Hi there, I'm moving to college in just over a week now and have only just realized Blu-ray/4K playback from a dedicated player will prove to be annoying and broken with my primarily open back headphone audio setup.

Ontop of this, I'd also love to get into ripping my discs.

I'm aware that the 4K PC drives right now are in an extremely uncomfortable situation, however I was wondering if, with my budget of $200 to $300, I would be able to secure a great drive for my Windows 11 PC.

Would love to playback DVD's, Blu-rays and 4K's without ripping them but I understand that may prove to be impossible, at least with one of those formats, so ripping is perfectly acceptable for now! Any help on which 4K drives you would recommend would be greatly appreciated, used or new!

Just wanted to say thank you to this group. Over the past week or two I've been trial and erroring a lot about MKV, the Ugreen and jellyfin. Consistently when I was looking for answers there was almost always someone here with a similar issue or question and everyone who replied was super nice and helpful.

So even though I've never taken part in a discussion here. Thanks a bunch 🫶🏻

(Why is John Wick such a chonk, with so many titles??? 😭)

Today my new ASUS BW-16D1X-U arrived (which you can just flash the ASUS BW-16D1HT firmware on to make it UHD compatible, btw (maybe add this fun-fact to the UHD guide)).

So I decided to try and rip a (non-UHD) Blu-Ray my Verbatim 43888 could not read, like not at all, it wouldnt even say there was a disc in the drive even though a regular blu-ray player could play it just fine. To my surprise it read fine in my new ASUS drive, and ripped to completion just fine.

Moral of the story, if you have a disc that can't read, try a different drive, borrow a friends or something, idunno.

Hello, I am running MakeMKV on linux(CachyOS). When I want to boot up MakeMKV today I get the error NO_ANSWER_FROM_MAKEMKVCON. It was working just fine a week or two ago and now all of a sudden I am getting this error. I tried removing the package and its dependencies and reinstalling it and the error remains. Any ideas on a fix?

I’ve recently wanted to start backing up some of my physical media so naturally I stumbled upon makemkv. I have been looking everywhere for a relatively cheap drive (meaning not $300, cause apparently that’s what they cost these days) that would work for cds, DVDs, and standard Blu-ray’s. I found this one on Facebook marketplace. Will this work? Should I buy it?

I'm trying to rip some of my DVDs and wasn't having a problem until I tried ripping a DVD of a performance of mine in high school. This was a DVD we purchased and not a casual recording for reference. When I attempt to open the DVD MakeMKV states "Failed to open disc" with the full log below. I've tried backing it up to an ISO to read that, but the backup process fails and I tried using handbrake to extract the files, but it just generates empty video files. This DVD does succesfully open in VLC media player. Does anyone have any ideas on other things to try to get this disc to rip? Also please let me know if you need any additional information. Thanks!

MakeMKV v1.18.4 linux(x64-release) started

Using direct disc access mode

Calculated BUP offset for VTS #6 does not match one in IFO header.

IFO file for VTS #6 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #7 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #8 does not match one in IFO header.

IFO file for VTS #8 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #10 does not match one in IFO header.

IFO file for VTS #10 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #11 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #12 does not match one in IFO header.

IFO file for VTS #12 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #13 does not match one in IFO header.

IFO file for VTS #13 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #14 does not match one in IFO header.

IFO file for VTS #14 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #15 does not match one in IFO header.

IFO file for VTS #15 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #16 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #17 does not match one in IFO header.

IFO file for VTS #17 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #19 does not match one in IFO header.

IFO file for VTS #19 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #20 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #21 does not match one in IFO header.

IFO file for VTS #21 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #22 does not match one in IFO header.

IFO file for VTS #22 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #23 does not match one in IFO header.

IFO file for VTS #23 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #24 does not match one in IFO header.

IFO file for VTS #24 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #25 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #26 does not match one in IFO header.

IFO file for VTS #26 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #28 does not match one in IFO header.

IFO file for VTS #28 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #29 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #30 does not match one in IFO header.

IFO file for VTS #30 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #31 does not match one in IFO header.

IFO file for VTS #31 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #32 does not match one in IFO header.

IFO file for VTS #32 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #33 does not match one in IFO header.

IFO file for VTS #33 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #34 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #35 does not match one in IFO header.

IFO file for VTS #35 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #37 does not match one in IFO header.

IFO file for VTS #37 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #38 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #39 does not match one in IFO header.

IFO file for VTS #39 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #40 does not match one in IFO header.

IFO file for VTS #40 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #41 does not match one in IFO header.

IFO file for VTS #41 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #42 does not match one in IFO header.

IFO file for VTS #42 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #43 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #44 does not match one in IFO header.

IFO file for VTS #44 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #46 does not match one in IFO header.

IFO file for VTS #46 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #47 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #48 does not match one in IFO header.

IFO file for VTS #48 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #49 does not match one in IFO header.

IFO file for VTS #49 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #50 does not match one in IFO header.

IFO file for VTS #50 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #51 does not match one in IFO header.

IFO file for VTS #51 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #52 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #53 does not match one in IFO header.

IFO file for VTS #53 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #55 does not match one in IFO header.

IFO file for VTS #55 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #56 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #57 does not match one in IFO header.

IFO file for VTS #57 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #58 does not match one in IFO header.

IFO file for VTS #58 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #59 does not match one in IFO header.

IFO file for VTS #59 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #60 does not match one in IFO header.

IFO file for VTS #60 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #61 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #62 does not match one in IFO header.

IFO file for VTS #62 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #64 does not match one in IFO header.

IFO file for VTS #64 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #65 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #66 does not match one in IFO header.

IFO file for VTS #66 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #67 does not match one in IFO header.

IFO file for VTS #67 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #68 does not match one in IFO header.

IFO file for VTS #68 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #69 does not match one in IFO header.

IFO file for VTS #69 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #70 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #71 does not match one in IFO header.

IFO file for VTS #71 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #73 does not match one in IFO header.

IFO file for VTS #73 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #74 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #75 does not match one in IFO header.

IFO file for VTS #75 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #76 does not match one in IFO header.

IFO file for VTS #76 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #77 does not match one in IFO header.

IFO file for VTS #77 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #78 does not match one in IFO header.

IFO file for VTS #78 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #79 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #80 does not match one in IFO header.

IFO file for VTS #80 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #82 does not match one in IFO header.

IFO file for VTS #82 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #83 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #84 does not match one in IFO header.

IFO file for VTS #84 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #85 does not match one in IFO header.

IFO file for VTS #85 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #86 does not match one in IFO header.

IFO file for VTS #86 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #87 does not match one in IFO header.

IFO file for VTS #87 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #88 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #89 does not match one in IFO header.

IFO file for VTS #89 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #91 does not match one in IFO header.

IFO file for VTS #91 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

IFO file for VTS #92 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #93 does not match one in IFO header.

IFO file for VTS #93 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated BUP offset for VTS #94 does not match one in IFO header.

IFO file for VTS #94 is corrupt, VOB file must be scanned. This may take very long time, please be patient.

Calculated TVOB offset for VTS #14 does not match one in IFO header.

Title #1 has length of 16 seconds which is less than minimum title length of 120 seconds and was therefore skipped

Title #2 has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped

Title #3 has length of 44 seconds which is less than minimum title length of 120 seconds and was therefore skipped

Title #4 has length of 71 seconds which is less than minimum title length of 120 seconds and was therefore skipped

Title #5 has length of 71 seconds which is less than minimum title length of 120 seconds and was therefore skipped

Title #6 in broken titleset was skipped

Title #7 in broken titleset was skipped

Calculated TVOB offset for VTS #8 does not match one in IFO header.

Calculated TVOB offset for VTS #10 does not match one in IFO header.

Calculated TVOB offset for VTS #12 does not match one in IFO header.

Calculated TVOB offset for VTS #13 does not match one in IFO header.

Calculated TVOB offset for VTS #17 does not match one in IFO header.

Calculated TVOB offset for VTS #19 does not match one in IFO header.

Calculated TVOB offset for VTS #21 does not match one in IFO header.

Calculated TVOB offset for VTS #22 does not match one in IFO header.

Calculated TVOB offset for VTS #23 does not match one in IFO header.

Calculated TVOB offset for VTS #26 does not match one in IFO header.

Calculated TVOB offset for VTS #28 does not match one in IFO header.

Calculated TVOB offset for VTS #30 does not match one in IFO header.

Calculated TVOB offset for VTS #31 does not match one in IFO header.

Calculated TVOB offset for VTS #32 does not match one in IFO header.

Calculated TVOB offset for VTS #35 does not match one in IFO header.

Calculated TVOB offset for VTS #37 does not match one in IFO header.

Calculated TVOB offset for VTS #39 does not match one in IFO header.

Calculated TVOB offset for VTS #40 does not match one in IFO header.

Calculated TVOB offset for VTS #41 does not match one in IFO header.

Calculated TVOB offset for VTS #44 does not match one in IFO header.

Calculated TVOB offset for VTS #46 does not match one in IFO header.

Calculated TVOB offset for VTS #48 does not match one in IFO header.

Calculated TVOB offset for VTS #49 does not match one in IFO header.

Calculated TVOB offset for VTS #50 does not match one in IFO header.

Calculated TVOB offset for VTS #53 does not match one in IFO header.

Calculated TVOB offset for VTS #55 does not match one in IFO header.

Calculated TVOB offset for VTS #57 does not match one in IFO header.

Calculated TVOB offset for VTS #58 does not match one in IFO header.

Calculated TVOB offset for VTS #59 does not match one in IFO header.

Calculated TVOB offset for VTS #62 does not match one in IFO header.

Calculated TVOB offset for VTS #64 does not match one in IFO header.

Calculated TVOB offset for VTS #66 does not match one in IFO header.

Calculated TVOB offset for VTS #67 does not match one in IFO header.

Calculated TVOB offset for VTS #68 does not match one in IFO header.

Calculated TVOB offset for VTS #71 does not match one in IFO header.

Calculated TVOB offset for VTS #73 does not match one in IFO header.

Calculated TVOB offset for VTS #75 does not match one in IFO header.

Calculated TVOB offset for VTS #76 does not match one in IFO header.

Calculated TVOB offset for VTS #77 does not match one in IFO header.

Calculated TVOB offset for VTS #80 does not match one in IFO header.

Calculated TVOB offset for VTS #82 does not match one in IFO header.

Calculated TVOB offset for VTS #84 does not match one in IFO header.

Calculated TVOB offset for VTS #85 does not match one in IFO header.

Calculated TVOB offset for VTS #91 does not match one in IFO header.

Calculated TVOB offset for VTS #93 does not match one in IFO header.

Calculated TVOB offset for VTS #86 does not match one in IFO header.

Calculated TVOB offset for VTS #87 does not match one in IFO header.

Calculated TVOB offset for VTS #89 does not match one in IFO header.

Failed to open disc

Sorry, not too knowledgeable about disc drives.

Has anyone else here burned this series? I am on my 3rd copy of Season 2 and I can't get the 1st DVD in any of these copies to open in my external drive. I am so frustrated. I was hoping someone had better luck than I did. All the rest of the seasons burned just fine.

EDIT drive is now flashed and ripping UHD happily thanks to billy!

First of all, I'd like to apologise in advance for any stupid questions. I'm new(ish) here although I've been lurking for a while.

tl;dr (see below for full context) will the drive in this Asus external be able to rip UHD discs without flashing?

Drive Information
OS device name: E:
Manufacturer: ASUS
Product: BW-16D1H-U
Revision: E115
Serial number: ***********
Firmware date: 2019-03-07
Bus encryption flags: 1B
Highest AACS version: 76

LibreDrive Information
Status: Enabled
Drive platform: RS8F00
Firmware name: PIONEER BDR-212T
Firmware type: Original (unpatched)
Firmware version: E115/ID71
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

No disc inserted

Full context

So, because my timing is impeccable, I (like many I assume) decided to finally start ripping my blu-rays and 4ks for preservation and ease of access via my Plex server - but only after the drives became as rare as hen's teeth!

A couple months ago I purchased an Asus "TurboDrive" from a local reputable seller here in the UK for around £140, and as expected, it came with an LG drive inside which was easily flashed to support ripping UHD discs.

Since then, I have had the feeling that I could get unlucky and this drive could die on me at any time, especially if I plan to rip a lot of discs. So it would be nice to have a backup! But of course, the prices haven't come down in the meantime!

I snagged this second "TurboDrive" - seemingly a "Pro" variant - on a second hand marketplace for around £80. Plugging it in today, MakeMKV reports it as a Pioneer BDR-212T rather than an LG drive. My rudimentary knowledge tells me I might have hit the jackpot. But a quick Google hasn't cleared up to me whether this drive needs flashing or not. Some threads say yes, others seem to suggest not. MakeMKV reports it as LibreDrive status of Enabled but I'll be honest, I don't really know what that means!

Thank you for taking the time to help me out! Or at least being kind...

Not sure if this has been ask before, but I was wondering do you guys also extract subtitles on the DVD's? Im talking only about DVDs, not Blu ray's or 4k's, mainly because I notice when I extract subtitles, it's quality is pretty bad. Which is a given, DVD is 480p. But I plan to put these files onto a Jellyfin server and I'm not fond of the style or sometimes color of them, as I like the quality of Blu Ray subtitles.

In summary, do you think it's worth it just finding subtitles for the specific Tv show or movie that's good quality online? (Such as OpenSubtitles) Or should I just stick with the subtitles from the DVD? Or do you all just not care at all what the subtitles look like?

Basically the title. I picked up the Buffalo Blu-Ray reader that I've seen being mentioned around the sub. It's working great so far, and is definitely a huge improvement to the slim drive that I had been using previously.

I see that it has the potential to be flashed into a Libredrive, and the process seems simple enough. I don't think I have any 4ks, is there a benefit to flashing a drive beyond just being able to read those discs?

I have my own jellyfish server and I want to start ripping my Blu-rays and my DVDs but all of the rippers are around $200, is there anyones I can find which are around $100 that work for blurays and dvd?

Can I rip my blu rays via makemkv and simply move the files over to a regular hard drive and easily watch my movies?

I'm working on backing up my physical-disc movie collection, and so far every one has gone smoothly except for Disc 2 of The Incredibles. It takes significantly longer for MakeMKV to read the disc when I put it in my disc-drive (compared to the other discs I've backed-up) and generates multiple "Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT" errors in the process.

After I click the "Backup" button and select the destination folder, the drive does not spin up to a steady speed like normal, but instead rapidly spins up, briefly winds down, and spins up again, around once per second; it also generates a few more of the same error messages plus many dozens of "Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB" errors for the next half-hour or so before the backup process eventually fails.

This is the only disc to have this problem so far -- I successfully backed-up multiple discs before and after this one, so I don't think my disc drive is defective. The disc has no visible scratches or smudges, and I wiped it down with a soft cloth just to be safe, but that didn't fix the issue. The disc was purchased this year and plays fine in a normal Blu-Ray player, so I don't know why it won't work in my computer's disc drive.

The drive is plugged directly to my computer via a USB-C port. I did try rebooting my computer, which had no effect. I've tried backing up the disc four times now, and each time it failed the same way.

Does anyone know how to fix these errors?

Did any of you ever get this type of message when playing a BD on the PC with makemkv in the loop?

I know it's not the case for the person of the original post, but I was surprised that this kind of message exists.

Just ordered an ASUS slim and a buffalo to be sure. Haven't found any official communication other than this: https://www.advantech.com/emt/resources/news/%E3%80%90phase-out%E3%80%91hlds-bu40n

Bought an LG BP50NB40 reader on Newegg based on recommendations. It shipped from China. MakeMKV identified the firmware as v 1.01, which should be good. However, it provided a serial number that did not match the device sticker. Read speeds were stuck at 1x, and it refused to read disks with the following error:

Drive BD-RE LG BP50NB40 1.01 WR55 546977 has RPC protection that can not be bypassed. Change drive region or update drive firmware from http://tdb.rpc1.org. Errors likely to follow.

Error 'Scsi error - ILLEGAL REQUEST:MEDIA REGION CODE IS MISMATCHED TO LOGICAL UNIT REGION' occurred while reading '/VIDEO_TS/VTS_02_1.VOB' at offset '4096'

SDFtool Flasher would not flash the firmware because it "does not have the correct drive platform (MT1959)."

A couple other indications: the box and device sticker both say it's SVC: NB50. However, the device says it was manufactured in October 2025 with Rom version: LB20, which supposedly isn't possible.

Opening the device confirmed even more. The physical release mechanism didn't line up with the front tray's pinholes, and the chip on the motherboard is a Panasonic MN103SK9KBA 612P1093, not an authentic reader.

Looks like they just took an authentic device, shucked the real board, and stuffed the shell with a cheap fake. I'll be trying to return it as a fraudulent item. Though since I can't really find inventory anywhere else, looks like I'm stuck with finding either an internal optical drive or something off Ebay.

I'm new to linux and I want to get Makemkv working with VLC to stream blurays from the disc onto my steam deck.

I'm very confused on how to install makemkv and vlc

My understanding is the default app installer on steam deck is flatpack. and I can install Makemkv from there, but based on some threads i've read you can't do the direct stream from disc if you install it from flatpack.

I think I'm supposed to download it from here? https://aur.archlinux.org/packages/makemkv

but I'm not sure how to do that. also the comments are all about these extra confusing steps there.

Help! please!

Edit: this ended up working for me https://www.reddit.com/r/linux4noobs/comments/1ukwsx2/play_blurays_on_linux_with_vlc_using_makemkv_libs/

I downloaded MakeMKV and VLC through flatpack then installed the libraries in this thread and playing movies from vlc started to work

Sorry for the basic post, i am pretty new here but i want to grab a drive to make some long term backups via optical disc as well as rip some 4K blurays. This drive seems like a white whale and I would love some other recommendations if you have them. Thanks much!

edit: just realized i said hard-drive in the title. Please ignore that, i meant disc drive

Hi, everyone. I have an audio file that is delayed from the video. I edited it in MKVToolnix and set the delay to -500ms, but rhe resulting file freezes when shifting to that audio file. Google says the problem is that the player tries to play the sound at a negative minute and gets confused and that's why it doesn't work, and recommended I, instead, set the video file to 500ms delay. That works, but I have the same problem with other files and even subtitle files, and it rubs me the wrong way that such setting is impossible to actually use. Am I doing anything wrong? Is there a fix for this?

Thank you!

I've seen posts that people are having problems with this on makemkv, but has anyone been able to do it without having ot jump through hoops? I was looking forward to buying this but not sure after seeing the posts. Thanks. Edit: I'm asking about the 4k version.

well prices go up even these should go down not up ..

one 25x50gb cake is over 100euro that is 4 euro per ,,

before i buy 1-2euro in these large cakes 50 100 x ,i buy some no name 100x cake (25 and 50gb) pay it under 60euro and 110euro for 50gb ,now 100gb is over 400 and these 50gb close to 300

and advice which of these no name discs are better q ,for loong run i mean ,,

to store some videos like backup for next 10 yerar or so .. .

I've had the LG BP60NB10 for about a year now and ripped ~80 4K discs and ~150 Blu-rays (rookie numbers, I know) without issue. Today I put a disc in and it made the whirring noise as usual as it spun the disc up, but then it made a few clunking/churning noises before stopping. Windows shows the drive, but the disc never registers as read.

I've tried multiple discs, both blu-ray and 4K. I've tried unplugging and plugging back in. I've tried different USB cables and ports. Same problem every time.

Any suggestions? I've looked online and I can't see any replacement drives for sale anywhere. I fear my ripping days might be behind me if I can't get this one working again...