another bug? select group of tracks, attempt to change "Automation Read Enable"

Author
williamcopper
Max Output Level: -68 dBFS
  • Total Posts : 1120
  • Joined: 2014/11/03 09:22:03
  • Location: Virginia, USA
  • Status: offline
2015/10/22 13:35:09 (permalink)

another bug? select group of tracks, attempt to change "Automation Read Enable"

You can conveniently set solo, mute, archive for a group of tracks, all selected, by right clicking and choosing "MSR" (confusingly until you've learned it, "Archive" is under "MSR" ... but oh well).    HOWEVER, you can not set or unset "Automation Read Enable" the same way -- when you uncheck that option, only one of your selected tracks will change.  
 
Since I never use "automation read enable" I like to get it turned off so the highlight doesn't distract ... but it must be done, as far as I can tell, one by one by one by one by one by one. 
#1

14 Replies Related Threads

    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 14:33:20 (permalink)
    Please state exact version of Sonar. This looks like an important feature request to me rather than a bug unless I'm missing something.

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
    #2
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 14:38:31 (permalink)
    Ctrl-clicking (quick grouping) the Read-enable button will do the trick.

    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
    #3
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 14:51:16 (permalink)
    I just tested this. Select your tracks (or the folder containing them), hold Ctrl and click one of the track's Read buttons. All buttons respond. No bigs.
     
    You are using the Right Click "MSR" menu and yes that results in only one track's Read button being enabled/disabled at a time from a selection group but seriously... how big of a problem is this? Not much.
     
    Also your reasoning for not wanting read enabled in the first place is... uh... questionable. You don't like seeing the button lit up? Is that what you are saying? If so that is silly.
     
    Having Read enabled does absolutely NOTHING unless there are envelopes on the track. The only valid reason AFAICT to disable it is if you have an envelope on the track you want disabled. There is nothing visually distracting by having the button enabled but even if that IS a major concern you can just select the tracks, hold Ctrl and disable one of the Read buttons. You can also use the MixModule to disable all Read Enable buttons in a project at once IIRC.
     
    In fact that Right Click MSR "Read Enable" option is probably a throwback from when all envelopes appeared right over top of the clips (instead of in Take Lanes) so would just be a way to disable them all from the right click menu along with the other MSR stuff. I have not tested that though.
     
    This is most certainly not a "bug". It's just something that does not work the way you THINK it should and more likely simply an obsolete control that has been left for the convenience of long time users who have it in their workflow (or the Bakers just haven't gotten around to scrubbing out the code).
     
    Seems like dredging for "problems" to me... as usual.
    #4
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 16:29:06 (permalink)
    DELETE WRONG THREAD!!
    post edited by Doktor Avalanche - 2015/10/22 16:43:18

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
    #5
    williamcopper
    Max Output Level: -68 dBFS
    • Total Posts : 1120
    • Joined: 2014/11/03 09:22:03
    • Location: Virginia, USA
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 17:39:31 (permalink)
    Thanks for the work-around, and the explanations.   I'd still call it a bug, when one action is done one way and another which looks exactly the same is done a different way.   
     
    But I'll agree it's minor, and I'll use control-click in the future.   Having all my hands busy usually means I hate two handed actions, but ok an old dog can sometimes learn new tricks.
    #6
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 17:44:20 (permalink)
    williamcopper
    Thanks for the work-around, and the explanations.   I'd still call it a bug, when one action is done one way and another which looks exactly the same is done a different way.   
     
    But I'll agree it's minor, and I'll use control-click in the future.   Having all my hands busy usually means I hate two handed actions, but ok an old dog can sometimes learn new tricks.


    You cant argue it is a bug. IF it was a bug when you did the actions the result would be something undesirable, the wrong thing happens. Not in this case. It works.

    You can argue it is bad design if what you say is correct. Nevertheless it is the current design good or bad. In order to change this then you need an enhancement to fix it.
    post edited by Doktor Avalanche - 2015/10/22 17:55:12

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
    #7
    Adq
    Max Output Level: -82 dBFS
    • Total Posts : 426
    • Joined: 2015/01/21 20:05:25
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 23:03:26 (permalink)
    For me it is the bug. If you press Automation Write Enable, it works for all selected tracks, and Automation Read Enable only for one. Could anybody see any logic with that? User is supposed to remember what options in what sub-menu work for all selected tracks, and what for only one. It is unacceptable. All right-click options should work for all selected tracks (if it have sense), that is how it works by standard in software design. Current situation reduce usability significantly.
    post edited by Adq - 2015/10/22 23:13:31
    #8
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 23:10:31 (permalink)
    Adq
    For me it is the bug. If you press Automation Write Enable, it works for all selected tracks, and Automation Read Enable only for one. Could anybody see any logic with that? User is supposed to remember what options in what sub-menu work for all selected tracks, and what for only one. It is unacceptable. All right-click options should work for all selected tracks (if it have sense), that is how it works by standard in software design. Current situation reduce usability significantly.



    I see this as you requesting a design change or an enhancement.
    Sorry Poor design <> Bug.
    If it changed the track selection scope when you didn't ask it to that would be a different matter.

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
    #9
    Adq
    Max Output Level: -82 dBFS
    • Total Posts : 426
    • Joined: 2015/01/21 20:05:25
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 23:17:35 (permalink)
    Doktor Avalanche
    I see this as you requesting a design change or an enhancement.
    Sorry Poor design <> Bug.
    If it changed the track selection scope when you didn't ask it to that would be a different matter.

    Ok, it is your point of view, but I can't see any practical difference. For me both poor designs and bugs absolutely must be fixed. But if developers take your point of view it leads to situation when they think: "Oh, it is a bug, we need to fix it. Oh, but it is just poor design, let's leave it as is, it is normal".
    post edited by Adq - 2015/10/22 23:28:33
    #10
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 23:43:22 (permalink)
    Adq
    Ok, it is your point of view, but I can't see any practical difference. For me both poor designs and bugs absolutely must be fixed.


    Regardless It still isn't a bug it's poor design and requires an enhancement to fix it. I totally agree with your statement that poor designs and bugs must be fixed.

    Adq
    But if developers take your point of view it leads to situation when they think: "Oh, it is a bug, we need to fix it. Oh, but it is just poor design, let's leave it as is, it is normal".


    Typical software company example..

    All developers and QA categorise issues similar to this:
    New feature.
    Enhancement.
    Bug.

    Once that happens they then assign a priority to it. Eg showstopper, high, low.

    Some assign an impact attribute to it (eg the percentage of people they think would be effected).
    e.g. High risk, low risk.

    Some reports will get discarded as duplicate or cannot repro.

    How they process this information is another matter. Often they hold triage meeting and debate if the the info they've received is accurate. No idea how cakewalk operates here that's their business.. But maybe something similar to this...

    https://en.m.wikipedia.org/wiki/Agile_methodology

    Remember a software company could have thousands of issues logged in their database. When you are dealing in these numbers you are going to be very strict when it comes to priotising. They need to make best use of their time.

    Of course if an issue does not end up in the database it's in no mans land..

    Cheers.
    post edited by Doktor Avalanche - 2015/10/22 23:58:16

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
    #11
    Adq
    Max Output Level: -82 dBFS
    • Total Posts : 426
    • Joined: 2015/01/21 20:05:25
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/22 23:58:19 (permalink)
    Ok, but here as users we have only two options: feature request and problem report. And in such not critical case the only difference is that with problem report you will wait forever for it to be reviewed, and with feature request it will never happen at all.
    #12
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/23 00:09:08 (permalink)
    Well that's your perception. My perception is that there are loads of feature requests being piled in one after the other, whilst there are still a backlog of bugs needing to be fixed.

    I don't see any issue myself IF there is a very poor design issue logging it in problem reports form AND putting it in the feature requests forum.

    If it's a 'nice to have' it clearly belongs straight into the FR forums. If it's a bug should be logged problem report.
    post edited by Doktor Avalanche - 2015/10/23 00:19:23

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
    #13
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/23 00:11:55 (permalink)
    BTW I have loads of issues I have logged in problem reports that haven't been looked at or fixed yet. Not complaining though (well not today).
    post edited by Doktor Avalanche - 2015/10/23 00:21:55

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
    #14
    jatoth
    Max Output Level: -83 dBFS
    • Total Posts : 363
    • Joined: 2009/08/12 06:31:35
    • Status: offline
    Re: another bug? select group of tracks, attempt to change "Automation Read Enable" 2015/10/23 13:50:44 (permalink)
    Adq
     If you press Automation Write Enable, it works for all selected tracks, and Automation Read Enable only for one. 
     
    User is supposed to remember what options in what sub-menu work for all selected tracks, and what for only one. It is unacceptable. All right-click options should work for all selected tracks (if it have sense), that is how it works by standard in software design. Current situation reduce usability significantly.




    To me, it is an oversight. While not technically a "bug", I seriously do not think the bakers "intended" this behavior. Any GUI in any software should be consistent in it's behavior. If a right click on one button acts differently there should be a valid intuitive reason why. Otherwise it should be fixed.

    John
     
    X3e Producer, Sonar Platinum, Sweetwater CreationStation i5 3.1gHz, 12 GB RAM, 500GB SSD OS drive, 1TB SSD audio drive, 1TB archive/misc drive, dual 22" monitors, Windows 7x64, SaffirePro40 (firewire), MOTU MIDI Express XT, Behringer BCF2000, dbx 586, Samson Servo 120a, Yamaha HS80M, Auratone 5c Cubes, Sennheiser HD650, Sony MDR 7509HD, Sony MDR 7506, Kurzweil K2500XS, Roland XP-30, Proteus 2000.
    #15
    Jump to:
    © 2025 APG vNext Commercial Version 5.1