From: tsepp2000@web.de
To: sox-users@lists.sourceforge.net
Subject: Re: sox/mansr: DSD to PCM
Date: Thu, 21 May 2020 18:44:00 +0200 [thread overview]
Message-ID: <trinity-bee39973-a528-4c56-a023-e2eb577b9003-1590079440804@3c-app-webde-bs62> (raw)
In-Reply-To: <yw1xftbtz8af.fsf@mansr.com>
Thank you Mans for your efforts. My mistake. I'm in the totally wrong forum.
Regards
Thomas
> Gesendet: Donnerstag, 21. Mai 2020 um 16:12 Uhr
> Von: "Måns Rullgård" <mans@mansr.com>
> An: tsepp2000@web.de
> Cc: sox-users@lists.sourceforge.net
> Betreff: Re: sox/mansr: DSD to PCM
>
> tsepp2000@web.de writes:
>
> > My question: Because we use this conversion to convert music files, which
> > are basically of the very best quality, in a way that goes very far
> > (conversion with influence of noise, time, gain and more ...), a
> > discussion with a 360 degree view of all phenomena would be very helpful,
> > how this can best be done with Sox to get an adequate (here) PCM file. The
> > standard procedure with Xrecode3, for example, is not optimal.
>
> The 'rate' effect with no special options should give good results.
> Conversion of DSD64 to a rate higher than 48 kHz will end up with some
> ultrasonic noise. If you don't like this, you can reduce it with an
> additional low-pass filter. That's all there is to it.
>
> --
> Måns Rullgård
>
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2020-05-21 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 7:46 sox/mansr: DSD to PCM tsepp2000
2020-05-20 8:16 ` Måns Rullgård
2020-05-20 9:17 ` tsepp2000
2020-05-21 14:12 ` Måns Rullgård
2020-05-21 16:44 ` tsepp2000 [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-19 13:18 tsepp2000
2020-05-19 20:22 ` Måns Rullgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-bee39973-a528-4c56-a023-e2eb577b9003-1590079440804@3c-app-webde-bs62 \
--to=sox-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).