Helpful ReplyTrack colour bug introduced with Lexington, can someone check?

Author
Skyline_UK
Max Output Level: -54 dBFS
  • Total Posts : 2133
  • Joined: 2004/04/15 17:55:09
  • Location: Midlands, UK
  • Status: offline
2015/12/24 07:43:09 (permalink)

Track colour bug introduced with Lexington, can someone check?

Steps to reproduce:-
1. Click on a track to select it.
2. Press 'I' to open the Inspector.
3. Change the background colour.
What should happen: when you click on a colour in the pallet the background colour rectangle changes to that colour.
What now happens: it doesn't change, you have to click somewhere else in the Inspector to make it happen.
 
Odd that something like this that's worked since, well, forever, has been knocked out of kilter.
I'll report it if someone can confirm, thanks.

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
Anderton
Max Output Level: 0 dBFS
  • Total Posts : 14070
  • Joined: 2003/11/06 14:02:03
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 09:42:27 (permalink)
I just tried it, but when I click on the track bar to bring up the color palette and mouse over the different colors, the gray background in the ProChannel changes. If I click on a color in the palette, the color "sticks" for both the track and ProChannel.
 
I tried this on an older project, then thought maybe it only happened with a new project created under Lexington, but it worked there too. Not sure what would cause your issue.

The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
#2
Skyline_UK
Max Output Level: -54 dBFS
  • Total Posts : 2133
  • Joined: 2004/04/15 17:55:09
  • Location: Midlands, UK
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 10:26:38 (permalink)
I don't follow Craig, I'm in Clip View in the Inspector where you can't see Clip View and ProChannel view at the same time? I think we're in different places.
 
Other:
- I get this on a new project also.
- I was working on a project this morning where all was as it has been for years, I thought I'd quickly update to Lexington, closed Sonar, ran the updater, reloaded Sonar and the same project, and bingo, this is now happening!
post edited by Skyline_UK - 2015/12/24 10:41:40

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
#3
SquireBum
Max Output Level: -84 dBFS
  • Total Posts : 347
  • Joined: 2013/06/26 13:23:55
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 12:29:46 (permalink) ☄ Helpfulby Skyline_UK 2015/12/24 12:50:08
Skyline_UK
Steps to reproduce:-
1. Click on a track to select it.
2. Press 'I' to open the Inspector.
3. Change the background colour.
What should happen: when you click on a colour in the pallet the background colour rectangle changes to that colour.
What now happens: it doesn't change, you have to click somewhere else in the Inspector to make it happen.
 
Odd that something like this that's worked since, well, forever, has been knocked out of kilter.
I'll report it if someone can confirm, thanks.



Skyline,
 
I can reproduce this behavior in Lexington.  I did not rollback to a previous Platinum version, but verified that X3 did work as expected.
 
To clarify the steps, this behavior occurs when you are using the "Background" field of the Clip tab of the Inspector to change a clip color.  The "Background" field does not update the color patch until you click somewhere else in the application.
 
EDIT:  Just wanted to add that this affects the "Foreground" field also.
-- Ron
post edited by SquireBum - 2015/12/24 12:46:37

Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
Windows 10 x64
AMD Phenom II X4 955 3.20 GHz
8 GB Ram
Nvidia GeForce 9500 GT
Echo Gina 3G
#4
Skyline_UK
Max Output Level: -54 dBFS
  • Total Posts : 2133
  • Joined: 2004/04/15 17:55:09
  • Location: Midlands, UK
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 12:38:10 (permalink)
Thanks Ron, I'll report it.
John

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
#5
Anderton
Max Output Level: 0 dBFS
  • Total Posts : 14070
  • Joined: 2003/11/06 14:02:03
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 15:00:50 (permalink)
Skyline_UK
I don't follow Craig, I'm in Clip View in the Inspector where you can't see Clip View and ProChannel view at the same time? I think we're in different places.


Ah, okay. When you referenced "track" and "background color" I thought you meant the background for the track, i.e., the track color, and the rectangle was the gray rectangle in the ProChannel. After reading SquireBum's clarification, I was able to reproduce what you described.

The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
#6
Lynn
Max Output Level: -14 dBFS
  • Total Posts : 6117
  • Joined: 2003/11/12 18:36:16
  • Location: Kansas City, MO
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 15:07:35 (permalink)

All the best,
Lynn

my songs
www.soundclick.com/lynnwilson

www.youtube.com/lywilson
my videos

Cakewalk by Bandlab| Sonar Platinum @ 64bits| i7 860 | 8 gigs ram | W10 @ 64 bits | RME FF 400
#7
Vastman
Max Output Level: -50 dBFS
  • Total Posts : 2508
  • Joined: 2006/08/30 02:49:18
  • Location: Oakland, CA
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 15:10:38 (permalink)
I just tried this as requested and everything works fine... I can change colors in the track side bar and all is changed, including prochannel.  I can change colors in the "track" part of the inspector, under the Automation section... ie, the "colors" section and it works fine.
 
