Major Issue with Split Node in Scriptnode
- 
Alright, forget all DAWs:
HISE -> Tools -> Simulate varying buffer size
Add the compiled bitcrusher code => complete mayhem.
Nice job HISE, you magnificient debugging beast!
 - 
Alright, it's fixed. It was indeed an issue where the split container expected a full buffer length so when a buffer with something less than this is processed, it started pointing to uninitialised memory which resulted either in silence or (worse) junk signal.
 - 
 - 
@Christoph-Hart Woohoo! Thank you

 - 
@Christoph-Hart Will confirm on our end after merging.
 - 
@Casey-Kolb The fix with the commit was incomplete (forgot to check HISE compilation), so make sure you pull the latest state.
 - 
@Christoph-Hart Back in business
 Works without frame container now. - 
@Christoph-Hart said in Major Issue with Split Node in Scriptnode:
Alright, it's fixed.
You're awesome!

@Casey-Kolb Nice catch

 - 
@Matt_SF said in Major Issue with Split Node in Scriptnode:
@Christoph-Hart said in Major Issue with Split Node in Scriptnode:
Alright, it's fixed.
You're awesome!

@Casey-Kolb Nice catch

+1
 - 
Since pulling in these changes, when I try to compile the effects as DLL I get the following error:
could this be related to the latest commits?

 - 
@Jlev777 Oops, I forgot to fix this line. Please try again, should work now.
 - 
@Christoph-Hart It works, thanks! :)
 
