MakeMKV support forum
https://forum.makemkv.com/forum/
Stick with 1.00. It works really well!ionblue wrote: ↑Tue Jul 02, 2019 8:18 pmHi there. I purchased an Archgon-8107S so I could rip UHD's and I've successfully downgraded it in a Windows VM to version 1.00. I saw a few other firmwares in the zip file, but wasn't sure which was best. Is 1.00 OK or should I use one of the other ones? I am able to read UHD now so at least that's working!
Well, everything is working now so I’m happy. If anyone knows what the other versions do and if I should use one, please let me know. I know I saw the N version mentioned in another thread, but again, I wasn’t sure about which one.
From the original thread announcing the MK FWs... "there are three different BU40 models - Taiwan, USA and Europe. If unsure, do not flash, and wait for LibreDrive flasher app to be released." As to which is which, I recall it being discussed in a different thread. Feel free to search if you just gotta know.
Just started using this external UHD drive - I can get through UHD discs just fine; however, I have noticed that there are spin down pauses at times during the process where the drive seems to go dormant, only to start back up seemingly at random. As noted, the process seems to never actually fail, but I'm not seeing consistent throughput from start to finish with firmware version 1.00. Read speeds reach 6.0X when the drive is active, so when the drive is running, it's running well. Is there something obvious I'm missing here? The only qualifier to note here is that I'm ripping direct to my QNAP TS-453 Pro NAS on my network. With that said, I was using a Pioneer BDR-XD05S to take care of standard blu-ray discs prior to acquiring this Archgon external - throughput was a consistent (albeit meager) 2.0X with no dormant stretches in read.
They usually slow right down on layer changes.d22901 wrote: ↑Mon Jul 15, 2019 11:02 pmJust started using this external UHD drive - I can get through UHD discs just fine; however, I have noticed that there are spin down pauses at times during the process where the drive seems to go dormant, only to start back up seemingly at random. As noted, the process seems to never actually fail, but I'm not seeing consistent throughput from start to finish with firmware version 1.00. Read speeds reach 6.0X when the drive is active, so when the drive is running, it's running well. Is there something obvious I'm missing here? The only qualifier to note here is that I'm ripping direct to my QNAP TS-453 Pro NAS on my network. With that said, I was using a Pioneer BDR-XD05S to take care of standard blu-ray discs prior to acquiring this Archgon external - throughput was a consistent (albeit meager) 2.0X with no dormant stretches in read.
Thanks for the follow-up. Will consider this behavior normal in that case. My Pioneer drive not exhibiting this behavior made me pause.MartyMcNuts wrote: ↑Tue Jul 16, 2019 5:15 amThey usually slow right down on layer changes.d22901 wrote: ↑Mon Jul 15, 2019 11:02 pmJust started using this external UHD drive - I can get through UHD discs just fine; however, I have noticed that there are spin down pauses at times during the process where the drive seems to go dormant, only to start back up seemingly at random. As noted, the process seems to never actually fail, but I'm not seeing consistent throughput from start to finish with firmware version 1.00. Read speeds reach 6.0X when the drive is active, so when the drive is running, it's running well. Is there something obvious I'm missing here? The only qualifier to note here is that I'm ripping direct to my QNAP TS-453 Pro NAS on my network. With that said, I was using a Pioneer BDR-XD05S to take care of standard blu-ray discs prior to acquiring this Archgon external - throughput was a consistent (albeit meager) 2.0X with no dormant stretches in read.
Indeed - the drive always seems to resume on 1.00 (eventually). Just seems to randomly stall many times during each rip. For instance, I'm at 2 hours and 38 minutes on a 4k rip of Avengers-Age of Ultron with still a little more time to complete. But when the drive is actually active, at 6.0X, this ~55 GB rip would be done in around 45 minutes or so (maybe even less) if it consistently read the entire time. I wonder if the MK version of 1.03 would modify this behavior in any way?MartyMcNuts wrote: ↑Thu Jul 18, 2019 12:54 amThat's ok. It happens but they eventually pick up speed again.