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


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

  1. Edit > Select by Time operates on tracks selected in the track view which can be more than just the one you have enabled for editing in the PRV, depending on how you switched views. When I want to select a time range in PRV, I usually just right-click and drag to lasso with or without snap enabled which will limit the selection to the the track that currently has focus in the PRV.
  2. I'm sorry not to have stated clearly enough the problem. It is the operation found (in track view) under the "Edit" menu: "Select", "By Time" that gives me difficulty from the piano roll window. The way "select by time" works is to give a pop up window allowing entry of bar numbers for start and end of the selection. I use the shortcut key FROM A PRV WINDOW very frequently to select a set of bars often far different than what is visible on the Timeline (which is why selecting by clicking on the timeline is not very useful). It is this operation, or some usable work around, that I'm hoping to find. Some way to select a group of bars for a limited set of tracks, those in use in the PRV .. I don't have an active version of the old Sonar right now, but I'm pretty sure it worked this way during those days: from within a PRV (which then could be set to include ONLY certain tracks) select by time gave the selection for just those certain tracks.
  3. You might want to read up on the "Auto Focus" & "Auto Lock" button functions in the top right corner of the PRV. I cannot recreate your issue when those are properly adhered to.
  4. Funny this topic came up because I’m not liking the new layout at all. It never puts the last projects in the cue. I’ve ended up opening back up versions by mistake. I can’t put my finger on what it is that has made this worse than the Cakewalk version and I’m one to slowly get used to new things but it’s been over a month and I’m still hating this thing. The start screen and the inability to make the PRV background white are my only 2 complaints so far.
  5. EDIT: Not an issue. Thought I had restarted Sonar (as it says "Requires Restart"), but I may have just closed/reopened the project. After a complete Sonar restart the note blobs scale as well. Nice! Noticed one glitch with the Custom Scaling. When you go above 100% (at least on my 3840x2160) the PRV note names get cut off. Here is 100%: Here is 105% - the top of the note names get cut off. Maybe the note blobs need to scale as well?
  6. Exactly. Cakewalk notation view is more for using as an alternative to PRV for composing basic midi driven music. It is by no stretch a full featured scoring app. Just like the Video feature is very basic as well. Use proper dedicated software for those tasks and then use Cakewalk for what it is designed for.
  7. I think that KeyAft events will become more important. For example, we build pipe organs and our new design is a smARTvalve which allows the pressure of each single pipe in the organ to be controlled individually. In midi V1, KeyAft is the only controller we can think of that can hold the information. The above suggestion of Promidi seems the way to go. Once you show the KeyAft information in the PRV, the "Key" selection should automatically switch to the selected note. As for the comment of msmcleod that the KeyAft information would become ghost information when the note's themself are deleted, I feel that KeyAft information is only available during a keypress from note/on till note/off, so it should be considered an integral part of that note and be deleted with it. All considered, I think that it should be very easy to implement this option in CW, as it is no different compared to the controller part: Controllers (already in place and working flawlessly in CWs PRV): select the control number, the control value is showed in the pane and can be edited with all the different tools. KeyAft (not implemented in CWs PRV yet): select the key number, the KeyAft value is showed in the pane and can be edited with all the different tools. I have no insight into the code of the CW program, but with me doing a lot of programming myself, it seems that it could be done in an hour, just duplicate the "Controller" item and add it to the list as "KeyAft", and re-associate the Controller-number to point to the Key number, and re-associate the Controller-Value to point to the KeyAft-Value. As for me, I'm really in need to have easy access to the KeyAft so that I can manipulate it with ease, so adding this function would be greatly appreciated.
  8. If you have 2 midi notes overlapping on the same key in PRV, when you try to select just the top one, it also selects the one underneath, unless you click on each note one at a time. (This is when you hold right mouse click and drag to mark multiple notes)
  9. Exactly, it just doesn't make any sense to me. I also found out that if you have stacked notes in the PRV and you mark all of them and you want to transpose them up or down, you can't select multiple notes by marking them, because when you do, it also selects the ones below that I didn't want to move... CbB seems to have a lot of silly things like this spread throughout, and it's messing too much with my workflow that I will have to look elsewhere to do my composing. I really wanted to get into using it as my daily driver, but it just keeps throwing shade at me, when I'm trying to do simple things. It's not really because I don't know how to use it properly, it's because I'm trying to do something and the program gives me resistance and says "Nope, I see what you are trying to do, but you will have to do it in a less intuitive way, at the expense of being pulled out of your creative flow".
  10. The way midi tracks display when there are overlapping clips has been annoying me forever. And CW just loves creating them when you play around editing in the PRV long enough and start copy/pasting or ctrl-drag-and-dropping, or whatever. I’ve never once wanted overlapping midi clips, but there ya go. I’m used to bouncing them back to a single flat clip and re-splitting them at my markers (and losing my edited clip names in the process), but yeah, if the Track View wasn’t lying to me by saying there’s no notes (or fewer notes) where there blatantly are some, I probably wouldn’t care about the overlapping clips thing. —- FWIW, my use case is “I never record any midi; I compose & ‘type it in’ in the PRV.”
  11. Absolutely. When I first tried Cakewalk I was 100% midi editing in DrT KCS event list. As we know Cakewalks event list is limited and the PRV is for the details. I think it took me a few years before I finally gave in and started using it. My event list workflow was over 15 year old. So it’s probably a good thing Cakewalks event list sucks as it forced me to learn to use a much better tool. And my overdub preferences are directly descended from the days of analog recording gear. Bad take! Record over it! Why would I want to keep a bad take? Workflow habit that is 40 years old.
  12. When you read these ideas you realize how we all have such totally different workflows. I hate it when I start working on what started as a pure midi file and find out the default setting of comping is turned on. All my templates are Overdub mode. Just now that happened to me and when I opened PRV to edit my 10 th and final take only to find PRV a total mess of notes! All 10 takes were there stacked up. It was easy to open the lanes and delete all but take 10. But it super annoying to me that the default is this instead of Overdub like most DAWs. Funny Cakewalk Next default is Overdub.
  13. not sure, but not an issue for me. when i open the PRV i see all the MIDI on the track regardless of number of clips or takes on that track. so it's later that if i know i'm going to copy the MIDI onto another track, i'll select the clips, bounce to clip (almost instant) and continue.
  14. Yeah, what John said. I upgraded to Melodyne Studio several years ago, and I don't regret a cent of it. Best money I've ever spent at the DAW Thing. The ability to work with multiple tracks simultaneously is so critical. I use it on everything I actually record, both vocals and guitars. (Everything else I do in PRV.) Vocals: adjusting lead vocals, and tightening up timing and fixing (or creating new) harmonies. (You can get away with a lot on backing vocal tracks.) Guitars: tightening up timing on multi-guitar rhythm tracks and leads, cutting out any noise between 'chugs', and occasionally tweaking a lead note. I record guitars dry and do the amp sim in-the-box, so even if any artifacts are introduced, they get crushed by the distortion applied afterwards.
  15. I used to do what you are doing. I don’t look at the meter I use the peak and hold numbers. I worked in small sections which more or less are one line of the lyrics. I have the G shortcut key to open the Gain dialogue. I would drag over the quiet parts and add a few db of gain. Play the part and observe the meter peaks. It was more of a visual editing process looking at the waveform to find quiet parts as well as listening to understanding the lyrics in the mix. When done I would print the track by exporting it, then I learned about bouncing to clip. This was a lot of work! Now it’s easy. I discovered a levelling tool in Melodyne which is brilliant and became part of my new workflow. It has 2 sliders one to bring up quiet parts and then one to lower the loud parts. It’s percentage based and I’m using around 70% on each. The results are I can toss the compressor and limiter in the trash bin. Well. I still use them as watchdogs. Im not sure at what version level of Melodyne this is included as I had it in the Editor version and I just upgraded to Studio. It’s on sale for a few more days if you need to upgrade. Best $99 I ever spent. And now I can work on harmonies all in one view. So all the tools you need to work on vocals are right there just like you’re working with midi in PRV. If used correctly there’s no noticeable artifacts.
  16. In PRV, holding the Alt key invokes the Scissor (note lower half) & Eraser (note upper half) tool cursor which are used when Left-clicking. However, holding the Alt key when Right-clicking Moves/Copies notes between tracks in PRV, but still uses the same cursors which is confusing because you're not sure what's going to happen next. Is this unavoidable because of the Alt key?
  17. When 2 clips are linked, any changes made to one automatically changes the other so you don't have to edit them separately. In PRV I often want to edit a series of notes in a linked clip, so I right-click lasso them, then copy & paste to a new location. At the new pasted location is where adjacent notes will disappear for no reason. Lasso selection is what causes this. Not sure if that's intended. Obviously single notes in linked clips don't need to be lassoed. But lassoing several notes is much faster than Shift+click selecting them individually.
  18. It doesn't work if auto-focus is enabled in the PRV.
  19. Right. There are times when it works as intended and then moments when it doesn't. Usually after a long session of editing. The full length clip thing happens sporadically at will. I could blame it on my version of Windows, but these issues have been with me forever. I prefer working full screen but may try splitting TV and PRV so switching is faster.
  20. You need to start by ensuring both tracks are enabled for editing in the PRV by swiping or Ctrl+clicking their track numbers in the PRV tracks pane . The first track you click will get focus (track name and number highlighted white) and be the target of a paste. You can change the focus by clicking a different track's name in the PRV tracks pane but you need to leave the track nmbers selected so both source and target tracks are showing. I'm not sure about the full-length clip; that may be related to the state of the Non-Destructive MIDI Editing option, but I can't say I've ever run into that. All that said, I generally prefer to do track-to-track or lane-to-lane moves in the Track View because it's easier to control and confirm exactly what you're getting.
  21. May have mentioned these in the past but these 2 issues have persisted for years thru every version of Sonar/CbB. I don't change any settings and they seem to happen at will. Using Ctrl+C & Ctrl+V 1. Sometimes pasted notes don't go to the intended track. They (1) end up on another track, or (2) disappear completely even tho "Undo Paste" is in the Edit list. Normally I can select the target track with the PRV Track list, but not always. When that fails, sometimes I have to switch to Track View and Select & Focus the intended track for it to paste there. Sometimes even this does not work and the note simply doesn't paste. 2. Pasted note clips should only be as long as the notes themselves but about 50% of the time they will paste with a new full length clip. Is this intended behavior?
  22. I wasn't clear (and was using incorrect terminology - sorry) about having multiple windows open (Tracks, PRV, Staff, etc.). I should have said "instances". While Console, PRV, Staff, etc. can all be open/undocked/viewed at the same time, what I was trying to convey was that it would be great to be able to open multiple instances of any/all of those windows. Examples would be 2 or more instances of the Console (1 with Tracks 1-12, another with Tracks 13-25, another with just buses, etc. - like in my original post). Or maybe multiple instances of the Staff view (one with piano, one with bass, etc.) - so, if you have the screen real estate, you don't have to toggle between them. Multiple Console windows would probably be most useful to me, but multiples of the others would probably be useful to others as well. Sorry to all that I did not explain clearly/correctly - my fault - still learning... :^)
  23. Yeah, it's a bit confusing. Especially when you have a filter on the PRV, and then you change what's visible on the Track View it breaks the filter and you have to run the filter again. But that's besides the point. I think you and I have both demonstrated that the current setup is confusing and isn't even working the way it was initially intended. What would make so much more sense would be to have the Track Manager be consistent and handle the visibility of all of the windows containing tracks, instead of having it work one way for two windows, then another (confusing) way on another window.
  24. The PRV has it's own filter button. AFAIK this is essentially a separate feature to the Track Manager, although it should respect the existing hidden status. It's not really about keeping the PRV in sync - it's a different beast to the Track View / Console View, as it's already filtering out audio tracks / aux tracks / buses - what it should be doing is applying its filter on top of the currently visible tracks. What isn't clear is what takes precedence... it seems to be taking it's cue from the Tracks View, which makes sense. But if the track is hidden in the Console View, but not hidden in the Tracks View should the track still be visible in the PRV? You may of course be just seeing a bug in the PRV filter in CbB. The Track Manager button required a bunch of reworking of the code behind the scenes - some of it got backported to CbB as it did fix some bugs, but it didn't get everything because the feature itself isn't there.
  25. I don't know if access to the Track Manager was an issue, as H and Shift+H work great (haven't tried it from the console yet tho). If the button could be added to the PRV as well, then that would be awesome!! And to keep everyone happy, a flag/checkbox could be added to give the user the choice of keeping the prv in sync, just like the option to keep the console in sync.
×
×
  • Create New...