Rip SACD with a Blu-ray player

thank you all verry mutch for your very quick answers

the IP should be fine
it is listed in the rooter and I get answer on ping request

yes I am using win xp I also tested on a win 7 system
Linux would be possible also when it helps

Quick Start mode in the S790's system menu is enabled

here is my AutoScript directory:

Verzeichnis von e:\AutoScript

31.10.2019 15:38 <DIR> .
31.10.2019 15:38 <DIR> ..
23.02.2019 21:02 207 AutoScript
23.02.2019 21:03 207 AutoScript.TSS
20.02.2019 22:11 350.830 sacd_extract_6200
3 Datei(en) 351.244 Bytes
2 Verzeichnis(se), 749.551.616 Bytes frei

otto
 

MikeyFresh

Moderator
Staff member
thank you all verry mutch for your very quick answers

the IP should be fine
it is listed in the rooter and I get answer on ping request

yes I am using win xp I also tested on a win 7 system
Linux would be possible also when it helps

Quick Start mode in the S790's system menu is enabled

here is my AutoScript directory:

Verzeichnis von e:\AutoScript

31.10.2019 15:38 <DIR> .
31.10.2019 15:38 <DIR> ..
23.02.2019 21:02 207 AutoScript
23.02.2019 21:03 207 AutoScript.TSS
20.02.2019 22:11 350.830 sacd_extract_6200
3 Datei(en) 351.244 Bytes
2 Verzeichnis(se), 749.551.616 Bytes frei

otto
OK, that should be good, however I can't really say for sure like I would with an actual screenshot.

Is there a reason why you must use the CLI?

While it absolutely should work, many people on other forums had endless problems trying it that way, it's the whole reason why the method detailed here is using a GUI instead, 9.9 out of 10 people prefer it to the CLI. Again, either one should work, but for easier troubleshooting here, use of the GUI removes one variable.

Windows XP may be a real problem. I do not recall anyone ever using it here, though that doesn't mean it won't work, however if I were you I would stick to the Windows 7 machine, just do a complete power cycle of the S790 with the flash drive removed, and then try again with Win7.

Is it safe to say this is the x64 Professional Edition of Windows XP (or for that matter hopefully you have a 64-bit version of Windows 7)?

I ask because I know for certain a 64-bit OS is needed when using the GUI, I'm not sure if that is a requirement when using the CLI, but it wouldn't surprise me at all if it were. If your Windows installs are all 32-bit, then what about your Linux machine, is it running a 64-bit OS? If so please try it.

It has been about 3.5 years since I've run any rips using the CLI, much too long ago for me to remember every detail of what the required set-up steps were. Once it became clear that Sonore's ISO2DSD was compatible with the Blu-ray player ripping method, I never used the CLI ever again.

More recently, I've never used the CLI with sacd_extract 3.9, however I note you are not actually trying to use 3.9 here. The CLI examples published with 3.9 don't look exactly like the commands you are using. For instance to create an ISO the Linux Terminal command example published with 3.9 looks like this:
Code:
$ sacd_extract -I -i192.168.166.168:2002
Thats probably just a Linux Terminal vs. Windows Console thing however.
 
Hello MikeyFresh

I now tested on a new clean machine
with win 7 professional 64-bit


And now ….. it works !

you have make me so happy !!!
I am not sure what I really tested on witch system after 3 days testing
but now it works :-))))
I double-checked
and I can tell win-xp 32 bit don't works !

Thank you very very much and have a good time
kind regards

otto
 
Thanks Sal and welcome aboard!

You might also give SACDExtractGUI a try now that you have the process up and running, it is a superior program in a number of ways.
So like I said I was curious about the speed deference so I grabbed my copy of Elton John - Tumbleweed Connection 5.1 Channel SACD.
First I ran ISO2DSD PCv7, it took 29:05 to complete the 7.11 GB, 12 track 5.1 multich folder.
Then I ran SACDExtract 0.3.9, it took 22 minutes flat to complete the same 7.11 GB folder.
Not quite the speed increase you projected but substantial none the less.
Thanks again Mikey and everyone for all you've put into these projects, truly awesome software.
 

MikeyFresh

Moderator
Staff member
Hello MikeyFresh

I now tested on a new clean machine
with win 7 professional 64-bit

