Rip SACD with a Blu-ray player

[MikeyFresh]

Now I just need to figure out how play back the files

We have a DSD playback options thread for that topic.

 

[MikeyFresh]

Step 7 shouldn't be necessary.

Thats correct, and the 2nd part of Step 3 is also unnecessary, just pressing Power OFF makes the drawer close and the machine enters sleep without any open/close button presses.

 

[nospoonboy]

Hello, I am new to the group and have been reading this thread for weeks in preparation.

Thank you so much for this guide and thread...but alas, I have been spending many hours without success. I have purchased a Sony BDP-S5100 and am running MacOS High Sierra 10.13.6 on a Mac Mini. I have successfully connected the Sony to my network via WiFi and everything with the machine looks to be in order. So far so good, but I have a few questions:

1. Do I have to compile the sacd_extract into a separate .dmg program? -- I followed the Terminal script directions and did not "have an sacd_extract v3.9 Unix Executable for Mac in your Home Directory" I searched my computer and found no such file that was created?

2. Do I need to do this prior to running iso2dsd_gui.jar? -- I have the USB with the AutoScript folder...I followed those steps and the Sony behaves exactly as described in the directions. When I attempted to extract with iso2dsd I got a "failed to connect" libsacdread message.

Any assistance would be very much appreciated. Thank you in advance for your time and attention.

 

[MikeyFresh]

Hello, I am new to the group and have been reading this thread for weeks in preparation.

Thank you so much for this guide and thread...but alas, I have been spending many hours without success. I have purchased a Sony BDP-S5100 and am running MacOS High Sierra 10.13.6 on a Mac Mini. I have successfully connected the Sony to my network via WiFi and everything with the machine looks to be in order. So far so good, but I have a few questions:

1. Do I have to compile the sacd_extract into a separate .dmg program? -- I followed the Terminal script directions and did not "have an sacd_extract v3.9 Unix Executable for Mac in your Home Directory" I searched my computer and found no such file that was created?

2. Do I need to do this prior to running iso2dsd_gui.jar? -- I have the USB with the AutoScript folder...I followed those steps and the Sony behaves exactly as described in the directions. When I attempted to extract with iso2dsd I got a "failed to connect" libsacdread message.

Any assistance would be very much appreciated. Thank you in advance for your time and attention.

Welcome to HiFi Haven. We'll get you sorted out in short order.

If you followed the instructions to a "T" and compiled sacd_extract 3.9 successfully, there would be a file called sacd_extract in your home directory. If you are absolutely certain you've looked in that home directory and it isn't there, then something went wrong with that process.

If you are unsure as to where to look, that path will look something like the below example:

Mike's MacBook Air -> Users -> Mike -> sacd-ripper-> sacd_extract

Take another look, and if you still don't see it, we'll take a quick short-cut to get you up and running.

 

[nospoonboy]

Welcome to HiFi Haven. We'll get you sorted out in short order.

If you followed the instructions to a "T" and compiled sacd_extract 3.9 successfully, there would be a file called sacd_extract in your home directory. If you are absolutely certain you've looked in that home directory and it isn't there, then something went wrong with that process.

If you are unsure as to where to look, that path will look something like the below example:

Mike's MacBook Air -> Users -> Mike -> sacd-ripper-> sacd_extract

Take another look, and if you still don't see it, we'll take a quick short-cut to get you up and running.

Thank you so much for your reply. Before we try a workaround let me verify a few things about the Terminal info. I have tried this 5 times today...so here are some issues:

This is the text EXACTLY as I have entered it:

xcode-select --install

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

brew install cmake

git clone setmind/sacd-ripper

cd sacd-ripper/tools/sacd_extract

cmake .

make

1. Do I need to make any alterations to any of the above text or type it all exactly as is?
2. Is the end of each line a return/enter? or is supposed to be typed all as one line? (I have tried both ways)
3. I have tried to copy and paste and also enter the text...and I have verified that none of these have created the sacd-ripper-> sacd_extract in my home directory

 

[MikeyFresh]

1. Do I need to make any alterations to any of the above text or type it all exactly as is?

I do see one difference in the 4th line compared to the original code, however it is late on a Saturday night and I've already had a couple of Jack Daniel's, so lets please just skip that for now, we can always come back to it. OK?

2. Is the end of each line a return/enter?

Yes, but again, we can always come back to this, right now we'll skip it.

3. I have tried to copy and paste and also enter the text...and I have verified that none of these have created the sacd-ripper-> sacd_extract in my home directory

OK, tough to say exactly what is going on there, but we'll need to leave it for now and come back to it if need be. We will also be setting aside (for the moment) ISO2DSD, close it if it's open, don't worry it doesn't need to be abandoned, just put on the back burner for now.

