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 enter sleep if you had already configured it.

Now I made the settings adjustments to the Sony player, but I did not disconnect and reconnect the power cord first, is that a MUST?

Also what is this about SLEEP mode, I made no settings adjustments for that and I don't know how to?

(BTW thanks for all of your patient and articulate replies to my discombobulated queries)
 
OK I'm home now, typing from my phone is cumbersome at best, and as well I didn't have my glasses with me, which makes just reading it a task.

What I should have said is port 2002 does need to be open, so if your landlord has it blocked, we are dead in the water until it is unblocked, though we could still do AutoRip. But let's hold off on that thought for now.

No a power cycle is not a requirement but it is considered good practice, especially since most people ignore the part about not doing repeated insertion and reinsertion of the flash drive. That solves nothing and actually creates its own set of problems, so if you have inserted the flash drive into the S590 more than once, please remove it and power down, then pull and replace the AC power cord.

If you had only inserted the flash drive once, then you should not be in need of a power cycle.

But going back to the port 2002, you'll get that very same error message unless the AutoScript has been read in, the tray opens, you place a disc in it, and then Power OFF to close the tray (this is sleep mode and you do NOT close the tray with the open/close button, instead you close it by powering OFF).

If you do the above, then the port test should succeed, and so should Running a rip. Please note the part in the instructions about watching the display flash OFF for a few seconds, until that is finished, the machine still isn't sleeping. Once the display stops flashing OFF, the S590 has snoozed, and you can successfully Test the port, and Run a rip.
 
...If you do the above, then the port test should succeed, and so should Running a rip. Please note the part in the instructions about watching the display flash OFF for a few seconds, until that is finished, the machine still isn't sleeping. Once it stops flashing OFF, you can successfully Test the port, and Run a rip.

I am ripping as I type! Yippee!

And here is a general question about SACD resolution and .dsf files and the various rates of DSD: double, quad, octuple. I don't understand all this tech stuff very well, but what is the rate of the DSD on any SACD: DSD2 or something higher? I assume that when SACD extract does the rip, it is the same rate as the source disc, which is standard... but what is that rate?

In the time it take to type the above paragraph I get the message:

Completed: 100% (77.0MB), Total: 100% (77.0MB) at 2.04MB/sec
We are done..
[DONE]


*** Now how do I remove the disc, and power off? And if I want to rip another disc, do I have to power off and then power on again, this time without inserting the thumb drive?

... And my resulting .dsf files from my first rip play fine on my JRiver Media Center, with my OPPO UDP 205 doing duty as the DAC (since my primary DAC, a Rega DAC-R, does not handle DSD files, only PCM).
 
I am ripping as I type! Yippee!

Outstanding, Bay City Ripper!

I assume that when SACD extract does the rip, it is the same rate as the source disc, which is standard... but what is that rate?

That would be single rate DSD or what is known as DSD64, and thats the only thing ever found on an SACD disc. So-called 2x (Double or DSD128) 4x (Quad or DSD256) and higher are only found in some DSD downloads, or by means of upsampling a lower resolution file, typically with HQPlayer or Roon. DSD64 refers to the SACD's 2.82 MHz sample rate, which is 64 times that of Redbook CD's 44.1 KHz.

Now how do I remove the disc, and power off? And if I want to rip another disc, do I have to power off and then power on again, this time without inserting the thumb drive?

To remove the disc just press Open to eject the tray. To rip another disc, just place a new one in the tray, and once again Power OFF to close it. Wait for the display to stop flashing OFF (player sleeps), then Run the next rip. You do not reinsert the flash drive for that.

The only hang up I've heard with regard to 4 or 5 consecutive rips appears isolated to the Windows version of the executable (i.e. I do not have this same problem on a Mac), however some users report that after about 4 or 5 consecutive rips the system stops working and requires a full power cycle using the AC plug.

We don't know why that happens on Windows but a good guess is there is something called a memory leak in that particular executable, which eventually exhausts the very limited onboard RAM in the Blu-ray player. On a Mac you can usually get 8-9 consecutive rips before needing the power cycle, so still likely a memory leak issue, but apparently less severe than with the Windows .exe.

It's nothing a power cycle won't fix, however always note after doing a power cycle whether or not the router has issued a new/different IP address to the player. If it did you need to make that alteration in the GUI.

After any power cycle you are back to square one and do need to reinsert the flash drive. Member @stereo hifi noted that a full reset can also be accomplished by pressing and holding down the power button on the machine for 10 seconds. That won't work with the power button on the remote however, only the one on the actual unit, and that could differ by specific model (he was using a BX59).
 
