I’ve never understood things like audtty, which remotely control graphical applications.
The inverse of that is fairly easy to understand: a console-based program controlled by a graphical interface. That’s an easy one.
But programs like audtty — and there are a lot of them out there — seem to be backwards.
Just because I can’t wrap my head around it, or can’t see the usefulness of it, doesn’t mean it doesn’t work.
Quite to the contrary: It works great, even up against the newest versions of Audacious.
Of course, running them side-by-side like above, is hardly the ideal. Probably better is running audtty over an ssh session, to control the audio on a distant machine.
But I have probably been working on low-end machines for too long, because still, I can’t see dedicating audio output to a machine that can handle Audacious in a graphical environment, and then committing control to a text-only application from far away.
Like I said, it just seems backward. 😐
But you can run shairport (Airtunes emulator) on older hardware and stream audio from your iPhone/iPad or other iGizmo/iApp. To my suprise getting shairport to work on my 233 MHz machine using a 54MB Wifi card was no trouble at all. http://genericnerd.blogspot.se/2013/03/shairport-on-233-mhz-success-story.html
Pingback: clxmms: Useful at a distance, I suppose | Inconsolation
Pingback: xcplay: A more immediate interface | Inconsolation