Rip SACD with a Blu-ray player

No joy. My S590 arrived yesterday, complete with remote and HDMI cable, and everything checks out, including the Ethernet connection and the opening of the player's door upon completion of the Autoscript routine and removal of the thumb drive. I've manually set the 590's IP, subnet, etc., following examination of the Auto settings, and the player appears in my Windows 10 Network display sporting that IP.

But I keep getting the "failed to connect" message shown here when I attempt to commence a rip. I've unplugged the player, set the player's system settings to Sony's defaults and then redone the settings to ensure that "Quick Start" is the default. When I turn off the player, it disappears from the Win 10 Network display. Whether I leave it off or turn it "on", I get the message pictured here when I try to rip, whether I set the output mode to ISO or DSF.

The 590 appears to be doing everything else right. What am I doing wrong?

Thanks in advance.

S590 Rip Failure.png
 

MikeyFresh

Moderator
Staff member
Hmmm, I know you have the outer enclosing folder called AutoScript at the root level of the flash drive, so that leaves the script itself as a question. Are you sure you have the Pioneer-Sony version of the script, and not the Sony ARMv7 version?

It's easy to click and download the wrong thing, the way you can tell is the correct script for the S590 has an sacd_extract piece called sacd_extract_160.

If it ends in 6200 instead of 160, that's the wrong script.

If it's the right script, there should be only one file with any file extension, that one being .TSS, the other two files should have no extension. If anything else shows a suffix (i.e. perhaps .txt was assigned if you took a look inside the script by opening it) just delete the file extension, or re-download a fresh script if there is any doubt about having made any keystrokes inside the script if it were ever opened previously.

Lastly, the ISO2DSD folder must stay all together just as it was downloaded, you can't do any housekeeping and delete or move anything from it, that folder must stay intact with all contents present and accounted for just as it was downloaded.
 
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.
 

MikeyFresh

Moderator
Staff member
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.
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.

You probably should use the newer SACDExtractGUI instead of ISO2DSD when doing this kind of troubleshooting, as it has Test buttons for Ping and Port 2002. That helps a lot in terms of figuring out where the issue is.

The only other things that have caused that error message are the following:
  1. Not actually an SACD in the tray, it's a Redbook CD.
  2. Hidden primary partition on the flash drive (try using a different flash drive).
  3. Flash drive partition scheme is not MBR.
  4. Anti-virus/malware program blocking Port 2002.
 
Thanks, Mike. I have some new flash drives arriving today, so I'll start there. A single-layer Sony SACD is in the tray, and disabling virus protection doesn't correct the problem. SACD_ExtractGUI flashes on for a split second, then disappears when I attempt to execute it, and running compatibility tests on it don't solve that one, either.

I'll leave you alone for at least awhile as I work my way through the process starting again at Step 1. Will let you know. I have a second S590 on the way, so you can be sure I'm committed to resolving this. :-)
 

MikeyFresh

Moderator
Staff member
OK, no problem at all in answering questions.

The SACDExtractGUI issue might be one that a handful of Windows 10 users have had in that double clicking it didn't launch the application. That has nothing to do with the application itself but rather, how Windows sometimes arbitrarily decides to open Java applets (.jar) instead of launching them. However in that scenario you'd see the jar open and display it's contents rather than just a brief flash and then nothing.

But we did have two members with that issue, and it's a Windows thing regarding the settings for what to do with a .jar file. One reported he could launch the program by right-clicking it, while another had to jump through some additional settings hoop to launch a Java applet like SACDExtractGUI.
 
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.
 

MikeyFresh

Moderator
Staff member
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.
Good deal, those 180 SACD rips will go by in a flash! ;)

OK maybe not a flash, but with a little enthusiasm you'll knock 'em down in relatively short order.

I do recommend trying to sort out SACDExtractGUI, gotta be a Windows Java applet launch thing. SACDExtractGUI can save you time as it is faster, and more capable in terms of functionality. Or, if slow and steady suits you, there is nothing wrong with good ole' ISO2DSD.
 

MikeyFresh

Moderator
Staff member
The SACD ripping train rolls onward, this thread now has 80,000+ views in 14 months.

We count members here from the U.S., Canada, Costa Rica, Columbia, Brazil, U.K., Germany, France, Hungary, Switzerland, Australia, Japan, Singapore, Philippines, and Hong Kong, as well as lurkers from many other countries too.

Thanks again to all participants!
 
A general question to the SACD ripping community: do you keep a spare player around in case your main one fails? I've had quite a few PC DVD drives fail over the last couple decades. On the one hand, it seems like a waste to have a completely unused unit sitting around doing nothing. On the other, while these units can often be found on the cheap, they're old and logic would suggest they're only going to get more rare and more expensive from this point.

I just bought a backup BX510 for $23 from eBay. It makes sense for me, because it will also serve as a 3D blu-ray player (before now, I've used my PC--it is connected to my TV and receiver by HDMI, but can be awfully fiddly and problem-prone when graphics drivers get updated).
 
A general question to the SACD ripping community: do you keep a spare player around in case your main one fails? drivers get updated).
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.
 
When I started ripping away last Thursday evening, I thought I had about 130-to-140 SACDs in my collection. This evening I put Rip #141 to bed, and that wraps up my Classical section (finally), but I'm nowhere near done. Each of four successive additional passes through my silver-disc complement kept turning up more SACDs, and I've finally topped out at 211. So I'll just keep plugging away.

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. Lack of it appears to be what's holding me back from getting the program up and running, as other Java apps work fine. Thanks in advance.

Some observations on my experience with the S590/ISO2DSD combo up to this point: (1) Rip transfer rate varies from 1.78 to 3.09 MB/sec across my Ethernet connection. Typically, Sony and Exton single-layer discs transfer the fastest, though I've had some hybrids clock in at 3.07. Telarcs move stubbornly consistent at 1.85 to 1.86. I estimate the average transfer rate at 2.2 MB/sec. (2) After seven rips, I have to re-Autoscript the S590. Going to the eighth rip returns a "Failed to connect" message. So I power down and restart the process. Not a big deal now that it's become rote.

Again, thank you for all the indispensable help embedded in this thread.
 

MikeyFresh

Moderator
Staff member
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.
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.

Click on the Intel/AMD platforms (64-bit) spoiler and then use the Windows x64 package.

The post itself dates to November 2018, however @Nexus3 graciously updated the links to newer compiles that reflect current (spring 2019) updates to the software.
 
Top