Thanks for all of that info, I will save that in case I run into the difficulties you describe with Windows. In the event I need to do a power cycle, I figured out that the easy way for me to do that will be to unplug the main AC plug of my power conditioner from the wall instead of trying to reach the Sony plug in the power conditioner which requires moving furniture to access.

I can't believe this is so straightforward, once I've got it all set up (thanks to your help). Now the next phase is to edit ID tags for all of those .dsf files, using the Tag&Rename program I purchased for that purpose (since my usual tag editor does not work with .dsf file types). Since I have already ripped and tagged the CD layer on all my SACD discs, it's just a matter of copy/pasting the info from dBpoweramp ID tag editor into Tag&Rename. ID tags are always the most laborious part of ripping discs.
 
Thanks for all of that info, I will save that in case I run into the difficulties you describe with Windows.

You can use the site's Bookmark function to get easy access to any post, it's the little icon directly left of the Post #, and you can label/name the bookmark something that will indicate it's significance.

In the event I need to do a power cycle, I figured out that the easy way for me to do that will be to unplug the main AC plug of my power conditioner from the wall instead of trying to reach the Sony plug in the power conditioner which requires moving furniture to access.

Or perhaps first give that press/hold down the Power button 10 seconds Reset thing a try, I'd bet that will work on an S590.

I can't believe this is so straightforward, once I've got it all set up (thanks to your help).

My pleasure, you've climbed the mountain, all down hill from here.
 
Well it has not been smooth sailing after yesterday's successful rip. Today it took numerous repeats of the whole sequence of powering down with AC disconnect, checking settings, whole thumb drive procedure... rip speed issues... got it ripping at a normal speed and then it was done and I exactly followed the instructions

To remove the disc just press Open to eject the tray. To rip another disc, just place a new one in the tray, and once again Power OFF to close it. Wait for the display to stop flashing OFF (player sleeps), then Run the next rip. You do not reinsert the flash drive for that.

and now I cannot rip another disc, keep getting this readout in GUI panel:

[RUNNING][C:\Users\Ferrara\Music\Music\SACD RIPPER\SACD Extract\sacd_extract.exe, -i, 192.168.1.249:2002, -s, -z, -2, -o, C:\Users\Ferrara\Music\SACD Files]


Response result non-zero or disc opened
libsacdread: Can't open 192.168.1.249:2002 for reading


[DONE]

I don't get it. I checked the IP address and it is the same, correct.

I guess I need to do this whole business over again! Power cucle off. Check Settings. Thumb drive repeat. WHAT IS WRONG HERE?

I did the entire Autoscript reinstall. Before it worked. Now, no go. Keep getting that message.
 
Last edited:
Any repeated reinsertion of the thumb drive causes an eventual 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.

Did I do something wrong by having to reinstall the flash drive too many times? I don't understand the above quote. Can I fix this and prevent it from happening again? Do I need a new flash drive? Is this player exhausted of RAM and now useless? Help, please...
 
libsacdread: Can't open 192.168.1.249:2002 for reading
That is the error I got when I had the IP address wrong. When I corrected it it began to work. On mine the IP address had a .73 or .78 range where you have .249
 
Response result non-zero or disc opened
libsacdread: Can't open 192.168.1.249:2002 for reading

Thats not an SACD, it is a Rebook CD. You can't rip a Redbook CD with this program.

That is the error I got when I had the IP address wrong. When I corrected it it began to work. On mine the IP address had a .73 or .78 range where you have .249

