Hi. Just took delivery of a BDP-S390 from eBay - it's pretty beat-up and doesn't have a remote, but it boots up and looks like starts an SACD when I put it in.

I think the new all-in-one scripts will be perfect for me - I don't have to worry about having a remote, etc. However, when I format the drive (tried both FAT32 adn NTFS) and put the contents of SACD_AutoRip_A1neo,zip in the root of that drive, nothing happens when I plug it into the blu-ray player. According to the instructions it should open the tray in ten seconds.

I've read some of the posts about changing quick-start, sleep, etc. settings - but I'm not sure what players that step is needed for. Do I need to track down a universal remote and fiddle with the settings on the blu-ray player for this to work for me?

Thanks.
 
Hi. Just took delivery of a BDP-S390 from eBay - it's pretty beat-up and doesn't have a remote, but it boots up and looks like starts an SACD when I put it in.

I think the new all-in-one scripts will be perfect for me - I don't have to worry about having a remote, etc. However, when I format the drive (tried both FAT32 adn NTFS) and put the contents of SACD_AutoRip_A1neo,zip in the root of that drive, nothing happens when I plug it into the blu-ray player. According to the instructions it should open the tray in ten seconds.

I've read some of the posts about changing quick-start, sleep, etc. settings - but I'm not sure what players that step is needed for. Do I need to track down a universal remote and fiddle with the settings on the blu-ray player for this to work for me?

Thanks.

Good evening and welcome to HFH.

If the disc tray does not open, that's failure to ignite and that must be addressed first before anything else. Nothing else can happen until you make the player read the script and auto-open the disc tray.

Fortunately, that one is likely easy to solve, we've come across this what seems like hundreds of times now, and why it happens is not completely within our control upfront, but it is very easily fixed.

First, you cannot put a zipped folder onto the USB flash drive, it must be unzipped. The resulting unzipped folder called AutoScript is what you put on the flash drive.

This means you need an outer/enclosing folder called AutoScript at the root of the USB flash drive, housing the other 3 items. For whatever reason, certain browser/OS/settings combinations will zip the AutoScript folder for download, even though it is tiny. Upon unzip, some browser/OS/settings combinations will discard that outer enclosing folder called AutoScript, assuming you only want the folder's contents. You need the folder called AutoScript (note I said folder, not to be confused with one of the files inside of it which is also called AutoScript).

You do not want any other additional enclosing folders, only that one called AutoScript, that is what goes at the root of the USB flash drive. If you have the folder structure right, the disc tray will surely auto-open, and also auto-close with A1neo.

The remote control is needed to ensure you have the Quick Start mode enabled in the player's OSD menu settings. You could use an existing universal remote with the Sony Blu-ray IR codes programmed, or if you have an Android smart phone or tablet, you can also use the Sony app called Video & TV SideView for Android, however unfortunately it appears the iOS version of the app has been withdrawn.

Does your USB flash drive have an LED activity indicator? If it does, I'd say go ahead and correct the folder structure as described above, get the disc tray to auto-open, and have an SACD at the ready to drop into the tray. Let the tray auto-close, and if the previous owner had already enabled the Quick Start mode, then you don't need any remote and in about 10 seconds after the disc tray shuts, you will see the LED activity indicator begin to blink, meaning an ISO is being written to the flash drive. Once complete, the disc tray will auto-open again (around 15-20 minutes depending on the runtime of the disc, stereo only discs more like 10 minutes).

We suggest NTFS formatting is best for AutoRip, because some SACDs with multichannel content will produce an ISO file size as large as 4.7GB, which exceeds FAT32's 4GB limit.

While AutoRip is easy, you still need either a software media player compatible with playing ISOs, or you have to extract .DSF tracks from that ISO using the very same software (SACDExtractGUI) that is used for the network sleep-server ripping method.

In all likelihood you are going to need that software in any event, because AutoRip will refuse certain discs that have so-called special characters authored into their metadata, not uncommon with classical music titles, but rare with anything else unless the metadata was not authored in English (i.e. certain SACDs produced by record labels in either Europe or Asia).

Are you a Windows, macOS, or Linux user?
 
Good evening and welcome to HFH.

If the disc tray does not open, that's failure to ignite and that must be addressed first before anything else. Nothing else can happen until you make the player read the script and auto-open the disc tray.

