Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TontonGuigui]

Hi there,

The following option does no longer work :
Tools/Options/Audio/Settings/Play silence at startup for hardware synchronization.
Whatever I might fill in (usually 6 seconds), it starts the music right after double-clicking a track.

This option was first introduced at my request, and I still really need it (belcanto usb link + external dac).

Would you mind taking a look at this one ?
Thanks in advance.

[Matt]

I'm having trouble reproducing this.

Remember that the setting only takes when you start from fully stopped playback (not paused).

Also, it only works for files played through the native JRiver audio engine (so does not work if you're playing Apple files with the QuickTime engine, etc.)

Thanks.

[leezer3]

Can't reproduce either, although I've got no DACs or funny sound cards in the equation.

-Leezer-

[TontonGuigui]

Hi,

I'm using Wasapi in exclusive mode, with the following options :

Output mode: WASAPI
Ouput mode settings...
  Open device for exclusive access
  Buffering : 1.00 seconds (More Responsive)

DSP & output format...
Output Format
  Sample rate
    Resample : Only sources less than 44,100 Hz or greater than 96,000 Hz
    Sample rate : 96,000 Hz
Bitdepth
  Bitdepth : 24-bit

Prebuffering: 6 seconds (recommended)
Play silence at startup for hardware synchronization: 6 seconds
Play files from memory instead of disk (checked)

Track Change
Switch tracks : Cross-fade (smooth) - 2s
Use gapless for sequential album tracks (checked)

The rest of the options are left to default values.

Does that help reproducing the issue ?

TontonGuigui

PS : yes I know when it takes place, and this is exactly when my dac needs to synchronize

[Matt]

Could you try switching options to see if you can find the option that causes the problem?

Like I said (and others in this thread), we haven't been able to reproduce the issue.

Thanks.

[leezer3]

Now I've started messing with the WASAPI settings, I can actually reproduce this
The problem seems to lie in the resampling- As soon as a file gets resampled, it kills the startup delay.

-Leezer-

[TontonGuigui]

Hi,

as far as I can tell, none of my files are resampled so far (I'm listening to either 16/44.1 (mainly) or 24/96 files).
I use this setting because my interface is limited to the specified range, and thought this was a (mc15) plus to expose such settings.

I'll try disabling it tonight and will let you know  ?

[leezer3]

Hi,

as far as I can tell, none of my files are resampled so far (I'm listening to either 16/44.1 (mainly) or 24/96 files).
I use this setting because my interface is limited to the specified range, and thought this was a (mc15) plus to expose such settings.

I'll try disabling it tonight and will let you know  ?

From that, aren't you resampling the 16-bit ones to 24-bit? 

-Leezer-

[TontonGuigui]

From that, aren't you resampling the 16-bit ones to 24-bit?

It's not really resampling but padding instead. But I guess you could say so.
Choosing to present 24 bits words is mandatory for bit-perfect playback and has never colluded with leading silence (so far  ).

Funny enough, if I do so, my dCS dac will tell me the data is 16/44.1 content.
If I choose not to use 24 bits words, then it sees the data as being 24/44.1 content (and so long for bit-perfectness).

[Matt]

Coming in build 160 and later:
Fixed: When resampling, startup silence for hardware synchronization durations would not be adjusted properly.

[TontonGuigui]

Hi,

EDIT
I've just tested it and I do confirm this is due to the resampling option (not the bitdepth one) output format in DSP studio (whatever the parameter, but I guess you got it).
Thanks a lot for nailing it, Leezer and Matt, and for the fix to come !  

TontonGuigui