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

[haggis999]

1 hour ago, Nexus3 said:

 

Hi haggis999,

 

you may want to checkout page 148 ?.

 

Aargh!!! I wish I'd seen those links before wading through all that Ubuntu stuff. I've only just returned to the forum and probably missed most of page 148. Unfortunately, I appear to have given Mindset and Richard Dale the impression that I actually wanted to run my own compilation for Windows. Their help was appreciated, but it was based on a misunderstanding in this case.

 

I will now have another go at making SACDExtractGUI do its stuff.

[haggis999]

27 minutes ago, Richard Dale said:

No problem with helping you out! Although I don't own any sacds or an sacd player I had an interesting time finding out about the sacd ripping software. I saw you mention cmake and jumped in to help as I use it quite a lot in my job, but unfortunately without having the context of page 148..

 

Thanks Richard. I realise you were doing your best to be helpful. We were both in the dark about p148. ?

 

Now that I have obtained the new version of sacd_extract.exe, my testing of SACDExtractGUI has proved successful so far, with one exception.

 

Several initial attempts to rip to a stereo DSF and a multi-channel DSF at the same time simply ended within 30 secs, without any results or any error messages. This started working only at about the fifth attempt.

 

EDIT:  My first rip to both stereo and multi-channel paddingless DSFs took about 16 1/2 mins, which I'm sure is several minutes faster than with ISO2DSD. The stereo rips were completed before the multi-channel rips started, so the process is sequential rather than simultaneous.

[haggis999]

3 hours ago, haggis999 said:

My first rip to both stereo and multi-channel paddingless DSFs took about 16 1/2 mins, which I'm sure is several minutes faster than with ISO2DSD. The stereo rips were completed before the multi-channel rips started, so the process is sequential rather than simultaneous.

 

2 hours ago, mindset said:

Somebody submitted a fix for that to github recently, but the executable you got had been probably created before that.  If you had succeeded in compiling sacd_extract, you would have picked the latest which includes that fix.

 

 

I have just re-ripped that same SACD using my previous ISO2DSD process. It took just under 22 mins to rip it in both stereo and multi-channel mode. That means SACDExtractGUI + sacd_extract 0.3.9 provided a worthwhile time saving of over 5 mins. If the later version of sacd_extract.exe can speed that up even more by running stereo and multi-channel rips in parallel then so much the better.

 

Now, all I need is for some kind person to post a link to a Windows compilation of the newer sacd_extract.exe!

[haggis999]

5 hours ago, mindset said:

It won't be any faster.  You are most likely limited by the player side's optical drive.  Plus, stereo and multi-channel cannot be read in parallel.  They are recorded at two separate locations and there is only one optical head in the drive.

 

Your earlier post advising me that a problem had recently been fixed by an update to sacd_extract.exe was attached to a quote from one of my posts. That quote referred to the stereo and multi-channel rips being read in sequence rather than in parallel, so I just assumed that was the problem in question.

 

