Bummer.
I came in looking to see if my Sony UBP-X800 would work. Sadly, it appears not to be the case.

Don't give up hope just yet, I believe your X800 uses Linux kernel version 3.10.26, which was only recently found to be compatible with the S6500, and some early production S6700 Sony models.

While to date the above two models are the only known compatible units not running Linux kernel version 2.6.35, that doesn't mean it will always stay that way.

If you have a spare USB thumb drive, perhaps you can add a data point to the research?

All you'd be doing is placing @Nexus3 's ARMinfo script at the root of the thumb drive, and then simply insert it into the X800's USB port. From there if the script is read, it (hopefully) will write two small .txt files to the pen drive which will provide clues about that unit's chipset and Linux kernel version.

Alternatively, if the player does not write anything to the thumb drive, then that unit will likely stay incompatible as evidently AutoScript won't run at all.

On a Mac your pen drive AutoScript folder structure will look like this:

ARMinfo.Screenie.jpg

You can fully disregard the "buda" folder, that's something the player will write to the drive for a feature called BD-Live, but is otherwise completely unrelated/irrelevant. After a few seconds, you would remove the thumb drive from the player and put it back into the computer to see if there are now also 2 .txt files with information about the player, if present they will be called kernelinfo.txt, and chipsetinfo.txt, and they might just yield clues that can push in the direction of the X800 someday becoming compatible.

It's worth a try if you have a USB thumb drive handy.
 
Good evening,

thanks to a friendly fella (from another forum), we have a new SACD ripping player model in town.

He first tested the ARMinfo script on his Yamaha BD-S677 and then confirmed its ripping capability via the corresponding AutoRip script.
The text-file extracts are as follows:

Linux (none) 2.6.35 #1 PREEMPT Mon Nov 17 16:52:46 CST 2014 armv6l GNU/Linux
-------------------
000000e9, 000000e2, 005fc2f1, 00000202, 00000000
return TRUE
IC Version: MT8560VBAG
MSB: 000000e9
LSB: 000000e2
table1: 005fc2f1
table2: 00000000
prot: 00000202
IPTV: 00000000
Byte28: 00000001
-------------------
MSB: 1110 - 1001
LSB: 1110 - 0010
DivXHT - 11
DivXUltra - 01
DivXHD - 00
-------------------
------------------------------
ROM: [BSP_GetIcFunc] u4FuncID = 0
|x
TZ: [BSP_GetIcFunc] u4FuncID = 1
|x
AACS: v|
---------
DivXHT: |x
DivXUltra: |x
DivXHD: |x
SACD: v|
DolbyTrueHD: v|
DTSHD: v|
3DVideo: v|
DolbyDDCO: v|
DivXPlus: v|
---------
DolbyHeadphone: |x
DolbyPLIiIixIiz: |x
DolbyEX: |x
DolbyDigitalPlus: v|
DolbyVSpeaker: |x
DTSSurdSensation: |x
Multichannel: v|
DVDAudio: v|
Playready: v|
RM: |x
WMDRM: [BSP_GetIcFunc] u4FuncID = 22
|x
CinemaNow: v|
Netflix: v|
Macrovision: v|
YahooWidget: v|
Browser: v|
AVCHD: v|
AdobeFlashLite: |x
Rhapsody: v|
NTFS: v|
---------
2ndARM: |x
DolbyAAC: v|
WMV: v|
HomeTheater: v|
WMA: v|
HDCD: v|
---------
H264_Encoder: |x
HDMI_RX: |x
InternalDIR: |x
AACPLUSv1: v|
AACPLUSv2: v|
SmoothStream: |x
---------
L2 cache: v|
------------------------------

You may now guess what the correct AutoRip script might be or just scroll back to page 82.


In any case, I fully expect to see more of the Yamahas joining the club sooner or later. :D
 
Make that known failures + 1. I grabbed one with fingers crossed, but now ouch:-). FYI, the numbers on the wall wart are: 1-493-089-11 and M1965875943 if that helps. It has a white label on the chassis with a date of 11/20/2019 but its a refurb so that does not make sense - I guess that must be the date of the refurb.

Perhaps we should switch methods and start collecting SERIAL NUMBERS (maybe omitting the last two digits), in order to distinguish the good and bad Sony BDP-S6700s.


And yes since the unboxing video was uploaded back in November 2016, SN 2030154 should be a GOOD one :tongue:.


This 2019 model for the Latin-American market is most certainly a no go - SN 4005315:



Whereas this refurbished model could be compatible - SN 1495517:
 
Last edited:
Perhaps we should switch methods and start collecting SERIAL NUMBERS (maybe omitting the last two digits), in order to distinguish the good and bad Sony BDP-S6700s.


And yes since the unboxing video was uploaded back in November 2016, SN 2030154 should be a GOOD one :tongue:.


This 2019 model for the Latin-American market is most certainly a no go - SN 4005315:



Whereas this refurbished model could be compatible - SN 1495517:


Well, here is my contribution - does not work: SN 16968XX, where 'XX' masks the last 2 digits as Nexus3 suggested.
 
Perhaps we should switch methods and start collecting SERIAL NUMBERS (maybe omitting the last two digits), in order to distinguish the good and bad Sony BDP-S6700s.
My non-working S6700 is SN 18322XX.

It was said to be a new open box by the retailer. It also refuses ARMinfo, nothing happens.
 
Hello @Srx & @MikeyFresh,

thank you for taking the lead and sharing the SN of your S6700 units.

Would you also consider providing the date (year & month) of your purchase (if you are the first buyer of the unit) & the initial/factory firmware level. Just paste the info into the last sheet HERE.

Cheers,

Nexus3
 
Compiled on a RPi 3B+ & RPi ZeroW - tested with Raspbian Buster & Ubuntu MATE 18.04.4 LTS.
Today I tested this on a Pi 4B (8GB) running Ubuntu MATE 20.04.1 LTS (64-bit).

Screenshot at 2020-07-25 16-21-11.png

I ripped the same disc (Dark Side Of The Moon) as I had with the ARMv7 Raspbian, er... Raspberry Pi OS build to compare the speed difference, however I now realize my comparison is invalid because the ARMv7 rip was over WiFi, while this ARMv8 rip was done using Ethernet. That's not a level playing field.

Nevertheless, this ARMv8 build shaved off 61 seconds of rip time, the Dark Side Of The Moon stereo tracks only took 11 minutes and 1 second. As with Raspbian, er... Raspberry Pi OS on ARMv7, this ARMv8 install running Ubuntu Mate 20.04.1 did not heat up at all, barely warm to the touch, and that was with no stick-on heat sinks as I've temporarily run out of them.

@Nexus3 , I'm now curious how long a snooze I'm in for if I decompress the DST on the multichannel tracks?

I remember trying that once on a Pi 3B running Nexus3's original compile for Raspbian a couple of years ago and the unit shut down right in the middle of the rip with no warning, evidently that was too big an ask and she overheated. I was concerned I might have damaged the board but that wasn't the case, it was fine and that 3B still runs to this day, though I never asked her to decompress DST ever again after that one meltdown.

This post was made with the Firefox web browser, on a RPi 4B (8GB) running Ubuntu MATE 20.04.1 (64-bit), a sub $100 Linux desktop computer I'm finding no fault with. As with digital audio, you can now get excellent desktop computer performance for under a Benjamin, while drawing about 10 watts of power, but you'll have to bring your own keyboard/mouse/monitor.
 
Good evening everyone,

after a long hiatus, may I present to you - a complete set of AutoRip scripts to make SACD ripping as simple as possible:

View attachment 25746

A special note of thanks goes to @Srx (for discovering the "nap mode") & @MikeyFresh (our topic showrunner, chief instructor and community motivator)!

Support the community by spreading the word, rating & commenting on our tools at websites like videohelp.com.
If you want to do me a favour, check out this feature request at Google 🔤 and leave your comment ✍ & upvote ⭐ there.


Happy ripping 💿 , stay safe 💪 & USE THE TOOLS AT YOUR OWN RISK! :Deal
Hi Nexus, much thanks for developing this tool, it has made the whole process much simplier and easier, saved a lot of my time!
 
Hello,

Thanks to the testing efforts of our fellow forum member @Sixtyten , the most advanced Blu-ray disc (Profile 5.0) player model from Sony, the UHP-H1 is also a SACD ripping capable device now :D:

SACD AutoRip_overview_v6.png

At the other end (more or less) of the product ladder, there is a also a newcomer - the Sony BDV-E190, a Blu-ray surround system.
This little fella could bring in an entire family, eventually (firmware notes US / UK):

  • BDV-E290
  • BDV-E385
  • BDV-E390
  • BDV-E490
  • BDV-E690
  • BDV-EF220
  • BDV-EF420
  • BDV-T39

Happy Ripping!
 
Good evening to all,

As we begin August 2020, this thread has surpassed 220,000 views, and 1,872 posts, in just under 27 months since inception.

In just the last six weeks, 7 new player models have been identified as SACD rip compatible (6.5 if you only count the S6700 as partially compatible depending on production date), including the first of what might be several additional Yamaha brand players.

The recent advent of the ARMinfo script by @Nexus3 allows for additional compatible player brands/models to be much more easily identified. Additionally, AutoRip A6 was added as a local rip method option for the most newly identified Sony models, which are the very first known compatible units not to employ Linux kernel version 2.6.35, suggesting there is likely more where that came from.

Last but certainly not least, there is strong ongoing development of sacd_extract 0.3.9.3, with new news forthcoming on that front, so please stayed tuned to this channel!
 
Mikey - continually amazed at your participation on this thread. Happy with my SACD ripping solution ("local rip" direct ISO to flash drive).

I think I ran into my first special-characters disk. Before I go down the route of getting the file server method up and running (the known workaround) is there an update on whether that problem is being looked at? I'm not even sure what part of the architecture that problem is in... is it in sacd_extract itself?

