[CWBRN-33240] - Crash when opening Pro Channel through ACT

Author
Post
Essentials Only Full Version
mesayre
Max Output Level: -87 dBFS
  • Total Posts : 195
  • Joined: 2012/07/07 09:29:57
  • Location: New York, NY
  • Status: offline
2015/05/17 13:42:07 (permalink)
0

[CWBRN-33240] - Crash when opening Pro Channel through ACT

Hey all,
   Been getting this one pretty reliably - can anyone confirm?
 
If I attempt to use ACT to step through the FX plugins on a given track, Sonar will crash when I get to a Pro Channel plug. To reproduce, try the following:
 
  1. Create a new project
  2. Create one new audio track
  3. Enable at least one Pro Channel module on that track
  4. Use a button on your ACT surface that is programmed to "Open Next Plugin". You will likely get an error message saying that there is no plugin stand-in (which makes sense, as there probably isn't one) or a really visually-funky plugin window. Hit it again and Sonar crashes. 
Workarounds:
  1. Select plugins with the mouse, which works as it should, but is a workflow drag.
  2. Re-program your ACT surface to instead "Focus next plugin". This works fine for ProChannel, but doesn't automatically open up the plugin windows of 3rd-party plugs, so you can't see what you're tweaking unless you program another button to open that window.
Either of these can work, but thought I should report this anyway because the "Open Next Plugin" is the default mapping for the Sonar ACT template on the Roland A-800Pro (and possibly other surfaces), so other users may experience this crash.
 
Sonar Platinum Dorchester, Win 7x64, Roland A-800Pro
 
Mike
post edited by mesayre - 2015/05/26 14:03:38
#1

2 Replies Related Threads
    azslow3
    Max Output Level: -42.5 dBFS
    • Total Posts : 3297
    • Joined: 2012/06/22 19:27:51
    • Location: Germany
    • Status: offline
    Re: Possible bug: Crash when opening Pro Channel through ACT 2015/05/17 15:30:11 (permalink)
    0
    Stable reproducible with "ACT MIDI" or any other plug-in, Sonar Crash in the second SetNextUIContext(ctx,dwId,UIA_OPEN) call (that info is for developers). Note that procedure should be performed exactly to reproduce.
     
    But with some FX inserted and focused, Sonar never switch to ProChannel by that command, it switch between FX windows only till some ProChannel module is in focus. In the last case, it show parameter window/error window and than continue with FX. "Focus" command works within ProChannel modules on one strip, when one was originally selected.
     
    So, since neither "Open" nor "Focus" commands  switching from FX to ProChannel, I do not see a big problem there for general device.
    Does on A-800Pro these commands move focus from FX to ProChannel modules? Are they also able to open ProChannel view in case it is not there?

    Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
    GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
    RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
    www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
    #2
    mesayre
    Max Output Level: -87 dBFS
    • Total Posts : 195
    • Joined: 2012/07/07 09:29:57
    • Location: New York, NY
    • Status: offline
    Re: Possible bug: Crash when opening Pro Channel through ACT 2015/05/26 13:50:34 (permalink)
    0
    Thanks for the response. 
     
    Yes, as you note, it's not currently possible to use the ACT command to go from an FX window to a ProChannel plugin. I would argue that it probably should be so that mousing isn't required, but that's another debate, I suppose.
     
    But as it stands now, even if I set up my control surface to use two sets of buttons (one for PC using "Focus Next/Prev" and one for FX using "Open Next/Prev"), I can still crash the whole program by accidentally hitting the wrong one. Even if no enhancements are made to the existing functionality, there should be a more graceful way of handling the exception (even if that means that using "Open Next" on a PC plugin does nothing).
     
    I'll submit this to the Problem Reporter and update with the ticket number.
    #3
    Jump to:
    © 2025 APG vNext Commercial Version 5.1