Writing automation in touch mode with JSFX GUIs doesn't work properly

[RobinGShore]

If I try to write automation from a JSFX GUI when a track is in touch mode, the parameters I'm writing to constantly fight back. It works fine if I use the generic JSFX sliders to write autoamation, but when I try to do it from a gui I end up with envelopes that look this:

I've tried this with several JSFX plugins that have GUIs and it happens with all of them. Is there some special sauce that plugin developers need to put in their code so this doesn't happen, or is this a bug with JSFX that needs to be fixed?

Take a look at the at this thread for a little more info/context:
https://forum.cockos.com/showthread.php?t=163614

[Justin]

JSFX needs to be extended to allow plug-ins to notify when the capture of a particular parameter ends, yeah.

[RobinGShore]

Thanks. If/when that happens, will old fx need to be updated to take advantage of the change, or will they work properly as is?

[X-Raym]

Arg, I coded all day a JSFX especially for writing envelope and I needed Touch mode to not overwrite the next part after play press... And then I discover this issue. 😥
Complete deal breaker for the workflow I wanted. I didnt find any workarround.



In latch mode, the value is written to envelope with slider_automate, but when press play it is still in latch mode so it erase next data.
I tried a script running in background to autoclear latch envelopes automatically, but this just don't let the JSFX to write value.



If touch support could be added to JSFX via slider_automate (called from GFX section), it will be very much appreciated.


Thx !

[X-Raym]

just made this script, which do allows to write automation from JSFX, as if touch mode (but using Latch mode)

function Main()
  time = reaper.time_precise()
  if time - last_time > 0.3 then
    reaper.Main_OnCommand( 42025, 0 ) -- auto clear latch envelope
    last_time = time
  end
  reaper.defer( Main )
end

last_time = reaper.time_precise()

Main()

Not ideal but working.

[Justin]

Originally Posted by RobinGShore

Thanks. If/when that happens, will old fx need to be updated to take advantage of the change, or will they work properly as is?

They will need to be updated. (This was added in 6.74), here's an example of how a JSFX can notify of touch automation recording:

mouse_cap ? (
  slider1 += (mouse_y - ly);
  slider_automate(slider1,0);
  lcap=1;
) : lcap ? (
  lcap=0;
  slider_automate(slider1,1);
);
ly = mouse_y;

[dromoer]

Originally Posted by RobinGShore

If I try to write automation from a JSFX GUI when a track is in touch mode, the parameters I'm writing to constantly fight back. It works fine if I use the generic JSFX sliders to write autoamation, but when I try to do it from a gui I end up with envelopes that look this:

I've tried this with several JSFX plugins that have GUIs and it happens with all of them. Is there some special sauce that plugin developers need to put in their code so this doesn't happen, or is this a bug with JSFX that needs to be fixed?
BSN writing services https://www.nursingpaper.com/bsn-writing-services/ can offer significant benefits to tech students, particularly those involved in interdisciplinary fields like health informatics or biomedical engineering. These services can help students understand complex nursing concepts, which can be crucial when developing technology solutions for healthcare. They provide a solid foundation in medical terminology and patient care procedures, ensuring tech students can communicate effectively with healthcare professionals and create more user-centered designs. Additionally, BSN writing services can assist in research and documentation, essential skills for any tech student aiming to innovate in the healthcare technology sector.

As a frequent user of JSFX GUIs for audio production, I've noticed that writing automation in touch mode can be frustratingly inconsistent. The controls often fail to respond to touch input as expected, leading to erratic parameter changes that ruin the precision needed for fine-tuning. It's disappointing, considering the potential of touch interfaces to streamline the workflow. I hope future updates will address these issues, as a reliable touch response is crucial for modern music production environments where speed and accuracy are paramount.