Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Matt]

SACD to DSF
MC34 can extract your SACD ISO files to DSF files. This makes the tracks from an SACD easier to manage. The files are created next to the ISO from the SACD. 

There is no data transformation or loss in the conversion process. It's simply copying the data out and flipping the byte ordering. It's similar to the tool sacd_extract.

Instructions
Right-click SACD tracks and pick “Convert SACD to DSF”.

The process runs in the Action Window threaded.

[Awesome Donkey]

Worth noting that the word convert used here doesn't mean it's resampled or goes through a PCM stage in the middle, it extracts the data from a SACD ISO and puts it into an individual DSF file, just like sacd_extract can do.

[Matt]

Good point! I'll update the original post as well.

[Awesome Donkey]

Thinking about it more, the Convert SACD to DSF wording could cause confusion as well, I can kinda see in the future questions asking about that. Maybe Extract DSF from SACD or something like would be better?

[Outlaw Audio]

SACD to DSF
MC34 can extract your SACD ISO files to DSF files. This makes the tracks from an SACD easier to manage. The files are created next to the ISO from the SACD. 

There is no data transformation or loss in the conversion process. It's simply copying the data out and flipping the byte ordering. It's similar to the tool sacd_extract.

Instructions
Right-click SACD tracks and pick “Convert SACD to DSF”.

The process runs in the Action Window threaded.

This is a worthy addition to Media Center's capabilities and is compelling for an upgrade.  Thanks Matt, now I can get rid of my Java client, upgrades and SACD_Extract GUI

[chef]

I agree, great new feature!

[dtc]

Thinking about it more, the Convert SACD to DSF wording could cause confusion as well, I can kinda see in the future questions asking about that. Maybe Extract DSF from SACD or something like would be better?

Agreed - extract takes away any connection about what convert does will DSD files.

Or

SACD - Extract to DSF

[margolbe]

This is a good feature.  For hybrid discs, would it be possible to create separate folders for 2 ch and 5 channel extractions.  A program like X-recode does this.

[Awesome Donkey]

Having options to extract stereo tracks and/or multichannel tracks only might be worth doing as well. Personally I'd only have interest in the stereo tracks.

[TheShoe]

I'd like to have the option for either, stereo or multi-channel.

This is a nice feature however when I do full ISO backups via sacd_extract, it's easy enough there to just do the DSF extract as well.

Would it be possible to shell out to sacd_extract to do the initial backup?  Obviously there's some settings that would need to be specified, eg the IP of the device doing the ripping.

[JrPinto]

Testing the new feature, I realize that the files names have the same name of the ISO file followed by the number of the track.

Is there some way to modify the settings so the names of the files could be created using the tag fields we want, by the time of the conversion?

Thanx.

[bob]

I'd like to have the option for either, stereo or multi-channel.

This is a nice feature however when I do full ISO backups via sacd_extract, it's easy enough there to just do the DSF extract as well.

Would it be possible to shell out to sacd_extract to do the initial backup?  Obviously there's some settings that would need to be specified, eg the IP of the device doing the ripping.

That's an interesting idea. I for one could use that.
Perhaps an external ripper interface like the external encoder interface??

[Awesome Donkey]

If you're going to allow using sacd_extract externally, it might be wise to use a specific fork or forks of sacd_extract that are better maintained and have bug fixes (e.g. the old issue when extracting .dsf causing pops that was fixed in newer sacd_extract forks).

[bob]

If you're going to allow using sacd_extract externally, it might be wise to use a specific fork or forks of sacd_extract that are better maintained and have bug fixes (e.g. the old issue when extracting .dsf causing pops that was fixed in newer sacd_extract forks).

I've been using the setmind version 0.3.9 IIRC. Seems to work well.

[Awesome Donkey]

I've been using the setmind version 0.3.9 IIRC. Seems to work well.

This one is a newer fork since the setmind fork hasn't been updated in 6 years (though it still works): https://github.com/EuFlo/sacd-ripper/releases

It even works on Mac/ARM (Apple Silicon) too!

[Matthew.Burt360]

Just wanted to add to this some issues I've had with this the past couple of days as it has cost me some serious time. (Tested on multiple SACD ISOs from differing sources)
----
Extracting DSF files from SACD ISOs in JRiver results in serious problems:

Incorrect "length" metadata: Files only play an average 20% of their duration on hardware players (e.g., Astell & Kern SR35), even though the audio is full-length.

Lower volume after DSD→DSD conversion: Even with DSP and Volume Leveling disabled, converted DSF files are noticeably quieter. (Maybe silent DSD to PCM to DSD conversion causing this)

Impact:
Files look fine inside JRiver but fail on real-world players. Users must re-extract ISOs using ISO2DSD or sacd_extract to get properly working DSFs.

Request:

Fix SACD extraction to write correct DSF headers (sampleCount/duration).

Ensure DSD→DSD conversions are truly bit-perfect.

System Info:
JRiver [34.0.19] • Windows [11] • Tested on Astell & Kern SR35

Thanks!

[JimH]

Astell & Kern has had other problems.   Try searching.  Test without A&K.

[Bumfuzzle]

Lower volume after DSD→DSD conversion: Even with DSP and Volume Leveling disabled, converted DSF files are noticeably quieter. (Maybe silent DSD to PCM to DSD conversion causing this)

Impact:
Files look fine inside JRiver but fail on real-world players. Users must re-extract ISOs using ISO2DSD or sacd_extract to get properly working DSFs.

Request:

Fix SACD extraction to write correct DSF headers (sampleCount/duration).

Ensure DSD→DSD conversions are truly bit-perfect.


Thanks!

I don't think it's about your system or configuration. There are easily detectable audio quality differences when extracted via JRiver 34.0.19...

[bob]

Just wanted to add to this some issues I've had with this the past couple of days as it has cost me some serious time. (Tested on multiple SACD ISOs from differing sources)
----
Extracting DSF files from SACD ISOs in JRiver results in serious problems:

Incorrect "length" metadata: Files only play an average 20% of their duration on hardware players (e.g., Astell & Kern SR35), even though the audio is full-length.

Lower volume after DSD→DSD conversion: Even with DSP and Volume Leveling disabled, converted DSF files are noticeably quieter. (Maybe silent DSD to PCM to DSD conversion causing this)

Impact:
Files look fine inside JRiver but fail on real-world players. Users must re-extract ISOs using ISO2DSD or sacd_extract to get properly working DSFs.

Request:

Fix SACD extraction to write correct DSF headers (sampleCount/duration).

Ensure DSD→DSD conversions are truly bit-perfect.

System Info:
JRiver [34.0.19] • Windows [11] • Tested on Astell & Kern SR35

Thanks!

Please give 34.0.20 a try, thanks.

[GrahamG]

Useful feature though I use iso2dsd to do this which is free and works fine (also works for the multichannel layer if present) so I'll probably stick to that. For me, the key advantage of dsf files is the ability to tag them with metadata.

[bob]

Useful feature though I use iso2dsd to do this which is free and works fine (also works for the multichannel layer if present) so I'll probably stick to that. For me, the key advantage of dsf files is the ability to tag them with metadata.

When I converted my SACD to DSF the tagging was carried over to the DSF file.