And now ….. it works !
Otto!
Thats outstanding, you got it resolved before the weekend was over, way to stay at it!

you have make me so happy !!!
I am not sure what I really tested on witch system after 3 days testing
but now it works :-))))
I double-checked
and I can tell win-xp 32 bit don't works !
My pleasure, and that's valuable feedback for anyone here wishing to use the CLI, apparently just as when using the GUI, a 64-bit OS is required.

Thank you very very much and have a good time
kind regards

otto
Once again my pleasure and welcome to HFH. If you'd like to try the state-of-the-art, use the link on Page 1 of this thread to download SACDExtractGUI, in that download package you will find sacd_extract 3.9 though it isn't labeled that way, however that's what it is. You will find it faster for DSF extraction, especially the multichannel content which is up to 4x faster when extracting from an ISO. There is a "read me" document in that package that details the additional commands that are available only in 3.9, for instance the Padding-less DSF option, or Concurrent Mode (ISO+DSF in one pass of the optical media), or your choice of a specific Output Directory.
 

MikeyFresh

Moderator
Staff member
So like I said I was curious about the speed deference so I grabbed my copy of Elton John - Tumbleweed Connection 5.1 Channel SACD.
First I ran ISO2DSD PCv7, it took 29:05 to complete the 7.11 GB, 12 track 5.1 multich folder.
Then I ran SACDExtract 0.3.9, it took 22 minutes flat to complete the same 7.11 GB folder.
Not quite the speed increase you projected but substantial none the less.
Thanks again Mikey and everyone for all you've put into these projects, truly awesome software.
Great stuff, that's interesting about the speed difference. I think there are two things at play there, one is just some discs do rip faster than others, it has to do with the total play time. Believe it or not the shorter run time discs actually never achieve peak speed, that is only reached with the longer play time discs where the laser is reading out to the very edge of the media, and the rotation speed of the disc is increased as a result.

That however isn't a total rip time thing, that's just MB/sec, the longer discs will reach a higher MB/sec speed towards the very end of the rip, however because they are longer of course the total rip time increases as well as a result, but the MB/sec is faster the longer the disc's play time.

