Rip SACD with a Blu-ray player

MikeyFresh

Moderator
Staff member
Wow! Amazing! Done my first SACD rip on a Sony S4100 - Da Capo by Love in stereo only. Came out at 24/96 after converting DSF to Flac. Listening to it now - sounds great, better than I’ve ever heard it.

I got the proceedure wrong at first and my PC lost its network connection a couple of times. Once I went through the first couple of pages of this thread all became clear and it worked a treat.

Many thanks, Mikey.
My pleasure John, glad it worked out with a minimum of trouble. Once again welcome to HFH!
 

MikeyFresh

Moderator
Staff member
Apologies if this has been mentioned before.

My set up for ripping is a Sony BDP-S5100 (using fixed IP) which is a wired Ethernet connected to a Netgear GS110TP network switch to which the router, PC and a NAS is connected also via wired Ethernet connection.

I found the quickest way to extract .dsf files from a SACD was to extract the .ISO image first, them use the power of the PC to extract the .dsf files very quickly. Extracting the .ISO from the SACD, ISO2DSD was reporting the transfer rate at typically 3.0 MBs/s, whereas extracting the .dsf files from the disc was usually 2.0MBs/s and sometimes even slower.

If you have lots of SACDs that you want to rip to .dsf files then consider extracting the .ISO first. It will save you a lot of time, albeit at the expense of disc space, but the advantage you get is not only speed but a backup .ISO of your SACD. :)

Cheers,
Alan
This is so true and while it has been mentioned at a couple of different points in the thread, it does bear repeating. Many people do like to keep the ISO as an archival back-up, but the main benefit of DSF extraction from the ISO as opposed to the SACD itself is one of speed. That speed varies both there, and also when extracting directly from the SACD based on a number of factors including whether or not the disc contains multichannel content, and of course whether or not you are electing to extract that multichannel content.

So the ISO creation goes faster of course when there is only stereo and no multichannel content, but that multichannel content slows the DSF extraction even far more, if you choose to undo the lossless compression called DST.

The above is only possible with sacd_extract 3.9 and SACDExtractGUI as the front end, you can't do that in ISO2DSD.

Fastest of all if keeping the ISO for archival purposes is using sacd_extract 3.9 and SACDExtractGUI in "concurrent mode", whereby the Blu-ray player makes one single pass of the disc and the software creates both the ISO and the DSF extraction at the same time. Exactly how fast that goes depends on your PC's processing power, and again, whether or not there is any multichannel content present on the disc along with whether or not you choose to decompress it (stereo is not subject to the DST lossless compression only the multichannel content is).
 

MikeyFresh

Moderator
Staff member
Tonight I successfully tested the release candidate 2 versions of the forthcoming AutoRip scripts on a Sony S7200. Many thanks go out to @Nexus3 for his help.

I'm told @walkaround also successfully tested this in Europe earlier yesterday, so it increasingly looks like a final release of this AutoRip script for at least some of the SACD rip compatible Blu-ray player models is imminent.

These AutoRip scripts allow for dispensing of the computer, network, Java, and GUI in executing an SACD rip, substituted with only the insertion of the USB thumb drive into the Blu-ray player in order to rip an ISO of the disc to that very same thumb drive.

The Sony-sleep version of this script (called A3) for S6200/7200 is unbelievably elegant, the USB thumb drive is inserted with the player already sleeping, it briefly awakens to automatically open the disc tray and the process involves placing a disc in the tray, and that's it. After 10 seconds the tray automatically closes and the rip to ISO starts about 5 seconds later. When the rip is finished, the disc tray automatically opens. Beyond easy and cool. Various versions of AutoRip are being worked on for the different SACD rip compatible Blu-ray players.

You do still eventually need a computer and the GUI software package in order to extract .dsf tracks from the ISO, or if your media player software is ISO compatible (eg. JRiver, Foobar, etc) then no extraction is even necessary, you could just play the ISO.

More to come on AutoRip, please stay tuned to this channel.
 
