Rip SACD with a Blu-ray player

MikeyFresh

Moderator
Staff member
The firmware is M5.R.0255. Not sure if that has an impact.
That firmware should work.

I'm pretty well out of troubleshooting ideas except to say that certain members have solved problems just by using a different thumb drive for the AutoScript. That said, they weren't getting that same error message that you are.

I have no explanation for why using a different thumb drive would help, other than to say if the drive had ever been reformatted previously using Windows, that can often create a hidden partition on it that will break this process.

The entire discussion of hidden partitions and how to fix that in Windows is beyond the scope of this thread, but you may wish to try a fresh download of the AutoScript onto a different thumb drive, especially if you have one that you know was factory fresh formatted still and had not ever been previously reformatted in Windows.
 
Hello,
First of all, I would like to thank MikeyFresh for inviting me to register on this particularly interesting site and all those who participate in its activity for all the information they share .
I am a French user and I do not practice English fluently enough to express myself as precisely as I would like in this language.
Moreover, this text is the Google translation of my first intervention on this site.
So - and I hope I do not contravene the rules by doing this - I will speak now in French.
As I imagine that some of the members of the community are also French-speaking, this could eventually be nice and useful.

J'ai profité de l'expérience que vous avez partagée et je suis parvenu, moi aussi, à ripper plusieurs de mes SACD, avec un SONY BDP-S490, acheté d'occasion pour moins de 50 euros.

La raison principale de mon intervention sur ce site est de préciser - pour ceux qui s'engageraient également dans l'aventure - comment ne pas trop buter sur une ambiguïté sur laquelle je suis resté coincé une bonne après-midi avant de trouver la solution, évidente après coup, pour arriver à mes fins.
Pour ma part, je fonctionne avec un PC sous windows 10.
J'ai donc téléchargé les outils nécessaires :
- les utilitaires géniaux Sonore ISO2DSD freeware et SACDExtractGUI, à la page Rip SACD with a Blu-ray player
après avoir donc acquis l'un des lecteurs de Blu-Ray qui permettent l'opération, dont la liste figure sur cette même page;
- les trois fichiers contenus dans l'extractible AutoScript.zip, téléchargeables à la page Rip SACD with a Blu-ray player.
Et c'est là que je n'avais pas bien tout compris. En effet, rien ne fonctionne si vous ne créez pas manuellement, à la racine de votre clé USB tout fraîchement formatée, un dossier nommé AutoScript dans lequel vous insérez les trois fichiers obtenus après la décompression de l'extractible AutoScript.zip.
Par contre, si vous suivez scrupuleusement cette démarche, le miracle s'accomplit sans coup férir.
Voilà, j'espère que cette petite précision pourra être utile à d'autres nouveaux candidats.

Encore merci à Mikey Fresh et à tous ceux qui contribuent à l'information sur la réalisation de ces rips, qui me paraissait être tellement complexe quand il aurait fallu l'aborder avec une PS3 beaucoup moins simple à mettre en oeuvre.
 
Hi, newly register here at Hi Fi Haven. Last week I discovered Hi Fi Haven for this exact topic, SACD ripping.

Due to the highly detailed information, I was able to collect everything required in an hour or two to begin ripping my SACDs collection. I ran into one roadblock with the sacd_extract downloading as a text file versus an executable on the Macbook. I found the detail I needed in the thread to resolve this issue. To my surprise, this has been extremely easy due to the detailed information here. Thank you!

I'm using a Sony BX-59 Blu-Ray player I surprisingly had laying. The BX-59 is wired directly into my router and SACDExtractGUI process both ISO+DSF stereo over wifi to my Macbook.

Just when my first SACD rip finished, I received a welcome personal message from @MikeyFresh while I was researching what the "Padding-less DSF" setting was. I accidentally unchecked the option during setup, but after Mike explained what it was for I determined I want it selected.

Mike shared the following on the Padding-less DSF setting. "Padding-less DSF should be used to minimize the potential for an audible click or pop between tracks that can occur on playback depending on a variety of factors, including which specific DAC you use, the playback software, how that particular disc was authored, etc...".

A dozen SACDs in now.
 
Hi Mikey,

I purchased an S5100 and it arrived a few minutes ago. And you were right - it works like a charm. I am pulling off the DSF's now. Its hardwired for the moment, and working running at a consistent xfer rate of about 2.5MB/sec. Now to figure out all the options on SACDExtractGUI.

Thank you for your help and for all of the others who contributed to this fantastic bit of magic. I'll keep watching for opportunities to return some of that to the community.

