Re: [Qutecsound-users] chnget vs. invalue

[Andres C. <man...@gm...>]

Hi Alex,

Yes, this version brings back support for chnget and chnset. As you
say, the main difference is that chnget and chnset work more like
softeware buffers, since the values are kept inside Csound. What
happens when you call chnget or chnset is that the internal channel
value is modified there and then. If you want to expose the channels
to the widgets, you must remember to add a chn_k line in the header.
OTOH, invalue and outvalue work as callback functions so when you use
the invalue and outvalue opcodes in Csound, they call the registered
callback function, and it is the application using the Csound API
which must store the values.

chnget and chnset are now working in QuteCsound, but the caveat is
that they can't be duplex. If they are they will behave strangely, so
for now just make the channels either input or output, but not both...

Cheers,
Andres

On Fri, Jan 28, 2011 at 5:30 PM, Alex Hofmann <ah...@gm...> wrote:
> Hi Andres,
>
> I discovered the menu point Configuration->Widgets->EnableWidgets,
> and than I can choose between "chnget" and "invalue".
>
> I've read, that "chnget" works as a softwarebus, to the csound API. What
> is the difference to invalue?
> Are multiple invalues using one channel?
>
> Best,
> Alex
>
> By the way, QtCsound 0.6.1 is fantastic, thank you very much!
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Qutecsound-users mailing list
> Qut...@li...
> https://lists.sourceforge.net/lists/listinfo/qutecsound-users
>