Thanks for the info

Dilaco1
I downloaded all the latest Windows 7 updates for an unrelated issue about 3 weeks ago. So I think that means my drivers are up to date.

Nope it won't be, Windows update is notorious for distributing ancient drivers. You need to go to manufacturers website for this. May I ask what the make and model of your display adapter is under device manager?
 

Dilaco1
Why would a computer with graphics issues be fine again just because an icon has been loaded a second time?
 

 
It is not being cached into the display memory correctly.
 
Thanks...

Dilaco1
My Windows setting is set to best performance - with no “eye candy”.
 
Hope this helps.

Data is always helpful   Any chance you could turn all the eye candy on for a few hours and see if any corruption occurs during that time?
 
Alex is right about the drivers, Windows often says my drivers are up to date but if I go to a company's web site, I find something newer. Maybe not better...but at least newer.

I'd like to add my experience here too... I've been experiencing this since x1 and on different machines. I have tried turning best performance and full graphic features on/off and it still happens. I am running the most current drivers for my gfx card... It happens with almost any icon at different times, so I don't think it's the icons themselves...

I have not reported it as I always wrote it off as a minor item and I've had (and still do) bigger fish to fry with Sonar issues... It has always been simple enough to re-load the icon and it goes away...

Keni

Interesting topic. FINALLY, a graphic issue I've never seen before.
 
I repeat, I do NOT have this problem (yet) in X1 or X2!
 
If anyone is collecting data on this issue, and if it helps, my 2 systems are listed below:
 
Windows XP sp3 desktop
Intel Core2Duo 32bit processor
NVidia GeForce 8400SG graphics
 
Windows 7 sp1 laptop
Intel i7 64bit processor
AMD Radeon graphics
 
 

As mentioned, if you're have probs with this do the experiment in step #30 - if not it would be impossible to understand the issue at hand. This has been around since X1; however most of us just leave it as its not critical to the core programme of audio production.

in one of my projects, this is just part of the console view
 
 
by deleting the entire contents of the Cakewalk Icon folder and re-saving this project file, this is what is found inside the Icon folder
 

 
even when the entire entire contents of the icon folder is deleted, the icons still load up with the project - however, they will appear to be garbled.
 
Somehow, somewhere, the project is saving the "icon" information within itself. i have searched since X1 but with no luck isolating the issue. If the linkage of the icon folder (not just the contents) is deleted, Sonar defaults to save the icons to a new folder in Users/(name)/AppData/Roaming/Cakewalk - if i do remember that path correctly.

That makes me think the images are being saved within the project and somehow the project file is corrupting them. Or Sonar is corrupting them as it embeds them into the project.
 
I haven't read every single post, so forgive me if this is a stupid question, but...
 
What happens if you open an X series project and load icons from a previous Sonar Icon folder, like Sonar 7 or 8?

Dilaco1
My screen resolution on a 22" PC monitor is at maximum: 1680 X 1050.

Try changing it to a more standard resolution like 1600 x 900, 1280 x 720, or 800 x 600.

soens
 
What happens if you open an X series project and load icons from a previous Sonar Icon folder, like Sonar 7 or 8?

Hmmm.... good question... 

my guess... best as at it is... it doesnt matter if the icons are from different projects and or be they custom created. Because if the icons are not available in the linked Default Icons Folder, Sonar will create them there. However, the size and quality of the icons may, just may, be questionable. It seems that Sonar somehow or somewhere creates another "icon(s)" file within the Project itself but this "icon(s)" is / are not stored properly.
 
if not how will the icons come back when they have been physically deleted from the link folder??? 

I recall for older OS versions, that there was a registry parameter for giving Windows a 'size' for its iconcache database file, but I don't believe it works the same way in Windows 7 or 8.  Certainly the parameter name is changed, at the very least, as a search of the Windows 7 registry does not find it under the same name it used to be in  XP or other older versions..
 
I did find a page with a small number of DOS primpt commands to enter, that clear the icondcache and delete the existing iconcache.db file, followed by restarting Windows.  This will have Windows rebuild the iconcache on the restart automatically.
 
That link is: http://www.sevenforums.com/tutorials/49819-icon-cache-rebuild.html
 
The page above has 2 listed options, with the 1st being to download and run a batch file - I would skip that and do the manual options listed under the 2nd option, first closing any open programs and such, since Windows will be restarted when the last DOD command is entered.
 
The above does apply to Windows 7 - I don't know if it applies for Windows 8 or not without looking.
 
I also found a slightly different variation of steps and commands to accomplish the deletion/rebuild of the iconcache.db file:
 
1.  Kill Explorer.exe process. In Windows 7,  click Start button > Hold down Ctrl+Shift & Right Click on empty area in the Start Menu > Click “Exit Explorer”. In Windows 8, you may do so via the Task Manager.
 
2.  Open the command prompt window, type each of the following and after every command, hit the Enter button:

  cd /d %userprofile%\AppData\Local
  attrib –h IconCache.db
  del IconCache.db
  start explorer
 
3.  Your Windows Icon Cache will have been rebuilt.
 
Bob Bone
 

Hi Bob, i think the Icon Cache in Windows are different from that of what Sonar is using. The file extensions are different. 
 
in Sonar, they use .BMP as the image file to be used with tracks. Windows Explorer uses .ICO
 
i could be wrong however, i think what you are describing refers to users having issues with Windows Explorer not displaying the icons correctly; something to do with the "desktop.ini" hidden file. Yup, there were issues with XP and Vista Explorer getting corrupted after a while; especially when users change the default icons of their folders in Windows Explorer via the Advanced Shell Command.