SACD Ripping using an Oppo or Pioneer? Yes, it's true!

[tmtomh]

3 minutes ago, Phthalocyanine said:

@tmtomh

The server method is great when it works, but when it does not it can be hard to troubleshoot.

 

Although you may eventually want to use the server method exclusively it might be useful for you to try my local ripping method via telnet because this a process that you can get feedback as you go.  At the least, you should learn how to telnet in order to see how the usb stick is mounted.
 

 

 

•  

 

 

Telnet functionality is automatically opened up with the script and this does not interfere with the server connection.

•  

  The only way that you can determine how the linux operating system is mounting the usb drive (as sda or sda1 or sdb or sdb1 etc.) is to use the telnet connection with the player and navigate to the /mnt directory and look there.  This is not something you can find in any of the Sony on-screen menus.

 

Thanks so much for your reply. I found one issue - but unfortunately it does not seem to have solved the problem.

 

I telnetted in to the Sony player and was surprised to see that the USB stick was mounted as sdb1 instead of sda1 - very strange since the unit has only one USB port. But it is a rear port, so perhaps the software/chipset assign sdb1 to the rear port regardless of whether the unit has a front port...?

 

So I changed the AutoScript to sdb1 instead of sda1. But now, instead of throwing up an error, DSD2ISO instead doesn't do anything at all - the "Execute" button greys out and no ripping status or error message appears. And, unfortunately, the Sony locks up completely at that point - I have to unplug it to get it to work again.

[tmtomh]

4 minutes ago, MikeyFresh said:

 

 

I have both a BX510 and a S5100 machine, I used no special version of AutoScript, the same exact copy I had been using on the Pioneer BDP-160 worked well for me on the Sony units with the server method and ISO2DSD.

 

Initially I used the method in which the Music Setting is toggled, however I found it a little easier to utilize the sleep method instead, as it allowed me to forego any on-screen display, or for that matter any need for an HDMI connected display:

 

https://vimeo.com/270884101

 

 

 

Thanks for your reply. What is the sleep method? I've looked for something involving sleep in the on-screen menus, but I can't find anything.

[tmtomh]

2 minutes ago, MikeyFresh said:

 

My BX510 has two USB ports, the one in the front is on the far right-hand side hidden behind a pop-out plastic door that literally just pulls away. Thats said, I use the rear panel USB port as shown in the previous post's video using a USB extension cable/dongle.

 

D'oh! You're right - I found the front port just now based on your comment.

Can you explain a bit more about "sleep mode" on this unit? Thanks!

 

@Vincent Neo - thanks for the tip about Linux mounting. You're right - it mounts as sda1 whenever I plug it in to the Sony for the first time after turning on the Sony, but if I unplug and replug, it mounts as sdb1. So that solves that mystery.

 

But I still can't get it to rip the SACD. It appears that when the script matches the mount point/ID of the USB stick - sda1 for example - I get the "non zero or disc opened - can't open 10.0.1.24:2002 for reading" error. And when the script does not match the mount point - sda1 vs sdb1 for example - the Sony just locks up completely.

[tmtomh]

4 minutes ago, MikeyFresh said:

 

Some pages back it was suggested by @mindset, and it works perfectly for me:

 

Step 1: Power on Sony BX510

Step 2: Connect USB thumb drive dongle/AutoScript runs/tray opens automatically/load SACD

Step 3: Power down Sony S5100/tray closes automatically/player goes to sleep/AutoScript gains root access control

Step 4: Execute rip in ISO2DSD with one click while Sony S5100 is fast asleep
 

You must first disable the power saver setting, I can't remember exactly what thats called but in essence it allows for fast start/boot from stand-by mode as opposed to dead cold/lengthy start-up boot sequence.

 

Wow, very cool! Unfortunately mine still isn't working that way - I press Execute on ISO2DSD and nothing happens. I'll try a different USB stick, since I can't think of anything else.

[tmtomh]

18 minutes ago, MikeyFresh said:

 

And maybe also a clean unaltered copy/version of the BDP-160 AutoScript might do the trick, the one I linked to works well for me.

 

Thanks. I grabbed your files and used the sleep method. Pressed Execute on ISO2DSD, and then after several minutes got a different error message: "Failed to connect - can't open 10.0.1.24:2002 for reading."

(And to be clear, I've confirmed and reconfirmed that the IP address is correct, and Quick Start mode is Off)

[tmtomh]

1 minute ago, MikeyFresh said:

 

I believe you want that Quick Start mode set for "On"... it allows the machine to fast boot (irrelevant for our purposes), and also to enter sleep mode on Power Down as opposed to complete shut down.

 

Holy sh** - that did it! It's ripping now. Fantastic!

 

As to what the issue was before, I'm still not sure if it was something in the other scripts, or some quirk of the USB stick, but it doesn't really matter as it's working fine now.

 

And that sleep trick is amazing - it basically makes the Sony unit function 95% like a regular external CD drive, except for SACDs. Of course you have to insert the USB stick each time, but otherwise it's basically as easy as ripping a CD.

[tmtomh]

2 minutes ago, MikeyFresh said:

 

Another @mindset revelation: you can remove the USB thumb drive and it is no longer needed at all unless the Sony's power cord is disconnected or some other power outage occurs, other than that the player will stay in ripping mode and you can execute consecutive rips without reinserting the USB thumb drive by sleeping the machine each time.

 

Yes, I (and I'm sure many others) discovered something very similar with the Oppos - you can take out the USB drive and they'll keep ripping SACDs one after the other until you turn them off. (The Oppos also have an energy saver vs quick start option, but I can't remember if the quick start option allows you to stay in ripping mode like with the Sony units.)

[tmtomh]

1 minute ago, MikeyFresh said:

 

Yes and if you have good WiFi, then the only cable needed is the Sony's power cord, which means the ripping station can be physically located anywhere there is a stable WiFi connection.

 

Without good available WiFi, you'd of course need an Ethernet cable connection as well as the Sony's power cord.

 

Yes, that was exactly my plan/intention when I got this, and the sleep method enables that.

[tmtomh]

4 hours ago, gammarayson said:

My first post here! I have successfully ripped over 60 SACDs with my Oppo 105D and Mac using the Sonore iso2dsd software. Despite my very basic computer skills, the process has been smooth without any problems. Now I have bought the Oppo 205, which does not allow the ripping of SACDs, so my plan was to sell the 105, and buy a cheap Sony or Pioneer for the sole purpose of ripping in future. I have bought a Sony BDP-S5100 relatively cheaply on eBay, but I can't get it to connect to my network. (I believe, this model is one of the ones that can rip SACDs).It is hardwired to my Airport Extreme router. I have noted the IP address and entered it in the software and clicked "execute" but get the message "failed to connect-can't open.." I have tried on my Oppo in the same way, and and it works perfectly. Am I doing something wrong? PS when I started the Sony for the first time, I was prompted to update the firmware. Was that a mistake, I wonder whether that removed the possibilty of SACD ripping? Thanks in advance!

 

@MikeyFresh provides very helpful info just above.

 

As someone in virtually the same boat as you, I can offer some info too, although a lot of it overlaps with Mikey's.

 

I had an Oppo 105, replaced it with a 205, and just got a Sony BX510 (identical to the 5100) off eBay. And I initially had problems making it work as well.

 

I got mine to work by changing multiple variables so I can't say with 100% certainty which changed fixed the problem, but here are a couple of things to check, which I think were the most likely culprits:

• Use a clean script. If you're using the server method (as I am), I would recommend using the simplest script possible, one that does not activate telnet but merely enables the server method. I think Mikey has linked to the appropriate files a little earlier in the thread. I am told that the more complex script variants that include both Oppo and Sony instructions, along with telnet activation, should work, but in my experience they did not.
• Turn the Sony unit off and back on again before re-trying your USB stick. When the stick is repeatedly unplugged and re-plugged without first turning off the Sony player, it will assign a different drive ID to it. The script depends on the USB drive being ID'd by the Sony as "sda1." But if you uplug it and re-plug it without rebooting the player, it will get ID'd by the Sony as "sdb1" the 2nd time, and "sdc1" the 3rd time, and so on - thereby breaking the autoscript, which is coded for "sda1."
• If you are freshly formatting the USB stick on a Mac, ensure it's formatted using Master Boot Record, and MS-DOS/FAT16. Do not use the Mac-default GUID, and don't use exFAT, because while the Sony supports FAT and FAT32, it appears not to support exFAT.
• As Mikey indicated, the sleep method is far simpler than the music-setting-switch method, even if you have a monitor attached. My Sony came with the quick-start function turned On, but since we're all buying these machines used, they are not necessarily set to factory defaults, and so you should check the prefs to see whether or not that function is On or Off on your unit.

I was really flummoxed initially, but I have now gotten it working, and it's super-easy. The only difference I detect compared to ripping with my Oppo 105 is that the Sony unit seems to rip about 10% slower. But since the Sony unit is a dedicated ripper rather than a music player like my Oppo was, I don't care about the extra minute or two it takes to rip an SACD.

 

Good luck!

[tmtomh]

5 hours ago, gammarayson said:

Ok, now I have the right AutoScript on my thumb drive(AutoScript TSS,AutoScript,sacd_extract_160) and have enabled Quick Start mode but the drawer does not open automatically when I insert the thumb drive in the Sony....

 

If that's the case, then I would tend to suspect the formatting of the thumb drive. Are you sure it's formatted in FAT16 or FAT32, with an MBR scheme/partition table?

 

In my experience, the only time the Sony's drawer wouldn't open was when I had the USB drive formatted as exFAT (which is similar to FAT32 but not the same).

[tmtomh]

22 hours ago, servoyguru said:

Well, thank you from me!

I got a Sony BDP-S490 for £29 on eBay last week & now have finally got it to rip an SACD using this method (although I tweaked the auto script file to use 'CLI(CLI_exec cp `ls -d /mnt/sd*`/AutoScript/sacd_extract_160 /)' instead of the hard coded mnt point)

 

So excited to now be able to get all my SACD's into ISO format & play them back from Mac Mini/Audirvana/Pro-Ject S2 Digital!

 

Thanks again everyone on this thread ? 

 

This is a fascinating tweak - thanks!

 

A couple of questions, if you don't mind:

1. When you change "sda1" to "sda*" does the script recursively look for sda0, sda1, sda2, etc until it finds a mounted volume with the sacd_extract_160 executible on it? Doesn't really matter I suppose - I'm just curious about how it works.
2. Is that little mark after the * just a single opening quotation mark, or is it some special diacritical character?

Thanks!

[tmtomh]

16 minutes ago, MikeyFresh said:

 

It is pretty cool, I think this was another @mindset suggestion back in April, but if I read/remember it correctly, it is unneeded when using the sleep method, i.e. if you already have the Quick Start mode enabled then this becomes unnecessary?

 

 

I think it is just a grave accent mark, on the Windows keyboard I use at work it's a shared key with the tilde, found directly to the left of the numeral 1 key.  If so it's an ` as opposed to '.

 

 

 

 

Thanks Mikey! Yes, I see now it's the grave accent - same location on Mac keyboards too.

 

RE the sda*` tweak, yes, it's not necessarily using the sleep method, since the machine doesn't need the USB key to be reinserted. It wouldn't hurt, however, to modify the script file that way for folks just getting started, as initial testing/working out the kinks can result in folks re-inserting the USB key without rebooting the machine, and this tweak would just eliminate one potential source of problems. (Not a criticism and not asking anyone to implement that tweak; just thinking out loud...)

[tmtomh]

29 minutes ago, servoyguru said:

Well, I may have been a bit 'premature' with my joy...

I brought a pile of SACDs from home to my office where Sony BDP-S490 is wired up & after getting one more disk to 'rip' easily using the sleep method & ISO2DSD, I couldn't then get any others to, even the ones I had just managed to rip ?

It was giving me this error

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

I then tried starting afresh & using the combined AutoScript (with both Telnet & server mode commands in it * the tweaked mnt), I could Telnet to Sony, but when I tried to extract, I also got this error

libsacdread: Not a ScarletBook disc!
libsacdread: Can't read Master TOC.

I have now managed, somehow, to get local ripping to work after some combination of on/off, USB in/out, & various Telnet commands & the 2ch/multi ch toggle, but I REALLY wish I could get the sleep mode working properly for multiple discs ripping

 

I agree with the above comment about modifying the script & any instructions with

 cd `ls -d /mnt/sd*`/AutoScript/

instead of the /mnt/sda1 , as newbies will likely get stumped by the drive changing during trial & error process

 

If anyone has the answer to my top errors that stopped ISO2DSD from working, I'd very much appreciate it ? 

Thanks

 

The first error (non-zero/disc opened; Can't open... for reading) is pretty generic - could be lots of potential causes. It basically means the SACD is not available to the ripping app. Usually with the Sony machines this is because there's been some glitch in getting the machine to unmount/"let go of" the disc. However, it could also mean that the disc, or its SACD layer if it's a hybrid, simply isn't detected by the machine...

 

... which leads to your 2nd error, which I think is much more specific: That means the Sony machine was not seeing the disc as an SACD. Some machines sporadically fail to read the SACD layer - temporary glitch or perhaps marginal laser.

 

There is an issue sometimes with overly long track titles or nonstandard characters in the disc title or some such - but I don't think they result in the kind of error you saw. I could be wrong though - others would know better.

[tmtomh]

1 hour ago, servoyguru said:

Well it would seem that I might have an issue with my Sony, as, as correctly deduced here, it isn't always recognising the SACD layer of my discs, hence the errors/failures.

I am sometimes managing to get discs to work by cleaning them & just trying to open & close the disc drawer lots of times until it 'sees' the SACD layer [I am concerned that it's my own fault as I put a CD Lens Cleaner in to drive hoping to clean the laser, but I may have inadvertatnly damaged it...]

So, unless someone has a good idea how I can fix this or make it always recognise my discs, I may have to try & pick up another one on eBay 8-( 

 

Sorry to hear this. I recall that when the Pioneer units were the lowest-cost known option, several people bought them, and some reported the same issue. In fact, if memory serves, I think even one or two new-old-stock 80FDs or 160s fresh out of the box wouldn't consistently read SACD layers.

 

The one silver lining here is that the Sony units are so cheap on eBay and elsewhere, you can pick up another one - or even two more - and still be out of pocket for less than one of the Pioneer units, which are the next-least-expensive option.

[tmtomh]

11 hours ago, Deyorew said:

I have a question about scratched sacds. I have a disc that iTunes rips but stutters, XLD won’t complete the ripping process due to errors (both are the redbook layer of course) but my sacd layer iso ripped fine.

 

is it possible that it ripped the iso but the data is compromised? Or if it completes the rip then it is a good rip? I was curious about errors in ripping....

 

anyone have experience with this?

since there doesn’t seem to be an accurate DB like there is for redbook, so how do I know I have an error free rip?

 

Could be the rip has errors in it. But also keep in mind that the SACD data is in a different layer, read at a different focal length. So scratches and scuffs on the disc will have different levels of visibility and cause different degrees of problems when reading each layer. So a disc that has trouble being read on one layer, might rip okay on the other.

[tmtomh]

@forester you make a very good point - there's no error-checking/secure-ripping for SACD rips, and while the majority of rips are fine, occasionally glitches crop up.

[tmtomh]

13 hours ago, Phthalocyanine said:

What is the size of your .iso?  It might be that the .iso got abridged.  Sometimes that happens if the .iso is over 4GB and you were ripping to  a FAT 32 file system.

 

Good point - and one of the reasons I like the server-based ripping method.

[tmtomh]

2 minutes ago, Phthalocyanine said:

But it's just as easy to format one's USB drive in NTFS and avoid the problem that way.

 

Not on a Mac.

[tmtomh]

1 hour ago, bbosler said:

I am new to this and want to rip my SACDs. I have a Sony BDP BX510 which from what I read on this thread should work, but the Sonore program says it can't read it. I also see many variations of doing this, different downloads, different USB sticks, etc.. I can't (won't) scroll through 135 pages trying to find what is the right way for my player. I am hoping somebody has this player and can give detailed instructions on how do it. I have mac and Windows computers so whatever works. Thank you in advance

 

I have a Mac, and after retiring my beloved Oppo BDP-105 from my main stereo system, I decided to sell it (which I haven't gotten around to yet), and so I picked up a Sony BPD BX510 cheap off eBay to use as a dedicated SACD ripper. It works great!

 

From your description, it's impossible to know what issue is causing your problem. So if you want to find the solution you might very well have to read through at least a portion of those 135 pages. However, since the Sony machines were only recently discovered to work for SACD ripping, you can easily start reading 5-10 pages back from here and fairly quickly find the Sony discussion.

 

That said, here are the main pitfall areas folks (including me) have encountered, which could impact a Sony-based ripping setup like yours:

• USB Stick formatting: USB stick has to be formatted as FAT/FAT16, or FAT32, or NTFS. When formatting on a Mac, you want to choose FAT/MS-DOS. Macs don't offer NTFS, and they don't offer FAT32. (They offer exFAT, which is similar to FAT32, but the Sony machine doesn't read exFAT in my experience).
• USB Stick formatting - Mac-specific issue: If you format it on a Mac, you'll also need to make sure the stick is formatted with a Master Boot Record boot sector. The Mac default is GUID, and the Sony will not read a GUID formatted USB stick.
• AutoScript Folder Location: The AutoScript folder must be at the root level of the USB stick. The AutoScript and SACD Extract files must be INSIDE that Folder - they should not be directly at the root level of the USB stick.
• AutoScript Files: The SACD Extract file must be the "160" version (which works on the Pioneer BDP-160, 170, BFD80, and the Sony units including yours). A file named SACD Extract, without the "160" in the name, is for Oppo machines and will not work for you. In addition, the AutoScript file you have must be written to call up that "160" version of the SACD Extract file, not the non-160 version. Normally if you have downloaded a package of files that includes the sacd extract 160 file, then the accompanying AutoScript file will already be properly coded to work with the sacd extract 160 file.
• AutoScript File - Ripping Method: As detailed below, you can rip to the USB stick connected to the Sony (Telnet method), or you can rip over your network to your computer (server method). Which method you want to use will impact which AutoScript file you use. There are universal AutoScript files that enable Telnet for local ripping while also containing the necessary commands to enable remote/server-based ripping. However, I found that these more complex files did not work for me. Ripping with my Sony unit worked only when I switched to a super-simple, bare-bones AutoScript file that enables only the function I need (I use the server method).
• Sony Player Setup: For the SACD ripping app to work, the Sony player has to unmount the SACD - it has to "give up control" of it so the SACD ripping program can take control. There are two ways to do this. One is to have the Sony connected to a monitor, and each time you put in an SACD, navigate to the Sony's Settings menu and toggle the stereo/multichannel SACD setting. It doesn't matter what it's set on, just switch it. That trick unmounts the disc, and then you can go back to your computer and click "Execute" in the Sonore app. The other, and IMHO better, way, is to ensure the Sony is set to "quick start" mode in its settings. Then when you put an SACD in the tray, close it with the power button instead of the eject button. That will close the tray and turn off the Sony machine. But since it's in "quick start" mode, it's really only sleeping, not off. This status prevents the Sony from controlling/mounting the SACD, while still leaving it able to be "woken up" by the Sonore app on your computer. So the procedure would be to turn on the Sony, stick the USB stick in the machine, wait for the disc tray to open, remove the USB stick, put the SACD in the tray, then press the Power button to close the tray and prep the unit for commands from the Sonore app. The advantage of this "sleep" method is that you don't have to re-insert the USB stick as long as the Sony stays connected to AC power; and you don't have to keep the Sony connected to a monitor.
• How the Sony Player Names/Treats the USB Stick: This is among the most devilish of potential issues. In most cases, the USB stick will be assigned the label/ID "sda1" by the Sony machine, and so the AutoScript file is coded to look for sda1. However, if you are having other problems with SACD ripping, and you are repeatedly removing and re-inserting the USB stick in the Sony machine during troubleshooting, then the Sony will label the USB stick "sdb1" the 2nd time you insert it, and "sdc1" the 3rd time you insert it, and so on - thereby breaking the AutoScript file, which expects to find everything at "sda1." This is particularly devlish because in this situation nothing is actually broken - the AutoScript, the USB stick, and the Sony machine are all working just fine, and it's just a temporary problem based on the fact that you've re-inserted the USB stick instead of inserting it for the first time. There's a way to modify the AutoScript file to fix this, but the simplest solution for non-techie folks is just to turn the Sony off and on again before re-inserting the USB stick. That reboot of the Sony will make it revert to the proper "sda1" label for the USB stick when it's inserted.
• Telnet (local) mode vs Server (remote) mode: You always will be controlling the SACD ripping process remotely, from your computer. But you can do it so the SACD rips locally, to the USB stick attached to the Sony; or remotely, over wi-fi to your computer. I greatly prefer the latter method, but others prefer the former. You have to do some things differently depending on which method you use - for example with the Telnet/local method you can't remove the USB stick because the USB stick is where the ripped SACD data is going to be written.
• Location and Installation of Sonore app: There's another sacd extract app/executable, that lives on your computer's hard drive. (Some say this executable is included in the Sonore app, but that was not my experience). This app has to be in the same place/directory/folder on your hard drive as the Sonore app is. Also, to use the Sonore app, you need Java installed on your computer. Newer Macs no longer come with Java installed, although I do think they automatically prompt you to install it if it's missing and needed. I don't know what Windows machines do.

So... it is very complicated in terms of the number of issues or factors that COULD cause the process to fail. On the other hand, it is unlikely that you will run into all of these issues, usually only 1, 2, or maybe at worst 3 of them. And they are all easily solved with careful reading and a little trial and error.

[tmtomh]

9 hours ago, diecaster said:

 

Are there any problems if I get a Sony BPD BX510 without a remote?

 

It's a real risk to do that. The machine has only four buttons on it: Disc open/close; Play; Stop; On/Off/Standby. To the best of my knowledge, those buttons cannot be used to call up and navigate the on-screen menus.

 

So without the remote, you cannot use the "toggle the stereo/multichannel SACD setting" method to get the Sony to surrender control of the SACD in order to let the sacd ripping app access the disc. You would have to use the "sleep" method instead. And if the machine came to you with the "quick start" setting disabled, you couldn't use the "sleep" method either, and without the remote you'd have no way to change that setting.

 

Also, without the remote you could not enter the information required to connect the Sony unit to your wi-fi network - so you'd have to use it plugged in to wired ethernet.

Finally, there are certain troubleshooting things that are impossible, or much more difficult, to do without using the remote to navigate the on-screen menus. For example, to see if the machine is labeling the USB stick as sda1 (and not just sda, or sdb1, or ssdc1).

 

The only other option I could think of would be to see if Sony offers a smartphone app that can remote control the player. Even then, however, such apps require the smartphone and player to both be connected to your network (since that's how the app controls the player). So you'd still need to hook up the Sony player via a wired ethernet connection at first.

 

All in all, IMHO it's just better to wait for a cheap deal on a unit with a remote. That's what I did - my BX510 was $30 shipped including remote, manual and original box and packing material. The top of the unit is pretty scratched up, but it works fine. That $30 shipped was, if memory serves, less than $10 more than the cheapest compatible Sony blu-ray player without remote that I found. So if you look around and are a little patient, you can find a unit with a remote for a price premium that is truly tiny compared to the best deal on a remote-less unit.

 

Of course you also could buy a remote separately - they're plentiful on eBay. But they usually run $15 or more, making it cheaper (and much simpler) to just buy a used machine that comes with a remote.

[tmtomh]

1 hour ago, TODDCA said:

 

I'm not actually getting any error.  When i start the SACD.cmd file, it opens a cmd window stays there for 10 -20 seconds and then closes.

 

I'll try the telnet method either tonight or tomorrow and report back.  Thanks, I've never actually used the telnet before.

 

My opinion is that the script is the problem. Dick's universal script is excellent, if that's what you're using - but with my Sony BX510 (aka S590), I couldn't get SACD ripping to work no matter what I tried until a replaced the autoscript with a super bare-bones one that does not include any telnetd (or inetd) commands and only uses the server method. YMMV of course, but if I were you I would try a different autoscript. MikeyFresh has posted links to the simpler 160 script a in the past 5 pages or so of this thread.

[tmtomh]

8 hours ago, TODDCA said:

 

Thanks for this.  Tried it out tonight.  

 

The tray opened automatically.  Once I ran SACD.cmd though everything went non-responsive.  The CMD window stayed open, showed the script line, but no download ever started.  At the Sony player, no buttons would work, not play,eject, power.  I had to unplug it to reset things.

 

I did verify, it was the execution of the SACD.cmd file that caused the player to lock up.  Prior to that, you could still eject the disc etc.. 

 

Thanks, for the continued assistance.

 

 

Sorry it still isn't working - but it seems you are making progress, as the tray has now opened.

 

I do recall that when I was first struggling to get my Sony unit to work for SACD ripping, I did run into a situation where the SACD ripping would start but nothing would happen - and the Sony player also would freeze up, just as you have described.

 

Unfortunately I'm not sure I can help you fix the problem, because as far as I recall, switching to Mikey's bare-bones script is what cured that problem for me.

 

I have a couple of ideas, but I'm not at all sure they are the cause of your problem.

 

One is the mount point/name of the USB stick in the AutoScript.TSS file. The TSS file is the script that triggers the executables that allow you to do the ripping. The first comment in it reads as follows: CLI(CLI_exec cp /mnt/sda1/AutoScript/sacd_extract_160 /)

 

The script assumes the USB drive will be mounted by the Sony as sda1. If you are unplugging and re-plugging the USB stick multiple times during your troubleshooting, and you are not turning the Sony off and back on again in between attempts, then each subsequent time you insert the USB stick into the Sony, the mount point will change - the Sony will label it sdb1 the 2nd time you insert it, sdc1 the third time, and so on. This will break the script. (There's also a chance that the stick is labeled just sda, without the "1", if you have formatted it incorrectly on a Mac - but I take it you're using a Windows machine, yes?)

 

However, in that case, I would expect that the tray would not even open - but it might be worth a try to check it out. Once the tray has opened but BEFORE you try to rip an SACD, navigate the Sony's menus to get to the USB stick and see what the Sony is calling it - if it's not sda1, then that is likely your problem.

 

Second, it is possible that the script is now loading fine, but the Sony machine is still holding on to control of the SACD disc, preventing the ripping app from accessing it. If you have the Sony connected to a monitor, you should be able to fix this by navigating to the menus and toggling the stereo/multichannel setting - do this after you close the tray and the SACD has been loaded, but BEFORE you start ripping. It doesn't matter which one it's set on or which one you change it to - will not impact how the SACD is ripped. It's just a trick to get the Sony to unmount the SACD so the ripping app can grab ahold of it.

The easier method, though, is the "sleep" method. Make sure the Sony is set to "quick start" mode - this will sleep, but not turn off, the machine when you press the power button. They key to the sleep method is that once the tray opens and you put the disc in the tray, you press the Power button, NOT the open/close button. This will close the tray and immediately put the machine to sleep, preventing it from mounting the disc. Because the machine is only asleep, though, it will still be able to be "awakened" by the SACD ripping app.

 

However, while my memory of my troubleshooting details is a little fuzzy, I seem to recall that when I had this problem - script working but Sony wouldn't "let go" of the disc - I would get a "cannot open for reading" error in the SACD ripping app, rather than just nothing at all happening. Nevertheless, my memory could be wrong, so it's worth investigating this.

 

Hope this helps! Let us know if you make any progress or any new discoveries about what might be the problem.

 

Finally, don't give up hope - I had zero problems ripping SACDs with my Oppo BDP-105, and I am pretty computer literate, and yet I still found the Sony quite fiddly and needed help from folks here. The Sony units are a pleasure for SACD ripping once you get it working, but you are not alone in having some difficulty initially.

 

 

 

[tmtomh]

2 hours ago, miksi said:

Thanks for quick answer,

price is 34/42/50 euros for sony models and 42 euro for pioneer plus shipping cost within Serbia (about 4-5 euros).

 

Given those prices I'd say the Pioneer, definitely - easier for SACD ripping and the price is a bargain.

[tmtomh]

1 hour ago, greynolds said:

No.  Ripping Bluray’s can be done pretty easily with a Blu-ray drive connected to a PC and using software such as MakeMKV, AnyDvd HD, etc.  There’s no point in anyone putting any effort into figuring out if it can be done and how with these players that can be used to rip SACDs; it would just be a waste of time since there’s already an easy way to do it.

 

Agree 100% - especially since USB Blu-Ray capable drives are not expensive.

[tmtomh]

11 minutes ago, stof said:

Thank you. I restart from scratch with your method (I never read before that we should have Autoscript folder + AutoscriptSACD!

 

1) : "Power up the Sony BDPS590. OSD should display USB device (front) near the top of the screen"

Regarding my Sony BDP-S4100, I see "Load" then "Home" then "0000"

 

2) : I change the option DSD Multi or DSD 2 channel

3) : telnet via putTTY

sony-player login: root
~ # cd /mnt/sda1/AutoScriptSACD/
-sh: cd: can't cd to /mnt/sda1/AutoScriptSACD/

 

If I check with ping 192.168.1.186 ==> the player is still reachable

 

 

In my experience - both my own direct experience and seeing others' experiences reported here - the most likely problem with a Sony unit is not tenet/IP/networking. Rather, it's a problem with getting the Sony unit to unmount and "give up control" of the SACD so the SACD ripping app can do its thing. This is totally consistent with the problem you are having: You can see the Sony on your network; you can ping it; it's reachable at its IP address - but the actual SACD ripping executable won't work.

 

These are not the symptoms of a network problem, but rather of a problem with not having set up the Sony machine to ensure it doesn't monopolize control of the SACD once the drawer has been closed. You won't be able to rip using the local/telnet method or the remove server method as long as this is the problem.

 

The difficult, manual way to make the Sony "let go" of the SACD is to navigate its menus into the settings and toggle the stereo/multichannel setting. @Phthalocyanine discovered this trick when he first spread the news that the Sony units can do SACD ripping: it doesn't matter if you toggle from stereo to multichannel or the reverse - the act of doing the toggle forces the Sony to unmount the SACD, allowing the ripper to take over.

 

But the easier method is what @MikeyFresh has elaborated earlier this thread: the "sleep" method. Set the Sony to "quick start" mode. Then instead of pressing the eject button to close the disc drawer and load your SACD, press the power button. That will put the machine to sleep, loading the SACD but preventing the machine from taking control of it - therefore allowing the SACD ripping executable to function.

 

I am grateful and filled with respect for those who've helped us be able to rip SACDs. I will say, though, that after a couple of dozen pages of discussion about Sony machine SACD ripping in particular, there's entirely too much discussion of telnet, network issues, and IP address stuff - that's not the major issue with the Sonys. It's the SACD unmounting/control issue, almost every time.