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

[Dick Darlington]

Lessons Learned Along the Way on my Journey to Sony BDP-S590 Ripping Nirvana 

 

‼️ Many kudos and thanks to you, Phthalocyanine, for expanding the universe of rip-capable players ‼️

 

For nigh on a year I’ve been happily ripping SACDs on my Oppo 103 thanks to ? Ted_B ? and other earlier contributors.  And yet, the "monsters under my bed" like fear that I would one day wake to find that my Oppo had bitten the consumer electronics dust ?? and to know that I was again in the shackles ⛓ of servitude to physical media has lingered all the while.  As the challenge and expense of finding a replacement ripper has increased over the past year, so too has been my therapist’s?‍?net worth???.

 

Needless to say I was quite chuffed??to learn of this windfall expansion of the rip capable devices pool.  I wasted no time in snagging an S590 for $35 (more than half of which was shipping ?) on eBay to serve as a backup ripper.?? Thank you again Mr. P!

 

It is working beautifully now, and I am delighted at no longer carrying all of my eggs in one basket, but this did not come without an afternoon of spinning my wheels in frustration ? and a growing concern that even if the exploit worked on some S590s it may not necessarily work on all.  Fortunately that was not the case.??

 

My initial attempts were thwarted by a few trivial issues and a soupçon of ill luck as it turned out.  So, I figured it might be worthwhile to share with the community the details of my brushes with some easily avoidable pitfalls.

 

Before I proceed, a few caveats and contextual notes may be in order:

• The following pertains to my recent experience with a Sony BDP-S590 specifically. However, some issues and observations may have broader applicability.
• The computers involved were a Mac running macOS High Sierra AND a PC running Windows 10.  Both were capable of ripping from my Oppo 103 without issue via my dedicated Oppo configured USB stick.  The point being: I was starting from a position of basic knowhow and a computer configuration and network environment that was verifiably working with the Oppo BDP-103. 
• My S590 is running firmware M12 R.0430 (the last supporting SACD-R as per Mr. Phthalocyanine).  I was unable to confirm the year of manufacture.

The obstacles I encountered with the S590 boil down to these four problems that will be described in full detail below:

1. USB stick partition table problem (of a benign nature)
2. Discrepancy in AutoScript files for Telnet method obtained via a posted Dropbox link
3. USB stick partition table problem (of an insidious evil nature)
4. My misinterpretation of the finer points of Mr. P’s autoload “workaround”

The details of each are as follows; not necessarily in the order that they were kicking my arse:
 

1. USB drive partition table type not compatible with S590 -- USB stick partition table problem (of a benign nature)

 

After getting nowhere with my initial “server method” attempts, I fetched a second USB drive, and used the Mac to erase it and create a fresh FAT32 volume and prepared it with the necessary “Telnet method” AutoScript folder and files.  When I inserted it in the rebooted player however, an error message “The USB device connected to this unit’s front panel is not supported.”  I replaced it with my original drive, and no such error (although it was still useless for ripping at this point).  I tried a third stick of a different model with a fresh FAT32 volume with no files and it too resulted in the USB device unsupported.

 

As it turned out, the problem was due to the partition table type being incorrect in the case of the “unsupported” USB drives.  The Mac defaulted to creating a GUID Partition Table (GPT) instead of the legacy Master Boot Record (MBR) table type.  A FAT32 volume can be created on either, but only a drive with an underlying MBR partition table will work.

 

Takeaway:  Your USB drive MUST be initialized as an MBR partition table device.  That may or may not be the default on your computer.  If in doubt an easy check is to first insert your intended USB drive in the S590 prior to setting up the AutoScript folder to confirm that it is recognized as a supported device.

 

2. Discrepancy in Telnet method AutoScript file

 

Having been setup to rip from my Oppo, which only supports the server method, the Telnet method was all new to me.  The instructions that I first found were in Ted’s post of July 22, 2016, which includes a Dropbox link to a Telnet method AutoScript folder.  It is possible that I overlooked a more recent link, but it is the one I found first and so it is someone else my come along and make the same misstep.

 

I repost the link here: https://www.dropbox.com/sh/eu48sjfmrgtxdan/AAB1Q8x6vRWMQAt1egXOevYQa?dl=0

 