I started reading this thread yesterday and was a little sceptical. I already had ISO2DSD software as I have a number of SACD ISO's that I'd converted to DSF. I had a Sony BDP-S7200 which I had used for playing SACDs before getting the OPPO 203. As I had the necessary tools I thought why not give it a go. I put the USB drive in the front slot initially and the process wouldn't work. Tried a few more times and still nothing. Was about to give up when I decided to move the USB to the rear slot. Fired up right away and about 15 / 20 minutes later had a ripped multi channel copy of Gloria Estefan Greatest Hits. It was an easy process compared to what I'd read previously. Well done to the writers of the script.
 
Sony-sleep version of this script (called A3) for S6200/7200 is unbelievably elegant,
Hello Mikey,

trying these AutoScript versions for my BDP-S490, is it possible to close port 2002 forever? Returning to the original old AutoScript version I always get "port 2002 is inaccessible" message. Ping is ok.
Thanks, Andras
 

MikeyFresh

Moderator
Staff member
Hello Mikey,

trying these AutoScript versions for my BDP-S490, is it possible to close port 2002 forever? Returning to the original old AutoScript version I always get "port 2002 is inaccessible" message. Ping is ok.
Thanks, Andras
Andras - No it is not possible, none of these scripts are ever stored in non-volatile memory or made permanent. You are not actually altering the unit's firmware in any way.

The only thing these scripts actually do is grab root access control of the player's lean-Linux OS, and tell it to output the disc's data over the network or USB ports. That is all.

To clear the script do a full power cycle reset, this means remove the thumb drive, power OFF, then pull and replace the AC power cord. The unit is now back to square one and operating normally.

Do not power On the unit with a thumb drive already inserted, always allow the machine's initial boot sequence to take place before inserting any thumb drives.

When you try the A1 AutoRip, you do not use any sleep method. A1 involves closing the disc tray normally, and then a toggle of the stereo/multichannel Music Setting in the player's on-screen displayed menu in order for AutoRip to gain root access/control. Once you do that stereo/multichannel toggle, the rip should start in 5-10 seconds.

I will try A1 today on an S5100 and let you know how it works for me.
 
Hello,

thanks for your quick answer but I don't know, what has happened.
I used the "Sony sleep-server" method: player power ON - connect USB - tray opens auto - place SACD -
player power OFF - tray closes auto - display flashes OFF - execute rip while my BDP-S490 sleeps.
USB root: AutoScript - sacd_extract_160 - Autoscript.TSS (I hope this is A1)
Now, connecting the USB drive the tray doesn't open. The player remains player, instead of being server.
I made some cycles and factory reset. I "feel" something (autorip.sh) redirected sacd data from network to usb drive.
I am very angry with me, I began today morning with a successful controll rip and after that I changed the content of the USB drive.
BTW, some days ago, when I ripped 30 sacd in line, I had to repeat the whole starting process about 3-4 times. I'm sorry for my bad English, I am an old musicophil from Hungary.
I will try everything.

Thanks, Andras
 

MikeyFresh

Moderator
Staff member
Hello,

thanks for your quick answer but I don't know, what has happened.
I used the "Sony sleep-server" method: player power ON - connect USB - tray opens auto - place SACD -
player power OFF - tray closes auto - display flashes OFF - execute rip while my BDP-S490 sleeps.
USB root: AutoScript - sacd_extract_160 - Autoscript.TSS (I hope this is A1)
Now, connecting the USB drive the tray doesn't open. The player remains player, instead of being server.
I made some cycles and factory reset. I "feel" something (autorip.sh) redirected sacd data from network to usb drive.
I am very angry with me, I began today morning with a successful controll rip and after that I changed the content of the USB drive.
BTW, some days ago, when I ripped 30 sacd in line, I had to repeat the whole starting process about 3-4 times. I'm sorry for my bad English, I am an old musicophil from Hungary.
I will try everything.

Thanks, Andras
Andras,

No big problem with your English, it is much better than my Hungarian! But we do need to clarify some things here and maybe a bit of advice on how best to test and use more than one script is in order.

First, I can't tell from your description if you are continuing to try AutoRip A1, or if you are just trying to resume with the original AutoScript using the sleep-server method?

If it is the latter, I would suggest a re-write of the original AutoScript folder using the download link on page 2 of this thread. However, the best practice for trying different scripts is not to keep writing and rewriting over and over again. You are best off using more than one thumb drive and labeling them to keep things clear and easy. Not everyone is crazy like me, but this is how I keep it straight:

Scripts.jpg

