... or to put it in simpler words: I see the whole combo Jsampler-LinuxSampler as a single device that has outs and ins (why ins? I still don't understand why). If it was a physical hardware unit it would be all encased in one box with outputs labeled OUTPUT. Then internally you map the channels to output through certain OUTPUTS. So you select them in the OUTPUTS column shown in the audio routing configuration panel of each Channel. Is not that simple? or maybe I'm missing something ;-)
Cheers, Hector On Fri, May 9, 2008 at 11:14 PM, Hector Centeno <[EMAIL PROTECTED]> wrote: > Recorders, audio interfaces and mixers always label as Output where > audio comes out and Input where audio goes in (at least that is what > I've experienced in my not too superficial presence in the audio > universe :-) ). Regarding Jsampler I think of the Channel Routing > panel as a place where you map that channel's signal to specific > OUTPUTS that LinuxSampler (JSampler) has (so I think of the "Audio > Out" column as a list of LinuxSampler's outputs or that Sampler > Channel output). Not that I'm mapping the signal to Jack's (or Alsa's) > INPUTS. That's why I get confused with the way it is labeled now. So > I'm guessing its just a matter of perspective since I agree with you > that the way the ins and outs are labeled in QjackCtl is confusing. > Cheers, > > Hector > > > > On Fri, May 9, 2008 at 7:35 PM, Geoff Beasley <[EMAIL PROTECTED]> 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. >> >> best, >> >> g. >> >> ------------------------------------------------------------------------- >> 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 >> > ------------------------------------------------------------------------- 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
