Rip SACD with a Blu-ray player

Thanks to Mikey and other contributors for this very helpful thread. I'd picked up a cheap Sony BDP-BX510 from eBay over 2 weeks ago and finally found some time after work yesterday to give this a try. I went for the AutoRip approach as I currently don't have internet or a private LAN set up in my apartment.

Since I was going to be ripping to ISOs and some SACDs can be larger than the 4GB FAT single file limit, I formatted my usb stick to EXFAT (I'm on a MacBook so no NTFS support by default) and placed the AutoRip script folder at the top level. The first issue I ran into was that the BX510 didn't recognize my EXFAT formatted usb stick. Luckily a quick search on the thread showed that my Sony model supports NTFS formatted drives. I installed Microsoft NTFS for Mac by Paragon Software which has a free 10 day trial and that gave me full NTFS functionality. I was then able to format my drive to NTFS. The sony BX510 was then able to recognize the usb stick.

The first Autorip A1 version I tried didn't work with my BX510. However I found a post from Mikey with a link to a newer A1 variant (post #849) and that one worked like a charm. I was able to rip 6 SACDs to my usb stick yesterday and then use SACDExtractGUI on my laptop to extract the multi-channel and stereo dsf files from the ISOs. The whole process was very fast. The first rip took about 21 minutes (with about 1 minute delay before the ripping started after the tray was fully closed). Subsequent rips took about 15 minutes each.

The only disk out of the 6 that I had any problems with was the "Deodato - Prelude & Deodato 2" from Dutton Vocalion. The ISO rip appeared to complete successfully. However, while I had no issues extracting the stereo dsf files using SACDExtractGUI, SACDExtractGUI got stuck on track 10 extracting the multi-channel files. I tried again specifying only track 11 or track 10 in the "select tracks" config with no luck. I'm able to play tracks 10 and 11 on the multi-channel layer using my Oppo blu-ray player so the disc itself is fine.

All in all this is a game changer for me as I can now not only back-up my SACD collection but I can now stream the dsd files from my computer/phone/iPad to my RME-ADI2 DAC which does a much better job than the DAC on my Oppo BDP-83 blu-ray player.
 

MikeyFresh

Moderator
Staff member
Thanks to Mikey and other contributors for this very helpful thread. I'd picked up a cheap Sony BDP-BX510 from eBay over 2 weeks ago and finally found some time after work yesterday to give this a try. I went for the AutoRip approach as I currently don't have internet or a private LAN set up in my apartment.
Welcome to HiFi Haven!
Good deal on that AutoRip success with the BX510, special thanks there again to both @Srx for the A1r2 script revision you used, and also to @Nexus3 for the original A1.

Since I was going to be ripping to ISOs and some SACDs can be larger than the 4GB FAT single file limit, I formatted my usb stick to EXFAT (I'm on a MacBook so no NTFS support by default) and placed the AutoRip script folder at the top level. The first issue I ran into was that the BX510 didn't recognize my EXFAT formatted usb stick. Luckily a quick search on the thread showed that my Sony model supports NTFS formatted drives. I installed Microsoft NTFS for Mac by Paragon Software which has a free 10 day trial and that gave me full NTFS functionality. I was then able to format my drive to NTFS. The sony BX510 was then able to recognize the usb stick.
Yes, NTFS formatting done using the Paragon driver for macOS works perfectly, so well that I actually bought the full-on version of it rather than just use the trial, not inexpensive but I think it will likely come in handy in the future too. NTFS is for certain preferable with AutoRip, and exFAT will not work with a Sony or Pioneer Blu-ray player, only the Oppo units accept exFAT formatted USB drives.

The first rip took about 21 minutes (with about 1 minute delay before the ripping started after the tray was fully closed). Subsequent rips took about 15 minutes each.
Rip time will of course vary by disc according to a number of different factors, however that 1 minute it took for the first rip to start seems too long. It can definitely be 15-20 seconds, however I've never seen anything approaching 1 minute. I wonder if you have seen the BX510 do that every time or not?

All in all this is a game changer for me as I can now not only back-up my SACD collection but I can now stream the dsd files from my computer/phone/iPad to my RME-ADI2 DAC which does a much better job than the DAC on my Oppo BDP-83 blu-ray player.
Game changer indeed, and streaming the files proves to be rather effortless over time, as compared to locating, loading, and playing the disc. Very convenient.
 
Rip time will of course vary by disc according to a number of different factors, however that 1 minute it took for the first rip to start seems too long. It can definitely be 15-20 seconds, however I've never seen anything approaching 1 minute. I wonder if you have seen the BX510 do that every time or not?
Thanks again Mikey. I did a second batch of discs today. Unfortunately I didn't pay attention to the time for the rip to start with this batch. I'll do that with my next batch later this weekend and update the thread.
 
Hello from Switzerland to the international community of SACD lovers and rippers!
Just to encourage you: I bought a new PC this weekend (an hp Pavilion) and just succeeded in configurating it for ripping SACD's.
Other than last time, when I had problems with the right version of the AutoScript files (for those who are interested: see posts no. 948 and onwards), this time my problems consisted in making the Java Runtime Environment (JRE) function properly.
Without going into further details, I can oly say that the valuable experiences shared by other members of this community were of the utmost importance to find the solution.
I am particularly referring to post no. 743. I consulted the link given by AndyT (a great thanks to you!!) and put two solutions into place, meaning the jar fix (solution no. 3, after which the GUI functioned normally) and the .bat solution (solution no. 4), after which the ripping process started normally.
Thank you again for your great help! I sincerely hope that you are ripping your SACD media successfully and that you are finding the time to enjoy all the music that (hopefully) is coming with it.
Kind regards from Switzerland as nighttime approaches in Europe!
Hififan62
 
Last night I was attempting to get the ripping process running. I got the drawer to open on my Sony BDP-S5100, but was unable to rip. SACDExtractGUI could ping the player, but couldn't open the disc. Powered it off and quit for the night. Today when I was getting ready to try it again, the 5100 won't even power on. Unplugged it multiple times, still nothing. Is it bricked? Thanks for any help
--Ed
 

MikeyFresh

Moderator
Staff member
Last night I was attempting to get the ripping process running. I got the drawer to open on my Sony BDP-S5100, but was unable to rip. SACDExtractGUI could ping the player, but couldn't open the disc. Powered it off and quit for the night. Today when I was getting ready to try it again, the 5100 won't even power on. Unplugged it multiple times, still nothing. Is it bricked? Thanks for any help
--Ed

Hi Ed and welcome to HFH-

Nothing about this process has ever bricked anything. The USB thumb drive runs a script, it is not a firmware change or any kind of permanent thing, in that it runs in RAM. So any power cycling of the machine will clear the script because RAM is by design not non-volatile memory. The script isn't saved anywhere on the machine when power is cut, the unit always returns to the standard mode after a full power cycle.

As far as a root cause for why your S5100 will no longer power up, I have no idea except to say go through some troubleshooting and methodically rule out any other power variables on that AC circuit (tripped breaker?) and if those steps don't remedy the situation, then the S5100 might have failed right before your very eyes.
 
Hi Ed and welcome to HFH-

Nothing about this process has ever bricked anything. The USB thumb drive runs a script, it is not a firmware change or any kind of permanent thing, in that it runs in RAM. So any power cycling of the machine will clear the script because RAM is by design not non-volatile memory. The script isn't saved anywhere on the machine when power is cut, the unit always returns to the standard mode after a full power cycle.

As far as a root cause for why your S5100 will no longer power up, I have no idea except to say go through some troubleshooting and methodically rule out any other power variables on that AC circuit (tripped breaker?) and if those steps don't remedy the situation, then the S5100 might have failed right before your very eyes.
Thanks for the welcome and everything you do on the forum...

Yep..probably just its time i guess. It was fine last night, and tonight, nothing. No problems with power, and no surges, here so I guess I'll just chalk it up as a bad player. Time to grab another one.
 

MikeyFresh

Moderator
Staff member
Hello from Switzerland to the international community of SACD lovers and rippers!
Just to encourage you: I bought a new PC this weekend (an hp Pavilion) and just succeeded in configurating it for ripping SACD's.
Other than last time, when I had problems with the right version of the AutoScript files (for those who are interested: see posts no. 948 and onwards), this time my problems consisted in making the Java Runtime Environment (JRE) function properly.
Without going into further details, I can oly say that the valuable experiences shared by other members of this community were of the utmost importance to find the solution.
I am particularly referring to post no. 743. I consulted the link given by AndyT (a great thanks to you!!) and put two solutions into place, meaning the jar fix (solution no. 3, after which the GUI functioned normally) and the .bat solution (solution no. 4), after which the ripping process started normally.
Thank you again for your great help! I sincerely hope that you are ripping your SACD media successfully and that you are finding the time to enjoy all the music that (hopefully) is coming with it.
Kind regards from Switzerland as nighttime approaches in Europe!
Hififan62
Good evening from NY,

Congrats on the new PC and getting it set-up to rip SACD!

Yes that link by @AndyT in Post #742 is huge for any Windows users experiencing trouble launching the application. I think there are only about 3 reports of this over time here which is quite puzzling, I wonder why most (but not all) Windows installs default to the proper behavior in launching the .jar file?
 
Good evening from NY,

Congrats on the new PC and getting it set-up to rip SACD!

Yes that link by @AndyT in Post #742 is huge for any Windows users experiencing trouble launching the application. I think there are only about 3 reports of this over time here which is quite puzzling, I wonder why most (but not all) Windows installs default to the proper behavior in launching the .jar file?
Good morning again from Switzerland.

Yes, you are absolutely right.

The problems I faced came as a really unwelcomed surprise, as my "old" computer accepted the JRE without any problems at all.

In order to have an idea of what I was possibly doing wrong, I doublechecked the Windows version I am running on both machines. They turned out to be exactly the same, at least on the surface.

Even the download by Firefox does not seem to have caused the troubles, as I missed the respective warning on the JRE page on my "old" computer.

So, both the problems and the solutions remain a complete mystery to me.

Notwithstanding this quite unsatisfying situation, I am content that I achieved what I had intended.

MikeyFresh has resumed the complexity of the situation in an absolutely correct way: (too) many variables that potentially can cause troubles.

To be quite sure: Without this forum I would have been at a complete loss. It is thanks to you that I did not get stuck after all.

But the whole process of ripping (and its glitches) can lead you to some almost philosophical questions:
1.) How do deal with the seemingly sometimes "illogical" functioning of your Windows machines?
2.) Would another environment function better or are you content with the situation, as a patch here and there leads to solutions that allow you to exploit your system as intended?

