Helpful ReplyMore on the buggy controller pane in PRV

Author
Post
Essentials Only Full Version
williamcopper
Max Output Level: -68 dBFS
  • Total Posts : 1120
  • Joined: 2014/11/03 09:22:03
  • Location: Virginia, USA
  • Status: offline
2015/03/23 21:33:24 (permalink)

More on the buggy controller pane in PRV

Not only is the controller pane a complete pain, it gets out of sync.   See attached image, one track, one controller on one channel, but the controller pane is still trying to assure me that there are 10 controllers in this one track.    Happens way too often, so one never knows whether one is deleting a controller in use or not in use.
 
(Aside, and I've said it before: the whole notion of having to delete controllers from the view over and over and over and over is just ridiculous.)   If you work with midi, you NEED to see certain controllers, but you NEED NOT see and don't want to see, others.  
edit image deleted
 
 
post edited by williamcopper - 2018/11/04 11:48:54
#1
List Solutions Only

11 Replies Related Threads
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/03/23 21:52:05 (permalink)
    Having ten lanes open in the PRV is no "assurance" that corresponding controllers actually exist in the track; it depends how you got there. Steps, man; we need steps! 

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #2
    Wookiee
    Rrrrugh arah-ah-woof?
    • Total Posts : 13306
    • Joined: 2007/01/16 06:19:43
    • Location: Akahaocwora - Village Yoh Kay
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/03/24 09:42:06 (permalink)
    Also as I read the screen it is telling me what controllers are active for different channels.  As the PRV is capable of showing multiple tracks that is what I would expect to see.
     
    You know the drill William if you consider it a bug then use the Problem Reporter form to correctly report your "Bug" then the Cakewalk support staff will do their job and investigate.
     
    This after all a peer to peer forum the purpose of which is to allow others to verify any potential "Bug" prior to it being reported in the required manor.   This is not where Cakewalk look for reported "Bugs" and potential problems.  
     
    If you do not report your bug to Cakewalk by the proper channels then Cakewalk will never be aware of it.

    Life is not about waiting for the storm to pass, it's about learning to dance in the rain.
    Karma has a way of finding its own way home.
    Primary, i7 8700K 16Gigs Ram, 3x500gb SSD's 2TB Backup HHD Saffire Pro 40. Win 10 64Bit
    Secondary  i7 4790K, 32GB Ram, 500Gb SSD OS/Prog's, 1TB Audio, 1TB Samples HHD AudioBox USB, Win 10 64Bit
    CbB, Adam's A7x's - Event 20/20's, Arturia V6, Korg Digital Legacy, Softube Modular, Arturia Keylab-88, USB-MidiSport 8x8 
    #3
    Splat
    Max Output Level: 0 dBFS
    • Total Posts : 8672
    • Joined: 2010/12/29 15:28:29
    • Location: Mars.
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/03/24 11:01:31 (permalink)
    It's not telling anything to developers we need steps to reproduce. If the author has no intention to ultimately use the cakewalk problem reporter he should stop posting in these forums period and just use the problem reporter.

    Here we validate first and then report it with problem reporter. This is peer review. Bugs without CWBRN numbers will be moved out of this forum or locked eventually as we can't do anything with them.
    post edited by Splat - 2015/03/24 11:08:33

    Sell by date at 9000 posts. Do not feed.
    @48/24 & 128 buffers latency is 367 with offset of 38.

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.
    #4
    williamcopper
    Max Output Level: -68 dBFS
    • Total Posts : 1120
    • Joined: 2014/11/03 09:22:03
    • Location: Virginia, USA
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/03/31 23:10:31 (permalink)
    I'm seeing this constantly, so anyone who uses PRV and the controller pane should be able to duplicate it.   You go to a new track, and controller lanes from the old track show up in the controller pane.   See other post about "channel" proliferation, making a bad thing worse. 
     
    heres a CWBRN-32278
    post edited by williamcopper - 2015/03/31 23:19:15
    #5
    robert_e_bone
    Moderator
    • Total Posts : 8968
    • Joined: 2007/12/26 22:09:28
    • Location: Palatine, IL
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/04/01 01:01:24 (permalink)
    If you want the Cakewalk folks to see that this was filed, and for them to see that sooner rather than later - I would suggest that you edit this thread's subject line to add the CWBRN number to the beginning of the subject text.
     
    Bob Bone
     

    Wisdom is a giant accumulation of "DOH!"
     
    Sonar: Platinum (x64), X3 (x64) 
    Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
    Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
    Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
    MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
    Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
    #6
    williamcopper
    Max Output Level: -68 dBFS
    • Total Posts : 1120
    • Joined: 2014/11/03 09:22:03
    • Location: Virginia, USA
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/04/01 11:46:50 (permalink)
    One of the earlier comments said "it might be multiple tracks", but if you look at the PRV title in the screen shot, it is ONLY ONE TRACK, while the controller pane is showing controllers that DO NOT EXIST in the track.    Again, I see this very frequently, but it requires a longish work session and is not something that I've been able to induce in a simple procedural way with a new project.  
    #7
    stickman393
    Max Output Level: -60 dBFS
    • Total Posts : 1528
    • Joined: 2003/11/07 18:35:26
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/04/01 12:47:47 (permalink)
    williamcopper
    it is ONLY ONE TRACK, while the controller pane is showing controllers that DO NOT EXIST in the track.   



    I've experienced this too, for what it's worth, although not the severity you're seeing.
     
    williamcopper
    I see this very frequently, but it requires a longish work session and is not something that I've been able to induce in a simple procedural way with a new project. 

     
    Yeah, well, how are the developers going to reproduce, debug, fix, and test their work, then? :-)
     
    Here's an alternative plan: Can you save your project as another name, containing the minimum number of tracks required to show the problem? Then verify you see the problem when you open the project from a clean new SONAR session...
     
    At that point, you should be able to submit a problem report and attach the simple project. This should reduce the number of steps required for the dev to follow in order to see the problem.
     
     
     
    #8
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/04/01 16:01:49 (permalink)
    I'll show you my steps if you show me yours:
     


    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #9
    williamcopper
    Max Output Level: -68 dBFS
    • Total Posts : 1120
    • Joined: 2014/11/03 09:22:03
    • Location: Virginia, USA
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/04/01 17:44:31 (permalink)
    Well, good, Brundlefly, your image shows some of the problems:   mod wheel on several different channels for one track, while the event list (what is shown) has only one channel.    And a mis-match of time: EL at one place, PRV at another.  
    #10
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/04/01 18:01:52 (permalink)
    Good catch on the times, but they're only out of sync temporarily because I scrolled the view in the PRV later. And the seemingly incorrect controller view was created by deliberate manipulation; there's nothing buggy about how it got to look that way. I just wanted to demonstrate that GUI snapshots are meaningless without knowing the steps that get you there.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #11
    SquireBum
    Max Output Level: -84 dBFS
    • Total Posts : 347
    • Joined: 2013/06/26 13:23:55
    • Status: offline
    Re: More on the buggy controller pane in PRV 2015/04/01 18:51:34 (permalink) ☄ Helpfulby stickman393 2015/04/01 19:08:56
    The only steps I have found that can reproduce the OP's problem involve using Bounce to Clip with a MIDI Track channel that doesn't match the channel in the clip, which forces a channel change on the MIDI data in the clip(s).
     
    I believe the forced channel change is working as designed and gives the expected results, since it has existed since at least Sonar 8.5 (earliest version I could confirm on my system).
     
    I agree that the MIDI data lane behavior could be improved to not persist the previous channel's lanes, but until someone logs a problem report the OP's problem could be avoided with some basic housekeeping and workflow modifications:
     
    1.  Set MIDI track channel to match the channel of the track's clip data before editing

    Doing this will prevent the "surprise" channel change that occurs with a channel mis-match when using Bounce to Clip.
     
    2. When intentionally forcing a channel change on a track using Bounce to Clip, close and re-open any open PRV window that is associated with the track.
    The MIDI data lanes automatically refresh when the PRV window re-opens and displays only the CC's from the current channel.
     
    EDIT: 
    3.  Set MIDI track channel to "None" before editing  (credit to bvideo in http://forum.cakewalk.com/FindPost/3200873)
    This will prevent the MIDI channel from being modified on the existing Notes and CC's when using Bounce to Clip.
     
    Ron
    post edited by SquireBum - 2015/04/02 02:59:36

    Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
    Windows 10 x64
    AMD Phenom II X4 955 3.20 GHz
    8 GB Ram
    Nvidia GeForce 9500 GT
    Echo Gina 3G
    #12
    Jump to:
    © 2025 APG vNext Commercial Version 5.1