Rip SACD with a Blu-ray player

[MikeyFresh]

Where I am running into problems, is that first - my pc does not allow me to format my USB FAT 32, only exFAT or NTFS.

OK, so you are using Windows then. You can use NTFS formatting with a Sony, but you cannot use exFAT, that only works on an Oppo player.

The USB flash drive does not typically need to be reformatted. They usually ship from the factory as FAT32 unless it is a very high capacity drive, in which case it sometimes ships exFAT from the factory. If you did not already reformat the drive, don't, it's probably already FAT32 unless 64GB or larger, and even then, it's still likely FAT32 fresh out of the package.

Can you post a screenshot of the folder structure on the USB flash drive?

 

[Oneslip17]

 

[MikeyFresh]

You need an outer enclosing folder called AutoScript housing those 3 items pictured.

Create a new folder on that drive, call it AutoScript, and put those 3 items you have there in it.

That takes care of the USB flash drive.

Then do the following steps (specific to the S6200/7200 models ONLY):

Specify the exact path to sacd_extract in the Program field using the Browse button.

Enable the S6200's Quick Start setting in it's on-screen displayed Settings menu.

Fully power cycle the S6200 and allow it to boot. Display eventually goes dark once initial boot sequence is done. The unit is now sleeping.

Insert the USB flash drive into an already sleeping (OFF state) S6200.

Allow the disc tray to auto-open, place a disc in the tray, then let it auto-close.

Wait for the display to cease flashing OFF, unit is now sleeping, then Run the rip.

That is the exact sequence necessary to rip with the S6200/7200 (it differs from all other Sony models).

 

[Oneslip17]

I have added the autoscript folder with all documents to the thumb drive.

I have enabled the quick start setting in the menu

Where I think I might be going wrong is in the powering on/off inserting USB sequence for the player. I cant seem to get the unit to "sleep". I'm going to try and follow each step once again to see if I can figure out where I am going wrong.

EDIT: I retried all steps and I still keep getting the same error. I've attached the screenshot below:



Thanks again for all your help.

 

[Oneslip17]

I got it to work, well kind of. It seems it was just the disc that wasn't wanting to rip. So I tried a different disc and it seems to work now. The only issue, is that the speed is like .5mb/s . VERY slow. I know my upload/download speed is capable of much better... Any ideas?

 

[MikeyFresh]

I got it to work, well kind of. It seems it was just the disc that wasn't wanting to rip. So I tried a different disc and it seems to work now. The only issue, is that the speed is like .5mb/s . VERY slow. I know my upload/download speed is capable of much better... Any ideas?

OK good, that's progress and the method is working, just slowly.

The up/download speeds are irrelevant in this application as there is no physical connection to the internet or your ISP going on at all, this is local network traffic.

A wired Ethernet (LAN) is your best option there and should yield speeds between 2.5-3MB/sec. on most discs. WiFi (WLAN) will be slower, but not super slow like you are reporting unless the player is physically very far away from your router, or there is considerable radio frequency interference of some sort, or the router is inundated with other heavy traffic such as streaming HD video, Xbox, etc... those are local network variables.

Can you try connecting via Ethernet?

 

[Oneslip17]

I could try with Ethernet, but it is not really the most convenient way to do it, because of how the house is set up. But I could give it a try. Is there a special kind of Ethernet cable that I need to plug into my router?

 

[MikeyFresh]

I could try with Ethernet, but it is not really the most convenient way to do it, because of how the house is set up. But I could give it a try. Is there a special kind of Ethernet cable that I need to plug into my router?

Nope, any Cat5 or better Ethernet cable will work about the same, with perhaps slightly better rip speed using Cat5e and above possible. I use Cat6a, but not for any reason other than to somewhat future proof it, and Cat5e is still current too. But regular old Cat5, while it certainly works, is now just a bit dated in terms of spec.

