• Welcome to RadioDJ - Free Radio Automation Software Forum. Please log in or sign up.

Rotations won’t work in 2.0.3.8 after update from 2.0.0.6

Started by Brockl, September 23, 2022, 04:14:01 PM

Brockl

Rotations won't load after upgrade, created a new one and it only runs once then won't load again.  Have updated the database with update sql. 

Any suggestions? Thanks

rgkluver

Quote from: Brockl on September 23, 2022, 04:14:01 PM
Rotations won't load after upgrade, created a new one and it only runs once then won't load again.  Have updated the database with update sql. 

Any suggestions? Thanks

Same problem here/upgrade path.  My station is down while I try to figure this out.

radiovoltrega

Same problem here, it also happens when creating a fresh one copying the previous one

rgkluver

After a bunch of trail and error, what worked for me to get AutoDj rolling again after the upgrade was to reset all the track counts, last played etc and then finally deleting my rotations and adding new ones.  Now I will have to go through my events to ensure the new rotations will be loaded on my timers.

Mixnetwork

I had same issue, I deleted everything, made all new, now it's working
Anyway, first i thought it was not working, after i made it new, but you have to close and restart Radio DJ every time, then it works
Music was my first love :D
https://privates-radio.de

radiovoltrega

Quote from: rgkluver on September 23, 2022, 07:15:37 PM
After a bunch of trail and error, what worked for me to get AutoDj rolling again after the upgrade was to reset all the track counts, last played etc and then finally deleting my rotations and adding new ones.  Now I will have to go through my events to ensure the new rotations will be loaded on my timers.

I've also tried to reset playcount and priority (and a database optimization). And after creating new rotations now it also seems stable!

radiovoltrega

Hey,

Just a reminder to avoid a stupid mistake we've made. We have an event on startup in order to load the main rotation (in case it had changed with other events) that we have forgotten to change to the new created rotation.

So the simptoms were that rotations only worked when specifing manually the correct rotation in the selector, but not when the program started...  :bash:

Best regards

djdynamix

Tearing my hair out here! I've established that deleting all the rotations and creating new ones does sort of work, but I have some big problems.

First of all, the new rotations are REALLY flakey. If they're longer than a few lines, a "Clear" only adds about half a dozen random lines from the rotation. Also all the events need to be rewritten for the new rotations, and the events don't always load the rotations reliably.

Secondly, and most importantly, I have a LOT of events and rotations I've put together over a few years of operation, and it would take me weeks of work to rewrite them.

Please can you come up with a more reliable way of uodating the database from 2.0.0.6 to 2.0.3.9?

Until you do, I'm just going to have to go back to using 2.0.0.6 which is a pity because I REALLY need the new metadata filters option!

Kiwi

Don't know if this will help but I had simialr issues and resolved things by using a earlier version of Mariadb. Had to use 10.3

Jade

Quote from: djdynamix on December 10, 2022, 01:45:47 AM
Tearing my hair out here! I've established that deleting all the rotations and creating new ones does sort of work, but I have some big problems.

First of all, the new rotations are REALLY flakey. If they're longer than a few lines, a "Clear" only adds about half a dozen random lines from the rotation. Also all the events need to be rewritten for the new rotations, and the events don't always load the rotations reliably.

Secondly, and most importantly, I have a LOT of events and rotations I've put together over a few years of operation, and it would take me weeks of work to rewrite them.

Please can you come up with a more reliable way of uodating the database from 2.0.0.6 to 2.0.3.9?

Until you do, I'm just going to have to go back to using 2.0.0.6 which is a pity because I REALLY need the new metadata filters option!

You should contact or message stevewa here on the forum. I had the same problem and he fixed my database so all my old rotations worked. It should be noted that Roderick posted this video a few days ago on fixing rotations https://www.youtube.com/watch?v=VbBY-kiYPJA - I haven't tried it since Steve got mine working but if it works for you let us know.

Calypso

Some things to consider regarding rotations not working - you may have checked these, but it may help:

* Somewhere along the line (versions of RDJ) the rotations didn't work because of wrong data in the mood/gender/language fields. Fix that with
update rotations_list set mood='---',gender='---',language='---';
* Take a look at your collations within your tables with HeidiSQL. Collations are the character set used for variables, and in the past they have been different to what they should be now. All your character variables (i.e. VARCHAR) should be of type "utf8mb4_unicode_ci". I ran into problems with rotations with these in the past for some reason. Warning: if you have very large values (going towards the boundaries sizewise) you can run into problems because unicode uses more space. If you get a warning/error while trying to change the collation, search for the largest varchars and make them a bit smaller.
* This weekend I've migrated my MariaDB server for RDJ testing purposes to 10.6 (coming from 10.3), and I ran into problems with my own SQL rotation rules. 10.6 seems to be a lot more aware of the difference between ' and " within queries and thus a number of my own SQL rules didn't work anymore.

This is what I can remember doing this weekend and before and my (very extensive) rotations have been entered somewhere early in the 2.0 branch and are working on 2.0.3.9 on MariaDB 10.6.


stevewa

Users should be careful not to overwrite mood gender or language settings which do not have the default value of 'Any'

Jurgen

Still doesn't work here as it should.

Mood, gender and language are correct in the database, SQL rotations work fine, also other rotations with more than one line work fine and I'm using the latest MariaDB and RadioDJ.

The only problem are the rotations with only 1 line, the ones where a radiostream is loaded. I did the same as in the video from Roderick, but it does not work at all!

Now I'm doing a workaround with events loading the radiostream, but using a different rotation. So, when the stream drops, music from the active rotation will start playing, but that's not what I want.

In the database I can't seem to find what's wrong.

Jurgen

Still looking for a solution.

My problem:
Rotation X consists only 1 track: radiostream A. This one doesn't work.
Rotation Y consists several tracks: Songs and jingles A, B, C, D,... (I believe it's 36 tracks and jingles) This one works fine.

I tried to overwrite the Rotation X with Rotation Y and did a restart of radiodj. This way Rotation X and Y both had Songs and jingles A, B, C, D,... in it and this way Rotation X worked fine.

So, I thought I was smart and deleted al tracks from Rotation X again and replaced it with the track "radiostream A". You should think this would work after a restart from radiodj, but it didn't.
Rotation X still blocks everything after using it.

In RadioDJ 2.0.0.6 everything worked fine. I updated the database as mentioned in the video's by Roderick, changed that one thing in the database (it has to be the same everywhere, don't know how it's called anymore) and I changed everything in the mood, language and gender sections to "-" instead of "Any".

It's a bit strange nobody else has this problem and nobody seems to know a solution.

Kiwi

I was able to duplicate your issue with a one line Rotation.

I solved it by the following instructions in the Event:

Disable AutoDJ
Clear Playlist
Load Rotation
Enable AutoDJ

Don't know if this suits you but...

Maybe this is a bug in RadioDJ that should be brought to Marius' attention?