@d-healey When I use Console.print it does seem the SampleDropper is performing BEFORE the Viewport.

Interface: Object 0x8371f570 (SampleDropper)
Interface: 50.0 (Samplemap)

I've got the Viewport calling for samplemaps in oninit. I've got the SampleDropper contained to the SampleLoadSave.js.

I guess I assumed that oninit was processed first and then the other .js files.

How do I go about switching the order in which their callbacks trigger?

Github is a confusing beast.

@d-healey said in Programmatically scroll the viewport to a given element...:

HiseSnippet 1290.3ocsW9ubhaCDGWlDe8fdsWuN8APC8eflzTLXLvj9CZHIcXtlbLkbYtNsctwwVDTiQhwVjDtax6V+y93z2f1U1dsgDljbLS4Ohrr18i9p0Zk1LHT5whhjgDihmLeJiX7LygyEpw8F6xEj96SLdt4kb1USkgJphEoH6MepaTDymXXrwOoMxn3lj3e+yOrmafqvik+JB4TI2i8y7IbU9aGz8k7ffCc8Ymvmrf01c66IE8jAxYff1vrFYpq2EtmyN1UaVAShwSNvmqjgCUtfX.a1S5Oe3X4UhD6OkGwOKfo6XQFBfRdMo2Xdf+.bwFQHFaNHeouQxR+KLOh6yydedH3yhGfl6whw.iB2mjr9.jjwBRZyDI8Bygdg7op7Qz54iM6KTrvQtPndQojXKov6JX1SBVHT6Lw8B1ggPmLOp3Tq11T3OU2sTIHbGonW5FROM8irE86nnymyT8jSlJEPmJkyrnbtmbEaRD3wu8GvqFICoU3PuZ6R4zukZUS+vVaUsTwX61Y5rnwUJ2Gd9KokoaQ4.nhkx3tSDCllXSKucB5c9SIWTo7uKJWUOok3h.tfQGMS3o3RAUJdoPdlkVvgxfJdnZ2FVSAyXUK89REi7fgBNQpm2JIud2R2.zV8xLFX4pZwjhsmaPvYvFwJKOaZAca8rzbwE9rqikPfzyMfNGBMVzuAhQwKs.l3b0X5WSspR+JZrw6VrTwaENzIeCjQbM9eEBKyqBFcyBAfikJ1qDUhmmR2Thd6gFMZkiktHBXgqbXchY384XEwrImwBWLPqMD14tb5vSdboCdIeKVvPonufqd0TVZ+CkA95s45muaxCI8iIjFUHUgfop3jnOOMIh4iwVB2WmEkEpIwKhEO1hbaHeZJjgAbeVXLfOxLd6vJb90822U4pSoSkEH0orPEWGQL1mcIblXRBdQy8YQWnjSi0c5lPhwSezJ+57I966NOuy9cuh6qFSLLM9an6XF+7wJcOGCBYVDbjLbVtgQg38hjBueCyj7xZkRZsRaqm11Hs0NssYZqSZaqz11oscPNY.QhVHRKjoEB0BoZgXsPtVHXKjbcjb8LshjqijqijqijqijqijqijqijafjafjajEFPxMPxMPxMPxMPxMPxMPx1HYajrMR1NKBijsQx1HYajrMR1FI2DI2DI2DI2DI2L6iGRtIRtIRtIRtIR1AI6fjcPxNHYGjrS19BjrCR1AI6fjagjagjagjagjagjagjakskCI2BI2BI2FI2FI2FI2FI2FI2FI2FI2Na2LRtMRtCRtCRtCRtCRtCRtCRtCRtCRtSVhRG8gMYY9O6AOtIOiu6zky3iTy0mr9jXCIS399AL7tib65C1wlNj+NvTSSqcpAVJV73qIt4Swe8ltQyFMhecb4Wi3AShTft5OApJSe9zqiXTe1H2YAJZzE.G39vKX9mHismb2JZfZoj9yBbUKWfktRxzAzhcwpZzUtHfEw7Eqz7CnpqZ2aUWOVI9ByAbk23UqwBqPi5ah9ePio0p9IlGLZDySkKvMMO7MqagoOvz+KxYJt37ibgO8vFAyimMYHThtGClcgfEDouWof9Ryj90z80QfgLgebm+E9kNnktuQ5fV3fvlNnzo25kbqqtZ3mF+FPSh3h+KZdjtOcEW2Baz4u0yaYT2ww5qqiMVWGsWWGattN5rtN1Zccr8C6n9+c5GmojSRRaHjiFbPb4QFFGHbgcfw6VI+GPeXG+g

yep - that looks like it was it.. thanks again.

@Straticah You can do anything you like, it's triggered in the mouse callback. The regular HISE sliders use shift click so that's what I used.

@Christoph-Hart Alright gotcha, this is good enough for now.

It seems like the shadow is always the same size no matter the zoom (drop shadow from path scales with zoom properly) and there's a size cap as well?

@d-navarra said in Sofia Woodwinds on github:

I thought I could start with an acoustic piano instead?

Go for it. When you're trying something new you'll build it more than once, it's all learning at this stage.

@d-navarra said in Sofia Woodwinds on github:

AHDSR - Reverb and velocity modulator are sufficient for a nice sounding acoustic piano or would you guys consider to use any other inbuilt fx?

It's your project, do what you want. Experiment to see what you like the sound of.

@d-navarra said in Sofia Woodwinds on github:

Since I'd like to use it as starting point and keep building on it

Don't do that. A piano is totally different to a flute which is different to a drum, etc. Build separate projects for each, using what you learned from the previous ones for the next. If you write clean modular code you'll be able to reuse it nicely in future projects - your first code will not be clean, so you should try and improve it with each iteration (I've been writing HISE code for 7 years and I'm still rewriting my code to improve it).

@d-navarra said in Sofia Woodwinds on github:

ould you guys link the envelops to the global modulator or directly link the parameters to some controls on the GUI?

I would decide this as I get into building the project and seeing what works and what is easiest to implement. Again, this is something you need to decide as you're going along. You should probably try both ways, and any others that you think of because - you're in the learning phase here, anything goes. You have my permission to fail repeatedly until you find the solution you want.

@meto396 I don't see anything wrong in that code. Make a new test project with one button and one panel and see if the issue occurs there.

@clevername27 said in Quick ScriptNode Tutorial:

You don't need to compile them at all.

The non-compilation requirement for Script Node also applies in cases where there are Faust nodes?

@ally using per voice oversampling is hugely ineffective so it‘s deliberately deactivated.

You can enable a global oversampler with Engine.setMinimumSampleRate() if you need that but usually aliasing on the oscillator level should be fixed otherwise.

@d-healey I've restarted my Mac and now it works! thank you. this was a good That was a good tip with the floating window

@aaronventure Yeah thanks, I know PluginDoctor but that's more about the project needs indeed

Still crashing on my favourite OS in release builds

@meto396 Aha I get it, you might be able to do it through scripting - but I don't know how :)

@Christoph-Hart Tested it, works perfectly here! 🙏🏻

@WillDevelop said in Set step size of button for pluginParameter ?:

then there's nothing you can do about it, right?

Open an issue on the github page and link to this thread.

Is the multipage creator any good?

Yes very good. Much software.

Jokes aside, it's not ready for client use. I have a vague roadmap for it, with phase 4 being stable enough to promote this as solution for HISE devs, but we're not there yet.

Phase 1: Use it for the internal HISE dialog windows. This is pretty much complete and the snippet browser is a glorious example of a new UX-friendly future of HISE.
Phase 2: Use it for the HISE installers. It kind of works but I'm still breaking those as I work on the multipage creator core architecture. I aim for the HISE 4.0.0 installers to be built with this system though.
Phase 3: Use it for my own projects as installer solution. This way I am responsible of fixing backwards compatibility stuff
Phase 4: Make docs & examples for other devs to use this
Phase 5: Integrate this entire system into HiseScript so you can use it to make modal dialogs, use standardized CSS for look and feel etc.

So we're at phase 1.5 at the moment but I decided to put it on hold and resume the work on the glitchfest that is called HISE for the next weeks.

@d-healey yeah, I just checked and with a script FX you can select the onControl callback (because it doesn't have the onController() callback). So it seems that something is just checking if the name vaguely matches and then returns the first match and calls it a day like a underpaid teenage employee...