I threw together a sneak preview of the new Cabbage VST patcher I'm
working on. The latest feature allows native Cabbage plugins to be
recompiled on the fly, anywhere in the signal chain. It's not quite
live coding, but it's still a lot of fun. All of the plugins shown in
this video are native Cabbage plugins, therefore all their code can be
accessed and recompiled on the fly too. I don't expect to release it
for a while yet, but thought this latest feature was too cool not to
show!

https://vimeo.com/62518410

It's all done with Juce.

http://www.rawmaterialsoftware.com/juce.php

We created the look and feel ourselves.

On 23 March 2013 23:25, Alex Weiss  wrote:
> Rory,
>
> This looks amazing! What graphics toolkit are you using, if you don't mind
> me asking? Qt?
>
> Alex
>
> On Sat, Mar 23, 2013 at 4:19 PM, Rory Walsh  wrote:
>>
>> I threw together a sneak preview of the new Cabbage VST patcher I'm
>> working on. The latest feature allows native Cabbage plugins to be
>> recompiled on the fly, anywhere in the signal chain. It's not quite
>> live coding, but it's still a lot of fun. All of the plugins shown in
>> this video are native Cabbage plugins, therefore all their code can be
>> accessed and recompiled on the fly too. I don't expect to release it
>> for a while yet, but thought this latest feature was too cool not to
>> show!
>>
>> https://vimeo.com/62518410
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>

This is fantastic!  How difficult would it be to send score events
into a cabbage module from my own app?

Cheers,
~ andy.f



On Sat, Mar 23, 2013 at 7:19 PM, Rory Walsh  wrote:
> I threw together a sneak preview of the new Cabbage VST patcher I'm
> working on. The latest feature allows native Cabbage plugins to be
> recompiled on the fly, anywhere in the signal chain. It's not quite
> live coding, but it's still a lot of fun. All of the plugins shown in
> this video are native Cabbage plugins, therefore all their code can be
> accessed and recompiled on the fly too. I don't expect to release it
> for a while yet, but thought this latest feature was too cool not to
> show!
>
> https://vimeo.com/62518410
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

osc will probably be the best bet. nodes in the graph can only accept midi or audio as each is essentially seen as a vst plugin. It would be easy to write a simple 'listener' plugin that would be hardwired to listen to your external app and output midi or audio accordingly..

sent from a mobile device...

Very nice Rory!  I had been meaning to add something similar to Blue
and seeing this is very inspiring.  It's super interesting too that
you're using full CSD's per item.  Well done!

On Sun, Mar 24, 2013 at 11:18 AM, Rory Walsh  wrote:
> osc will probably be the best bet. nodes in the graph can only accept midi
> or audio as each is essentially seen as a vst plugin. It would be easy to
> write a simple 'listener' plugin that would be hardwired to listen to your
> external app and output midi or audio accordingly..
>
> sent from a mobile device...
>
> On 24 Mar 2013 11:10, "andy fillebrown"  wrote:
>>
>> This is fantastic!  How difficult would it be to send score events
>> into a cabbage module from my own app?
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>> On Sat, Mar 23, 2013 at 7:19 PM, Rory Walsh  wrote:
>> > I threw together a sneak preview of the new Cabbage VST patcher I'm
>> > working on. The latest feature allows native Cabbage plugins to be
>> > recompiled on the fly, anywhere in the signal chain. It's not quite
>> > live coding, but it's still a lot of fun. All of the plugins shown in
>> > this video are native Cabbage plugins, therefore all their code can be
>> > accessed and recompiled on the fly too. I don't expect to release it
>> > for a while yet, but thought this latest feature was too cool not to
>> > show!
>> >
>> > https://vimeo.com/62518410
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>

The only problem is recompiling an instance if midi-in is needed. audio effects can be recompiled without problems but midi ones lose midi functionality after I call csoundCompile. can't seem to figure out if it's a problem with my signal graph or a problem with Csound.

