Miska Posted October 10, 2014 Share Posted October 10, 2014 Has anyone found or heard a difference using or not using the DST to DSD converter option in ISO2DSD for stereo? for Multi channel? DST is lossless compression, so decompression results in original DSD stream. I believe I already have a fix for that crash when input is DST. I'll see if I can also include speed improvement for the conversion before releasing update... Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted October 15, 2014 Share Posted October 15, 2014 Jussi, the previous DFF2DSF version processed multichannel DFF files correctly: OK, this is some completely unexpected side-effect of the changes. I'll look into it and make a new release... Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted October 15, 2014 Share Posted October 15, 2014 OK, this is some completely unexpected side-effect of the changes. I'll look into it and make a new release... Now this problem has been fixed with version 1.2.1... Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted November 14, 2014 Share Posted November 14, 2014 Is there DSF2DFF converter also? As far I heard, only some strings in file header needs changing. Someone, who can wrote such programs, maybe include both options in one package: DFF2DSF and DSF2DFF. Bogi? The entire data layout is different between the formats. So all the data needs to be rewritten. I would otherwise do such, but I never implemented DFF writing algorithms, because for my testing purposes DSF was enough (and better). Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted November 14, 2014 Share Posted November 14, 2014 Such troubles happened with some ISO's. In that case sacd_extract creates DFFs with corrupted (shortened) metadata. I have no easy solution for this case. I have a fix for the DFF2DSF to ignore these corrupted metadata blocks. I'll try to make a new release soon... Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted November 14, 2014 Share Posted November 14, 2014 I decided right now was the moment to do it... I just uploaded version 1.2.2: Signalyst It should just ignore any corrupted non-essential headers. Please let me know if there are any issues. My test file set is fairly limited... Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted November 15, 2014 Share Posted November 15, 2014 Miska, the newest dff2dsf.exe v1.2.2 reports error if pathname(s) contain spaces. Previously such filenames/pathnames were processed correctly, if they were enclosed in double quotes. OK, strange, because the only change is related to handling corrupt ID3v2 tags inside DFF. I'll check it... Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted November 15, 2014 Share Posted November 15, 2014 At least in some earlier versions of Windows, downloaded executables were tracked and blocked by default You can right-click on the executable and select "Properties" from the context menu and see if there's an "Unblock" button in the property dialog. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted November 15, 2014 Share Posted November 15, 2014 I found the issue is relevant only for the 1st (input) DFF parameter. In the case of 2nd (output) DSF parameter spaces cause no troubles. Thank you for the information! That's even more strange, as both use the same file I/O class... I'll try to reproduce the issue and track it down. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted February 23, 2016 Share Posted February 23, 2016 Anybody know why neither Jussi's command-line 1.2.1 or 1.2.2 DFF2DSF nor Bogi's workflow DFF to DSF app will convert a DSD256 5.0 DFF file? I get an immediate 1kb DSF file, with no error message. I have PM's into Peter and Jussi earlier today but nothing yet. I got the PM, but haven't got time to check yet. At least some multichannel files I was testing with earlier worked OK. But I will certainly look into this. Does the same file work OK in HQPlayer? Both use the same code, apart of course from the DSF writing part. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now