Dynamics, Limiter and Saturator (I'm not using wet amount on the unit because unit will be a member of the fx chain and we want to blend original signal) gives very very small delay and makes a phase problem when they used alone on parellel line.
Also If we use this units in a arrayed fx line like above, it will give a little more latency because of the sum of the delays on each unit. But these latencies are very very small, I think they are smaller than 1 ms.
When I tried to give little small delay on dry signal's simple gain unit, it's impossible to catch it. Also the latencies will be different on different computers I think.
I use i7, 12GB RAM, 1TB SSD, 2x2GB Graphics PC.
I´m affraid not Christoph. I set Embed AudioFiles in plugin to YES so I think it isn´t the explanation. Anyway I´ll show you the content of Appdata/Roaming folder in both computer. I try to copy and launch the app again in the other system and then make a screenshot...
thanks , for the moment...
I mean the finished compiled plugin. HISE compiles the plugin successfully but;
When I open it on a DAW and start to play, the DAW is freezeng and not responding. I understand that this is why that I use above routing on master contaner. Because the channels are conflicting.
Actually no need to do that, just leave it 1&2 to 1&2 on master container like you do in snipped.
Ah yes that is a safety measure so that existing user presets will not be overwritten.
The UserPresets that you build in HISE will be embedded into the plugin. When you launch it it checks if the AppData folder exists and only if it doesn't exist it extracts the presets.
It works great! Thank you so much for your support.
I've used my plugin in FL Studio 12 with all buffer sizes; from 256 to 2048, it works on all of them
You are so fast for problem solving thank you so much...
in the dynamic example:
in thye musicbox example:
catch the vu meter in these examples.
No need to password because no need to use this zip file. We only use VST3 SDK.
The reason of compiling error is that I'm using Visual Studio Enterprise 2015. I've installed Visual Studio Community 2017 and the problem is gone.
I am finally able to connect Rosegarden MIDI playback port to HISE! I just have to use the standard Midi through-port 0, easy right? Strangely all the other virtual ports created are not seen by HISE, but this one works!
Thanks so much for the help! hope that this post will be useful for other Rosegarden users. Thank you for the nice project!
Looks like your connection to Forum was lost, please wait while we try to reconnect.