Rip SACD with a Blu-ray player

Yes:-) been there done that x2 to be sure no change - I want to be sure its not the config of this machine, I have a couple of simpler boxes that I can use..
Hi Mikey,

Nailed it - works fine did ~25 discs last night and this morning. I will write up a the details and post it tomorrow.

Thanks again for your help.
 
Hi Mikey,

Nailed it - works fine did ~25 discs last night and this morning. I will write up a the details and post it tomorrow.

Thanks again for your help.
Hi Mikey,

In summary, I had a 2 part problem that is now solved.
1. I reinserted the USB drive thinking the AutoScript needed to be rerun - that's been corrected (only insert once).
2. I was using a non-SACD disc - in a 2 CD set, only one of them was an SACD - the SACD discs are labeled DSD and/or SACD.
 

MikeyFresh

Moderator
Staff member
Hi Mikey,

In summary, I had a 2 part problem that is now solved.
1. I reinserted the USB drive thinking the AutoScript needed to be rerun - that's been corrected (only insert once).
2. I was using a non-SACD disc - in a 2 CD set, only one of them was an SACD - the SACD discs are labeled DSD and/or SACD.
Great! Thanks for clarifying, I've revised some older posts in which the instructions stated to remove the USB thumb drive, but they made no explicit mention of not reinserting it.

There had only been a few scattered mentions of that and the potential for problems that it can cause, so I've clarified it in the step-by-steps and as well your post here should put it to rest.
 
OK, I spoke to the developer, and unfortunately it could be bad news for the Blu-ray players involved.

I wish I had better news for the two of you, but maybe it's as simple as the setting above needs revision? Hopefully so, otherwise it could also be a case of having loaded a regular Redbook CD into the tray. Don't laugh.
Lucky day! Just completed my first 3 rips. Sorry for the delay, but I've been traveling for work.

Unfortunately I took the nuclear vs scientific approach. But did these 4 things:
o Reformatted the USB drive (quick)
o Redownloaded the autoscript files
o Reset the BDP-BX510 to factory & then made the changes described in post #446
o Waited to remove the USB until after powering off (going into sleep mode)

Mikey- thanks for all of your help. Couldn't have made it here without you.
 

MikeyFresh

Moderator
Staff member
Lucky day! Just completed my first 3 rips. Sorry for the delay, but I've been traveling for work.
Lucky day indeed, back from your trip and the ripping task is now sorted!

Reset the BDP-BX510 to factory & then made the changes described in post #446
Ok so the golden question for inquiring minds is whether or not the Sony on-screen menu settings had been done previously or not, specifically this one as it directly relates to the error message you were getting:
3. Setup -> Music Settings -> Super Audio CD Playback Layer (SACD)

If the above hadn't been set right, that's why you got that error message. On the other hand, if it had already been correctly set, then you had a Redbook CD in the tray as opposed to an SACD, or a damaged SACD whose TOC and timing code can't be read so the machine defaulted to the CD layer.

Either way, that's much better news than a potentially failing/dodgy laser/mechanism in the player, one of the early symptoms of that is when the player stubbornly refuses to reliably play the SACD layer but seems to have no trouble with the Redbook layer.
Mikey- thanks for all of your help. Couldn't have made it here without you.
My pleasure and happy ripping!
 
Yes, Linux is very very good!

I am beyond impressed at how fast and easy the installation of Linux Mint 19.1 went, I have done various "clean installs" of both Windows and macOS over the years, none of those come close to how fast and easy the install of Mint 19.1 was for me. After the install, and some configuration in the settings that govern the look/theme/font etc... I ended up with this desktop:

View attachment 10351

After installing and configuring the Firefox browser, Thunderbird email client, and JRiver Media Center 24, it was time to set this unit up for SACD ripping using @Nexus3 's Linux compile of sacd_extract 3.9 and SACDExtractGUI.

One difference with Linux Mint as compared to Windows or macOS is there's no need to download and install the Java Runtime Environment, as that's already preinstalled and ready to go with the Linux Mint OS.

The download for the above SACD ripping Linux package is found here.

Once downloaded the package needs to be opened and unzipped, Firefox will prompt for instructions on what to do next:

View attachment 10352




Once opened, the actual unzip is called "Extract" in Linux, use that Extract button on the upper left-hand side of the window:


View attachment 10353


Choose a location for the unzipped files (in this example I chose the Desktop) and complete the Extract:


View attachment 10355

Now show the extracted files, as both the sacd_extract, and SACDExtractGUI.jar will need to be made executable with a Terminal command. Open the Terminal and type the following:

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

Repeat the above Terminal command, this time dragging and dropping the SACDExtractGUI.jar file onto the Terminal window, its file path/name will appear. Press Enter.

Now close the Terminal, you are ready to rip SACD after final configuration of the software settings in the GUI. Double-click and launch the SACDExtractGUI.jar:

View attachment 10357

Final software configuration includes the following:
  • Specify the path to sacd_extract in the Program field using the Browse button.
  • Use the Fing app for iOS/Android or the Blu-ray player's on-screen display to verify its IP address, entering it into the Input field by selecting the Server radio button.
  • Choose what file format(s) to output in the Processing field (the above example is 2-channel stereo DSF tracks only).
  • Choose a destination for the ripped tracks by selecting an Output directory using the Browse button in the Output field.
Lastly, enter the Sony Blu-ray player's on-screen display setup menus and ensure the following Settings:

1. Setup -> Audio Settings -> DSD Output Mode (Off)

2. Setup -> BD/DVD Viewing Settings -> BD Internet Connection (Do not allow)

3. Setup -> Music Settings -> Super Audio CD Playback Layer (SACD)

4. Setup -> System Settings -> Quick Start Mode (On)


And then the moment of truth arrives, assuming the above preparation is complete, you are ready to rip SACD using the following sequence:


Step 1: Power on the Sony Blu-Ray Player, monitor the initial boot sequence via it's front panel display

Step 2: Connect USB thumb drive / AutoScript runs / tray opens automatically / place SACD in tray but don't close it

Step 3: Power down the Sony / tray closes automatically / player goes to sleep / AutoScript gains root access control

Step 4: Pause while Sony display flashes OFF / remove USB thumb drive* / Run rip with one click while the Sony sleeps

Note: Sleep mode is only required with Sony brand units and is unnecessary with the various compatible Oppo, Pioneer, or Cambridge model Blu-ray players. You can only enter Sleep mode by having first enabled the Quick Start menu setting.

* Leave the thumb drive removed from here forward unless power has been physically cut to the machine, or it has been used for general disc playback/movie watching etc... do not reinsert the thumb drive unless one of the above two conditions exists.

Reinserting the thumb drive causes an exhaustion of available RAM in the Blu-ray player, and/or the flash drive to be mounted by the lean-Linux OS at the wrong mounting point, the AutoScript will only work when the flash drive has been mounted by the OS at the primary mount point.

When the rip is finished the GUI will indicate completion by saying [DONE]:

View attachment 10358

Now visit whatever destination you designated as the Output directory, and there you will find the finished ripped SACD album.
These Linux steps were also super helpful for Windows. Everything went smooth except I experienced an issue that the Sony S590 didn't like my Sandisk Extreme 32GB USB3 drive no matter what size I made the partition regardless of FAT32/FAT/exFAT/NTFS.
Switching to an 8GB Sandisk Cruiser with FAT32 worked perfectly.
 

MikeyFresh

Moderator
Staff member
Over the weekend a breakthrough was made which has the potential to add more Blu-ray player models to the known compatibility list. For now the process is still being refined and is described by Mindset as "hacky" which likely means too complex for those of us in plain clothes. We'll see if this can be boiled down to an AutoScript version that is essentially plug and play as with the current compatible models.

I actually played a small part in this, not from an implementation standpoint, and my initial idea was actually somewhat primitive, I merely suggested just trying the Oppo script on the 2014 model year Sonys that are currently incompatible, and that did not work. That lead to one of the key contributors just wondering aloud what might happen if elements of the Oppo script were combined with elements of the Pioneer-Sony script, and then tested on certain currently incompatible models.

That got the wheels spinning with these Linux experts, and they have now successfully combined elements of both scripts to create an AutoScript version that worked on the previously incompatible BDP-S790 (actually a 2012 model year player that was stubbornly refusing to cooperate until now), and also the 2014 model year S6200.