Thanks again...
 
Mikey - continually amazed at your participation on this thread. Happy with my SACD ripping solution ("local rip" direct ISO to flash drive).
Thank you very much, I do appreciate it and I also acknowledge all of the other valuable contributors that made this whole thread possible.

I'm not even sure what part of the architecture that problem is in... is it in sacd_extract itself?
Yes it is.

I think I ran into my first special-characters disk. Before I go down the route of getting the file server method up and running (the known workaround) is there an update on whether that problem is being looked at?
Could be special characters or it could be an excessive file path length. Do you see a bunch of special characters in the disc's metadata, i.e. non-English characters in the title, movement etc ?

If not, it could be an excessive file path length and sometimes all you need to do there is shorten that to the extent you can. With AutoRip that really just means naming the flash drive one single character, such as "R" for rips, or "S" for SACD, just use a single character (ignore the quotation marks I used).

If you are only short a character or two on the path length, and your flash drive has a name that is several characters long, sometimes this can be an easy solution.

If it is indeed a case of special characters, then you should install the network server method software, i.e. SACDExtractGUI, and that will solve it.

While sacd_extract is under continued development, compiling it for AutoRip is another matter, and though I would suspect that will happen at some point so that AutoRip has the latest version of the binary, right now AutoRip does sometimes refuse some discs with special characters, or an excessive file path length due to the way the metadata was authored.
 
Hi Everyone,

We have a new script for the Sony BDP-6500. I revised the the original script to make it work in an automated sleep-server mode on the S6500. "Automated", here simply means once the USB is inserted, the script will open the disc tray for you, wait 10 sec for you to insert the disc and then close the tray. The server will be waiting for you to connect from the java SACD_ExtractGUI or command line. Note: the tray will not eject when the rip is finished. Link = BDP-S6500

SEE INSTRUCTIONS BELOW

Our sincere thanks go to mindset for his patch of the ARMv7 executable, aka sacd_extract_6700, and to Nexus3 for compiling it. Nexus3 also contributed knowledge to us that was critical in the successful development of the script.

Special thanks to MikeyFresh for his support and coordination of this effort.

  1. Plug in the machine
  2. Insert the USB
  3. Insert the disc when tray opens
  4. Wait for tray to close & the power light to go off
  5. Go to the GUI and click "Test" to see if port 2002 is "accessible" and if true
  6. Click Run to start the extract
For the next disc,
  • Remove the USB drive,
  • Power the unit on, wait for the red light to come on
  • Power off - wait for the light to go off and
  • Reinsert the USB drive.
  • Follow steps 3-6


If you have any difficulty with 7-11, fully power cycle the device:
· Unplug it and wait a few seconds
· Plug it back in and resume.
 
Last edited:
Anyone one in Toronto wants it make a bit of $$$ to help a frustrated covid mad audiophile get past the last hurdle to SACD heaven. Im willing to bring my player to you so you can figure out why this is happening. I got the right IP address, right software, etc.oppo error.png
 
Last edited:
Anyone one in Toronto wants it make a bit of $$$ to help a frustrated covid mad audiophile get past the last hurdle to SACD heaven. Im willing to bring my player to you so you can figure out why this is happening. I got the right IP address, right software, etc.View attachment 26191
Good afternoon,

I'm operating at a deficit after a very damaging hurricane yesterday, battery power only.

Windows, Mac, or Linux computer?

Can you confirm that you have an outer/enclosing folder called AutoScript, that houses the 3 additional files on your USB flash drive?
 
Anyone one in Toronto wants it make a bit of $$$ to help a frustrated covid mad audiophile get past the last hurdle to SACD heaven. Im willing to bring my player to you so you can figure out why this is happening. I got the right IP address, right software, etc.View attachment 26191
I'm getting the same message. I have a Sony BDP-S6500 and the computer is a MacBook Pro. I have tried 2 SACDs. What happens is that I plug in the USB with the AutoScript folder at the top level, there are 3 files within that folder.

I power up the player, the player boots up and I can see the home screen with the APPs, after a few seconds it shuts down and the CD tray opens. I enter an SACD and the tray auto closes. The power turns off, I press the execute button, wait a few minutes and get the same message as you.

Any help would be gratefully appreciated, I'd like to experience Depeche Mode Violator album and The Police Every Breath You Take in DSD quality on my hifi.

System:
Allo Digione Signature streamer with a 1TB SSD
Denafrips Ares II DAC
Hegel Röst Integrated AMP
Magnepan LRS Loud Speakers
2 X SVS SB-1000 Subwoofers

Thanks in advance for all help received
 
Hi Mike yes..Mac...got the Autoscript files open and on the drive.I think if its done properly the tray should open on its own?..It doesnt open.
Yes, tray should open automatically, might be worth formatting the USB as MS-DOS Fat, then dropping the auto script folder at the top level. You may even want to download the auto script again. Plug the USB in when the player is in standby and then power the player on.
 
Back
Top