Jump to content

Lord Tim

Members
  • Content Count

    464
  • Joined

  • Last visited

Everything posted by Lord Tim

  1. Can confirm that BBCSO Core works the same re: not being multitimbral, which surprised me a little bit at first. It's a hell of a resource hog, but I've taken a leaf out of the book that a lot of virtual instrument composers do and create new tracks with the most common articulations I think I might need for each instrument, rather than playing around with keyswitches. I don't do all of them, and generally have a "Aux Articulation" track that I set up with something uncommon, but it's a very fast way to work, but very much at the expense of system resources. (Needless to say this is a VERY BAD IDEA on my retiring M620 dual core machine with just 8 gigs of ram ) From what I could see in the interview that Jesse Jost did recently, articulation maps will make short work of fiddling around with keyswitches, which will be wonderful. I've always disliked using keyswitches and trying to remember what was assigned to what and where, so having an Arranger-like track with it written there it front of you will be, well, a Cakewalk. I'd be surprised if there isn't already an articulation map available for BBCSO somewhere that could be imported or converted.
  2. I think it's common knowledge by now that Steve is really a rogue subroutine written by Greg Hendershott that somehow became sentient, and learned how to post replies on the forum.
  3. Roughly around every 6 months, so this isn't typical. I'd make sure you're updated to the latest version, then follow the instructions here: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.32.html#:~:text=Double-click the BandLab Assistant,desktop to start BandLab Assistant.&text=Click the Apps tab.&text=Under Cakewalk by BandLab%2C click,being activated by BandLab Assistant. That *should* sort it out.
  4. Lord Tim

    Had Enough!!

    The only time this has happened to me was when I had a disk failing. I've been using Cakewalk stuff for decades and never had this happen other than file corruption on a dodgy disk. I can definitely say that it absolutely SUCKED losing files and having to rebuild things before I realised what was going on, however. 😑 Like Bill said above, I have to ask though, who did you ask for help with this? You only have one post (the OP), which means it hasn't been anywhere here on the forum, and there's a LOT of very knowledgeable and helpful people on here that could have given you some great advice. I'd start with a disk scan first and work backwards from there. If that comes up clean, I'd still suggest troubleshooting with a different disk for your project files to rule that out entirely.
  5. Essentially what you have here is the equivalent of walking into a fully kitted out recording studio. If you've never been in a studio before, how could you possibly expect to know how the patch bay worked, or how to set up the correct gain structures or any of those kind of things without learning how it works? And even if you are fairly well versed with a particular recording studio, walking into a different studio with different gear and set up puts you almost back at square one. Cakewalk is a professional program that gives professional results if you learn how it works first, which is why it can seem not user friendly - any complex thing like this must have the basics learned first. With that being said, I've helped a few people get started on this who have tried out other software packages in the past and after the initial getting to know how it all worked period, they all found things extremely easy compared to a lot of other apps. Like Millzy mentioned above, you can hide quite a lot of the more advanced stuff to concentrate on the things that matters to a novice user. By default, Cakewalk guides you to using the Basic workspace, which is far less busy and shows far less of the stuff that a seasoned user may need. If you're not set up to use the Basic workspace, you can learn about them HERE. But for obvious mandatory things like recording, opening and saving files, choosing instruments, etc, this is something that every DAW does more or less the same but also in their own way. You'll find a lot of fantastic tutorials, especially for new users, in the Tutorials section: https://discuss.cakewalk.com/index.php?/forum/35-tutorials/ THIS THREAD especially is a great place to start. I'd wager that after a couple of hours going through this stuff and trying things out yourself, a lot of the "what am I even looking at?" factor will just fall into place, and you'll be able to cruise along at your own pace for most things you'd want to do.
  6. I'm running a 49" super ultrawide here so this kind of thing would be super useful for me too. Ideally, I'd love for the UI to be similar to, say, the Adobe suite where you can dock anything pretty much anywhere you like, even as sub windows to other windows.
  7. Try shifting the hue. It's not a perfect solution, but you can get some pretty great results in a lot of cases.
  8. I think what's there is pretty good already (and very much agreed - too much info jammed in your face actually does the opposite with making people feel comfortable), but we've seen a bit of confusion around the place with some initial set-up and people using the wrong driver models and that kind of thing. I think the actual onboarding isn't bad at all, but perhaps a "want to know more?" sort of link to a short video / doc to help people get the most out of an initial install? Like Jim says, the Arranger docs were sensational. It'd be awesome to have a visible but optional link to something like that get started, IMO.
  9. Workspaces definitely went through a bit of an evolution since they were introduced as Lenses and I do think it confused people since Screensets also existed and they seem like they're more or less the same thing on the surface. I think getting a user to check out the docs to see if that can get them to the end point (ie: uncluttering the UI to focus the tools and workflows to the task they want to achieve) is still a valid suggestion, but yeah - I also tend to agree that it would be nice to see a series of docs/videos similar to the Arranger stuff to help people get the most out of them. The Arranger docs were excellent! Just FYI though, when you first install CbB now, you get an onboard dialogue that gets you to enable a workspace that suits your needs, with an explanation of what it is. Basic is suggested for new users. I'm sure this could all be refined more, though! I think a really detailed "Getting Started" guide would be a good idea for this kind of thing. There's a couple of great YouTube channels out there that do some good ones, but having something during the onboarding process or linked to in help would go a long way, similar to you being guided when the Help Module is open. Advanced users don't need that, but new users would find that invaluable.
  10. I do use it, but not often. It can be really handy for a client if I'm doing different versions of a song (say, instrumental mix, full mix, or variations of a mix, etc.) and I can basically set and forget and let it export at the end. I haven't tried using it to transfer project settings though - I normally set up a temporary Track Template for that, but I think this is something I'll explore a bit more now it's on my radar. Super useful tool!
  11. Check out Workspaces in CbB - if you're finding the UI too busy then you can show as much or as little of it as you like, and set up a specific Workspace to hide everything except for the controls you need to record. Best of all worlds!
  12. Sorry, not overly helpful to your problem, but I can confirm BBC is working as expected here with no crashes. Running the latest build. If you can get a crash dump and send it into support, they might be able to trace your problem.
  13. A good parallel to what Mark is saying here is how I release my music. My main act LORD is a commercial band. We sell product that brings in money to help us make more music and create more merch, etc. We also run our own independent record label and we have a half a dozen acts on it, but LORD is the flagship artist that subsidises some of the smaller artists that don't pull in a lot of money, but ultimately they're still out there getting publicity, which directs more traffic back to our label. Additionally, I've occasionally released personal project songs for a "whatever you want to pay, even nothing" payment model. If I get a coffee out of that stuff every other week, I'm more than happy. The point is just to do it because I want to, not because of any commercial reason. But that said, just because I'm allowing this to be free, it doesn't mean that I'm giving up the copyright for the writing or replication / duplication / distribution rights at all, in fact I'm happy to go after anyone who violates those terms, even though I'm absolutely fine for them to have as many personal copies of those songs as they like. From a business point of view, giving stuff away makes no sense, but we've had people discover our label through this stuff that have gone on to discover our commercial acts, become big fans and bought the entire back-catalogue, so even free stuff has value. I'm all for open source stuff (or collaboration / free to distribute music for that matter) but it doesn't automatically mean free isn't still very valuable as your intellectual property.
  14. Hilariously, Googling "does Cakewalk by BandLab install adware?" brings up this thread, so it's very meta! 😛 But on a serious side, I think we've gotten to the bottom of some really important questions here. We now know Cakewalk uses unleaded code. Finally! (Also, this is actually a really good thread for people with similar questions about the addons, registration, Bandlab Assistant, etc. so I think it's a really positive thing we all had this discussion. )
  15. Bandlab Assistant is there as a way to manage downloads and deliver updates, as well as activating Cakewalk. Like a lot of people have mentioned, it's almost the defacto way a lot of companies are providing their products now, rather than just sending you to a website to get an .exe file. Why? First, it allows Bandlab to know how many people are using the product. This is a no-brainer thing for any business, and similar to what would happen if you had to buy a product from a web store. You would have to sign up to buy it, the company would know there's another person using their software. This also gives them the option of contacting customers directly to let them know about future news or products. It's just fundamental business sense to know who your customers are and how many. Secondly, it allows Cakewalk to receive frequent updates. The pace of updates and fixes since the pre-SONAR days is just staggering. There's no yearly wait between versions, major release style features are added several times a year, bug fixes happen every other month... it's just amazing. MANY long-standing bugs from years ago are being addressed constantly - just a quick scan around the forums will show you that. But seeing as the program is being updated so frequently, and the dev team is a smaller more focussed team now, it doesn't make sense to have people on outdated versions of the program when it comes to troubleshooting. That "annoying bug where X things happens when I try to do Y" in a version from 8 months ago may have already been fixed in a more recent update. No need to send tech support on a wild goose chase or fill the forum with angry "IT DOESN'T WORK!!" messages if you have the latest version that's already been fixed. Thirdly, it's used for Activation. There's really nothing stopping anyone from being "clever" and uploading the Cakewalk installer to their own software site. If there was no activation, you're at the mercy of using outdated software, or possibly software that is indeed bundled with unwanted add-ons from that site, or even malware. Plus, you (and Bandlab) lose the benefits of the first couple of points. Activation requires you get this software from the official site, and it's tied to your free account. To make sure you're using a current version, every 6 months or so, it'll check to see if your activation is current and prompt you to sign in and get an update if need be. It's not required to run Cakewalk day to day, but it's necessary to make sure it's all working well. Plus, you also have an entirely optional network to transfer audio to other users, upload to to a service similar to SoundCloud and have a fairly big loop library if you choose to use Bandlab's other online services. Any or all of those things can be entirely ignored but they do add value to the service if you want them (much like the add ons that you don't need to download to use Cakewalk - why get them if you don't need them? But if you do, it's nice to have the option.) You've heard from a lot of users now, plus 2 of the developers (including the CTO) and I think it's pretty clear by now there's no ulterior motive for anything you might be concerned about. The forum would be full of people freaking out if so. There's not really a lot else anyone can say at this point. It's a full-featured professional DAW that used to cost hundreds of dollars for each new version, but is now offered for free, with constant updates and fixes, and in return Bandlab just want to know who is using it and that it's current to save chasing ghosts. You basically have the option of choosing to accept all of this and using a great program for free, or not, and finding that it's not so different to other paid products out there. Good luck!
  16. Ultimately NONE of those add-ons are required to run Cakewalk as a professional DAW. They're optional because everyone's needs are different. If I'm not planning to edit themes, why would I bother grabbing the Theme Editor? If I don't plan on doing sample replacement on drums, why waste time and space grabbing Drum Replacer? It's not really that complicated. The best news is that after you're up to speed with everything, spent time in this forum learning about things or going through the help docs, and you think "hey, you know what? Maybe having X add-on would be a useful thing for me after all" it's just a couple of clicks away. My advice is just grab the main program and not worry about anything else until you need it. I myself find those add-ons super useful, but as I said, everyone's needs are different.
  17. Well, this fixed every issue I came across so I'm pretty stoked! Great work!
  18. I wouldn't be getting it from any 3rd party places; it's included in the APPS section of Bandlab Assistant. Follow THESE steps, but choose Theme Editor instead of Drum Replacer: https://help.cakewalk.com/hc/en-us/articles/360003456374-How-To-Install-Drum-Replacer
  19. This seems related to the stuff in this thread, that we were trying to help @Ben Staton lock down: Definitely can reproduce fairly reliably on my crappy workstation but not at all on anything else. It's a tricky one!
  20. Yeah, so selecting multiple tracks and doing Collapse to Lanes would basically move all of those tracks to a single track (the top one of the batch, maybe?) and stack them all up in lanes, and the reverse would be selecting a track that already has Lanes in it, and doing Explode to Tracks and every Lane is extracted onto a new single track, either using the originating track as the first track or creating a whole new batch. I do like the idea of Send to Track though. Any or all of these ideas would be amazing additions! There's a few things you'd have to factor in, like if it involves effects or softsynths, if there's any routing to consider (Aux/Busses, Sidechains, etc.) so I'd imagine it wouldn't be a "Hey it would be easy enough if you guys just..." job for the Bakers.
  21. Interesting. I'm running a 32:9 super Ultrawide here myself, and my crappy machine barely has the guts to drive it properly (most machines I have eat it for breakfast with their video cards). What kind of monitors / video cards does everyone have here? It might just come down to things not keeping up while pixels are pushed around a bigger screen .
  22. This all looks amazing! Can't wait to try out the new arranger stuff especially when I get a break next.
  23. Yep, I had a more expanded version of that already up... uh... somewhere? (I'm sure a search will find it, it was a fair while ago) Basically it was Collapse to Lanes and Explode to Tracks, which would work as you would expect by those names. That would be a MASSIVE time saver for me!
×
×
  • Create New...