Jump to content

Сzeslaw

Members
  • Posts

    96
  • Joined

  • Last visited

Posts posted by Сzeslaw

  1. In the video:

    1.to the left in the Cakewalk window is the Vienna Ensemble Pro5 plugin,

    2. on the right - the instance of Vienna, which is connected to the plugin, but launched outside Cakewalk,

    In both cases (when either Cake or Vienna windows are active), the spacebar starts playback in Cakewalk - this is the correct behavior.

    18 hours ago, Noel Borthwick said:

    In your video you have not enabled the "give all keystrokes to plugin" button in the main VEP plugin window. Does it make a difference if that button is enabled?

    No.

    18 hours ago, Noel Borthwick said:

    Also to clarify - the video you posted is with it working properly correct?

    Yes.

    18 hours ago, Noel Borthwick said:

    BTW we had a case for this already logged. Unfortunately it did not get investigated in this release. I will escalate it and we'll address it since it appears to be a regression.

    OK, Thanks!

    15 hours ago, Noel Borthwick said:

    Lets say ahem that this is pretty unorthodox behavior for a plugin to do and I've literally never seen any other plugin do this.

    :)

    15 hours ago, Noel Borthwick said:

    I have made a couple of changes to listen to keystrokes at the app level, and now the play button and spacebar work in VEP.  However we'll have to test it and make sure there aren't any unwanted side effects to this. 

    OK!

  2. 5 minutes ago, msmcleod said:

    You just run the setup forJBridge.  Cakewalk has in built JBridge support, so don't run a scan within JBridger application.

    Sorry, I didn't know that jBridge integrates into Cakewalk by BandLab!

  3. 19 hours ago, msmcleod said:

    Out of interest, does this setting make any difference?

    I suspect it might have to be unchecked when using VEP.

    This parameter was disabled for me, but enabled it does not change anything.

    msmcleod, can we hope to fix this problem in newer versions?

    • Like 1
  4. Surprise surprise !!! This works in versions 26.04.0.151 (2020.04.build151)!!!

    https://drive.google.com/file/d/1BvF2iiDTPLcRVDMLj2wRX6v4SmBbDXSs/view?usp=sharing

    And in the next version 2020.04, playback starts immediately after loading the project with the VEP window in focus, but if you activate the CbBL window and then the VEP window again, playback will no longer start.

    I have installed sequentially versions of CbBL one after the other, starting with 24.4.0.13.

  5. 14 hours ago, Canopus said:

    Are you sure you're running Vienna as a VST and not as a stand-alone executable?

    Absolutely.

    Maybe you don't know how the DAW+VEP works? Sorry, but judging by this post of yours, you do not know.

    14 hours ago, Canopus said:

    That should come as no surprise. If Vienna is run as a stand-alone executable and has focus, of course it will receive all keystrokes. That's how every Windows application works.

    The VEP VST plug-in from the DAW connects to a host instance on the same computer or on another (connected over your home network) and runs VEP as a host. And as NGC 598 said:

     

    12 hours ago, NGC 598 said:

    It works with Сubase, Studio 1 and Reaper

    Is this a surprise for you?

  6. Hello everybody!
    It has long been an urgent problem!
    In such DAW as Reaper, Cubase, Studio1, when the Vienna Ensemble Pro5/6 window is active, starting playback of the project in these DAWs with the Space key is normal.
    When Vienna is working with CbBL, playback does not start! And this is very uncomfortable and upset.

    Can this be fixed?

    • Like 2
  7. 4 hours ago, Philip G Hunt said:

    is there some way I can do a clean install of the build 2020.08 (which was the last truly stable version I had) or 2020.09 -

    I've rolled back from 2021.14 to 2021.01, but when I try to roll back to earlier versions it corrupts my install and I have to uninstall and reinstall CbB build 2021.14 again. Help!

    Hey! I have installer version 26.08.0.100, and apdate 26.08.0.120.

    Upload to google drive?

    • Thanks 1
  8. Thanks for Update 202.09.06.000!

    But...

    Quote

    Option to decouple global Snap to Grid from the Staff view with UseGlobalSnapForStaffView=0 Cakewalk.ini setting.

    This do not work. In Win7 and Win10 too.

  9. 18 hours ago, msmcleod said:

    There's two things in play here:

    1. The positioning resolution (dictated by the Global Snap - which is set to whole measures)
    2. The note length, which is dictated by which note you've clicked.

    There's actually a couple of other settings in the View menu that may affect things:

    3. The "Display Resolution" - I pretty much always keep this at 1/32.
    4. The "Fill Durations" setting, which I suspect is checked on your set up. I normally keep this unchecked.
     

    1. That's just it, that in version 2020.05 nothing in the staff does not depend on this setting - the notes can be inscribed in any part of the rhythm.

    https://1drv.ms/u/s!AlLNG4SDVWiJgqYnewqpOfC0wm4izA

    2. Sorry, but because of the difficulty of translating this phrase, I don't understand.

    3. Yes, I do the same.

    4. Disabling this feature does not affect anything.

    Quote

    What you're selecting is different note lengths,  not different position resolutions.

    No matter what I do, a note of any length hits the first beat of a measure.

  10. On 9/2/2020 at 7:42 PM, msmcleod said:

    @Vyacheslav - can you clarify this for me?

    In the previous release, the snap was hard-coded to 1/32... so you would have to aim quite precisely between the two bar lines to correctly position the notes rhythmically. In other words, there was always 32 positions between the bars where the note could be placed.

    Now, when global snap is on and set (for example) to 1/4, you don't need to be as precise as there's only 4 positions it could be placed in rhythmically.

    When global snap is off, it reverts back to the previous release's behaviour of 1/32.

    To my mind, having the global snap set to a less precise amount makes it easier to aim, not more difficult.... or am I missing something?
     

    @msmcleod - Thanks for the answer!

    If I understood you correctly ...

    https://1drv.ms/u/s!AlLNG4SDVWiJgqYoHPS-DatGIZBYiQ - Here you can see that (figuratively speaking) I do not have four positions and all the notes fall into the first beat of the measure, wherever I clicked with the mouse in the measure.

  11. 14 hours ago, msmcleod said:

    Just click the Global Snap to turn it off - it'll revert back to the old behaviour of  1/32nd (or 1/24 when using triplets).  

    Thanks! But this is not convenient! It is very inconvenient to do this every time you switch between the Staff and Tracks windows.

    It is also inconvenient, because without being bound to the rhythmic grid, all the notes have to be entered, literally aiming with the mouse not only at the stave's rulers in terms of the pitch of the notes, but also in terms of their rhythm.

    • Thanks 1
  12. Quote

    The Staff view respects the global Snap to Grid settings for note positioning when drawing notes.

    Is it possible to disable this and do it as it was in previous versions?

    UPD Maybe I translated something wrong with the help of Google translator.
    I ask you to suggest how to change the spelling of notes in version 26.08 to the previous method (as in version 26.05).

    26.08

    https://1drv.ms/u/s!AlLNG4SDVWiJgqYoHPS-DatGIZBYiQ

    26.05

    https://1drv.ms/u/s!AlLNG4SDVWiJgqYnewqpOfC0wm4izA

  13. Quote

    The Staff view respects the global Snap to Grid settings for note positioning when drawing notes.

    Is it possible to disable this and do it as it was in previous versions?

    UPD Maybe I translated something wrong with the help of Google translator.
    I ask you to suggest how to change the spelling of notes in version 26.08 to the previous method (as in version 26.05).

    26.08

    https://1drv.ms/u/s!AlLNG4SDVWiJgqYoHPS-DatGIZBYiQ

    26.05

    https://1drv.ms/u/s!AlLNG4SDVWiJgqYnewqpOfC0wm4izA

    UPD It turns out that I posted this post on the wrong topic. Sorry!

×
×
  • Create New...