PRV Height Not Retained in Platinum

Author
Post
Essentials Only Full Version
benjaminfrog
Max Output Level: -81 dBFS
  • Total Posts : 477
  • Joined: 2006/11/05 12:26:57
  • Location: Minneapolis
  • Status: offline
2015/02/09 18:32:27 (permalink)

PRV Height Not Retained in Platinum

If I double-click on a midi clip to open the PRV, it opens in the bottom half of the screen. If I click Shift+D, it maximizes it. If I then hit D it minimizes it. Hitting D after this point toggles it back and forth between fully minimized and fully maximized. However, if, when minimized, I double-click on a different midi clip, it opens the PRV in the bottom half only again. This is not the way X3 functioned and I hope it's not the way Platinum is supposed to.
 
Does anyone know if this is intended behavior? If so, is there a setting that will allow me to configure it to behave like X3? If not, has anyone else reported this as a bug yet?

SONAR Platinum
Windows 10 Pro x64
ASRock Z97 Pro4
i7-4790K 4.0GHz
32GB RAM
Intel® HD Graphics 4600
RME Fireface UFX
http://www.sewardsound.com/
#1

1 Reply Related Threads
    zrapture
    Max Output Level: -90 dBFS
    • Total Posts : 23
    • Joined: 2015/01/14 23:44:47
    • Status: offline
    Re: PRV Height Not Retained in Platinum 2015/03/13 16:18:56 (permalink)
    Hi! I've got the same problem here, but only with certain pieces I'm working on. It's extremely irritating. I haven't reported it as a bug, nor do I know how to do so.
     
    I believe I read somewhere that it may have to do with an outdated template. If so, then I guess I'll have to do a full install of Sonar Platinum. That's a shame, because updating from X3 was so darn quick...
     
    Hmmm, I can't see how to add attachments to this forum BB. I HAVE found a template that works without the aggravating behavior, based on the normal template. I've saved it as NormalBehavior.cwt and loaded it here for public use --> [link taken down]
     
    Note that I did manage to revert to the bad behavior, even using this template, so be careful...
     
    The OP (benjaminfrog) has determined that files creating using Sonar X3 templates as a base do not exhibit this behavior. I'd say that this is partially resolved. If you are a new user for this release, then I'd say that Cakewalk still needs to investigate a resolution to the problem.
    post edited by zrapture - 2015/03/15 15:49:51
    #2
    Jump to:
    © 2025 APG vNext Commercial Version 5.1