The above way of compiling sacd_extract 3.9 for Mac was originally a required thing, as we did not have a pre-compiled hosted source from which to download from.

Since November 24, 2018 we do have a precompiled download source courtesy of our own @Nexus3 . So for ease of troubleshooting and getting you going right here and now, we'll use that, and we can always return to the above if need be.

The only additional thing we'll need to do with the download source is deem it a UNIX Executable, as your Mac will not trust it like it would if you compiled it yourself from sources (i.e. you are the developer there, but not with the download). There will be a single line of code in Terminal to deem the downloaded version executable, that's it, and it will work. Ready?

The download is found on Page 15 of this thread in Post # 284. Click the spoiler for Intel/AMD platforms x64, and download the Mac OS package. Unzip it to your desktop for the time being, though it doesn't actually matter where you put it, and eventually you'll probably want it in your Applications folder.

Once that is done, you'll need to deem the sacd_extract portion of the package a worthy UNIX Executable by way of the following single line of code:

Type the following command in Terminal:

chmod +x

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

Then simply close the Terminal window, and you will now have a Unix Executable inside the download package, and be ready to rip.

Please advise when the above is done.

 

[nospoonboy]

So I completed the steps and here is what terminal looked like:



Am I now suppose to have a sacd_extract in my home folder? Or is this suppose to run in the background and allow the SACDExtractGUI.jar to operate? I am sorry, but I am still confused about how these programs work together and how sacd_extract is related to iso2dsd.

Thank you so much for your help!

 

[MikeyFresh]

So I completed the steps and here is what terminal looked like:

You lost me, which steps? The download and unzip of SACDExtractGUI from Post # 284 that I described directly above?
If so then you are no longer looking in your home directory (that was only for the compile that you were attempting yourself that we have set aside for now).

Now you'd be looking in that same download package folder to see that the sacd_extract piece is indeed a Unix Executable (the single line of code is a command that tells the Mac to allow that file to be executable).

So if you did the above, the SACDExtractGUI folder will look something like this:


If you have the above, Great!
Double check/be sure that you do not have any remaining instance of ISO2DSD still running and if you do, kill it with the red radio button in the upper left-hand corner of that window (never use ISO2DSD's Quit button as it has a bug).

Please advise if you do have the above folder/files in the screenshot.

 

[MikeyFresh]

Or is this suppose to run in the background and allow the SACDExtractGUI.jar to operate? I am sorry, but I am still confused about how these programs work together and how sacd_extract is related to iso2dsd.

Yes, it runs in the background, SACDExtractGUI is just a Java-based front-end interface that allows you to use the executable in a GUI environment rather than through arcane Terminal commands. Please for now forget ISO2DSD, we can come back to it, but for now we are not using it in any way. Make sure it isn't still running.

 

[nospoonboy]

The steps I was referring to were the steps that you had listed in your previous post #586 :-)

Here is what I have now:



And I have confirmed that I do not have ISO2DSD running (I checked activity monitor to verify).

 

[MikeyFresh]

Then you are good to go for final settings configuration and ripping!

First we'll do the final software configuration, then one more check of the Blu-ray player itself.

Click/launch the SACDExtractGUI.jar file you have in the folder to bring up the user interface:



Final software configuration includes the following:

• Specify the path to sacd_extract in the Program field using the Browse button (overwrite that field).
• 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.

When the above is done please fully power cycle the Blu-ray player by removing the USB thumb drive, Power OFF, then remove and replace the AC power cord. Once the unit does an initial boot sequence when the power cord is replaced, it should then enter sleep mode if you had already configured it (enabled Quick Start). Leave the USB thumb drive aside for right now and double check the following on-screen menu 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)

It is at this point you are ready to rip an SACD:

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 / disc tray opens automatically / place SACD in tray but don't close it

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

Step 4: Wait for Sony display to cease flashing OFF* / remove USB thumb drive** / Run rip with one click while the Sony sleeps

*S390/BX39 users just wait 5 full seconds in lieu of display going dark

** 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 those two conditions exists.

Any repeated reinsertion of the thumb drive causes an early 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]:



Now visit whatever destination you designated as the Output directory, and there you will find a folder with the finished ripped SACD album!

You can do approximately 7-8 consecutive rips by repeating the above process, just open the disc tray, place a new disc in it, and once again close the tray with the Power OFF button. After approximately 7-8 consecutive rips, the player's very limited RAM will be exhausted, and a full power cycle with the thumb drive removed is necessary, followed by a reinsertion of the thumb drive, after which you'll then get another 7-8 consecutive rips before the same thing happens again. Rinse and repeat.

 

