Keni

Another new benefit I'm finding related to this... When snap is disabled, the grid continues to be visible. Excellent! I use them as visual reference points while editing and always disliked how they disappeared when snap (set at grid follows snap) was disabled... This too will be a help to me. I hope it's not just something snagged due to the change of shortcut binding? I only unbound the single entry...

OK... That sounds easy... Doing it now! Thanks again! Excellent! That worked at last! I now remember that in some update N got assigned to something entirely different. That's when I reassigned it to N...

Can anyone suggest a place I can download the default bindings for CbB? I have only old Sonar bindings saved not thinking when I installed and updated to my customized bindings... Foolish human! ?

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???

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...

Thanks Will... I'll find it. I even remember seeing that setting before...

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...

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?

I believe decent sampler has some current issues . I’ve run into a number of problems with it myself. The last straw was when it prevented the project from opening. I’ve since stopped using it.

I couldn’t agree more! ??

Thanks Pal! Interesting little program

That’s a thought. I'll see if I still have any other DAWs that allow vsti (entry level frequently as I don’t ever use these DAWs) Thanks for the idea...

Thanks Wibbles... I thought of that but I’m avoiding it as long as I can. This is an odd duck synth being long discontinued so I’m apprehensive...

Thanks Tim... I tried that immediately. Still the same. Same in blank new project...

I've been using this vsti for a long time... Obvious by it's age.... ? I have just noticed something peculiar that has changed. It was not like this previously and I know of no updates or timers in the app... Everything is working fine, except for visual representations. The knobs and switches never move though you can hear the changes that are being done and they continue to operate. So... My question is does anyone know of some crazy timer or switch etc. that may be causing this? Just now thinking could it be a change in a C++ update somewhere? <sheesh> new strangenesses never cease to occur! ?

Yeah, i realized drum maps was wrong and added the keyboard note names afterwards as that was what I was really thinking. I wasn’t expecting to exactly replicate what you were asking for, only to think of work arounds..

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?

Couldn’t you use a drum map to accomplish this?

Not gonna happen, but thanks.

Thanks Mark... I'm surprised it wouldn’t be easy, but I understand. As to clips belonging to track. I understand that too, the lanes tool is a method of selecting which clips are active on the track. I’ve always known that. Some of the problems here are (I believe) somewhat syntax if that’s the right word. My calling them sub-tracks was not to imply they are active tracks, only information easily exposed as track if selected. My idea was simply a location to harbor fx which would attach/insert to any active clips on that lane. Of course there are other ways to accomplish... That doesn’t lessen it’s value, only it’s immediacy/necessity. I have no problem living without this as often as I ever need clipfx to begin with. This was an idea that I mentioned which got such harsh responses it provoked me into continuing... Thanks again...

Everyone’s entitled to their opinion . A rose by any other name ...

I know you see it that way. I still disagree. I don’t use lanes as tracks. I do advanced comping within them. I’m surprised you don’t see that. Lanes contain clips all to be used with the common processing of the track with the exception of tools such as clipfx which are bound to an individual clip. This idea is simply an extension of that. I don’t use folders. Using separate tracks is load creating. I’ve been working this way for 20 years... I use tracks as tracks and lanes as take information feeding the track.

Not to derail this thread, but... Absolutely! In this forum I have posted regarding those issues regularly since the change from layers to lanes. There was a little improvement initially but now years since any more "fixes"

This topic is difficult it seems. I was initially very disturbed when we went from layers to lanes. I know many people think of lanes as multiple takes of a live performer, but often it is purely a place to jigsaw selected clips for use as a single track. Cake has many cool features for doing live performance tracking and comping. I currently have jo need of those tools and rarely use "comping mode" though I constantly use lanes to comp my selections. In the process of doing this, after some chopping, some clips require some extra, special processing. Hence, clipfx. All that I was suggesting is that it would streamline some work where clipfx could be assigned to multiple clips simply by placing them in a common lane and using that lane for this exclusive purpose while still sharing the track's fx. I spend most of my editing time inside lanes making things happen. The logic gets more complex and load heavy doing this with multiple tracks so I find clipfx work great and this simply an expedient extension. No great issue here as I can easily live without it. I pray to the great god of Cake programming to solve my zoom/display issues one day soon as this does cause me constant difficulties.

Though I understand their' meaning, I don't necessarily agree. Without being privy to the actual code to know how everything is accessed, it would be futile...