Ranked Staff View fix request list

Author
BobF
Max Output Level: 0 dBFS
  • Total Posts : 8124
  • Joined: 2003/11/05 18:43:11
  • Location: Missouri - USA
  • Status: offline
2015/05/18 11:34:53 (permalink)

Ranked Staff View fix request list

I have no stronger affiliation with anyone at Cakewalk than any of the rest of you.  I'm just an impartial, non-Staff View user with an idea on how to present a clean, prioritized list of fix requests to Cakewalk.  I will take your input and compile a list of specific Staff View fix requests you're looking for, presented in order by the number of individual requests for each item.  Once compiled, we can send this Cakewalk for consideration. 
 
IMO this will accomplish two things; a) it will provide the Cakewalk team with a prioritized list of outstanding Staff View items that need attention from the user perspective.   b) the total number of submitters and counts for each item will provide a clear picture of just how many people are impacted by these items.  This might not accomplish much on a resolution timeline, but I don't see how the clearer picture that should result from this process could possibly hurt anything.
 
This will be easier (for me) to manage via email.  Please send your 1 .. n (no ties) list (please keep n <= 10) to bobf8332 AT gmail DOT com.
 
I'll prepare the list in order of number of requests, along with the number of requests made for each item.  I will periodically update the list and post it in this thread.
 
Am I crazy? 

Bob  --
Angels are crying because truth has died ...
Illegitimi non carborundum
--
Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64
Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s 
Waves Gold/IKM Max/Nomad Factory IS3/K11U

#1

