How do you store DFF ( untagged ) files?

[bogi]

Stephanie, I'm glad you succeeded to make ISO2DSF working!

 

Miska is author of dff2dsf.exe command line converter and I am author of ISO2DSF tool including the context menu interface. So your questions are related to me.

 

The ZIP archive of ISO2DSF contains PDF guide ISOtoDSFv110.pdf. The installation part of the guide contains the points you are asking for. If you have a suggestion to improve the guide, please let me know.

[sjg]

Ted and Bogi -- Hi. You guys are great. I addressed my message to Miska by accident, but I was referring to the ISOtoDSFv110.pdf guide -- I believe something is missing here:

 

 

The missing text I believe refers to downloading Mr. Wicked's ISOtoDSD software.

 

The other point I raise regarding the instructions is that for me to get the program to work I needed to move the executable files to the main directory not the sub directories where they are located.

 

 

I needed to copy the 2 exe files into the main directory and not the sub directories as they are packaged in the zip files.

 

thanks again, Stephanie

[ted_b]

1) Mr Wicked's link is right above your circle (Mr Wicked wrote sacd_extract, not "ISOtoDSD")

2) "this archive" refers to the one you are reading about, namely Bogi's

3) in ALL cases it says to extract/unzip "to same folder as used in step 1 ". Don't extract all the Bogi (edit: I mean Miska) versions, just the one you need (i.e click on Win32, don't unzip the parent folder).

[bogi]

Stephanie, I see your point. I think it would be easier to start with my archive ISO2DSF_v1.1.0_Win7_Win8.zip and then add dss2dsf.exe and sacd_extract.exe to it.

 

This is my change proposal:

 

INSTALLATION

 

 

1. Unzip this archive to any directory on your computer.
    
    
   
2. Download sacd_extract from https://code.google.com/p/sacd-ripper/downloads/list
   Open the downloaded archive and copy sacd_extract.exe to the same directory you used in the step 1.
    
    
   
3. Download DFF2DSF tool from Signalyst
   Find dff2dsf.exe in the downloaded archive and copy it to the same directory you used in the step 1.
    
    
   
4. In Windows Explorer, go to the directory, where you installed all the files. To create 'SACD ISO to DSF per track' Windows Explorer context menu item for ISO file type, run AddContextMenuItem.bat.
    
   

[bogi]

Don't extract all the Bogi versions, just the one you need (i.e click on Win32, don't unzip the parent folder).

 

Ted, you meant 'Don't extract all the Miska versions' :-)

[ted_b]

Sorry, yes Miska versions. (Now I'm doing it).

 

Stephanie still would have issue cuz step 3 would result in all versions extracted. Stephanie needs to extract ONLY the contents of Win32 (in this Windows example)

 

Maybe just include Miska's executable (with a big shoutout and link to HQPlayer) in your package since no one can use the other ones (OSX, Linux) with your stuff right now anyway, and it reduces the confusion and downloads, let alone folder structure.

[bogi]

Therefore I wrote "Find dff2dsf.exe in the downloaded archive and copy it to the same directory you used in the step 1."

The .exe file appears in the win32 subdirectory of the archive.

 

Edit: I will add a picture of the installation folder to the guide. That will be easiest to understand.

[sjg]

bogi -- I think that adding a picture of the installation folder would be most helpful, especially for folks like me.

[rodrigaj]

I want to break in here to verify: You still need a special SonyPS3 to extract the DSD code from SACD correct?

[Miska]

3) in ALL cases it says to extract/unzip "to same folder as used in step 1 ". Don't extract all the Bogi (edit: I mean Miska) versions, just the one you need (i.e click on Win32, don't unzip the parent folder).

 

IMO, easiest way is

1) Double click the ZIP

2) Double click on the win32 folder

3) Drag-and-drop the dff2dsf.exe where ever needed... (or use Ctlr-C and Ctrl-V)

[Miska]

I just released dff2dsf v1.2.0 with support for (optionally) writing out given ID3v2 tag data to the output DSF file while writing it out.

 

I also made the processing buffer larger again. Now the speed increase on Linux was just 0.02 seconds for me (on 200 MB file), but on Windows the difference could be larger.

[DMM]

I uploaded dff2dsf v.1.1.0 update here:

Signalyst

 

There is now also 32-bit Linux binary included.

 

Thanks Miska! 32bit version works perfectly...

DFF2DSF v1.2.0
Copyright (C) 2014 Jussi Laako / Signalyst. All rights reserved.
./dff2dsf <infile> <outfile> [tagfile]

[ted_b]

I want to break in here to verify: You still need a special SonyPS3 to extract the DSD code from SACD correct?

 

Correct. I wrote a guide about it here:

https://dl.dropboxusercontent.com/u/3487125/SACD%20ripper%20primer%20v4.0.1.pdf

[paul3000h]

I used ISO2DSF_v1.1.0_Win7_Win8 . All appeared to go well, took about 3 to 4 minutes for a 1.2 gig iso but no .dff or .dsf file in the output folder or anywhere on my computer. Just the cue and text files. See pics. The dff to dsf conversion at the end happened in about 5 seconds.

 

Please advise.

[paul3000h]

Re the various ideas of install instructions this is the way I put it in a reminder to myself in the installation folder:

 

copy all from ISO2DSF_v1.1.0_Win7_Win8 into here

copy sacd_extract.exe from sacd_extract_0.3.7_WIN32 into here

copy dff2dsf.exe from dff2dsf-120\win32 into here

