View Issue Details

IDProjectCategoryView StatusLast Update
0002563ardourfeaturespublic2020-04-19 20:13
Reporterwicked_boy Assigned Tocth103  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Summary0002563: Ability to record multiple MIDI CC's and NRPN's in real time and automatically split out into automation lines.
DescriptionIn Hardware Based studios, it is common for people to have multiple hardware devices (synths and fx units) which may have controllers (knobs sliders buttons) that have pre-determined MIDI CC's possibly even setup as NRPN's). Some devices can have in excess of 20 of these...
The current MIDI implementation in ardour requires each controller to be setup as an automation track within a channel and also linked to the controller (CTRL middle click).. So to setup ardour to deal with this may take an hour or so for each external MIDI device (really not practical)..

Ideal operation would be for ardour to be able to record these events in in the same way one does MIDI notes (press record and play then record in the performance)... Then after the initial record be able to view the individual parameters as automation tracks... (with the controllers preferably automatically assigned already).. Allowing for "fixing" of performance errors e.t.c...

The inclusion of real time MIDI sysex messages would also be ideal, (a sysex message maybe used to control things such as LFO speed.. only the last byte of the message is likely to change, which would enable separate messages to be identified)..
TagsNo tags attached.

  Users sponsoring this issue
Sponsors List Total Sponsorship = US$ 50

2009-02-22 23:19: wicked_boy (US$ 50)
  Users sponsoring this issue (Total Sponsorship = US$ 50)

Activities

hansfbaier

2009-03-12 06:57

reporter   ~0005802

As far as I know parts of that should work: Record some MIDI with CCs.
Then right click on the recorded track, select automation->show all automation,
and all recorded ccs incluing (N)RPNS should appear, each one in its own lane.

As for sysexes I wonder whether you read the blog, but I am not sure how the UI should / will look like.

wicked_boy

2009-03-12 07:35

reporter   ~0005803

When I tried this a couple of weeks ago, the CC's didn't seem to record unless I actually setup the automation .. will try again..

With regards to the sysexes, I have read the blog, this is really a suggestion for the UI.. as sysexes can be used as kind of a controller (e.g. for my TX81z I use it for LFO speed which can't be controlled by standard CC's).. So the messages for each parameter would have all of the bytes except the last exactly the same (which often as recorded would , hopefully this would allow ardour to distinguish between each type)... If you would like some examples of the messages I can put these into a MIDI file and send it across.

The gui would look like exactly like another automation track for each recorded parameter....

cheers

Allan

wicked_boy

2009-03-15 22:52

reporter   ~0005822

slight delay on retesting as I am unable to startup SVN 3.x (see bug 2584).. will try and recompile again tonight..

wicked_boy

2009-03-18 12:43

reporter   ~0005832

Okay I can see that this is happening. but something else is also happening that doesn't look right.. In qjackctl I have only one port (of a possible 20) connected to the MIDI track.. during recording I only moved one controller.. (on breath control).. however large amount of MIDI information appears to have been recorded.. across multiple controllers and even note information ..(even though none were being played on the controller connected to that input)..

Is there something I am missing here??

hansfbaier

2009-03-18 19:06

reporter   ~0005836

A Midi Monitor like kmidimon might definitely help here. It is very likely that the data recorded is indeed what was sent.

wicked_boy

2009-03-18 23:04

reporter   ~0005837

I will install kmidimon tonight.. If I can't test tonight though, it is unlikely I will be able to progress till Sunday (GMT +11)

I did have the MIDI monitor on, but that was for the control port not the port associated to this MIDI track.

Also, as I use discreet MIDI ports for each device, there should have been no other information.

drobilla

2009-04-04 01:04

developer   ~0005856

This has been implemented (by myself) in the 3.0 branch for literally years, save for SYSEX.

You may be seeing a minor bug, at most...

wicked_boy

2009-05-25 16:09

reporter   ~0006028

at the moment I can't even compile successfully (damn it I was loving having working MIDI clock).. however the only thing then is the real time sysex messages ... (recorded like CC's not just one off messages)..and having them somehow look the same as the MIDI CC's....

I'll try and do a mock up..

Dave, once i can get a working version again.. I'll throw you 50 bucks as a thank you .. I know it's not much .. but what I can afford in these times.. With the NRPN's I'll put in another 50 to Hans (if he ends up doing it)..

drobilla

2009-05-25 16:48

developer   ~0006029

Displaying SYSEX as an automation-like curve is not possible. SYSEX does not have a numeric value. Some of them do, but it's SYStem EXclusive by definition, so Ardour doesn't know. (N)RPN is fine.

3.0 is currently in the middle of a refactor by Paul so I can't really make a working version at this time (or it would be a waste of time to do so, anyway). Open new tickets for your compile problems.

drobilla

2009-11-01 20:06

developer   ~0007062

Working again for CC at least, several old related bugs fixed, though I still need to do more testing.

Havn't checked NRPN yet.

drobilla

2009-11-01 20:07

developer   ~0007063

Unrelated to issue, but since you mentioned, MIDI clock sending is working fine for me, but things seems to be offset significantly. Need to look into this and see who/where the culprit is...

cth103

2010-07-21 15:49

administrator   ~0008538

Closing this as fixed; please report problems as separate bugs. Thanks!

system

2020-04-19 20:13

developer   ~0021870

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2009-02-22 23:18 wicked_boy New Issue
2009-02-22 23:19 wicked_boy Sponsorship Added wicked_boy: US$ 50
2009-02-22 23:19 wicked_boy Sponsorship Total 0 => 50
2009-03-12 06:57 hansfbaier Note Added: 0005802
2009-03-12 07:35 wicked_boy Note Added: 0005803
2009-03-15 22:52 wicked_boy Note Added: 0005822
2009-03-18 12:43 wicked_boy Note Added: 0005832
2009-03-18 19:06 hansfbaier Note Added: 0005836
2009-03-18 23:04 wicked_boy Note Added: 0005837
2009-04-04 01:04 drobilla Note Added: 0005856
2009-05-25 16:09 wicked_boy Note Added: 0006028
2009-05-25 16:48 drobilla Note Added: 0006029
2009-11-01 20:06 drobilla Note Added: 0007062
2009-11-01 20:07 drobilla Note Added: 0007063
2010-07-21 15:49 cth103 cost => 0.00
2010-07-21 15:49 cth103 Note Added: 0008538
2010-07-21 15:49 cth103 Status new => resolved
2010-07-21 15:49 cth103 Resolution open => fixed
2010-07-21 15:49 cth103 Assigned To => cth103
2020-04-19 20:13 system Note Added: 0021870
2020-04-19 20:13 system Status resolved => closed