I'm using blue for the first time and I was wondering if blue can create and
use MIDI files for playing instruments.



--
View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185.html
Sent from the Csound - General mailing list archive at Nabble.com.

I know you can import midi files into blue and, of course, use them that way
but I'm not too sure if blue can actually create a midi file file or not. I
haven't used blue in a while. In fact, I'll check that out real quick.



--
View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718186.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound can create midi files with the --midioutfile=FNAME option (and the midi out opcodes)


On 21 Nov 2012, at 05:29, John Colgrove wrote:

> I know you can import midi files into blue and, of course, use them that way
> but I'm not too sure if blue can actually create a midi file file or not. I
> haven't used blue in a while. In fact, I'll check that out real quick.
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718186.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"
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

But can I use blue to "edit" MIDI just like in a DAW?



--
View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718189.html
Sent from the Csound - General mailing list archive at Nabble.com.

blue does not export MIDI as it uses Csound-type notes internally. As
Victor mentioned though, blue can drive Csound instruments that send
MIDI, and that can be captured to disk. I do not have plans to support
generating MIDI directly at this time, as a MIDI (or OSC) generating
instrument can fairly easily be created in blue.  If you need an
example, I could try putting one together.

Also to note, I'm planning on putting together a screen recording
tongiht that discusses the new features in 2.3.0.  I'll have it posted
online either tonight or tomorrow morning.  Hopefully it should help
get a sense of what working in blue is like.

Thanks!
steven

On Wed, Nov 21, 2012 at 8:38 AM, peiman khosravi
 wrote:
> You can use blue to edit score notes just like a DAW. It has a piano roll.
>
> P
>
>
> On 21 November 2012 07:56, Cacophony7  wrote:
>>
>> But can I use blue to "edit" MIDI just like in a DAW?
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718189.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"
>>
>

It seems like I'm looking for the piano roll. I wish/hope that the piano roll
can be MIDI associated. Perhaps I don't need it. I was just looking for an
easy way to compose my instruments.



--
View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718206.html
Sent from the Csound - General mailing list archive at Nabble.com.

blue does not record MIDI into PianoRolls at this time.  One can play
an instrument with MIDI in realtime, but the recording aspect is not
there.  blue 3.0.0 will be the release that supports realtime all
around in the program, and recording MIDI and OSC will be a part of
that.  Until then, drawing notes with the PianoRoll works (I'll try to
cover a little bit of that in the video I record tonight).

On Wed, Nov 21, 2012 at 6:34 PM, Cacophony7  wrote:
> It seems like I'm looking for the piano roll. I wish/hope that the piano roll
> can be MIDI associated. Perhaps I don't need it. I was just looking for an
> easy way to compose my instruments.
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718206.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"
>

...Well then I'm looking forward to your video. Can you predict or estimate
when blue 3.0.0 will come out?

Can I download the source code too?
I believe it's written in Java.



--
View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718214.html
Sent from the Csound - General mailing list archive at Nabble.com.

Steven, unless you have your tutorial video agenda locked down, then; 


The Mixer  seems to take some getting used to. Does it always create a
Channel for each and every Instrument? Can the inapplicable Mixer
Channels be removed?   

To me it seems the Mixer overhead created by 30 or 40+ instruments seems
too much. Just not confident yet on its basic use. 

Nice work though!  Brilliant.  All good.  Look forward to the Video. 

blue 3.0.0 will take some time to build; I think maybe February
sometime might be possible, but that's a best guess.  There's some
variables as to how long different parts will take, and I haven't done
a thorough planning session yet to do estimates for each of the parts.
 The work for 3.0.0 not only involves rewriting the current rendering
engine, but also developing a new concept of Machines I'd like to
introduce (something like Buzz Machines, but maybe a better model is
the iOS application TableTop).  It essentially would allow realtime
machines that allow arbitrary signal routing. I'm working out the
details of realtime and non-realtime usage (essentially, I want to
prove to myself that all realtime performance objects can also be used
in non-realtime settings).

I have some work planned for 2.4.0 at the moment, and in December I
will start redoing the blue website, and more importantly blueShare
(do things like tagging on instruments and presets, comments on
instruments, following of users or subscribing to notifications of
instrument versions, adding versions to instruments; that also means
allowing tagging within blue and adding search capabilities to the
instrument and effects system).  3.0.0 work will be done on the side
as exploratory work, and I think it will become mainline work starting
in January sometime.

As for the source code, yes, blue is open source, and the code is
available from the Sourceforge GIT repo:

https://sourceforge.net/projects/bluemusic/develop

It requires using Netbeans to develop.

Hope that gives some ideas of where I'm at with the program and what
I'm planning.  If you have questions about the source code, feel free
to email me off list or use the blue-dev list.

Thanks!
steven


On Wed, Nov 21, 2012 at 9:57 PM, Cacophony7  wrote:
> ...Well then I'm looking forward to your video. Can you predict or estimate
> when blue 3.0.0 will come out?
>
> Can I download the source code too?
> I believe it's written in Java.
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Hello-blue-tp5718185p5718214.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"
>

Hi Adam,