That is what I used to create my USB drive, but alas nothing happened upon insertion and my attempt to Telnet from my Windows 10 PC resulted in the “connection refused” pound sand message.  Eventually I noticed that the contents of the AutoScript files had “inetd” in the Telnet server launching line instead of “telnetd” as shown in the text of Ted’s post.  When I replaced the “inetd” in the AutoScript files with “telnetd”, that was when my S590 fortunes began to change for the better although I wasn’t quite out of the woods.

 

Takeaway:  Although “inetd” is presumably the correct daemon to launch on other players to enable Telnet access, it does not seem to be the case for the Sony S590.  Inspect your AutoScript and AutoScript.TSS and if necessary replace “inetd” with “telnetd” before attempting a Telnet connection to your S590.

 

3. Just plain evil USB drive partition table (or lack thereof) anomaly

 

As luck would have it I was using my original, randomly selected from my stash, 16 GB Kingston USB drive when I made my aforementioned Telnet method breakthrough.

 

BTW, this was the drive I originally tried to use for the server method with no success past the point were the tray opened.  Attempts to connect with sacd_extract from Windows crashed and burned every time.  But now I had repopulated it with a working telnet AutoScript and I was able to telnet in and logon as root. Wahoo!

 

My euphoria was short lived.  When I attempted to cd over to the USB device I was presented with the “no such file or directory” message.  And sure enough, /mnt/sda1 did not exist but rather the USB drive had been auto-mounted as “sda” and not “sda1” as assumed by all the AutoScript variants I’ve encountered.

 

Aha I am thinking; the S590 uses sda whereas the others use sda1. (I was wrong of course but it made sense at the time.) NO WONDER it didn’t work with the server method AutoScript!  So I grabbed a different USB drive and set it up for the server method but with sda1 changed to sda; and exclaimed THESE HANDS ARE TOUCHED BY GOD!

?‍♂️ 

I waited a few minutes for the champaign? to chill and tried again.

No joy.??‍♂️WTF?

 

By using the rear USB port for my Kingston telnet drive *after* rebooting and inserting a different USB drive in the front, I could “ls /mnt” and see where the front drive was mounted.  Note that in this case, the rear inserted Kingston drive mounted at “sdb” rather than “sda” since it was inserted second.

 

I repeated this for several drives and in every case the other drive ended up at “sda1”.  WTF?  So basically “sda1” was correct for every single USB drive I had EXCEPT for the one I randomly chose at the beginning and was still trying to use.  That one always mounted as “sda” (unless it was inserted second whereas it would mount as “sdb”).

 

So what was different about the Kingston?  I couldn’t believe that the brand was a factor.  The clue to solving the mystery was the way it appeared within the Disk Utility app on my Mac. Every external drive is displayed as a top level “external physical disk” e.g. “disk3” having one or more sub-level “external physical volumes”, e.g. “disk3s1” underneath; except for the Kingston.  It shows up as an “external physical volume”, “disk7”, at the top level with no sub-levels.

 

The Kingston works normally in every way and I’ve since made it work in both Telnet and server modes by changing sda1 to sda, but it is truly special.  Too bad that’s the one I picked initially.  Any other of my MBR partitioned USB sticks would have worked in server mode on the first try.  Ah well.

 

After looking at the Kingston with Test Disk and some other tools (albeit not PTEDIT which I no longer have a copy of) it is a “non-partitioned disk” and considered to be invalid by those tools.  Clonezilla and GPartEd both choke on it, but Windows, macOS, and the Linux on the S590 seem to fully tolerate it’s alternative orientation.  I cannot replicate the weird structure to save my life and I’ll probably die never knowing how it came to be, but there it is.

 

Takeaway:  Don’t be unlucky.?

 

4. Misinterpretation of “autoload workaround” instructions
(IOW: I’ve been stupid so you don’t need to.??‍♂️)

 

I completely misunderstood (to the point of getting it arse backwards) Mr. P’s explanation of his fortuitous (and impressively so!) discovery of the autoload workaround.  I was believing that after toggling between 2-channel and multi-channel in Music Settings but before starting the rip, the disk had to be reinserted in order for the change invoked by the toggle step to take affect.  But in fact the rip operation can be done immediately after the toggle, but will not work after reinserting a disk unless and until the Music Settings toggle step is repeated.

 

Takeaway:  Starting from the point where the sacd_extract server is running on the player and the inserted disk has been autoloaded: toggle the setting in Music Settings and then proceed with the rip via sacd_extract or if you prefer, iso2dsd. The toggle action must be repeated immediately after each subsequent disk insertion.

Well there you have it.  May The Force be with you, and may the Goddess light your way.

 

Dick

 

PS:  Note for Mac users. FWIW, as others have mentioned the option to select MS-DOS FAT32 is no longer present on newer versions of macOS; only MS-DOS FAT.  This is not a problem and there is no need to find another means of formatting your USB drive.  If you choose MS-DOS FAT it will actually create the volume as FAT32 as necessary based on the size of the drive.

 

PPS: I have informed my therapist?‍?that her services are no longer required.

[bellhead]

Do you love SACD / DSD sound? I do and always have.

Why is there so much negativity about it on the other sites?

 

Whenever it is mentioned, people say it's just remastering, or DSD is fundamentally flawed, or it's a placebo affect.

To me it's night and day with transparency, bass clarity, speed, far better defined images, lack-of-fatigue in the highs, no digital shrillness,

analog-like-advantages, and on and on.

 

But there is real, almost hostile pushback, and I just don't understand it.

Yep, PCM processing has come a long way, and I love what my Chord DAVE does with PCM (and it also does a fine job with native DSD, thankfully), but there is nothing like DSD to these ears.

I sure hope the format stays alive in some capacity.

 

This new method of turning SACDs into files is a Godsend, and I would hope it revives DSD to some degree. Hope springs eternal you know. But it won't happen if there is all this criticism of it. I just don't get how the audiophile community could be so critical of something that just sounds so great. I guess there is no accounting for taste, but do others in this thread hear what I have always heard from DSD?

 

Thanks for any comments.

 

So as not to disrupt this thread, please reply to this new thread I created for this topic here:

 

[greynolds]

5 minutes ago, bellhead said:

Do you love SACD / DSD sound? I do and always have.

<snip>

This isn't the right thread to discuss this as it has absolutely nothing to do with ripping the discs...

[bellhead]

OK, I thought of starting a new thread for it, but I felt this was the thread where DSD fans would congregate, so point taken.

I did agonize over going off on a tangent here I have to admit. It's just that this is so important, I felt it was worth it. I am sorry for disrupting the subject.

 

If people here think my post was inappropriate, please let me know and I'll shift it to an independent thread.

 

OK , here is the thread for this subject:

Thanks for any responses. I feel this is an important subject that is related to this thread.

[HenkNZ]

I just read Dick Darlington's post!  Awesome.  Now.... Why can I not get my Oppo 103 to work with my Mac?  I am close to giving up.

Anyone with a set of working Oppo and Mac instruction that they can share?

[tmtomh]

28 minutes ago, HenkNZ said:

I just read Dick Darlington's post!  Awesome.  Now.... Why can I not get my Oppo 103 to work with my Mac?  I am close to giving up.

Anyone with a set of working Oppo and Mac instruction that they can share?

 

I'm afraid you're going to have to be a little more specific about what problem you're running into with your 103 and your Mac - like what step are you stuck on?

 

@Dick Darlington indeed, great set of instructions!

 

One small addition to your bit about formatting USB drives with a Mac. You are quite right that MS-DOS will work in many cases, and that the current version of macOS no longer shows "FAT32" as an option. However, MS-DOS is FAT16 formatting and that's limited to 4GB drives/volumes. For larger volumes you need FAT32 - and macOS actually does still do this, but they've changed the name to exFAT for some reason. So it is still available.

 

I mention this because I've gone to format some drives recently in PC/Windows format on my Mac, and "MS-DOS" was greyed out as an option (because the discs were well over 4GB in size). I finally noticed the exFAT option and all was well.

[HenkNZ]

Yes, indeed, I need to be more specific.

