Jump to content

chris.r

Members
  • Posts

    2,872
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by chris.r

  1. in Browse BandLab Projects, when I click View Project Online it opens the Cakewalk Core folder in windows explorer window, am I doing something wrong? edit: happened with no bandlab project loaded, once I opened a bandlab project it worked ok
  2. That's exactly what I'm going to test tomorrow with me on my production PC and my 9-years old son on his phone and it just happened we have one of these USB mics at home laying around. I expect him to get into things instantly with just a snap and then getting bored slowly with time while waiting for me trying to figure out a few things like for example what exactly the stems are, my best bet would be it's the tracks and/or busses, as we don't have that particular feature in Cakewalk (by that name). Or what are the Track Regions in Download Settings (probably just clips) vs Track Mixdown, etc. I asked for the video tutorial more with the other vocalists in mind because I know some of them are so much tech-resistant that giving them a phone connected to wifi into hand and asking for anything more than typing in a text message may result in a crash of the internet if something goes wrong, literally 😂
  3. Definitely going to check it out. I have a couple vocalists with an USB mic-to-a phone, that are waiting for a collaboration. I hope someone can make a short video tutorial for such scenario where one person creates a project on the phone and records just a vocal track (maybe creates a simple click track first there) then invites a producer to collaborate, and then the other way around. Any takers?
  4. Same here! I'm right now on a project where I was wishing for an offset to the whole tempo line and my thoughts were exactly 'not going happen'
  5. I think the confusion is that when you lasso select ordinary automation nodes, they do actually become available for cut, copy and paste operations. However, when you lasso select tempo nodes, they only become available for delete operations. In this respect, tempo tracks differ slightly from standard automation lanes. Maybe you could make tempo nodes that have been lasso selected also available for cut, copy and paste operations. The time range can be derived from the time of the first selected tempo node to the time of the last selected tempo node. Confirming the same. I don't think that copy/cut/paste operations for just the tempo nodes, that are lasso-selected, is an available feature in Cakewalk at all. I agree this could be very useful.
  6. I'd like that idea of copy/past just the lasso-selected tempo nodes. But on my system I can only confirm that lasso-selecting (right mouse click) just the tempo nodes don't make them available for copy/cut/paste operations at all. What's weird is that I'm getting unexpected results when trying copy/paste lasso-selected nodes of a normal volume envelope in an audio track: I lasso-select a group of envelope nodes and copy, but then only the last node of all selected gets pasted. I'm trying getting familiar with working with the envelopes in general here, so I beg a pardon for this. EDIT: actually I was wrong, in a normal volume envelope I can paste just the last node regardless of how many I select, if I select a few and without the last node than nothing gets pasted at all. Don't know if it's a bug, I just discovered that behavior while learning how to work with the tempo track envelope and comparing it to a volume envelope on the occasion.
  7. Thanks. We can't exclude prochannel effects in the plugin manager, can we? Yes, both the CA2A and PC2A do appear on the list simultaneously. I don't think we have any way to exclude one of them, well I couldn't find any.
  8. Ok I checked and there is no trace of any PC2A plugin in my 'Shared Utilities\Internal' folder so I guess that the prochannel version of my CA2A resides somewhere else under different name, sorry for confusion. I assume then it is safe to install the new EA and that the new PC2A and my old CA2A will both appear independently in the PC?
  9. What we do if already having CA2A+PC2A? Is the PC plugin overwritten or should we disable the old one first in the plugin manager?
  10. Another huge update, congrats , the new tempo offset is a biggie! Glad to see PC2A, wish we could see the Concrete limiter in the future, that's the one I'm missing from the old days (sorry, had to say it)
  11. IIRC you can scan plugins from the 2 locations and then change to a new location and scan plugins there, it will keep previous plugins.
  12. That means that the loop is not Groove-Clip enabled. You need to right click on the clip first and choose 'Groove-Clip Looping'. Also it works best if the loop is just a few bars long. I can't tell how well it can work with a song length loop, may be fine if you manage to count the proper amount of beats. EDIT: probably clicking 'Loop' button in the LCV (to the left of the 'No Slice' drop-down) will work too
  13. Set this drum loop to groove loop first (right click on the clip and choose Groove-Clip Looping) then open it in the Loop Construction view (right click View > Loop Construction) and set the correct amount of Beats there. Now you can simply slip-drag the clip edge (without Ctrl+L this time) to make it play in loop.
  14. Shame they discontinued the VX series keyboards.
  15. I recon doing the same in the Loop Construction view in Cake.
  16. Someone having already his/her full version of AT5 and wants to swap the serial# for something else?
  17. Lasso-select with right mouse button is not intuitive at all, I've got adapted to it with time (it's extra annoying in the prv) but then it always pays back when I lasso-select with right mouse button in Windows' File Explorer etc.
  18. Aaaargh... even on my UVI account the changelog still says 3.0.17. No way to know what's got changed.
  19. Preparing space for 12 pages of outstanding deals on my desktop tomorrow 👍
  20. +1 for this and I wish similar smoothing out/balancing/averaging the tempo changes (!) but that's another feature request, I suppose
  21. That would be huge, though not enough for for some, me included. I'd wish for example, for every controller line, somewhere on the left, a folded list of all available controllers, where we could freely enable/disable each cc#, to show only those we'd want to work with on that line, and for that moment (for example we could get two lines with separate controller sets for Osc1 and Osc2 of a synth or two separate drawbar sets of upper/lower keyboard - to compare/edit with reference to each other and notes), AND enable/disable a chosen cc#(s) for overwrite-recording (similar to write-enable an envelope). That's just top of an iceberg what ideas could be added to the editing toolset, some of them, really basic, much missing. But like I said, I don't see midi editing anywhere on the top of requests for most of the userbase, unfortunately.
  22. The piano roll section for editing controllers is fine if you're dealing with just 2-3 controllers, if you have to deal with 20-30 then it looses sense. I just opened one of my projects with only one instrument... the Hammond organ . And instantly remember the hassle when it comes to edit the controllers. If you're going to record the organ track properly there you can easily exceed 30 of them in one track, 2x9 drawbars for both manuals plus at least 2 for the pedals that's already 20, then there is expression pedal which in some cases is moooving constantly the whole track populating it with never-ending waves of cc#11 events. Plus some intermittent leslie switch movements, drive, volume, click, V/C, rocker switches and cabinet settings... many of them drawing at once in the prv! I mean, just working on the expression pedal alone in prv is a grind, not to mention if you'd want to overwrite just a single controller events line, for just a part of the song. There are no tools. I can't see how working on orchestral tracks would be much different, except there could be even more hassle in big projects.
  23. From a few sources I did see that the AAS guys are no longer in love with Cakewalk, don't know the reasons. Better let them know the crash happens in all DAWs (I'm sure you did).
×
×
  • Create New...