Jump to content

Canopus

Members
  • Posts

    1,181
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Canopus

  1. 1 hour ago, User 905133 said:

    If we had a midi data flow chart we might know (1) if there is something else causing the behavior (and if so, what), (2) if the behavior is by design, or  (3) if it is a bug (along with other odd behaviors which no one seems to know if they are intentional or bugs). 

    In order not to derail this thread any further, I will just say that the posts above indicate that the ACT layer somehow blocks the MIDI note data being sent from the controller to the code that renders the PRV keyboard. I don’t think it’s is any more complicated than that. And I sure hope it’s not by design. :)

     The important thing is that there now seems to be a reliable way to reproduce the issue. 

  2. 1 hour ago, Mehrdad said:

    I figured out what's causing this issue for me but the reason is quite a bummer. It was due to enabling Cakewalk's MIDI ACT feature for me. Whenever I enable the MIDI ACT Function and set my MIDI keyboard as the ACT device the next time that I open up any project in Cakewalk this happens

    Quite so! Great troubleshooting, @Mehrdad! In CbB I had created an ACT Controller/Surface for my MIDI keyboard and when I now removed it, the visual keys on the PRV keyboard started to work. And in SONAR Platinum by contrast I did not have any ACT Controller/Surface defined, which is why the visual keyboard worked there without any issue. Now that the cause seems to be determined there’s at least some hope to have it fixed. As long as the root cause wasn’t found I didn’t see any point in reporting it as not everyone was experience this issue. Maybe we should send a trouble report each to support in order to get some attention?

  3. 22 minutes ago, RobertWS said:

    It looks like you are using an early access version (EA?)

    There is a separate forum for that.

    This is not something that started to occur in 2021.01 EA. It has been like this for quite some time in CbB production releases, although I don't know exactly when it started.  I know for sure that it was present in 2020.08 but I think it was a problem long before that. However, I also realise that not everyone is affected by this issue.

  4. Yes, same for me as well. This problem has been mentioned before, but I’ve never seen any response or comment from support.

    https://discuss.cakewalk.com/index.php?/topic/18788-prv-animation-on-midi-input

    https://discuss.cakewalk.com/index.php?/topic/18923-issue-with-piano-roll

    As I wrote in one of those threads, when I run SONAR Platinum 2017.10 (i.e. last SONAR) it still works with live input, but not so in CbB. Something seems to have been changed in the code that renders the PRV keyboard, but not for the better. Here’s an animated GIF showing the problem in CbB side by side with SONAR:

    qF4hTeF.gif

  5. The theme Lead has now been updated to support GUI modifications in CbB 2021.01, or more specifically the addition of four buttons to the Large size Select module. Personally I will however switch to the Medium size Select module so that everything will look as before to save some screen estate.

    kb2cDwC.png

    There are some additional changes as well:

    • The Arm All Tracks button in the Control Bar’s Mix Module has previously been blue (as it is in Mercury). However, as the Arm button on each individual track is red, Arm All Tracks has now been made red as well for better consistency.
    • The meters in the Performance module have been changed from orange to blue to better match the theme’s overall appearance.

                 Ov6lWGb.png

    • Unselected synths in the Synth Rack now have a dark background colour, as the previous blue highlight background for both selected and unselected synths may have been confusing.
    • The button in the Export module had a slightly incorrect back­ground in both large and small size. This has now been fixed.
    • The Freeze and Archive buttons didn’t exactly match the appearance of the other buttons in the Track module. This has now been fixed.

    Download the theme from the link supplied in the first post.

  6. Both Gran Vista and Carbon have now been updated to support GUI modifications in CbB 2021.01, or more specifically the addition of four buttons to the Large size Select module. There are some additional modifications as well:

    • The Control Bar buttons used to set areas for Select, Loop, and Punch have been slightly modified, in that the marker triangles on those buttons have been gi­ven the same colour as the corresponding function in the Track View; yellow for Loop, green for Selection, and red for Punch. This is a feature that I’ve borrowed from my Lead theme where it was introduced. Here’s how these changes look in Gran Vista, but Carbon has similar modifications.

                 N0xs9jo.png

    • The Arm All Tracks button in the Control Bar’s Mix Module has previously been blue (as it is in Mercury). However, as the Arm button on each individual track is red, Arm All Tracks has now been made red as well for better consistency.
    • The meters in the Performance module have been changed from orange to blue to better match the theme’s overall appearance. That colour wasn’t pos­sible to change at the time these themes were created, but has apparently been quietly exposed to the Theme Editor since then.

                 mXwbm7A.png

    • Unselected synths in the Synth Rack now have a dark background colour, as the previous blue highlight background for both selected and unselected synths may have been confusing.

    Download the themes from links supplied in the first post. There you will also find a link to the release history.

  7. Well, I think there is. In Preferences > Customization > Keyboard Shortcuts > Key Bindings, set Area to Track View and in the Search field write Ripple. This will result in two functions being displayed: Options | Ripple Edit Selection and Options | Ripple Edit All, ready to be bound to whatever keys you'd like.

    • Like 1
    • Thanks 2
  8. Yeah, I got a measly €20 voucher this time which equals around 12 % of my purchases directly from UVI last year. And it’s only valid until the last of January, a month when they normally don’t have any deals anyway. Oh, well. They can keep it. My loyalty has its limits.

    • Like 1
  9. There are mainly two types of piano plug-ins; those that are sampled and those that are modelled. Sampled instruments are based on actual recordings of physical instruments, while modelled instruments are based on computer algorithms emulating the sound of physical pianos. There are also some hybrids of which the True Pianos previously bundled with some versions of SONAR is one. Of the pianos mentioned above, XLN Audio's Addictive Keys is a sample based instrument while Pianoteq makes modelled ones.

    Each kind of technique has its loyal followers. May I suggest that you try to decide for yourself what pianos you prefer before you pick out your Big Credit Card. Free pianos do exist but are few and far between. Also, the quality may vary. In addition some of them require the full Kontakt plug-in from Native Instruments, which in itself is quite expensive.

    There are plenty of demos. Some of them are quite usable but often come with a limited number of octaves and/or fewer microphone perspectives. The 49 key demo from XLN Audio that John mentions above I think is very good. It's free and there is no time limit so you can use it as long as you wish.

    Should you look for a full 88 key version and are on a tight budget, there is a grand piano called Mini Grand from AIR Music Technology which often can be found for $10 or thereabout. It’s actually currently available for €10.27 at Plugin Boutique. It’s not on level with more expensive grand pianos, but as always you get what you pay for. However, it does require iLok for copy protection.

  10. 18 hours ago, cclarry said:

    It's a really good deal.  The 8DIO Choirs are really good...

    Indeed they are. Not that I can make them any justice, but here is a short demo of the only 8DIO choir I've got; Requiem Pro.

    To facilitate the listening experience, here's the lyrics:

    Quote

    cc-Larry, Glo-ri Cre-dit
    cc-Larry, Sanc-tum Cre-dit

     

    • Great Idea 2
    • Haha 1
  11. There were GUI changes made to CbB 2020.04 relating to the Arranger that affected all themes. Based on the clip and that your issue apparently fixed itself, I guess that you use Tungsten and previously saw some old cached version of it. But I remember that you made a couple of themes yourself in the old forum. If you want to update them, here’s a thread describing the modifications necessary to user themes if they are to be used with CbB 2020.04 or later:

     

    • Thanks 1
  12. If I understand your problem correctly, you need to set your keyboard to Local Off to turn off its built-in tone generator. I have no personal experience of Artesia but according to the PE-88 manual you turn Local Off by following these steps:

    Quote

    Press the [FUNCTION] button repeatedly to select MIDISET, then press the [ENTER] button to confirm, the LCD will display LOCAL, press the [ENTER] button to confirm, use [+/-] buttons set the value the function On or Off.

     

  13. 59 minutes ago, Sleetah2000 said:

    1).  Clicking on a Folder Midi/Audio-Qty hides/unhides tracks in both Trackview and Console views with a single click.  Conversely, when you click on "+/-" in trackview, folded tracks still remain visible in Console view.  [...] In any case, if one carries excess tracks, I find it very handy to control what you can see in console view at the click of a button, rather than scroll across many pages of minimized faders that you don't need to worry about right now.  

    I actually played around with the same idea about a week ago. I even made an animated gif to show how it might look, but I never posted it. But hey – here it is.

    1ltVtxz.gif

     

    • Like 1
    • Thanks 1
  14. 35 minutes ago, husker said:

    Maybe, maybe not.  I was asking if the historical upgrade price was $99, which now seems to be $199.

    The last time Arturia offered an upgrade to a newly released version of V Collection for $99/€99 seems to have been in 2016. Since then the upgrade price at release time has always been $199/€199.

    4-5 $99/€99 (2016): http://forum.cakewalk.com/Arturia-V-Collection-Special-Offers-m3515043.aspx

    5-6 $199/€199 (2017): http://forum.cakewalk.com/ARTURIA-V-Collection-5-owners-Updates-available-go-get-Also-VC-6-is-out-m3703671.aspx

    6-7 $199/€199 (2019): https://discuss.cakewalk.com/index.php?/topic/3322-arturia-v-collection-7-announced/

     

×
×
  • Create New...