As of today, I have no answers to these question and I will most certainly not have to have to them as the pleasure of listening to some wonderful music will hopefully prevail.

Sorry for the digression...

Enjoy your very days...

Kind regards from Switzerland
Hififan62
 
Hei there,
greetings from Norway.
I have for a couple of years been using the Sony BDPS590 to rip SACDs. Using a Windows 10 server.
I was untill yesterday been using ISO2DSD , but now moved to the SACDExtractGUI.
For the ISO2DSD I used the methode below to get the SACDs ripped and I have needed to continue to use it to make it work.

1. Insert the USB flash drive with the AutoScript folders into the front USB port of Sony BDP S590.
Power up the Sony BDPS590. OSD should display USB device (front) near the top of the screen.
2. Insert SACD. When the disc loads, BDPS590 will go to Play mode, listing the tracks on the SACD.
3. On the Sony remote:
Return button 2X to the Video tab
Left arrow 2X to the Settings tab
Down arrow to Music Settings, Enter
Note: After you rip the first SACD, on subsequent discs, Music Settings will already be selected.
4. Select Super Audio CD Playback Channel, Enter. Change the option (DSD Multi or DSD 2 channel) to the other option. DO NOT EJECT SACD; the disc is now ready to backup.
5. From here the ripping should start nicely from SACDExtractGUI.

