Virus TI Snow synth parameters to DAW

    Hi,


    I'm sorry if this issue has been discussed before, but it seems that when I change patches on my Virus TI Snow the active patch parameters aren't reflected to the DAW (in this case Logic). Issue is clear when using a hardware controller (eg. mackie, touchosc). This causes nasty parameter-jumps if one is not careful of the settings in Virus.


    Has any1 else been affected by this and/or found some fix?


    Cheers.

    I'm not sure if I understand the problem exactly. So you are using the VALUE buttons on your TI Snow to change the currently selected patch and the change is not reflected in the "Virus TI Snow Control" plugin? Is this what is happening in your case?


    Best wishes,
    Jörg Hüttner

    Virus Control & Virus hardware work just as expected. The issue is with the DAW (Logic) "seeing" the same parameter values.


    Workflow:
    * Start Logic
    * Load Virus Control into a software instrument track (Part 1 will be "-Init-")
    * Hit "A" on keyboard (open automation mode)
    * Select automation "Virus Ti Sn" -> "Part 1" -> "[1] AmpEnv Attack". This should be value 0. Automation line should be of color black as we haven't made any changes (shows the value it's getting from the synth)
    * Hit "A" on keyboard again (close automation mode)
    * In Virus Control or Actual synth change patch to "Veldisa BC" or any other that's supposed to have AmpEnv Attack different than 0.
    * Hit "A" on keyboard again (open automation mode)
    * "[1] AmpEnv Attack" is still showing value 0, but should show value from the currently selected patch (for "Veldisa BC" it's 13).


    Of course this isn't a major issue, but a small nuisance in an otherwise amazing synth! Cheers :)

    i know that phenomena. it happens especially when parameters change slowly over a long duration of time. it happens with every plug-in in logic. one possible way around it is to use a controller to automate the parameter in question instead of an automation lane. if you e.g. assign the mod wheel to open up the filter instead of drawing the filter frequency into automation. technically, it is not the same and when you automate a lot, it will not add overview ;) but it works and sometimes that's all i need.
    best, marc

    I'm not at my main studio right now, but off the top of my head I'm going to suggest adding a node a bit further along the automation line, that should give the playhead something to register.