I do use the PlayerInfo Class introduced by Phillip Whelan.

In my current solution, the setlogfeature is connected to the valueChanged Signal of "playposition" to calculate the current playing track using the PlayerInfo Class.

Eniginerecord and shoutcast are also continuously calculating what audience is listening.

It looks like a good idea, to let only one class calculate this and emit a signal when the current playing track is changed. I am not sure what is the right thread for this work and what is the outcome for enginerecord and shoutcast. For now, I am satisfied with the current solution.

I do use the PlayerInfo Class introduced by Phillip Whelan.

In my current solution, the setlogfeature is connected to the valueChanged Signal of "playposition" to calculate the current playing track using the PlayerInfo Class.

Eniginerecord and shoutcast are also continuously calculating what audience is listening.

It looks like a good idea, to let only one class calculate this and emit a signal when the current playing track is changed. I am not sure what is the right thread for this work and what is the outcome for enginerecord and shoutcast. For now, I am satisfied with the current solution.