Did you really mean to quote a different part of my post that referred to erratic starting of the ripping process? If not, then what issue was addressed by the update (I tried checking your Github link but couldn't find anything relevant)?

[haggis999]

30 minutes ago, wedgeworld said:

I just realized I never looked at the top for a player model. I have been unable to rip my first SACD. I have the Oppo 105D and the packet I downloaded from your dropbox just says SACD. No brand or model.  Is it possible my issues are because I don't have the correct autoscript for my player?

 

If you check Page 1 of this thread you will see a link to my detailed instructions for ripping SACDs using an Oppo 103 or 105. This contains links to all the required files.

 

[haggis999]

1 hour ago, nUUK25 said:

…..OPPO BDP-103eu is also a rip alternativ Bluray player to the mentioned Sony models ?

 

Yes, both the Oppo BDP-103EU and the BDP-105EU are capable of ripping SACDs.

[haggis999]

Will SACDExtractGUI ever emulate the capabilities of dBpoweramp?

 

I have been ripping my growing SACD collection using my Oppo 105 ever since I discovered this forum thread about 3 years ago. The latest SACDExtractGUI software does an excellent job, with one significant exception - there is no mechanism for controlling the DSF filenames, folder names and metadata in the highly sophisticated manner I am used to when ripping CDs using dBpoweramp (via profile settings and manual editing of metadata sourced from several online sources before starting a rip).

 

Almost all my recordings are of classical music and getting these things right is a vital requirement for properly organising my collection. At present, I am forced to do almost all of this manually after ripping a SACD, though I always rip the CD layer with DBpoweramp, which gives me a source for copying and pasting metadata to the DSF files,   

 

Is this a situation that is ever likely to improve or is it technically impossible to achieve dBpoweramp-style functionality when ripping SACDs?

[haggis999]

1 hour ago, EugenF said:

Latest builds:

Version 0.3.9.3-23-gb562b812f5984d6d181dd21961d422c28484c0aa pre-release.

https://github.com/EuFlo/sacd-ripper/releases/tag/0.3.9.3

 

I've just downloaded this latest version, but SACDExtractGUI only appears to display its own version number. I can't see any reference to what version of sacd_extract.exe is being run. Do I need new glasses or have I misunderstood what you mean by version control?

[haggis999]

3 minutes ago, EugenF said:

Version is shown with test button on SACDExtractGUI

 

I was just about to post back that the Test button didn't give me any version info, but then I noticed a second Test button on the top right corner and that did the trick.

 

Two buttons with the same name isn't ideal. Is anyone offering a later compilation of SACDExtractGUI than the version v0.1-5-g97d05f95 I am using?

[haggis999]

37 minutes ago, David_B said:

Hope it's ok to post this here. Seems like a lot of Oppo experts, so here goes: I’m usually good at this kind of thing myself, but I must have set something up wrong, and want to see if there’s anyone in this group with a solution. I have two Blu-Ray players which also play SACD. A Sony unit, and an Oppo BDP-103; both feed into my Yamaha Rx-A 680, via HDMI. The issue is that when trying to play an SACD on the Oppo, it’s being converted to PCM, instead of being played as DSD. Doesn’t happen with the Sony. Informed suggestions welcome. TIA.

Assuming that the Oppo BDP-103 interface is the same as my BDP-105, you simply go to the Setup Menu and select Audio Format Setup/SACD Output. You then have a choice of Auto, PCM or DSD.

[haggis999]

I haven't been actively checking this forum thread for 9 months.

 

I would be very grateful if someone can please save me the trouble of ploughing through all the posts over that period and tell me where to find the latest compilation of SACDExtractGUI and the latest version of sacd_extract.exe.

[haggis999]

SACDExtractGUI is a significant improvement on ISO2DSD. I'm aware it's on GitHub but it needs compiling, which is beyond my capability at present.

[haggis999]

The SACDExtractGUI dialogue box makes a reference to https://github.com/setmind/SACDExtractGUI.git, but this requires compilation skills.

 

I've now found a source at https://www.videohelp.com/software/sacd-extract, which provides download links for both a compiled version of SACDExtractGUI v0.1-7-g135cbd5d and a copy of a compatible version of sacd_extract.exe.

 

Problem solved.

 

EDIT:  Since writing the above, I have now found that compiled code is indeed available from that GitHub link. It's reached via the Releases section in the right hand sidebar. You can tell I'm not familiar with GitHub...

[haggis999]

4 hours ago, Lkdog said:

OK, I apologize in advance but I am stuck getting this to work on my OPPO 105 and Win 10 system network.

I downloaded the files and followed the instructions using SONORE on this document.

 

Ripping SACD using Sonore

 

It took me awhile to be able to get the JAR file with the Sonore app open but finally got that going using a program called JAR Executer.

 

I have the USB stick in the OPPO with the Autoscript Folder and the three files in it.

Loaded the SACD.

 

I put the network address for the OPPO into the Server Input screen in SONORE.

192.168.1.101  (I removed the 2002 at the end of the address, and then put it back. Neither way works).

I set it for DUAL and SONY DSF.

 

I hit EXECUTE and get nothing.

Tried both wireless and hard wired.

 

The OPPO is working on my network as I use J River to play files on it.

Any ideas as to what I am doing wrong here?

 

Thanks.

Do the 3 files in your Autoscript folder have exactly the same names as shown in the fourth bullet point on my instructions? It's important that only one of them has a file extension. When you powered up the Oppo 105 with the USB stick plugged in did the drawer open automatically after a few seconds?

[haggis999]

8 minutes ago, Lkdog said:

 

Thank you for your time. Things seemed to be going fine until I tried to open the JAR file to open the SONORE application. Finally got that going.

 

SONORE application just doesn't talk to the OPPO. Everything looks like it should in the SONORE application.

 

The files are exactly as your instructions require:

 

AutoScript
AutoScript.TSS
sacd_extract
 

They are in the folder labeled AutoScript. Nothing else on the USB stick.

 

When I power up the OPPO with the USB stick plugged in the drawer opens halfway and shuts quickly.

The OPPO says USB IN.

I reopen the drawer and put in an SACD and it loads normally.

I have turned off Auto play and Auto resume.

 

No luck when I hit EXECUTE in SONORE. 😞

 

 

 

If you open a cmd prompt in Windows and enter Ping 192.168.1.101, do you get a response from your Oppo?