Fortunately, that one is likely easy to solve, we've come across this what seems like hundreds of times now, and why it happens is not completely within our control upfront, but it is very easily fixed.

First, you cannot put a zipped folder onto the USB flash drive, it must be unzipped. The resulting unzipped folder called AutoScript is what you put on the flash drive.

This means you need an outer/enclosing folder called AutoScript at the root of the USB flash drive, housing the other 3 items. For whatever reason, certain browser/OS/settings combinations will zip the AutoScript folder for download, even though it is tiny. Upon unzip, some browser/OS/settings combinations will discard that outer enclosing folder called AutoScript, assuming you only want the folder's contents. You need the folder called AutoScript (note I said folder, not to be confused with one of the files inside of it which is also called AutoScript).

You do not want any other additional enclosing folders, only that one called AutoScript, that is what goes at the root of the USB flash drive. If you have the folder structure right, the disc tray will surely auto-open, and also auto-close with A1neo.

The remote control is needed to ensure you have the Quick Start mode enabled in the player's OSD menu settings. You could use an existing universal remote with the Sony Blu-ray IR codes programmed, or if you have an Android smart phone or tablet, you can also use the Sony app called Video & TV SideView for Android, however unfortunately it appears the iOS version of the app has been withdrawn.

Does your USB flash drive have an LED activity indicator? If it does, I'd say go ahead and correct the folder structure as described above, get the disc tray to auto-open, and have an SACD at the ready to drop into the tray. Let the tray auto-close, and if the previous owner had already enabled the Quick Start mode, then you don't need any remote and in about 10 seconds after the disc tray shuts, you will see the LED activity indicator begin to blink, meaning an ISO is being written to the flash drive. Once complete, the disc tray will auto-open again (around 15-20 minutes depending on the runtime of the disc).

We suggest NTFS formatting is best for AutoRip, because some SACDs with multichannel content will produce an ISO file size as large as 4.7GB, which exceeds FAT32's 4GB limit.

While AutoRip is easy, you still need either a software media player compatible with playing ISOs, or you have to extract .DSF tracks from that ISO using the very same software (SACDExtractGUI) that is used for the network sleep-server ripping method.

In all likelihood you are going to need that software in any event, because AutoRip will refuse certain discs that have so-called special characters authored into their metadata, not uncommon with classical music titles, but rare with anything else unless the metadata was not authored in English (i.e. certain SACDs produced by record labels in either Europe or Asia).

Are you a Windows, macOS, or Linux user?

Crikey, that was it. I had the files in the root of the USB drive instead of the AutoScript folder. It's cranking away now. Looks like the settings for Quick Start were already enabled - which is good since I lost the manual to my ancient universal remote and forgot my account info for my Harmony 600!

The only SACD I have right now is the first RATM disc, so hopefully that won't have a problem with the metadata. I'll dig into converting the ISO after I confirm that it rips. Main test will be when I get my Goodbye Yellow Brick Road SHM-SACD in the mail on Friday :-)

You're right, the LED indicator on the USB stick is very helpful.

Speaking of helpful - thanks for the help!
 
Looks like the settings for Quick Start were already enabled

Outstanding!

I lost the manual to my ancient universal remote and forgot my account info for my Harmony 600!

So did I, I've got a Harmony 600 that is useless to me and I can't be bothered with it.

The only SACD I have right now is the first RATM disc, so hopefully that won't have a problem with the metadata.
The Rage disc won't have any problem, and neither will the Goodbye Yellow Brick Road SHM.

You're right, the LED indicator on the USB stick is very helpful.

Speaking of helpful - thanks for the help!

My pleasure, once again welcome to HFH!
 
Thanks Mike, with your help I have successfully ripped a number of my favourite SACDs starting with 'Dark Side of the Moon'. Completing that first rip was an awesome experience. I put the files on to a usb drive and plugged it into my Denon receiver. The album sounded spectacular, significantly better than playing the SACD disk.
 
Hi,

I am new to HifiHaven.org. I heard of this site from a friend. I have tried everything from the beginning of this Thread to rip SACD's with my Sony BDP-S590 Blu-Ray player. It always comes up with the following statement:
[Running]...
Failed to Connect
libsacdread: Can't open 10.242.104.120:2002 for reading