I also submit this may be the solution to the mysterious high-end Pioneer LX-58/88 incompatibility, though that will be much harder to sort as those were expensive players sold primarily in Japan, and thus not widely available for further testing.

Anyone owning an S790, or a 2014 model year Sony Blu-ray player such as the S6200 (or really any 2014-15 Sony that is capable of SACD playback), please stay tuned to this channel.
 
Hi Everyone,

It has taken me a little while to post my thoughts and thanks to Mikey but here goes:

Firstly I have to say what a top bloke Mikey is.

I had a few issues with my initial attempt, using a Cambridge Azur 752 BD.

These were entirely down to me not fully understanding the importance of the connection between the PC/Player and the router.

I use Ethernet Powered Adaptors set up in my home, to save on any cabling running through the house. This works a treat normally but not when I was trying to use the SACD Extract Gui method. It threw a wobbly and planted a Microsoft sniffer called Nmap in the PC network setup, this prevented the network from working, on how I had it organised, with the adaptors.

I then changed tack. Rather then use the Azur for ripping, I purchased a Sony S4100, relatively cheap, on eBay.
I then hard wired the Sony player and the PC to the router, bypassing the adaptors.
This did the trick!!
It all worked seamlessly and I have now ripped my entire collection of multichannel SACD's (over 275)

I hope this explanation will help others to carry out successful ripping. Yes it is a bit daunting at first but once its up and running, you can sit back and relax!!

Thanks again Mikey :cool::vegetalia
 

MikeyFresh

Moderator
Staff member
Hi Everyone,

It has taken me a little while to post my thoughts and thanks to Mikey but here goes:

Firstly I have to say what a top bloke Mikey is.

I had a few issues with my initial attempt, using a Cambridge Azur 753 BD.

These were entirely down to me not fully understanding the importance of the connection between the PC/Player and the router.

I use Ethernet Powered Adaptors set up in my home, to save on any cabling running through the house. This works a treat normally but not when I was trying to use the SACD Extract Gui method. It threw a wobbly and planted a Microsoft sniffer called Nmap in the PC network setup, this prevented the network from working, on how I had it organised, with the adaptors.

I then changed tack. Rather then use the Azur for ripping, I purchased a Sony S4100, relatively cheap, on eBay.
I then hard wired the Sony player and the PC to the router, bypassing the adaptors.
This did the trick!!
It all worked seamlessly and I have now ripped my entire collection of multichannel SACD's (over 275)

I hope this explanation will help others to carry out successful ripping. Yes it is a bit daunting at first but once its up and running, you can sit back and relax!!

Thanks again Mikey :cool::vegetalia
Kingy,

Thats outstanding! Way to stay at it!

I like the strategy of using an inexpensive S4100 for the SACD rip heavy lifting. The Azur 752 is a really nice machine and if you are counting on it well into the future, it makes perfect sense to pick up a 2nd-hand Sony and remove the wear and tear of SACD rips from the nicer unit.

Congrats again!
 
Hello,
I've been using the methods of this forum for a few months now with very few issues, however, I am running in to issues with certain SACDs and I'm not 100% sure why. I believe it has something to do with the characters in the file name on the disc, but not in every case. All are surround sound, but I can't get their stereo portions to rip either so I think that's a coincidence. I've also ripped probably 70 multichannel albums with no issues (ripped both the stereo tracks and the multichannel tracks for all of them).

I'm using a Sony BDP-S5100. I have several albums that keep aborting before they rip any tracks. Specifically the below (names are copy/pasted from the rip folder, as this is what the program is attempting to title the albums):

1. "Los Angeles Philharmonic Conductor Esa-Pekka Salonen - Stravinsky Le Sacre du printemps Bartók The Miraculous" -Deutsche Grammophon, 2006 (link)
2. "Royal Flemish Philharmonic, conducted by Philippe Herrewegh - Ludwig van Beethoven Symphony No.4 in B flat, Op.60 & Symp"-Pentatone, 2011 (link)
3. "Ludwig Ruckdeschel an der größten Domorgel der Welt im Do - Klang Raum Dom - Orgelmusik aus drei Jahrhunderten" - Symicon, 2004 (link)

The first and third albums have strange characters that I thought might be messing up the program (you can see how they are misinterpreted by windows), but the second album doesn't appear to have anything like that. Here's the readout from SACDExtract for the second album:

"Processing [C:\Users\CJ\Desktop\SACD Rips\Royal Flemish Philharmonic, conducted by Philippe Herrewegh - Ludwig van Beethoven Symphony No.4 in B flat, Op.60 & Symp\01 - Royal Flemish Philharmonic, conducted by Philippe Herrewegh - Symphony No.4 in B flat, Op.60 - Adagio - Allegro vivace.dsf] (1/8)..
[DONE]"


Any ideas what might be wrong? These won't rip in stereo, multi, on DSF, DSDIFF, ISO, anything.


PS. my version of SACD Extract says "SACDExtractGUI v0.1-5-g97d05f95" and "sacd_extract version 0.3.9@setmind-8-gae5301f0419644a946479cb9b59bdd5c6cfcf71e" if that matters.

I appreciate the help, and thanks for the great program!
CJ
 

MikeyFresh

Moderator
Staff member
Hello,
I've been using the methods of this forum for a few months now with very few issues, however, I am running in to issues with certain SACDs and I'm not 100% sure why. I believe it has something to do with the characters in the file name on the disc, but not in every case. All are surround sound, but I can't get their stereo portions to rip either so I think that's a coincidence. I've also ripped probably 70 multichannel albums with no issues (ripped both the stereo tracks and the multichannel tracks for all of them).

I'm using a Sony BDP-S5100. I have several albums that keep aborting before they rip any tracks. Specifically the below (names are copy/pasted from the rip folder, as this is what the program is attempting to title the albums):

1. "Los Angeles Philharmonic Conductor Esa-Pekka Salonen - Stravinsky Le Sacre du printemps Bartók The Miraculous" -Deutsche Grammophon, 2006 (link)
2. "Royal Flemish Philharmonic, conducted by Philippe Herrewegh - Ludwig van Beethoven Symphony No.4 in B flat, Op.60 & Symp"-Pentatone, 2011 (link)
3. "Ludwig Ruckdeschel an der größten Domorgel der Welt im Do - Klang Raum Dom - Orgelmusik aus drei Jahrhunderten" - Symicon, 2004 (link)

The first and third albums have strange characters that I thought might be messing up the program (you can see how they are misinterpreted by windows), but the second album doesn't appear to have anything like that. Here's the readout from SACDExtract for the second album:

"Processing [C:\Users\CJ\Desktop\SACD Rips\Royal Flemish Philharmonic, conducted by Philippe Herrewegh - Ludwig van Beethoven Symphony No.4 in B flat, Op.60 & Symp\01 - Royal Flemish Philharmonic, conducted by Philippe Herrewegh - Symphony No.4 in B flat, Op.60 - Adagio - Allegro vivace.dsf] (1/8)..
[DONE]"


Any ideas what might be wrong? These won't rip in stereo, multi, on DSF, DSDIFF, ISO, anything.


PS. my version of SACD Extract says "SACDExtractGUI v0.1-5-g97d05f95" and "sacd_extract version 0.3.9@setmind-8-gae5301f0419644a946479cb9b59bdd5c6cfcf71e" if that matters.

I appreciate the help, and thanks for the great program!
CJ
Likely Disc 1 and 3 have the issue of so-called diacritical characters, while Disc 2 is simply too lengthy a title and thus when you add in the track name the path becomes too long. I'm puzzled by the diacritical mark issue because it was supposed to have been resolved for server method ripping, and I myself have not had that problem arise using either a Mac or Linux, so I wonder if that's a Windows issue.

One thing you can try is to use an Output directory destination that is very short, I mean, name it literally one character.

So as a test, try writing the files to a thumb drive that you have named "R" for rips (lose the quotation marks of course). No other folders or anything else, just that one letter as the name of the thumb drive, then try to rip to that output directory. See if shortening the path in that way actually allows the rip to commence. Even if it does, certain tracks may still fail if they are really long in character length.

You can also have a look at the data side of the disc and make sure that there are no obvious scratches, scuffs, or detritus that have damaged the timing code or TOC. If you see scratches/scuffs or anything else that doesn't belong on the disc, try to lightly clean and polish it.

Lastly, it does appear some discs simply have issues with the way they were authored such that they are not rippable. It is unclear what those issues exactly are, it could just be the tracks have too lengthy a character length, or it could be something else.

