Geoff Beasley wrote:
> On Saturday 10 May 2008 06:39:31 Grigor Iliev wrote:
> 
>> I think I'll rename them to: Audio Out - > Source and Audio In ->
>> Destination
> 
> please don't do that; it breaks the standard convention in the audio 
> universe. 
> an external OUTPUT (SOURCE)  is always an 'INPUT' from within your 
> destination device (Jsampler) NOT an 'OUTPUT', and the 'OUTPUT' from your 
> destination device is always an OUTPUT  NOT an INPUT to another device ( even 
> though in fact it is.)
> INPUT to OUTPUT is how it goes; not the other way around.
> 
>  Qjackctl makes this same error and it's non-sensical from any normal audio 
> point of view. The perspective should never be from "within" the audio 
> source, but from "without". If you ran an audio studio this way you would go 
> totally insane in minutes. Patchways would be completely 
> unmanageable. "Readable Clients/outputs" etc will confuse audio engineers all 
> over the world. Left pane should be Input ( because that's what they are: 
> external outputs coming "IN") and right pane OUTPUTS. That's the convention 
> and it works :) Rui you should seriously consider changing this as I have 
> mentioned before. This isn't a small point actually as it relates to studio 
> logic quite directly. You can choose not to conform but it would make more 
> sense to be compliant.
> 

yes, i can also agree with you ;)

however, the way things are exposed in qjackctl it's all in the 
application client perspective and *not* of the user.

outputs are in fact the application client outlets which might well be 
sources of signal (producers). inputs are in turn client instance inlets 
and should be regarded just as signal sinks (consumers).

this strictly follows the internal jack semantics, regarding port type 
nomenclature model, in the api perpective that is, thus also of the 
client application programmer pov.

afaic, this qjackctl naming convention was in deed "borrowed" (ie. 
copied verbatim) from its predecessor, Matthias Nagorni's qjackconnect 
;) and its been like so for ages if not ever--it's been 5+ years now :)

i guess changing that status quo will cause more confusion than it 
already is, at least to the jack community :P

anyway i might consider having an user preferences option to it, or some 
one could just step in and donate some code? :))

cheers
-- 
rncbc aka Rui Nuno Capela
[EMAIL PROTECTED]

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Reply via email to