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

[Dick Darlington]

4 minutes ago, salk81 said:

Right, thanks for pointing out that mistake.  Even if I were to correct that, I still have a problem because my player is not a 103 or 105,  Right?

As far as I know that is correct since as previously noted, the BDP-95 doesn’t support SACD ripping. 

[salk81]

I guess I am stuck then as I can't seem to find any players listed to work with ISO2DSD

[MikeyFresh]

12 minutes ago, salk81 said:

I guess I am stuck then as I can't seem to find any players listed to work with ISO2DSD

 

The list of known compatible units is here.

[Phthalocyanine]

40 minutes ago, salk81 said:

I guess I am stuck then as I can't seem to find any players listed to work with ISO2DSD

There is another method that does not use ISO2DSD and which allows you to do more trouble-shooting but also requires more steps -- telnet with local ripping.

I can send you a guide for doing that with a Sony if you are interested.

[salk81]

 That would be much appreciated, I shall wait for it 

[hyendaudio]

On 2/13/2019 at 6:23 PM, hyendaudio said:

I wasn't presuming anything, just advising that I'd be offline for a bit and not responding to follow ups. I too have a day job and don't carry SACD players around my pocket 😎. I certainly dont expect anyone to hang around waiting for me.

 

That said: I do have the full iso2dsd distribution in the folder; I'd forgotten that the other 2 files were part of the package. However, since I've been through several iterations of code, config, and folders during this troubleshooting exercise I think it makes sense to clean up - the folder I created for this is a bit of a mess now - and start fresh with the consolidated instructions you and Phthalocyanine have so generously and patiently provided. I will do this over the next 2-3 days (as time permits - tomorrow is pre-committed and I hope you don't need me to explain why 💘) and report back.

 

Just to highlight:  I am really appreciative of your help here.

 

Thank you. 

OK, cleanup completed, and all instructions followed exactly. I even downloaded and extracted a fresh copy of iso2dsd from Sonore and created a brand now folder at the root level of my drive. Same problem. I'm going to look for a Sony BDP-S series player and see if that solves my problem. 

[Phthalocyanine]

20 minutes ago, hyendaudio said:

I'm going to look for a Sony BDP-S series player and see if that solves my problem. 

Good idea.  If you get the same problems with the Sony then you know there's some fundamental problem with your network connection or something else.  If you get the Sony to work then you can try to figure out what's going wrong with the Pioneer knowing that your other fundamentals are OK.

[hyendaudio]

1 minute ago, Phthalocyanine said:

Good idea.  If you get the same problems with the Sony then you know there's some fundamental problem with your network connection or something else.  If you get the Sony to work then you can try to figure out what's going wrong with the Pioneer knowing that your other fundamentals are OK.

Sony BDPS-S590 should be here tomorrow. Stay tuned.

 

On 2/11/2019 at 7:30 PM, MikeyFresh said:

 

Do you want to try the server method instead?

 

No reason why the local method and Telnet shouldn't work with that unit, but maybe you will have better luck with the server method as an alternative.

Hi MikeyFresh.

 

I just replied to your PM as well. I've gone to the DropBox link you provided (re-publishing here for anyone else who's interested, as I had to search a bit to find one the first time - BDP-160 AutoScript) and I still get the same result. The player boots fine off the USB drive and the door opens. I load a CD and the player reads it, properly identifying it as an SACD. I then ran Sonore's iso2dsd application (I'm guessing that's what you mean by "server method"), correctly entering the pingable IP address (192.168.0.160) with the default port of 2002 and the result is: Failed to connect libsacdread: Can't open 192.168.0.160:2002 for reading. 

 

Thank you again. 

 

Should I throw in the towel on this player and go for a Sony? I'm reluctant to try an Oppo as according to what I've read, if the firmware's been updated it won't work.

[superstar19]

8 minutes ago, hyendaudio said:

Sony BDPS-S590 should be here tomorrow. Stay tuned.

 

Hi MikeyFresh.

 

