Re: PATCHED Scarletbook-SACD-Extractor
Marq Pargman
FWIW I have put together a few documents with some how-to type information specific to Mac users focusing on the USB media preparation (i.e. formatting) and macOS network tools (e.g. telnet) respectively. It appears that the lion's share of people on this thread are Windows based and consequently important Mac specific details, such as what @JuanDG has pointed out w/r/t formatting the flash drive, are discussed infrequently.
The first document is a somewhat in-depth discussion USB media formatting and includes very detailed macOS based step-by-step instructions, GUI based and command line based and covering a variety of formatting file system and partition scheme options. It also addresses player compatibility (or lack thereof) with the available formatting choices. And finally, it provides an array of NTFS file system solutions and how-to information for Mac users.
Although this document is primarily targeted toward the Mac user audience, it covers media format to player compatibility, which is inherently OS independent, and so there is a fair amount of general information applicable to Windows users as well.
Next up is a guide that touches on Vogon poetry whilst aiming to familiarize the Mac user with some core network tools that are likely to need at some point during their SACD ripping quest. This second document will also provide the macOS based reader with a gazillion options for coping with Apple's recent removal of the native telnet client. This includes but is not limited to a detailed step-by-step procedure for installing Homebrew and from that the Apple telnet client.
An even better option is to upgrade (through burning to an upgrade CD) an intermediate firmware version that works for SACD and which is better than the most recent version in certain ways (i.e. allows for playing of SACD-Rs and does not have Cinavia). The best version for the S590 is M12.R.0430.
I've been a successful user of a Pioneer BPD-80FD for well over a year now (maybe 2). I've had no issues have started to grow a real SACD collection since I found out it was feasible . Am I correct that none of the players this works on are still made? I think I bought one of the last rounds of the 80FD that were still new. The only things I use the player for are ripping SACD's and playing 6 channel rips across the network (I can't get Plex to play mult-channel right).
However, in the back of my mind, nothing electronic lasts forever. The ability to rip SACD's is important enough to me I'm starting to think about picking up another Pioneer or one of the Sony players used just to hold as a backup. Does anyone keep a backup player, just in case?
While I don't know the answer to your original question about any potential work being done to make newer model players compatible with SACD ripping, I definitely keep a back-up player for this very purpose and in fact am now considering adding a Sony for that same purpose.
Like you, I originally bought a new Pioneer BDP-80fd to use as my ripping station, got that unit up and running flawlessly using ISO2DSD on my Mac, and made countless rips with it before getting a little worried about it's ultimate longevity/lifespan. It's not a piece of junk, but I find it's build quality fairly lacking.
I had hoped to buy a new Oppo BDP-103 right at the end of that model's production run, but it was a snooze and lose scenario, when I went to pull the trigger the new units had vanished and the price of used units had climbed to the point I didn't want one unless it was a local sale where I could gauge the condition upfront.
Then I got lucky and found the essentially similar Cambridge CXU on closeout pricing, $799 shipped from Crutchfield, and I jumped on it. A bit more expensive than an Oppo BDP-103 would have been, so not ideal, but worth it in my opinion and now I have much greater peace of mind.
and googling the error brings up various other examples. The explanation about 2064 vs 2048 byte sectors is given here in sacd-ripper issue #80, and as I mentioned previously it was solved long ago by foo_input_sacd which is derived from sacd-ripper. The patch isn't very complicated, but one would need to rebuild sacd_extract_160.
In the page you link to, they are talking about playing songs from and extracting songs from an .iso that has already been ripped. The Foo-bar plug-in plays .isos that have already been ripped. So this does not appear to address a ripping issue. Rather it is an extracting issue from a ripped iso.
I use foobar2000 to play the iso file. The Win 10 PC connects to a Yamaha AV amp by a HDMI cable. Is there any trick to play a 5.1 channel iso? Same problem occurs in the dsf files converted by sonore.
Right, but if you look at the sacd_extract source code this particular error is thrown from a part that is engaged both when ripping a disk and reading an iso file. Either way, iso file or actual disk, the data is arranged in fixed-length sectors and can't be read without knowing the correct sector size. But I agree that until we have an sacd_extract that also tries to read 2064 byte sectors, we won't know for sure whether this is the actual problem.
I'm getting this issue using a "real" sacd as you put it, see above :-). But taking your point beyond a bit further, the fact that there are actual PS3 rips of this title out there could mean that a newer patched version of sacd_extract was used.
As mentioned above, I'm getting this error with the actual columbia sacd disc in a Sony BDP-S590. Other sacds are ripping fine. It could be happening for other reasons, I grant. Speaking of the bdp 160 code, it would be helpful if you could share it so we can have a look. The patch is fairly trivial, but it needs to be compiled for arm6 platform in order to test, so any info on how your version was built would be helpful.
I have shared everything I have, skeptical! I am not the author of this stuff, and don't even rip via this method (I use PS3). I am the OP cuz I was the one who first gave you folks the heads-up on this alternative ripping option (and given my history with documenting PS3 SACD ripping). Nothing more. I have stated this many times, including in the first post (which I try to edit/curate periodically if someone has a new set of steps, etc)
I see that in @ted_b's OP, in the link for the BDP-160 instructions there is an exact reference to the naming convention used as I describe above, I don't know why the version you are using is named differently or what about it could be different and potentially causing you a problem.
Great, and I thank you for it , and it's 99% successful for me! If you didn't actually compile the binary it would be helpful if you could point me to where it was obtained. The main thing is that the github source code is for creating the PS3 binary, and your sacd_extract_160 appears to be a "de-PS3'd" version and it's unclear exactly how that was done. I'm looking for the specific patches/makefiles.
b1e95dc632