This is after I have my S590 wired with ethernet cable to my router. The Ping using SACDExtractGUI is connecting fine to the S590's IP (even when S590 is turned off). I have enabled the QuickStart mode to On. Set to SACD on the player as well. I have all the software in folders on my Windows 10 desktop and with Java I have opened both iso2dsd and SACDExtractGUI to open SACD_Extract v.3.9. The USB was formatted to FAT32 using windows. (No guarantee it has an MBR partition because that isn't an option in windows). When i start up the S590 player I insert the USB, the drawer auto-opens, I insert the disc, I press the power button on the unit, I click "Run" on the GUI programs after the unit is off. The result is the same after hours of trying multiple combinations.

I would appreciate any help,

Thanks!
 
Hi,

I am new to HifiHaven.org. I heard of this site from a friend. I have tried everything from the beginning of this Thread to rip SACD's with my Sony BDP-S590 Blu-Ray player. It always comes up with the following statement:
[Running]...
Failed to Connect
libsacdread: Can't open 10.242.104.120:2002 for reading

This is after I have my S590 wired with ethernet cable to my router. The Ping using SACDExtractGUI is connecting fine to the S590's IP (even when S590 is turned off). I have enabled the QuickStart mode to On. Set to SACD on the player as well. I have all the software in folders on my Windows 10 desktop and with Java I have opened both iso2dsd and SACDExtractGUI to open SACD_Extract v.3.9. The USB was formatted to FAT32 using windows. (No guarantee it has an MBR partition because that isn't an option in windows). When i start up the S590 player I insert the USB, the drawer auto-opens, I insert the disc, I press the power button on the unit, I click "Run" on the GUI programs after the unit is off. The result is the same after hours of trying multiple combinations.

I would appreciate any help,

Thanks!

It sounds like you have everything correct, just be sure that both ISO2DSD and SACDExtractGUI are not open at the same time as that could cause a conflict.

Open only SACDExtractGUI, and power cycle the S590 (with the flash drive removed), allow it's initial boot sequence to complete after re-connecting the AC cord, at which point it will sleep. Now power it up, and after the display settles (no disc), insert the flash drive and try again.

If that does not work, you need to try a different USB flash drive, as some are either not using MBR as the partition scheme, or they have a hidden primary partition that is fouling things up.

If the above fails, try AutoRip A1neo to see if you can rip an ISO directly to the flash drive.
 
It sounds like you have everything correct, just be sure that both ISO2DSD and SACDExtractGUI are not open at the same time as that could cause a conflict.

Open only SACDExtractGUI, and power cycle the S590 (with the flash drive removed), allow it's initial boot sequence to complete after re-connecting the AC cord, at which point it will sleep. Now power it up, and after the display settles (no disc), insert the flash drive and try again.

If that does not work, you need to try a different USB flash drive, as some are either not using MBR as the partition scheme, or they have a hidden primary partition that is fouling things up.

If the above fails, try AutoRip A1neo to see if you can rip an ISO directly to the flash drive.
It Worked!!! I needed to add the AutoScript to a different USB flash drive. After doing that it worked perfectly. Thanks for your help! Looking forward to hearing my SACD's in DSD as they were intended.

Thanks Again!
 
Thanks Mike, with your help I have successfully ripped a number of my favourite SACDs starting with 'Dark Side of the Moon'. Completing that first rip was an awesome experience. I put the files on to a usb drive and plugged it into my Denon receiver. The album sounded spectacular, significantly better than playing the SACD disk.

My pleasure Steve, glad you were able to get the process up and running with no troubles.

I know what you mean about completing that first one, a rather huge sense of having come full circle with the format for those of us who have wanted to rip these discs for years. Good to hear the rip sounds great played back by the Denon from a USB drive!
 
Hello All. First time poster here. I am having trouble getting SACDExtractGUI to work in my environment, even though I have zero problem with ISO2DSD. I read all 89 pages of this thread to see if anyone reported a similar problem [and all of CA/AS, which I have followed from the start], and could not find such. If I missed it, please accept my apologies. I was an early PS3 ripper, and then a subsequent ISO2DSD user. Generally, these experiences were very productive. My entire collection of 200+ DSDs resides in my Roon Nucleus+, and is backed up on an NAS. It's not a big deal if I cannot get SACDExtractGUI working, because now, I generally only need to rip an occasional new purchase, and the slight inconvenience of not being able to save to network storage is not a big deal. But I would like to get it working if I can. I am sure this is a user error issue, so would appreciate any guidance.