I just replied to your PM as well. I've gone to the DropBox link you provided (re-publishing here for anyone else who's interested, as I had to search a bit to find one the first time - BDP-160 AutoScript) and I still get the same result. The player boots fine off the USB drive and the door opens. I load a CD and the player reads it, properly identifying it as an SACD. I then ran Sonore's iso2dsd application (I'm guessing that's what you mean by "server method"), correctly entering the pingable IP address (192.168.0.160) with the default port of 2002 and the result is: Failed to connect libsacdread: Can't open 192.168.0.160:2002 for reading. 

 

Thank you again. 

 

Should I throw in the towel on this player and go for a Sony? I'm reluctant to try an Oppo as according to what I've read, if the firmware's been updated it won't work.

Have you tried a different USB drive? I was getting similar results with 32 or 64GB drive and then tried an older 2GB USB drive and everything worked after that.

[MikeyFresh]

32 minutes ago, hyendaudio said:

 

I just replied to your PM as well.

 

I did not get any further replies.

 

32 minutes ago, hyendaudio said:

I've gone to the DropBox link you provided (re-publishing here for anyone else who's interested, as I had to search a bit to find one the first time - BDP-160 AutoScript)

 

As stated previously (sorry for the repeat but I'm hoping others can avoid confusion), that link has caused many others a problem in that it points to the content of the AutoScript folder rather than the enclosing folder itself. Use the Download button in the upper right-hand side of the Drop Box GUI to download the correct thing.

 

35 minutes ago, hyendaudio said:

Should I throw in the towel on this player and go for a Sony?

 

No I think you should stop trying to run the program from the NAS as you stated in your original PM, and place that folder onto the PC itself. Or if you are sure that program should run from the NAS, then ask yourself if Java 8 was installed on that NAS or not? 64-bit Windows?

 

[greynolds]

 

1 hour ago, hyendaudio said:

 I'm reluctant to try an Oppo as according to what I've read, if the firmware's been updated it won't work.

 

Why do we keep revisiting this???  It's like Groundhog Day.

 

As stated over and over in this thread, that is NOT true.  All Oppo BDP-10x players (BDP-103, BDP-105, BDP-103D, and BDP-105D) will work with any firmware version, including the latest.  The only reason to avoid the supported Oppo players is to go with less expensive options.

[captainbrent]

4 minutes ago, greynolds said:

 

Why do we keep revisiting this???  It's like Groundhog Day.

 

As stated over and over in this thread, that is NOT true.  All Oppo BDP-10x players (BDP-103, BDP-105, BDP-103D, and BDP-105D) will work with any firmware version, including the latest.  The only reason to avoid the supported Oppo players is to go with less expensive options.

Agreed, but we should probably remind folks that it is official stock Oppo firmwares that are known to work and that any hacked firmwares, could very well not work.

[greynolds]

10 minutes ago, captainbrent said:

Agreed, but we should probably remind folks that it is official stock Oppo firmwares that are known to work and that any hacked firmwares, could very well not work.

That would apply to anything though.  If you install hacked firmware on ANY device, you have to be willing to accept any consequences that come with it.

[MikeyFresh]

3 hours ago, hyendaudio said:

Hi MikeyFresh.

 

I just replied to your PM as well. I've gone to the DropBox link you provided (re-publishing here for anyone else who's interested, as I had to search a bit to find one the first time - BDP-160 AutoScript) and I still get the same result. The player boots fine off the USB drive and the door opens. I load a CD and the player reads it, properly identifying it as an SACD. I then ran Sonore's iso2dsd application (I'm guessing that's what you mean by "server method"), correctly entering the pingable IP address (192.168.0.160) with the default port of 2002 and the result is: Failed to connect libsacdread: Can't open 192.168.0.160:2002 for reading. 

 

Thank you again. 

 

Should I throw in the towel on this player and go for a Sony? I'm reluctant to try an Oppo as according to what I've read, if the firmware's been updated it won't work.

 

I thought the above posted earlier today looked very familiar.

 