Another tip. If the ISO file name uses some letters like õ,ö or others it's not possible to extract the DSF files. Just the ISO file. You would need to change the letters from f.ex ö to o.
 

MikeyFresh

Moderator
Staff member
Hei there,
greetings from Norway.
I have for a couple of years been using the Sony BDPS590 to rip SACDs. Using a Windows 10 server.
I was untill yesterday been using ISO2DSD , but now moved to the SACDExtractGUI.
For the ISO2DSD I used the methode below to get the SACDs ripped and I have needed to continue to use it to make it work.

1. Insert the USB flash drive with the AutoScript folders into the front USB port of Sony BDP S590.
Power up the Sony BDPS590. OSD should display USB device (front) near the top of the screen.
2. Insert SACD. When the disc loads, BDPS590 will go to Play mode, listing the tracks on the SACD.
3. On the Sony remote:
Return button 2X to the Video tab
Left arrow 2X to the Settings tab
Down arrow to Music Settings, Enter
Note: After you rip the first SACD, on subsequent discs, Music Settings will already be selected.
4. Select Super Audio CD Playback Channel, Enter. Change the option (DSD Multi or DSD 2 channel) to the other option. DO NOT EJECT SACD; the disc is now ready to backup.
5. From here the ripping should start nicely from SACDExtractGUI.

