truc - support thread

[thecontrolcentre]

Nice plugin ... my No.1 in the DEV Challenge

[Exit Zero]

This is in my top 5. Very, very nice!! It'll be part of my performance setup as long as it passes my "stress tests".

thanks for the feedback

out of interest, what are your stress tests? (and did truc pass?) I'd be interested in case I could use or adapt your testing for my own pre-release testing of plugins

I usually set up an Ableton Live 'session view' template with several tracks loaded up with clips using follow actions and then let it go for many hours - sometimes overnight. At the bottom of each track (column) of clips I set the follow action to go back to the top. Each column of clips has a different number of clips so that no two clips are ever playing simultaneously once the 'follow action cycling' begins. I also dedicate one track to midi control. I'll construct some random parameter automation clips which tweak the plug-in I'm testing which run along side the other audio clips - also utilizing follow actions. I get pretty wacky with the automation curves so to hopefully test as hard as possible. The ultimate idea is that these automations will process the audio clips in the other tracks in various ways. I load up as many instances of the plugin until I feel I've taxed the CPU to a reasonable point. Ideally all of this is in addition to already stress tested components of your existing setup. (I'm going to shoot for 3 instances in my stress test.) Now to further enhance this test, I also try to work the other components of my setup - playing loaded instruments, recording clips into empty slots - basically running all the other stuff which came before adding this new component.

After passing these tests, I start to use the plugin in question during rehearsals - but will still hold off using it Live until several rehearsals later where I'm confident it will be trustworthy.

[de la Mancha]

@ controlcentre - fanks

@ Exit Zero - that's a hell of a test! I understand from a live performance point of view, you want to make sure nothing fails in an embarassing way. If you do test truc, please let me know if it passes. (and I can make a 'STRESS TESTED' label for the website )

[core]

It seems the puck doesn't move when I close the plug-in window in FL Studio. It just stays at the value it is at when I close the window for me.

[Jazzyspoon]

ON Cubase sx3, Truc will not 'freeze' or render correctly. I go to freeze the track and the parameters stop at a certain value and the entire (drum) track is at the one parameter. The ever changing badassness of this plug is brought to one moment and thats the effect you get. This might be a known issue, but I love this thing and would really like it to be able to freeze correctly. I believe the same thing happens in the rendering of the entire track process. Used Truc as a major tweaker in this ugly beast of a remix.
You get my vote for sure.

[core]

That seems to be the same thing I'm experiencing, hopefully it can be fixed because this plug-in is very useful

[de la Mancha]

holy heck! I don't know how that one got past me, sorry guys.

I've just had a quick look at the SE source file and although I haven't had the time to test it out yet, I think I know what the bug is. I've used the GUI side of some modules (the puck animation positions) to modulate the mix levels, so I think that doesn't work if the plugin window is closed or on rendering to audio.

If that's what it is'll try and get a fix uploaded as soon as possible, hopefully this weekend

thanks for reporting the problem guys

[de la Mancha]

OK, so after spending the weekend rewriting all the GUI side processing into audio processing, my big fear has come true. such a version would eat your CPU, belch, fart and ask for more. Many hours and much marital strife later, I re-wrote the top xy pad, found 50-60% CPU usage and wept in my beer

So, I'm sorry but truc will need to stay as is it (as least for now). It's not all doom 'n' gloom though. You can still record the truc mixer channel audio in real-time in your host, or use a free recorder vst, like voxengo recorder for example: http://www.voxengo.com/product/recorder/

truc was originally conceived as a 'live performance' plugin, which was why I picked the GUI side for all the modulation in truc, it being much lighter in CPU. being a n00b at this plugin game (not even a year in) I didn't make the connection that the GUI side is not processed when rendering /window closed. It seems obvious now, but not at the time.

Once again, sorry if this causes extra hassle to record the audio realtime, but it's necessary to keep the CPU in check
If you have any questions about recording realtime in your host, we will try to help if we can. (we have FL Studio, Live, eXT2 and Reaper between us). If you have any tips on realtime audio recording in other hosts, they would be gratefully received too. I will update the manual and my website with some info on this subject in the next few days.

[core]

Thanks man. Too bad it can't be fixed within reasonable CPU usage, but using a vst recorder isn't so bad
Still one of my favorite plugs of the DC

[bobsled]

Still one of my favorite plugs of the DC

[Laguna Rising]

Still one of my favorite plugs of the DC

An excellent plug indeed, I'm using it more and more



Cheers