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

[Kal Rubinson]

4 hours ago, EugenF said:

Indeed Kal!

ISO's ripped with old versions with sacd_extract are ok. Nothing changed fundamentally here.  

In case of dsf/dff files maybe only for those guys who are very sensible to pops/crackles noises.   

Well, there are many variables including the software, hardware and setup along with personal sensitivities.  I had not been aware of the ticks between tracks on the Levine/Mahler but, prompted by this thread, I relistened and noticed them.  Now, they bothered but I cured them by that slight change in JRMC setup.

I also wonder about listening styles as a factor.  Some listen close-up, physically and acoustically, while others, like me, attend to the space/ambiance and, especially with good multichannel recordings, tend to minimize such ticks by regarding them along with random real noises.

[pmarinac]

On 2/16/2020 at 6:14 AM, Kal Rubinson said:

I cannot imagine anything that would justify re-ripping a large library.  I can imagine switching to a new version for subsequent rips.

 

Not so bad really if you kept the iso's somewhere in one place, more or less, and have plenty of disk space. I stored my iso's in the output directories so I had to sweep.exe copy the files back off of my NAS to reprocess them, but definitely worth it.  Batch files are your friend in this case.  Quick re-extract in a windows batch file with the commands:

for /F "usebackq delims==" %%I in (`dir /B *.iso`) do sacd_extract -2 -s -c -i "%%I"
for /F "usebackq delims==" %%I in (`dir /B *.iso`) do sacd_extract -m -s -c -i "%%I"

Kudos to Eugene--really made my day.  The tagging and auto determination if stereo/multi subdirectories and disc directories are needed really helps.  Elimination of the crash on long path/file names, great!  Simplifies the workflow immensely. 

[Kal Rubinson]

1 hour ago, pmarinac said:

Not so bad really if you kept the iso's somewhere in one place, more or less, and have plenty of disk space. I stored my iso's in the output directories so I had to sweep.exe copy the files back off of my NAS to reprocess them, but definitely worth it.  Batch files are your friend in this case.  Quick re-extract in a windows batch file with the commands:

Understood but, even so,it will take an earthshaking enhancement to justify it for the thousands of ISOs I have.  Not gonna do it.

[EugenF]

@pmarinac:  It can be done in one command because sacd_extract can extract stereo and multichannel in a single run:  

for /F "usebackq delims==" %%I in (`dir /B *.iso`) do sacd_extract -2 -m -s -c -i "%%I"

[EugenF]

On 2/16/2020 at 1:24 PM, BlueSkyy said:

Thanks very much!  It would be helpful if you implemented some more definitive version control so people like me don't get mixed up on what we are running.

Starting from now version control is done.

[BlueSkyy]

2 hours ago, EugenF said:

Starting from now version control is done.

 

Yippee!  Excellent for those of us who don't know what we've got!

[EugenF]

4 hours ago, BlueSkyy said:

 

Yippee!  Excellent for those of us who don't know what we've got!

Latest builds:

Version 0.3.9.3-23-gb562b812f5984d6d181dd21961d422c28484c0aa pre-release.

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

 

