INTERACT FORUM

More => Old Versions => JRiver Media Center 32 for Windows => Topic started by: slerch666 on January 26, 2024, 02:31:01 pm

Title: Play silence at startup for hardware synchronization: Setting does not save
Post by: slerch666 on January 26, 2024, 02:31:01 pm
Subject describes the issue.
MC 32.08.

I open Playback options -> Play silence at startup for hardware synchronization -> 1 second

I press OK. Start playback, 1 second pause, hardware happy.

I stop the track. If the track used custom EQ, it resets silence synch to NONE.

If I only play tracks I haven't added custom EQ to, the silence setting stays as expected between plays.


I can deal with it. The "issue" it causes is that MC starts the track, it goes for about .75 of a second where it is "playing" and I hear nothing, then I hear it.

For the record, the hardware I am using does the lack of audio on start on every other application. MC gives me a level of control to fix the stupid lack of audio on the HW side so I use it and would like the setting to be saved.


It did this in the final build of MC 31 from my testing as well. I do not know when it began happening as I didn't realize it had been changed until I really sat and watched what happened and why my audio wasn't playing the way it used to.
Title: Re: Play silence at startup for hardware synchronization: Setting does not save
Post by: Matt on January 26, 2024, 04:41:03 pm
Startup silence is saved along with your preset.  So whatever you had it set at when you saved, that will be loaded when you play and use a preset.
Title: Re: Play silence at startup for hardware synchronization: Setting does not save
Post by: Matt on January 26, 2024, 05:24:06 pm
I found a problem though.  Thanks!

Next build:
Fixed: When loading a DSP preset, it was not restoring numeric fields properly so they became strings and sometimes didn't work.

This could make the value not save and restore like expected.
Title: Re: Play silence at startup for hardware synchronization: Setting does not save
Post by: slerch666 on January 29, 2024, 06:01:09 am
I found a problem though.  Thanks!

Next build:
Fixed: When loading a DSP preset, it was not restoring numeric fields properly so they became strings and sometimes didn't work.

This could make the value not save and restore like expected.
I was pretty sure I wasn't going crazy. :D

Thanks for the quick response and quick fix!

There's a reason I keep using MC.