Sony Blu-Ray Players used for SACD ripping

QuadraphonicQuad

Help Support QuadraphonicQuad:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
So a further update. Reset the bluray to factory settings, then changed the options as above. Used a fresh USB stick and unzipped a new download of the Extracter. Rebooted the PC, power cycled the blu-ray player and attached it using a different network cable. Followed the steps to the letter, using a different SACD and the same warning appeared.

I'm pretty obstinate when it comes to stuff like this, I'll keep trying until works. In this instance however, I think I'm beat.

Hmmm. I'm a bit perplexed myself looking through your posts. May I suggest something outside the box? Perhaps your SACDExtractGUI program is not compatible with the version of the sacd_extract_160 file that you have. Try downloading the original Sonore SACD Extract that looks like this one on my computer:

program.png


Here is a link to the Sonore site where you can download it:
http://www.sonore.us/iso2dsd.html
Then try the whole ripping process and see if that gets you over the hump. This older version isn't as sophisticated as SACDExtractGUI...for example you can't ping...but I've never had a problem using it.
 
Via a router. IP address is 192.168.0.24 on the SACD extractor its 192.168.0.24:0202 I get a ping back okay - when I start to run it I get host unreachable. Checked my firewall nothing obviously or immediately wrong so I think I'll change the IP address on the player to something else and see if that makes any difference,
Quick question, is the ip address/port number you're using exactly as you noted above, or is there a typo? I believe the port number should be 2002, not 0202.

Sent from my K5000 using Tapatalk
 
That's a typo due to my Homer Simpsonesque fingers. Downloaded Fing to check the open ports on the device's IP address and it comes back as 50002. Changed the IP address accordingly to 192.168.0.24:50002 and the ping and test comes back as reachable when the player is on. When it does the whole sleep mode thing the ping works, but the test generates an "unreachable" error. In the off chance I tried 2002 as well. Same thing.

Changing the SACD output from 2CH to Multi-channel (or vice versa) didn't make a poke of difference. Nor did trying this with the player on.

So I have to conclude something is causing the port on the device to close when the player goes to sleep. Fing confirms this - as soon as the player goes to sleep the open port disappears.

I'm going to take a break from trying this. I've (it feels like) spent the whole weekend trying this, and I'm at the point where the player is going to get a hammer through it.
 
That's a typo due to my Homer Simpsonesque fingers. Downloaded Fing to check the open ports on the device's IP address and it comes back as 50002. Changed the IP address accordingly to 192.168.0.24:50002 and the ping and test comes back as reachable when the player is on. When it does the whole sleep mode thing the ping works, but the test generates an "unreachable" error. In the off chance I tried 2002 as well. Same thing.

Changing the SACD output from 2CH to Multi-channel (or vice versa) didn't make a poke of difference. Nor did trying this with the player on.

So I have to conclude something is causing the port on the device to close when the player goes to sleep. Fing confirms this - as soon as the player goes to sleep the open port disappears.

I'm going to take a break from trying this. I've (it feels like) spent the whole weekend trying this, and I'm at the point where the player is going to get a hammer through it.

I WOULD FEEL THE SAME AS YOU WITH WHAT YOU ARE EXPERIENCING !!

As I am at a loss as to why this is occurring, can I recommend connecting with Mickey Fresh over at HifiHaven, as he was brilliant in sorting out my initial problems. Fresh pair of eyes and all that.
https://hifihaven.org/index.php?threads/rip-sacd-with-a-blu-ray-player.3652/He really is a top bloke and will try to solve your problem.

Strange that it seems that it is the actual player which maybe the cause of the problem....I haven't read about this before.
I too downloaded a program to check on the port status as it kept on stating cannot open the bloomin port, on mine!!

You are not alone, I walked away from mine for a couple of weeks when I first started, as I was getting nowhere fast..turned out it was the Autoscript file not being in a folder..grr
Sorry I can't be of any more help at this stage.
But I will keep researching and scratching my head to see if there are any other possible answers.
Please keep posting with any other thoughts or trials you have or are experiencing.

Where are you based within the world time zones? Can provide prompt replies if that's doable?
 
Last edited:
I have found this post on the HIFI Haven thread: Post 554
https://hifihaven.org/index.php?threads/rip-sacd-with-a-blu-ray-player.3652/page-28
Different Sony player but looks like the same problem that Sixtyten is experiencing.

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?

That's a typo due to my Homer Simpsonesque fingers. Downloaded Fing to check the open ports on the device's IP address and it comes back as 50002. Changed the IP address accordingly to 192.168.0.24:50002 and the ping and test comes back as reachable when the player is on. When it does the whole sleep mode thing the ping works, but the test generates an "unreachable" error. In the off chance I tried 2002 as well. Same thing.

Changing the SACD output from 2CH to Multi-channel (or vice versa) didn't make a poke of difference. Nor did trying this with the player on.

So I have to conclude something is causing the port on the device to close when the player goes to sleep. Fing confirms this - as soon as the player goes to sleep the open port disappears.

I'm going to take a break from trying this. I've (it feels like) spent the whole weekend trying this, and I'm at the point where the player is going to get a hammer through it.

This is the update from the poster but it shows you are not alone....deff worth contacting the main man over on this site

I did get it working and yes my Folder did look like that.
I am not sure what caused it but I did have to go the route of

1) unplugging the power cable and plugging it back in
2) putting the USB stick in the front port ( tray opens)
3) inserting the disk and push the open/close button
4) and then pushing the power off button to put it in sleep mode
5) click the Execute button in ISO2DSD

I then had to work out switching out for another disk.

6) after first disk is done, push the open button and take out the disc
7) put the next disk in and push the open/close button
8) then push the power off button again
9) click the Execute button in ISO2DSD

I was able to rip 4 discs and it creates a nice folder with the Album name and each track
as it's own file
Now I just need to figure out how play back the files

Hope that helps
 
Just found this post over at HIFIHAVEN :
I know there’s been some “concern” over whether or not Sony might release a firmware update which might disable this functionality. I had to install a system update to get my player to connect to the network (and therefore run ISO2DSD successfully). I can confirm that as of Thursday 5/16/2019, the Sony system update does NOT kill the ripping functionality for the S390.

I wonder by installing the latest update on the Sony S4100 if that will permit this ripping process to work?
That's what I did on mine.
 
Just found this post over at HIFIHAVEN :
I know there’s been some “concern” over whether or not Sony might release a firmware update which might disable this functionality. I had to install a system update to get my player to connect to the network (and therefore run ISO2DSD successfully). I can confirm that as of Thursday 5/16/2019, the Sony system update does NOT kill the ripping functionality for the S390.

I wonder by installing the latest update on the Sony S4100 if that will permit this ripping process to work?
That's what I did on mine.

I guess I'm still a little confused, help me out here please. It looks like from Sixtyten's screen shot on post #129 that he's running the newer program, the ISO2DSD (older program) keeps getting mentioned. So what's up with that?
 
I guess I'm still a little confused, help me out here please. It looks like from Sixtyten's screen shot on post #129 that he's running the newer program, the ISO2DSD (older program) keeps getting mentioned. So what's up with that?
The ISO2DSD is this:
Converts ISO files to DSD
http://www.sonore.us/iso2dsd.html
Which is not what Sixtyten is using

I'm just usin that as an example to give peace of mind that this problem has been experienced by others trying to initiate the rip process.
 
and another post :
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 know its ISO2DSD but to me the finger is pointing at a network error.

EXCUSE ME WHILE I WATCH THE LAST EVER GAME OF THRONES...
 
Back
Top