The USB stick opens the tray on the Oppo.  I have also added the Oppo to my Ethernet network and took off the wireless adaptor for this. I can see the Oppo IP address on my network, next to my Mac using network mapping software.  I am using latest macOS, btw.  From this I assumed that the USB device was formatted properly and the scripts were working.  When I then run the sonore gui it returns Failed to connect, cant open for reading..  

[HenkNZ]

Also, I looked at the script files, both are the same, except for one having the .tss extension.  Is this right?

 

[Dick Darlington]

41 minutes ago, HenkNZ said:

Also, I looked at the script files, both are the same, except for one having the .tss extension.  Is this right?

 

Are you including the “:2002” port number in the dsd2iso server address field?

[HenkNZ]

Yes: 

[HenkNZ]

[HenkNZ]

oh.... I have the BP103D.  I wonder if this is an issue?

[One and a half]

3 hours ago, HenkNZ said:

I just read Dick Darlington's post!  Awesome.  Now.... Why can I not get my Oppo 103 to work with my Mac?  I am close to giving up.

Anyone with a set of working Oppo and Mac instruction that they can share?

You haven't confirmed any settings in @Dick Darlington excellent post, how are we to know what you've tried or ignored??

 

Not mind readers. Anyway you couldn't have read all the instructions to the letter, your screenshot shows direct to Sony DSF. Set this to ISO.  Details!!

 

The USB stick partitioning and formatting is super critical, did you do this? Details!!

 

[greynolds]

While his post was excellent, the specifics in @Dick Darlington's post apply primarily to the Sony player, not the Oppo.  There may be some useful takeaways there, just don't expect to follow those steps to the letter with an Oppo and expect success; if nothing else the script files are slightly different.

 

While I agree that ripping to ISO makes more sense than converting to individual DSF files, it should have no impact on whatever the fundamental problem @HenkNZ is having getting the computer and the Oppo to talk with each other.

 

If the disc drawer opens with the USB stick inserted, then setup on the Oppo side is most likely good and the issue is probably going to turn out to network configuration (the player and computer on different subnets, for example) or computer configuration (a software firewall blocking a port that needs to be open, for example).  I'm not a Mac guy, so I really have nothing to offer in terms of specific suggestions there.  Is there a Windows PC or laptop available that could be used for testing purposes to see if you can rip to that?  If so, that could help isolate the problem to the Mac or the home network.  What's the IP address of the PC? If it isn't 192.168.1.xxx, then that might be the problem as the Oppo probably needs to be on the same subnet as the computer.

 

Oppo BDP-103, BDP-103D, BDP-105, and BDP-105D are all interchangeable for this task, so having a BDP-103D definitely isn't the problem.

[HenkNZ]

Ok, so have also checked my Oppo.  It is 103D version.  I do not know if it has the same chipset as the 103.  My unit is in firmware 83-1226.  This may also be an issue.  

1. USB drive is a 2GB one, formatted to FAT32 with MBR partitioning.
2. When I insert the USB, I can see on my TV that it says Open after about 3 seconds.  The tray opens and I load the disk, then hit close.
3. I can see that my Mac and the Oppo are all on the same subnet: 192.168.1.73 and 76 respectively. Mask is 255.255.255.0.
4. Using a network inspection tool on the Mac I can see that the ping to the Oppo is 2ms.  It is there and responds at that level.
5. On the Mac, the software is on a second volume, not the OS volume and in a directory at the root of that volume with a short name (SACD).
6. In response to another message above, I followed the Word document that I found in a linked Dropbox folder for setting up he Sonore software.  
7. When I use wireless (Mac and Oppo on a wireless network) I find that when I hit execute it takes a few seconds before I get the message above.
8. When I use the ethernet connection, the result is immediate.
9. I have a Surface tablet that runs Windows 10.  I had no success from there.
10. I have a Windows 7 VM - no success from there.

I am hoping that this will help others like myself that are very new to this sort of stuff.  

[n2it]

10 hours ago, Dick Darlington said:

4. Misinterpretation of “autoload workaround” instructions
(IOW: I’ve been stupid so you don’t need to.??‍♂️)

 

