java midi in

[menno]

Hi Steven,

do you think it is possible to extend the PianorollObject so that it can draw the notes that i'm playing on my midikeyboard?
Also on the Csound mailing list i'm looking for options to intergrate the live playing of a midikeyboard into Csound. But maybe in the case of using Blue it could be much simpler by the use of the Java API to be able to record midi notes and midi events?
This is just an open question and not in any way meant to bother you with the subject in great depth, i'm just checking and looking ahead for that feature to be able to record and store midi in Blue.

greetings
Menno

[Steven Yi]

Hi Menno,

I actually had a slightly different design in mind where MIDI input is
done on a higher level, so that if you set to record, you choose what
object to record to, be it a PianoRoll, GenericScore, etc.  I think
this is more in line with what you see in other MIDI-based apps for
recording audio or MIDI data, where they only record to new objects as
opposed to rewriting over old ones (at least, that's what's in my
head, having not used a MIDI-based app except for seeing what's in
them every once in a while).

The recording of audio and MIDI will probably be one of the first
major tasks after blue2 goes out, and a lot of that relies on
implementing note pfield metadata on instruments.  From there,
soundObjects will be able to query information from instruments to
auto-setup themselves, which would be especially useful for pianoRoll
and tracker objects.  I am also thinking of samples a good bit and
working out a system for those.  Most likely a percussion-based
sampler instrument will be done first as it will be easier to
implement, then later a keyboard-based sampler with samples assigned
to key ranges, etc. to be done.

Also, regarding the MIDI data, it will most likely be recorded and
translated to notes, with the original MIDI data discarded.  I don't
like MIDI's coarseness of information, so want to to keep get that
into something more flexible as soon as possible.  If MIDI data would
be wanted after that, I would most likely rather put in a MIDI
translator to move back from score to MIDI, but this is an area I have
not spent much time thinking about yet.

Thanks!
steven

On Mon, Apr 6, 2009 at 5:47 AM, menno <nabob_cd@...> wrote:

>
> Hi Steven,
>
> do you think it is possible to extend the PianorollObject so that it can
> draw the notes that i'm playing on my midikeyboard?
> Also on the Csound mailing list i'm looking for options to intergrate the
> live playing of a midikeyboard into Csound. But maybe in the case of using
> Blue it could be much simpler by the use of the Java API to be able to
> record midi notes and midi events?
> This is just an open question and not in any way meant to bother you with
> the subject in great depth, i'm just checking and looking ahead for that
> feature to be able to record and store midi in Blue.
>
> greetings
> Menno
> --
> View this message in context: http://www.nabble.com/java-midi-in-tp22908094p22908094.html
> Sent from the Csound - Blue - User mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bluemusic-users mailing list
> Bluemusic-users@...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>

------------------------------------------------------------------------------
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users

[menno]

Steven Yi wrote:

I actually had a slightly different design in mind where MIDI input is
done on a higher level, so that if you set to record, you choose what
object to record to, be it a PianoRoll, GenericScore, etc.  I think
this is more in line with what you see in other MIDI-based apps for
recording audio or MIDI data, where they only record to new objects as
opposed to rewriting over old ones (at least, that's what's in my
head, having not used a MIDI-based app except for seeing what's in
them every once in a while).

I've worked with Cubase quite a while. The way i was working then was make a loop let's say for 4 bars and then build every time it repeated itself play a new note. This was a nice way to create sequence patterns. Later, after having copied several times these 4 bars i glued them together so it became 1 part. Then i would use my midicontroller to record controller data that influence the filter and the Q (CC74 and 71) of that filter. Also i used another button on my midicontroller later on on the same material to change the expression or volume (CC10 and 7) of the existing notes. Also the level of the reverb or chorus could be recorded on the notes (CC93 and 91 i believe).

Steven Yi wrote:

Also, regarding the MIDI data, it will most likely be recorded and
translated to notes, with the original MIDI data discarded.  I don't
like MIDI's coarseness of information, so want to to keep get that
into something more flexible as soon as possible.  If MIDI data would
be wanted after that, I would most likely rather put in a MIDI
translator to move back from score to MIDI, but this is an area I have
not spent much time thinking about yet.

I agree that midi imposes limits on the score notes of Csound. The flexibility of each of the Csound events was exactly what i missed in the sound possibilities with sequencers like Cubase. In Csound every sound can be molded by the different pfields. A sequencer like Cubase or Reaper forces you to a 12-note octave for example, and i had to use another controller to do pitchbending to get some sort of microtuning in my sounds. Midi notes gives you starttime (p2), duration (p3), pitch (p4) and volume (p5). Pitch and volume in a rather poor resolution.
Perhaps other pfields could be assigned to midicontrollers too?
On the other hand it allows for some quick sketsching. Then do the refinements afterwards but put down the main idea.

thanks for sharing your ideas on the subject, Steven.
greetings
Menno