Can we fix the track colour bug introduced in Lexington please?

Author
Post
Essentials Only Full Version
Skyline_UK
Max Output Level: -54 dBFS
  • Total Posts : 2133
  • Joined: 2004/04/15 17:55:09
  • Location: Midlands, UK
  • Status: offline
2016/03/29 07:35:22 (permalink)

Can we fix the track colour bug introduced in Lexington please?

http://www.cakewalk.com/Support/Contact/Problem-Report-Status/43213
There were threads on this:
http://forum.cakewalk.com/Clip-colors-not-displaying-correctly-m3339860.aspx
http://forum.cakewalk.com/Track-colour-bug-introduced-with-Lexington-can-someone-check-m3340233.aspx
and I filed CWBRN 43213 on 26th December 2015.  Checking just now it's still classified as 'new'!!  I know it's not a major one but I think that a function that had worked perfectly for years but becomes broken by an update should be fixed asap.
 

My stuff
 
Intel Sandy Bridge i7 2600 @ 3.4GHz, 4 cores, 8 threads, 16GB RAM.
OS & Programs drive: 240GB SSD
Data drives: 1 x 1TB drive RAID mirrored, plus extra 1TB data drive 
Windows 10 Home 64 bit
Cakewalk by BandLab 64 bit, Studio One 3, Band In A Box 2016, Ozone 8
+ too many other plugins
BandLab page
#1

1 Reply Related Threads
    pwalpwal
    Max Output Level: -43 dBFS
    • Total Posts : 3249
    • Joined: 2015/01/17 03:52:50
    • Status: offline
    Re: Can we fix the track colour bug introduced in Lexington please? 2016/03/29 08:24:22 (permalink)
    Skyline_UKI filed CWBRN 43213 on 26th December 2015.  Checking just now it's still classified as 'new'!!

    you'd think it would have at least been reviewed by now! if it has, but it still shows as "new" then maybe a new status is required ("under review" or something) so users feel like it's worth reporting this stuff?
    but at least it hasn't got status "status changed"... ;-)

    just a sec

    #2
    Jump to:
    © 2025 APG vNext Commercial Version 5.1