Just an update, since I haven't posted in awhile -- Headshaker's detailed information helped immensely here and I believe we've found the root cause of these issues (or if not, we've found another substantial issue that needed to be resolved anyway, so either way, cheers, Headshaker!)

It looks like it's actually a combination of two separate issues that have to interact in order for the problem to manifest, which is why it's been such a difficult process to track it down.

As for why this is taking so long to "fix"... first, some background -- as you may know, v3 uses a modular architecture in which the control panel can run on one physical server/VPS, and manage multiple (local or remote) physical/VPS streaming server nodes.  Right now, because the autoDJ depends on MySQL, the streaming nodes aren't fully independent -- that's a holdover from how v2.x worked.  Our goal for a future release (post v3.0.0) is to eventually fully decouple the streaming nodes from the control panel by abandoning MySQL in favor of SQLite, and put the autoDJ's SQLite databases on the streaming nodes, making the streaming nodes 100% self-contained and independent.

Back on point, one of the two issues that's contributing to the problem reported in this thread is the manner in which we're allowing sc_trans2/ices to pull down track information from the control panel server in the interim.  Instead of putting a quick band-aid fix on that, we're taking the time to make some more fundamental changes that not only fix this problem, but will eventually need to be made anyway to "pave the road" for the move to SQLite as well.

We're wrapping up those changes now and will have a new build out in the next few days for everyone to test.

And to everyone else with unreplied forum posts, I'll be looking at those as soon as this build is done.  Sorry for the wait, but because this CPU load issue is bringing down servers, it takes priority.

Hurrray !!!!

You comforted me

Thanks for that repaly

Just an update, since I haven't posted in awhile -- Headshaker's detailed information helped immensely here and I believe we've found the root cause of these issues (or if not, we've found another substantial issue that needed to be resolved anyway, so either way, cheers, Headshaker!)

It looks like it's actually a combination of two separate issues that have to interact in order for the problem to manifest, which is why it's been such a difficult process to track it down.

As for why this is taking so long to "fix"... first, some background -- as you may know, v3 uses a modular architecture in which the control panel can run on one physical server/VPS, and manage multiple (local or remote) physical/VPS streaming server nodes.  Right now, because the autoDJ depends on MySQL, the streaming nodes aren't fully independent -- that's a holdover from how v2.x worked.  Our goal for a future release (post v3.0.0) is to eventually fully decouple the streaming nodes from the control panel by abandoning MySQL in favor of SQLite, and put the autoDJ's SQLite databases on the streaming nodes, making the streaming nodes 100% self-contained and independent.

Back on point, one of the two issues that's contributing to the problem reported in this thread is the manner in which we're allowing sc_trans2/ices to pull down track information from the control panel server in the interim.  Instead of putting a quick band-aid fix on that, we're taking the time to make some more fundamental changes that not only fix this problem, but will eventually need to be made anyway to "pave the road" for the move to SQLite as well.

We're wrapping up those changes now and will have a new build out in the next few days for everyone to test.

And to everyone else with unreplied forum posts, I'll be looking at those as soon as this build is done.  Sorry for the wait, but because this CPU load issue is bringing down servers, it takes priority.

When is the new build with all fixes going to be released !!!!!!

George

 

we are also waiting for the new build... we have been waiting for a standalone control panel since years... and now that cc 3 is almost prepared for a RC we are getting anxious!

We're wrapping up those changes now and will have a new build out in the next few days for everyone to test.

So ? 'Next few days' has gone. We're still waiting.

We're wrapping up those changes now and will have a new build out in the next few days for everyone to test.

We're wrapping up those changes now and will have a new build out in the next few days for everyone to test.

So ? 'Next few days' has gone. We're still waiting.

So Steve B, when are we going to get the New build?

Please keep us all informed with progress instead of keeping us hanging around (Costing us Money!!)

George

Still nothing
I'm starting to be apset :/

Everyone are waiting for update for something about 2 months ??

Steve, don't You understand that You could have a lot of clients but for that You just will start to loose them ... ?

I will wait one more month, if still nothing I will leave centova....

I very much appreciate everyone's enthusiasm for the new release.  Rest assured the delays aren't intended to piss anyone off.

A new build is making its way to the deployment servers now.  The core stability changes we made to address the issues in this thread have been running successfully on two of our internal "semi-production" machines, and hosting a substantial number of streams, for a couple of weeks now with no issues.

Please start new threads for any issues in this new build.  I'm going to lock this thread now as it's become a bit of a hodgepodge of various issues.

Thanks, all!