[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?

[EugenF]

21 minutes ago, haggis999 said:

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?

Version is shown with test button on SACDExtractGUI

or 

sacd_extract -v

And returned:

sacd_extract version 0.3.9.3, built commit hash: 0.3.9.3-23-gb562b812f5984d6d181dd21961d422c28484c0aa
 

Every version of  build is now taken from git commit hash to know what release is.

The future builds will have automatically (from git) numbers like this: 0.3.9.3-24-hash..., 0.3.9.3-25-hash.....

[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?

[austinpop]

While I truly appreciate Eugen's efforts, I just want to share that at least for my setup, I still get the best results (in terms of pops/ticks) with the original SACDExtractGUI linked here.

 

On Eugen's request, I tested his latest 0.3.9.3-23 on the troublesome Mahler 2 - Kaplan Vienna discs. My methodology was to replace the original sacd_extract.exe in the SACDExtractGUI package with Eugen's version. Just to be clear - I am listening for the pop at the track boundary during normal playback - i.e. gapless transition from track n to n+1.

1. @mindsetversion in SACDExtreactGUI - with "padding-less DSF." Pop is still there, but extremely soft. 
2. 0.3.9.3-23 pop is very slightly louder than the @mindsetversion in SACDExtreactGUI - but without "padding-less DSF."
3. 0.3.9.3-23 pop is louder than the @mindsetversion in SACDExtreactGUI - with "padding-less DSF."

Not that I plan to anyway, but I'm not ready to do mass re-rips yet...

[EugenF]

On 2/19/2020 at 1:22 AM, austinpop said:

1. 0.3.9.3-23 pop is very slightly louder than the @mindsetversion in SACDExtreactGUI - but without "padding-less DSF."

Very funny  🙃 . In this case both apps are creating tracks with identical audio content, except mine adds a few more bytes for performer id3 tag. The first track generated by mindset app is bigger because pause is included in it.

[EugenF]

On 2/19/2020 at 1:22 AM, austinpop said:

0.3.9.3-23 pop is louder than the @mindsetversion in SACDExtreactGUI - with "padding-less DSF."

Indeed not working well with -z option.  😥

Now fixed the problem.

Thanks for feedback @austinpop!

[MikeyFresh]

Breaking news out of Germany this morning indicates the Denon DBT-3313UDCI Universal Player can rip SACD using the Sony ARMv7 version of the AutoScript, with no sleep mode or other special tricks needed, tested using SACDExtractGUI.

 

If any members here own that particular player, or any similar vintage Denon/Marantz model, please give that script a try and report back the results.

[austinpop]

Just wanted to give a big shout out to @EugenF and a teaser for a new feature he'll be putting out soon: the concatenate option. This effectively allows you to select a subset of tracks in the ISO, and extract them into one DSF file.

 

The Kaplan Mahler 2 is the perfect use case. Across 2 discs, there are 42 tracks, representing 5 movements. They are:

• Disc 1
  • Movement 1:       tracks 1-14
• Disc 2
  • Movement 2:       tracks 1-5
  • Movement 3:       tracks 6-14
  • Movement 4:       track 15
  • Movement 5:       track 16-28

Using this new version, I was able to extract 5 dsf files - each dsf file requires a separate pass, or invocation of sacd_extract. These extractions go rather quickly, so it's not a big burden to run multiple passes.

 

This is a huge advance. It effectively solves the pops problem with this Mahler disc, and others like it that have track boundaries within a movement. While there is still a pop between movements, it's really not an issue anymore. And I believe Eugen is working to eliminate that pop as well.

 

Kudos - and looking forward to the release version.

[MikeyFresh]

On 9/14/2016 at 10:13 PM, KenKJS said:

Has anyone tried this with the Denon DBT-3313UD?

 

My understanding is that it uses the Mediatek MT8580 SoC for video processing.

 

On 10/6/2016 at 9:01 AM, jpu018 said:

Bump

Can anybody confirm/comment ?

 

Yes it does work, all this time later.

 

The Sony ARMv7 AutoScript is fully compatible with this Denon model as mentioned one week ago. It stands to reason the very similar but slightly less well appointed DBT-1713UD model will also work, however that still needs to be tested. I hope to test the DBT-1713UD on Monday evening. 

[MikeyFresh]

After testing with various methods and scripts, It appears the Denon DBT-1713UD is incompatible.

 

While similar looking to the now known compatible DBT-3313UD, there are significant differences between these two units, for instance the MediaTek SoC employed. The known compatible 3313UD model utilizes the MT8580, while the seemingly incompatible 1713UD model uses the MT8555.

 

While that MT8555 chip is used in certain other compatible units, notably the Oppo BDP-103, there must be something else different in the 1713UD model's Linux kernel, as all attempts with every script version including the various AutoRip scripts has failed.

 

If anyone has any thoughts as to something to check or try with the DBT-1713UD,  I'm all ears, otherwise we'll have to mark this one down as incompatible.

[alexanderdemaet]

I have a Cambridge Azur 752BD and everything works except ; 

Version:  1.20
        Area Description Phonetic: Armenian Spirit
        Track Count: 18
        Speaker config: 5 Channel
        Track list [1]:
                Title[0]: Menk kaj tohmi
                Title[1]: Ana krunk
                Title[2]: Kani vordjan im
                Title[3]: Chant et Danse
                Title[4]: O'h intsh anush
                Title[5]: Matshkal
                Title[6]: Solo kamantcha: Dun en glkhen
                Title[7]: Garun a
                Title[8]: Chants de mariage
                Title[9]: Al aylukhs
                Title[10]: Plainte: en sarer II
                Title[11]: Azat astvatsn - Ter kedzo
                Title[12]: Sirt im sasani
                Title[13]: Hayastan yerkir
                Title[14]: Hey djan
                Title[15]: Hov arek
                Title[16]: Lamento: sev mut amper
                Title[17]: Alagyeaz - Khnki tsar
Processing [Armenian Spirit.iso] (1/1)..
We are done..

[alexanderdemaet]

Got a newer version of Sacd extract and it worked!! 

[rwwjr44]

What and where is the latest version of SACD extract? 

 

Thanks

[tngiloy]

I need help.

 

I have used this way to rip 50+  sacd's over the past couple years. 

I have recently moved the Oppo 103 to a new location in my house. Same internet/modem. 

Turned on Oppo. Plugged in the same thumbdrive I have been using. The drawer didn't open. Power cycled Oppo and tried again. Drawer still didn't open.

I Opened the 'iso2dsd_gui.exe' on my laptop and double checked the ip address and it was the same. Hit 'execute' and after a little while I got the 'failed to connect' error message. Checked the thumbdrive and all 3 AutoScript files were on there, but as I read the instructions it states that the files should be in a folder named Autoscript in the root drive.

So I created a new folder on the thumbdrive, moved the 3 files to 'new folder', and then renamed folder 'AutoScript'. Power cycled the 103, inserted thumbdrive and still no joy. Still get 'failed to connect'.

Turned off and disconnected VPN just in case and still won't work.  Unplugged the Oppo wireless adapter and hardwired the network connection, still nothing.

What am I missing? What am I doing wrong?

[Crwilli57]

Re-read your post, not IP address.  
 

good luck

[tngiloy]

Thanks

No. it was one of the things I checked. The Oppo's address is the same. I'll triple check to make sure, but I don't think that's it.

The only thing I can think to do that I haven't tried, is to get a new thumbdrive. Possible that after a few years it has become corrupted somehow.

[tngiloy]

Whoops. I checked the rear of my Oppo and I had left a thumbdrive plugged in that I had stored my backup settings on. I removed it, plugged in the Auto Script thumbdrive in the front usb slot and the drawer opened as it should.

I'm expecting a couple sacd's in the next few days and will test then, but I think that fixed it.

Duh,

Tom

[chichaz]

On 3/11/2020 at 11:01 AM, tngiloy said:

Whoops. I checked the rear of my Oppo and I had left a thumbdrive plugged in that I had stored my backup settings on. I removed it, plugged in the Auto Script thumbdrive in the front usb slot and the drawer opened as it should.

I'm expecting a couple sacd's in the next few days and will test then, but I think that fixed it.

Duh,

Tom

Yes, having another thumb drive connected likely prevented the Oppo's firmware from running the script off the correct one. We all make mistakes, it's human.

P.S. Everyone please wash your hands! #NoMoreCovid-19