i want to replicate your bug. X1c on vista or W7

Author
BlixYZ
Max Output Level: -74 dBFS
  • Total Posts : 805
  • Joined: 2010/12/31 16:45:54
  • Location: Barrington, NJ
  • Status: offline
2011/09/10 09:16:07 (permalink)

i want to replicate your bug. X1c on vista or W7

i finally updated to  X1c- i was in no hurry due to smooth running in x1b.  I'm getting curous about why every incarnation of X1 has been trouble free for me while being so problematic for others.  If  you have a bug that u can replicate, tell me the steps and I'll try to produce it.  Then I'll know whether or not it's just because I dont use a certain function or combination of commands.  I'm just really curious at this point.  

James W
BlixYZ Recording Studio
BlixYZ Records

Audient ASP800 thru Focusrite Saffire Pro 40
Mackie Control Universal + C4
Yamaha HS50's plus Matching Sub, Tannoy 501a
Blue Baby Bottle, AT 4050, Neumann TLM 103, etc.
UA 610, Focusrite/ART/Neve 2CH.
Windows 10
#1

7 Replies Related Threads

    FastBikerBoy
    Forum Host
    • Total Posts : 11326
    • Joined: 2008/01/25 16:15:36
    • Location: Watton, Norfolk, UK
    • Status: offline
    Re:i want to replicate your bug. X1c on vista or W7 2011/09/10 09:40:38 (permalink)
    Ok you asked, here's a few I've reported. X1c is more buggy for me than X1b. Nothing I can't work round but bugs all the same. All confirmed by CW BTW.

    5782 - Minor step sequencer display issue
     
    Steps to reproduce
     
    Create a drum pattern in step sequencer, save it
    Open a row so that you can see velocity info displayed
    Delete a couple of hits
    Reload pattern drawn at step one  

    Expected result
     
    I would expect to see the new drum hits velocity shown in the velocity display
     
    Actual result
     
    No velocity info is drawn until I click on the open row button again.
     
     
     
     
     
    5786 -
    PRV separate snap to bug
     
    Open step sequencer knock up a quick beat and leave the clip somewhere in a MIDI track
    Assign that track output to a Drum Map - this is the 'secret' ingredient.

    Any old drum map will do.
    Using the same MIDI track open the PRV somewhere away from the step sequencer clip
    Set the PRV snap to to a different value to the main snap to. I'm using 32nd in PRV, whole as main, just cos it really shows the bug.
    Now insert a note into the PRV.
     
    Mine is snapping to the whole, i.e. the main snap to. Turn the main snap off and it snaps to the PRV setting.
     
    5787
    Step Sequencer is blank when double clicking on a clip assigned to a drum map
     
    Create a step sequencer clip
    Assign the track it is on to a drum map
    Close the step sequencer
    Double click in the bottom half of the sequencer clip
     
    Expected Result
     
    I would expect the step sequencer to open the clip and display the hits
     
     
    Actual result
     
    The step sequencer opens in it's default state. ie. no notes or pattern
     
    5794
     
    Step sequencer clips truncate on bounce to clip
     
    To reproduce
     
    Create two or more step sequencer clips & a MIDI clip on the same MIDI track
    Roll out the step sequencer clips so they are longer than when created
    Select all of the clips and then bounce to clip
     
    Expected behaviour
     
    I expect the resulting clip to be the same length in time as the total of the selected clips
     
    Actual behaviour
     
    The step sequencer clips truncate and I end up with a much shorter clip.
     
     
    CWBRN 5807
     
    PRV gridline view won't remember setting when turning global snap off or PRV snap on
     
    To reproduce
     
     
    Make sure global snap is on
    Open PRV and set "Show Vertical Gridlines" to on and then set the resolution to something other than 1/4.
    Turn PRV snap on and/or Turn global snap off
     
    Expected result
     
    I would expect the grid view resolution to remain at my chosen value
     
    Actual result
     
    The grid view resolution resets to 1/4

    post edited by FastBikerBoy - 2011/09/10 09:41:43
    #2
    BlixYZ
    Max Output Level: -74 dBFS
    • Total Posts : 805
    • Joined: 2010/12/31 16:45:54
    • Location: Barrington, NJ
    • Status: offline
    Re:i want to replicate your bug. X1c on vista or W7 2011/09/10 09:54:35 (permalink)
    cool, thanks.  these all concern the ss and the prv.    are these the hub of most X1c bugs?
    #3
    FastBikerBoy
    Forum Host
    • Total Posts : 11326
    • Joined: 2008/01/25 16:15:36
    • Location: Watton, Norfolk, UK
    • Status: offline
    Re:i want to replicate your bug. X1c on vista or W7 2011/09/10 10:35:17 (permalink)
    All the ones I've found centre round drum maps, the only one that is consistent without a drum map is the velocity display bug, and that's real minor.

    The drum map ones are more annoying. Not the end of the world but annoying all the same.

    The PRV gridline display bug CWBRN5807 is more noticeable, and more annoying because that would be the obvious work round for one of the snap bugs, except it doesn't work.
    #4
    BlixYZ
    Max Output Level: -74 dBFS
    • Total Posts : 805
    • Joined: 2010/12/31 16:45:54
    • Location: Barrington, NJ
    • Status: offline
    Re:i want to replicate your bug. X1c on vista or W7 2011/09/11 11:41:49 (permalink)
    Here's what I got so far:
        5782 - Minor step sequencer display issue
     
    could NOT reproduce
     
       
        5786 -
        PRV separate snap to bug
     
    DID reproduce

        5787
        Step Sequencer is blank when double clicking on a clip     assigned to a drum map
     
    DID reproduce


        5794
     
        Step sequencer clips truncate on bounce to clip

    DID NOT reproduce.

    It really is annoying little stuff.  BUG is the perfect word.
    I use all of Sonar's tools on an "as needed" basis depending on what client I'm working with.
    I do use the step sequencer, but I haven't needed it lately.
    I am embarrassed to admit that I've NEVER used drum maps.  When I want to pick and choose drums sounds, I usually do it within the synth (BFD, Battery, SD, etc).

    I will try the rest when I have a few mins.
    #5
    FastBikerBoy
    Forum Host
    • Total Posts : 11326
    • Joined: 2008/01/25 16:15:36
    • Location: Watton, Norfolk, UK
    • Status: offline
    Re:i want to replicate your bug. X1c on vista or W7 2011/09/11 12:07:02 (permalink)
    Yeah just niggles. TBH I only ran into most of those as my X1c install coincided with a new project start and I was working on drums most of the day.

    5807  is being reported on here quite regularly. Strange how some bugs only seem to appear on some systems. As I said though all of those I posted are confirmed by CW and "submitted to development" so hopefully fixes are in the pipeline.
    #6
    Bub
    Max Output Level: -3.5 dBFS
    • Total Posts : 7196
    • Joined: 2010/10/25 10:22:13
    • Location: Sneaking up behind you!
    • Status: offline
    Re:i want to replicate your bug. X1c on vista or W7 2011/09/12 10:58:44 (permalink)
    BlixYZ

    i finally updated to  X1c- i was in no hurry due to smooth running in x1b.  I'm getting curous about why every incarnation of X1 has been trouble free for me while being so problematic for others.  If  you have a bug that u can replicate, tell me the steps and I'll try to produce it.  Then I'll know whether or not it's just because I dont use a certain function or combination of commands.  I'm just really curious at this point.
    How can you test a bug if it's already been fixed? There are well over 200 bugs in X1 that have been addressed and fixed ranging from Snap to Grid, to memory leaks in plug-in's, to the Pro Channel turning on/off by itself. All confirmed by Cakewalk.

    Asking people to list bugs so you can replicate them is just asking for trouble in this place, even though I do believe you are being sincere in wanting to help.

    The short answer is, you didn't use a lot of the things that were buggy, and there are way too many to list. The best thing to do is do a fresh install and check what was fixed before install a patch and see if you can duplicate the problem listed in the fix list for that patch.

    The only time there is a bug is if Cakewalk can reproduce it and have fixed it, or have responded saying yeah we saw it and sent it on to development ... it doesn't matter if an individual user can reproduce it, Cakewalk has to be able to reproduce it.

    Good luck,

    Bub


    "I pulled the head off Elvis, filled Fred up to his pelvis, yaba daba do, the King is gone, and so are you."
    #7
    pwal
    Max Output Level: -46 dBFS
    • Total Posts : 2909
    • Joined: 2004/08/24 07:15:57
    • Status: offline
    Re:i want to replicate your bug. X1c on vista or W7 2011/09/12 11:26:24 (permalink)
    they should just make the bug tracker browsable/public so we can what bugs are actually on the list...

    list of stuff
    #8
    Jump to:
    © 2024 APG vNext Commercial Version 5.1