11 Replies Related Threads

    Kamikaze
    Max Output Level: -45 dBFS
    • Total Posts : 3013
    • Joined: 2015/01/15 21:38:59
    • Location: Da Nang, Vietnam
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/18 11:44:15 (permalink)
    I believe this is the list Craig took to Cake, but cake haven't publicly responded to it.
     
    1.  Ensure that the snap-function works correctly.  When selecting a 16th note, the snap should move by that amount (with an override option of course).   Same with all note values.   Now, a smaller note value will cancel out Sonar's ability to snap to larger note values.
     
    2.  Tied and dotted triplets, 32nd note triplets and 64th notes should display correctly.
     
    3.  When screensets are used and switched back and forth, the order of the instruments in the staff view track pane becomes confused.
     
    4.  When trying to open a note's properties when that note is on the first space or below the the staff, it doesn't always work easily.
     
    5 . Note icons back in SV
     

     
    #2
    Doktor Avalanche
    Max Output Level: -32.5 dBFS
    • Total Posts : 4294
    • Joined: 2015/03/26 18:02:02
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/18 11:52:55 (permalink)
    > Am I crazy?  
     
    You are definitely crazy  but I think this can be an extremely productive thread as long as the specific problems are discussed. As far as the Cakewalk side of things (i.e. the opinion that they haven't dealt with the issues in timely manner) may I strongly suggest that would probably be best left to the other thread which has become so large it's ceased to become productive.

    Good idea anyway! Thankyou for being productive.
    #3
    BobF
    Max Output Level: 0 dBFS
    • Total Posts : 8124
    • Joined: 2003/11/05 18:43:11
    • Location: Missouri - USA
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/18 11:58:30 (permalink)
    Kamikaze
    I believe this is the list Craig took to Cake, but cake haven't publicly responded to it.
     
    1.  Ensure that the snap-function works correctly.  When selecting a 16th note, the snap should move by that amount (with an override option of course).   Same with all note values.   Now, a smaller note value will cancel out Sonar's ability to snap to larger note values.

    2.  Tied and dotted triplets, 32nd note triplets and 64th notes should display correctly.

    3.  When screensets are used and switched back and forth, the order of the instruments in the staff view track pane becomes confused.

    4.  When trying to open a note's properties when that note is on the first space or below the the staff, it doesn't always work easily.

    5 . Note icons back in SV




    This is intended to be an extension of that list, compiled from a larger group of users with a stake in Staff View.

    Bob  --
    Angels are crying because truth has died ...
    Illegitimi non carborundum
    --
    Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64
    Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s 
    Waves Gold/IKM Max/Nomad Factory IS3/K11U

    #4
    michael diemer
    Max Output Level: -68 dBFS
    • Total Posts : 1128
    • Joined: 2013/05/24 18:54:50
    • Location: Maine, USA
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/18 12:08:21 (permalink)
    Bob, I sent you my list via email per your instructions.

    michael diemer
    Intel Quad Core i7-3770 Ivy Bridge
    32 GB ram
    1TB Western Digital Black X2
    Microsoft Windows 7 Pro 64
    UR22 interface
    Bandlab Cakewalk/Sonar 8.5 Studio
    GPO-EWQLSO Gold-Vienna SP ED-Cinematic Strings 2
     
     
     
     
    #5
    TomHelvey
    Max Output Level: -80 dBFS
    • Total Posts : 537
    • Joined: 2013/02/26 20:23:54
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/18 21:30:37 (permalink)
    Kamikaze

    1.  Ensure that the snap-function works correctly.  When selecting a 16th note, the snap should move by that amount (with an override option of course).   Same with all note values.   Now, a smaller note value will cancel out Sonar's ability to snap to larger note values.


    The snap needs to be independent of note duration. If it isn't, you would never be able to enter a series of dotted eighth notes or a half note on 2. Fixing the problem as suggested above would break it even worse that it is now.



    System: i7-6900, 64Gb, AMI X99 Carbon Pro Gaming, AMD Radeon HD 7700, Win 10 Pro
    PCIe: UAD Octo
    USB: MOTU midi express 128, OB-6 Module, Akai MPK-249, Moog SUB 37, Antelope Orion 32 HD, Softube Console 1, iLok, eLicenser
    DAW: Cubase Pro, Ableton Live, Sonar Platinum
    Plugins: Waves, UAD, Xfer, Lennar Digital, u-he, Reveal Sound, Spectrasonics, SoundToys, VPS, Blue Cat, iZotope, NI, Valhalla, Lexicon, etc.
     
    https://soundcloud.com/thomas-helvey
    #6
    mettelus
    Max Output Level: -22 dBFS
    • Total Posts : 5321
    • Joined: 2005/08/05 03:19:25
    • Location: Maryland, USA
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/18 21:44:31 (permalink)
    BobF
     
    Am I crazy? 




    Only if you keep doing the same things repeatedly and expect a different result (Alex beat me to the punch, but couldn't resist temptation!)

    ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
    #7
    Kamikaze
    Max Output Level: -45 dBFS
    • Total Posts : 3013
    • Joined: 2015/01/15 21:38:59
    • Location: Da Nang, Vietnam
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/18 22:00:14 (permalink)
    I agree Tom. I was posting the list of 5 things that Craig took to cake, if you look at the post I took this from, you'll see I also said the same thing
    http://forum.cakewalk.com/FindPost/3189561

     
    #8
    jatoth
    Max Output Level: -83 dBFS
    • Total Posts : 363
    • Joined: 2009/08/12 06:31:35
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/19 08:28:01 (permalink)
    Isn't that horse dead enough yet?
    In my case it's been 7 years
     
    mettelus
    BobF
     
    Am I crazy? 




    Only if you keep doing the same things repeatedly and expect a different result (Alex beat me to the punch, but couldn't resist temptation!)




    I guess you can call me crazy too.

    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.
    #9
    williamcopper
    Max Output Level: -68 dBFS
    • Total Posts : 1120
    • Joined: 2014/11/03 09:22:03
    • Location: Virginia, USA
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/19 13:26:46 (permalink)
    I took a quick look at staff view today.    It's better, maybe, than it used to be, but there is so much that just looks bad.   These things are not on your list, but they are what anyone who is accustomed to music scores sees instantly.  
     
    Beams:  always flat
    Enharmonics: frequently wrong, and not easy to change (the only way I found is to call up the Note Properties dialog, highlight the pitch field, and type in the correct name.)
    Stem length: for notes with ledger lines, comically short.
     
    Interface things:
    -- That flashing thing that shows where your mouse pointer is, in time, notes, and midi number?    Good grief.  I can see a beginner liking it, but I really do not want a flashing thing that is fixed in place and does not follow the cursor.    Could not find a way to disable it.  
    -- Need the option to have staff names 'float' ... it's completely impractical to go back to the beginning to remind yourself which is the trumpet and which the horn; likewise key signatures and perhaps time signatures need a float option. 
     
    More subtle things, one could live with them:
    -- Spacing is pretty crude, vertical and horizontal. 
    -- Combine tracks onto a staff?  This may be possible, but I didn't see a way to do it.   Very helpful in compressing an instrument, divided up in order to get articulations, but back together for the musical line. 
    -- "hairpin" the only option for the hundreds of things one might put into a score .. 
    -- "pedal" for all tracks, even the trumpets and horns? 
     -- the horizontal band under staves ... is that for placement of dynamics and hairpins?  very bad idea.  And it appears that once it is put on, it won't go away.    Consider this: staff lines are horizontal lines, there are five of them.    With those bands, two more are placed in 'ledger-line' area ... making for a very hard to read version of even a simple score.
     
     
     
    post edited by williamcopper - 2015/05/19 13:37:24
    #10
    noynekker
    Max Output Level: -66 dBFS
    • Total Posts : 1235
    • Joined: 2012/01/12 01:09:45
    • Location: POCO, by the river, Canada
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/19 21:37:15 (permalink)
    williamcopper
     
     
     -- the horizontal band under staves ... is that for placement of dynamics and hairpins?  very bad idea.  And it appears that once it is put on, it won't go away.    Consider this: staff lines are horizontal lines, there are five of them.    With those bands, two more are placed in 'ledger-line' area ... making for a very hard to read version of even a simple score.
     
     
     


    I asked on the forum a long time ago about this being a possible bug, but no one else could reproduce it.
    Recently I had it happen again, I made the mistake of clicking the "CHORDS" button to turn it off while the project was playing. It doesn't like that. Only way to turn that horizontal band off now is to close Sonar and re-open.
     
    Other projects work as expected, the "CHORDS" button can be turned on and off . . . just don't do it while the project is playing, or it seems to stick. So again, can anyone reproduce this ? Or is this thread just for confirmed bug fix list ?
     
    Another Staff issue I ran into a few days back was inserting Sustain Pedal on/off (Midi controller 64) events.
    When it reaches the inserted Sustain on (level 127) . . . it mutes the track, until the Sustain off event (level 0)
    When you look at this section in PRV view, what has happened is that all the notes have been changed to just a white outline for the section where the Sustain Pedal is inserted.
    If I can't figure this one out, maybe I'll start another thread about this.

    Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.

     
    #11
    BobF
    Max Output Level: 0 dBFS
    • Total Posts : 8124
    • Joined: 2003/11/05 18:43:11
    • Location: Missouri - USA
    • Status: offline
    Re: Ranked Staff View fix request list 2015/05/20 16:30:39 (permalink)
    I've received one list at this point.  I guess the list Anderton got in one of the other threads has what folks are looking for most, so there is little interest in going thru this exercise.
     
    Here's the list I received in case any Staff View users are interested:
     

    1. Fix triplets! (Actually more correctly called "tuplets.").
     
    2. Be able to print a score where each page has only the instruments actually playing at that time, so there are not, like, ten empty instrument tracks on each page, with a gazillion rests!
     
    3. Sometimes you can't insert a dynamic marking, like mf or mp, under the staff, because apparently there is not enough room.
     
    4. Be able to add octave markings, like this:    .........8v.  This signifies that the passage is to be played an octave lower or higher (I did not notate this exactly due to limitations of the keyboard - there should also be lines that indicate up or down). Doing this prevents the use of excessive ledger lines.
     
     5. Be able to bracket groups of like instruments. Woods, brass, strings, percussion all form mini sections within the orchestra, and it is traditional to bracket them off for easier reading.
     
    6. Allow the user to choose where slur lines should be. This is done to indicate bowing in stringed music, and phrasing in wind instruments.
     
    7. Add little abbreviations like:  Tr........  This indicates a trill. Actually, it should be a wavy line, but dots will do. This allows you to notate a trill with just one note, instead of like twenty!
     
    8. Tremelos: they are abbreviated by placing horizontal lines through the note sten. One line means you play the note twice, two lines means you play it four times, etc.
     
    9. Harmonic indicattions: On strings and harp, (and sometimes flutes), the player plays harmonic notes, which guitarists are very familiar with. the notes sound an ocatve or more higher. they are indicated by placing little circles over the notes heads.
     
    10. Be able to add wedges to show an agressive attack on a note. Similarly, be able to show string bowings as up or down.
     

    Bob  --
    Angels are crying because truth has died ...
    Illegitimi non carborundum
    --
    Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64
    Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s 
    Waves Gold/IKM Max/Nomad Factory IS3/K11U

    #12
    Jump to:
    © 2025 APG vNext Commercial Version 5.1