Turns out it is an exact copy and paste copy from Tuesday at 5:18pm. So even though the post from that date was answered, you copied and pasted it here again? Good luck with this tact.

[hyendaudio]

2 hours ago, MikeyFresh said:

 

I did not get any further replies.

 

 

As stated previously (sorry for the repeat but I'm hoping others can avoid confusion), that link has caused many others a problem in that it points to the content of the AutoScript folder rather than the enclosing folder itself. Use the Download button in the upper right-hand side of the Drop Box GUI to download the correct thing.

 

 

No I think you should stop trying to run the program from the NAS as you stated in your original PM, and place that folder onto the PC itself. Or if you are sure that program should run from the NAS, then ask yourself if Java 8 was installed on that NAS or not? 64-bit Windows?

 

no reason in the world why it wouldn't work from a mounted drive but I had tried that initially anyway, and AGAIN as you had recommended it, and I am nothing if not thorough when I go through my troubleshooting procedures. Windows 10 is 64x by default and yes - as you can see in the screenshot below, it is 64 bit Windows, v10 (although I admit I do run a fairly old PC). ISO2DSD won't load if there is an issue with the version of the OS or Java and yes, Java 8 is installed. The problem is not in launching the app, the problem is in connecting to the player, which is refusing telnet and iso2dsd connection requests. 

 

No further replies as of yet because I am at work (from home today, as it happens, which is why I was able to take a few minutes to work on this) and had other matters to attend to. I apologize if I cannot be available on a moment's notice to attend to your requests - which is precisely the reason why, earlier this week, I notified you and others who are monitoring this thread that I would be offline for a bit.  It didn't occur to me that an hour here or there would be that important. 

 

I hope you'll forgive my irritation but I am a bit put off by the aggressiveness in the replies. Whereas I understand your frustration with having to address download procedures which likely resulted in many requests for assistance when setting up the autoscript folder and its contents, please note that I am new to this thread and had no previous knowledge of this issue - I certainly didn't have it. That said, I am not a novice here. As I stated in an earlier PM to you, I know my way around operating systems and application installation and support, ethernet (and other) networks and electronics (I won't go into my experiences or specific skill sets here). I replied previously that I am going to try this with a different player, as I suspect the issue may be with the one I'm using. 

 

I will reply back to this thread when I have further updates; likely sometime Sunday or Monday. 

 

Wishing everyone a pleasant holiday weekend...

[hyendaudio]

38 minutes ago, MikeyFresh said:

 

I thought the above posted earlier today looked very familiar.

 

Turns out it is an exact copy and paste copy from Tuesday at 5:18pm. So even though the post from that date was answered, you copied and pasted it here again? Good luck with this tact.

Actually, I did not copy and paste anything. I was replying to a thread. Not sure what makes you think I am reposting this?

[MikeyFresh]

6 minutes ago, hyendaudio said:

Not sure what makes you think I am reposting this?

 

Because the same exact thing (word for word) is posted above 3 hours ago, and also last Tuesday. Good luck with the S590.

[captainbrent]

1 hour ago, greynolds said:

That would apply to anything though.  If you install hacked firmware on ANY device, you have to be willing to accept any consequences that come with it.

Yes, that goes without saying but, there's always someone....

[hyendaudio]

19 minutes ago, MikeyFresh said:

 

Because the same exact thing (word for word) is posted above 3 hours ago, and also last Tuesday. Good luck with the S590.

I suspect someone quoted my reply from last Tuesday (could have been me, in which case I do apologize!). 

 

Considering that this is now working, I've cancelled the order for the S590.

 

Thanks again for your help!

[Phthalocyanine]

2 minutes ago, hyendaudio said:

Considering that this is now working,

Great!  At your convenience, when you have a moment in the next week or so and feel like it, could you satisfy our curiosity about what the problem was, if it is now clear.  Happy Ripping!

[Dick Darlington]

@hyendaudio it seems likely that although your AutoScript is being launched, which is the only way your tray would open, sacd_extract is not running. This assumes there are no firewall or network issues of course. One scenario that could cause this would be if your USB is not mounting as SDA1. I once had fits with a weirdly formatted usb stick that mounted as SDA. Period. Not SD some letter some number; just SDA. Apparently it is possible to format a disk with a volume and yet zero partitions, but I will go to the grave not knowing how to reproduce it. But I digress. Point is if your script assumes SDA1 as is the norm, but your AutoScript volume is anything else, then yes the tray opening command will work. And yes the ABCDEFG display command will work, but you gonna be sol when it comes to sacd_extract. 

 

OTOH there could be something else preventing sacd_extract from running. So basically what you really need is Telnet so you can see WTF is going on. So imho I would focus on establishing a Telnet connection and worry about the ripping thing later. To that end, remember that some players require launching inetd to invoke Telnet and others require telnetd. I can’t recall how that shakes out atm. 

[Dick Darlington]

1 minute ago, Dick Darlington said:

@hyendaudio it seems likely that ...

 

 

Er uh ... never mind. 😔 

 

Congratulations 🍾🎉 though. 

[hyendaudio]

35 minutes ago, Dick Darlington said:

@hyendaudio it seems likely that although your AutoScript is being launched, which is the only way your tray would open, sacd_extract is not running. This assumes there are no firewall or network issues of course. One scenario that could cause this would be if your USB is not mounting as SDA1. I once had fits with a weirdly formatted usb stick that mounted as SDA. Period. Not SD some letter some number; just SDA. Apparently it is possible to format a disk with a volume and yet zero partitions, but I will go to the grave not knowing how to reproduce it. But I digress. Point is if your script assumes SDA1 as is the norm, but your AutoScript volume is anything else, then yes the tray opening command will work. And yes the ABCDEFG display command will work, but you gonna be sol when it comes to sacd_extract. 

 

OTOH there could be something else preventing sacd_extract from running. So basically what you really need is Telnet so you can see WTF is going on. So imho I would focus on establishing a Telnet connection and worry about the ripping thing later. To that end, remember that some players require launching inetd to invoke Telnet and others require telnetd. I can’t recall how that shakes out atm. 

This all makes sense, but considering that I was never able to open a telnet session it was impossible to see the mount point of the USB drive. It's likely the firmware with the usb drive (a handout from an IT vendor whom I won't implicate as I'm quite sure they never anticipated my use case 👹) caused some unexpected behavior. 

 

The solution was to use a different USB thumb drive. We know that PNY 512MB drives work. Now. 

 

So I guess if everything else works but connections to the player are refused, one recommendation would be to try a different, freshly formatted drive. A name brand drive wouldn't hurt...

 

I guess we can this to the growing database of USB drive known issues or incompatibilities. 

 

Epilogue:  I couldn't cancel the order for the Sony BDP-S590n before I ship it back anyone who wants it is welcome to it. Its refurbished with a 30 day warranty for $80 (I paid $79.92, I might just keep the $0.08 as my profit)

[hyendaudio]

47 minutes ago, Dick Darlington said:

 

Er uh ... never mind. 😔 

 

Congratulations 🍾🎉 though. 

Still, valuable input. And thank you! Gonna see how my 1st rip came out now.

[salk81]

4 minutes ago, hyendaudio said:

This all makes sense, but considering that I was never able to open a telnet session it was impossible to see the mount point of the USB drive. It's likely the firmware with the usb drive (a handout from an IT vendor whom I won't implicate as I'm quite sure they never anticipated my use case 👹) caused some unexpected behavior. 

 

The solution was to use a different USB thumb drive. We know that PNY 512MB drives work. Now. 

 

So I guess if everything else works but connections to the player are refused, one recommendation would be to try a different, freshly formatted drive. A name brand drive wouldn't hurt...

 

I guess we can this to the growing database of USB drive known issues or incompatibilities. 

 

Epilogue:  I couldn't cancel the order for the Sony BDP-S590n before I ship it back anyone who wants it is welcome to it. Its refurbished with a 30 day warranty for $80 (I paid $79.92, I might just keep the $0.08 as my profit)

I'd be happy to get my hands on it