Wouldnt something like a mixer with each channel having its own thread?
On Sat, Apr 26, 2014 at 2:49 PM, Vesa <[email protected]> wrote:
> I'm a bit all over the place with these questions lately, but bear with
> me...
>
> I'm not very familiar with threads so I might be way off here, but seems
> to me that in FxMixer, we go through all of the channels in a recursive
> function just to add them on the job queue - and we do this every
> period. Additionally it seems (I could be wrong as I'm not sure how the
> queue works) that this puts the channels in the exact opposite order
> than what they should be processed in.
>
> Would it make sense to instead create an array or QVector that stores
> the order of the channels in which they should be placed in the queue,
> and only update this array each time channels are added/removed or
> channel sends changed? Then just add the whole array each time in to the
> queue...
>
>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> LMMS-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
--
Jonathan Aquilina
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
