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

[mikegee2]

My thanks to Phtalocyanine and Mindset for getting me straight. I have read the entire thread, but as a newbie at ripping, I became confused when some posts talked about Sonore in one reply and the command line in the next. I look forward to trying this over the holidays.

 

Again, my thanks!!

MIkeGee

[Deyorew]

So I’ve encountered an issue. Elton john self titled ripped fine to iso. Extracted 2 channel iso to dsf fine. When extracting the multichannel dsf, it gets to track 5 then stops at 33%. I tried 3 times and it stops in the same place every time. Anyone know about this issue?

[Phthalocyanine]

1 hour ago, Deyorew said:

it gets to track 5 then stops at 33%

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.

[Deyorew]

Iso is only 2gb. I tried dsf and dff. No luck. Still freezes on track 5 at 33%. 

 

I will try ripping the disc again maybe? 2ch extraction worked. Just no multi.

 

anyone else rip and extract the multichannel layer of Elton John self titled without issues?

[mindset]

2 hours ago, Deyorew said:

Iso is only 2gb. I tried dsf and dff. No luck. Still freezes on track 5 at 33%. 

 

I will try ripping the disc again maybe? 2ch extraction worked. Just no multi.

 

anyone else rip and extract the multichannel layer of Elton John self titled without issues?

SACDs are normally organized in the order of TOC, 2ch audio, and multi-channel audio.  Most of the 2ch + multi-channel SACDs I own are larger than 2GB, so if your .iso is 2 GB in size, your .iso could have been ripped incompletely as @Phthalocyanine mentioned. 

 

I am not sure if you bother to do this, but there is a way to to tell how big roughly the .iso is supposed be based on the data in the TOC. I have tested this only on Linux.

LOG_MODULES=all:4 LOG_FILE=test.log sacd_extract -i test.iso -s -m

This will write a debug log to test.log.    You can terminate this with CTRL+C once dsf extraction starts.  Around the head of test.log, you can find the offset and size of each track like this:

[0]: Queuing: Elisabeth Leonskaja - Johannes Brahms (1833-1897) Klavierwerke (1)/20
- Elisabeth Leonskaja - Klavierstücke op. 119 - Rhapsodie. Allegro risoluto.dsf,
area: 1, track 19, start_lsn: 2065132, length_lsn: 100616, dst_encoded_import: 1,
dsd_encoded_export: 1

This is the last multi-channel track of the disc, and its offset is 2065132 and length is 100616 so the tail of this last track is 2065132+100616=2165748.  Since each sector is 2048 bytes in size, the approximate .iso size is 2048 * 2165748 = 4.13 GB

 

[Phthalocyanine]

10 hours ago, Deyorew said:

Iso is only 2gb

Please tell us more about how you are ripping -- what player?  What method? (server? local ripping to USB?)

[Deyorew]

I use the Sony s390. Sonore on a Mac. Telnet /wireless. I have ripped about 30 discs no problem. The other Elton John titles ripped and extracted fine in multichannel 

[Phthalocyanine]

13 minutes ago, Deyorew said:

The other Elton John titles ripped and extracted fine in multichannel 

And their .iso sizes are much bigger than 2GB right?

Have you tried re-ripping this disc?

[Deyorew]

You’re right. The other EJ titles were 3.5-4.5gb so I need to try re ripping.

[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.

[Deyorew]

I wasn’t sure how to switch to server method. Just adjust the sacd extract file? I tried doing wired before wireless and could never get it to work. 

 

Re ripping the file and it should have been 3.4gb so I didn’t have a good rip. Thanks for all your help guys. I’m still newb status with this.

[Phthalocyanine]

4 hours ago, Deyorew said:

I use the Sony s390. Sonore on a Mac. Telnet /wireless

 

1 hour ago, Deyorew said:

I wasn’t sure how to switch to server method. Just adjust the sacd extract file? I tried doing wired before wireless and could never get it to work. 

If you're using Sonore on a Mac you are using a variant of the "server" method.  It's just ripping via a network connection, wired or wireless doesn't matter.

[Phthalocyanine]

2 hours ago, tmtomh said:

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

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

[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.

[bbosler]

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

[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.

[Nevermore]

20 minutes ago, tmtomh said:

 

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.

 

Excellent post! This would have saved me from joining the site, had it been posted earlier.

[MikeyFresh]

I've been ripping successfully on a Mac using ISO2DSD for a couple of years now, but recently I also got a Lenovo Windows 10 machine and want to try it too.

 

I noticed on the Sonore web page that they don't list Java as a requirement for ISO2DSD under the Windows instructions, but they do list that requirement for both Mac and Linux.

 

Does anyone know if Java is not actually required to run ISO2DSD using Windows, or is that just an error of omission on the Sonore web page Windows instructions?

 

 

[One and a half]

1 hour ago, MikeyFresh said:

I've been ripping successfully on a Mac using ISO2DSD for a couple of years now, but recently I also got a Lenovo Windows 10 machine and want to try it too.

 

I noticed on the Sonore web page that they don't list Java as a requirement for ISO2DSD under the Windows instructions, but they do list that requirement for both Mac and Linux.

 

Does anyone know if Java is not actually required to run ISO2DSD using Windows, or is that just an error of omission on the Sonore web page Windows instructions?

 

 

Well, there’s no real update to the Sonore app, so java is still needed, there’s a prompt anyway during the Install to download if java is not there.

[diecaster]

7 hours ago, tmtomh said:

 

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.

 

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

[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.

[Phthalocyanine]

@diecaster

@tmtomh is right.  You really need a remote to make ripping work.

The Sony BD remotes are entirely interchangeable for the 2012-2013 models, the ones that do the SACD ripping.

My Sony RMT-B118A remote works for my S390, S590, and S1100 (not a ripping model but the same year line as the S5100.)

I looked on Ebay and this remote is going for as low at $5 with free shipping.

So getting a cheap separate remote is a real possibility.

As an even cheaper alternative, almost any cheap universal remote (one of which you may already have) should have the Sony codes (since they are such a major manufacturer).  But if you don't have a universal remote lying around, I would go with a cheap Sony replacement model on Ebay as discussed above.

[bbosler]

tmtomh , thanks, i finally got it going. I did not have the 160 files and it was not in quick start. I am ripping away, thank you, thank you, thank you

[MikeyFresh]

22 hours ago, bbosler said:

I can't (won't) scroll through 135 pages trying to find what is the right way for my player.

 

29 minutes ago, bbosler said:

tmtomh , thanks, i finally got it going. I did not have the 160 files and it was not in quick start. I am ripping away, thank you, thank you, thank you

 

@tmtomh's post was both very comprehensive, and valuable to this thread, for you and for any others that might be lurking or become new members at some point wishing to rip SACDs with a Sony Blu-ray player.

 

However it should be noted that your stance of "can't/won't scroll through 135 pages" was both a little bit disrespectful to the many who have contributed to this thread to get it this point, as well as plain old lazy. The information you were seeking was on page 132, that's just 3 pages back.

 

I say this so that any new readers of this thread will know that finding information in it isn't quite as daunting or impossible as some might make it out to be.

[bbosler]

Mikey, thank you for pointing out that I only had to scroll through the first 132 pages to find the answer and not the entire 135.  Even if it is only 3 pages back it didn't seem to make much sense to start at the end and go backwards. That said, I did go through a bunch of it and found many conflicting posts about how to go about doing this with various methods, numerous caveats about different machines, various places to find files, as well as posts telling me what had been posted earlier was incorrect and they had another way to do it. At that point I asked for help which was graciously provided. That was greatly appreciated. Getting scolded for asking for that help serves no useful purpose. I also disagree with your assertion that it is not a daunting task. Given that there are now 135 pages of posts with people continuing  to struggle clearly points out that it is not a simple matter. Another HUGE thanks to the people who offered constructive advice.