Persistence of Module parameters: TPC/IP Server / Tuning Command Syntax

Hi Rodrigo,

I can try to help you troubleshoot this. It will be useful for me to know a bit more about your setup.

Which version of Audio Weaver are you using? What is the target platform where your custom module lives? 

Can you please detail the sequence of steps you are taking to try to tune the module over TCP/IP? When you make the tuning change, does the module update correctly and the data processed by the module reflects the array update but then the change does not persist when stopping/restarting Audio Weaver, or does the change not take affect at all?

Thanks,

Michael

Hi Rodrigo,

Thanks for the additional information.

When you stop the server and start again, are you also stopping and restarting the processing design or does the processing design continue running in the background and the server reattaches to the target?

If the processing continues running in the background, then it's expected that the array changes would persist and we will need to dig deeper.

If the processing design is stopped, then when you restart it Audio Weaver will re-perform the dynamic instantiation of your processing design; that is, it will resend a series of binary commands describing how to assemble and configure the design based on the design file. If you are using Designer to run the design file, then the Server will translate the parameter settings from the design into binary commands and the array changes should persist. If you are instead loading a binary design file (.awb) outside of Designer, then the array changes would not be saved in that binary file unless you save and update the file with that tuning adjustment.

I hope this helps you resolve this issue. Please let me know if you are still having difficulty getting the array changes to persist.

Thanks,

Michael

Hi Michael,

I have a similar problem.  

When I set a value to  "gain" of  "Scaler" module from my program  via TCP/IP and stop AWE Designer  processing,  the value(gain) was SAVED.

However I set   "isMuted"  of "Mute Smoothed" module and stop processing, the value (isMuted) was NOT saved.

Also  an coefficient  array set to "BiquadCascede" module was NOT saved.

I did not restart the processing.

Is it possible to save any variables set via TCP/IP  before we stop processing? 

Is it possible to send a command to save coefficients of Biquads to file  such as "Save to file..." ? 

Best Regards,  

M.S

Hi M.S.,

It will be useful for me to know a bit more about your setup. What version of Audio Weaver are you using? What is your target platform? When you say a parameter is or is not saved, how are you determining this (you mentioned you are not restarting the processing - what happens if you do restart)? Is your processing dynamically instantiated from AWE Designer over the TCP/IP tuning interface, or is it loaded outside of AWE Designer?

Thanks,

Michael

Hi M.S.,

Thanks for sharing the screenshots and your sequence. Can you please share the AWD and the script you used? It will help us avoid any errors in trying to reproduce this behavior if we use the same files on our end.

Thanks,

Michael

Hi M.S.,

Thanks for sharing these. I see the same behavior on my end so I will have our Platform Development team look into this.

Thanks,

Michael