Hello again, Your instructions worked like a dream for 2 of my 3 SACDs, unfortunately the third seems to be resistant to ripping. It is a TUDOR label disc made in switzerland of Italian Concertos and arias for Trumpet and Soprano - Gabor Tarkovi Trumpet soloist. The Case & Disc both have the SACD logo on them. I've tried & tried but after a few seconds the disc tray opens & stays open. If there are resistant Discs it might be worth adding this one to the list. I have tried cleaning it carefully but still no joy.

Very likely that's the old issue of how the disc metadata was authored. Unfortunately there is no easy solution to that one.

In short, the character limit is exceeded causing an error.

I bet that disc has a very lengthy combination of composer, artist/conductor, work title, and track title?
 
Hello -- A tremendous thank you to @MikeyFresh for starting (and maintaining!) this thread, and thanks also to the many other posters who have shared tips here! Thanks to all of you, I've been able to successfully extract multichannel from Elton John's Captain Fantastic SACD, and to play it via Roon. I used a Sony BDP S390 (purchased used specifically on the basis of information in this thread), together with a Windows 10 laptop running ISO2DSD. Roon playback is from the same laptop.

I do have a couple of questions, as I am very new to SACD and ISO formats.

When I ripped the multichannel from SACD to ISO, I used the "Multichannel" channel option and "Raw ISO output" option in ISO2DSD. Then, after the ISO had been created, I pointed ISO2DSD to the just-created ISO file (with "Multichannel" selected again) to extract .dsf tracks. My question is: to extract the *stereo* High-Res version that is also on the SACD, can I just point ISO2DSD to the *same* ISO file that I already created, and select the "Dual" channel option? Or do I first need to rip the SACD to a new ISO file using ISO2DSD with the "Dual" channel option selected? (Or, just rip directly from the SACD to stereo .dsf files, as per the use case discussed by MikeyFresh when starting this thread?)

A related question (or just another way of asking the same question) is: When ripping an ISO file from SACD using ISO2DSD and the methods discussed in this thread, will the ISO *always* contain the entire contents of the SACD? Or will the contents of the ISO depend on whether "Dual" or "Multichannel" was selected in ISO2DSD when ripping?

Finally, to extract the CD audio that is also supposedly on the SACD, should I aim to just put it into my CD player and rip as I would any ordinary CD..? (Haven't tried this yet -- just wanted to be aware of any caveats regarding this).

Thanks in advance for any information!
 
Last edited:
W
Hello -- A tremendous thank you to @MikeyFresh for starting (and maintaining!) this thread, and thanks also to the many other posters who have shared tips here!

Welcome aboard, it's our pleasure.

My question is: to extract the *stereo* High-Res version that is also on the SACD, can I just point ISO2DSD to the *same* ISO file that I already created, and select the "Dual" channel option? Or do I first need to rip the SACD to a new ISO file...

Yes, just point to that very same ISO, and select the Dual channel option for extracting the stereo tracks.

When ripping an ISO file from SACD using ISO2DSD and the methods discussed in this thread, will the ISO *always* contain the entire contents of the SACD? Or will the contents of the ISO depend on whether "Dual" or "Multichannel" was selected in ISO2DSD when ripping?

The former, an ISO is a complete backup copy of the disc in it's entirety, if that disc has both stereo and multichannel content, then both will present in the ripped ISO. Admittedly the software GUI could be a little more clear in that regard if when selecting the Raw ISO output mode option, the channel mode were to be greyed out and not even offered as an option to toggle, that would be logical and provide the end user with a clue as to how it actually works. The software is imperfect in that regard, it doesn't make any difference if you select Dual or Multi in the channel mode when ripping an ISO, that always results in the full SACD content being ripped.

Finally, to extract the CD audio that is also supposedly on the SACD, should I aim to just put it into my CD player and rip as I would any ordinary CD..?

Yes the Redbook CD content on Hybrid SACDs should be ripped using standard methods with a computer CD-ROM drive just as you would any ordinary CD, with various software choices including iTunes, dBPoweramp, XLD, JRiver, Foobar, etc...
 
I used a Sony BDP S390 (purchased used specifically on the basis of information in this thread), together with a Windows 10 laptop running ISO2DSD.

ISO2DSD is a great program that has served us well for years now, however I strongly urge you to upgrade to the state-of-the-art program called SACDExtractGUI, also linked to in the EDIT section of the OP of this thread.

SACDExtractGUI has been out since last fall, it contains sacd_extract v3.9 which offers various improvements to the 3.7 version that's in the now aging Sonore package. Specifically, v3.9 is faster, especially when extracting multichannel tracks from an ISO where it achieves up to a 4x speed increase over the v3.7 found in ISO2DSD.

The newer GUI is also superior to that of ISO2DSD, offering various new functions including the ability to designate output directories, a concurrent mode where both an ISO and DSF are created simultaneously with just one pass of the disc, and Padding-less DSF which minimizes the possibility of small clicks or pops marring the inter-track transitions, which is especially destructive to gapless albums.
 
Wahoo!
It's working! I received a Sony BX 59 today and got everything beaten into submission and ripped my first SACD.
I first tried to use a crossover cable and will have to try that again because I discovered that I was entering an incorrect IP address.
But I am too exhaused to try that again. As Scarlett pointed out, "tomorrow is another day."
Thank you all for this great thread.
 
Wahoo!
It's working! I received a Sony BX 59 today and got everything beaten into submission and ripped my first SACD.
I first tried to use a crossover cable and will have to try that again because I discovered that I was entering an incorrect IP address.
But I am too exhaused to try that again. As Scarlett pointed out, "tomorrow is another day."
Thank you all for this great thread.

Great news Gene, glad you found yourself a nice condition BX59 and got the process down without much trouble.

Upgrade to SACDExtractGUI, it is better in a number of ways than ISO2DSD, faster and more capable, the state-of-the-art as of fall 2018.
 
Great news Gene, glad you found yourself a nice condition BX59 and got the process down without much trouble.

Upgrade to SACDExtractGUI, it is better in a number of ways than ISO2DSD, faster and more capable, the state-of-the-art as of fall 2018.
downloaded
 
Last edited:
Great news Gene, glad you found yourself a nice condition BX59 and got the process down without much trouble.

Upgrade to SACDExtractGUI, it is better in a number of ways than ISO2DSD, faster and more capable, the state-of-the-art as of fall 2018.

Any chance of an idiot's guide to getting SACDExtractGUI to work on Windows 10. I've downloaded, unzipped to a folder and everytime I double click on the exe file I don't get anything.
 
Any chance of an idiot's guide to getting SACDExtractGUI to work on Windows 10. I've downloaded, unzipped to a folder and everytime I double click on the exe file I don't get anything.

No guide necessary, don't double-click the .exe, instead to launch the program you are double-clicking the .jar file.

Specify the path to sacd_extract using the Browse button, and enter your player's IP address.

Make sure any previously running instance of ISO2DSD has been fully killed, and it doesn't hurt to power cycle the player in that regard, noting any potential change to the assigned IP.
 
No guide necessary, don't double-click the .exe, instead to launch the program you are double-clicking the .jar file.

Specify the path to sacd_extract using the Browse button, and enter your player's IP address.

Make sure any previously running instance of ISO2DSD has been fully killed, and it doesn't hurt to power cycle the player in that regard, noting any potential change to the assigned IP.

I've done that but I get the message to look for an app in the app store to open the .jar file.
 
I've done that but I get the message to look for an app in the app store to open the .jar file.

OK, I don't get that behavior in Windows, neither Windows 10 nor my older now retired Windows 7 machine did that, but another member very recently described the exact same thing you are.

He was able to launch it by right-clicking the .jar and selecting Open.

This all actually has nothing to do with SACDExtractGUI per se, it is a Windows/Java thing and does not affect everyone. The .jar file in the SACDExtractGUI package is an executable, meaning it should launch when double-clicked. But for some reason on some Windows systems it doesn't, however the right-click and Open command should then work.

You can Google it for more information, it's the weird wild whacky world of Windows thats doing this, rather than anything being specifically wrong with the SACDExtractGUI program.
 
OK, I don't get that behavior in Windows, neither Windows 10 nor my older now retired Windows 7 machine did that, but another member very recently described the exact same thing you are.

He was able to launch it by right-clicking the .jar and selecting Open.

This all actually has nothing to do with SACDExtractGUI per se, it is a Windows/Java thing and does not affect everyone. The .jar file in the SACDExtractGUI package is an executable, meaning it should launch when double-clicked. But for some reason on some Windows systems it doesn't, however the right-click and Open command should then work.

You can Google it for more information, it's the weird wild whacky world of Windows thats doing this, rather than anything being specifically wrong with the SACDExtractGUI program.

OK, I found that the association app with the .jar file was one I'd removed off the system. I've updated Java to version 1.8. In trying to associate I've found the Java installation in Program Files (x86) and gone open with java.exe. That flashes a cmd box then disappears. Does anyone know which .exe file I should use in the bin folder as there are a number? I think I'm nearly there.
 
In my win10 in Program Files (x86)\Java\jre1.8.0_211\bin\javaw.exe is associated.
In file commander you can choose "Java(TM) Platform SE binary" as a .jar association.

Thanks, I've just tried this and still nothing. I'm missing something which is probably something obvious but I only wish I knew what it is.
 
I've updated Java to version 1.8.

You mean Java v8, right? The latest is version 8 u211.

I've seen references to folks who had to entirely uninstall Java, then install an older version (don't ask), then uninstall that older version and reinstall the latest version in order to solve this stupid Windows issue. Something about the registry remaining stubbornly broken until the above was done, which somehow fixed it.
 
You mean Java v8, right? The latest is version 8 u211.

I've seen references to folks who had to entirely uninstall Java, then install an older version (don't ask), then uninstall that older version and reinstall the latest version in order to solve this stupid Windows issue. Something about the registry remaining stubbornly broken until the above was done, which somehow fixed it.

Yes, I've got version 8 u211.
 
Hello all, and @MikeyFresh -- sorry for the delayed response -- was unable to get to this yesterday. Thanks so much for the information about ISO's -- that answered all my questions. Thanks also for the tip about SACDExtractGUI. I believe I did try it first, but ran into some problem (I don't remember what, as I tried numerous things that didn't work) and then tried ISO2DSD and that program started up right away (although successful ripping took longer -- see below). But I'll try again.

Let me provide a bit more information about my experience, in case it can help someone else. Before I achieved success with the ripping, I did run into innumerable "libsacdread: Unable to establish connection" errors. This was on both Mac OS (which was what I tried first) and Windows 10. Changing firewall settings didn't seem to help, and after maybe 20 attempts, all the while wondering what I was doing wrong, and constantly searching this thread for ideas, I was getting a bit disheartened. (For those of you who run into problems, may I say: Just keep trying -- you will get there!) Ultimately what did enable ripping was an idea from MikeyFresh's post #127 in this thread, which mentioned enabling network discovery in case of a libsacdread error. As far as I can tell, the procedure given there to enable network discovery no longer applies to Windows 10, but this link Configuring network discovery on Windows 10 did it for me. Then, ripping with ISO2DSD from my Windows 10 laptop worked, and after all the non-starts, it was quite a thrill to see it working!

I haven't gone back and tried on Mac OS, but I believe I would need to enable Sharing, which (I think) is the equivalent of network discovery. If I try that and it works, I'll report back.
 
Back
Top