However, as it seems to be affecting VePro, doesn't that also make it a VSL issue? Seems to me that it does.
:-)įrom Martin's comments above, re: that latency comp was somehow not fully working properly in PT10 (but was with another SDK which was used for PT11) seems to verify that there IS a latency issue that VSL is aware of. Very uncharacteristically for VSL, I have heard nothing back - must have gone down a rabbit hole. Support asked for a session, which I gave them and I also sent a crash report. then out - very maddening, and very hard to get work done. Tracks would be in sync, then not in sync. I contacted VSL support several (like 3+.) weeks ago as I was having crazy timing issues - I had recently purchased MirPro24 and was using it in PT10 as a plugin.
Mafiacondon: I saw above that you asked whether it was an Avid issue, a VSL issue, or both.