If WiFi is far more convenient, then arrange the player so that it is physically closer to the router, without sources of interference right nearby. WiFi should not be that much slower than Ethernet, you should still be able to get 2-2.5MB/sec. via WiFi but the speed is dependent on the physical distance to the router, and the elimination of any sources of radio frequency interference.

 

[Oneslip17]

Nope, any Cat5 or better Ethernet cable will work about the same, with perhaps slightly better rip speed using Cat5e and above possible. I use Cat6a, but not for any reason other than to somewhat future proof it, and Cat5e is still current too. But regular old Cat5, while it certainly works, is now just a bit dated in terms of spec.

If WiFi is far more convenient, then arrange the player so that it is physically closer to the router, without sources of interference right nearby. WiFi should not be that much slower the Ethernet, you should still be able to get 2-2.5MB/sec. via WiFi but the speed is dependent on physical distance to the router and the elimination of any sources of interference.

Brilliant, I'll give that a shot. Thanks again for all your help. This will help me pass some time during isolation.

 

[NSBulk]

I found significantly faster and consistent speeds with ethernet vs. wi-fi and I have good wi-fi. It just meant the player had to be in the other room. Have fun!

 

[MikeyFresh]

Brilliant, I'll give that a shot. Thanks again for all your help. This will help me pass some time during isolation.

My pleasure, glad the steps posted worked well for you, and you can make some SACD ripping progress while passing the time during shelter in place!

 

[jamisonia]

Just got the BX10 replacement drive in today, it was easy to swap the drive and I'm ripping SACDs as we speak. I didn't even bother to put the cover back onto the BDP.

Oneslip, from what I can tell it looks like there is an issue with your network connection. Its not connecting for some reason to that BD player. That's also a weird IP address. Its usually 192.168.1.XX with the XX being unique to each device on your network. I'd double check that both on your router's software and on the BD player itself.

 

[MikeyFresh]

Just got the BX10 Drive in today, it was easy to swap the drive and I'm ripping SACDs as we speak. I didn't even bother to put the cover back onto the BDP.

Outstanding, that's great news and a fast turnaround on the part. Did you use the same seller/listing for the part that I did, or did you find someone more nearby you that had it?

Oneslip, from what I can tell it looks like there is an issue with your network connection. Its not connecting for some reason to that BD player. That's also a weird IP address. Its usually 192.168.1.XX with the XX being unique to each device on your network. I'd double check that both on your router's software and on the BD player itself.

Oneslip got it going after all, however the rip speed is a problem so he might switch from WiFi to Ethernet.

 

[Oneslip17]

Yes, I did get it going. A big thanks to everyone who helped. I was able to re-position my BDP-6200 closer to my router and now I am pulling speeds of about 1.5mb/s. Which is way better than before. Thanks again to everyone who helped me with this project. It is truly appreciated. Cheers!

 

[jamisonia]

So I'm having an issue with only one SACD. I've tried ripping this SACD about 4 times. I'm able to get the ISO, but only 1 track. Even when I try to pull the files directly from the ISO it only grabs one track. I've cleaned the SACD, and it doesn't appear to have any scratches (honestly it might be one of my better condition ones). Included a capture of what I'm seeing. There are 7 tracks on the SACD.

 

[jamisonia]

Outstanding, that's great news and a fast turnaround on the part. Did you use the same seller/listing for the part that I did, or did you find someone more nearby you that had it?

I got it from someone different on ebay. I had decided to take a risk on the BX10 before you linked me that seller, but their listings seemed almost identical. Worked out great. Honestly I almost think it might have worked out better to start out with a brand new drive.

 

[MikeyFresh]

So I'm having an issue with only one SACD. I've tried ripping this SACD about 4 times. I'm able to get the ISO, but only 1 track. Even when I try to pull the files directly from the ISO it only grabs one track. I've cleaned the SACD, and it doesn't appear to have any scratches (honestly it might be one of my better condition ones). Included a capture of what I'm seeing. There are 7 tracks on the SACD.

View attachment 22516