[nospoonboy]

I have followed the above directions and I recieved a "Failed to connect" message.



I pinged the Sony and this was the result:



I am at a loss :-(

 

[MikeyFresh]

I have followed the above directions and I recieved a "Failed to connect" message.

View attachment 11754

I pinged the Sony and this was the result:

View attachment 11755

I am at a loss :-(

OK, and if you use the Test button in the Program field, it finds sacd_extract?

Similarly, if you can Ping that IP, can you also use that Test button in the Server field to see if Port 2002 is open?

 

[nospoonboy]

Ah ha...so the sacd_extract test was successful, however the test for Port 2002 failed:



Is there a workaround for this?

 

[MikeyFresh]

Not a workaround per se, but a look at two possibilities.

Can you post a screenshot of what the USB thumb drive folder looks like when viewed in Finder?

 

[nospoonboy]

 

[MikeyFresh]

Ok, there are your two issues, one of which is major, but they are so easily solved you won't believe it.

First, delete both of those SanDisk bloatware crap items the thumb drive shipped with. If you think they are in some way useful or valuable (they aren't), just save copies to your Desktop or some other safe keeping place, but remove it completely from the thumb drive which means delete and empty the Trash too if they end up there. This is the minor issue.

Second, you have the wrong version of the AutoScript for an S5100, and that one is on you. The instructions clearly state which player models use the ARMv7 version (evidenced by sacd_extract_6200 in the folder), your S5100 is NOT one of the players that uses that script. Thats the major issue.

So, delete the entire AutoScript folder you have there (again empty the Trash if it ends up there), it won't work with an S5100, and download the Pioneer-Sony script found on Page 2 of this thread. You can delete the Buda folder too, but the Blu-ray player will just place a new one there, so it really doesn't matter if you delete the Buda folder or not.

Once again, ensure that you actually have an enclosing folder called AutoScript, and do not click into any of it's contents for any reason, just leave them alone after ensuring you have the correct enclosing folder structure, it should look like this:

Now eject the thumb drive, fully power cycle the S5100 one more time, and proceed from the instructions above to execute a rip.

 

[nospoonboy]

Mikey, I cannot thank you enough! You're right, this was on me (I think I was confused by the list of Sony players and got it in my head that I was supposed to use the new ware for the Sony...oh well). I appreciate your patience.

I have successfully ripped my first disc! Listening to Mahler's 6th right now in DFF with Audirvana.
So is the ISO2DSD program to convert the DFF to FLAC? Not sure what people are using the ISO2DSD for.

 

[MikeyFresh]

Mikey, I cannot thank you enough! You're right, this was on me (I think I was confused by the list of Sony players and got it in my head that I was supposed to use the new ware for the Sony...oh well). I appreciate your patience.

No problem, it's my pleasure, last night I was just watching favorable outcomes in the NCAA basketball tourney while we started sorting your problem. I am in 1st place currently in my office pool! 🏀

I have successfully ripped my first disc! Listening to Mahler's 6th right now in DFF with Audirvana.

Now that's the name of the game! 🔨

So is the ISO2DSD program to convert the DFF to FLAC? Not sure what people are using the ISO2DSD for.

Prior to October 2018, there was no such thing as SACDExtractGUI, so we used ISO2DSD for the entire process by default.

Since the advent of SACDExtractGUI, most people have migrated to it but many (like me) chose not to just kick the venerable ISO2DSD to the curb, instead opting to update the sacd_extract piece in that package (ISO2DSD contains sacd_extract 3.7 which is now old).

Doing so gives you the rip speed increases available from the new package, but not the additional functionality.

So last night when I was imploring you to leave ISO2DSD off to the side, that was because it does not have the test buttons needed to zero in on problems when troubleshooting. We would have figured out what was going on anyway, but it would have taken longer. Back in the good ole' days (prior to Oct. 2018) it was all we had to work with, so troubleshooting was harder.

SACDExtractGUI now allows us to more rapidly narrow the choices for what the problem is, though you still need to know where to look to confirm. You had multiple issues going on last night, I still have no idea why your own attempts to compile sacd_extract 3.9 failed, but at this point it's moot, we just used @Nexus3 's compile for macOS instead.

However nothing was going to work at all when using the wrong version of the AutoScript. You aren't the only one to have ever done that, and there are plans to revamp that aspect too so it is a little more clear both from a file naming aspect, and how those files are housed in the cloud repository. We'll get there, in the meantime it can be a touch confusing, but it's nothing that can't be overcome just by checking a few things.

 

[nospoonboy]

This answers my question about ISO2DSD. I am very happy with the ripping speed as I just finished ripping my 3rd disc.

P.S. good luck with the office pool