Jump to content

Jan

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by Jan

  1. On 1/4/2022 at 12:28 PM, Mark MoreThan-Shaw said:

    Also. Whilst I am thinking about it. What is the number string shown next to the "Vox " folder ? It's the parent folder that contains the "Lead Vox " and " Bvs " Subfolder

     

    Looks like a possible bug - integer overflow. This is the lowest possible 32-bit signed integer value.

    • Thanks 1
  2. I've had the same issue back in 2018. I had three instances of BlueARP targetting different VST instances. Played just fine, but nothing in the mixdown. Any ideas if this has been fixed/resolved in newer versions of Cakewalk? If not (given that 2021.09 is getting some improvements to how exporting audio works) perhaps we could bring it to the devs' attention? Or perhaps make a feature request for native support of VST MIDI (note generating) plugins (so that we don't need to do all this magic with extra tracks and "wiring")?

  3. 5 hours ago, Noel Borthwick said:

    Thanks, we have no control over this - its all handled by Windows.

    This seems to be a font that is a combination of bitmap (smaller sizes) and vector (larger sizes) - I believe it's the plain old MS Sans Serif. Changing the font on those labels would probably solve that.

    While I'm here - kudos on the new look of the envelopes, I was just thinking a couple of days ago "I wonder if Cakewalk finally got rid of this outdated 3D look for nodes" :) Maybe this will convince me to upgrade (still on 2019.09 here...)

  4. 11 minutes ago, Noel Borthwick said:

    Every installer starting from this release will have a rollback to prior version. So you will only be able to go as far as 2020.01 by rolling back successively.
    We don't  plan to have rollbacks to earlier than that.

    Ah, I see, so assuming there'd be a 2020.03, 2020.05 - 2020.05 would let me rollback to 2020.03, then from 2020.03 I'd be able to rollback to 2020.01, correct?

  5. 15 hours ago, Noel Borthwick said:

    Currently the rollback will only go to the immediately prior release.

    So, if I have 2019.09, install 2020.04 and find out that something is not working, my only "official" option is to go back to 2020.01, which might have the same issue... I hope "rollback to what *I* had" is in the works :) Keep it up.

  6. On 4/15/2020 at 2:56 PM, Noel Borthwick said:

    @RBH yes we plan on releasing rollback installers going forward with every release.

    Will they rollback to the previous released version or the version that I had installed? For instance, I'm on 2019.09 ATM. If I install 2020.04 and decide to rollback will it rollback to 2020.01 (previous release) or 2019.09 (the one that I had)?

  7. On 1/23/2020 at 5:46 PM, Morten Saether said:

    As with Simple Instrument Tracks, you must split the Instrument tracks if you wish to edit MIDI automation.

    Pardon this slight OT and a more general question: Why there cannot be MIDI automation on the Simple Instrument Tracks? Is this by design? Are there plans to bring MIDI automation to Simple Instrument Tracks? I mean... that would've simplified my projects so many times, I could've probably cut the number of tracks by ≈⅓.

  8. On 10/21/2019 at 11:16 PM, Bill Phillips said:

    I have a 1st gen 18i8. I usually install the latest driver listed on My Hardware Focusrite page and don't have any significant problems. I have the latest version 4.63.24 installed and seems to have fixed the bug with changing buffer size while CbB is open. Both the latest and the previous version work fine and I found work arounds for adjusting buffer size in the previous version. I'm tickled and am impressed with the performance especially when compared with the original 1st gen drivers.

    Could you elaborate a bit more about the "changing buffer size while CbB is open"? What exactly is the issue and what are the workarounds? Thanks!

×
×
  • Create New...