The second thing at play there is whether or not you are extracting from an ISO. Apparently that 4x speed boost is only really applicable to extracting DSF from a previously created ISO, because in that scenario you don't have the limiting factor of the optical drive as a bottleneck. So if the DSF you extracted was from the SACD itself, the Blu-ray player's optical drive is the ultimate speed limitation there. If however you first create an ISO, and then extract the DSF from it, the sky is the limit on that extraction speed, I managed to hit 55MB/sec extracting from an ISO I created from the Axis Bold As Love SACD reissue (although that's a stereo/mono disc with no DST compression).

I think in the end it's 6 of 1, half a dozen of the other in that the initial ISO creation also of course takes time, so what you gain on extraction, you already lost upfront on the ISO creation. The reason people do it that way is to retain a full archival backup of the SACD, which is what the ISO is (minus any Redbook content).
 
Great stuff, that's interesting about the speed difference.
Yep, great stuff, thanks for the info!
BTW, Like me, my computers no spring chicken either. LOL
I built it in late 2008 getting the closeout of the Q Yorkfield processors just after the i series were introduced. The quad core Q9550 was top of the line in it's day though, running at 4x2.83GHz, Gigabyte motherboard maxed out at 8 GB of Reaper memory. I have updated the optical drives to blu-ray and 1 TB of SS drive (2 more TB coming). Still a decent box but I will replace it with something totally silent after the MB or processor finally lets the smoke out. LOL
 
Last edited:
A bit of an update on ripping experiences, in case it's helpful/useful to anyone. Some time ago (post 927, early August), I reported that ripping using the Autorip A1 variant on Sony BDP S390's had been successful for me on multiple SACDs. However, there was one disc that simply failed to rip using Autorip, on my two different S390's -- but did, however, rip using SACDExtractGUI.

I'm now reporting more of the same: since August, I've continued to gradually acquire SACDs, and have continued to successfully use the Autorip A1 variant on a Sony BDP S390 to rip them. I am able to expand my library with SACDs only because of being able to rip them, which is thanks to this thread -- at this point, I would never acquire discs if I had to actually physically shuffle them in and out of a player to listen to them. Ripping the SACDs with Autorip has been a very convenient process -- for me, it's actually the easiest ripping process as compared with CDs, DVD-A's, or Blu-Rays.

However, yesterday I did run into a disc again that simply would not rip using Autorip, on either of my S390's -- but again, it did rip using SACDExtractGUI. So, this is just to highlight the benefits of being able to use multiple ripping techniques as needed (all thanks to @MikeyFresh and others on this thread!). And also, just a heads-up to anyone else using the Autorip A1 variant on a Sony BDP S390.
 
Finally joined after watching this thread for a long time. Firstly a huge THANK YOU Mikey et. al. for the thread and especially the software that has been liberating my SACD collection.

Like otinkyad, I've been using a couple of Sony S390's, mostly using the GUI across WiFi, but recently also with Autorip A1. And like otinkyad I've found a few discs that don't work with Autorip, but rip fine with the GUI.

That's all from me, thanks again and happy ripping!
 
Salut chers audiophiles :patriot:,

Thank you MikeyFresh for that royal introduction, not sure I deserve it though :redface:.
Now lets get down to business, here are my latest compilations of setmind's great SACD ripping tools:

Code:
SACDExtractGUI v0.1-7-g135cbd5d

sacd_extract version 0.3.9@setmind-13-g58db5f16fcf410ae4d6aeca226a067b37ade136a

Linux x64 package: sacd_extract-LINUX-v0.3.9@setmind_git_2019-03-21.zip



macOS x64 package:
sacd_extract-MACOS-v0.3.9@setmind_git_2019-03-21.zip



Windows x64 package:
sacd_extract-WINDOWS-v0.3.9@setmind_git_2019-03-21.zip


Linux armhf package: sacd_extract-LINUX-armhf-RPi-v0.3.9@setmind_git_2018-10-08.zip
[works on Raspbian & should be useable on any other distro too]


View attachment 8975


Should the need for DSD audio players arise, please drop a note for what platform / operating system they might be required for.
I will publish the SW links in this thread though, to keep this one solely for ripping topics.

Happy ripping & USE THE TOOLS AT YOUR OWN RISK! :Deal

This is a question about an old post (#284, quoted above) from @Nexus3. Are the checksums for the MacOS version correct? I ask because I don't get those. (I do get the checksums shown above for the Windows version.

Any information would be much appreciated, as I would like to start using SACDExtractGUI on Mac, but don't want to install if I don't get the same checksums as shown by the creator. Thanks in advance!
 

MikeyFresh

Moderator
Staff member
This is a question about an old post (#284, quoted above) from @Nexus3. Are the checksums for the MacOS version correct?
Thats a good question, the post itself dates to Nov. 2018 when SACDExtractGUI was first available, however Nexus3 did recompile from Mindset's latest updated sources in late March, which was announced in Post #623. Those recompiles were then linked to in the original post #284 you mentioned, so those files are not as old as the post itself.

I guess it's possible that he forgot to revise/update the checksums listed in the original post for the macOS version, and no one noticed. All I can say is I have downloaded and used that package and countless others have too with no issues.

You can also compile sacd_extract v3.9 yourself from sources, I have a build script if you care to use it, should still work but no guarantees there.

I wish I could help more but for whatever reason my Hash Calculator app doesn't want to calculate for the entire folder, just the individual pieces inside of it. I don't know why that is.
 

MikeyFresh

Moderator
Staff member
This is a question about an old post (#284, quoted above) from @Nexus3. Are the checksums for the MacOS version correct? I ask because I don't get those. (I do get the checksums shown above for the Windows version.

Any information would be much appreciated, as I would like to start using SACDExtractGUI on Mac, but don't want to install if I don't get the same checksums as shown by the creator. Thanks in advance!

On second look, I do get the checksums to match perfectly if I don't let the unzip occur, in other words those checksums are for the zipped folder, and they do match using Hash Calculator on my MacBook Air.

Safari for whatever reason wants to just auto-unzip the folder, however if I download it using Chrome it stays zipped, and the checksums do match when leaving that folder zipped:

17815
 

MikeyFresh

Moderator
Staff member
Finally joined after watching this thread for a long time. Firstly a huge THANK YOU Mikey et. al. for the thread and especially the software that has been liberating my SACD collection.

Like otinkyad, I've been using a couple of Sony S390's, mostly using the GUI across WiFi, but recently also with Autorip A1. And like otinkyad I've found a few discs that don't work with Autorip, but rip fine with the GUI.

That's all from me, thanks again and happy ripping!
Good evening and we're glad you joined, congrats on your S390 set-up, welcome aboard.

Is there anything in particular you noticed about those SACDs that failed using AutoRip? For instance, was the disc authored using any special characters, or perhaps there are very long file path names caused by excessive character length in the disc title and artist/conductor/orchestra combination?
 
Hello @MikeyFresh -- thanks so much for your extremely fast and helpful replies! Spurred by your finding that you do get the correct checksums, I looked into this some more. I'm *very* sorry to report that I was calculating the checksums incorrectly (I wasn't using the correct flags on the MacOS command line) -- and now that I'm doing it right, I do get the same checksums as reported by @Nexus3.

Terribly sorry for wasting your time -- thanks so much again for the help!
 
Good evening and we're glad you joined, congrats on your S390 set-up, welcome aboard.

Is there anything in particular you noticed about those SACDs that failed using AutoRip? For instance, was the disc authored using any special characters, or perhaps there are very long file path names caused by excessive character length in the disc title and artist/conductor/orchestra combination?
BTW, I've now had four albums in a row that wouldn't rip with AutoRip A1 variant. To make sure I wasn't forgetting a step in the procedure, I went back to a disc that had ripped in the past -- and that still rips just fine. I can try looking more systematically at the discs that have not worked with Autorip (6 albums in total, comprising perhaps 10 discs), and report back.

It's this string of Autorip failures, as a matter of fact, that has me trying to set up SACDExtractGUI on MacOS, which would for me be more convenient than using on Windows as it presently is.
 
Hello @MikeyFresh -- thanks so much for your extremely fast and helpful replies! Spurred by your finding that you do get the correct checksums, I looked into this some more. I'm *very* sorry to report that I was calculating the checksums incorrectly (I wasn't using the correct flags on the MacOS command line) -- and now that I'm doing it right, I do get the same checksums as reported by @Nexus3.

Terribly sorry for wasting your time -- thanks so much again for the help!
And... SACDExtractGUI is now running for me on MacOS -- thanks and apologies again!
 

MikeyFresh

Moderator
Staff member
BTW, I've now had four albums in a row that wouldn't rip with AutoRip A1 variant. To make sure I wasn't forgetting a step in the procedure, I went back to a disc that had ripped in the past -- and that still rips just fine. I can try looking more systematically at the discs that have not worked with Autorip (6 albums in total, comprising perhaps 10 discs), and report back.

It's this string of Autorip failures, as a matter of fact, that has me trying to set up SACDExtractGUI on MacOS, which would for me be more convenient than using on Windows as it presently is.
Yes that would be interesting to see why some discs fail with AutoRip, anything you note there is of interest. Also interesting then if you get the exact same results using the GUI with macOS vs. Windows.
 
....Is there anything in particular you noticed about those SACDs that failed using AutoRip? For instance, was the disc authored using any special characters, or perhaps there are very long file path names caused by excessive character length in the disc title and artist/conductor/orchestra combination?
Nope, but it has only happened a couple times. In one case it was one volume of a set of Handel piano concertos, but another volume AutoRip'd fine. Both spelled Händel with an ä and both had basically the same character length. AutoRip failed at least 6 times before I gave up. Confirmed the other disc AutoRip'd more than once.
 
Last edited:
Hey Mikey. Thanks for all your work here. Unfortunately I can not get my Sony BDPS590 to work. It does not see to want to read the AutoScript. I bought it off eBay and am worried about the firmware. In any event here is the screen shot of everything I have done so far.

Any help would be much appreciated. Thanks

17845
 
SACDExtract
Hey Mikey. Thanks for all your work here. Unfortunately I can not get my Sony BDPS590 to work. It does not see to want to read the AutoScript. I bought it off eBay and am worried about the firmware. In any event here is the screen shot of everything I have done so far.

Any help would be much appreciated. Thanks

View attachment 17844
I'm not Mikey but I believe your issue is using the AutoScript code. Your 590 uses the standard iso2dsd or SACDExtract coding.
 
Top