@CatABC I don't have a lot of time right now, otherwise I'd provide a snippet to demonstrate what I mean. Maybe @d-healey could help with that?
If not, give me a week or two and I'll provide something.
There might be something in the actual HISE snippet browser too.
@Christoph-Hart said in How do I get the pixel data under the mouse cursor?:
@Orvillain I could add a wrapper to Path.contains(), then you can at least create shapes with hit zones using paths and test the hover state with the mouse positions, this relieves you from the burden of weird geometry and a JSON file.
Hey Christoph, that sounds like it would be very useful.
This is called multi-timbral, rather than multi-output. Although they are semi-related.
But basically... each one of those buttons activates a panel where you can access a unique instance of a synth or a sampler, or whatever. So in effect... if you want multi-timbral support, you add as many samplers or synths as you desire, and then you use midi processing scripts to control the flow of data between them, as well as showing and hiding sub-panels in your UI, where each sub-panel corresponds to a range of controls for each synth/sampler.
Basically, think of it like building multiple engines within a single plugin. It isn't a trivial thing to do, but definitely possible within HISE.
@Christoph-Hart said in How do I get the pixel data under the mouse cursor?:
@Orvillain you need to rethink that entire approach, even in JUCE it's almost impossible to query the actual pixel at a given position because the image data is passed to the GPU so the CPU will not now the blended state.
Thanks. The only other thing that springs to mind right now is:
Assemble the filmstrip panels as I want them.
Provide a JSON file that gives click zone co-ordinates.
On a click, check the current position, and check if it falls within a specific coordinate region.
If it does, tell the film strip to animate.
If it doesn't, do nothing.
@d-healey ahhhhhhhh suckage. Hmmmm. I can definitely provide X/Y data in a JSON file, and parse the current position in relation to that, to be able to detect which image I am hovered over. But these images might overlap... which meannnnnssss.... hmmm, I need to think about it some more.
Basically the goal here is... load a bunch of film strips that can potentially overlap with some transparent areas.... click on one of them, and trigger the filmstrip animation. But I can foresee that if the images are overlapping, I'll end up triggering the wrong animation if I click in a particular area where they overlap unintuitively.
The ideal solution would be to parse the current pixel (or pixels in a grid around the mouse cursor) and detect if that particular sub panel is transparent or not. If it is, don't trigger the filmstrip animation. If it isn't, then trigger it.
@d-healey Because there's nothing like a getPixelData(x=a, y=b) method for panels I guess?
Say I have a panel, and inside it there are two sub panels, each one containing a PNG image. The PNG images have transparency. I want to sweep the mouse across the top level panel, and have each sub panel process the pixel under the mouse, and return a true if the pixel is transparent (taking a threshold into account) or a false if it isn't.
How would I do this?
@ulrik Yes, this is the kind of thing I was imagining.
You'd have to link the click event of your drum pad to a call to Message.sendToMidiOut() somehow I would guess.
@Christoph-Hart Looks like Jatin has made some progress with this:
https://github.com/jatinchowdhury18/RTNeural/issues/143#issuecomment-2472915024
So does this bring us closer to being able to load NAM models into RTNeural inside Hise???
@d-healey I'd do this in the raw sample content, personally. You could easily script something in Lua inside Reaper to do this.
@aaronventure Is there a good beginner tutorial on how to use Faust within HISE?
@clevername27 Are you using broadcasters?? Those all seem to fire off once on init as they get connected.
@griffinboy I'd love to get a look at your process there!
This looks great @griffinboy thanks!
I was literally pondering how I'd prototype something in Python, and then port it over to HISE. I reckon super basic Python prototype > c++ nodes > ScriptNode network using said nodes.
Yeah nice one, I get it now. It worked inside HISE but not in the plugin because the scope of the broadcasters was wrong. Won't make that mistake again!
I've genuinely been hitting my head against this for 4 weeks. :pouting_face: