Jump to content

GreenLight

Members
  • Posts

    549
  • Joined

  • Last visited

Posts posted by GreenLight

  1. On 10/20/2019 at 12:25 AM, KyRo said:

    I second those calling for marker enhancements, with a multicolored section system (a feature requested for Cakewalk a number of times over the years), perhaps as a new time ruler, akin to Pro Tools' et al:

    Great to see so much consensus around requesting marker improvement! :D (We're actually so much in tune that both of us posted ProTools pictures in this discussion. 😜)

  2. Hi all!

    I have been having an intermittent problem with Cakewalk (and maybe Sonar?) for a long time, but unfortunately I can't really reproduce it reliably.

    I preview a lot of wav files using the browser, and sometimes certain files "bypass" the preview bus and somehow play back anyway, often REALLY LOUDLY, making me jump in my chair. No meter in Cakewalk moves, but I can see the sound card mixer software reacting. It doesn't happen very often, but when it does it seems to affect a specific file: that file always has the same problem every time I play it during that session. I just had the issue with a wav loop, but after restarting Cakewalk, the same file played back normally through the preview bus. 😕

    So I'm wondering if anyone else has experienced this? I just had the problem on Cakewalk 2019.09 build 70.

    I don't know how to troubleshoot or to properly report it... :(

  3. With regards to markers, I kind of like ProTools' solution of a separate marker "section" (or "track" maybe, but it doesn't look like a track really).

    It makes markers very easy to distinguish, albeit by sacrificing some vertical space:

    image.png.4a99db5d153eaf515864b66f03e0c6e3.png

    Image from recordingrevolution.com:
    https://www.recordingrevolution.com/optimize-pro-tools-marker-colors/

    Something for Cakewalk to be inspired by, perhaps? :)

     

    • Like 3
  4. 13 hours ago, Helene Kolpakova said:

    Is it possible to revert the Rewind behaviour to the one in previous versions? The fact that it keeps playing after the rewind button has been pressed, breaks my flow as it feels counter-intuitive and introduces an extra button press: [Space] to stop + [W] to rewind, instead of a single [W].

    I haven't had time to install 2019.09 yet, but I am interested about this possibility as well. My workflow is to use W like you all the time, expecting playback to stop. :)

    From the Feature Overview thread:

              "Go to Start and Go to End buttons (?) now accurately seek to project beginning and end, and do not stop playback."

    Does the stopping only concern the buttons and not the actual keybindable actions? Or was it just an unfortunate choice of words...?

    Maybe we could have two different keybindable actions:

    • Go to Start (and stop)
    • Go to Start (and keep playing)

    Then it would be easy for the user to select. :)

    • Great Idea 1
  5. On 10/3/2019 at 1:53 AM, Noel Borthwick said:

    I meant in the code we catch the exception and ignore it. Its not a recommended procedure but its a failsafe.
    You can't prevent the crash yourself till you get the fix from us...
    Please report it to them - I will also file a bug report directly.

    So if I install 2019.09 right now, I won't be able to use projects that use U-he Satin?

    I am SO psyched about the Duplicate Clips feature, it's something I have requested a couple of times in the past. :D:D

  6. 51 minutes ago, Tenfoot said:

    Thanks @Tenfoot, cool! Had no idea it existed, but I'm sure it can be very useful ! :D

    My first thought was that project loading times might be annoying, and then I read your post above... 😛

    • Like 1
  7. On 9/1/2019 at 4:34 PM, JoseC said:

    The main error with the Matrix is thinking that it is like Live's Session view, trying to use it like it and becoming frustrated.

    <CUT>

    Thanks a lot for your extensive reply, @JoseC! And really smart ways of using it, including the SysEx trick, I will remember that! :D

    • Like 1
  8. 48 minutes ago, JoseC said:

    As I said above, you can automate that using step probabilities and recording the Matrix output. I agree with you that it needs more polishing. If its integration with the Matrix was a bit better it would be a more powerful tool than it looks at first sight.

    Yes, I've used step probabilities a little when programming hi-hat patterns, I think I'll investigate it a bit more...

    How is Matrix best put to use, if you're only doing studio work? I suppose it's a Live-style pattern trigger feature? I've never really investigated it...

  9. On 8/30/2019 at 3:33 PM, jackson_js22 said:

    Is there a way to force Step Sequencer to "follow" the song progression ?

    Unfortunately no (as others already said) and the step sequencer does also not follow playback position if you have extended your step sequencer clip using groove clip looping (CTRL+L).

    Step sequencers in general are probably most used for drum programming for electronic dance music and hiphop, but I recently got a great melodic sequence out of it for a techno track, with some great happy accidents when clicking and removing notes. :D

    It would benefit from some more polishing though... :)

  10. Hi all!

    Can anyone replicate these 2 step sequencer bugs? (Although I'm not sure #2 is technically a bug, but at least for me it doesn't behave as expected).

    Bug 1: Undocked Step Sequencer window status not remembered after closing window

    1. Create a blank project and create a step sequencer clip
    2. Double click the step sequencer clip and it should open docked
    3. Undock the step sequencer
    4. Close the undocked step sequencer window
    5. Double click the step sequencer clip again and it has forgotten it was undocked - it opens docked again

    Bug 2: Step sequencer playback marker cannot handle groove-clip looped step sequencer clips
    As I mentioned above, I'm not sure this is technically a bug, but at least for me it doesn't behave as expected.

    1. Extend a step sequencer clip several measures using groove-clip looping (CTRL + L and drag)
    2. Play the clip and watch the step sequencer window: the playback meter only works the first measure, then it's blank. I would expect it to loop and indicate current step as long as the clip has been looped.
    3. Note: The PRV seems to also not be able to display notes in groove-clip looped step sequencer clips. Only the notes in the first bar are shown.
      (I find it really useful that all note changes in the step sequencer are also immediately shown in the PRV – love it! I would just love them to be shown when looped as well. :))

    I am using Cakewalk 2019.07 Build 79.

    Thanks for a great product! :)

     

     

  11. Hi all!

    If I remember correctly, it should be possible to extract MIDI note information from an audio clip by just dragging it to a MIDI track?

    Since I reinstalled my studio PC, that no longer seems to work - when I release the mouse button, Cakewalk asks:

    Quote

    "Audio to MIDI conversion may take a while depending on audio duration. Do you wish to proceed?"

    ...but nothing happens when I click yes (I do see a quick progress bar flashing by though).

    Am I missing something? Any ideas? Thanks!

  12. 35 minutes ago, Alan Tubbs said:

    Noel, impressive  list over time.  Maybe someone should try to pitch It to the mags ...

    @Alan Tubbs Might you yourself have any clout with regards to this, as you're a regular contributor to the magazine in question? :)

    And great job with all your reviews in SOS, by the way - the Cakewalk ones and all the others! :D

  13. On 6/10/2019 at 11:12 AM, Promidi said:

    This can be done globally. Under "Controller names", "Standard" in Define instruments and Names, you can customise the list as shown below.

    It would be nice if this can be done per VST synth, however.

    Thanks for the great tip, Promidi!

    I know there is a MIDI CC standard, but the parameters a MIDI CC controls are often unique per project anyway, at least for me. Any given parameter on any given VST synth could be MIDI learned to (almost) any MIDI CC number, so pre-defining global parameter names is not really feasible.

    Assigning a name to an envelope would probably be most convenient when creating the envelope. :)

    • Great Idea 1
×
×
  • Create New...