BrainModular

Re: Piano Roll Event Outlet

2020-01-29T18:54:43+02:00

great! and sure, i'll remember to email next time

fixed in the next release.
but it's more appropriate to send bugs reports by mail?
at least faster.

Statistics: Posted by bmartin — 29 Jan 2020, 17:54

Re: Piano Roll Event Outlet

2020-01-28T18:52:17+02:00

fixed in the next release.
but it's more appropriate to send bugs reports by mail?
at least faster.

Statistics: Posted by senso — 28 Jan 2020, 17:52

Re: Piano Roll Event Outlet

2020-01-15T00:33:03+02:00

This is great news! Thanks!
BUT! -
link two piano rolls via array out to array in. put one note on channel 1 and another on channel 2. I can see that the array now has the information in it, unfortunately the piano roll doesn't seem to recognise it properly at the 'array in' - everything on roll 2 is still put on Channel 1. even though if it comes out of the second roll's 'array out' the info is there.
Still the feature is more or less there and that is fantastic!

Statistics: Posted by bmartin — 14 Jan 2020, 23:33

Re: Piano Roll Event Outlet

2020-01-12T17:07:56+02:00

the solution 1 is implemented in HH4 !

CODE:

beat position = 1 //first beatevent duration = 0.5 //half a beat-8thMIDI channelMIDI message = 144 //MIDI-NOTE-ONMIDI data1 = 63 MIDI note 62MIDI data2 = 98 //velocity

Statistics: Posted by senso — 12 Jan 2020, 16:07

Re: Piano Roll Event Outlet

2020-01-07T10:42:46+02:00

I was really hoping the new HH would bring a solution to this!

All midi events from a file in piano roll still get squashed into one midi channel when they pass out of the array outlet...

Any chance of a new midi module to get around this?

Statistics: Posted by bmartin — 07 Jan 2020, 09:42

Piano Roll Event Outlet

2019-01-16T21:41:27+02:00

keep old module in legacy folder and make a new one !

Statistics: Posted by oli_lab — 16 Jan 2019, 20:41

Piano Roll Event Outlet

2019-01-15T22:48:59+02:00

I'm not sure i understand the technicalities of backward compatibility, but could a second 'events' inlet/outlet pair be added to the pianoroll - something like 'multichannel events' - which could handle the multichannel midi in either of the ways suggested? or could a switch be added that offers the possibility of switching from a default of merged channels to multichannel with MSG and CHN combined?
If that's not possible how about a Piano Roll substitute module ('Midi Sequence'?) which would add this functionality to the basic piano roll model along with any other improvements that people are looking for? This would avoid any backwards compatibility clash.

Statistics: Posted by bmartin — 15 Jan 2019, 21:48

Piano Roll Event Outlet

2019-01-09T13:59:15+02:00

I prefer the second solution as it is coherent with the way midi messages are usually done.

Statistics: Posted by oli_lab — 09 Jan 2019, 12:59

Piano Roll Event Outlet

2019-01-09T09:11:22+02:00

Could be easily implemented but the pb is the backward compatibility:
the array size will be 6 length instead of 5 actually if we have

CODE:

beat position = 1 (first beat)event duration = 0.5 (half a beat-8th)MIDI channelMIDI message = 144 (MIDI-NOTE-ON)MIDI data1 = 63 (MIDI note 62 : D5)MIDI data2 = 98 (velocity)

or of course we could merge MSG and CHAN info like:

CODE:

beat position = 1 (first beat)event duration = 0.5 (half a beat-8th)MIDI message = 144 + MIDI channel -1MIDI data1 = 63 (MIDI note 62 : D5)MIDI data2 = 98 (velocity)

but in both cases we'll have troubles.

Statistics: Posted by senso — 09 Jan 2019, 08:11

Piano Roll Event Outlet

2019-01-08T16:03:59+02:00

I guess it would be useful, although I don't really deal with multi-channel midi files, but I might when dealing with MPE implementation.

Statistics: Posted by x.iso — 08 Jan 2019, 15:03

Piano Roll Event Outlet

