Hi,
 
I'm fed up with a X3 producer bug: while I play or record in a project, if I move with the mouse the beginning or the end of an audio clip, the sonar process gets blocked: it hangs, and I have to kill it, so the last modifications are lost.
This bug was not present in versions <X3 (I had X2, X1, 8.5)
I submitted the bug but cakewalk didn't look at it (the bug report status didn't change at all).
 
So I'm wondering if this bug was fixed in the Platinum version.
Any Platinum user could test it and tell me?
BTW, I couldn't find a list of fixed bugs in Platinum... before, cakewalk was providing such a list with all releases.

I can check it out a little later, but did you ever get this issue confirmed by others in X3? I tend not to do that kind of editing during playback, much less during recording (!), but i wouldn't expect it to be a big problem unless maybe the clip boundary moved across the current Now time. Even then, I would just expect a minor audio glitch not a hang.

Not a problem in either X3 or Platinum for me. Moving clip boundaries across now time during playback doesn't even really glitch unless there's a whole lot going on and the CPU is working hard. Moving clip boundaries during recording is not possible because the slip-edit cursor is not available; apparently that's just not supported. Must be more to the recipe, or it's project/environment-specific as these things often are.

ssebs
BTW, I couldn't find a list of fixed bugs in Platinum... before, cakewalk was providing such a list with all releases.

Here you are:
 
2015/Allston Update
http://blog.cakewalk.com/sonar-2015-under-the-hood-enhancements-and-fixes/
 
Braintree Update
http://static.cakewalk.com/cakewalk/products/sonar/release_notes/Welcome_to_the_SONAR_Braintree_Release.pdf?_bta_tid=3.TPY.CEfj_Q.CBY1.5z1K..AyVMZg.b..l.A_tC.a.VPENoA.VPEOyA.r1RPvg&_bta_c=kc84jtxhyo7pusnriyzbpcnuxk7n4
 
Cambridge Update
http://static.cakewalk.com/cakewalk/products/sonar/release_notes/Welcome_to_the_SONAR_Cambridge_Release.pdf?_bta_tid=3.TPY.CEfj_Q.CCCp.6C19..AyY_qw.b..l.A_tC.a.VRSP4g.VRSQMw.Kx5a9A&_bta_c=4c9ylnlowmzwilvz6kph34f2k8g3w
 

Hi, thanks for your help!
Regarding this bug, then I have to investigate in which case it happens, I guess that it's linked to a vst which causes the issue..
+ thanks for the fixed bugs lists