@toxonic For importing external c++ as nodes

@Christoph-Hart Excellent ! Thanks

@d-healey Got you! I didn't think that would interfere. Thank you! That fixed it.

@Christoph-Hart
Okay, found it and enabled OpenGL, it works better. Still not really smooth, but i can work with that so far.
I checked out system monitor, and found, that only one CPU core is really working, since i enabled OpenGL. I will try to figure out, why.
However, thank you for your help so far! :-)

@d-healey Well, that was easy. Thanks a lot for your help! This is my first experience with development.

For some reason it only compiled VST, but at least it works :)

@Christoph-Hart said in Rubberband v3:

The license got pricier too though

Everything is pricier today :)

@Lindon -ok this is a bug - doing it that way doesnt work - you have to create a whole new softbypass container and then put your node inside it...

We've confirmed this is not just specific to our project but happens with any project on both Mac and PC in certain DAWs (Cubase, Bitwig, Live) using the most recent develop branch. We've tested on many different computers with all the permutations. I'm really not sure what's going on here, but it doesn't have anything to do with the bitcrusher. It happens when using the split node in any project. In certain DAWs, the VST will only Output the left channel, regardless of the effects in the chains.

@toxonic It was in the error message you posted ;)

45ffbe1b-d9b3-4926-981e-9739f5c36e30-image.png

@Lindon the Spectral Analyser changed.... You are meant to be able to create your own curve (but I'm not sure it works?! 😆 )

@Christoph-Hart Oh My GODDD 😂😂😂😂😂

Still seeing this one.

@Christoph-Hart said in Adventures in ScriptNode - Episode 3 - Bit Crusher:

@Lindon Then either reduce the bit amount or the input gain (quieter signals will have more quantization noise).

well that might be an interesting approach - reduce the gain pre-bit reduction, then boost the gain post - but I cant find a way to boost a signal in ScriptNode - the core.gain only goes to 0dB...oh hang on silly me - I can set the params for the gain in teh node itself...

@d-healey --yeah thats what im thinking I will have to do when I get to that part of the process... unless @Christoph-Hart has done the pull by then...

Actually all those loop types are supported in SNEX, if you take a look at the SNEX test suite, you'll see a bunch of test cases that use them:

https://github.com/christophhart/HISE/blob/develop/tools/snex_playground/test_files/loop/for_loop2.h

BTW, most features of the SNEX language are covered by a test file, so if you want to explore what is working, you can build the SNEX playground (tools/snex_playground), then click on the SNEX logo on the top left to load any test (there are about 500 tests in there). It's also a great way of reporting bugs within the SNEX language, so if you find anything, just write a test file that reproduces the issue and I'll add it to the list (that's how I implemented most of the SNEX language features).

However in most cases you don't need to write these manual loops and can just iterate every value of a container using the range based for loop. This is a known concept in C++ (and for(n in myArray) is the HiseScript equivalent.

https://www.cprogramming.com/c++11/c++11-ranged-for-loop.html

@d-healey a few reasons.

@gorangrooves Awesome! No problem :)

@ulrik what a Legend 🙌🙌🙌💯🥃👏🎢
That code was just amzing 💯🔥

alt text

@Christoph-Hart Thank you, yep I need to properly get my head around this stuff!