Its probably related to the fact I had to abandon calling csoundReset between calls to compile. It causes a crash each time. I'll look into it a little more when I'm back on my Linux machine. It's easier to debug csound stuff there than on windows.

If you have the code in a git branch or somewhere accessible, perhaps
we can take this to the dev list and sort it out there.

On Sun, Mar 24, 2013 at 11:39 AM, Rory Walsh  wrote:
> The only problem is recompiling an instance if midi-in is needed. audio
> effects can be recompiled without problems but midi ones lose midi
> functionality after I call csoundCompile. can't seem to figure out if it's a
> problem with my signal graph or a problem with Csound.
>
> Its probably related to the fact I had to abandon calling csoundReset
> between calls to compile. It causes a crash each time. I'll look into it a
> little more when I'm back on my Linux machine. It's easier to debug csound
> stuff there than on windows.
>
> On 24 Mar 2013 11:24, "Steven Yi"  wrote:
>>
>> Very nice Rory!  I had been meaning to add something similar to Blue
>> and seeing this is very inspiring.  It's super interesting too that
>> you're using full CSD's per item.  Well done!
>>
>> On Sun, Mar 24, 2013 at 11:18 AM, Rory Walsh  wrote:
>> > osc will probably be the best bet. nodes in the graph can only accept
>> > midi
>> > or audio as each is essentially seen as a vst plugin. It would be easy
>> > to
>> > write a simple 'listener' plugin that would be hardwired to listen to
>> > your
>> > external app and output midi or audio accordingly..
>> >
>> > sent from a mobile device...
>> >
>> > On 24 Mar 2013 11:10, "andy fillebrown" 
>> > wrote:
>> >>
>> >> This is fantastic!  How difficult would it be to send score events
>> >> into a cabbage module from my own app?
>> >>
>> >> Cheers,
>> >> ~ andy.f
>> >>
>> >>
>> >>
>> >> On Sat, Mar 23, 2013 at 7:19 PM, Rory Walsh  wrote:
>> >> > I threw together a sneak preview of the new Cabbage VST patcher I'm
>> >> > working on. The latest feature allows native Cabbage plugins to be
>> >> > recompiled on the fly, anywhere in the signal chain. It's not quite
>> >> > live coding, but it's still a lot of fun. All of the plugins shown in
>> >> > this video are native Cabbage plugins, therefore all their code can
>> >> > be
>> >> > accessed and recompiled on the fly too. I don't expect to release it
>> >> > for a while yet, but thought this latest feature was too cool not to
>> >> > show!
>> >> >
>> >> > https://vimeo.com/62518410
>> >> >
>> >> >
>> >> > Send bugs reports to the Sourceforge bug tracker
>> >> >
>> >> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> > Discussions of bugs and features can be posted here
>> >> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> > "unsubscribe
>> >> > csound"
>> >> >
>> >>
>> >>
>> >> Send bugs reports to the Sourceforge bug tracker
>> >>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> Discussions of bugs and features can be posted here
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> "unsubscribe
>> >> csound"
>> >>
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>

On Sun, Mar 24, 2013 at 7:24 AM, Steven Yi  wrote:
> Very nice Rory!  I had been meaning to add something similar to Blue
> and seeing this is very inspiring.  It's super interesting too that
> you're using full CSD's per item.  Well done!

Yes, this is the most exciting part, imo.  Can I put score events into
one of these CSD's and make some kind of play/stop/rewind instrument
or module in cabbage for listening to it while playing around with
different routings and effects?

~ af

> Yes, this is the most exciting part, imo.  Can I put score events into
> one of these CSD's and make some kind of play/stop/rewind instrument

no problem.

> or module in cabbage for listening to it while playing around with
> different routings and

routing can be done on the fly so you can dynamically send audio wherever you like. But each module can only receive midi,  audio or OSC. Also keep in mind that cabbage plugins support Python through Csound so it's possible to build python midi note generators.

/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