this is a new project I did late last night with Lexington.
 
what am I missing?

Dana
We make the future... Climate Change Music
VastMaschine:SP4L/W10/i74930K/32GB/RME/CAD E100s; The Orchestra! NOVO!/Inspire/BohemianViolin&Cello, ARK1&2,/MinimalCapriccioMaximoSoto/OE1&2, Action&Emotive/Omni2/Tril/RMX/All OrangeTree/Falcon/APE Jugs/Alpha&Bravo/BFD3 & SD3
Gravity/DM307/AEON/DM/Damage/Diva/HZebra/Hive/Diversion/VC4/Serum/Alchemy/blablabla
Spitfire/8DIO/SL/KH/EW/NI; Shred1&2/AGF,G,M&T Torch&Res&Ren/GD-6; Ibanez SR1200&SR505
NOVAX FanFret Tele&Strat 
#8
Vastman
Max Output Level: -50 dBFS
  • Total Posts : 2508
  • Joined: 2006/08/30 02:49:18
  • Location: Oakland, CA
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 15:24:29 (permalink)
ahhhhh... thanks Squire... I see... it's the clip coloring section... yep! funny, I consider this bug to be a little xmas present for me... I never changed the background clip colors before! just used the data colorations that come from the track colors...
 
 

Dana
We make the future... Climate Change Music
VastMaschine:SP4L/W10/i74930K/32GB/RME/CAD E100s; The Orchestra! NOVO!/Inspire/BohemianViolin&Cello, ARK1&2,/MinimalCapriccioMaximoSoto/OE1&2, Action&Emotive/Omni2/Tril/RMX/All OrangeTree/Falcon/APE Jugs/Alpha&Bravo/BFD3 & SD3
Gravity/DM307/AEON/DM/Damage/Diva/HZebra/Hive/Diversion/VC4/Serum/Alchemy/blablabla
Spitfire/8DIO/SL/KH/EW/NI; Shred1&2/AGF,G,M&T Torch&Res&Ren/GD-6; Ibanez SR1200&SR505
NOVAX FanFret Tele&Strat 
#9
Lynn
Max Output Level: -14 dBFS
  • Total Posts : 6117
  • Joined: 2003/11/12 18:36:16
  • Location: Kansas City, MO
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 15:29:03 (permalink)
My problem is changing color in the clips inspector.  It behaves as described above by SquireBum.
 
"To clarify the steps, this behavior occurs when you are using the "Background" field of the Clip tab of the Inspector to change a clip color.  The "Background" field does not update the color patch until you click somewhere else in the application."

All the best,
Lynn

my songs
www.soundclick.com/lynnwilson

www.youtube.com/lywilson
my videos

Cakewalk by Bandlab| Sonar Platinum @ 64bits| i7 860 | 8 gigs ram | W10 @ 64 bits | RME FF 400
#10
Skyline_UK
Max Output Level: -54 dBFS
  • Total Posts : 2133
  • Joined: 2004/04/15 17:55:09
  • Location: Midlands, UK
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 15:54:54 (permalink)
I change foreground and background colours on every project track's clip(s), so I hit this bug as soon as I'd updated to Lexington.
I always use standard colours in every project so I can instantly identify each track:
- Drums and percussion: red background, white foreground
- Bass: brown, yellow
- Keys: royal blue, white
- Strings: light green, purple
- more...

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
#11
Anderton
Max Output Level: 0 dBFS
  • Total Posts : 14070
  • Joined: 2003/11/06 14:02:03
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/24 19:37:12 (permalink)
Skyline_UK
I change foreground and background colours on every project track's clip(s), so I hit this bug as soon as I'd updated to Lexington.
I always use standard colours in every project so I can instantly identify each track:
- Drums and percussion: red background, white foreground
- Bass: brown, yellow
- Keys: royal blue, white
- Strings: light green, purple
- more...




Good tip. What's the "more"? 

The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
#12
Skyline_UK
Max Output Level: -54 dBFS
  • Total Posts : 2133
  • Joined: 2004/04/15 17:55:09
  • Location: Midlands, UK
  • Status: offline
Re: Track colour bug introduced with Lexington, can someone check? 2015/12/25 03:45:29 (permalink)
Thanks Craig, my other standard colours I always use:
- Synths: Purple background, yellow foreground
- Brass: yellow, dark blue 
- Guitars, rhythm: light pinks, dark purple
- Guitars, lead: bright pinks, dark purple
- Vocals: grey, purple
 
These are the colours that these instruments suggest to me!
 

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
#13
Jump to:
© 2025 APG vNext Commercial Version 5.1