Table Playhead Animation
-
-
I hope it will return in HISE 3
-
No it will be back and it will be better than before...
-
-
@Christoph-Hart PS is there anything in particular that prevents doing colour fades on the table path?
-
Just your imagination
https://docs.hise.audio/glossary/custom_lookandfeel.html#table-editor
-
@Christoph-Hart Oh yes I'm an idiot!
-
Is there a planned release date for version 3?
It seems like everybody is waiting for it also, so I am too
-
@harris-rosendahl Sometime this year - in reality HISE 3 will never exist because HISE is constantly changing, so although there may be a release tagged as v3 at some point it will be out of date within a week
-
@d-healey Good info, thank you
-
@d-healey said in Table Playhead Animation:
@harris-rosendahl Sometime this year - in reality HISE 3 will never exist because HISE is constantly changing, so although there may be a release tagged as v3 at some point it will be out of date within a week
As I see, scriptnode branch can't be used in a commercial release because it has performance issues such as cpu spikes and also as adviced previously, this branch shouldn't be used.
So when will the scriptnode can be used or Hise v3 will be released?
-
If you don‘t use actual scriptnode, the scriptnode branch is the current branch that everybody uses for their commercial products. What makes you think that there are CPU spikes?
-
@Christoph-Hart Yes I am definately seeing the cpu spikes on the current scriptnode branch exported plugin. When I open the plugin in the Cubase, Reaper or Ableton it is ok. But the cpu usage simultaneously jumps to 100% immediately and returns back again. This is annoying actually.
I've followed your advices and made something similar to this post: https://forum.hise.audio/topic/3626/dynamics-compressor-scriptnode-question/11?_=1616761850750
A frame processing, no oversampling, there are 3 compressors, 3 analysers (controls 3 gain modules) and 3 filters inside. Also like you adviced, I can't compile C++ network because it is broken. So is the current scriptnode ready for commercial releases like this combination? If yes, then I think this cpu spike is a bug.
-
So is the current scriptnode ready for commercial releases like this combination?
No, as I said, scriptnode itself is not ready yet, but you can use the scriptnode branch for building commercial plugins with HISE that don't use the feature.
I think the spikes you're seeing come from the old way the parameter modulation was communicated to the UI and it might be fixed. If not, then compiling the node to C++ definitely will (and this is highly recommended as soon as you go down to frame-processing).
However I am close to the state where I can care about backwards compatibility and migration of old scriptnode patches to the system (there were a few breaking changes that need manual migration).
-
@Christoph-Hart said in Table Playhead Animation:
So is the current scriptnode ready for commercial releases like this combination?
No, as I said, scriptnode itself is not ready yet, but you can use the scriptnode branch for building commercial plugins with HISE that don't use the feature.
I think the spikes you're seeing come from the old way the parameter modulation was communicated to the UI and it might be fixed. If not, then compiling the node to C++ definitely will (and this is highly recommended as soon as you go down to frame-processing).
However I am close to the state where I can care about backwards compatibility and migration of old scriptnode patches to the system (there were a few breaking changes that need manual migration).
It would be awesome at least compiling to C++ in the current scriptnode branch. So we wouldn't have to wait for the v3 release. If v3 is completely different, no problem for me I can build from scratch again. But at least the current scriptnode branch capabilities would be awesome. Thank you for this awesome framework!
-
Yeah, I'm not putting any effort in a system that is about to be replaced in a few months (and releasing a plugin now with the old scriptnode code would be a terrible idea).
I'm currently in the cleaning up phase and making the new SNEX workbench usable by brave people (the compilation process is tightly integrated there so you don't have to specify any custom paths or recompile HISE as it loads the compiled code as DLL during development). I suggest to wait for this (this should happen in the next weeks), then you can try to migrate your old scriptnode patches to the new system and enjoy the shiny new scriptnode...
-
@Christoph-Hart Good to know, Thank you!
