Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: Roberto Brandolini on July 09, 2012, 02:11:00 am

Title: Crossfade issues
Post by: Roberto Brandolini on July 09, 2012, 02:11:00 am
I discover another bug, if this can help you to investigate.
Using sctransv2 and shoutcast2:
If I try to change the cross fade settings nothing change.
If I disable it (0) after restart sctrans still continue to crossfade 8 seconds.  There's no way to disable it.
I check the source.conf of the server.
It seems CC not write the correct value. Is still xfade=8
If you manually write the value, it works and CC doesn't read it and change it.
Title: Re: Crossfade issues
Post by: Centova - Steve B. on July 12, 2012, 10:38:39 pm
Apparently Nullsoft renamed this from 'crossfade' in v1 to 'xfade' in v2, and we're still using the old name.  Will update our code -- thanks!
Title: Re: Crossfade issues
Post by: Centova - Steve B. on July 12, 2012, 10:46:48 pm
Actually no, I spoke too soon -- not only are we are indeed using the 'xfade' option, in my copy of Centova Cast it's updating both 'xfade' and 'xfadethreshoold' with no problems.
Title: Re: Crossfade issues
Post by: DrO on July 13, 2012, 01:43:47 am
could be from using an older version the the sc_trans v2 betas - i keep finding lots of people using beta 5 or earlier which have such bugs.
Title: Re: Crossfade issues
Post by: My Auto DJ on July 14, 2012, 03:54:47 am
Is it because you are trying to change the value logged in as the user, I think you must be logged in as ADMIN to make the change.
Title: Re: Crossfade issues
Post by: Roberto Brandolini on November 02, 2012, 05:17:10 am
Hi Steve,
I see that this issue is not resolved.
All my accounts works fine but changing the crossfade value in the account settings, after restart server not change in source.conf the xfade value.  Is still=8.
Changing value in source.cong directly it works.

Why?

I'm running last version and I make changes with admin account.
Title: Re: Crossfade issues
Post by: Centova - Steve B. on November 02, 2012, 04:15:35 pm
Ahh, thank you -- while the change we made previously caused the setting to "stick" in the interface, it didn't correctly map it to the configuration file directive.  This has been fixed for the next build.