search

jevinskie / sacd-ripper-google-code

Automatically exported from code.google.com/p/sacd-ripper
GNU General Public License v2.0
2 stars 2 forks source link

SACD_Extract 0.3.6 produces audible clicks at the beginning and at the end of each extracted DSDIFF track file #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Extracting single DSDIFF track files from ISO
2.
3.

What is the expected output? What do you see instead?
I expect single DSDIFF track files and get single DSDIFF track files which have 
an audible short click at the very beginning of each track file and also at the 
end of each track file

What version of the product are you using? On what operating system?
SACD_Extract 0.3.6 WinXP

Please provide any additional information below.

Original issue reported on code.google.com by musiklie...@googlemail.com on 9 Jan 2012 at 10:40

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Lieber Musikliebhaber,
we discussed this issue already in   issue #6.
the clicks are NOT produced by sacd_ripper, but result from dsd to pcm 
conversion. When you play your dff files on a pcm audio equipment (like the 
soundcard of your computer), the playing software does a dsd to pcm conversion. 
This conversion process is mainly a heavy lowpass filtering, called decimation, 
which produces transient responses at the beginning and at the end of each 
conversion process. So these clicks are artifacts from dsd to pcm conversion.
I recommend to extract a DSDIFF Edit Master File with CUE sheet, convert the 
whole DSD-Image to PCM with a software of your choice (foobar2000, 
Audiogate...). Then cut your PCM-Image into single tracks using the CUE sheet.
PM me, if you have questions.
yours, t.

Original comment by thom...@gmx.net on 15 Jan 2012 at 11:05

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Agreed.

However, this procedure is quite cumbersome. It would be really great if a 
future version of SACD_Extract could do direct-to-wav/flac output and 
automatically take care of this problem. Is this possible?

Original comment by lich000k...@yahoo.de on 16 Jan 2012 at 7:36

GoogleCodeExporter commented 9 years ago 
>It would be really great if a future version of SACD_Extract could do 
direct-to-wav/flac output and automatically take care of this problem. Is this 
possible?

It is possible to output PCM. But the PCM conversion itself is just not that 
'simple'. For ex. to do it properly gain should be calculated in advance (after 
1st stage conversion). And last but not least the DSD to PCM algorithm is very 
complicated to get right. Saracon does a very good job with its aliasing 
filter, it would be very hard to get that similar kind of quality.

Original comment by mr_wic...@hotmail.com on 17 Jan 2012 at 9:11

GoogleCodeExporter commented 9 years ago 
Saracon supports batch processing. How about an option to output wav/flac using 
Saracon? Maybe the DSD could be modified such that no clicks would appear.
If the clicks are indeed  produced at junctions of different passages of 
digital silence, these passages could be made equal.
Alternatively, silence could be added at the beginning and end of a track 
before the conversion and removed again afterwards.

Original comment by lich000k...@yahoo.de on 19 Jan 2012 at 5:19

GoogleCodeExporter commented 9 years ago 
As reported earlier and further investigation confirms this has to do with 
nothing but the pcm conversion itself.

Original comment by mr_wic...@hotmail.com on 3 Feb 2012 at 12:32