I completely misunderstood (to the point of getting it arse backwards) Mr. P’s explanation of his fortuitous (and impressively so!) discovery of the autoload workaround.  I was believing that after toggling between 2-channel and multi-channel in Music Settings but before starting the rip, the disk had to be reinserted in order for the change invoked by the toggle step to take affect.  But in fact the rip operation can be done immediately after the toggle, but will not work after reinserting a disk unless and until the Music Settings toggle step is repeated.

 

Takeaway:  Starting from the point where the sacd_extract server is running on the player and the inserted disk has been autoloaded: toggle the setting in Music Settings and then proceed with the rip via sacd_extract or if you prefer, iso2dsd. The toggle action must be repeated immediately after each subsequent disk insertion.

 

 

I've got a Sony BDP-S590 running fw M12.R.0430.  I'm able to get Telnet working.  I can't seem to get the server running on my S590 Which sacd_extract file are you using on the player?  When I used used the Pioneer instructions/file which I think I am supposed to do, running ./sacd_extract_160 -S and it gave me an error similar to below. 

 

On 2/14/2018 at 6:37 PM, Phthalocyanine said:

 

insmod: can't insert '/tmp/filevKgrMe': invalid module format
[0]: install_modules: mknod/insmod filed
rmmod: can't unload 'sacd_read': unknown symbol in module, or unknown parameter
[0]: Can not install modules

 

 

I had run the sacd_extract_160 after changing the music setting as described. 

 

Also - to be sure, I tried the oppo ./sacd_extract -S, I got a libiconv.so.2 missing error.

 

I used the telnet AutoScript files as mentioned by Dick.  Which sacd extract did y'all use to get it to work?

 

Thanks,

Joey

 

 

 

 

[Phthalocyanine]

@Dick Darlington

 

Your post shows you to be both technically adept and a tenacious trouble-shooter.  You suffered from circumstances I did not face (funky USB drive formatting, wrong program name in the text of the script) and you still managed to get ripping to work with the Sony BDP-S590.  Congratulations!

 

A few observations on your points:

 

USB stick partition table problem

The fact that Macs running the latest OS use the GUID partition table by default for formatting USB drives is a quite useful bit of information that may explain problems that some Macs are experiencing with the SACD ripping process.  These older Blu-Ray players may even predate the existence of the GUID partition table.  In any event, the Sony BDP-S590 wants and needs the old MBR partition table.  The easiest method might be to use or borrow a Windows computer to format the USB stick, because Windows uses MBR for formatting USB drives.

 

Now here’s an additional complication just to make life more interesting and difficult.  For doing “local” SACD ripping onto a USB drive with a Sony BDP-S590, the ideal file format is not FAT32 but rather NTFS.  This is because even FAT32 has a built-in limit of 4 GB.  SACDs have the physical structure of a DVD, which means that they can hold up to 4.7 GB.  There are not many but there are a few SACDs, mostly classical concert recordings, that are larger than 4 GB.  So if you rip one of these to a FAT32 drive, it will receive up to 4GB and then truncate the file -- without telling you!

 

(This was also a recognized problem with using the PS3 for local ripping, which could only rip to a FAT32 file system.  Apparently the PS3 would make a file at the 4GB limit but go on to produce another file with the remaining content, and there were programs for combining the two files.)

 

Fortunately, the Sony BDP-S590 will recognize a NTFS formatted USB drive so you can format it way and rip SACD .isos that are larger than 4 GB.  You may not encounter this issue very often, but if you think one of your SACD is long, such as a classical symphony, you should consider using NTFS format for the USB drive.  (For NTSC, of course, like FAT 32, the partition table should also be MBR.)

 

Discrepancy in AutoScript files for Telnet method obtained via a posted Dropbox link

Quote

Eventually I noticed that the contents of the AutoScript files had “inetd” in the Telnet server launching line instead of “telnetd” as shown in the text of Ted’s post.

The text of The AutoScript folder I have been using has two files, Autoscript and Autoscript.TSS, both of which have the following content if you open them up in Notepad (or another text editor):

 

#MTKAT 0.xx script

CLI(CLI_exec echo root::0:0:root,,,:/root:/bin/sh >/etc/passwd)

CLI(CLI_exec /usr/sbin/telnetd &)

SLEEPMS(3000)

CLI(CLI_app.vfdmg.b clear_msg)

CLI(CLI_app.vfdmg.b scroll_msg start)

SLEEPMS(5000)

 

The third line launches the executable program telnetd, which is located in the directory path /usr/sbin.  So if the text in the dropbox file you used inetd instead that’s something different from what I got, and by editing it you got it back to what I’ve been using.

But interesting enough according to Wikipedia

Often called a super-server, inetd listens on designated ports used by Internet services such as FTP, POP3, and telnet. When a TCP packet or UDP packet arrives with a particular destination port number, inetd launches the appropriate server program to handle the connection.

As you note in your take-away, launching inetd could conceivably work on some systems, but not, it seems, the Sony BDP-S590. 

My misinterpretation of the finer points of Mr. P’s autoload “workaround”

Quote

But in fact the rip operation can be done immediately after the toggle, but will not work after reinserting a disk unless and until the Music Settings toggle step is repeated.

The rip operation must be done after the toggle and any reinsertion will put you back to square one.  When you insert a disc at the beginning or reinsert it at any later point, the disc is automounted and cannot be reached by the ripper program.  You must toggle to dislodge the disc from its automount state and while it is in that unmounted state launch the ripper.

[Phthalocyanine]

@n2it

 

Check the text of the files in your folders.

 

The AutoScript folder has two files, Autoscript and Autoscript.TSS, both of which have the following content if you open them up in Notepad (or another text editor):

#MTKAT 0.xx script
CLI(CLI_exec echo root::0:0:root,,,:/root:/bin/sh >/etc/passwd)
CLI(CLI_exec /usr/sbin/telnetd &)
SLEEPMS(3000)
CLI(CLI_app.vfdmg.b clear_msg)
CLI(CLI_app.vfdmg.b scroll_msg start)
SLEEPMS(5000)

The AutoscriptSACD folder has three files, Autoscript, Autoscript.TSS, and sacd_extract_160.

The Autoscript and Autoscript.TSS files both have the following content if you open them up in Notepad (or another text editor):

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

sacd_extract_160 is the correct executable file for the Sony BDP-S590.

[HenkNZ]

@Phthalocyanine Seems the Sony is an option if I cannot get my Oppo going, but the Oppo can play my Bluray of Crime of the Century, which is what I am after.  I am keen to get a good backup of it as it was expensive and I can live with a FLAC version when I travel, for example.

[captainbrent]

1 hour ago, HenkNZ said:

@Phthalocyanine Seems the Sony is an option if I cannot get my Oppo going, but the Oppo can play my Bluray of Crime of the Century, which is what I am after.  I am keen to get a good backup of it as it was expensive and I can live with a FLAC version when I travel, for example.

I'm not sure if I'm misunderstanding your post but this method cannot be used for ripping Bluray Audio's, only SACD's!

[HenkNZ]

@captainbrent @Phthalocyanine Yes, indeed.  Forget the Bluray comment, I was going to say that if I cannot get Oppo to work, I may go Sony for my SACDs

[CatManDo]

If you have a suitable Oppo (103/105), it's worth reading/searching this thread for solutions, instead of trying another player.

 

Most of the time, the issue preventing SACD ripping is with the network (IP adress, firewall), with the file system on the USB stick, the files on the stick, or the computer from which the extraction is started. Nothing to do with the player (when it is a suitable model). You may get the same problems with another player.

[greynolds]

8 hours ago, HenkNZ said:

Ok, so have also checked my Oppo.  It is 103D version.  I do not know if it has the same chipset as the 103.  My unit is in firmware 83-1226.  This may also be an issue.

As I wrote in the post immediately before yours, the BDP-103D is fine.  ALL of the BDP-10x players (with and without the "D" suffix) use the same MediaTek SOC, which is what matters for this SACD ripping trick.  Having a BDP-103D definitely is not a problem - I've been using a BDP-105D for ripping, which is a BDP-103D with better analog audio capabilities.  The firmware version also is not an issue.

 

One thing I'm not sure I've seen mentioned in your posts: did you turn auto play OFF on the Oppo?  If not, that could be the problem.

[n2it]