My IP (or anyone else's) and your IP are totally unrelated, there is no relationship there, it is simply how your router decides to provision the IP address. If you are unsure of the IP check the on-screen display or use Fing. Whatever it says your IP is, that's what you use.
 
Did I do something wrong by having to reinstall the flash drive too many times? I don't understand the above quote. Can I fix this and prevent it from happening again? Do I need a new flash drive? Is this player exhausted of RAM and now useless? Help, please...

Please relax, nothing you do is ever permanent. No you cannot permanently exhaust the player's available RAM, power cycling always resets it.

The error message in that post suggests either the script had not yet been read in (like in your very first problem post last night), probably after you did a power cycle, OR it was in need of a power cycle.

Again, I do not have this issue on my Mac, but others using Windows do. It seems to be a memory leak in the executable and there is nothing you can do about that except power cycle the machine every 4 or 5 rips to reset the RAM, then read-in the script again with the USB flash drive after the power cycle is complete.

Take your time, you'll notice after you replace the power cord the unit goes through an initial boot sequence (watch the front panel LED display). After that boot sequence is over the machine will be in an OFF state, so turn it on and again, and wait for the display to show the unit is ready. Then insert the flash drive and after placing a disc in the tray, Power OFF to close it, and watch/wait until it stops flashing OFF, then Run the rip.
 
Thats not an SACD, it is a Rebook CD. You can't rip a Redbook CD with this program.

D'oh! I am such an idiot. You're right. What happened was I was ripping my hybrid SACD of Todd Rundgren's Something Anything, and it is a two-disc set with the CD audio split onto two discs due to length of program material, while the stereo SACD content is all on disc 1, and I had tried to rip disc 2 with my SACD extract. I have inserted the SACD disc and it is working now!

And the slow speed issue I complained about in my PM to you is not happening, rip speed bopping along at 2.2MB/sec.

Thanks for clueing me in to what I was doing wrong.
 
Hi!
Today I updated windows and I'm getting this error message. The player address seems the same.

Do i need to rerun java?
 

Attachments

  • error.PNG
    error.PNG
    23.2 KB · Views: 14
Hi!
Today I updated windows and I'm getting this error message. The player address seems the same.

Do i need to rerun java?

Thats twice today for that error message! See Post #813 directly above.

You are attempting to rip a (Redbook) CD, but the program will only rip (Scarlet Book) SACDs.;)
 
The only hang up I've heard with regard to 4 or 5 consecutive rips appears isolated to the Windows version of the executable (i.e. I do not have this same problem on a Mac), however some users report that after about 4 or 5 consecutive rips the system stops working and requires a full power cycle using the AC plug.

What happens with me on Windows 10 is I get just 2 full speed rips, then what happens is for the 3rd consecutive rip the speed slows down to a crawl (from 2.2MB/sec to less than 0.10MB/sec). And then I have to do the full power cycle and reinitiate the thumb drive script, and then it usually works, but only for another 2 rips.

I guess it ain't perfect, but it's the best I can expect. This will only be a hassle as I get thru ripping my whole SACD collection of only three dozen discs, and have to keep starting over. At the rate I am buying SACDs at this point (none in several months due to the high prices of SACDs), I won't have to worry about this too often.
 
What happens with me on Windows 10 is I get just 2 full speed rips, then what happens is for the 3rd consecutive rip the speed slows down to a crawl (from 2.2MB/sec to less than 0.10MB/sec). And then I have to do the full power cycle and reinitiate the thumb drive script, and then it usually works, but only for another 2 rips.

I guess it ain't perfect, but it's the best I can expect. This will only be a serious hassle as I get thru ripping my whole SACD collection of only three dozen discs, and have to keep starting over. At the rate I am buying SACDs at this point (none in several months due to the high prices of SACDs), I won't have to worry about this too often.

As mentioned previously, try a reset by doing a press/hold of the power button for 10 seconds as mentioned by @stereo hifi , that should not prove to be any big hassle, and once done all you'd need to do is reinsert the flash drive. Note that can't be done with the remote, only with the power button on the actual machine.
 
As mentioned previously, try a reset by doing a press/hold of the power button for 10 seconds as mentioned by @stereo hifi , that should not prove to be any big hassle, and once done all you'd need to do is reinsert the flash drive. Note that can't be done with the remote, only with the power button on the actual machine.

Yep, you are right, that works.
 
Some time ago there were a few members here, all of whom using Windows, reporting something similar to what @No Such Member is experiencing with regard to ripping SACD using a Sony Blu-ray player and SACDExtractGUI/3.9, similar though not identical reports of needing to power cycle/reboot the machine after multiple consecutive rips.

I say similar because these reports are not identical at all, which is interesting and suggests maybe it isn't just a memory leak in the executable. If it were, wouldn't all members using Windows experience just about the exact same thing, with perhaps only minor variations among different specific models eg. S390, 590, 5100 etc...?

Those past reports indicated a need to power cycle/reboot the Blu-ray player and rerun the AutoScript every 5 or so rips. Some of those reports go back to the original version of sacd_extract 3.9 circa fall 2018, while the more recent report by @No Such Member indicates trouble after just 2 consecutive rips, whereby the 3rd consecutive rip attempt plods along at super reduced speeds and/or fails.