By the way I did upgrade the firmware once I found an article where you noted updates had not interfered with ripping, YET. (someone else is running the same version)

-Steve
 
Hi Mikey,

It worked twice then stopped and I did not change anything. However, my machine that talks to the S5100 hung - the java applet stopped working and the network hung - odd (its wired). I did not spend time debugging the cause as rebooting my cable router fixed the problem both times.

The USB is one of 2 Sandisk Cruzers both fat32 formatted and the directory structure looks like:
1549416915280.png
I did a factory reset of the player and then set the following:
1. Setup -> Audio Settings -> DSD Output Mode (Off)
2. Setup -> BD/DVD Viewing Settings -> BD Internet Connection (Do not allow)
3. Setup -> Music Settings -> Super Audio CD Playback Layer (SACD)
4. Setup -> System Settings -> Quick Start Mode (On)

I follow this sequence
  1. start with the player unplugged and the USB drive removed
  2. Plug in the player
  3. Wait for it to boot up (flashes "Wait, Wait") in the display
  4. Player immediately goes to sleep
  5. I power it up
  6. When the display says "Empty" (which it does very quickly), I insert the USB in the front slot (rear slot seems to make no difference)
  7. The drawer opens in a few seconds
  8. I insert the disc, remove the USB (its still flashing - showing active) and press the power button
  9. Player goes to sleep after flashing "Off" a few times.
  10. I turn to my computer where the java applet is ready to go and hit "Test" (alternatively - just hit "Run") to see if the port is accessible and it often is now.
  11. I click on Run and get the following message reliably - unfortunately.

1549419011955.png


And of course the disc is not opened. I've closed the GUI a few times w/out success. What's irritating is that I already made transfers before. Now I cannot - I've shut off my AV and Malware stuff - still no success.

Any ideas about what is causing the non-zero or disc opened error message when the test shows its open before and after the "run".

Thanks,

-Steve
 

MikeyFresh

Moderator
Staff member
Any ideas about what is causing the non-zero or disc opened error message when the test shows its open before and after the "run".
I don't and what's crazy is you are the 2nd member in a row having that exact error message using Windows. The only difference is @svq can't get any rip to commence whatsoever, whereas you did.

Not only have my own rips using my Windows 10 machine been flawless, but various other members going back to last October when the compiles for sacd_extract 3.9 and the new GUI first became available have also had no problems using Windows.

Very strange, but I will report this to the developer and see if he can recreate it or for that matter offer a solution.

In the meantime, I only see one confusing thing in your post above:

8. I insert the disc, remove the USB (its still flashing - showing active) and press the power button
This is not normal behavior unless I'm reading it wrong. You are saying the LED on the flash drive continues to blink as active while the tray is open? If so that is not how my systems behaves at all, on my set-ups the LED flashes only briefly, then stops, as it is reading in an absolutely tiny miniscule file of 345 kilobytes total, in just a second or so my flash drive LED stops blinking.

So if I'm reading it right, please try the following, load disc in tray, press OFF, and wait for all flash drive activity to cease before removing it. This is good practice anyway, you never want to remove a storage device during an active read or write. I very much hope the script is not corrupted now, but to guard against that variable you can always delete the AutoScript you have a write a fresh one to it.

The chances of corruption are nearly 100% if the thumb drive is removed during an active write, but that's not what occurred here, it was an active read, so it should still be OK. However to eliminate that as a variable, delete what is on the thumb drive and flash a fresh copy of the AutoScript, then try again as described above, only removing the thumb drive after all LED activity ceases.

EDIT: Another thing I should add is after a rip completes and you are ready to do another, do not ever reinsert the USB flash drive, that is entirely unnecessary and will eventually cause a problem for two reasons. The first is that the Sony's OS can mount the drive from the wrong point the 2nd time because it thinks the drive is still mounted at the primary point, but the script will only run from the primary mount point. The second reason is each insertion of the thumb drive uses more RAM, which is in precious short supply on these machines, eventually the unit runs out of RAM.

So don't ever reinsert the thumb drive, you don't need to, the script is still read into memory from the first time. To execute a 2nd rip just eject the tray, load a new disc in, and Power OFF again. The machine will sleep again and is then ready for another rip. There is no repeated insertion of the thumb drive.
 
  • Like
Reactions: Srx
Thanks Mikey for the quick response - I did as you suggested , no luck I received the same exact message.

-Steve
 

MikeyFresh

Moderator
Staff member
Thanks Mikey for the quick response - I did as you suggested , no luck I received the same exact message.

-Steve
OK, but what about another full power cycle?

