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

[MikeyFresh]

10 hours ago, Phthalocyanine said:

In other words, the secret sauce may be in a separate chip or circuit board not the common Sony BD optical unit.

 

Thus I very likely will have to disassemble the replacement part I have, extract the laser pick-up assembly portion, and transplant it into the existing drive mechanism, assuming the new part is fully swappable with the existing.

 

Also assuming that's the only thing wrong with it in the first place, apparently the laser can be rendered inoperable by a bad electrolytic capacitor in the power supply, which is easy to see and fix. I'm very much hoping it is something stupid easy like that and I don't have to take apart the disc drive at all.

[MikeyFresh]

10 hours ago, mindset said:

Here is what I got from players I have:

 

BDP-S390: MT8551KAAG

BDP-S590: MT8560EAAG

BDP-S1100: MT8552DAAU

BDP-S5100: MT8560EAAG

BDP-S6200: MT8580DJAG

BDP-S6500: MT8580DJAG

BDP-S6700: MT8580DJAG

 

So that right there is actual proof this exploit is not necessarily limited to machines with the MT8560 and 8580 SoC then, no?

[MikeyFresh]

1 hour ago, loadam59 said:

No problem to rip in local mode.

 

Have you had any luck with the 6200 script and the Pioneer LX58?

 

Or can you make the LX58 report on itself?

[MikeyFresh]

On 3/1/2019 at 10:04 PM, Phthalocyanine said:

I'll be very interested in your replacing the optical drive in the Sony you just got.

I've never done it.

The stuff I see in the service manuals (like this from the S590 Service Manual) has somewhat scared me because it shows typical Sony hyper-security lockdowns.

 

Turns out the hardest part in replacing a dead BPX-7 optical drive in an S7200 is the simultaneous release of the 6 plastic retainer clips that hold the chassis cover on.

 

Once that stubborn hurdle is cleared, the actual optical drive replacement involves 4 Philips head mounting screws and 3 ribbon cables. Thats all, it works fine now, reads and plays CD, SACD, DVD, and Blu-ray discs with the $12.99 BPX-10 replacement part.

 

The dead BPX-7 drive would sound as if it was reading the TOC, but would always then display "No disc" on the front panel. It wouldn't even read the TOC of a regular CD or any other disc.

 

The only complication so far is purely cosmetic, I'm not sure how to remove the piece at the very front of the tray that the tray fascia attaches to. You have to remove that fascia to get the drive out, but the BPX-7 has some additional piece that looks like it mounts with foam tape, and that is what the tray fascia mounts to. Seeing as this $9.99 gem was already fairly beat up, I'm not sure I care much. But if it starts to bother me I may see about disassembling the BPX-7 to use it's entire tray piece, or try to pry off the bit I need and then use new foam tape to adhere it to the front of the BPX-10 tray.

 

As for SACD rips, I can only get the awake-server method with the stereo/multichannel toggle to work, so far @mindset's S6200 sleep version with insertion of the AutoScript AFTER sleeping the machine will not work for me on the S7200, I don't know why.

[MikeyFresh]

6 hours ago, lardee said:

The SACD is a US release of a Decca album, all mainstream so I doubt non-latin characters is the issue but I have tried several attempts when other SACDs were being ripped fine.

 

Raising Sand is a Redbook CD, that's why it won't rip using sacd_extract. I have never seen this title mentioned anywhere as available on SACD.

[MikeyFresh]

5 hours ago, loadam59 said:

Did you have the Super Quick Start Mode ON ?

The led on your usb key should be blinking when you insert it 😎

 

I think in my menu it's just called "Quick Start" as with the other Sony models.

 

I don't remember seeing anything about a Super Quick Start mode (did I miss something there)? My S7200 is on Software Version M21.R.0180, I think that's current as I didn't get a notification of any available updates.

[MikeyFresh]

35 minutes ago, Phthalocyanine said:

(What is a Super Jewel Box anyway?)

 

It is the type of jewel box that most of the mainstream SACD releases were packaged in, with rounded corners. Kind of rare (but definitely not unheard of) for regular Redbook releases to be packaged that way

 

[MikeyFresh]

15 hours ago, loadam59 said:

The led on your usb key should be blinking when you insert it 😎

 

The LED does blink and I figured out what was going wrong, I was waiting too long at which point the AutoScript wants to reopen the disc tray.

 

So with the S7200, once the machine is put to sleep and the thumb drive then inserted, you have only a second or two once that thumb drive LED indicates activity to hit the Run button in the GUI to execute the rip. If you wait any longer than that, then the disc tray reopens.

 