Another tip. If the ISO file name uses some letters like õ,ö or others it's not possible to extract the DSF files. Just the ISO file. You would need to change the letters from f.ex ö to o.
Welcome to HiFi Haven, I believe you are the first member from Norway to post in the thread!

So you've chosen to use the "awake-server" method in toggling the stereo/multichannel setting, have you tried the sleep-server method as well?

I ask because it involves far fewer button presses and so is generally favored by the members here, all you need to do is close the disc tray with the OFF button and assuming the unit was already configured for the Quick Start mode, you can then just Run the rip, after that one button (OFF) press.
 
I will try it again, but I think I was not able to connect with the player. That was why I posted how I needed to it. But, will try one more time the Quick Start Mode again :-)
 

MikeyFresh

Moderator
Staff member
I will try it again, but I think I was not able to connect with the player. That was why I posted how I needed to it. But, will try one more time the Quick Start Mode again :-)
Yes with Quick Start enabled, the only other thing you need to do is watch the front panel LED display after pressing OFF to close the disc tray, that display will flash OFF for a few seconds. Once it goes dark, then just Run the rip.
 

MikeyFresh

Moderator
Staff member
Good afternoon, and Happy Labor Day to those of us in the U.S.

Some time ago new scripts were developed that allowed SACD ripping compatibility with a few additional Sony Blu-ray player models: the S790, S6200/BX620, and the S7200. These units utilize an ARMv7 chipset that required a different sacd_extract component in the AutoScript folder.

While that newer ARMv7 AutoScript had been flawless on my S790 using the exact same sleep-server method steps as with the other 2012 Sony models, it was somewhat more finicky in use with the S6200/7200 which are 2014 model year machines. It worked on the S6200/7200, but the sleep-server method was not entirely reliable, and seemed to only grant a short window of opportunity to Run/Execute a rip in the GUI after the disc tray was closed.

More reliable with the S6200/7200 was the awake-server method, but that requires accessing the player's OSD menu in order to toggle the stereo/multichannel setting, hardly convenient when considering it must be done all over again for each and every disc ripped.

I had forgotten about that fussiness largely due to the advent of the AutoRip A3 script, which allowed the S6200/7200 to rip a full ISO directly to the flash drive, merely by placing a disc in the tray when it auto-opened. Too easy and elegant, AutoRip A3 became the standard for use with my S7200 due to being the most convenient option, as my unit is housed in a cabinet one floor down from the router and with no access to Ethernet, it uses WiFi for a network connection. Not exactly ideal for the server method in terms of ripping speed.

But while AutoRip A3 is superior in many ways for use with an S7200, you do then lose certain functionality offered only in the GUI, for instance the Concurrent Mode (ISO+DSF creation in one pass of the optical media). Moreover, there seem to be at least a small amount of SACDs that refuse the AutoRip method for reasons unknown at this time.

Recently I welcomed @TomasN to HiFi Haven, to my knowledge our first member here from the Czech Republic. Tomas had noted a few SACDs he owns simply refuse to rip on his S7200 when using AutoRip A3.

We don't know the exact reasons why these particular discs won't cooperate with the AutoRip process, so Tomas set about revising the original Sony ARMv7 script in hopes he could rip those discs using the sleep-server method instead.

In revising that script, Tomas has not only managed to rip those problem discs that refused all attempts using AutoRip A3, but he has also eradicated the fussiness that the S6200/7200 previously exhibited when using the sleep-server method and the GUI. He did this by combining elements of the existing ARMv7 script with that of the AutoRip A3 script, and the result is a hybrid that behaves not unlike A3, but with the GUI and sleep-server method. The sleep-server steps on the S6200/7200 with this new script are as follows:

