Multiple instruments, single project or multiple projects?

Christoph Hart

Alright, I just commited the improvement for the script processors - it just restores the content values without recompiling the script - the onControl Callbacks get executed of course.

Check out the example that switches the table values of another script processor:

HiseSnippet 1271.3ocsW82aZaDF9bRr1h6XpcZ+4jlk+KhRpKNgzjrpoU9QngTf.AhCjtnNi8Y3B19PmOHPp5mj8kbeC1tyFGLAHML0ZIv9d+wcO988dd3nJAaB88wDfvyZLtODH7Ch0G6Q6lqqAxCTLOP3GEKa3SgD4PSYG22v2GZADDV+cbCBatAH35e9irFNFdlvol..cLxDVB4hnSs9Wu88HGmBFVvFH2XQm9sEMwd4vN3AL7rtXJPeCydFcfUL3gslHXHBdqOPHk3d6pR5o09tLppp20db4cerOk.lCHDnGUmkNPPT3eYWBhGagnXRcpAExly0yhsFWuK9VuvkVG4iZ6.4Cz.0YXJzLHWWjiU0nxlO.HrQ0oEw0CKh+rXYjE5d6SKlOOvg7zLhWNEVaVHswLPRaYPp.1whOAKAdBwf2Fgv6Eh0MIn9zod3X6mlXcInKzIXM80ESHw5S9T4gFDYVocHzW92k+fhl19p6gOrcksO3zhoN3zNYJz7lZtYFQ7NXLaPK7Mm99StfY7R8bUR2cDw97rEu8lQEunvnRGyrap2YHkjeLtg8o100apd5I8x+9h0Jz7tKzKea1CqdbCmsq0vZuLW05hiZzplyqK07nVtWnejmY9z4aUwIamyp18t6Jby494yBKzTU8cWVoX5LJ6jPZS9kh1to+lgyRMzKOVMDmszupPuqpwgUS88X3jiuZWU77QuF6Zsum1Eoq2ywnxIoKODZmGiKeBlju69srynhOYXQbNkqeSBo3U6vl.m1naPPFdzxXqANFrMMrNP.wUsCbpwjJSZo7Ljmjh78tU1JX5SHEaExgcaiyhGwlubXOJi0nZXYEYMoRzSJ6Hqkh+Yq2H8pWI+gSqeVk6S9Zonb8g7cY8gDJB5Wffc4wMyr7oDRxxJHJz0W42jUxw2OIq8mdgOrqRBoOOYId0rqg8.OSJB6Ii8pfovy7Rtkzmj1T5yROzis8hbwgHA63.IKxKuhQdjzR5MvsMjrCqn4L.xhis6Z4cGUBzmcCFPsSFxY9PPluT6Z1q2mkX72YY+ROM1uYXgNVfXuhdH5Y8gSTxhJOyYw1Ntooki3VCJCKHrollWxALo4yEelDNKTZfzyymHxD0EAHl3hj38CCpIw+MEv7xWLQzn5ZbkU9uFMwAqSMi1UQNd7Qzwwm4u8xshg38WDW9Fi.r+qhOJM8K+pDoM+2BhwnxMLXveVdbfojJA2VHCNvyWj9FkeH28VjEsKi6t6go1IvPWHpSWJyxgodH6Mb9SDeANIH5jZoRwkitmo0m.6aPfMvUcLFmz2vsuC7bVmZG4vm8qBIYcvl8lii1OrCD3LY6A11PxxTF95pYrLogf3lif+rm19sGRmmotD27zW5uRb+4n5yq07DI+aDR9SDQD3aBBX9emX3yOf1C.VFTCfvwhoOTc1qgm071KqczckFSNHWv3d2bSosa5zxY+vwrur2lG5QgiAOUIjWHVEQM6tXMj0V.wi8N9z0PRsPMjEVBm+.kIDOlsM1jNEraHVn4+2SOtBP4b7.JxqSYCJAMhonUYfac1wyMgLj34Ac74mmdMdaObbJ9XdkoNzyJUzgsm3TiOVXhSsHm.WCSB9ilgaV3ZneefEFl7BN3+lr+ABarrVz1DNtcYmi9ill7BwKYHewYr6JmwdqbFoW4L1eky30qbFGrxYb3ijA+OsjY.E6FRK.f+CjAFVbL

d.healey

Thanks, going to build this now :D

d.healey

"(along with the functions for restoring synths as a whole)."
Could you tell me a bit more about this?