On Sun, Mar 24, 2013 at 8:09 AM, Rory Walsh  wrote:
>
>> Yes, this is the most exciting part, imo.  Can I put score events into
>> one of these CSD's and make some kind of play/stop/rewind instrument
>
> no problem.
>
>> or module in cabbage for listening to it while playing around with
>> different routings and
>
> routing can be done on the fly so you can dynamically send audio wherever
> you like. But each module can only receive midi,  audio or OSC. Also keep in
> mind that cabbage plugins support Python through Csound so it's possible to
> build python midi note generators.

Ok, I'm trying to work this out in my head without knowing a whole lot
about how this all works, so bear with me ...

The way I understand it is I can generate a CSD with my app that
includes an instrument for the audio output with a score that drives
the instrument.  Then I can put the CSD in a Cabbage module that
outputs the audio and enables routing to other Cabbage modules?  That
would be sweet.  If the Cabbage graphs and module settings can be
saved and opened again after closing Cabbage it would be exactly what
I've been looking for.

---

I got Cabbage built on Linux Mint 14 fairly easily, but there's some
kind of audio driver issue holding me up.  I get lots of feedback when
I try to make an effect, and when I mute the system audio I can't get
it back afterwards.  The same thing happened when I tried out Ardour
3.  If I can't figure it out soon I'll switch over to Windows and try
it out there.  How hard is it to build Cabbage with MinGW?

Cheers,
~ andy.f

> The way I understand it is I can generate a CSD with my app that
> includes an instrument for the audio output with a score that drives
> the instrument.  Then I can put the CSD in a Cabbage module that
> outputs the audio and enables routing to other Cabbage modu

this is correct.

> would be sweet.  If the Cabbage graphs and module settings can be
> saved and opened again after closing Cabbage it would be exactly what
> I've been looking for.

They can.

> I got Cabbage built on Linux Mint 14 fairly easily, but there's some
> kind of audio driver issue holding me up.  I get lots of feedback when
> I try to make an effect, and when I mute the system audio I can't get
> it back afterwards.  The same thing happened when I tried out Ardour
> 3.  If I can't figure it out soon I'll switch over to Windows and try
> it out there.  How hard is it to build Cabbage with MinGW?

Never built with mingw but I'm working with Linux mint too. I'm in transit at the minute. I can help sort your build errors later on. But note that the new patcher code is not yet on github.

>
> Cheers,
> ~ andy.f
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

On Sun, Mar 24, 2013 at 8:50 AM, Rory Walsh  wrote:
>
>> The way I understand it is I can generate a CSD with my app that
>> includes an instrument for the audio output with a score that drives
>> the instrument.  Then I can put the CSD in a Cabbage module that
>> outputs the audio and enables routing to other Cabbage modu
>
> this is correct.
>
>> would be sweet.  If the Cabbage graphs and module settings can be
>> saved and opened again after closing Cabbage it would be exactly what
>> I've been looking for.
>
> They can.

Awesome!



>> I got Cabbage built on Linux Mint 14 fairly easily, but there's some
>> kind of audio driver issue holding me up.  I get lots of feedback when
>> I try to make an effect, and when I mute the system audio I can't get
>> it back afterwards.  The same thing happened when I tried out Ardour
>> 3.  If I can't figure it out soon I'll switch over to Windows and try
>> it out there.  How hard is it to build Cabbage with MinGW?
>
> Never built with mingw but I'm working with Linux mint too. I'm in transit
> at the minute. I can help sort your build errors later on.

No build errors, just the driver issue which is not cabbage specific.
I disable the mic input and it seems to be working ok, now.

> But note that the new patcher code is not yet on github.

I'm with Steven on this one ...push soon!!!  =)

Cheers,
~ af

Are you using Jack?

sent from a mobile device...

I don't think so.  Not sure.

