The ISO2DSD folder has it's own version of sacd_extract, that one should not have the _160, only the one on the flash drive should have the _160.The Autoscript folder contains the sacd-extract-160 file (at 343 KB). And the .TSS is the only file with an extension. So the thumb drive looks fine. The ISO2DSD folder contains sacd_extract, not ...160. I assume that If I can't "housekeep" the folder, I can't copy ...extract-160 to it.
And now with the 590 in sleep mode, I get no message at all when I "execute" ISO2DSD with an SACD in the player. Guess I'll start all over again by unplugging the 590 and redoing the whole routine.
Good deal, those 180 SACD rips will go by in a flash!Yippee!!! Creating a new Autoscript flash drive did the trick! Lenny B's reading of Rhapsody in Blue and An American in Paris are processing as I write this. Thanks, Mikey. I won't be tearing any more hair out. Now I have only 180 more SACDs to go.
Yes. A day after I ordered a used BDP-S590 to plunge into SACD ripping (commenced last Thursday thanks to this indispensably informative thread), I decided to order a second one as a backup. The units are "used", after all, so to me system redundancy is a no-brainer--especially given the an-offer-I-couldn't-refuse low price of admission.A general question to the SACD ripping community: do you keep a spare player around in case your main one fails? drivers get updated).
The download package in Post # 284 has everything you need, including the sacd_extract.exe that is 3.9, though it isn't named that way. It is the latest compile for Windows however. It contains an updated version of the front-end Java applet that is the GUI itself.Up to this point I've used ISO2DSD, but I'll give SACDExtractGUI a shot if someone will point me to where I can get Extract 3.9 for Windows 10.