I have two Oppo 103 players. One is inside my MSB UMT. I am able to rip SACDs from both using ISO2DSD. I have replaced the sacd_extract Unix executable inside my ISO2DSD folder with the latest 3.9 version from SACDExtractGUI. The AutoScript folder on the USB stick that I plug into either of my players is the set from SACDExtractGUI. I am running Mac OS X, currently either Catalina or Big Sur. This is my third time trying to get SACDExtractGUI going under Mojave, Catalina, and now Big Sur. It's been the same outcome each time.

Here is a screen shot from ISO2DSD:
Screen Shot 2020-07-01 at 5.14.50 PM.png

And here is a screen shot from SACDExtractGUI. As you can see, everything seems to test fine, but when I run the app, nothing happens.
Screen Shot 2020-07-01 at 5.20.19 PM.png
 
It Worked!!! I needed to add the AutoScript to a different USB flash drive. After doing that it worked perfectly. Thanks for your help! Looking forward to hearing my SACD's in DSD as they were intended.

Thanks Again!

My pleasure, glad you had another USB flash drive available!
 
The AutoScript folder on the USB stick that I plug into either of my players is the set from SACDExtractGUI.
Good evening and welcome to HFH.

The above quoted portion of your post is the issue, you only use the sacd_extract file in the GUI package with the GUI itself, it is not the same/interchangeable with the one in the AutoScript folder on the USB flash drive.

The USB flash drive contains a different version of the executable unique to the player side of the equation.

So the original Oppo-Cambridge version of the AutoScript folder is what you will use in it's entirety on the USB flash drive, you do not substitute anything there, use it just as is, like you had been with ISO2DSD.

Additionally, I can see from your screenshot that you also need to specify the exact path to sacd_extract in the Program field using the Browse button (overwrite what is currently in that field). There you are pointing the GUI at the sacd_extract component that came in the GUI's download package, it is located in that folder.
 
Good evening and welcome to HFH.

The above quoted portion of your post is the issue, you only use the sacd_extract file in the GUI package with the GUI itself, it is not the same/interchangeable with the one in the AutoScript folder on the USB flash drive.

The USB flash drive contains a different version of the executable unique to the player side of the equation.

So the original Oppo-Cambridge version of the AutoScript folder is what you will use in it's entirety on the USB drive, you do not substitute anything there, use it just as is, like you had been with ISO2DSD.
Thanks for the quick reply. Sorry I was not clear. I am aware of that. The AutoScript folder is the one I have downloaded from the instructions on page 2 of this thread for the Oppo/Cambridge. I only meant to clarify that the USB stick contains the files intended to be placed on the USB stick in conjunction with SACDExtractGUI. IOW, nothing on the USB stick is "left over" from ISO2DSD. I changed nothing inside the folder that I downloaded from the link on p.2. And FWIW, I have tried 4 different USB sticks. All work with ISO2DSD. None works with SACDExtractGUI.

I will update the "Program" field and report back. Also FWIW, here is the complete text at the bottom of the screen shot that seems to have been cut off when I uploaded the file:

Code:
[RUNNING][sacd_extract, -i, 192.168.1.97:2002, -w, -I, -s, -z, -2, -o, /Volumes/ISO Backup]

[DONE]
And yes, running a Mac: Mojave, Catalina, Big Sur.
 
Last edited:
Thanks for the quick reply. Sorry I was not clear. I am aware of that. The AutoScript folder is the one I have downloaded from the instructions on page 2 of this thread for the Oppo/Cambridge. I changed nothing inside the folder.
OK, so the other portion of my post is what needs fixing then, specify the exact path to sacd_extract in the Program field using the Browse button. However if you are using a Mac then there is one additional step, it is detailed on the SACDExtractGUI download post, but I'll repeat it here.

On both macOS, and Linux (but not Windows), you need to designate sacd_extract a worthy Unix executable, because it does not have a signed certificate from a known developer. This is a security feature that happens automatically on a Mac, but it's an easy fix.

Open Utilities -> Terminal and type the following command:

Code:
chmod +x

Followed by a single space after the above code. Then just drag and drop the sacd_extract file onto the Terminal window, at which point it will automatically fill in/populate the file path/name. Press Enter.

Thats all, you can now close Terminal, and the file is now recognized as a Unix executable. All set.
 
I will update the "Program" field and report back. Also FWIW, here is the complete text at the bottom of the screen shot that seems to have been cut off when I uploaded the file:
This solved the problem. If this is specified in the instructions, please forgive me for missing it. On a Mac, it requires two clearances in the Security & Privacy System Preference pane. And I definitely already designated sacd_extract as a worthy Unix executable using "chmod +x" [it ran under ISO2DSD just fine, but SACDExtractGUI seems to require the extra step after correctly setting the file path]. Again, if I missed the two-step, my apologies. Anyway, might be worth highlighting. At any rate, all good. Thank you again for the tremendous amount of intellectual capital, time, and effort put into making this a reality.
 
This solved the problem. If this is specified in the instructions, please forgive me for missing it. On a Mac, it requires two clearances in the Security & Privacy System Preference pane. And I definitely already designated sacd_extract as a worthy Unix executable using "chmod +x" [it ran under ISO2DSD just fine, but SACDExtractGUI seems to require the extra step after correctly setting the file path]. Again, if I missed the two-step, my apologies. Anyway, might be worth highlighting. At any rate, all good. Thank you again for the tremendous amount of intellectual capital, time, and effort put into making this a reality.
My pleasure, yes that's in the instructions but I think I know why sometimes it is passed over, the developer thought it helpful to show something in that field, but it should probably be blank. When users see the field comes pre-populated, they tend to leave it alone, when really what is in that field does need to be overwritten.

The reason ISO2DSD isn't the same way is simple, ISO2DSD is hardcoded to only look in that very same program folder for the executable, you can't put it elsewhere, it has to be in the original downloaded folder or the program won't work.

With SACDExtractGUI, you can place the executable anywhere you want, so long as you point the GUI at it.

The double security thing only happens in Catalina and later, I am running Mojave and there (or earlier) all you need to do is deem sacd_extract a Unix executable and you are all set to go. Starting with Catalina, they make you jump through one additional security hoop with regard to permissions in the Security And Privacy pane of System Preferences as you described.
 
My pleasure, yes that's in the instructions but I think I know why sometimes it is passed over, the developer thought it helpful to show something in that field, but it should probably be blank. When users see the field comes pre-populated, they tend to leave it alone, when really what is in that field does need to be overwritten.

The reason ISO2DSD isn't the same way is simple, ISO2DSD is hardcoded to only look in that very same program folder for the executable, you can't put it elsewhere, it has to be in the original downloaded folder or the program won't work.

With SACDExtractGUI, you can place the executable anywhere you want, so long as you point the GUI at it.

The double security thing only happens in Catalina and later, I am running Mojave and there (or earlier) all you need to do is deem sacd_extract a Unix executable and you are all set to go. Starting with Catalina, they make you jump through one additional security hoop with regard to permissions in the Security And Privacy pane of System Preferences as you described.
Excellent explanations. Thank you. Yes, seeing “sacd_extract” prepopulated in that field—and running the Test and getting what looked like a good result—completely lulled me into not seeing that problem. And correct on Catalina. Same with Big Sur.
 
I just received a BDP-S790 that I picked up on Ebay for $50 shipped. It is suprisingly good condition, so far I have verified that it plays SADCs. It did not come with a remote so I am waiting for one that I ordered to arrive.
 
My pleasure Steve, glad you were able to get the process up and running with no troubles.

I know what you mean about completing that first one, a rather huge sense of having come full circle with the format for those of us who have wanted to rip these discs for years. Good to hear the rip sounds great played back by the Denon from a USB drive!
Here's a recap of my last week:
Saturday - purchased a NOS S5100 locally here on Vancouver Island
Sunday - joined HiFiHaven. Overwhelmed by the volume of posts on SACD ripping. Asked for latest ripping procedures for S5100.
Monday - Mike replied providing just what I asked for.
Tuesday - completed my first rip.
Friday - tearing through my SACD collection, almost completed all the stereo rips. When complete will commence the multi rips.
If only every week was this productive!

Steve
 
Back
Top