Good afternoon Paul and welcome to HFH!Hello to all!
I've been reading through this thread, and by following the excellent directions and refinements provided by many members, have been successful in ripping about 15 SACDs thus far. And a big thanks to @MikeyFresh for moderating and keeping this thing rolling!
All that said, I've hit a snag when I try to use the recommended SACDExtractGUI program. I can get it to work fine with the Sonore ISO2DSD, though -- stereo rips run about 6-7 minutes/disk. Playback via Roon has been effortless. Here's my rip system:
* 2012 MacPro running Mojave (10.14.6)
* Sony BDP-S590 ($40 delivered on eBay this week; $10 Amazon remote) via wireless network (I can't get it to connect via wired - known good cable and connection, too. Oh well...)
* Old 2GB SanDisk Cruzer USB
* The sacd_extract-MACOS-v0.3.9@setmind_git_2019-03-21.zip which was referenced in this thread, downloaded a couple days ago. I did make the sacd_extract executable, as shows in the screenshot.
I do the steps to get the Sony blu-ray player ready - again, I've had consistent success with the ISO2DSD program.
The SACDExtractGUI app fires up, and I can:
1) Test the app;
2) Ping the disk player;
3) Check the port;
4) Set a download directory;
5) Initiate a program run.
As you see from the screenshot, all are successful, but the program itself stops and starts instantly. Anyone got any ideas?
View attachment 28082
Cheers,
Paul
Good afternoon and welcome to HFH!Hello SACD Ripping Community !
I'll Get very soon a brand new Sony BDP-X700 (BLU-RAY Player)
This reader is provided with :
- an ethernet connection,
- a USB Key connection,
- and reads SA-CD discs.
If I'am right nobody so far made any test with this machine. So, How can I know wether this Machine is SACD RIP-Compatible or not ?
Thanks in advance.
Patrick.
How you know it is a known good connection? The device that you plug the other end of the cable into, does it have lights to indicate the negotiated ethernet speed? You don't say if you are using DHCP, or static IP, or tried both. If you haven't tried using a static IP, I suggest doing so. IMHO, going wired is better than WiFi.* Sony BDP-S590 ($40 delivered on eBay this week; $10 Amazon remote) via wireless network (I can't get it to connect via wired - known good cable and connection, too. Oh well...)
Good afternoon Paul and welcome to HFH!
Based on your screenshot it looks like all you need to do is re-specify the exact path to sacd_extract in the Program field using the Browse button (overwrite what is currently in that field).
I said known good cable and "connection" meaning that other devices plugged into that cable, which hasn't been removed from the switch wired to the firewall, and they find the DHCP server just fine, and have full gig connectivity (in no particular order - a Mac laptop, RPis 2/3/4, a Win10 box, an Ubuntu 18/20.) This Sony unit doesn't appear to have a connection light on it. It worked first try on wifi, connecting to the otherwise same network - it's just a flat 192.168.1.x/24. I'm enough old-school to want everything wired pretty much always (and balanced connectors, too) but when the wifi worked, I moved on to the interesting problem of getting my rips going. I'll keep fooling around with this part, too.How you know it is a known good connection? The device that you plug the other end of the cable into, does it have lights to indicate the negotiated ethernet speed? You don't say if you are using DHCP, or static IP, or tried both. If you haven't tried using a static IP, I suggest doing so. IMHO, going wired is better than WiFi.
I said known good cable and "connection" meaning that other devices plugged into that cable, which hasn't been removed from the switch wired to the firewall, and they find the DHCP server just fine, and have full gig connectivity (in no particular order - a Mac laptop, RPis 2/3/4, a Win10 box, an Ubuntu 18/20.) This Sony unit doesn't appear to have a connection light on it. It worked first try on wifi, connecting to the otherwise same network - it's just a flat 192.168.1.x/24. I'm enough old-school to want everything wired pretty much always (and balanced connectors, too) but when the wifi worked, I moved on to the interesting problem of getting my rips going. I'll keep fooling around with this part, too.
You don't say if you are using DHCP, or static IP, or tried both. If you haven't tried using a static IP, I suggest doing so. IMHO, going wired is better than WiFi.
Thanks for the quick response, Mikey! I thought it was kind of weird that it seemed to start and immediately finish, but maybe it's just a lack of error message that I interpreted as success. I'll give it a shot and report back here.
But the switch the player is connected to should. Does it light up?This Sony unit doesn't appear to have a connection light on it.
That is great assumption and exactly how it works for me under my Fedora Linux. IIRC, even the instructions say to start the GUI in the same place the ripper program is placed. So, why it isn't working for you is beyond me.I'd assumed that since sacd_extract was sitting in the same directory I'd kicked off the GUI from, it'd find it.
Here was my initial process:For that I'd suggest maybe the process in setting up a wired connection in the S590's settings menu did not complete? You do have to set it up for a wired connection just as you need to set up a wireless connection. You have to see that through to the last screen and let it complete.
For the record and for any newbies or lurkers, while I agree that Ethernet is better for ripping SACD becuase it is not prone to interference and is somewhat faster, that doesn't mean that use of WiFi is some big problem, or that a static IP is ever required.
So long as the distance to the router is reasonable, and there are no sources of 2.4GHz interference, WiFi works just fine for ripping and is only a little bit slower. DHCP works fine with these Blu-ray players, there is no need for a static IP, you of course can use one if you like but it is absolutely not a requirement and in my opinion adds unnecessary steps and complexity to the set-up. I am not arguing anyone, but I am setting the record straight, WiFi works, and a static IP is not a requirement.
Yes, when I first did it, I opened a terminal window, made my way to the correct directory, and kicked off SACDExtractGUI by invoking Java on the .jar, with appropriate switches. Had already done the chmod +x on sacd_extract, which was sitting "next to" the .jar in the directory. Using ISO2DSD, it worked as expected. SACDExtractGUI had to have the sacd_extract fully qualified to invoke it correctly. (Though the good news was that doing that allowed me to use an even more up to date build.)That is great assumption and exactly how it works for me under my Fedora Linux. IIRC, even the instructions say to start the GUI in the same place the ripper program is placed. So, why it isn't working for you is beyond me.
Though, I do have to ask... were you actually in the directory when you started the GUI, or pointed to the GUI program from another location? I actually start the GUI from within the directory where all of the files are located.
What happens if you skip the manual setup and just use Wired Setup -> Auto -> Save & Connect?7) On Manual, select "Custom" setup, then "Auto" for IP address; "Auto" for DNS; and "No" for Proxy Server
Hi all
I picked up a very good Sony S5100 locally when I found my 6700 didn't work and it's quite amazing.
Used A1neo AutoRip.
So far though, out of 3 discs, 2 failed without explanation. The first one (Pentatone) appeared to complete, but there was no ISO. When I retry them, the player just spits them out again.
I couldn't see any incomplete ISO files on the drive.
Anybody encounter this? Any suggestions? (tried to search the thread but couldn't find a phrase that returned anything.)
Thanks
Phil
Thanks for the tip.Yes for some discs, typically classical music with so-called special characters in the metadata, AutoRip fails.
For those discs you need to use the network player as server method.
There is an even newer build available than .71, please see Post # 1937 and click the spoiler for The Software, there you will find a link to the .88 version of the executable for macOS.Though the good news was that doing that allowed me to use an even more up to date build.)