1. Ensure the Quick Start mode is enabled in the player's OSD menu settings.
2. With the S6200/7200 in a sleeping/OFF state, insert the USB flash drive.
3. Player wakes, disc tray auto-opens, place a disc in the tray but don't close it.
4. Disc tray auto-closes, player auto-enters sleep mode once display goes dark.
5. Run/Execute the rip from the GUI.


This is a really cool revision to the ARMv7 script for the S6200/7200. The player behavior mimics AutoRip A3 with regard to the automatic operation of the disc tray and sleep mode, however the rip is then run using a GUI over the network. Perhaps most importantly, certain discs that had stubbornly refused ripping via AutoRip A3 seem to have no issues using this revised sleep-server method on the S6200/7200.

I have revised Post # 26 on Page 2 of this thread with the addition of this new S6200/7200 script, and made a corresponding separation/differentiation between it and the original Sony ARMv7 script version which continues to work well on the S790. So for S790 users, continue using that original script and the original sleep-server method steps, while S6200/7200 users should migrate to the newer script using the revised steps outlined directly above in this post.

Special thanks to @TomasN for revising this script to be more easily used and compatible with the S6200/7200 machines, and to @TonK for pointing out problems with the original ARMv7 script in the first place. This was truly an international effort that will help S6200/7200 users in general, but especially if you have any discs that are proving uncooperative with AutoRip A3.
 
Brilliant improvement on S6200! About a quarter way through my stack of SACDs I switched to this method. Not finicky, much faster, no speed degradation, and a very easy change. Many thanks.
 
Hi there! I hope that I can get some help here having just come across this site.

I'm using a Sony BDP S-7200

The thumbdrive has 3 files encased in a root folder called "AutoScript":
- autorip.sh
- AutoScript
- sacd_extract_6200

I'm also using "sacd_extract-WINDOWS-v0.3.9@setmind_git_2018-10-08" for extraction:
- sacd_extract.exe
- SACDExtractGUI.jar
- SACDExtractGUI.properties
- USE_AT_YOUR_OWN_RISK
- version.txt
It also contains 2 sub directories "doc" and "src"

At the moment, I'm able to get a Ping signal and Test signal working, but libsacdread can't open the port for reading... I'm not ready to give up :)

Here's what went on log-wise:

SACDExtractGUI v0.1-5-g97d05f95

Use of this program that results in any form of copyright infringement is strictly prohibited.

[RUNNING][ping, -n, 3, -w, 1, 192.168.0.101]


Pinging 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time=1ms TTL=64
Reply from 192.168.0.101: bytes=32 time=3ms TTL=64
Reply from 192.168.0.101: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.101:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms

[DONE]

[SUCCESS] Port 2002 of 192.168.0.101 is accessible.
[RUNNING][sacd_extract.exe, -i, 192.168.0.101:2002, -s, -z, -2, -o, C:\Users\chiag\Desktop\Playing The Angel (SACD)]


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

[DONE]



Hoping for the best!! :)
 

MikeyFresh

Moderator
Staff member
Hi there! I hope that I can get some help here having just come across this site.

I'm using a Sony BDP S-7200

The thumbdrive has 3 files encased in a root folder called "AutoScript":
- autorip.sh
- AutoScript
- sacd_extract_6200

I'm also using "sacd_extract-WINDOWS-v0.3.9@setmind_git_2018-10-08" for extraction:
- sacd_extract.exe
- SACDExtractGUI.jar
- SACDExtractGUI.properties
- USE_AT_YOUR_OWN_RISK
- version.txt
It also contains 2 sub directories "doc" and "src"

At the moment, I'm able to get a Ping signal and Test signal working, but libsacdread can't open the port for reading... I'm not ready to give up :)

Here's what went on log-wise:

SACDExtractGUI v0.1-5-g97d05f95

Use of this program that results in any form of copyright infringement is strictly prohibited.

[RUNNING][ping, -n, 3, -w, 1, 192.168.0.101]


Pinging 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time=1ms TTL=64
Reply from 192.168.0.101: bytes=32 time=3ms TTL=64
Reply from 192.168.0.101: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.101:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms

[DONE]

[SUCCESS] Port 2002 of 192.168.0.101 is accessible.
[RUNNING][sacd_extract.exe, -i, 192.168.0.101:2002, -s, -z, -2, -o, C:\Users\chiag\Desktop\Playing The Angel (SACD)]


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