So for using the Sleep-server method on the S6200/7200, it makes sense to edit out the line in the script that opens the disc tray as you don't want that happening after sleeping the machine.

 

How do I edit out that line?

[MikeyFresh]

6 hours ago, Phthalocyanine said:

In a Mac, use a reputable text editor program.

 

With macOS the native/venerable TextEdit application gets the job done without issue, it does not try to change the existing .TSS file extension.

[MikeyFresh]

5 minutes ago, Dick Darlington said:

My first clue that something was going on with non visible characters was when I noticed subtle differences in file sizes. A file edited on the Mac appearing to have the exact same contents as a working one had slightly fewer characters which led me to looking at the EOL markers. What I found was that of the three varieties, the Mac/Unix LF did not work whereas both the DOS CR and the “Mac classic” CR did. 

 

 

Thank you for that explanation, I had to this point only deleted that line that opens the drawer and so would not have known anything other than that worked in TextEdit.

 

Now if I give the script referenced by @loadam59 above, I'll know to copy/paste/edit an existing line rather than actually hit Return and start a whole new line.

 

Is there any text editor available for Mac that will behave properly?

[MikeyFresh]

On 3/8/2019 at 7:25 PM, Nexus3 said:

Please test the new (shortened) scripts and comment on them!

 

 

I used the Sony S7200 to test both A2 and A3 tonight with no luck. Interesting results however.

 

First I tried the A2 AutoRip script as described in the previous post in awake-mode. After inserting the thumb drive with the unit ON/awake, the disc tray only opens about 1/4 of the way and then immediately closes again. It never fully opens and so there is no chance of even loading a disc.

 

Next I tried the A3 AutoRip script in sleep-mode as described in the previous post. After inserting the flash drive with the player OFF/sleeping, the tray opens and a disc is loaded, however the tray only then automatically closes about 1/4 of the way before reversing course and fully reopening.

 

I guess I'd like to ask/confirm what exactly should be in the folder for doing AutoRip, i.e. is it just two items or are there 3 total as with the standard AutoScript? A clarification about exactly how many items, and what they are called, and their contents would help me understand if I'm even doing this right.

 

Thank you and goodnight from NY.

 

 

[MikeyFresh]

On 3/12/2019 at 6:04 PM, Nexus3 said:

A2 - release candidate 2:

#MTKAT 0.xx script
CLI(CLI_exec cp /mnt/sd*/AutoScript/sacd_extract_6200 /)
CLI(CLI_exec insmod /lib/modules/2.6.35/BDP/splitter.ko)
CLI(CLI_exec /sacd_extract_6200 -S &)
CLI(CLI_drv.ir.rx.sq 0xaf000)
CLI(CLI_exec /mnt/sd*/AutoScript/autorip.sh)
CLI(CLI_drv.ir.rx.sq 0xaf000)

 

Reporting AutoRip success here using an S7200 with A2 (rc2) and the stereo/multichannel toggle!

 

I will circle back to see if trying A2 (rc2) again without the toggle also works. 

 

In the meantime I've also extracted .dsf tracks from that ISO using SACDExtractGUI, first I wrote them right back to the same SanDisk Cruzer USB2.0 thumb drive at a respectable 4.5mb/s. Then I extracted and wrote the very same .dsf tracks to my MacBook Air's desktop at a blazing 53.6mb/s, about 12x faster! This is a stereo only disc, so there is no DST decompression taking place, but still... Holy extract speed Batman!

 

 

Thanks very much to @Nexus3 for getting my scripts straightened out. I stare at my Windows laptop enough all day at work, I don't like taking it home if I don't have to, but I completely see what @Dick Darlington is talking about with TextEdit on a Mac, even somewhat careful manipulation ends up failing for me there and so to remove that variable it is highly advised to use NotePad ++ on Windows for any script revisions in order not to drive yourself crazy.

 

Now onward to A3 (rc2)...

 

 

 

 

[MikeyFresh]

On 3/12/2019 at 6:04 PM, Nexus3 said:

A3 - release candidate 2:

#MTKAT 0.xx script
CLI(CLI_exec cp /mnt/sd*/AutoScript/sacd_extract_6200 /)
CLI(CLI_exec insmod /lib/modules/2.6.35/BDP/splitter.ko)
CLI(CLI_exec /sacd_extract_6200 -S &)
CLI(CLI_drv.sacd.tray 1)
CLI(CLI_exec sleep 10s)
CLI(CLI_drv.sacd.tray 0)
CLI(CLI_exec /mnt/sd*/AutoScript/autorip.sh)
CLI(CLI_drv.sacd.tray 1)

 

