Have you ever run Synplant in another host on your hardware? I have no clue at the moment, but I'll make some more efforts in reproducing this on Monday. I can't see how it can be related to CPU architecture either. Synplant does clear it's reverb the first time around, but these are short delay lines and I've measured the CPU impact to be totally negligible. They do not use mutexes, but lock-free synchronization techniques. They do not allocate any memory in real time. In all other aspects they work the same way. Synplant has 64 samples latency, as does Microtonic actually, but because we have had issues with the first transients when bouncing we report 60 to add a 0.1ms "headroom". Nearly a second of silence is of course not acceptable. Every issue that I hear about is noted down and I really do try to go through everything in due time. We are constantly working on improving our products in all hosts. We currently have four different channels for support (forum, support emails, facebook and twitter), and not being able to synchronize our support efforts over these systems is one of the problems we need to work on. It happens and it's not acceptable and we need to improve how we work with this forum. As I said I've finally been able to look up and fix a number of minor problems in Cubase for our upcoming updates, but I have not seen anything like you are describing.Īnd yes, I am sorry that Fredrik and I missed answering on this support thread directly. Some go away in minor upgrades while other ones appear. Many of these problems are random in nature and difficult to reproduce. It is the one DAW we have had most problems with over the years (even more than Logic). I have been quite frustrated by the situation with Steinberg and (lack of serious) developer program for a long time. You caught me in a bit of a bad mood to be honest. I'm sorry if my reply sounded like a poor excuse. Do you think it might be CPU related (AMD Phenom II X6 1055T)? No other troubles at all with other VSTis either. I'm not currently having any other issue with Sonic Charge synths, and this one isn't very annoying. These values don't change later, after resuming normal behavior. Devices > Plug-in informtation shows 64 as latency for Synplant and 60 for Microtonic.
It looks like some kind of an incomplete initialisation. (Same goes for any project containing an instance of Synplant.)
Then, all instances play normally until I open the project again. Synplant on the other hand takes almost a second before starting to play a sound, whichever instance I try first. In the same project with one instance of Microtonic and several instances of Synplant, just after opening the project, Microtonic plays immediately as soon as I play a note on my MIDI keyboard. Microtonic is definitively not behaving like Synplant regarding this problem. A 5 seconds response telling "We are waiting for this or that." would have been very welcome before a month went by. Sorry, but don't BS me, your excuse doesn't cut it.
0 kommentar(er)
