Thats what Christoph Hart thought in 2018 when he started working on SNEX

Christoph Hart
@Christoph Hart
Posts made by Christoph Hart
-
RE: if/else statements inside the scriptnode
-
RE: Export to HLAC monolith unsupported samplerate error
yup, it's just a shortcut to selecting each sample and typing in the values by hand.
-
RE: Export to HLAC monolith unsupported samplerate error
Another option is to "fix" the loop points inside HISE. Your basic samplerate is 24kHz when you've imported the samples and created the samplemaps, but now you've converted it to 48kHz. This means that every sample index is just being multiplied by 2, so if your loop start was at sample index 1000, it now needs to be at 2000.
Just drop this in a script processor that sits in a Sampler and it will operate on the currently loaded sample map (Be aware that if you paste this in the onInit callback it will get executed right away).
/** Select all samples in the current samplemap ".*" is Regex and means everything. */ const var allSamples = Sampler.createSelection(".*"); /** You'll get an array of all samples, which you can iterate */ for(s in allSamples) { /** Just multiply all sample properties with 2 */ s.set(Sampler.LoopStart, parseInt(s.get(Sampler.LoopStart)) * 2); s.set(Sampler.LoopEnd, parseInt(s.get(Sampler.LoopEnd)) * 2); s.set(Sampler.SampleEnd, parseInt(s.get(Sampler.SampleEnd)) * 2); } /** This needs to be called after a sample manipulation op in order to refresh the UI. */ Sampler.refreshInterface();
-
RE: Export to HLAC monolith unsupported samplerate error
Use a batch converter, then it should be just a single click. If you use 48000 kHz the conversion will not change the signal (as it will just duplicate each sample from your source samplerate).
The HLAC codec is fixed to 44,1, 48k, 88k or 96k and there is no point changing the entire codec for a edge case like this.
-
RE: Export to HLAC monolith unsupported samplerate error
Just convert them to 48000kHz
-
RE: Bookmarks & breakpoints
Yes, @Natan is right, I've added the Ctrl modifier because I clicked on it too many times by accident.
Code bookmarks were just a small helper tool that added a commented line with the prefix
//!
(or something like that). Then you could jump between locations using the context menu. However it became a victim of the most recent code editor refactoring, but I think I just commented out the code, let me check... -
RE: Loops failing to play if end loop == sample end
Can you make a minimal example project? It works here.
-
RE: Blurry Panel?!
Yes I think there was an issue with the gaussian blur IPP routine on macOS which is why I deactivated it. Box Blur doesn't look as smooth, but it's way faster anyway.
-
RE: Local variables for namespaces
Could we get local variables for namespaces?
I would say that if you exceed 32 variables in a single namespace it might be better to break down the code into multiple modules for clarity anyway. Also I'd like to keep
local
variables inside inline functions to not confuse people more. -
RE: Preset Browser Tags crash app on Windows
This was just a small glitch introduced by the expansion redesign and should work now...