@VirtualVirgin I appreciate the enthusiasm. When I do take the wraps off, I'm following @d-healey's lead, and releasing the rest of my code to the community. Let me know if there's something specific you'd like.

@ustk @HISEnberg @aaronventure @d-healey Thanks, guys!!!!

@Christoph-Hart Thank you.

@Christoph-Hart That was fast. I'm confused how is that different from what I asked about?

Could the profiler be adapted to measure latency?

@HISEnberg Thanks man. I am indeed using child panels—good thought. I guess I'm wondering if it's a good idea simply to assign the same callback function to all of them. (Is there overhead with that? Etc.) Cheers.

@Tangerine_Sounds said in Sampler Workflow Advice:

this video is exactly what i need

You may find yourself saying that a lot.

I've got an array of dynamically-generated panels (green boxes) inside of a viewport, inside a container panel. I'd like to have a single mouse callback for when users click on a green panel—and to know which panel was clicked. The viewport is to accommodate cases where the number of dynamic panels exceeds the space to draw them.

Any ideas?

Cheers.

@d-healey Yes, capturing and creating a communication channel to your current and potential customers is helpful. Dave and some of the other developers here managed to beat the odds, and carve out a self-perpetuating market for themselves, starting from ground zero. I think those are the best people to ask (as you have here, and people are answering.) Certainly better than me.

@iamlamprey Good advice, though unless you have an audience, you're likely to put a lot of work into videos that no one sees. Though just in general, I agree this is the way to go—nice one, mate.

@aaronventure Help me with the ScriptNode, and I'll help you with this? (And thanks.)

@aaronventure It's a Bundle—a file structure that appears to be a single file (to the user) but is actually a folder. Have you watched the video? It's demonstrated there. The only writing I do is the standard HISE temporary audio and MIDI files when copying them to the host DAW.

@aaronventure @Christoph-Hart

If I understand you, I may doing this in one of my plugins, though I'm going a bit further than that. Users can create complex instruments, within the compiled plugin, and then distribute a single file—which loads into any instance of the compiled plugin. This includes new sample maps, samples, additive synthesis parameters, impulse responses, HISE tables, MIDI files, and so on.

I'm doing it without expansions—it's just drop and go for the user. I broke it up into multiple files, and put them inside a bundle. I'm not sure what would be the equivalent on windows and GUN/Linux, but I'm guess there's something comparable.

Anyway, you're welcome to my code that (assuming it does) provide the functionality you want. Here's a video showing it in action.

Please note that the encoding DSP—which is doing most of the heavy lifting here—is an offline process. The HISE plugin provides real-time access to the encoding data within traditional DAW host workflow.

@Allen interesting - what does this allow you to do?

@d-healey Dave, can you post "it's now" when it's happening, lol?

@Lindon said in Can We PLEASE Just Get This Feature DONE:

meanwhile I have built an automated complaint generator entirely in HISE - that sends silly pointless barbs to the forum every 17 minutes and every 7th time thru asks the dumbest question possible....whilst simultaneously advertising t-shirts for sale... I think at this point I wont need to interact with the forum ever again.....

OMG I just realised I'm a bot.

@Christoph-Hart said in Can We PLEASE Just Get This Feature DONE:

Why stop at a cube? I'm currently working on this and it allows to create a 2D representation of any shape that you can 3D print to get your plugin as a real object.

I'm currently testing the different file formats for each printer, but I expect it to be ready in about 14 minutes.

Finally.

@Christoph-Hart keeps adding all these useless features, and @d-healey keeps improving them, when this is what we really need. I'm talking about a GUI that expands in all four directions at once. But the real mic-drop is that each expansion panel has the original panel transformed—to give users a different perspective on the plugin's existing feature set. It's science.

Also, HISE needs to be louder.

@d-healey Is that more like a philosophy question? I guess none of us really think about all those unused nodes.