On Sun, Mar 24, 2013 at 9:27 AM, Rory Walsh  wrote:
> Are you using Jack?
>
> sent from a mobile device...
>
> On 24 Mar 2013 13:17, "andy fillebrown"  wrote:
>>
>> On Sun, Mar 24, 2013 at 8:50 AM, Rory Walsh  wrote:
>> >
>> >> The way I understand it is I can generate a CSD with my app that
>> >> includes an instrument for the audio output with a score that drives
>> >> the instrument.  Then I can put the CSD in a Cabbage module that
>> >> outputs the audio and enables routing to other Cabbage modu
>> >
>> > this is correct.
>> >
>> >> would be sweet.  If the Cabbage graphs and module settings can be
>> >> saved and opened again after closing Cabbage it would be exactly what
>> >> I've been looking for.
>> >
>> > They can.
>>
>> Awesome!
>>
>>
>>
>> >> I got Cabbage built on Linux Mint 14 fairly easily, but there's some
>> >> kind of audio driver issue holding me up.  I get lots of feedback when
>> >> I try to make an effect, and when I mute the system audio I can't get
>> >> it back afterwards.  The same thing happened when I tried out Ardour
>> >> 3.  If I can't figure it out soon I'll switch over to Windows and try
>> >> it out there.  How hard is it to build Cabbage with MinGW?
>> >
>> > Never built with mingw but I'm working with Linux mint too. I'm in
>> > transit
>> > at the minute. I can help sort your build errors later on.
>>
>> No build errors, just the driver issue which is not cabbage specific.
>> I disable the mic input and it seems to be working ok, now.
>>
>> > But note that the new patcher code is not yet on github.
>>
>> I'm with Steven on this one ...push soon!!!  =)
>>
>> Cheers,
>> ~ af
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>

sent from a mobile device...

I find it pretty stable when using just the stand alone host.

On Sat, 23 Mar 2013, Rory Walsh wrote:

> I threw together a sneak preview of the new Cabbage VST patcher I'm
> working on. The latest feature allows native Cabbage plugins to be
> recompiled on the fly, anywhere in the signal chain. It's not quite
> live coding, but it's still a lot of fun. All of the plugins shown in
> this video are native Cabbage plugins, therefore all their code can be
> accessed and recompiled on the fly too. I don't expect to release it
> for a while yet, but thought this latest feature was too cool not to
> show!
>
> https://vimeo.com/62518410
>

What am I supposed to see?  There are beeps and a yellow (orange?) stripe, 
occasional coloured rectangles....  No idea what is happening.  I assume 
that there is something wrong with the video?

==John ff

If you're not seeing the little pink creatures chasing the giant blue
elephants then something is definitely wrong!



On 24 March 2013 18:54, John ffitch  wrote:
>
>
> On Sat, 23 Mar 2013, Rory Walsh wrote:
>
>> I threw together a sneak preview of the new Cabbage VST patcher I'm
>> working on. The latest feature allows native Cabbage plugins to be
>> recompiled on the fly, anywhere in the signal chain. It's not quite
>> live coding, but it's still a lot of fun. All of the plugins shown in
>> this video are native Cabbage plugins, therefore all their code can be
>> accessed and recompiled on the fly too. I don't expect to release it
>> for a while yet, but thought this latest feature was too cool not to
>> show!
>>
>> https://vimeo.com/62518410
>>
>
> What am I supposed to see?  There are beeps and a yellow (orange?) stripe,
> occasional coloured rectangles....  No idea what is happening.  I assume
> that there is something wrong with the video?
>
> ==John ff
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

Yeah!!



--
View this message in context: http://csound.1045644.n5.nabble.com/Cabbage-patcher-demo-tp5721434p5721480.html
Sent from the Csound - General mailing list archive at Nabble.com.

Not yet, for now it's just plain old Csound5 but there are some nice
features in Csound 6 that will no doubt be used in the future.

On 25 March 2013 17:24, alfonso santimone  wrote:
> great Rory!!!
> is there CS 6 under the hood?
> a.
>
> www.elgallorojorecords.com
> soundcloud.com/alfonsosantimone
> www.facebook.com/alfonsosantimone
>
>
> On Mon, Mar 25, 2013 at 2:08 PM, Shawn56  wrote:
>>
>> Yeah!!
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Cabbage-patcher-demo-tp5721434p5721480.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>