Also reporting success with A3 (rc2) on the S7200!

 

This one is the most elegant yet, with the machine sleeping I inserted the USB thumb drive and when the tray opened, placed an SACD in it. Tray closed automatically and after about 5-6 seconds, the rip started as evidenced by the flash drive's LED activity. When the rip ended, the disc tray opened. Voila:

The strange thing with this particular disc was the .dsf extraction speed to my MacBook Air's SSD did not hit warp speed at all, instead it struggled to stay right about 4mb/s and the fan came on and it hit warp speed. I wonder if this Channel Classics disc was authored using DST on the stereo tracks?

 

 

So A3 (rc2) works very well, but I'm puzzled by the slow extract speed unless it is just something specific to that disc. Or, conversely, perhaps it's something about the Analogue Productions disc I used with the A2 test that allowed for such high extraction speeds?

 

All in all, GREAT work on these AutoRip scripts by everyone involved, thank you and once again a special thanks to @Nexus3 for straightening out the scripts, and @Dick Darlington for bettering my understanding of the pitfalls of TextEdit.

 

 

[MikeyFresh]

1 hour ago, Dick Darlington said:

Yes. If you go to the first page and look at the bottom of the first post you'll find the recently updated player list provided by @MikeyFresh

 

I think that link on Page 1 is once again stale, based on recent findings last month. Here is an up-to-date listing:

 

The following is an updated list of Blu-ray player brands/models known to be SACD rip compatible:

 

Sony brand compatible Blu-ray players:
BDP-S390 (also sold as BX39 in some markets)
BDP-S490
BDP-S590 (also sold as BX59 in some markets)
BDP-S4100
BDP-S5100 (also sold as BX510 in some markets)

BDP-S790 * (only with ARMv7 AutoScript version)

BDP-S6200 * (also sold as BX620 in some markets, only with ARMv7 AutoScript version)

BDP-S7200 * (only with ARMv7 AutoScript version)

Pioneer brand compatible Blu-ray players:
BDP-80FD
BDP-160
BDP-170

Oppo brand compatible Blu-ray players:
BDP-103 and 103D
BDP-105 and 105D

Cambridge brand compatible Blu-ray players:
Azur 752BD
CXU

Arcam brand compatible Blu-ray & CD/SACD players:
FMJ UDP411
FMJ CDS27

 

Primare brand compatible Blu-ray player:
BD32 MkII

Electrocompaniet brand compatible Blu-ray player:
EMP3

[MikeyFresh]

7 minutes ago, Phthalocyanine said:

Using a Sony requires just one additional step from what you were doing with your previous Oppo.

 

Thats right, really a negligible difference, not worth worrying about in comparison to use of the other player brands. This is especially true when considering the cost/availability advantage of the Sonys.

 

In fact it's no real difference at all when using the sleep-server method, amounting to the pressing of the Power OFF button to close the disc tray instead of the open/close button (end of difference).

[MikeyFresh]

7 minutes ago, Waynefi said:

Is there any reason that in this case the S390 won't work for some reason ?

 

There is no reason, that model simply works, however it is the bottom of the line known-working Sony. Perhaps a little patience would yield an S590 or 790 which have somewhat superior build quality, or the 2013 model year S5100/BX510 for instance, all of which have the added feature of an LED display that gives some visual feedback as to what is happening when you initiate a rip.

 

The S390 is fine, but lacking any front panel display, you are left to just carefully follow instructions and not get any visual indication as to what is happening. Not a huge thing, but it's the main reason I just leave my S390 in reserve and use one of the other Sony models, I like the front panel display feedback.

[MikeyFresh]

18 minutes ago, ady_lister said:

Should anything else be on my USB apart from the Autoscript and the sacdextract_160?

 

I had the .TSS file on / off but got same results, so I took it off.  If I need the .TSS file on, what should be on it?

 

All of the above needs to be inside an enclosing folder called AutoScript.

 

That enclosing folder called AutoScript needs to reside at the root level of the USB thumb drive.

 

In Windows 10 it looks like this:

 

[MikeyFresh]

12 minutes ago, ady_lister said:

Thanks, Ok so I do need the .TSS

 

Ok done that.

 

So you have the enclosing folder called AutoScript now?

 

If so, you need to do a full power cycle, which means power OFF with the thumb drive removed, pull/replace the AC power cord, power ON and wait for the initial boot sequence, then insert USB thumb drive and proceed with the rip sequence.

 