2019-01-08T11:47:42+02:00

Nobody else interested in multichannel arrays from midi piano-roll?

Apart from building some sort of script to parse midi files I can't see any other way to be able to do fun things with manipulating midi file data outside real-time

Statistics: Posted by bmartin — 08 Jan 2019, 10:47

Piano Roll Event Outlet

2018-11-12T00:58:23+02:00

Currently the event outlet of the Piano Roll seems to put all the midi events onto channel one only - if you send the event stream from one roll to another you'll see them going to channel 1. For the purposes of manipulating the event information as an array - sorting and swapping values etc, it would be nice if the channel information could be integrated as well (e.g. to keep the drum track information on channel 10 of a standard midi file).
It would also be good if the array could be easily divided into the chunks of midi information - but that's another subject perhaps...

Statistics: Posted by bmartin — 11 Nov 2018, 23:58

Re: Piano Roll Event Outlet

2020-01-29T18:54:43+02:00

great! and sure, i'll remember to email next time

fixed in the next release.
but it's more appropriate to send bugs reports by mail?
at least faster.

Statistics: Posted by bmartin — 29 Jan 2020, 17:54

Re: Piano Roll Event Outlet

2020-01-28T18:52:17+02:00

fixed in the next release.
but it's more appropriate to send bugs reports by mail?
at least faster.

Statistics: Posted by senso — 28 Jan 2020, 17:52

Re: Piano Roll Event Outlet

2020-01-15T00:33:03+02:00

Statistics: Posted by bmartin — 14 Jan 2020, 23:33

Re: Piano Roll Event Outlet

2020-01-12T17:07:56+02:00

the solution 1 is implemented in HH4 !

CODE:

beat position = 1 //first beatevent duration = 0.5 //half a beat-8thMIDI channelMIDI message = 144 //MIDI-NOTE-ONMIDI data1 = 63 MIDI note 62MIDI data2 = 98 //velocity

Statistics: Posted by senso — 12 Jan 2020, 16:07

Re: Piano Roll Event Outlet

2020-01-07T10:42:46+02:00

Statistics: Posted by bmartin — 07 Jan 2020, 09:42

Piano Roll Event Outlet

2019-01-16T21:41:27+02:00

keep old module in legacy folder and make a new one !

Statistics: Posted by oli_lab — 16 Jan 2019, 20:41

Piano Roll Event Outlet

2019-01-15T22:48:59+02:00

Statistics: Posted by bmartin — 15 Jan 2019, 21:48

Piano Roll Event Outlet

2019-01-09T13:59:15+02:00

I prefer the second solution as it is coherent with the way midi messages are usually done.

Statistics: Posted by oli_lab — 09 Jan 2019, 12:59

Piano Roll Event Outlet

2019-01-09T09:11:22+02:00

Could be easily implemented but the pb is the backward compatibility:
the array size will be 6 length instead of 5 actually if we have

CODE:

beat position = 1 (first beat)event duration = 0.5 (half a beat-8th)MIDI channelMIDI message = 144 (MIDI-NOTE-ON)MIDI data1 = 63 (MIDI note 62 : D5)MIDI data2 = 98 (velocity)

or of course we could merge MSG and CHAN info like:

CODE:

beat position = 1 (first beat)event duration = 0.5 (half a beat-8th)MIDI message = 144 + MIDI channel -1MIDI data1 = 63 (MIDI note 62 : D5)MIDI data2 = 98 (velocity)

but in both cases we'll have troubles.

Statistics: Posted by senso — 09 Jan 2019, 08:11

Piano Roll Event Outlet

2019-01-08T16:03:59+02:00

I guess it would be useful, although I don't really deal with multi-channel midi files, but I might when dealing with MPE implementation.

Statistics: Posted by x.iso — 08 Jan 2019, 15:03

Piano Roll Event Outlet

2019-01-08T11:47:42+02:00

Statistics: Posted by bmartin — 08 Jan 2019, 10:47

Piano Roll Event Outlet

2018-11-12T00:58:23+02:00

Statistics: Posted by bmartin — 11 Nov 2018, 23:58