Also I noticed an issue with the script I'd made, if you add a modulator to an envelope and then click the save button, then you remove the modulator and then hit load the saved modulator won't reappear until you add another modulator to the envelope. Playing around with this and changing the values in the modulator etc can also cause HISE to crash and close.

Christoph Hart

Just use Synth.getChildSynth() and call the export / restore methods on this object to restore whole sound generators (and even samplers with sample maps).

Adding modulators programmatically is a bit difficult because it sometimes doesn't update the interface (if it's of any help, the compiled versions won't have this problem...)

I'll need to check this a bit more thoroughly. Can you reproduce a crash with certain steps or is it just random?

d.healey

I made a quick video to demonstrate how to cause the crash using the script I posted yesterday. Also how do you post code here so it's on one line like you do? I use the ``` but it's always placed in a large box.

https://youtu.be/fJ9vA6hHmEc

Christoph Hart

Thanks, I'll investigate.

You are posting XML snippets. If you post HiseSnippets (the ones you get using File -> Export -> Export as Web Snippet), you'll get a String without line breaks which fits nicely in one line...

d.healey

Cool, I found another way to crash HISE :) this time I'm using restore and export on childSynths, basically whenever I make a change and hit save and load it crashes. Try adding a container and a sampler to the container and it crashes instantly without having to press any buttons even!

HiseSnippet 1184.3ocsV8+SabCE2GvM0KaTsNs+.73mBprzj1xV0XnUR.1xJDh5QQUpppy4NGN2dwNxmu.YH9mX+kt+C1d19tbWBWYDjVDBc980O989X6WeoHfljHjHmu7zoioHmux0eJWE0Ihv3nt6ibdn6wjDEUhshZOcLIIgFhbbV8W0Bb7VCY982+RaRLgGPKDgPmIXAziXiXpBo+wKeEKN9PRH8T1nRV+7W1MPv6HhEo.dV0sIZLI3Sjyo8HZyVwEMgQuHA4zz8YOsg7SsF7m603y9axYGz3iu3T8mnfTojxUmAtibbc9G3mi6AgLkP5qHJJDy0ZKBm5GItfaS8YrD1fXpdQKjOfIq3CEwg5Mu9aTmHVbX+7RXBBhR+hB5p1B525dLKjMSdQg8qMJvEdTtz5rxsAuV2S34TBdqYg2ib8CjrwpBMZr8MYR+LnypDsxe459jmzsWmidy9G3Wql96tmVqifqfpciDp52nryiT02t4l6nUi6Hov9ASvIvdC5r3wDNMdKbDKjhYpsvDdHNgLQu.y3XUDXhjBQpFPMRT3IDYtu80th2EmmNRXnQT8MJavFagaB+A4urTM1puwDaQDLYHINgVoMZvzk22fAvPkLkt3d47Xw.RLVL3iz.E.YhBeAPvwQPyvrClPhSoI3gBoYo.9GrKL0vjF0xbOMgJsoYehh.6qqt1lGepx3Vlc4UNRBjkvyoJa3mEcnTFR41BaCs+cGMVHUDt5m.8rDK13BENHVvoVDYf9V3AoJbRDQp2UR5PJbnIf9c2npblNg0mGv5hRQKZfhejfDNe2ocpRI302vnYVEs01P+oktAMm69ZRPktazLy8bmK4MOcjg5atHKABh4iFPop2bZpOWNClyk28dHj5RZcFrp4NXF9mWHvfrG+3MqcUMuRt9N16KmvByaOsKOjdYcFjzq080CeSuNm18jdlyMc16niZuWmW4WaXJOPwDbrf2SnnmvqaRA3yhZFNrJU5BlTDGSkUoUegq7VbqNrEGPkaY4TF6XCwYRw6t6bm81rlGn2CnXulNNlDPKSSyNMbASEYoX.UanTLxrPScxOW64cCluI463UyCJTKj+LhUVpuSMHOioKzjZ.4C1JTy8qKPkA0PSxCxtmmMyEjdMUqZXook2CXciTCts.ToWpO.aQ5+EvtFt6e9WNpc2d4HvdPqjgBdWNScxX5r0VBYtjlnYDwxhJHfkkZHdUXVgna9bEJ6vO7v0pYlCeoLOasd9yVZhHhEpmSoL2DY3PHmG3969mz6pqsAqbDdXVDrWqXBw5tktZJOBdeQ9rL2sPT55oJBwMe.FFCPDlFSTyOafd1pLEvIz4d8sqtpjvTSKO60RLvPyJGXnUUcf6HbejaelJHpZ7tRE3EZo+ei2rwuV28fgCgahJ.6ZtG9166rVKATdsHUw3meLQIYWBScBu83CC1FPAjvAFZhdRzUzrJ65l505JiOkG1LeL0LkszqcxT1JWIZDIPJ9PfkVpGv6AFI.l3lQl8fY2g03V4LQMtGASc9gf.cg36AjWsGOco83YKsGOeo8X6k1ieXo83GWZOdws3gdD+8RUhQ1iEHz+B3sqkq.

Christoph Hart

Alright, thanks. BTW, do you know how to run HISE in debug mode from within Visual Studio?

Just change the configuration to Debug in VS2015, compile and it should open a debug instance. If you get a crash there, it stops in the debugger and points to the line of code which causes the crash.

This information will vastly improve the efficiency of tracking down those bugs - not that there are any left :)

d.healey

That's a good idea, I shall do it :)

d.healey

Just tried building the debug 64bit and I got this fatal error:
"1>D:\HISE Development Builds\HISE-master\projects\standalone\JuceLibraryCode\hi_native_jit.cpp : fatal error C1128: number of sections exceeded object file format limit: compile with /bigobj"

The regular standalone 64bit build worked fine though.

Christoph Hart

Ah yes, that one. Go to Project -> Properties (Alt+F7) -> C++ -> Command Line and add /bigobj in the
Additional Options box (which should be empty).

This happens because the Debug version creates a bigger intermediate object file before linking it to the executable and your computer is maxed out on RAM for these steps.

d.healey

With the code I posted a few days ago and the crash I described with the container and sampler the debugger breaks here:
alt text

Using the same code, adding a sampler, making changes, saving and restoring them using my scripted buttons crashes HISE at this point
alt text

I'm really not sure what I need to be looking for in VS it's been many years since I did any work in it and nothing on the scale of HISE so hopefully these images are of some use!

Christoph Hart

That's what I suspected, thanks for checking this. BTW, if you click on "Break" in the last picture, it should point you to the line (that would be interesting, because the second error is a bit more critical because it wants to read from an object that was already deleted (and even then, it should say 0x0000000005 and not 0xFFFFFFFFF.... :)

d.healey

Have you found a solution for this crash?

Christoph Hart

Nope not yet, I got caught up in writing a lossless audio compressor the last days :)

d.healey

Oh that's even better :) how's it going?

Christoph Hart

It works well for decaying samples (with ~60% size which is equal to FLAC but the decompression is way faster because the algorithm is much simpler).

For sustain samples it's not that good though (80-90%) but maybe I can improve this.

For general audio files it's horrible - when compressing a mastered music track you still end up with 99% file size.

I'll devote a new blog entry to this once it's done where I'll explai how it works.

Christoph Hart

I am using three compression algorithms, each with different decoding / compression ratios:

the "Block" algorithm is a simple bit depth compressor without any processing
the "Delta" algorithm detects a cycle in the waveform and stores delta values until the cycle is invalidated
the "Diff" algorithm uses 4x downsampling + bit depth reduction for the error signal (basically you take each 4th sample, draw a line between them and store the deviation of the second and third sample).

I made some more tests & first decoding benchmarks:

=====================================================
FLAC ratio:	33.1% file size
Block ratio:	74.2% file size
Delta ratio:	66.8% file size
Diff ratio:	57.3% file size
=====================================================
PCM speed:	11842.3x realtime
FLAC speed:	1705.3 x realtime
Block speed:	10086.3 x realtime
Delta speed:	8175.8 x realtime
Diff speed:     tba.

The performance limit is uncompressed PCM decoding, which works at about 12000x realtime speed. While offering a far better compression ratio, FLAC's decompression speed is far behind the others (14% of PCM speed). The Block algorithm comes pretty close (and in a streaming context it might surpass the uncompressed PCM performance because it has to load fewer bytes from the disk). I didn't implement the Diff decompressor yet, but I expect it to yield something like 6000 - 7000x realtime speed, which will be the bang for the buck algorithm.

Another speed advantage will come from using memory mapped files for this (the FLAC reader in JUCE doesn't support memory mapping).

This format will also be used for the preload buffers so it'll drop the RAM usage significantly (currently the preload buffers are stored as 32bit floats!)

d.healey

This looks awesome! well done. The drop in RAM usage will be very welcome but what is the effect on CPU?

Christoph Hart

Well if you can decompress 8000 voices in realtime the CPU usage for each voice is 0,0125%

Multiple instruments, single project or multiple projects?

12

1.9k

10.7k

93.0k