• SONAR
  • Q for CW Support - Old bugs : re-report or what? (p.2)
2015/02/06 08:24:06
sxahern
WookieeBy customising plugin menu's what exactly do you mean?  
 
The order?
 
what appears in them?
 
could you please give us a clue.
 
I only ask as I have been running customised Plugin menu's for both FX and Instruments for a couple of years.




The problem Im experiencing is with custom plugin menus not displaying the customised list of plugins properly.  Specifically, in places where there are (mostly right-click based) plugin insertion menus where the custom plugin menus can be used, Sonar wont display submenus containing VST2 plugins, or VST2 plugins at all.  The only place this doesnt occur is the browser.  Im aware that its not a common issue, but it has been confirmed as replicable. 
This is somewhat disappointing to me because Ive been used to using customised menus since Sonar had VST support.
 
However, as I say, Im not posting about this bug.  What Im actually trying to find out is whether old reported bugs on need to be 'revived' or re-submitted for the new version of Sonar or not, as I can no longer add new information to that existing bug report. Im not even sure if that database is still active.
 
 
 
 
2015/02/06 08:39:31
Paul P
 
If a known bug has not been fixed in a new version, it couldn't hurt to resubmit a report.
 
2015/02/06 08:40:12
Bristol_Jonesey
sxahern
Bristol_Jonesey
This forum is peer to peer.

 
But frequented by CW support staff, as per Ryan's post.
 
 
 
Plus, posting here, there's the possibility that someone else already knows the answer to the question and can reply, peer to peer. 
 
If you want a direct answer, contact Customer Support.

 
Ah, so you're saying I need to contact Customer Support to enquire whether I should contact Customer Support.  That's useful, cheers. 
And implying that asking publically on the forums, in a thread like this, is a bad idea despite the fact that it would mean other people who might not know whether or not they also need to contact Customer Support to enquire whether they should contact Customer Support will know whether or not to contact Customer Support.   Hmmm.
 
 

In order to facilitate this, we need to know exactly what the problem is.
 
You seem reluctant to post details
2015/02/06 11:38:52
sxahern
Bristol_JoneseyIn order to facilitate this, we need to know exactly what the problem is.

 
No, you'd just need to know what the procedure is regarding reporting old bugs, which would be entirely independent of what those bugs are.
 
You seem reluctant to post details

 
That's an interesting viewpoint, because even though the details are actually pretty much irrelevant to my actual question, I have posted them, in my reply to Wookieee.  
 
 
 
 
2015/02/06 11:43:09
sxahern
Paul P
If a known bug has not been fixed in a new version, it couldn't hurt to resubmit a report.



Cheers, I guess I'll do that. 
2015/02/06 13:47:35
vintagevibe
sxahern
Bristol_JoneseyIn order to facilitate this, we need to know exactly what the problem is.

 
No, you'd just need to know what the procedure is regarding reporting old bugs, which would be entirely independent of what those bugs are.
 
You seem reluctant to post details

 
That's an interesting viewpoint, because even though the details are actually pretty much irrelevant to my actual question, I have posted them, in my reply to Wookieee.  
 
 
 
 


You get that a lot on this forum.
2015/02/06 13:50:28
Bristol_Jonesey
sxahern
Bristol_JoneseyIn order to facilitate this, we need to know exactly what the problem is.

 
No, you'd just need to know what the procedure is regarding reporting old bugs, which would be entirely independent of what those bugs are.
 
You seem reluctant to post details

 
That's an interesting viewpoint, because even though the details are actually pretty much irrelevant to my actual question, I have posted them, in my reply to Wookieee.  
 
 
 
 


Ah, I didn't see that when I posted.
2015/02/06 14:22:33
Wookiee
sxahern
WookieeBy customising plugin menu's what exactly do you mean?  
 
The order?
 
what appears in them?
 
could you please give us a clue.
 
I only ask as I have been running customised Plugin menu's for both FX and Instruments for a couple of years.




The problem Im experiencing is with custom plugin menus not displaying the customised list of plugins properly.  Specifically, in places where there are (mostly right-click based) plugin insertion menus where the custom plugin menus can be used, Sonar wont display submenus containing VST2 plugins, or VST2 plugins at all.  The only place this doesnt occur is the browser.  Im aware that its not a common issue, but it has been confirmed as replicable. 
This is somewhat disappointing to me because Ive been used to using customised menus since Sonar had VST support.
 
However, as I say, Im not posting about this bug.  What Im actually trying to find out is whether old reported bugs on need to be 'revived' or re-submitted for the new version of Sonar or not, as I can no longer add new information to that existing bug report. Im not even sure if that database is still active.
 

 
I think I can see what your talking about as I just tried a little test in X3, my Platinum machine if off at the mo,  If I open the FX bin in a clip it was not set to use the personalised menu but when I made that change it did persist when I closed X3 down and reopened it.  Perhaps there is the problem that particular flag does not get set when setting FX to use a customised menu in the browser or track FX Bin?
 
Regarding unfixed problems that have followed on from one version to the next I would say it can do no harm to report again.
 
Hope that helps.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account