On Jan 19, 2017, at 08:20, Kyle Robbertze wrote:
> This should also be possible by (ab)using the icecast/shoutcast module
Nice idea! You wouldn’t even need an external IceCast or ShoutCast instance,
seeing as GlassCoder now includes an integrated icecast server. Then
On 19/01/2017 15:14, Fred Gleason wrote:
> On Jan 19, 2017, at 08:09, Cowboy >
> wrote:
>
>> If I understand correctly what he's after, I'd be considering
>> a VNC in view-only mode, and never mind library and all of the
>> potential problems that would come
On Jan 19, 2017, at 08:09, Cowboy wrote:
> If I understand correctly what he's after, I'd be considering
> a VNC in view-only mode, and never mind library and all of the
> potential problems that would come with that.
That’s one solution (albeit an expensive one in terms of
On Thu, 19 Jan 2017 07:53:30 -0500
Fred Gleason wrote:
> I suspect there’d be a lot of nasty edge cases to deal with.
If I understand correctly what he's after, I'd be considering
a VNC in view-only mode, and never mind library and all of the
potential problems that
On Jan 19, 2017, at 07:38, Emir Yapıcı wrote:
> I mean, RDAirPlay's Log Machine side. Like green for Now Playing and light
> green for next events.
Gotcha.
I suspect there’d be a lot of nasty edge cases to deal with. For example, what
should happen in cases where
Hello Fred!
I mean, RDAirPlay's Log Machine side. Like green for Now Playing and light
green for next events.
19 Oca 2017 15:34 tarihinde "Fred Gleason" yazdı:
> On Jan 18, 2017, at 19:09, Emir Yapıcı wrote:
>
> Can we follow which log and what
On Jan 18, 2017, at 19:09, Emir Yapıcı wrote:
> Can we follow which log and what is playing in the studio from RDLogEdit,
> like coloring in RDAirPlay's log machine? It would be helpful for client side
> to watch log correctly.
Hi Emir:
I don’t think I understand your