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

[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

[hisefilo]

@d-healey

"We gather to seek your blessings for Christoph, the guiding light in the realm of DSP software. May his creativity and wisdom continue to shine brightly, bringing innovation and inspiration to all who follow his path. Grant him the strength to overcome challenges, the clarity to make sound decisions, and the grace to lead with humility and kindness. Bless his endeavors, and may his contributions leave a lasting impact on the world.

Amen."

[ulrik]

@hisefilo

[Christoph Hart]

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.

You end up with two automation tracks which do the same thing if you have recorded a MIDI CC automation and the plugin parameter automation, so that's a point on my side, no?

[hisefilo]

@Christoph-Hart @d-healey You are much more experienced than me. If you think the expected behavior is the actual one, I'm ok with that. I just saw the opposite on commercial grade plugins.

[d.healey]

@Christoph-Hart said in isPluginParameter and Midi CC (not working in HISE 4.0.0 and 3.x.x):

You end up with two automation tracks which do the same thing if you have recorded a MIDI CC automation and the plugin parameter automation, so that's a point on my side, no?

This is the problem. We should be able to record everything in the parameter automation lane, but as it is it appears we have to use a controller lane for CC data and a parameter lane for parameter data when the knob is moved with the mouse on the GUI.

To put it another way, recording into the parameter automation lane with MIDI learn doesn't seem to work.

[ustk]

@Christoph-Hart having two automation tracks for the same parameter seems no good.
Which one wins the contest when playing?
What happens when correcting a live recorded track (aka cc) with, let say a touch-latch mode rec with the mouse?
A lot of weird case scenari are waiting to show... well maybe not so many, seeing this came out just today

[d.healey]

@Christoph-Hart Apparently you fixed this issue before - https://forum.hise.audio/topic/8695/ismetaparameter-automation-help/5

:)

[Christoph Hart]

@d-healey I think that was related to directly recording automation through a mapped parameter in the DAW and not through the MIdI assignment within the plugin.

[d.healey]

@Christoph-Hart ah yes that's a good point!

[d.healey]

@hisefilo In your second gif (the Jimmy's shack one) are you using MIDI learn to control the slider?

[hisefilo]

@d-healey no. Comes learned. But I unlearned and learned again to check. Same results

[d.healey]

@hisefilo I remembered that when I'm automating parameter in my DAW I assign the CC directly to the automation lane rather than using MIDI learn, I don't know if that's available in all DAWs though.