To create 'SACD ISO to DSF per track' Windows Explorer context menu item for ISO file type,

run AddContextMenuItem.bat.

 

Important: Do not move location of the installed files and do not delete them, if you wish to use the

context menu or shortcut. Use the uninstallation procedure described below, if you wish to move or

delete the installed files.

[bogi]

paul3000h, try to lower the value of parameter $albumtitle_length in iso2dsf.cfg

 

Thanks for your suggestion to improve the documentation, it will help me to update the guide.

[paul3000h]

I discovered the problem was the DFF2DSF tool from http://www.signalyst.com/professional.html was later version, 1.2.0 when I used the previous version it worked fine.

 

A small thing 'press any key to close' never worked.

 

Thanks again to all involved for great programs.

[bogi]

The small thing is that I had to write "Press <Return> to close", or change the implementation.

 

I'm not sure with your finding, that the cause was DFF2DSF. Your 1st "black" picture shows, that sacd_extract was started, but exited unexpectedly during processing of 1st track. Till that time point DFF2DSF was not yet invoked. It is started when all tracks are extracted by sacd_extract.

 

I observer that behaviour when I tested sacd_extract alone. It's some bug in sacd_extract, when the last optional parameter for output directory is used. I added the $albumtitle_length parameter to the iso2dsf.cfg file after I noticed this behaviour. Shortening the output directory helped in the cases I tested..

 

Previouslly you most probably extracted other ISO files, not that one which now caused your troubles. The issue with sacd_extract <outdir> parameter si not systematic. It occurs only with ISO's where artist or album names are very long strings.

[Miska]

Previouslly you most probably extracted other ISO files, not that one which now caused your troubles. The issue with sacd_extract <outdir> parameter si not systematic. It occurs only with ISO's where artist or album names are very long strings.

 

Without small extra hassle, combined full path name of a file can be max 255 characters on Windows.

 

On Windows, dff2dsf support file paths up to 32768 characters long.

[paul3000h]

The small thing is that I had to write "Press <Return> to close", or change the implementation.

 

I'm not sure with your finding, that the cause was DFF2DSF. Your 1st "black" picture shows, that sacd_extract was started, but exited unexpectedly during processing of 1st track. Till that time point DFF2DSF was not yet invoked. It is started when all tracks are extracted by sacd_extract.

 

I observer that behaviour when I tested sacd_extract alone. It's some bug in sacd_extract, when the last optional parameter for output directory is used. I added the $albumtitle_length parameter to the iso2dsf.cfg file after I noticed this behaviour. Shortening the output directory helped in the cases I tested..

 

Previouslly you most probably extracted other ISO files, not that one which now caused your troubles. The issue with sacd_extract <outdir> parameter si not systematic. It occurs only with ISO's where artist or album names are very long strings.

 

But when I re did it with the previous version of DFF2DSF it worked, maybe because zone alarm asked permission 1st time.

[paul3000h]

Some interesting observations:

 

 

Sadly the clicks are not gone.

 

 

DSF made with ISO2DSF_v1.1.0_Win7_Win8

Dff are auto deleted so I re-made them with iso2dsd_PC_v6 from Sonore

No clicks at end of DFF's but sadly clicks at end of all DSF's

File sizes of 1 to 6 DSF's are slightly bigger than the DFF's

File sizes of 7 to 8 appear the same in explore but in properties the reverse is true ie DFF's are slightly bigger than DSF's

Foobar shows tag info for all DFF's, how? DFF's are not writeable.

Foobar shows no tag info for the DSF's.

Foobar shows slight time differences for same tracks.

 

 

Please see pics attached.

[bogi]

You are the 1st who reports click issue, it's important to know what's the reason. The known click issue of sacd_extract is only one of possibilities.

 

DFF and DSF files are of different formats. Different DSF encoding and different headers. So their size has not be the same for the same track.

 

Foobar uses CUE sheet, generated by sacd_extract, when you run the Sonore tool.

My ISO2DSF generates CUE sheet too. Therefore I'm surprised it didn't work for you with DSF files. Could you please attach here the CUE sheet with shorter filename?

[paul3000h]

Problem is definitely not with ripping iso. I now play iso's only with zero ticks. Ticks are zero in the dff's created in sonare but the dsf's made originally with sonare and now also with iso2dsf contain ticks at end of each track.

 

 

Cue sheets and txt attached but not connected to ticks, dff's created with sonare with cue sheet ticked are the ones in Foobar with tags showing. The dsf's have no tags but anyway easily created with the cue sheets or txt.

 

Remove the .txt from the 2 cue files as .cue was not allowed to attach.

Anna Moffo.txt

Anna Moffo created in sonare.cue.txt

Anna Moffo.cue.txt

[Miska]

No clicks at end of DFF's but sadly clicks at end of all DSF's

 

One possibility is that the player you use doesn't handle DSFs correctly... It must take into account that the last block is almost never full.

[bogi]

paul3000h, the issue with CUE sheet si now clear. I have it already corrected, but the vrsion 1.1 doesn't contain yet the correction.

Please test the CUE sheet issue with ISO2DSF v1.1.1: https://docs.google.com/uc?export=download&id=0B1IZPbDClIn6TEQyaFZuUkM1Uzg

 

About the tick issue, it's about many different tools including the playback software and settings, for example DSP plugins. Ted summarized many possible causes here: http://www.computeraudiophile.com/f11-software/how-do-you-store-dff-untagged-files-21780/index4.html#post356594