So clear the unit by powering it down, remove the thumb drive for that, pull and then replace the power cord, that whole 9 yards. Then once the machine has fully rebooted, insert the thumb drive, load a disc, Power OFF, remove thumb drive only once all LED activity ceases, then run a rip and note my EDIT above, do not reinsert the thumb drive as that causes problems and is unnecessary. This was mentioned earlier in the thread but perhaps not prominently enough.
 
  • Like
Reactions: Srx
I don't and what's crazy is you are the 2nd member in a row having that exact error message using Windows. The only difference is @svq can't get any rip to commence whatsoever, whereas you did.

EDIT: Another thing I should add is after a rip completes and you are ready to do another, do not ever reinsert the USB flash drive, that is entirely unnecessary and will eventually cause a problem for two reasons. The first is that machine can mount the drive from the wrong point the 2nd time because it thinks the drive is still mounted at the primary point. So don't ever reinsert the thumb drive, you don't need it, the script is still read in form the first time, to execute a 2nd rip just eject the tray, lod a new disc in, and Power OFF again. The machine will sleep again and is then ready for another rip. There is no repeated insertion of the thumb drive.
ARGH - I did that - reinserted the drive - more than once. Any ideas about how to correct it?

-Steve
 

MikeyFresh

Moderator
Staff member
ARGH - I did that - reinserted the drive - more than once. Any ideas about how to correct it?

-Steve
Just do the above sequence, and again, to avoid the possibility the script was corrupted by removal during the LED activity, you've flashed a fresh/clean copy of the AutoScript, correct?

If so, just do the above full power cycle reboot as described, slow and methodical. Then follow the revised steps, do not remove the drive while the LED is still flashing, and do not reinsert the drive after a rip finishes and you should be OK.
 
  • Like
Reactions: Srx
Just do the above sequence, and again, to avoid the possibility the script was corrupted by removal during the LED activity, you've flashed a fresh/clean copy of the AutoScript, correct?

If so, just do the above full power cycle reboot as described, slow and methodical. Then follow the revised steps, do not remove the drive while the LED is still flashing, and do not reinsert the drive after a rip finishes and you should be OK.
Thanks! Will do.
 

MikeyFresh

Moderator
Staff member
And yes I have flashed a new copy of the scripts.
OK, and another note on use of the thumb drive for future reference, while the Oppo, Cambridge, Pioneer units do not seem to mind being powered up with the thumb drive already inserted, the Sony machines do not like that and can very often (but not always) malfunction if the initial boot up takes place with the thumb drive already inserted.

So when starting a Sony machine, always leave the thumb drive out until the initial boot sequence is completed, then you can insert the drive if you were recovering from a full power cycle... or, if you were simply powering the machine ON again from an OFF state, there is absolutely no need to reinsert the AutoScript then either as the unit was only in stand-by (that's what Quick Start mode enables) and will still remember the script from the last time you used the machine.

On my S590 that I currently have set-up in my bedroom, I have ripped countless discs over about 6 weeks now where the AutoScript thumb drive was never reinserted that entire time. This is because I don't use the machine for any general use, there is no movie watching or anything else, so it just stays in ripping mode and when you turn it OFF with the power button it is only going into stand-by/sleep, you can always awaken it with either the open/close button or the power button and no reinsertion of the thumb drive is necessary, it's still ready to rip. Mine has been used that way for many weeks at a time including just last night, I powered it on and just loaded a disc, Powered OFF, and ripped. The last time I did that was about a week ago, doesn't matter, the player remembers the script unless the power cord is pulled. The script was read in 6 weeks ago.
 
OK, and another note on use of the thumb drive for future reference, while the Oppo, Cambridge, Pioneer units do not seem to mind being powered up with the thumb drive already inserted, the Sony machines do not like that and can very often (but not always) malfunction if the initial boot up takes place with the thumb drive already inserted.

So when starting a Sony machine, always leave the thumb drive out until the initial boot sequence is completed, then you can insert the drive if you were recovering from a full power cycle... or, if you were simply powering the machine ON again from an OFF state, there is absolutely no need to reinsert the AutoScript then either as the unit was only in stand-by (that's what Quick Start mode enables) and will still remember the script from the last time you used the machine.

On my S590 that I currently have set-up in my bedroom, I have ripped countless discs over about 6 weeks now where the AutoScript thumb drive was never reinserted that entire time. This is because I don't use the machine for any general use, there is no movie watching or anything else, so it just stays in ripping mode and when you turn it OFF with the power button it is only going into stand-by/sleep, you can always awaken it with either the open/close button or the power button and no reinsertion of the thumb drive is necessary, it's still ready to rip. Mine has been used that way for many weeks at a time including just last night, I powered it on and just loaded a disc, Powered OFF, and ripped. The last time I did that was about a week ago, doesn't matter, the player remembers the script unless the power cord is pulled. The script was read in 6 weeks ago.
Ok - tried it again and got the same response - I reset it to factory defaults before I did it and then checked the 4 parameters you specified and the IP was the same. Fresh load of scripts off the dropbox too.

Let me find a manual and see if there is a hard reset that may shake it loose. And I will try it from a laptop.

-Steve
 
Yes:-) been there done that x2 to be sure no change - I want to be sure its not the config of this machine, I have a couple of simpler boxes that I can use..
 

MikeyFresh

Moderator
Staff member
Hello,
First of all, I would like to thank MikeyFresh for inviting me to register on this particularly interesting site and all those who participate in its activity for all the information they share.
Welcome to HFH @Cabasse , it's my pleasure and we are glad you found this thread useful for extracting your SACDs, and the site as a whole interesting for its many facets.

I am a French user and I do not practice English fluently enough to express myself as precisely as I would like in this language.
Moreover, this text is the Google translation of my first intervention on this site.
Don't worry, the Google Translation worked very well! It's very easy to understand you in the Google translated English.

Encore merci à Mikey Fresh et à tous ceux qui contribuent à l'information sur la réalisation de ces rips, qui me paraissait être tellement complexe quand il aurait fallu l'aborder avec une PS3 beaucoup moins simple à mettre en oeuvre.
Encore une fois, mon plaisir et bienvenue à bord. Vive le rips de SACD!
 

MikeyFresh

Moderator
Staff member
I can get to sleep mode, ping, and pass the "Test" with SACDExtractGUI. But when I execute it reads "Response result non-zero or disc opened libsacdread: Can't open 10.0.00.23:2002 for reading"
It worked twice then stopped and I did not change anything.
OK, I spoke to the developer, and unfortunately it could be bad news for the Blu-ray players involved.

He said that error message from sacd_extract.exe is an indication of:
  1. no disc
  2. non-SACD disc
  3. or CDDA layer selected over the SACD layer
#3. Can be checked by simply playing the disc on the player with a TV connected to it. The player indicates so in the on-screen display when the SACD layer is being played back. If the CDDA layer is indeed selected over the SACD layer, the player's setting needs to be changed to make the SACD layer the default layer.

The first thing then to double check is the following on-screen display menu setting:

Setup -> Music Settings -> Super Audio CD Playback Layer (SACD)

If the above setting is correct try to play an SACD. If the player shows it is playing the DSD content, then we are completely stumped. If on the other hand the player refuses to play the DSD layer and instead is playing back the Redbook CD (CDDA) layer, then unfortunately that likely means a faltering laser or mechanism, and the unit would need at the very least a laser lens cleaning.

I do know of one guy in England who had this trouble a year or more ago and he actually found a tear down video for his unit's mechanism, took it apart and cleaned it, put it back together and it then proceeded to work just fine.

I wish I had better news for the two of you, but maybe it's as simple as the setting above needs revision? Hopefully so, otherwise it could also be a case of having loaded a regular Redbook CD into the tray. Don't laugh.

This can and does happen, probably because many people will own the very same album title on both formats, and at some point might have mistakenly placed the wrong disc back into the SACD jewel case. So double check that the disc you are trying to rip is actually an SACD, and if so, inspect the underside "run out groove" inner hub area of the disc for any scratches or damage to the TOC and timing code. If the machine can't read the SACD layer's TOC or timing code due to damage or detritus, it may then revert to the CD layer of the disc if that is actually seen by the laser as playable.
 
  • Like
Reactions: Srx
I don't and what's crazy is you are the 2nd member in a row having that exact error message using Windows.
Hello,
About these difficulties of using the USB key with Windows 10, I would like to repeat, without being sure that this is the solution, my experience has proven positive:

En effet, rien ne fonctionne si vous ne créez pas manuellement, à la racine de votre clé USB tout fraîchement formatée, un dossier nommé AutoScript dans lequel vous insérez les trois fichiers obtenus après la décompression de l'extractible AutoScript.zip.
Par contre, si vous suivez scrupuleusement cette démarche, le miracle s'accomplit
Either, translated into English:
"nothing works if you do not manually create, at the root of your freshly formatted USB drive, a folder named AutoScript in which you insert the three files obtained after decompressing the extractable AutoScript.zip.
On the other hand, if you scrupulously follow this step, the miracle is accomplished."

I hope this suggestion will help windows 10 users.
 
Top