Can you actually play these very same discs in the S5100? If yes, then it isn't a problem with the timing code or TOC being damaged, it is down to the way it was authored.
 
Likely Disc 1 and 3 have the issue of so-called diacritical characters, while Disc 2 is simply too lengthy a title and thus when you add in the track name the path becomes too long.

One thing you can try is to use an Output directory destination that is very short, I mean, name it literally one character.

So as a test, try writing the files to a thumb drive that you have named R for rips. No other folders or anything else. See if shortening the path in that way actually allows the rip to commence. Even if it does, certain tracks may still fail if they are really long in character length.

You can also have a look at the data side of the disc and make sure that there are no obvious scratches, scuffs, or detritus that have damaged the timing code or TOC. If you see scratches/scuffs or anything else that doesn't belong on the disc, try to lightly clean and polish it.

Lastly, it does appear some discs simply have issues with they way they were authored such that they are not rippable. It is unclear what those issues exactly are, it could just be the tracks have too lengthy a character length, or it could be something else.

Can you actually play these very same discs in the S5100? If yes, then it isn't a problem with the timing code or TOC being damaged, it is down to the way it was authored.
Thanks for the input. I can play them from the S5100. I tried the usb drive method just now and unfortunately it still didn't work. Maybe it was just authored in such a way as to make ripping difficult or impossible. Let's hope they don't get wise to that!
 

MikeyFresh

Moderator
Staff member
Thanks for the input. I can play them from the S5100. I tried the usb drive method just now and unfortunately it still didn't work. Maybe it was just authored in such a way as to make ripping difficult or impossible. Let's hope they don't get wise to that!
It's the excessive path length on some classical titles, where everything under the sun such as the title of the piece/work, the composer, the conductor, the orchestra, and then the actual track name make that file path too lengthy.
 

airdronian

Junior Member
It's the excessive path length on some classical titles, where everything under the sun such as the title of the piece/work, the composer, the conductor, the orchestra, and then the actual track name make that file path too lengthy.
I guess you can't really edit the metadata until it's ripped, can you ?
 

MikeyFresh

Moderator
Staff member
I guess you can't really edit the metadata until it's ripped, can you ?
Not with the server method, I believe it may be possible when using the so-called "local method" in which the files are written to the same USB thumb drive that houses the AutoScript. That is done via a Telnet session, typically with PuTTY, and is therefore much more complex and requiring more than just basic computing skills.

Many people have loads of issues trying to get that method to work at all, which is why I've only detailed the server method using a GUI here. That arcane CLI stuff just isn't fun for most people, and I would be unable to provide support for it.
 
Great thanks for blazing the trail! I was looking for a simple method to extract the stereo contents from a collection of SACDs to listen on my Topping D30 / JDS Labs Atom / Sennheiser HD600s, and have found this great forum. Ordered a refurbished Sony S590 on Amazon and over the weekend extracted 2-channel DSD from all my SACDs.

I connected the Atom amp directly to the S590 analog outs and listened to a couple of SACDs, and then ran the extracted dsf files through the Topping DAC for comparison. The quality of the sound is much better with the Topping.

The extraction method is flawless. One minor inconvenience: every 10 or so disks the java application (I tested both SACDExtractGUI and ISO2DSD) would return an error:
Failed to connect
libsacdread: Can't open 192.168.1.181:2002 for reading

The only way I colud clear this problem was by rebooting the player (basically, pulling the plug off). My suspicion is there is perhaps a memory leak in the server executable sacd_extract_160 and after a series of runs the process grows too big. But I can be wrong with my diagnosis - I didn't try to telnet into the box and collect more info.

Thanks again,
Jerry
 
Great thanks for blazing the trail! I was looking for a simple method to extract the stereo contents from a collection of SACDs to listen on my Topping D30 / JDS Labs Atom / Sennheiser HD600s, and have found this great forum. Ordered a refurbished Sony S590 on Amazon and over the weekend extracted 2-channel DSD from all my SACDs.

I connected the Atom amp directly to the S590 analog outs and listened to a couple of SACDs, and then ran the extracted dsf files through the Topping DAC for comparison. The quality of the sound is much better with the Topping.

The extraction method is flawless. One minor inconvenience: every 10 or so disks the java application (I tested both SACDExtractGUI and ISO2DSD) would return an error:
Failed to connect
libsacdread: Can't open 192.168.1.181:2002 for reading

The only way I colud clear this problem was by rebooting the player (basically, pulling the plug off). My suspicion is there is perhaps a memory leak in the server executable sacd_extract_160 and after a series of runs the process grows too big. But I can be wrong with my diagnosis - I didn't try to telnet into the box and collect more info.

Thanks again,
Jerry
I use a Sony BX-59 and experience the same issue with SACDExtractGUI failing to connect after a number of discs. I also power down the BX-59 and removal power for 5-10 seconds and it the problem is cleared. If I recall correctly I'm able to ping the BX-59 via apple terminal and the BX-59 returns a response when in this condition.
 

MikeyFresh

Moderator
Staff member
Great thanks for blazing the trail!
Welcome aboard Jerry, glad you got the process going and were able to rip your collection!

The extraction method is flawless. One minor inconvenience: every 10 or so disks the java application (I tested both SACDExtractGUI and ISO2DSD) would return an error:
Failed to connect
libsacdread: Can't open 192.168.1.181:2002 for reading

The only way I colud clear this problem was by rebooting the player (basically, pulling the plug off). My suspicion is there is perhaps a memory leak in the server executable sacd_extract_160 and after a series of runs the process grows too big. But I can be wrong with my diagnosis - I didn't try to telnet into the box and collect more info.
I use a Sony BX-59 and experience the same issue with SACDExtractGUI failing to connect after a number of discs. I also power down the BX-59 and removal power for 5-10 seconds and it the problem is cleared. If I recall correctly I'm able to ping the BX-59 via apple terminal and the BX-59 returns a response when in this condition.
In the above two member's experience, is this happening after you have removed the thumb drive and left it out entirely for the subsequent rips, or are you reinserting the thumb drive and running the script anew for each rip?

I ask because this was not well explained by me originally, and only recently did I revise various older posts to make it more clear. Originally, all it said in the step-by-step instructions was to remove the thumb drive, and there were also a few other scattered posts that stated you could then leave the drive out and successfully execute additional rips.

What it did not originally state clearly (but now does after various revisions) is that the thumb drive should be removed and should not be reinserted at all unless power has been cut to the machine. Reinsertion of the thumb drive causes two different problems, one is that the machine's very limited available RAM will eventually become exhausted upon repeated reinsertion and rerunning of the script. The second problem is the thumb drive will eventually fail to be mounted by the OS in the primary position, which breaks the process.

So are both of you above saying you had read those recent post revisions, and this issue still happens after a bunch of consecutive rips even if the thumb drive was removed and never reinserted?
 
Welcome aboard Jerry, glad you got the process going and were able to rip your collection!





In the above two member's experience, is this happening after you have removed the thumb drive and left it out entirely for the subsequent rips, or are you reinserting the thumb drive and running the script anew for each rip?

I ask because this was not well explained by me originally, and only recently did I revise various older posts to make it more clear. Originally, all it said in the step-by-step instructions was to remove the thumb drive, and there were also a few other scattered posts that stated you could then leave the drive out and execute additional rips.

What it did not originally state clearly (but now does after various revisions) is that the thumb drive should be removed and should not be reinserted at all unless power has been cut to the machine. Reinsertion of the thumb drive causes two different problems, one is that the machine's very limited available RAM will eventually become exhausted upon repeated reinsertion and rerunning of the script. The second problem is the thumb drive will eventually fail to be mounted by the OS in the primary position, which breaks the process.

So are both of you above saying you had read those recent post revisions, and this issue still happens after a bunch of consecutive rips even if the thumb drive was removed and never reinserted?
I believe I've read the posts prior to the updates. I ran into the exact problems you describe above, and have been leaving the USB stick inserted as that provided better results. I'll now try removing the USB stick as instructed and go from there.

Thank you
 
I believe I've read the posts prior to the updates. I ran into the exact problems you describe above, and have been leaving the USB stick inserted as that provided better results. I'll now try removing the USB stick as instructed and go from there.

Thank you
I looked at the script file in the AutoScript directory. There is a command to start the server process in the background, so yes, it makes sense to remove the thumb drive after the first time the script runs - there should be only one server listening on port 2002. And that’s what I was doing yesterday...
 
Top