• SONAR
  • 06 Update Track View Unusable (Solved..(fingers, toes, legs and eyes crossed) (p.3)
2017/07/01 13:02:44
LunaTech
Unfortunately, because I looked forward to the new features of these releases.... I agree......
2017/07/01 14:12:11
Keith Albright [Cakewalk]
That's really bizarre.  Do you use any track sorting?  Mind sending me the cwp of what resulted in the crazy display?  
 
As far as image sharing I use postimg.io  Usually direct link from that will paste an image into the image link in this forum. Then, you get an inline image.
 
As far as cursors/hit testing, we are working to improve the experience with different displays, dpi.  There's a lot of combos there.   
You can try dpi.lv to show the dpi of your display.  
 

 
However, the resolution used by programs will differ based on the scaling value in display settings.  
 
For example, while it shows 3840 x 2160 for this laptop with a 13.3" diagonal screen, I'm running with a scaling of 250% (Recommended).  
 

 
That yields a 1536 x 824 resolution when we output to the screen.  100% would be way too small to use but would be the full 3840 x 2160 resolution. To calculate the resolution used when drawing to the screen you just take the percentage, divide that by 100 and then divide the resolution numbers by that.  So for 250%, I just divide by 2.5.  If your scaling was 400%, it would be divided by 4, etc.
 
So to help troubleshoot the cursor issues, we'd like to know the reported dpi and diagonal as well as the current scaling you are running.  
 
Thanks.
 
Keith
2017/07/01 16:13:55
LunaTech
Hello Keith,
 
Sent a PM... Could not attach .cwt file. But this happens even in a new project. Here are the pics: The last is a new project
.
 

 

 

 
 
2017/07/01 17:06:02
scook
Try creating a problem report
Reference this thread and attach the cwt file to the report
PM the report number to Keith.
2017/07/01 17:33:20
Keith Albright [Cakewalk]
What build # that has the issue?
Does this start as soon as you open SONAR and then a new project or does it happen after closing/reopening projects.
I ask because we had an issue like that before we went to EA but it was fixed for the final version.
The splitter bars look way way way too big.  
 
2017/07/01 18:16:18
Keith Albright [Cakewalk]
Another thought, can you open the piano keyboard (alt + shift + 0) and see if that looks too large?
If you don't have a touch monitor it should be about 2 inches per octave.
I'm thinking the data the monitor driver is returning as far as physical size might be unusual.
 
2017/07/01 19:38:02
LunaTech
Hello Keith,
 
This starts with every project no matter what. Also the keyboard is HUGE!! spans across both monitors and then some.. WOW.... One key is like 3 - 4 inches wide. My question is.. Is not the video card reporting the same thing in May 2017? What's different?
2017/07/01 19:38:35
LunaTech
Hello Scook,
 
Thanks for the suggestion....
2017/07/01 19:43:33
LunaTech
Hello at Keith,
 
More fun ... closed Platinum, opened again.. Loaded cwt.... Hit alt/shift/0 and now the piano keyboard looks fine.. 
2017/07/02 02:51:01
Anderton
LunaTech
More fun ... closed Platinum, opened again.. Loaded cwt.... Hit alt/shift/0 and now the piano keyboard looks fine.. 



I guess you need to let the tubes warm up 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account