I do have my Windows 10 laptop at home this weekend, so I decided to do a test as most of my prior rips with Windows were just isolated tests using only 1-2 discs at a time, my main ripping platforms are macOS, and Linux based. I only really use Windows for business, and certain small testing. My Windows 10 test will initially seek to replicate the parameters being used by @No Such Member , i.e. DSF stereo extraction.

So last night I power cycled my Sony S590 to clear the decks for a consecutive rips test with that unit. The S590 is connected to my router via Ethernet, and the Windows 10 laptop connects to my network via WiFi.

Rip #1:
Grant Green: Green Street

13888


2.66MB/s, not too shabby for WiFi...

Rip #2:
Grant Green: Grantstand

13890


2.85MB/s, slightly faster (not all discs rip at exactly the same speeds of course).

Rip #3:
Grant Green: Idle Moments

13891


2.93MB/s, a tad faster still...

Rip #4:
Pink Floyd: Dark Side Of The Moon

13892


2.81MB/s, still quite fast...

Rip #5:
Mathew Sweet: 100% Fun

13893


2.56MB/s, slightly slower but still very acceptable for WiFi...

At that point I turned in for the night. But the test isn't over. I simply turned off the S590, and today I will turn it back on and just resume ripping, no power cycle, no reinsertion of the AutoScript, no anything other than open the tray, load a disc, Power OFF (sleep mode), and Run the rip:

Rip #6:
Joan Baez: Diamonds And Rust In The Bullring


13894

2.87MB/s, picked up right where we left off last night...

Rip #7:
Ella Fitzgerald: Let No Man Write My Epitaph

13895


2.69 MB/s, still no apparent big slowdown or problems...

Rip #8:
Aaron Neville: Nature Boy


For this one I decided to throw a wrench in the works and change the rip parameters to ISO+DSF.

13897

Houston? We have a problem. But I doubt it has anything to do with having changed the rip parameters, much as that might seem the logical conclusion. I now wish I hadn't introduced that variable when I did, but it's too late to go back.

The actual problem likely has nothing to do with me changing the GUI settings to request different output. What the error message above says is the server running on the Blu-ray player was suddenly no longer accessible on Port 2002, my client PC could not connect to it.

But why is that? Probably as originally surmised here by other members using Windows, a slow memory leak in the executable that eventually exhausts the Blu-ray player's very limited available RAM. Thats as good a guess as any, however any/all alternative explanations or theories are welcome.

But would a power cycle/reset fully resolve it? I decided to try the press/hold Power for 10 seconds version of this, more or less a reset as opposed to an actual physical remove/replace of the AC power cord. The machine behaves the same way on reset as it would if the plug had been pulled, on reboot the display shows WAIT for 10 seconds or so, then the unit resumes stand-by.

I powered it on, reinserted the USB flash drive to read in the AutoScript and the tray opened, then placed a disc in the tray and closed it by entering sleep mode via Power OFF.

Rip #8 redux:
Aaron Neville: Nature Boy


13898

Normal ripping resumed, in concurrent mode, both ISO+DSF created in one pass of the optical media.

13899

2.92MB/s, complete DSF and ISO creation, all tracks present.

So what did we learn with this test?

I'm not entirely sure, except to say on my S590 using the Windows version of sacd_extract 3.9, consecutive rips totaling 7 showed not a peep of trouble, nor any slowdown. Then on rip #8 the server was suddenly unavailable and all attempts to recover failed except for a full reset of the Blu-ray player, at which point normal ripping resumed after reading in the AutoScript on the USB flash drive again.

Windows users, I invite your own input and experience with this phenomenon, or for that matter if anyone has run into this on macOS, or Linux.
 
Thanks, MikeyFresh, for making and documenting these thorough tests for the benefit of myself and the community here!

As it turns out, the difficulties I've been experiencing during the past couple days (detailed in my several posts above this one) have turned out to be almost entirely a consequence of unstable wifi on my home network, and not due to any glitches or defects in either the SACD Extract app or my Sony BDP-S590. The slow rip speeds were the biggest hindrance to performance and that is all on account of my router, most likely.

The only other difficulties I have been having were either a consequence of my own user error as I am learning the procedures here, or the noted Windows .exe memory leakage which has necessitated going through the flash drive Autoscript reset from time to time. I lost count but I think I got through at least half a dozen rips before I got the error message that suggested I needed to do the reset, today. I've done over a dozen rips today and I'd say things are relatively stable now, if a bit slow on account of my wifi speed.

The last tip or reminder I would offer anyone who is getting any kind of read failure message in the GUI panel is double check the IP address on the player. My IP address would sometimes change after rebooting the router when I had to do that.
 
Back
Top