CWBRN-25087 - Report Details

Name: Bentley Ousley
Product: SONAR Producer
Version: X3e
Status: Submitted To Development
Summary: Kush Pusher VST sizing issue
Description:
Since installing the X3e update (this issue was not present in X3d or prior), the Kush Pusher VST plugin becomes scaled in a way where the interface is not fully visible
This only appears present in the Kush Pusher plug- no other of their plug-ins exhibit this visual anomaly
Expected Results: The Kush Pusher to remain the same size and to have full access to the plug in's parameters.
Actual Results: The VST is now scaled larger and is not resizable. You can see a visual image of the issue here: http://forum.cakewalk.com...-m3013732.aspx#3014304 Cakewalk Product Support advised this to be logged through the system as a formal bug.
Provided Specs: SONAR and VSTs are installed in 32 bit
Audio 1: - - Integrated /On-board Audio - -
Audio 2:
Driver Mode: ASIO
Operating System: Windows 8 64-bit
Reproducibility: Reproducible

Thanks - sorry delays at my end, I will take a look when I get the time. I've taken note of your post. Others may chirp in .... in the meantime.... cheers.

Just tried on Rapture, Session Drummer, SI-String, Bass station, Kontakt, and Z3TA. I could not reproduce and my end.
 
I can't say whether this is an issue with X3E or the actual plugin, normally I would assume the plugin as other plugins are behaving. Over to Cakewalk for this one.

FWIW - I don't think this is the same as your issue, but it just goes to show how weird the software/hardware world can be. I updated to a version of Sonar a long time ago (maybe it was 7 to 8 or something) and M-Audio's Key Rig did exactly what you described. I went crazy trying to figure it out until I downloaded a new graphics card driver. Not only was the problem solved, but a Focusrite interface I had been testing and which gave all kinds of pops and crackles stopped popping and crackling. Go figure.
 
Last time I was in Boston, I was told the #1 source of issues that Sonar tech support has to deal with relates to 3rd plug-ins.

Hi Folks,
 
We've been in contact with Kush Audio regarding this issue. Essentially, the plugin is responding to system font size. If you have a system font size set to medium or large, the plugin does not draw correctly. The system font size setting is found by right clicking the desktop, choosing screen resolution, and "make text and other items larger or smaller." This would occur on X2, X3d and X3e and is not specific to our recent update. Typically, VST plugins set the font internally and should not respond to system font changes. 
 
For now adjusting the system font setting to 100% (default size) should fix the issue for this particular plugin. We've alerted Kush Audio regarding this issue as this may require a fix on their end. 

Nice to have feedback. Thanks Dan.

Yeah - cool beans on figuring it out.  I recall way back that if my Windows font size was too big that things in Sonar would not draw correctly, but I don't recall if that was in a plugin or in Sonar itself.
 
Bob Bone
 

Since the issue is actually caused by a REACTION from the plugin to the font size, it seems like the thread title could/should be adjusted to better reflect that it is that it is some plugins that react improperly to font size, and not Sonar 'causing' this to happen.
 
If I was sitting in a parked car, in the passenger seat - eating a cheeseburger, and some kid kept running his bicycle into the side of my car I don't think I should get the blame for it.  (although in this day and age I would likely get sued).
 
Just a thought on suggesting a thread title change - I would hate to see some potential Sonar buyer pass on Sonar by thinking it is causing problems like this in plugins.
 
Bob Bone
 

@Dan, that's QUITE the mug, by the way.  You look quite eh, 'focused', yeah, that's it  :)
 
Bob Bone
 
 

robert_e_bone
Since the issue is actually caused by a REACTION from the plugin to the font size, it seems like the thread title could/should be adjusted to better reflect that it is that it is some plugins that react improperly to font size, and not Sonar 'causing' this to happen.

I changed the title to mention the specific plug-in in case other Sonar users own the same plug-in and indicated it was solved. Hopefully the OP doesn't mind but I think the current title would be more helpful should people encounter this problem