No doubt an excessive file path length issue, too much meta data authored into the disc, it can't exceed 260 characters (including spaces) for any given track.

To take your best shot, shorten the write path in the following way. Name a USB storage device literally one character, maybe R for rips, or S for SACD, but the point is the name of that drive is just one character.

Designate it as the Output Directory, and don't put another folder inside of it, just allow the files themselves to be written directly to that drive that has a one letter name. This gives you the most remaining characters with which to fit all of the metadata that is authored onto the disc into the file path name, and which you cannot truncate prior to the rip.

Right now your ISO path is this: C:\users\jamisonia\desktop\sacd, which is 31 characters eaten up out of the 260 total available before the program bombs.

If you shorten that to a single character, i.e. the name of the drive and nothing else, you might just have enough leftover characters remaining to fit the stupid excessive metadata string they chose to author that disc with within the 260 character path name limit. So the Windows file path would be something like this:

D:\R (for "rips") or maybe E:\S (for "SACD")... something like that is your best shot at then fitting the remaining meta data string within a 260 character total limit.

Ditto the DSF file path, it's only one character shorter than that of the ISO, so write the DSF tracks to that very same single character USB drive name, to give yourself the best shot.

If that doesn't work, I might also have one other option.

PS - maybe to simplify upfront, try just the DSF extraction, don't create an ISO, just so that you'll know if it bombs again sooner than you would if also writing the ISO concurrently.

 

[jamisonia]

No doubt an excessive file path length issue, too much meta data authored into the disc, it can't exceed 260 characters (including spaces) for any given track.

To take your best shot, shorten the write path in the following way. Name a USB storage device literally one character, maybe R for rips, or S for SACD, but the point is the name of that drive is just one character.

Designate it as the Output Directory, and don't put another folder inside of it, just allow the files themselves to be written directly to that drive that has a one letter name. This gives you the most remaining characters with which to fit all of the metadata that is authored onto the disc into the file path name, and which you cannot truncate prior to the rip.

Right now your ISO path is this: C:\users\jamisonia\desktop\sacd, which is 31 characters eaten up out of the 260 total available before the program bombs.

If you shorten that to a single character, i.e. the name of the drive and nothing else, you might just have enough leftover characters remaining to fit the stupid excessive metadata string they chose to author that disc with within the 260 character path name limit. So the Windows file path would be something like this:

D:\R or maybe E:\S... something like that is your best shot at then fitting the remaining meta data string within a 260 character total limit.

Ditto the DSF file path, it's only one character shorter than that of the ISO, so write the DSF tracks to that very same single character USB drive name, to give yourself the best shot.

If that doesn't work, I might also have one other option.

PS - maybe to simplify upfront, try just the DSF extraction, don't create an ISO, just so that you'll know if it bombs again sooner than you would if also writing the ISO concurrently.

This fixed it. Thanks so much. I have now ripped all of my SACDs. I didn't have a whole lot, but its nice to have them all backed up. I've successfully backed up just about every movie and music on spinning discs I have. Only HD DVD left to go. 2 8TB HDD's later....

Thanks for all of your help MikeyFresh

 

[MikeyFresh]

This fixed it. Thanks so much. I have now ripped all of my SACDs. I didn't have a whole lot, but its nice to have them all backed up. I've successfully backed up just about every movie and music on spinning discs I have. Only HD DVD left to go. 2 8TB HDD's later....

Thanks for all of your help MikeyFresh

Good deal, it's my pleasure and I'm glad you now have all of your SACDs ripped. Perhaps now you, just as many other members here have commented, would be much more disposed to buy additional SACDs down the road, knowing that you can easily rip them.

I'm also pleased that S5100 optical drive swap out repair went smoothly, congrats on that, I was wondering when we'd have another member here end up with a unit in need of repair. These machines are now old, but as you said, perhaps this is really best in the end, that replacement part is cheap and you now start over with a new optical drive as opposed to one with unknown amounts of previous mileage on it. Go ahead and put her bonnet back on, she's all good to go.

