isPluginParameter and Midi CC (not working in HISE 4.0.0 and 3.x.x)

[hisefilo]

@Christoph-Hart Yes, The goal is to allow user to record automations using CC sliders on any midi controler, not moving sliders on the UI with the mouse.

[Christoph Hart]

@hisefilo but why don‘t you just record the midi data instead of trying to automate through midi?

[hisefilo]

@Christoph-Hart because I want to allow user to live-record midi automation, then have the chance to edit it as an automated parameter. (Is this not a common practice? maybe is just me using it that way)

[d.healey]

@hisefilo In your original gif I don't see you enabling record?

[hisefilo]

@d-healey This gif is a working example for other plugin, not my debug plugin.

yes, did't record but parameter was moving up and down. This gif is the same but record enabled

[d.healey]

@hisefilo So what happens if you enable record in the original example?

[hisefilo]

@d-healey nothing, does not record. give me 2 minutes

[hisefilo]

@d-healey

[ustk]

Just my 2cent, tried a brainworx synth in PT, it both works with mouse and CC on the same automation track

[d.healey]

@hisefilo What is midiAutom.setConsumeAutomatedControllers(); set to?

[hisefilo]

@d-healey true, and false. both fails

[d.healey]

@hisefilo You need to set it to false

[hisefilo]

@d-healey will re-check! compiling...

[hisefilo]

@d-healey

Content.makeFrontInterface(600, 600);

const var midiAutom = Engine.createMidiAutomationHandler();
midiAutom.setConsumeAutomatedControllers(false);

HiseSnippet 1069.3oc2W0saaTDEd1XOPrCTnnHDWtWvEtRUQ1PofDBUmerCVsNwJaZg6hlr6w1ixryrL6ro0Twc77vyBuB7Fz2.3L6Z6c1Dm1fEEQwWXo47yb9Nm472NRqBgzTkl303zYI.w6CnAyjlo6OkwkjAGP71jFAmmMoCYuYIrzTHh34U6PKWuF0I4+d0i1iIXxPnjDg7LEODdBOlaJoNp6i4BQeVDbJO1Q5GzcPnRtuRnxPjTi1ljvBufMANhYEaCJw685EwMJcfgYfThW88TQyBlpdtrP9mwS4mK.6gNj.7hJH2WIhrH1Rkr+TtHZzBONkP7niJ8+ZE9+1zg7H9R5kwgONmgeoFtwCuMpBuZUfWGW301Adq.RdNPpdAjtKMHTySLkbr3YK5.oAziYXX2EJExR1nsGceEJgzrSL6BnuFOrTiVOrc666i+cuusYSLzmZ7ujo8iQOb2LiJ1+676ImvkvNgZ.cogKXvLbk76YxHAnagJuTicRACZuzrXXtfPj09Zk.EMs0XlHErVablLzdI9J4QJCbrr08Z9xlMZ9KM8uJqwiWIuxqckrsoV5WmhsjYwmC56itrHCVJHFuq9HRu4GQ2brvhnrifJ4.I2bbBHuoLOx7mF6C9bTghZxetuy7m6.AOBzDN9p99zGKUm2gjCX2hLxSGb.yvVbM3MhVIAzFt0A7N.tDKBKxhZPO.RuvnRxkMNQIs12ay2nQewRC5Oo6rkG5dV2jEdz.T7OkFf4K9+.6Rv+PPBZFFJ6fExZrFFS6rx7Qz9nL80vOchMQhvSGIxvzrQKDpHdkTkXQSfMoLadEFMudEBVaphxDVK5VvZ6RMmAl.ToJwVIHS4lYtcw9GqJ91Bw6RGwMgSWMF2XEXDeneafw4899PZuwigPSI.qS6+iucZz4Z96TX9sxyfxG+ja7aHi5lmC86214PI254PGGZPyeplISSToUt3.HleJVEk5R7ooNo2Nz2Wwzqj0qdT0RBWCvLY57zhciUYRSkzfZut4gcVy4g0+O27v2AJ1qLxtwBLFviSDPO4kf.aHmiwOA6.OlkILKnVMWdnRpRlpj7P2G5S.ilOYhs0XI1WoCsqwfKMURY6tm.Bf4lz94ceBlrwzXbBVyXQm+1qurx2qOiV.WeaAn+6tMoq8+6lzmnxLb4jgLLID2CfdTVb.1aLDPqKkfvtkj2F19aEmaaOWzbTFke3OweyY1wd1aNyNKX9uhMhYgZ0YgEaZYyS2LmB52x7kKZPGZO6uhUrra3dVXX0q5ZJ9Eqqhe45p3CVWE+p0UwGttJ90qqheyaVwpeYhy9zBaKysbOTjX3TQ49IT4FbfLBdwhqFqdzUl41SFUYtclPbMYrDuhbAW.O+pMu0neYo8xs+sC+ie9Ws8t07yyLP4Z2CvgDZSQAMY3nd464640SxvR2Bp+EpVNQg.

results:

[d.healey]

I'll test it here

[d.healey]

Yeah I get the same result, no data is written in the DAW automation lane

[hisefilo]

@d-healey thanks mate! that makes me feel not that lonely :)

[d.healey]

I think what Christoph is perhaps suggesting is instead of recording automation data for the knob we record CC data for the controller (mod wheel in this case). But then as you point out we'll end up with two automation tracks for the same control which isn't good and it will definitely confuse users.

Also you might have multiple plugins on the same track and a controller automation could affect all of them while parameter automation is targeted to the specific plugin.

[hisefilo]

@d-healey so what do you recommend?

[d.healey]

@hisefilo Praying to the Christoph gods