@tiesvdam I don't think you can get rid of it, I solved it by painting the path in a panel, and removing the "extra line" parts by manipulating the path string
The moving ball is from the envelope floating tile but the rest is a painted panel

it involves converting the path to string - remove certain strings - convert it back

I hope there is a better way to do it, but I don't know if there is any.
Anybody knows how to do it in a less cumbersome way?

this is part of the string manipulation, p is the path

var a = p.toString().split(" "); var ax = parseInt(a[6]); var ay = parseInt(a[7]); var acx = parseInt(a[4]); var acy = parseInt(a[5]); var dx = ax + (parseInt(a[14])-ax)*0.95; var dy = parseInt(a[15]); var sx = parseInt(a[17]); var sy = parseInt(a[13]); var rx = parseInt(a[22]); var ry = this.getHeight()-3; var str = a.join("\n"); var path = Content.createPath(); path.fromString(str); g.setColour(Colours.chartreuse); g.drawPath(path, path.getBounds(1), 1.0);

paintedahdsr.gif

@DanH Worked! Thanks man

@Christoph-Hart Can we get the default name of the sidechain to be the name of our HISE project?
Right now, an external sidechain is named "External Sidechain (+bus)" which can get confusing if you have 2 different plugins made with HISE on the same channel.

HISE_SidechainName.png

@d-healey Oh ok good to know. It might need a "skipping change on init" like for the callbacks...

I just found an easy solution for my use case using mouse events instead:

const var bc = Engine.createBroadcaster({ "id": "bc", "args": ["component", "event"], "tags": [] }); bc.attachToComponentMouseEvents(componentsToTrack, "Clicks Only", ""); bc.addListener("this", "md", function(component, event) { if (event.mouseUp) Console.print(component.getId() + " " + component.getValue()); });

@d-healey Ah I had it in a midi script processor - doh!

Thanks!

@Casmat said in Viewport Styling Methods?:

One question, should you use just one panel in the viewport or generate a new panel for each list item you have in the viewport?

If it's a simple list then one panel.

If each item in the list needs an interactive element then use child panels.

@rglides Thanks

@d-healey thank you

@d-healey it's a 1 to 1 relationship in this case so I think I might be ok. I'll test it in the morning and see if it works for me though. I appreciate both your input and replies, thankyou

@jBam said in Midi Controller VST built in HISE... thoughts??:

Seems promising in terms of basics (HISE can send midi out). So does that mean I can link a parameter to a midi out function and have it send ANY midi message like Cc, rpn, nrpn, sysex... or is it Cc only??

So as it stands, HISE built apps or plugins can only send note on/off (with velocity), CC, pitch bend, aftertouch and MPE.
Other messages such as program change, MIDI Clock, MTC, MMC and SysEx are not supported at the moment.
I added a feature request here to make additions to support all message types:
https://forum.hise.audio/topic/11665/fr-support-for-all-midi-message-types?_=1740115136462

@Morphoice

You can map it to a function of best fit using python / matlab.
Ask chat gpt how to do this from a table of data.

Alternatively you could create a lookup table of accurate values.

I didn't realize you were going for analog tracking, that's a different case to digital, yes.
The tracking lookup only happens once per note, so you don't have to worry about efficiency here. Envelopes by comparison need optimization as they are applied per sample.

@DanH said in Tip for those of us hosting files on S3 - use Bunny instead:

Would you mind DM-ing me too please? Guess it possibly doesn't bode well for the future though...

Yeah I'll send it across. If they don't respond I'm just going to post the plugins publically (they're GPLv3). Unless Bunny changes their API or Wordpress significantly changes, there isn't much that could cause the plugin to stop working and it doesn't look like too complicated a plugin so I could probably fix it anyway.

@Lindon Yes, I just tried to do it this way and it worked. Thank you.)

@pelle

Sounds like a bit of work but certainly. You'll have to design the algorithm though and do lots of thinking and testing to actually get something like that behaving smoothly. Try to prototype something simple and then extend it.

@d-healey thanx for your fast response as always
found the issue , akai daw have 2 ways to set / re scan your plug-ins, 1 is in preference and the other is in the plug-in manager, there was the confusion, so I went to the preference / plug-in folder/ and select my Mac hd/laudio/vst and also AU FOLDER, it seems akai route the search by default to its own plug in folder (VST3/au) in its own directory, you need to add other locations manually, PROBLEM SOLVED,thanx

@d-healey Ok well - I downloaded the latest HISE build and removed all the code I added recently - and it seems to be running in PluginVal at least - now the slow process of adding it all back in until it breaks again....

@d-healey
Reading.....apparently so hard for me....
Per advice of the legal dept....when advertising/marketing and mentioning the "source" product we always have to say "based on" the source product AND have the disclaimer concerning ownership. We would make bold, general statements about how our product replicates famous hardware with "uncanny" accuracy, but we never would say that we were the best Marshall JCM800 emulation.
If that all makes sense?

@rglides Hopefully, thanks for the suggestion!