Cheers!

 

[1likeh1f1]

Dear MikeyFresh, thank you for this thread. It is a treasure found! I'm not a forum user, so please bear with me on this posting (hope I'm completing it correctly).

I am now setting up to rip my SACD's using your guidance in the "Rip SACD with a Blu-ray player" thread. As an unsophisticated user, I'm attempting to follow your instructions explicitly so that I don't run into problems.

Tonight, I ordered a Sony BDP-S5100 player ("Sony Player")and intend to use it to rip my SACD's via my laptop (Win 7 Pro 64 bit OS, I'll call "My Laptop") using sacd_extract-WINDOWS-v0.3.9@setmind_git_2018-10-08.zip (1.1 MB) as you recommend.

I will use it via Ethernet connection to my LAN and I understand that I only need to look up the IP address assigned to the Sony Player and insert it into the SACD extraction application via its GUI. I will also configure the GUI only for two-channel ripping, even though I do have some multi-channel SACD's as I only intend to capture the DSD from the SACD into .dsf files (rather than mess with ISO information), as you have previously suggested. I'll use the SACD itself as a physical archive (as I'm doing with my CDs).

I'm using Roon Core on a dedicated music server running Windows 10 Pro 64 bit and I'll move my .dsf files to it from My Laptop. My T+A DAC plays DSD directly (i.e., no PCM conversion). So, I only need to derive the .dsf files for my two-channel audio system.

I am first setting up a Sony USB 2.0 2GB thumb drive ("Thumb Drive"):
(1) I wiped it. Then ensured it is formatted to FAT32 (there is no option to specify the partition scheme as "Master Boot Record"; so I left it as the "Default" partition setting. Please let me know if I've missed something there (using Windows 7 64 bit OS).
(2) I sought to install at the root level the AutoScript that you specified on page 2 of the thread. Link follows: AutoScript
There is a zipped folder, per se, and there are three individual files in the folder: AutoScript, AutoScript.TSS and sacd_extract_160. But each time I attempt to open the folder (not each individual file), I have to click through the attached error message.

Queries:
Thumb Drive -
Why am I obtaining this message with the folder from the link?
Is this going to have any bearing on the ability of the Sony Player to access and utilize the routines contained on the Thumb Drive?
Also, is the zipped folder OK? (I just unzipped it after moving it to the Thumb Drive and the folder and the three files all seem to be sitting there looking pretty, Read-only" as "H:\AutoScript"; sorry for my overall naivety - I've just read your posts where you emphasize not messing with the AutoScript folder at all...I want to resolve any issues with the Thumb Drive as I wait to receive the Sony Player and would appreciate your kind assistance to ensure that the routines will run properly on the Sony Player once I receive it.)

Sony Player -
Will there be any distinction inserting the Thumb Drive I've now set up in the front port versus the rear port on the Sony Player?
I've seen many posts in this thread regarding firmware on the players; do I care at the outset? (i.e., if the device arrives and works, then I leave the firmware alone. Or, do you have a target firmware version range that the version on the device I receive should neither predate or succeed?) I would also appreciate your guidance on any settings I should make on this specific Sony Player as I will only be using it for this SACD ripping - nothing else (I see post 69 - is there anything else for this particular model that you've discovered since?).

My Laptop -
Regarding the sacd_extract-WINDOWS-v0.3.9@setmind_git_2018-10-08.zip (1.1 MB) to be installed and run on My Laptop, I have the zipped file now in my Downloads. Perhaps a silly question: do you have any recommended file path for the unzipped folder? I also want to confirm with you that I should launch and use the "SACDExtractGUI.jar" file rather than the "sacd_extract.exe" application file.

Also on My Laptop, I just installed Java, but I'm reading that Google Chrome doesn't support it. As that is my default browser, do I care w/r/t this endeavor? (If so, I'll probably use Explorer - but it's pretty tin-canny and I'd rather not unless necessary).

I'm working my way through the thread best I can...

Thank you so much in advance.