[DONE]



Hoping for the best!! :)
Greetings and welcome to HiFi Haven!

Hmm, I'm not entirely sure what is happening there as it seems the program is running and has actually recognized the disc title, or did you create a desktop folder called Playing The Angel that appears in the C drive path?

I guess in order to back up just a bit, your thumb drive has the AutoScript for the S6200/7200 linked to on Page 2 of this thread, correct? I ask because it looks from a file name perspective exactly the same as AutoRip A3, but they are in fact different.

So assuming you are using the new 6200/7200 script and not AutoRip A3, then I'd double check a few things:

1. You have enabled the unit's Quick Start mode in the OSD menus
2. You have inserted the thumb drive into an already sleeping S7200
3. Disc tray auto-opened, place a disc, tray auto-closed, S7200 auto-sleeps (display goes dark)
4. Confirm the IP address assigned to the player has not changed

Assuming all of the above checks out OK, I'd suggest a full power cycle (with the thumb drive removed) by pulling and replacing the power cord. Allow the unit to reboot and initialize, then ensure it is in OFF/sleep status before attempting the above steps again.

Also try the Test button in the server Input field to see if the software thinks Port 2002 is open for business, and confirm the path to sacd_extract is correct in the Program field by using the Browse button.
 
Greetings and welcome to HiFi Haven!

Hmm, I'm not entirely sure what is happening there as it seems the program is running and has actually recognized the disc title, or did you create a desktop folder called Playing The Angel that appears in the C drive path?

I guess in order to back up just a bit, your thumb drive has the AutoScript for the S6200/7200 linked to on Page 2 of this thread, correct? I ask because it looks from a file name perspective exactly the same as AutoRip A3, but they are in fact different.

So assuming you are using the new 6200/7200 script and not AutoRip A3, then I'd double check a few things:

1. You have enabled the unit's Quick Start mode in the OSD menus
2. You have inserted the thumb drive into an already sleeping S7200
3. Disc tray auto-opened, place a disc, tray auto-closed, S7200 auto-sleeps (display goes dark)
4. Confirm the IP address assigned to the player has not changed

Assuming all of the above checks out OK, I'd suggest a full power cycle (with the thumb drive removed) by pulling and replacing the power cord. Allow the unit to reboot and initialize, then ensure it is in OFF/sleep status before attempting the above steps again.

Also try the Test button in the server Input field to see if the software thinks Port 2002 is open for business, and confirm the path to sacd_extract is correct in the Program field by using the Browse button.
Thanks so much MikeyFresh!

Yes, I feel really welcomed here... thanks again so much for your help... I've managed to get the ripping up and running :)

My mistake was inserting the thumb drive while the machine was on.

Inserting the drive while the player was asleep was something new and that really hit the bull's eye! :jump
 

MikeyFresh

Moderator
Staff member
My mistake was inserting the thumb drive while the machine was on.
Inserting the drive while the player was asleep was something new and that really hit the bull's eye!
OK great! Yes the S6200/7200 are unique to the other Sony models in that regard, all of the other Sonys can only accept the AutoScript and then enter sleep mode with the machine already ON, while the S6200/7200 are the opposite, the script gains root access/control only if the thumb drive is inserted into a sleeping machine.

Thanks so much MikeyFresh!
My pleasure and glad you are up and running on the S7200, a very nice ripping platform when using @TomasN 's latest version of the script.
 
Congratulations to @TomasN for this newly developed script for the Sonys S6200 and 7200 and thanks to Mikey Fresh for his quick implementation into the script folders. ( Post # 26 on Page 2 ). Some remarks: upon downloading from this source the script did not function for me on my windows system I had again to change all endings of the script lines from merely LF to CR/LF with the Notepad++ program, including the last line which did not have an ending at all. Secondly, I assume that the autorip.sh is no longer needed because it is only a single line sleep command which is already implemented in the autoscript file ( AUTORIP.SH is not allocated at all ). In my case the ripping was not directly succesful, but it turned out to be a problem with the SACDextractGUI. I assumed that also here one should use sacdextract_6200 .exe, after browsing to the original SACDextract file of the mindset folder it was running perfectly. Really amazing!!!!!!!
I had quite a bunch of SACD which were not accepted in the autoripping sleep method on my S7200, now they were all accepted and ripped.....
 
Top