Please, have these bugs been fixed in X2?

Hi there,

I am still on the fence about upgrading to X2. It is about money, because I am still missing some decent limiter and thinking of buying Voxengo Elephant right now. And then X2 upgrade would be postponed at least a month.

But the other thing is, I want to get bug fixes with X2 as well. Mainly fixes of bugs I have been experiencing and fighting again for months while using X1 Expanded, version D.

I have reported all of them to CW, I discussed some with the support but generally I have not received any final resolution from CW, whether this or that bug will be fixed or not. Except for one bug.

Could you please try the following steps in order to reproduce the buggy behavior from X1,  in X2?

  Bug 1:  a few days ago I received an email from CW saying this was Fixed. But also reflected in X2? CWBRN-3584
  Lasso selecting nodes in Lanes (envelopes) with Aim assist beyond current view causes graphical mess. 

  - Steps: go to Lanes, have Aim assist on, zoom in so you do not see all nodes in the track, lasso select all modes you see, hold the right-click while selecting and scroll the view so you scroll the remaining nodes - make the view moving horizontally.  
  - Result in X1: the Aim assist line interfere with the lasso rectangle view and create weird graphical mess while moving horizontally. 
- Result in X2: ?????

Bug 2:
  VSTi does not produce sound when the Now time was repositioned forward while the playback was running.  Case 11493

- Steps: use for example Superior Drummer, record a MIDI clip, 6-8 measures, now disarm record, start the playback - you hear your recorded drums, now move the Now time forward a little, hit any key on your MIDI keyboard
- Result in X1: after moving the Now time forward during playback, hitting MIDI keys does not produce sound from VSTi, although the audio meters are moving and the pre-recorded MIDI is triggering sound from the VSTi. One has to stop and restart the playback to hear the sound again.
- Result in X2: ???????
(btw this is very annoying bug when I am improvising and need to move to different parts of the project...)

  Bug/or not bug, but still 3:  CWBRN-3692
E.g. Kontakt 5, Alicia Keys or Scarbee Vintage keys, having "Zero controllers on stop" checked in the MIDI settings, stopping playback after the Pedal Down event, the sustained sound continues to sound. One has to start and stop the playback in order to make it quiet.  
Happens with GPO4 as well, Truepianos as well... seems to be related to VSTi, not DXi synths.

Please, could you try this for me in X2 and let me know if you can reproduce it?

Thank you in advance.

Marek

Check, Check and check :) All three issues have been resolved in X2. 

1. Lasso selection is completely reworked and is not susceptible to redraw problems.
2. Many inaccuracies with realtime MIDI triggering were resolved including this one. The timing of realtime triggered MIDI playback is also greatly improved in X2.
3. This is also fixed - we now send explicit velocity zero note offs to synths on stopping playback in addition to an all notes off message that several synths didn't respond to.

rainmaker1011


One more: CWBRN-9346

Summary: Moving a group of midi events in PRV cause Sonar to freeze and lag
Description: create a MIDI clip linked to VTSi, quite a long
go to PRV and select bunch of events
move the selected group to another measure
Expected Results: midi events should be moved to desired position fast and smoothly, without making Sonar to freeze and lag
Actual Results: if there are more MIDI events in the group (lasso selection), sonar lags and freezes before the group get moved to the desired position.

I've never had SOANR freeze (as in must kill) but lag? Yes, if there excessive events selected (i.e. < 100 seems immediate, thousands seem to lag... never tried to find the "line in the sand" though)

This is what I needed to know :)

Thanks for the fast reply - great news. Soon I will become next proud owner of X2. :)