I just noticed a fix to the midi keyboard has been pushed, does it solve this?

For Reaper, you can change shortcut behaviour.

1 -For plugins you can send all keyboard input to the plugin ( this is done by FX menu.)

2- You can set the shortcut scope to global, normal and global+text field (this is done by actions - edit shortcut )

@bendurso I can't remember. It's been years since I dealt with sample libraries.

@Christoph-Hart said in Monlith reference sample start/end screwed up:

just check the monolithoffset property for differences between the two.

Running into issues with this again. One thing I noticed is I have a sample map, which was previously saved as its own monolith, contains monolith offset values, but when I redirect the sample map to another monolith, these offsets don't change. Should they?

Is it a case that both sample maps need to have the same mapping but the properties of the zones can be different?

@Christoph-Hart that's still hardcoded and all the node instances of that file will share the seed

but you have me an idea to just link the random node from scriptnode into the faust parameter, so that'll work as the random node gets instanced on startup

@d-healey Alright these are fixed now.

@HISEnberg I know. I'm just reporting this issue in the Hise GUI.

@Noahdeetz

I have gone down this route once more, and so I will be testing this again soon,
but this time I am using a peak meter node as the Display Buffer.

So far it's working, but I haven't compiled it yet.

The advantage of using a Display Buffer over a Global Cable is that the Display Buffer has memory of past events (within the buffer). This can be useful if you need to access this data, for instance if you wanted to calculate RMS or other loudness calculations, or if you want to draw a graph that follows the volume over time.

@d-healey Hence why I posted it in Bug Reports :upside-down_face: 😁

I‘ll check them again but I noticed you have turned on the HiseScript compiler optimizations. Does turning them off in the settings help?

@d-healey @Natan The problem continues even today. If we declare the event as undefined it works perfectly. Would there be a problem with this trick?

audioFile.setContentCallback(function(event) { if (!isDefined(event)) { var rootNote = AudioLoopPlayer1.getAttribute(AudioLoopPlayer1.RootNote); knbRoot.setValue(rootNote); } });

Or to be even safer, remove the condition (works as well):

audioFile.setContentCallback(function(event) { var rootNote = AudioLoopPlayer1.getAttribute(AudioLoopPlayer1.RootNote); knbRoot.setValue(rootNote); });

Oh and the pitch detector seems to be working now (at least with my samples)

@paper_lung Ignore me, found it. For those wondering, it's on the plugin window itself under the settings icon.

@bendurso Do you have modulation targets in the script network? I had to remove them before it worked in my network, something like:

"RemovedChildElements": ["Modulator"]

@Christoph-Hart This seems to be fixed by commit: 5a83aef - - revert & remove compile error at argument mismatch (for now)...