softwerk-dev

Re: [softwerk-dev] softwerk input

[Paul Barton-D. <pb...@op...>]

  pre-ps: shimmer.mp3 is actually 4.7MB, not 610kB, so stream it :)

>BTW it would be cool to not have to mentally convert notes into midi
>values. 

Heh. So says the musician. I tend to feel quite the opposite! I tend
to work math and music together and prefer the numbers to the names.

Of course, the right thing is a filter to change the way they are
displayed. Consider it on the todo list.

	 Is it possible to input note values directly from a external
>controller? I tried "Recorded MIDI", but it seems to take everything,
>not just the note value. And it doesn't show the midi number so it can
>be edited later.  

Point taken. I'll add them to the todo list.

>I would like to do the same thing for absolute pitch, say. 

I don't quite understand what you mean here.

--p

Re: [softwerk-dev] softwerk input

[Paul Barton-D. <pb...@op...>]

>How hard would it be to do this? I'd like to try this, if you think it
>would be a decent thing for a beginner to do.  I know c++, but have no 
>experience with any of the libraries of pbd, nor do I have much midi
>experience. This seems like a good place to start!

should be fairly easy, and i agree with the design goals.

in sequence.cc, there is a method called start_midi_grab(). this
connects another method called "handle_midimsg()" to the "any" signal
of the MIDI input parser for the sequence's input port. every message
that is received is used to set the next step until all steps are set,
and then we remove the connection to the "any" signal.

so instead of doing that, connect to the "note_on" signal, and extract
the note number while in handle_midimsg, using it to set the step
value. most of the logic will stay exactly as it is now.

have fun!

--p

Re: [softwerk-dev] softwerk input

[Josh G. <jg...@us...>]

Paul Barton-Davis wrote:

>   pre-ps: shimmer.mp3 is actually 4.7MB, not 610kB, so stream it :)
>
> >BTW it would be cool to not have to mentally convert notes into midi
> >values.
>
> Heh. So says the musician. I tend to feel quite the opposite! I tend
> to work math and music together and prefer the numbers to the names.
>
> Of course, the right thing is a filter to change the way they are
> displayed. Consider it on the todo list.
>

How about color coded?? I don't really care what the note # or name is
myself. I more care what the relative difference is between notes. I
wonder what it would look like if you spread a RGB spectrum over 128
notes. Could you tell the difference between two values? Hmm. Perhaps
display the note value as a tooltip to each entry. Just a thought. It
would be cool to select the note format though.
I find the current way of changing note values to be a real pain. Perhaps
I'm not doing things right, its really hard to control the value with the
mouse though. I usually end up typing the values. Perhaps I should finally
try to get into some C++ and look at your widgets to get a better
understand of how they work :) I've done a bit of GTK widget programming
with Smurf and might be able to help.
I wan't a nice sequencer program but there are some things that are
bugging me about Softwerk. Its a great program, it just could be better :)
I could say this about my program as well. It never ends..

Lates..
    Josh

Re: [softwerk-dev] softwerk input

[Reynald H. <be...@op...>]

all I meant was that if I position the mouse over a value, then press a
key on my midi keyboard, the number will show up in the box, as if I had
typed it in. "absolute pitch" refers to the mode I'm usually in. 

How hard would it be to do this? I'd like to try this, if you think it
would be a decent thing for a beginner to do.  I know c++, but have no 
experience with any of the libraries of pbd, nor do I have much midi
experience. This seems like a good place to start!

reynald



>          Is it possible to input note values directly from a external
> >controller? I tried "Recorded MIDI", but it seems to take everything,
> >not just the note value. And it doesn't show the midi number so it can
> >be edited later.
> 
> Point taken. I'll add them to the todo list.
> 
> >I would like to do the same thing for absolute pitch, say.
> 
> I don't quite understand what you mean here.