Also ensure that ISO2DSD was fully restarted, and never use the Quit button to quit that program as it definitely causes issues, close the program via the red X at the upper right-hand corner of the window.

[MikeyFresh]

28 minutes ago, ady_lister said:

I followed the advice to change that line to 'telnetd'.

 

If you are using ISO2DSD, and the stereo/multichannel toggle, that means you are not using Telnet at all, you are using the server method.

 

I don't then know why you are changing the script with regard to things that only apply to using Telnet, but I'd be willing to bet that script is now broken. For instance, you probably tried to poke around inside the middle file, and I can see that Windows has now deleted the .TSS file extension.

 

Rather than guess at it, wipe your thumb drive clean and place a new enclosing folder called AutoScript on it with freshly downloaded contents. Then, power cycle the machine again and proceed with the rip sequence.

[MikeyFresh]

1 hour ago, Dick Darlington said:

Actually only one AutoScript file is necessary. The Sony players don’t care if it’s the .TSS or the sans extension one. I have never tested to determine which is dominant if both are present. The Oppo players don’t recognize the script unless it has the .TSS extension. No clue about the Pioneers.  My guess is they’re the opposite of the Oppo and only recognize the extensionless script. 

 

Interesting, I have always just left that download package intact/as is and never tried to eliminate any portion of it.

 

Tough to say then what exactly was going wrong in today's problem case, I wasn't actually suggesting it was the lack of the .TSS file extension, just simply that was a clue or indication displayed in his screen shot that the user had been poking around in the scripts, and thus all bets were off on any errant keystrokes or other changes having broken them.

[MikeyFresh]

24 minutes ago, Waynefi said:

Embarrassed to say I am lost. I wanted to try this tonight.

 

 

What program did you use with the Oppo or for that matter do you plan to use with the Sony with the server method, ISO2DSD?

 

24 minutes ago, Waynefi said:

Do I need to delete those few files that were put on for the OPPO ?

 

Yes, wipe the USB thumb drive of the files for the Oppo, they won't work with a Sony Blu-ray player.

 

24 minutes ago, Waynefi said:

I got the Sony server method instructions from Phthalocyanine, but understand most of the instructions, but am stuck on what and where I have to load some initial folder/files on the PC, and what to put on the USB.

 

The USB thumb drive needs the Pioneer-Sony script found here, however you need to be sure you actually have an enclosing folder called AutoScript. For some reason (especially on Windows) the DropBox web interface seems to yield the folder's contents and discard the actual enclosing folder, that enclosing folder is needed in all cases.

 

Try this:

 

 

If you only get the contents and not the enclosing folder, create an enclosing folder called AutoScript and place the downloaded contents into it.

 

[MikeyFresh]

26 minutes ago, Phthalocyanine said:

I thought the Mark I was based on the Oppo 93/95

 

It is and so very likely incompatible, as with the Cambridge 751BD.

 

For reference, the chipset is described as the Mediatek MTK8530.

[MikeyFresh]

1 hour ago, Phthalocyanine said:

Yes but I thought recent research here had determined that it was the kernel type 2.6.35  that was the most important thing not the particular Mediatek MTK number.

 

Thats right and the Sony S390 for instance does not use either the MT8560 or 8580 that were once thought to be the only compatible CPUs.

 

The MT8530 found in the BDP-93/751BD, and BD32 Mk. I hails from Oct. 2009. The kernel version 2.6.35 debuted in Aug. 2010, so not impossible that a firmware update could have occurred that utilized the newer kernel version on those slightly older machines. I don't know if the disc player manufacturer would have relied on Mediatek for such an update, or if they would have been expected to develop that themselves (likely).

 

I think I saw a reference on the AVS Forum to this older era of machine using kernel version 2.6.27 which debuted in Oct. 2008, but who knows if that's actually the case, or if I'm even remembering that right.

 

I also saw a reference in that same thread to the Oppo 93/95 units using some sort of a special version of that Mediatek chip, called the OP8531.

[MikeyFresh]

23 minutes ago, Nexus3 said:

Is there anyone eager to comment on / second the following proposal?

 

I second that proposal, there are Oppo BDP-93/5, Cambridge 751BD, and Primare BD32 Mk.I owners that can benefit.

 

I certainly lack the technical knowledge necessary to verbalize the exact task at hand however.

[MikeyFresh]

1 hour ago, LazyBorzoi said:

Can someone please point me in the right direction?

 

Check your PMs.