Second, if you have gone into the contents of these scripts using Notepad++ for any reason, it is very possible if not probable that an errant keystroke broke the script. Rather than go nuts just trying to figure out if that even happened, just erase the thumb drive(s) and rewrite a fresh script, paying attention that there is always an outer enclosing folder called AutoScript in every case.

I will test A1 shortly, but I have already tested A2 and A3 on the S7200 and after a full power cycle, returning to the original script and the sleep-server method has not presented any problem.
 

MikeyFresh

Moderator
Staff member
I've just successfully started an AutoRip using A1 on an S5100. The only appreciable difference between using A1 on the S5100 and A2 on the S7200 was the amount of the time it took for the script to actually run, it only took about 5-6 seconds for the S7200 to begin ripping, evidenced by the thumb drive's LED indicator flashing which means the ISO is being written.

With the A1 script on the S5100, it took probably double that time, I'd say about 10 seconds, so long that I thought it didn't work. But in the end the thumb drive LED began flashing, and so that AutoRip is now in progress.

When it finishes, I will power cycle the S5100, redeploy the original sleep-server AutoScript, and then attempt a rip using the GUI and the original method.
 

MikeyFresh

Moderator
Staff member
Dear MikeyFresh,

Many many thanks for you repeting the whole process to my stupid head. I have forgot the enclosing folder at the later experiments.
Now it is working again!

Thanks, Andras
I thought that might be it. ;)

I just removed the thumb drive with a completed A1 AutoRip ISO out of my S5100, then power cycled it, and placed the original sleep-server AutoScript back into that machine.

After launching SACDExtractGUI on my Linux Mint box, I am now ripping an SACD the old-fashioned way (actually, the old-fashioned way uses a Playstation 3, but we won't go there).

Glad you are up and running again on your S490!
 
I have a Sony BDP-BX510 and I cannot get the ISO2DSD to connect. I always get the following error... libsacdread: Can't open 192.168.10.104:2002 for reading. I tried the command line too and got the same error message. The Unit opens the tray like it is supposed to so the script appears to be functioning properly and the disk does not start playing once put into the drive. Any tips on what to check?
 
Windows or Mac?
Windows 10 64 bit.
I tried the various hints at when to load the cd and pulling out the USB stick.
Still get the same error. is there a specific Firmware version that works best on these machines.

It's on the latest one.

M15.R.0257

I also disabled the firewall on Windows with no change
 

MikeyFresh

Moderator
Staff member
Windows 10 64 bit.
I tried the various hints at when to load the cd and pulling out the USB stick.
Still get the same error. is there a specific Firmware version that works best on these machines.

It's on the latest one.

M15.R.0257

I also disabled the firewall on Windows with no change
All firmware versions work.

Your USB thumb drive should look exactly like this, does it?

AutoScript-Win10.jpg
 
Hello Mikey,

As I wrote, after ripping many SACDs I had two problems. One of them is resolved because ISO2DSD accepts special characters. The SACDExtractGUI hasn't been able to do these yesterday, even with UTF-8 supplement.
The other: with regard to long title and track names, I assumed that DSF ripping has only track issue. I evaded the problem. In both ripping app, I have tried ISO ripping today. Successful on all three problematic disks.
The ISO ripping time is not very low: for example 4.5GB at avg. 3MB/sec > 25 minutes.
The ISO rip file is converted by foobar2000 in 7-12 minutes to 44.1 kHz 24-bit stereo and 5-channel surround FLAC(5) format.

Andras
 

MikeyFresh

Moderator
Staff member
The other: with regard to long title and track names, I assumed that DSF ripping has only track issue. I evaded the problem. In both ripping app, I have tried ISO ripping today. Successful on all three problematic disks.
This is very interesting in that others reporting this file length issue (or special characters for that matter) had been asked to try ripping to ISO as a solution, and they reported that it did not work for them which always puzzled me. That made no sense.

I had also thought ripping to DFF should work around those issues as well, because DFF does not support any meta data whatsoever.

The SACDExtractGUI hasn't been able to do these yesterday, even with UTF-8 supplement.
Did you recompile sacd_extract 3.9, or only try by using the updated GUI?

The developer had stated the problem lies in both the GUI and also in the actual .exe, so that executable needs to be recompiled in addition to using the updated GUI. Then it should (hopefully) work.
 
Top