@Phthalocyanine @Dick Darlington

 

Thanks for you help!  I figured out my problem. 

 

When I first tried, I had inserted the disk and couldn't get it to work on the first try - and eventually the player turned off automatically.  When I restarted (with all the right files), instead of taking the disc out, I left it in.  I did then the music setting toggle and it didn't work (gave me an error).  Finally I had to actually start the disc playing, then toggled the settings and ran the extract program and it worked.  (I finally have my MOFI Dire Straits - Brothers in Arms SACD ripped in DSD! and using a $40 Sony BDP-S590)

 

Of course, it also worked if I inserted the disk, toggled the setting and ran the extract program.

 

So if you leave the disc in and restart without re-inserting it, you need to start it playing first.  

[Dick Darlington]

8 hours ago, Phthalocyanine said:

The third line launches the executable program telnetd, which is located in the directory path /usr/sbin.  So if the text in the dropbox file you used inetd instead that’s something different from what I got, and by editing it you got it back to what I’ve been using.

 

But interesting enough according to Wikipedia

 

Often called a super-server, inetd listens on designated ports used by Internet services such as FTP, POP3, and telnet. When a TCP packet or UDP packet arrives with a particular destination port number, inetd launches the appropriate server program to handle the connection.

 

As you note in your take-away, launching inetd could conceivably work on some systems, but not, it seems, the Sony BDP-S590. 

@Phthalocyanine thank you and thanks for the additional info.

 

Until this morning, I have wrongly believed that the Telnet method is not possible on the Oppo for some reason I knew not what.  My first attempts with the Oppo last year were unsuccessful until I aborted the Telnet method and went with the server method.  I *think* I remember finding a post around that time stating that the Oppos don't have Telnet available.  

 

Maybe I dreamt it; I don't know but I subsequently posted that bit of misinformation myself many months ago, and so if anyone comes across that, please ignore! 

 

I decided to revisit it this morning and lo and behold Telnet works beautifully on the Oppo after all.  It even displays the scrolling "ABCDEFG..." just as stated in @ted_b's instructions.  One thing I forgot to mention in my post yesterday was that the scrolling letters don't manifest on the Sony S590; at least not for me.  What I get instead is the display set to all zeroes, i.e. "0000".

 

However, as it turns out the Oppo does in fact require the "inetd" in the script and NOT "telnetd" as in the Sony's case.  The Oppo contains both the inetd and telnetd binaries in /usr/sbin whereas the Sony has only telnetd.  I looked at the running processes on the Oppo and both inetd and telnetd are running by the time I logon as root; so apparently the former ends up launching the latter. Try as I might I could not set up the script to launch telnetd directly on the Oppo though.  I am guessing it requires so command line options that are supplied automatically by inetd.

 

Soooo ... I set up a Telnet method USB stick that works for both players by including both daemon launch lines with a 1 second wait in between as follows:

 

#MTKAT 0.xx script

CLI(CLI_exec echo root::0:0:root,,,:/root:/bin/sh >/etc/passwd)
CLI(CLI_exec /usr/sbin/inetd &)
SLEEPMS(1000)
CLI(CLI_exec /usr/sbin/telnetd &)
SLEEPMS(3000)
CLI(CLI_app.vfdmg.b clear_msg)
CLI(CLI_app.vfdmg.b scroll_msg start)
SLEEPMS(5000)

 

I then have a second folder, "SACD_Extract" at the root level containing both "sacd_extract" (for the Oppo) and "sacd_extract_160" (for the Sony) and finally a set of text files corresponding to each that I can "cat" in the terminal window to jog my memory in regard to subsequent commands I need to enter.

 

@HenkNZ, I am a loss for suggestions beyond what others have already offered for your case other than you might want to try the Telnet route so that you can manually run sacd_extract on the player side to confirm that it runs okay and then to see if it reacts in anyway when you try and connect with iso2dsd from your Mac.  The caveat here is that Apple decided to protect us all from ourselves and took the telnet client away from us in High Sierra so you will need to find a PuTTY like alternative for your Mac first if you want to go down that path.  Whatever the problem is you can bet it's something really simple.  It always is.  In hindsight anyway.  Good luck!