Author Topic: increasing number of ACT parameters  (Read 2288 times)

Offline kvalca

  • Newbie
  • *
  • Posts: 2
increasing number of ACT parameters
« on: June 22, 2016, 05:21:12 PM »
Hi AzSlow3,

First, it is my congratulations for this wonderful controller. The new version of Az Controller with OSC is terrific.

My Rapture Pro template (Lemur in iPad) with 300 ACT parameters works perfectly for OSC.

I set the Az Controller for OSC connection and both the input response (Lemur iPad) as the output from the plugin are very fast.  The latest versions of Az Controller (0.5r0b314 and 0.5r0b316) work correctly.

The Rapture has 1483 Pro plugin parameters, Z3TA 2: about 500 parameters. Now we have to be modifying the configuration file: genericpluginparams.xml. On the other hand, there are many parameters that can not reach set by limiting the maximum number.

Would it be possible to create a version of the driver with a higher number of ACT parameters (currently 300)?

Other question: Lemur (Midi and OSC Controller) allows nested containers or windows causing the OSC names are very long and do not enter the box "OSC address" (Hardware tab). In this cases, the hardware assignments are difficult to modify or revise.

Anyway, thank you very much for your AZ Controller.

Regards, Kvalca

Offline azslow3

  • Administrator
  • Hero Member
  • *****
  • Posts: 1144
Re: increasing number of ACT parameters
« Reply #1 on: June 22, 2016, 06:26:47 PM »
Hi Kvalca,

Thank you for nice words. Also thank you for confirmation that AZCtrl works with Lemur. Since I have developed and tested OSC part with TouchOSC on Android only, I had worries the result can be incompatible with other programs.

I have realigned the Hardware tab and increased ACT parameter number per type from 100 to 499. By stupidity I have used "ACT 500" as "Invalidate parameter" in many presets (instead of defining such Function directly), so increasing the number over 499 is more complicated (but possible if required).

But there can be problems with that number. That is rather "heavy" parameter, it can produce up to N*3*13 calls AZCtrl->Sonar->VST per second in case the GUI is open or "ACT Scan" is specified in preset. So effectively we have increased the pressure on the system from 4000 to 20000 per second. I can not predict either that can influence Sonar/Performance/Audio glitches/something else.

So please downloaded the test version with that change (v0.5r0b318 in the Download area) and with GUI open check you have no glitches with Rapture (or other VST with many parameters).

Offline kvalca

  • Newbie
  • *
  • Posts: 2
Re: increasing number of ACT parameters
« Reply #2 on: June 26, 2016, 09:56:24 PM »
Hello Azslow3,

Thank you very much for the new version of the driver.

I modified the layout for 500 parameters. I tried the new driver with various connections:
i) iconnectmidi4 with very low latency.
ii) USB Thetering with slightly higher latency
iii) Wifi more latency

I do not detect alterations due to the new controller (1500 parameters) in Rapture Pro, Z3TA + 2, Addictive Drums 2, Addictive Keys. The problem is that Rapture Pro already has many glitches without Sonar (microhost).

I detect a slight delay in the feedback (Layout with 500 parameters) when switching sound or program in Rapture Pro (in my opinion, perfectly acceptable). All feedbacks are direct (unchanged) to each logical control.

The main problem is corruption of the parameter file: genericpluginparams.xml, but I think it is like the driver version with 300 parameters.

If someone wants to test the layout to send me a PM.

Regards, Kvalca

Offline azslow3

  • Administrator
  • Hero Member
  • *****
  • Posts: 1144
Re: increasing number of ACT parameters
« Reply #3 on: June 26, 2016, 11:10:41 PM »
I do not detect alterations due to the new controller (1500 parameters) in Rapture Pro, Z3TA + 2, Addictive Drums 2, Addictive Keys. The problem is that Rapture Pro already has many glitches without Sonar (microhost).
Thank you for testing.
If you have not submitted RP glitches you observe to CW, please do so. Even in case you do not get any direct feedback from them, they pay attention to user reports.

Quote
I detect a slight delay in the feedback (Layout with 500 parameters) when switching sound or program in Rapture Pro (in my opinion, perfectly acceptable). All feedbacks are direct (unchanged) to each logical control.
500 parameters is quite some processing on all sides (Sonar -> AZCtrl -> Wifi -> iPad -> graphics) summed with the "standard" update delay (75ms). So I think it is normal you can notice it.
But check that all monitors in AZCtrl are "Ultra", I periodically forget myself (the default "Normal" is very slow...).

Quote
The main problem is corruption of the parameter file: genericpluginparams.xml, but I think it is like the driver version with 300 parameters.
In that part please describe the observation as detailed as possible, here or in PM (to me).
But first of all, are you using AZ ACT Fix?