ProppFrexx ONAIR User-Forum

Please take at the new v3.0.14.3 - which I just uploaded. It adds something to play with... a kind of a first version. It doesn't cover all possible dynamic or conditional filters, but at least a lot. You can now use standard track macros within script-line filters. Any regular track macro like for ...

I assume you mean setting the Media Entry Type, e.g. to "Hot", "Music", "New Music" etc. (else there is no other possibility to change the 'color' directly; the color of the playlist entry is assigned to this entry type!) However... The Media Entry Type is an attribute ...

That's why I said: "...Yes, there are improvement planned..."

Do both exist in the same lib or in different lib?
Are you search in both libs or only in one?
And note, that 2 physical files mean 2 different media entries!

Yes, there are improvement planned, but it is already possible today using multiple PF instances using multiple advert libs. E.g. one PF instance is the main/master station playing the main program and scheduling one master advert lib using overlays. The 2nd PF instance uses its own Advert Lib and i...

I did some further tests here, e.g. doing a mass change on 500 tracks...but that also worked out as expected.
Or could it be, that you just tested (searched for the new data) too quickly?
For example saving the TAG data to 100 tracks and re-reading those TAG data back in might take some time...?

Ohh yes, you are right. I do actually remove all those 'unplayed' entries/tracks from the history when a new program is started in a new playlist window. But in your case I assume you start the program as a TimeUpdateSync within the same playlist window...and yes, in that case it seems I have simply...

?How could it be worst - as in my tests it works perfectly? Before you also posted: "...Strange! I did a test here and it works as you describe...." - which means the AutoWatch feature was/is to some extend working! The Find Window (result) once displayed re-reads the TAG data from the phy...

When rescan says, that it needs to read 76 TAGs, that means, that the file modification date of 76 files is 'younger' that the date when the TAGs have been last read in for it. ProppFrexx and the MLS keep a date and timestamp for each media entry when the TAG data was last read in. If the AutoWatch ...

I just tested the scenario here, but the AutoWatch feature was working as expected. E.g.: - I edited the TAGs of a file with the ProppFrexx Tagger (i.e. I changed the Artist name to something funky). - That in turn triggered the 'AutoWatch' feature of the MLS, which re-read the TAGs respectively. - ...