DSD to PCM Conversion suggestions

フォーラム TuneBrowser DSD to PCM Conversion suggestions

  • このトピックには12件の返信、2人の参加者があり、最後にstoraidにより6ヶ月、 3週前に更新されました。
13件の投稿を表示中 - 1 - 13件目 (全13件中)
  • 投稿者
    投稿
  • #14639
    storaid
    参加者

    Hello, Tiki

    I have a few suggestions regarding the DSD to PCM Conversion feature:

    1. Can the default setting of ‘Auto’ be changed to ‘Fixed’?

    I think the word ‘Auto’ might be misleading since the output format is fixed at 44.1KHz.

    2. If it’s possible to change to ‘Fixed’, could you also provide an ‘Auto’ option for dynamic conversion?

    I think the settings of DoP could be a reference:

    – DoP64: 176.4kHz/device’s max bit depth

    – DoP128: 352.8kHz/device’s max bit depth

    The maximum sample rate for ‘Auto’ should be capped at 352.8kHz, as the DoP256 format is not very common.

    You might want to consider these two suggestions.

    Thank you!

    PS: Also, the DSD to PCM Conversion process isn’t an on-the-fly transcoding, is it? I’ve noticed that it takes a little time before the output is sent to the device for decoding.

    #14645
    Tiki
    キーマスター

    Hello.

    This function is for decoding to DAC. In the case of the Auto setting, the conversion is as follows.

    • 2822kHz -> 88.2kHz
    • 5644kHz -> 176.4 kHz

    If you are talking about file transfer to UPnP Renderer, conversion is only supported for audio/L16.

    #14650
    storaid
    参加者

    Hello, Tiki

    I thought the DSD to PCM Conversion for UPnP renderer and local devices was the same…

    You’re right, for the UPnP renderer, it currently only outputs L16/44.1KHz.

    I would like to offer some suggestions.

    Many current streaming DAC devices generally can decode audio files up to 384KHz…

    At a minimum, there should be support for 192KHz…

    1. Is it possible to make some adjustments in the settings? (As there might still be some streaming DACs that only support up to 192KHz)

    For example:

    – DSD64: 88.2KHz

    – DSD128: 176.4KHz

    And then the maximum output value being 192KHz.

    2. Add an option for selecting the Maximum Bit depth: 16, 24, 32

    I hope you can consider these suggestions.

    Also, when using UPnP Renderer output, the waiting time for the DSD to PCM Conversion process is much longer than in Foobar2K…

    In Foobar2K, the DSD to PCM conversion process is almost instantaneous and very fast.

    Why is the conversion speed slower in TuneBrowser?

    Thanks

    #14651
    Tiki
    キーマスター

    Do you really think I know why?

    #14652
    storaid
    参加者

    Hello, Tiki

    I forgot you use libdsd2pcm for conversion
    Sorry for causing you trouble…(=´ω`=)

    1. and 2. suggestions, You can consider taking a look if it’s possible.

    #14933
    Tiki
    キーマスター

    Hello,

    TuneBrowser 5.5.0 now supports transcoding to wave format as well as audio/L16. This conversion to wave format is enabled by default. audio/L16 format only supports 16-bit, 44.1/48 kHz, but the wave format (as you know) additionally supports high-resolution formats.

    This feature is called WavProxy (WPRX) in TuneBrowser. Conversion is done on the fly, similar to audio/L16.

    #14946
    storaid
    参加者

    Hello, Tiki

    thanks for ur feature enhancements..

    tested DSD64, DSD128 files

    it’s working well..

    and, I have a question..

    it’s possible to set Gain(db) like DSD-PCM Conversion????

    #14947
    Tiki
    キーマスター

    Thank you for testing.

    Gain is not currently applied. I will consider it.

    #14961
    Tiki
    キーマスター

    Hello.

    In version 1744, the following gain is applied when converting from DSD to PCM.

    – TreeItem: Playback settings – Playback settings detail – DSD-PCM Conversion
    – Property: DSD to PCM Conversion – Gain (dB)

    #14969
    storaid
    参加者

    Hi, Tiki

    Tested it between +0db and +6db.

    seems like it’s working

    What information can I find in the Log to determine if this function is working?

    #14979
    Tiki
    キーマスター

    Thank you for testing.

    I am relieved to hear that it is working well.

    Currently, there is no log information about gain. I’d like to add something in the next release.

    #15013
    Tiki
    キーマスター

    Now, gain is recorded in the log.

    2024/04/23 21:25:32,904: UL02606: T03e6c: HTTPServer: [<DeviceName> :45XXX]: DecoderParam:
    2024/04/23 21:25:32,904: UL02609: T03e6c: HTTPServer: [<DeviceName> :45XXX]: DSD : Yes
    2024/04/23 21:25:32,905: UL02610: T03e6c: HTTPServer: [<DeviceName> :45XXX]: - xPCM: Auto
    2024/04/23 21:25:32,905: UL02611: T03e6c: HTTPServer: [<DeviceName> :45XXX]: - Gain: 6
    #15015
    storaid
    参加者

    Thanks, Tiki

    I can see the gain message was recorded in the log

    
    
    2024/04/23 20:58:24,024: UL10852: T00ae0: HTTPServer: [10.1.1.134 :54980]: Socket accepted.
    2024/04/23 20:58:24,024: UL10853: T06258: HTTPServer: [10.1.1.134 :54980]: Processing [GET] /TuneID/00007582-RFHE1EEFF5C.dsf_WPRX?DecodeEx=WavProxy
    2024/04/23 20:58:24,024: UL10854: T06258: HTTPServer: [10.1.1.134 :54980]: Tune: 00007582-RFHE1EEFF5C.dsf_WPRX ->
    2024/04/23 20:58:24,024: UL10855: T06258: HTTPServer: [10.1.1.134 :54980]: \\10.1.1.127\music\[Hi-Res]NieR - Automata Vinyl [A+B Side]\NierAutomata\Weight of the World.dsf
    2024/04/23 20:58:24,030: UL10856: T06258: HTTPServer: [10.1.1.134 :54980]: Source: 10.1.1.156 [http://10.1.1.156:29400/TuneID/00007582-RFHE1EEFF5C.dsf_WPRX?DecodeEx=WavProxy]
    2024/04/23 20:58:24,030: UL10857: T06258: HTTPServer: [10.1.1.134 :54980]: This is mine.
    2024/04/23 20:58:24,030: UL10858: T06258: HTTPServer: [10.1.1.134 :54980]: Mine:Yes Managed:Yes Recorded:Yes Local file: [\\10.1.1.127\music\[Hi-Res]NieR - Automata Vinyl [A+B Side]\NierAutomata\Weight of the World.dsf]
    2024/04/23 20:58:24,034: UL10859: T06258: HTTPServer: [10.1.1.134 :54980]: DecodeEx:WavProxy
    2024/04/23 20:58:24,034: UL10860: T06258: HTTPServer: [10.1.1.134 :54980]: DecoderParam:
    2024/04/23 20:58:24,034: UL10861: T06258: HTTPServer: [10.1.1.134 :54980]: RSMP: No
    2024/04/23 20:58:24,034: UL10862: T06258: HTTPServer: [10.1.1.134 :54980]: DMIX: No
    2024/04/23 20:58:24,034: UL10863: T06258: HTTPServer: [10.1.1.134 :54980]: DSD : Yes
    2024/04/23 20:58:24,034: UL10864: T06258: HTTPServer: [10.1.1.134 :54980]: - xPCM: Auto
    2024/04/23 20:58:24,034: UL10865: T06258: HTTPServer: [10.1.1.134 :54980]: - Gain: 6
    2024/04/23 20:58:24,086: UL10867: T01a9c: --> EVENT /SR_AVTransport.notify: uuid:0eb808be-1dd2-11b2-b622-f293cc1e7d64
    2024/04/23 20:58:24,086: UL10869: T01a9c: Subscriber: [Event]: Received EVENT: [AVTransport]
    2024/04/23 20:58:24,086: UL10871: T01a9c: Subscriber: - [AVTransport]: Device notification: Node found: [TransportState ] : [TRANSITIONING]
    2024/04/23 20:58:24,086: UL10873: T01a9c: UPnP_P: [Proc:TrState ] <EVT>: PlayerUPnP UPState changed [STOPPED ] to [TRANSITIONING ]
    
    
13件の投稿を表示中 - 1 - 13件目 (全13件中)
  • トピック「DSD to PCM Conversion suggestions」には新しい返信をつけることはできません。