The German forum talks about ‘non-play function’. This function makes it possible that if an item is played, which is not included in the log, or if no player is playing (for example in assist mode), its own text is sent as a log. The name of the station is mentioned as an example on the German forum.
This function contains a “seconds until ‘no item is playing’ is triggered.”
which you can see as a kind of threshold of how long it takes before the ‘no playing’ metadata is sent.
This function works in the encoder, where you can enter a ‘No item playing’ metadata. The data in that field is then sent as metadata.
I also read in the German forum that it should now also be possible in other logging options. However, I do see the ‘threshold’ here, but not the input field of ‘No item playing’ metadata.
Is this option for the standard logs hidden somewhere else within mAirlist? or is it not yet possible to enter a specific text?
It would be a nice addition to be able to create your own metadata in the separate logs.
In the encoder, you can simply enter the default text for the “not playing” state, correct.
For the Logging section, the configuration is slightly different. Check out the “Scope” settings on the “Filter” tab - they control in which situation this log interface is triggered at all:
So basically, if you want to use the “Not playing” feature, you would create another log interface (or duplicate the existing one with ctrl+c/ctrl+v), check only the “not playing anymore”, and configure it to send the static text.
That makes sence.
Maybe a feature request to make it adjustable seperate in each log. When u use different log files for example;
u have a log for audio stream where u want the url of ur website.
On a live videostream u would like to have ur slogan.
And for rds u simply want the station name.
The way it works now makes sence, maybe this could be a nice feature in the future.
Well, you can do that now, just by setting up a separate logging for the “not playing” case.
The thing is, when we put the separate settings within the config of each single logging interface, there will be a lot of fields/tabs/etc. to add.
For a simple log file, it is very easy: Assuming you have the same filename for all cases, just make four fields in the config: Text to write on start, on stop, on current title, and for “not playing”.
But imagine you do that with e.g. HTTP GET logging, and you want so have some URL parameters only for start, some for stop, etc. - I don’t know how to put that into the GUI efficiently.
