Thank you jasensmith for your understandiong reaction. You are right there are of course a lot things one might do to research and try to solve a problem and if a software is just a few weeks on the market one would expect, that the research of problems reported by customers would be essential to make sure to clear all possible bugs or usage-problems. The more astonishing I found that nearly everyone here (expect the VSL-Guys themselfe) have already occupied himself more with this subject than the VSL-Support has until now.
To become concrete about your suggestions:
- Since there is no crash, I fear crashlogs would not be that informative if they nevertheless might be than I do not understand, why no one of the VSL-Siupport ever has asked for. ðŸ˜
- Remote acces? yes even if this might be a bit more complicate in a Host-Slave-Setup, however I would be ready for.... but the VSL-Support obviously not ðŸ˜
- Videos might be helpful very often, especially when it comes to understand exactly what the user expiriences. In this caser the matter is pretty simple the Synchron-Player resets every sertting immediatly when ever the playback stops.
This phenomen has in it self nothing dubious or misunderstandable, since it is usually the result of certain Cubase-Settings when either you have set the Programsettings to do so (which is here not the case - but the Support even never asked that pretty simple question😠) or when the Latch-mode option in the expressionmaps settings is unchecked, which is here also not the case (even if the Support also did not asked for that😠).
To pretend that this phenomen is something independent from the Synchronplayer (as the Support does without any attempt even to ask for all information to reproduce the problem😠) caused by the DAW and its settings would mean in consequenc, that it should occur likewise with every other connected VST working in the same context. (It even does not afford that much technical intelligence to simply ask for how other VST-behave in the same project. What the VSL-Support again did not in any moment.😠).
However the fact, that even the VI act in exactly the same project on the same slave without any playback-stop-reset (while the Synchron player up to now still resets with every playbackstop😠) proves imho that the problem is obviously limited on the new synchron player and in so far definitly a problem of nothing else than the VSL-Synchron-Player .
I would expect, that VSL should have an interest, that new 'Software which was just released a few weeks ago should run without problems and thus be interested to solve Problems that occur, but for me as pretty long and faithful VSL-User it is more than sad,m that they obviously simply refuses to do even the least kind of probnlem-research but prefer to insult those who report those well founded problems of their software and their Support as "bold". ðŸ˜