Jump to content

Search the Community

Showing results for 'prv' in content posted in Feedback Loop.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • News & Announcements
    • Product Release Info
    • Frequently Asked Questions
  • Cakewalk Products
    • Cakewalk by BandLab
    • Instruments & Effects
    • Feedback Loop
  • Community
    • Content
    • Tutorials
    • Songs
    • General Music Discussion

Product Groups

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

  1. Is this not doable? My old Ensoniq had this and my current one can receive it. You can turn on Key Aftertouch & Channel Pressure in Preferences, and PRV has ChanAft in Controller Pane, but I don't see Poly or Key Aftertouch per se.
  2. Until it is implemented, one way I can think of doing something close to this is with Articulation maps in the PRV.
  3. Can we please have the ability to rename CC lanes in the PRV (When the name is visible)
  4. Currently, Instrument definition files only function for external synths and external sound modules. It would be good if we can add Instrument definition files for VSTi plugins. Mainly for CC types so the correct names show up in the CC lanes in the PRV. I know these names can be configured globally. However per plugin would be nice. Yes, I know I could “just use Automation lanes”. But PRV CC lanes are, currently more flexible (transform tool for exampel),
  5. When stretching a note in PRV, the tooltip creates a flickering image of itself. This only occurs on my new Win11 laptop's 2nd monitor when CbB is maximized full screen. (NVIDIA GeForce RTX 3050 Ti laptop GPU) Not noticed on previous Win10, Win7, or XP systems using the same 2nd monitor. And does not appear on the laptop's main screen or when floating on 2nd monitor.
  6. I use single Controller view. Under the PRV view menu, I always have “Show Multiple lanes” deselected. In fact I resisted the change from CPA9 until this view option was added to Sonar Platinum. (and CbB)
  7. Yeah... I run into this a lot. Need/want to revert or change zoom is always a manual zoom in the PRV. I think it would be very handy to have the various zoom methods available in this view as well as the manual method.
  8. Or use contrasting colors. Same but opposite issue with PRV Note Name colors being too dark.
  9. You open the PRV on track 1, you add some controllers on the left side, draw no events in the right pane, close the PRV and reopen it, everything is vanished. If you have many tracks, it's not handy and time consuming.
  10. Yes, like having cc1 controller showing up by default on left side when the PRV is opened. With some libraries, many cc's may be involved in the making of a song.
  11. When you are working on a project with several changes of musical key (such as C to E-minor) it would be great if multiple sets of "snap to scale" settings could be saved in the project. When you are working on such a project, moving around from section to section, when there is a change of key, you have to go into each track in the PRV and set/reset the musical key you want in the Snap to Scale for each track. This is quite laborious! Perhaps such a feature could be incorporated in the Arranger model.
  12. Yes, the grid should continue to show because youre just disabling snap without disabling the PRV snap grid.
  13. Very likely... It's been frustrating me for a long time... This is some new news to me though and I will investigate. Thanks David I did change the binding so I will see how that affects things. I changed it I'm sure, because it wasn't toggling snap in some manner... OK... Why can't I find such a variable in either global or PRV keyboard bindings???
  14. I think we've been through this a couple times before. Per the documentation: "The Piano Roll view always obeys the global Snap to Grid on/off setting, even if you specify an independent snap resolution in the Piano Roll view." What this is saying is that if Global Snap is off, PRV snap will also be off. 'N' is bound to 'Snap Toggle Extended' by default. If you've changed this default binding to 'Global Snap On/Off' the PRV snap on/off status will not follow the Global snap on/off.
  15. OK... Frustated in my search. I do remember seeing such an item (follow global snap) somewhere... But for the life of me I've been unable to fine it in any drop down menu, Nor in Preferences snap settings, so I've also looked elsewhere such as in keyboard shortcuts, but it's not there either... I guess I'm going blind faster than my eyes.... my brain too! Can anyone offer any pointers? Thanks! I'd love for this issue to go away. I do a lot of midi editing... According to the help docs, Note: The Inline Piano Roll always obeys the global snap resolution. The only option seems to be to enable/disable PRV snap which overrides it... Again, I'm still stuck with multiple switches to totally enable/disable snap while in PRV... Maybe what was being referred to was the grid follows snap resolution? Nah, that didn't change it either... It's plain and has been for quite some time on my machine. If there is a way to solve this, I still can't find it. Using the N key only toggles global snap... not prv snap. That requires a mouse click away in the upper corner of the prv where the snap settings reside... ...goin' back to looking more for what I'm missing. I tried adding "FollowGlobalSnap" to the cakewalk.ini with either a 0/1 setting... no change there either.PRV always requires mouse toggle separately from the N key which is set to toggle snap... Still can't find any other options but I continue to search... Somebody please stop me if they know there currently is no way to do this... Thanks...
  16. @Mark Morgon-Shaw and the others Exactly so, many times I too find myself in a situation of trying to remember (most of the time try...) the actual range of notes available to me for individual instruments in use on the various midi channels. Most of the time it varies not only with respect to the "correct" range of individual instruments (violin,viola,etc), but also with respect to the fact that different libraries can also have a narrower or wider range than the one of the "real" instrument, making it even more complicated to remember the available ranges. Also, just last week I was using a sections type library and not only there was this problem but since it had also multi-intruments patches , in the single patches there were in practice 4 or 5 ranges for the different instruments loaded, and the ranges were always different depending on the patch. Using more than one patch translated in a situation that was even more complicated. A further example of how it would be really useful to have a visual feedback through colors and writings customizable on the keys as an additional guide when working directly in the PRV panel on single notes or chords to orchestrate what has already been composed. There are also all the cases in which an NKS keyboard or multiple monitors are not available, for example if you are traveling with a laptop but want to try some corrections or changes on the fly. As you write, this addition would have zero impact for those who are not interested, but I'm sure that if present it would be a function that would be used by many in different ways. A bit like the arranger or expression maps that are born with a purpose but being flexible they can also adapt to other needs than those for which they were designed. Even to me it does not seem a complex addition (on paper...maybe it's on the code...I don't know). Especially if implemented with only the possibility of "manual" configuration " for now, as I explained above, and therefore without having to recover data directly from kontakt through VST, which would complicate the things, it would increase the risk of incompatibility or errors in the event of future updates of kontakt or vst protocol and would also not allow the insertion of "custom" text (very important too as I explained) or assign the same saved configuration to different midi channels with different patch loaded (I think of when changes made in multitrack mode in the PRV panel with focus on active track). I also hope that my little suggestion will be taken into consideration and examined regarding its feasibility for a future update of CbB. Let's hope too maybe in @msmcleod consideration, if he has some time to examine this suggestion and thanks to all!
  17. Turn off your "follow global snap" setting in the PRV - under the file tab. I'm really lazy to make video right now, sorry | or | read the doucumentation how to disable this setting. Everyone working in the PRV should know where to locate this.
  18. Mine are typically the same and I too use the n key to enable/disable snap. But when I’m editing in the PRV snd hit the n key, PRV snap disables and the track is snapping to my global so I must manually disable that each time as well. I work with my snap pretty light so I can usually do my tweaks without doing this, but sometimes...
  19. When I am editing, I typically have the Track View snap interval set fairly coarse, such as one measure, and the Piano Roll View (PRV) snap interval fairly fine, such as 1/16 note. I start with snap enabled for both Track View and Piano Roll View, but they are set to different snap intervals, and they respond accordingly. To toggle snap on or off, I use the N key, which is assigned to Snap Toggle Extended (I think that was actually the original default). The N key simultaneously toggles snapping for both Track View and PRV, even if they are set to separate snap intervals. I never use the PRV control to disable snapping. Whether I am editing in the Track View or PRV, the N key is my single keystroke to toggle snapping on or off. Is this the functionality you are looking for?
  20. It is still currently necessary to enable disable both global snap as well as PRV snap when working in PRV to turn snap on/off. If you simply disable PRV snap, the system reverts to using the global snap. A bit of a pain most of the time for me as I essentially never want to use my global values in the PRV. If I turn of PRV snap, I mean for snap to be off completely. It would be nice. Maybe an option for off vs revert to global?
  21. Hey Folks Because I make so much music I'm all about the workflow, so over time I've added my own macros and shortcuts to my Streamdeck to make up for some things I feel CBB is missing that save me time. The one I use the most is whilst in the Track View is : " Transpose Up or Down one octave " - I made one button for each. Just select the clip and hit the button. Boom. Done. I find this super handy, it works on midi & audio and my workaround is basically a macro of : Process-Transpose- with +/- 12 semitones which then hits OK. It is way faster than doing it manually as it only takes a split second for the macro to complete, but it allows you to quickly try parts in different octaves and is especially handy during arranging for midi strings and pianos etc. or doubling orchestral part that need to be in different octaves. There is already a shortcut for Process-Transpose that can be bound to a key but this takes it one step further by going up or down an octave PS - I know it can be octave shifted in the PRV but I am talking about just in the Track View to save time. Whilst I can happily use it on my own streamdeck I think if this could be incorporated as a keybinding option a lot more folks would make good use of it.
  22. Thanks for the explanation, yes I can understand how it would be helpful over and above the standard articulation keyswitches now. I don't have a fancy light up NKS keyboard but I do have 3 screens so I tend to have any Kontakt instruments open on screen 3 so I can glance up and check I'm using the the right note range or keyswitches. I can't always recall what some notes ranges do on certain instruments as they are so varied and It would be very handy to have them on the PRV if I chose to and having slept on it I think I would use quite regularly . This suggestion would really enhance workflow for Kontakt users such as myself and I am sure there are other use cases for it I haven't thought of , but I also like that it would have zero impact on anyone else and hopefully wouldn't require too much Dev time as it's really just enhancing something that already exists. We should ask @msmcleod what he thinks about this suggestion but it gets my vote.
  23. Thank you all for your interest I usually use the articulation pane function massively and I love it. This additional feature that I have indicated, as far as I am concerned, does not serve as much to indicate the key switches on the piano keys, as you rightly write for that there is already the articulation function, but rather to write down other things on the piano note keys. I'll give you an example, the first one that comes to mind. If you don't have in operation for various reasons (for example because you are outside with the laptop) a lighted NKS keyboard and you are doing notes corrections and insertions through the PRV, it would be useful to have the colored indications of the range extension that you have available for the instrument. In addition, you could also create various piano keys templates for orchestration in which you can indicate instruments range according to the ones used using different colors and also add on the piano key a text indicating which instrument the color zone is (copy this "customized piano roll definition" on multiple tracks and you can use it in PRV multitracks editing too, etc. These are only a few ideas there would be many other examples. You can adapt it to very different needs in a flexible way as you have colors and the two custom text zones (the maximum available in the tiny space) on the keys. We already have this, maybe add a third option that open a configuration panel (as in my screenshot demo example) where you can create save and reload your piano keys settings (similar to the articulation pane) The drum map is a totally different thing, also notes don't have duration but maybe you mean drum map in "note names" this could partially solve the name problem but even this is different from what I proposed, there aren't anymore the piano keys layout and the assignable color zones.
  24. It’s actually easy, but cumbersome... On a track you wish to use a drum map, select it from the midi output widget on the track. To create a new one or edit, there's an option to create in this same list. I’m sure there are plenty of detailed instructions available. You can search this forum or YouTube etc. ...just thinking. I believe you can create a keyboard map. Right click on the PRV keyboard and you will find a list of available keyboard maps. These can be created at your whim as well. They may be more appropriate?
  25. Hi everyone, in the past, a similar request has already been made, however I would like to propose it again with some variations as I think, a new feature like this on the PRV, if it will be implemented, could be very useful. Personally I found myself many times in the condition in which it would have been enormously useful for me to have a customization of this type of the notes pane in the PRV view. First of all to have a quick visual indication of the extension available to me for each VST instrument used in the various tracks, but not only, even an additional personalized text would have allowed me to insert useful additional "reminders" on the individual keys. This customization should be done per single track and not a global. In practice, a custom instrument definition can already be assigned to a single track through the appropriate menu. It would therefore also be a matter of adding an additional "custom text and colors" option to the menu already present. This option should open an edit window similar to that already in use for the articulations in which to be able to enter and save as a preset also, the personalized data. The keyboard notes names would obviously be fixed instead text1, text2 and color would be customizable. Text1 and Text 2 fields should be displayed in different areas of the piano keys and it should be possible to use them both or not to allow better management of the limited space available and to have maximum flexibility according to use (in some cases it would be visually more linear to use only the text1 field, in other cases only the text2, or a combinaltion of both,etc). I think an image can explain very simply what I mean so I insert one as an example. The possibility of entering the personalized data manually would also be relatively simple and fast so as not to require automatic retrieve from the VST instrument (for example I think kontakt note colors) which would probably create some more complications with VST data exchange . Also if we insert manually the data through CbB in this way, we can also insert the custom texts which are very important too. I hope my suggestion will be taken into consideration for a future release. Let me know what you think. For now I thank the developers once again for their work!
  • Create New...