Unfortunately I had finished recording the video last night and then
saw your email.  I was a bit too tired to reply then.  As for the
mixer, the channels are auto-created per instrument, but if your
instrument does not use blueMixerOut, I think blue optimizes out those
channels (have to recheck).  The overhead shouldn't be that much since
it uses chnget to grab the pointer, passes the audio through Effects
(as UDO's), then sums and outputs.

The mixer system though could be changed to not automatically create
channels, or do some kind of detection.  If you have an idea of
workflow for it, I'll be happy to hear it.  (Perhaps better to discuss
on the blue users list or add a feature request.)

Also, as a sidenote, I'm also trying to figure out I am going to
integrate the mixer system with the machine system I have planned.
They might just be mutually exclusive, or the mixer may exist as a
machine in the machine space.  Pure speculation at this point; I'll
post to the blue list once I have some time to write down design ideas
and can do some mockups.

Thanks!
steven


On Wed, Nov 21, 2012 at 11:31 PM, adam  wrote:
> Steven, unless you have your tutorial video agenda locked down, then;
>
>
> The Mixer  seems to take some getting used to. Does it always create a
> Channel for each and every Instrument? Can the inapplicable Mixer
> Channels be removed?
>
> To me it seems the Mixer overhead created by 30 or 40+ instruments seems
> too much. Just not confident yet on its basic use.
>
> Nice work though!  Brilliant.  All good.  Look forward to the Video.
>
>
>
>
>
> 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"
>

Hi Stephane,

Sorry about that!  I had written the email this morning and thought I
had sent it, but after seeing your email I found it in my Drafts
folder.  The other email should now be sent and has the URL.  I will
be using that playlist for future blue videos when I have a chance to
post them; if anyone has a specific request, I'll try to put some more
time into videos as I can.

Thanks for asking about it!
steven

On Thu, Nov 22, 2012 at 10:43 PM, Stephane Boussuge
 wrote:
> Hi Steven,
>
> Where can we see your new video about Blue ?
>
>
> stf
>
>
> 2012/11/22 Steven Yi 
>>
>> Hi Adam,
>>
>> Unfortunately I had finished recording the video last night and then
>> saw your email.  I was a bit too tired to reply then.  As for the
>> mixer, the channels are auto-created per instrument, but if your
>> instrument does not use blueMixerOut, I think blue optimizes out those
>> channels (have to recheck).  The overhead shouldn't be that much since
>> it uses chnget to grab the pointer, passes the audio through Effects
>> (as UDO's), then sums and outputs.
>>
>> The mixer system though could be changed to not automatically create
>> channels, or do some kind of detection.  If you have an idea of
>> workflow for it, I'll be happy to hear it.  (Perhaps better to discuss
>> on the blue users list or add a feature request.)
>>
>> Also, as a sidenote, I'm also trying to figure out I am going to
>> integrate the mixer system with the machine system I have planned.
>> They might just be mutually exclusive, or the mixer may exist as a
>> machine in the machine space.  Pure speculation at this point; I'll
>> post to the blue list once I have some time to write down design ideas
>> and can do some mockups.
>>
>> Thanks!
>> steven
>>
>>
>> On Wed, Nov 21, 2012 at 11:31 PM, adam  wrote:
>> > Steven, unless you have your tutorial video agenda locked down, then;
>> >
>> >
>> > The Mixer  seems to take some getting used to. Does it always create a
>> > Channel for each and every Instrument? Can the inapplicable Mixer
>> > Channels be removed?
>> >
>> > To me it seems the Mixer overhead created by 30 or 40+ instruments seems
>> > too much. Just not confident yet on its basic use.
>> >
>> > Nice work though!  Brilliant.  All good.  Look forward to the Video.
>> >
>> >
>> >
>> >
>> >
>> > 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"
>>
>

Hi Steven 
I am interested in exploring blue after only about a 10 year hiatus :-)
Is there a manual online or a how to posted for a new/olbie to look at?
Kind regards

pp~

Patrick Pagano B.S, M.F.A
Audio and Projection Design Faculty
Digital Worlds Institute
University of Florida, USA
(352)294-2020

________________________________________
From: Steven Yi [stevenyi@gmail.com]
Sent: Thursday, November 22, 2012 6:02 PM
To: Csound
Subject: Re: [Csnd] Re: Hello blue

Hi Stephane,

Sorry about that!  I had written the email this morning and thought I
had sent it, but after seeing your email I found it in my Drafts
folder.  The other email should now be sent and has the URL.  I will
be using that playlist for future blue videos when I have a chance to
post them; if anyone has a specific request, I'll try to put some more
time into videos as I can.

Thanks for asking about it!
steven

On Thu, Nov 22, 2012 at 10:43 PM, Stephane Boussuge
 wrote:
> Hi Steven,
>
> Where can we see your new video about Blue ?
>
>
> stf
>
>
> 2012/11/22 Steven Yi 
>>
>> Hi Adam,
>>
>> Unfortunately I had finished recording the video last night and then
>> saw your email.  I was a bit too tired to reply then.  As for the
>> mixer, the channels are auto-created per instrument, but if your
>> instrument does not use blueMixerOut, I think blue optimizes out those
>> channels (have to recheck).  The overhead shouldn't be that much since
>> it uses chnget to grab the pointer, passes the audio through Effects
>> (as UDO's), then sums and outputs.
>>
>> The mixer system though could be changed to not automatically create
>> channels, or do some kind of detection.  If you have an idea of
>> workflow for it, I'll be happy to hear it.  (Perhaps better to discuss
>> on the blue users list or add a feature request.)
>>
>> Also, as a sidenote, I'm also trying to figure out I am going to
>> integrate the mixer system with the machine system I have planned.
>> They might just be mutually exclusive, or the mixer may exist as a
>> machine in the machine space.  Pure speculation at this point; I'll
>> post to the blue list once I have some time to write down design ideas
>> and can do some mockups.
>>
>> Thanks!
>> steven
>>
>>
>> On Wed, Nov 21, 2012 at 11:31 PM, adam  wrote:
>> > Steven, unless you have your tutorial video agenda locked down, then;
>> >
>> >
>> > The Mixer  seems to take some getting used to. Does it always create a
>> > Channel for each and every Instrument? Can the inapplicable Mixer
>> > Channels be removed?
>> >
>> > To me it seems the Mixer overhead created by 30 or 40+ instruments seems
>> > too much. Just not confident yet on its basic use.
>> >
>> > Nice work though!  Brilliant.  All good.  Look forward to the Video.
>> >
>> >
>> >
>> >
>> >
>> > 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"

Hi Patrick,

There's some videos here:

http://www.youtube.com/playlist?list=PLdiJLUsiIP-wh5U3arDq0sYGaiEuQCMnb

You can view the manual from here:

http://blue.kunstmusik.com/pages/manual

thought it looks like it's a few versions behind.  If you download
blue, the manual does come with the application, and is accessible by
going through the file system or selecting to open it from the help
menu.

Feel free to email me if you have any questions.

Cheers!
steven

On Sat, Nov 23, 2013 at 7:59 PM, Pagano, Patrick
 wrote:
> Hi Steven
> I am interested in exploring blue after only about a 10 year hiatus :-)
> Is there a manual online or a how to posted for a new/olbie to look at?
> Kind regards
>
> pp~
>
> Patrick Pagano B.S, M.F.A
> Audio and Projection Design Faculty
> Digital Worlds Institute
> University of Florida, USA
> (352)294-2020
>
> ________________________________________
> From: Steven Yi [stevenyi@gmail.com]
> Sent: Thursday, November 22, 2012 6:02 PM
> To: Csound
> Subject: Re: [Csnd] Re: Hello blue
>
> Hi Stephane,
>
> Sorry about that!  I had written the email this morning and thought I
> had sent it, but after seeing your email I found it in my Drafts
> folder.  The other email should now be sent and has the URL.  I will
> be using that playlist for future blue videos when I have a chance to
> post them; if anyone has a specific request, I'll try to put some more
> time into videos as I can.
>
> Thanks for asking about it!
> steven
>
> On Thu, Nov 22, 2012 at 10:43 PM, Stephane Boussuge
>  wrote:
>> Hi Steven,
>>
>> Where can we see your new video about Blue ?
>>
>>
>> stf
>>
>>
>> 2012/11/22 Steven Yi 
>>>
>>> Hi Adam,
>>>
>>> Unfortunately I had finished recording the video last night and then
>>> saw your email.  I was a bit too tired to reply then.  As for the
>>> mixer, the channels are auto-created per instrument, but if your
>>> instrument does not use blueMixerOut, I think blue optimizes out those
>>> channels (have to recheck).  The overhead shouldn't be that much since
>>> it uses chnget to grab the pointer, passes the audio through Effects
>>> (as UDO's), then sums and outputs.
>>>
>>> The mixer system though could be changed to not automatically create
>>> channels, or do some kind of detection.  If you have an idea of
>>> workflow for it, I'll be happy to hear it.  (Perhaps better to discuss
>>> on the blue users list or add a feature request.)
>>>
>>> Also, as a sidenote, I'm also trying to figure out I am going to
>>> integrate the mixer system with the machine system I have planned.
>>> They might just be mutually exclusive, or the mixer may exist as a
>>> machine in the machine space.  Pure speculation at this point; I'll
>>> post to the blue list once I have some time to write down design ideas
>>> and can do some mockups.
>>>
>>> Thanks!
>>> steven
>>>
>>>
>>> On Wed, Nov 21, 2012 at 11:31 PM, adam  wrote:
>>> > Steven, unless you have your tutorial video agenda locked down, then;
>>> >
>>> >
>>> > The Mixer  seems to take some getting used to. Does it always create a
>>> > Channel for each and every Instrument? Can the inapplicable Mixer
>>> > Channels be removed?
>>> >
>>> > To me it seems the Mixer overhead created by 30 or 40+ instruments seems
>>> > too much. Just not confident yet on its basic use.
>>> >
>>> > Nice work though!  Brilliant.  All good.  Look forward to the Video.
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > 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"
>
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>