You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi again! ... I've been seen quite of 'fun stuff' activity in the qt5 branch lately...so here's a proposal (It is based on the comments a radio technician made me yesterday as I showed my 'Linux based Radio Automation suite' :-):
The starting point is how good is the RDAirplay 'Next Timed Start' time coloring thing... very very useful! RED -> overshedule , YELLOW -> a stop gap.... But this nice feature seems to be restricted to just the MainLog, and only once the log is running.
When handling logs, but, the thing is that, while you can foresee that matter by carefully looking the event timing and mentally make the picture, it would be very useful to have some coloring (the bold blue line is awesome!) and/or help... both in RDAirplay and, to some extent, in DRLogEdit
Until yesterday, I haven't realized how much I rely on those bold blue lines... It would be far harder without that bold blue font styling!... so, why not to add some styling to highlight the timing on just the previous related events? (just only on those that will not play, or will stop after playback, etc, based on the blue line timing)
There're many possibilities... maybe maybe coloring just the time column would be enough, maybe the whole event (never in bold)... the idea is that 'red' events above the 'blue bold' instantly highlight oversheduled events. Converselly, if there's an stop gap, it would be great to have some 'yellowing' on the previous event, to highlight this event will be followed by a stop gap.
Another idea is something like an 'Est. Playback time' field showing how much of the cart is estimated to play... for example: a red 0:00 meaning the cart will be skipped, and yellow value diplaying the cart lenght + est. stop gap showing the gap (again there're probably more clever ways to implement the concept)
Best regards!
The text was updated successfully, but these errors were encountered:
Hi again! ... I've been seen quite of 'fun stuff' activity in the qt5 branch lately...so here's a proposal (It is based on the comments a radio technician made me yesterday as I showed my 'Linux based Radio Automation suite' :-):
The starting point is how good is the RDAirplay 'Next Timed Start' time coloring thing... very very useful! RED -> overshedule , YELLOW -> a stop gap.... But this nice feature seems to be restricted to just the MainLog, and only once the log is running.
When handling logs, but, the thing is that, while you can foresee that matter by carefully looking the event timing and mentally make the picture, it would be very useful to have some coloring (the bold blue line is awesome!) and/or help... both in RDAirplay and, to some extent, in DRLogEdit
Until yesterday, I haven't realized how much I rely on those bold blue lines... It would be far harder without that bold blue font styling!... so, why not to add some styling to highlight the timing on just the previous related events? (just only on those that will not play, or will stop after playback, etc, based on the blue line timing)
There're many possibilities... maybe maybe coloring just the time column would be enough, maybe the whole event (never in bold)... the idea is that 'red' events above the 'blue bold' instantly highlight oversheduled events. Converselly, if there's an stop gap, it would be great to have some 'yellowing' on the previous event, to highlight this event will be followed by a stop gap.
Another idea is something like an 'Est. Playback time' field showing how much of the cart is estimated to play... for example: a red 0:00 meaning the cart will be skipped, and yellow value diplaying the cart lenght + est. stop gap showing the gap (again there're probably more clever ways to implement the concept)
Best regards!
The text was updated successfully, but these errors were encountered: