> If you don't have doxygen, the manual doesn't get built. I see Antti
> still hasn't updated the copy on the JACK web page. But, there's
> still a copy on my system you can look at: <www.joq.us/jack/refman>.
No doxygen, gotta hit your site :)
> Yes, that sounds right. Anything more would be appropriate for a
> specific transport control client. For status display, the transport
> state and perhaps optionally the frame time in HH:MM:SS:DD format
> could be useful. Alternatively, you could display Bar, Beat, Time
> information, but only if it's available.
> There's code in JAMin CVS for this <http://jamin.sourceforge.net>. It
> supports both the old and new transport interfaces, which makes it a
> lot more complex. But, doing just the new stuff is easy.
> Most of what you need is in these two relatively small source files...
By looking into those files, JAMin doesn't seem to have Bar:Beat:Time
display, or have I missed it close? But anyway, that's a minor.
> I recommend compiling the transport control conditionally based on the
> existence of jack_transport_query() in libjack. That way, your code
> still works with older versions of JACK, but with no transport
> control. There's code in JAMin `configure.in' for that, too.
I guess I can do it too, very easily. OTOH Isn't there any way to get the
JACK's version from some header file at compile time? Guess it should be
some #define ... like this example for 0.82.3:
#define JACK_VERSION 0x008203
> There's no reason for qjackctl to be a timebase master. That is now
> only required for generating extended time information, which you have
> no reason to do.
> Any JACK client can start and stop the transport. No special
> privilege is required. It can be done from any thread. I can't think
> of any reason for you not to make those requests if the user presses
> the appropriate buttons. Since qjackctl is generally visible on the
> user's display (or KDE panel), it seems like a convenient place to put
I'll try to put this transport gadgets on qjackctl very soon. My doubts
lie in where in the GUI? That is, without disrupting a lot the layout
already there. The first place where I can think of putting the transport
buttons and state display is under the Statistics tab (which sould be
renamed to Status tab :)
A complete GUI redesign should be needed nevertheless, and that will be
for qjackctl 0.1.x release branch, in near future. Any suggestions will be
welcome, of course.
rncbc aka Rui Nuno Capela