Hi,
I'm currently playing around with the demo version of Audiomulch and enjoying it very much. However, I'm struggling to get the metasurface to work with Reaktor and Kontakt (I've not tried other NI instruments yet). Everything is fine until I create a couple of snapshots on the metasurface and start interpolating between them - at that point the audio cuts out and the plugin ceases to pass audio through it.
I realise that the automation parameter setup in some of the NI plugins is a mess for various reasons, but any advice would be great. Not being able to use the metasurface with Reaktor is a deal breaker for me I'm afraid.
All the best,
Everything is working for me over here with reaktor and the meta-surface. However, I'm using an alpha of AM. Maybe ross could chip in. What version of reaktor are you using? 5.6.2
Yup, Reaktor 5.6.2.
There have been some changes to metasurface<->vst plugin parameter syncing for version 2.2. I recommend you contact beta@audiomulch.com and get access to the latest beta version.
However, what you're describing sounds very strange. You could try disabling all but a few Reaktor parameters in the metasurface parameter tree and see if that helps.
But I really do recommend accessing version 2.2.. and if there is still a problem I will try to resolve it quickly. This is exactly the kind of issue I'm working to resolve at the moment for the 2.2 release.
Thanks.
Hi Ross,
Thanks for the help - beta request email duly sent.
I thought about unticking a bunch of the parameters but they are unnamed ID's, so I don't know which is which. Worse, there's something like a thousand of them and no ctrl/shift select (or 'ctrl - a') means I'd have to manually switch each and every one off. Unless I'm missing a 'deselect - all' button or something... might be something to add to the roadmap/backlog.
Would you rather I try the beta or dig-deeper into the current release version to try to get to the bottom of this? Either way, I'm not going to be able to play around with anything for another twenty hours or so.
Cheers,
Does the CPU meter hit the red or spike during Metasurface interpolation? Also, does this behaviour happen consistently in all Reaktor ensembles (or Kontakt sample sets) or just specific ones? The thing about Reaktor especially is that CPU demands can vary widely depending on what .ens is loaded...
> I thought about unticking a bunch of the parameters but they are unnamed ID's
That's fixed in the 2.2 beta
> Worse, there's something like a thousand of them and no ctrl/shift
> select (or 'ctrl - a') means I'd have to manually switch each and every one off
You can toggle them all by checking the checkbox for the contraption. There is also a right-click disable all option.
> Would you rather I try the beta or dig-deeper into the current release
With respect specifically to using Reaktor with the Metasurface, I think there has been enough change already that you will get more joy with the beta, even if it doesn't yet completely solve your issue (but it may)
It seems totally fixed in the beta. ID's appear properly and parameters interpolate nicely. I was getting a bit of glitching when I was running two instances of Reaktor and manipulating both with the metasurface. However, when I then reduced the number of parameters being controlled to just those being used by the Reaktor ensembles (as opposed to all the unnamed and reserved ones) it stopped, leading me to suspect that spitting out 2000 parameters with every mouse movement was causing my CPU to spike. Seems perfectly acceptable under normal use and it's a relatively laptop - I'll look out for it in future though.
I think it'd still be useful to be able to shift click parameters in the metasurface to turn them on and off. For example, when I sorted the Reaktor ensemble ID's so that those being used were displayed at the top I still had to enable each with a mouse click (roughly 25 parameters, 2 instances of Reaktor, loads of mouse clicks). Being able to shift click this bunch would allow users to get it done in a just a few clicks.
Thanks again for the help Ross. I'm really excited about seeing how far I can push this and I suspect that I'll be using heavily for a bunch of applications over the coming months.
> However, when I then reduced the number of parameters being controlled to just those being used
> by the Reaktor ensembles (as opposed to all the unnamed and reserved ones) it stopped
This is something I'm going to fix. At the moment the metasurface will interpolate every parameter, even if the values of all snapshots for that parameter are identical. Obviously there's a lot of overhead in doing this when you have something like Reaktor with 1000 dummy parameters.
> I think it'd still be useful to be able to shift click parameters
Yeah, it's a reasonable idea. I'll see what can be done.
+1 fthis idea
Great, thanks Ross :)