Tezza

Did you hit the monitor button on the track with the instrument, it's in the track header next to the record button..

I think it is just the instruments that are missing to move Cakewalk up the popularity ladder a bit. In my view they should be given priority next. When I read the Cakewalk splash page, I agree with most of what is on there, there is a lot to like but then there is this: -------- A World of Instruments Whether you’re a songwriter, producer, or composer, Cakewalk by BandLab has the instruments you need to build your production from the ground up. ------- It does have instruments but I would regard them as basic, it doesn't have a Kontakt like Instrument player, Cubase has Halion, Studio One the Presence instrument etc A DAW needs it's own instrument player/sampler. I think in Sonar that was Dimension Pro? That also really adds a lot to the marketing side as well. People know then if they get the DAW they can make good sounds. The current instruments don't look very modern and are limited. If I didn't already have Komplete Ultimate, I probably wouldn't and in fact couldn't, make Cakewalk my primary DAW. I have 9 DAW's on my computer at the moment, just looking at them before upgrading the computer. Before I was using Studio One primarily but I am now using Cakewalk and migrating some projects over to it. I now am becoming more familiar with it and do everything in it. I like the interface much more than the other DAW's. It's a size thing, everything in Cakewalk is easier to see, the big EQ slideout and the Prochannel stuff and the piano roll etc, I could go on but the aim of the thread is whether Cakewalk is gaining popularity with Bandlab users. I don't know about that but in terms of popularity with other DAW users I think that just adding an instrument player of some kind would be a good start. Then everything advertised on the splash page would be correct and then you would also have even more features to market on that splash page. I think that the idea people are not using the product because of bugs/instability is absolute rubbish, I don't find it any different to other DAW's, they all run stably on my system and they all have little quirks here or there. I don't like the frequent updates though, this seems to be something unique to Sonar users, who expect one a month and think that is a good thing. I think it's a terrible idea. It seems sometimes these updates break things and another comes out just as quickly to correct it. Other DAW's you get 1 every 3 to 6 months or so. I prefer that. Perhaps there is a Beta testing section needed in the forum somewhere either visible to the public or only to logged in members where these updates can be tested more widely by some users before release.

Congrats! I used the Dell Precision laptops for ages for video editing, they also can have 4 hard drives, 2 inbuilt ssd, 1 M.2 SATA and then you can swap out the DVD drive for another SSD. Not the superfast ones as in your Alienware. I don't know if they still even make the precision's today. Being able to have multiple internal drives in a laptop cures one of the drawbacks of using them in the first place. Even just having 2 would be sufficient these days for a music editing laptop but 3 would be the standard and with 4? well now your just being spoiled!

You could go for the 32 or 80 ohm version, with the 80 you get the same cups as the 250 but the lower ohmage, it's essentially the same as the 250 but only 80 ohms. The 32 ohm version is actually a different headphone, it has different cups (non velour) and there are also other differences I think. The cable or cable ends might be different It's worth checking this out. I used 60 ohm headphones with my 2i4, headphone volume was never a problem. It's not just about volume though, USB powered interfaces don't sound great if you have to really crank the volume. I definitely would not get the 250 unless you are going to have external amplification. If the different cups on the 32 or any other differences are ok for you, then I would get those. If you prefer the velour cups and the differences of the 80 ohm then get those. I am looking at headphones at the moment, I have a number I am testing but none of the DT770, when I did research those, I came to the conclusion that I would get the 80 ohm version, can't remember exactly why but you do need to look a bit closer to the differences between the 32 and 80 ohm version of those headphones. Your needs may be different to mine.

Well I just did it and there were no problems. I didn't check anything before uninstall, just dumped it off the computer, restarted and reinstalled the full program. Just had to change some preferences and do some setups but that is common with other DAW's when you reinstall. I don't use Sonar I only have CbB and Komplete Ultimate 10 mainly as sounds. I didn't follow any "clean uninstall instructions". Just uninstalled it, restarted the computer and reinstalled it. I am not worried about registry keys, most software leaves those behind, it doesn't mean the installer/uninstaller is broken. There would need to be a specific reason to mess with those which usually relates to authorization or something like that, or if you feel a clean install is really necessary. All my projects are running as they are supposed to. I had to do it because I would never feel comfortable using software that I would be hesitant to uninstall/reinstall. That's like one of my favorite tricks if I get weird behavior from the DAW, it's not a last resort for me. I didn't see any difference reinstalling CbB as I would reinstall Vegas or Studio One or other DAW's. I think your advice relates more to those with Sonar installed alongside CbB, that does seem to be more complicated from what I've read and I wouldn't know how that works and cannot test it on my computer because I don't have Sonar. I guess it would depend on the complexity of the OP's setup as to whether this would be an easy or hard procedure or whether it might make any difference to the problem or be too much hassle.

Is it? Never done it in Cakewalk yet but was pretty much common practice in video editing and some other DAW's, especially for problems like this where it seems there is some miscommunication between the audio driver and the software. I have done it in Studio One and Vegas Pro, there was no problem, easy to do. Why would it be considered last resort in Cakewalk?

Can you uninstall Cakewalk, restart the computer and then reinstall Cakewalk?

That is correct, "X" toggles aim assist on and off with standard keyboard shortcuts. I think Starship wants to leave the line there but remove the information box at the top of the aim assist line, to have the option to do so. I don't think it is possible to do that at the moment.

Looking back over this thread, I still cannot see any evidence that duplicates this bug. There just isn't anyone giving a first hand current account that specifically relates to software VST effects losing their settings when Cakewalk is closed down/restarted. The only evidence is to the contrary, namely, that other users currently using the same plugins are not experiencing the issue. There are second and third hand account stories about this bug but no current complaints and attempts to duplicate have failed. The issue being dealt with on another thread referred to here (TVR Productions), relates more to hardware VST patches not being saved, I am not sure this is the same thing. The offer has been made for Chernobyl Studios to contact support regarding this and they have chosen not to do that, so I do not know what else can be done. The wider issue of online video content producers being paid by DAW manufacturers is really between them and the DAW manufacturer. I've seen these arguments play out all over different DAW forums. Generally though, DAW manufacturers don't do this. It is difficult for DAW manufacturers to establish relationships with third party on-line content providers in this way, because the video creator that might be operating around the other side of the world is then tied to the organization, any bad videos/mistakes they make or any bad on-line behavior they may engage in, can then come back to haunt the organization. There are also many of them, who do you choose? The others will be upset! It is generally expected that third party on-line video content creators will tap into other markets such as UDEMY, Lynda.com, Groove videos etc and for them to establish their own video selling marketplace perhaps leveraging off Youtube. One perspective from DAW manufacturers I have seen is that these on-line video creators are actually profiting from the DAW manufacturers work. By making videos of them and selling them. I am not saying any of these observations apply between Chernobyl Studios and Bandlab, just that I have seen the same argument play out again and again in different settings. I can certainly very much relate to those who pour their heart and soul into a project, create massive bodies of work, only to find there is no financial payoff for it. Maybe notoriety, recognition and respect by others but no money in the bank. This can very often be the agonizing pain before the transformation though. What I have learned is to re-purpose the content and find different markets for it, adapt it to suit different markets.

Wow! no sense of humor! You said you were drinking beer while making the video and you could be seen drinking the beer while making your video. Your voice was slurred and your gait wandered, you looked drunk to me. I didn't misrepresent you at all, you were drinking beer, you looked drunk and you were drunk. That doesn't seem very professional to me. Why would any DAW maker want to be affiliated with someone who drinks alcohol and gets visibly drunk while making training videos? and then attacks DAW users online with threats? What about kids who might be learning the DAW, that's a bad example to set, you should be ashamed of yourself. Seems to me you need to make a choice if you want to be taken seriously as an online video trainer, leave the alcohol behind, it will only cause you trouble in your business as it is now. Alcohol and business don't mix. Instead of insulting me, you should be paying me for giving you valuable professional business advice.

I am just trying to clarify the issues in the video and actively searching for others who may have the issue. I openly asked others to report the issue. I don't know how you can interpret this to mean that I am saying the only person with the issue is the one in the video, that is not correct. There are 2 threads with this issue and it seems Max Arwood may be on to something. I never had the issue myself, if you read my post again you will see I am quoting Max's workaround in the above post. I don't want to reference the previous forums because you can never tell whether they are talking about Sonar or Cakewalk. It's also filled with people grumpy about the collapse of Sonar and going on about really old Sonar bugs. In addition, every topic seems to be seeded with irrelevant posts, you have to wade through them all to find the gems. Why drag all that into this forum? I also like to be clear that we are talking about the current program, not one 15 years ago. Even if there are still old bugs present, looking at them with fresh eyes should be better than with old, jaded, cynical eyes. Saying things like it never happened in any other DAW only Sonar/Cakewalk assumes that you have tried every other DAW all the time. It has also happened in Studio One for example but that was due to the changes in native plugin features between v2 and v3. I think you are exaggerating your claims. If you jumped ship 4+ years ago then how could you have ever even used Cakewalk? Your the second person I've encountered who does not use the program, just comes here to get deals from the deals section and drops disparaging remarks about Cakewalk while here. You do not think that is disrespectful? You take the benefits this forum provides but then criticize the program for which this forum was built, a program you don't even use. If you have something useful to add from your first hand experience with the problem that might help solve the issue then fine. But since you don't even use the program I cannot see how that can be. How are you contributing to help fix the issue?

Hi Max, did you send this info off to Noel? Could be useful, thanks, Tezza

Thanks Mark, looking at that thread, it's still not clear to me what is going on, it sounds as though TVR Productions was opening old Sonar projects in current Cakewalk and was getting unexpected problems. Is this the problem? People opening old Sonar projects in Cakewalk? Cardinal Sin, that is a repost of what this post is about so it's not really a different post. Grem says it happened to him once or twice but that is the only additional information. It reminds me a bit of when I was using Studio One v2 and then upgraded to Studio One v3. Opening a v2 project in v3 was supposed to be compatible but weird things happened like after an hour of editing or there abouts, suddenly the the now time marker would lose synch with the project. Many reported this and it was looked into, sometimes happening, sometimes not, but in the end the solution recommended was to finish v2 projects in v2 and to start new ones in v3. I know that Cakewalk is supposed to be compatible with past versions of Sonar, in terms of opening and running old projects but is this really the case? I guess, to eliminate this possibility, it would be good to hear from someone who has started a new project from scratch in Cakewalk and is experiencing this problem. Alternatively, to those in that thread who were experiencing the problem, were these old Sonar projects being opened in new Cakewalk? It could be some sort of project version incompatibility. Max Arwood seems to think it's a VST 2/3 confusion, he had a workaround to correct the situation in his case and was advised to send a post to Noel, did that happen? Max's workaround: I’m pretty sure this is a VST2/VST3 issue They should not be mixed together in the same project But if you insist on it you could try this Don’t know why is works - but now I don’t have to worry about what kind of plugins I use VST2,VST3 32bit/64bit and I can again focus on the mix. Here is what I do - Uncheck boxes in vst settings Replace if possible Recycle plugin windows Then when you save the file name it Auto-save copy of song name.cwp (Replace song name - your song name) ALWAYS use save as and never Use save or CTRL-S Don’t know why but I have not lost any setting in since early March. I have been loosing settings over and over. It has been a nightmare resetting the plugins over and over. I think 2 years give or take. I seems a little weird but after 2 months and way over 100 saves and reopens with all plugins remembering their settings I know it works for me. Good luck Thanks, Max Arwood

I am not asking you to prove anything, it's not about belief. I am genuinely interested as to whether support for these claims exists, if it does, then what has been said by those who experienced the problem will be of value and it will be worthy of staff to investigate. We need to hear from the people who are CURRENTLY experiencing this problem first hand in Cakewalk by Bandlab and with what plugins. That would be a good start. At the moment we have one complaint from Chernobyl Studio's.

I am not going to search the old Cakewalk forum, issues relating to Cakewalk need to be posted in this forum. I have no interest in old Sonar. Unless there are current Cakewalk users reporting this issue on this forum then it doesn't exist. It may well be that the issue was addressed and that is why no-one else is reporting it. Where? can you show the thread links? if this is the case then it would be relevant information to addressing this bug.

I have to say, I am always suspect when people come onto DAW forums raving about Reaper or pushing it in some way. This seems to be marketing strategy used by Reaper crew. I would have more respect for the video if it just laid out the problems without constant reference to Reaper. Having said that, what are the problems indicated by the video? no-one has clarified that and isn't that what we should be doing in reporting bugs? From what I can see these are the bugs reported by the video: 1. Third party plugin presets not being maintained when the project is shut down and restarted. (fabfilter and waves?). I personally have not experienced this and it appears no-one else in this thread has either, so we would need to find more people who have experienced this, if it is happening then it would be a serious issue. Can anyone duplicate this bug? 2. Playback now time marker sometimes will not stop, keeps going, stop button greyed out, have to shut down Cakewalk. I have experienced this, but not in Cakewalk. I experienced it in Pro tools and Studio One when I was using a Focusrite 2i4 interface. An updated driver by Focusrite fixed the problem. There are others in this thread with the problem, are they running Focusrite interfaces with old drivers? This seems to be an audio driver/software problem rather than a specific bug in Cakewalk. I have also seen it reported on other DAW forums. 3. Missing Prochannel modules from an update in 2016, no details given of what that is and how it is related to Cakewalk, Cakewalk started in 2018 so must relate to old Sonar. I didn't really understand from the video what this was about, whether it related to old Sonar or has anything to do with the current Cakewalk. I have not experienced any missing Prochannel modules and have not seen any complaints about that in this forum. 4. Too many audio dropouts, claims has to up ASIO driver to 1024 instead of 512. I can't see the problem here, just run at 1024 then. If running at 1024 when mixing cures audio dropouts for your project then run it at that. Different DAW's process things differently, Pro tools won't even run properly at all without a second hard drive whereas other DAW's will (to a point). I find Mixcraft for example will run projects and mix at insanely low ASIO latencies on my system but Pro-tools won't, Studio One is about the same as Cakewalk. 5. GUI is lagging, says it should be an instant switch between screens but is not. I couldn't see what was happening here, the screens switch at the same pace as in other DAW's. It's not something I have noticed, I use a 6gb graphics card. I only see one bug being reported here, the resetting of plugin settings, serious if it can be replicated, but no-one else appears to be having this problem. The playback not stopping seems to be more related to incompatibilities between audio drivers and software across all DAW's rather than being a specific Cakewalk bug. I don't understand the missing Prochannel module complaints. The higher latencies needed to prevent audio dropouts when mixing is not a bug. and neither is the GUI lag swapping screens as far as I can see. The only thing in this video worthy of getting drunk and swapping DAW's would be the third party plugin issue if it is indeed an issue for others who don't drink while driving their DAW.

Absolutely! It will also suck the life out of YOU! Sitting in a chair, hunched over staring at a screen trying to fix up a hundred broken up chords to get rid of everything that you think you need to (sometimes there will be nothing left). Only to discover that when you stop zooming in on the guitar chords and rather just listen to them in the mix with everything else, the original files sound fine. Timing is something you have to get right though.

Midi tracks require an instrument (or synth in sonar terms). Midi tracks themselves don't use much bandwidth but the VST instruments attached to them can. What VST's do you use? It is most likely a ram issue since that is what Cakewalk is complaining about, however, given that you are running everything on a single HDD (no matter how big it is). This is not ideal for a DAW to run well on when you start upping the track count and adding sample based VST instruments. It could be not enough ram for what you are doing or as Mcleod suggests a mismatch of ram or faulty ram or some other fault with the ram. If you do have different ram mixed together then you might need to upgrade to completely fresh single 8 gig stick to begin with or 2 new matched 4's if that is all your motherboard supports. Depending on your use of VST and samples, you probably won't need more than 8 gig of ram. But if you have the money then 16gig might be good. It might be that you don't have a computer that can keep up with your new processing demands. More ram and another hard drive to put your recordings on might be a good start. Both of these things are cheap as these days. If you can swap out ram and put another hard drive in your self, that is what I would be doing in your situation. If you are not computer inclined, then get a quote from your local computer tech store, they usually don't charge much. I have an unimpressive older generation i5 and 8 gig ram and 3 hard drives, it all works well enough for my needs. I am looking to move to a 2 drive system with samples and OS/ applications on a single large SSD and then a standard large 7200rpm HDD for recording and move to 16gig ram. You could try tweaking software settings to cure your problem, running with a larger ASIO buffer (1024) for mixing and lower (64, 128 or 256) for recording but I don't think that will fix this problem.

If bandlab assistant needs updating, sometimes it won't do this very well. It's best just to delete it and then get the latest one from Bandlabs website and install that one. I've never been a fan of 32 bit bridges in 64 bit applications so I wont use 32 bit plugins in Cakewalk. I suspect that a lot of instability comes from DAW's that use bridges either natively or third party. You say it happens when you load up tracks, how many are you using? 10, 100? could be ram, might not have enough for what you are using it for or have some dust in the computer, need to reseat ram if crashes are frequent and random but it could also be your hard drive set up. You might be experiencing the limitations of a single hard drive, you don't mention what hard drives you have or how many. When you start loading up tracks on a single hard drive, no DAW likes that. It's best to get all your system specs first before looking at software as the cause of the problem, just need to know what hard drive(s) you have and whether you use a lot of VST's/samples/loops or it's all recorded audio and how many tracks.

Thanks Craig, yes I have spent weeks fiddling with Studio Ones display controls but never end up with an acceptable situation, you can only brighten the arrange window and piano roll together, everything else is set, the surrounding GUI and track headers (unless you use the color controls but there is no default light color). When you do change the arrange window then you start to get other problems with the playback line and cursor disappearing and the transparency of the automation lines looking strange. Also, the Presence instrument that comes with Studio One is all black. The icons and transport controls and sliders for the arrange and piano roll windows are very small and dark. I prefer DAW's that respect their users enough to supply a functioning light default color scheme as an option, one that has been worked out by the DAW's graphic artist, that blends in properly. Not just to supply a black color scheme and then say all the people who want a brighter interface need to fiddle with the controls. I would say with Studio One that how I have the piano roll now is really nice and clean and light, might put that in as a feature request to be added to the Mercury theme here.

When I was trialing out the latest DAW's I just plugged my guitar in, recorded something through an amp sim and then recorded something over that in the next channel etc. This worked out of the box for all DAW's except Cakewalk, everytime I tried to record something over the last track playback would stop, I thought it was broken or a bug until sometime later I found this in Preferences that was clicked by default? What good is this dialog box? Also things like screen sets vs lenses, I have a list won't put them all down. It might be just as useful to mention the option of asking for features to be removed in this feedback forum ie add "or you would like features removed" to the descriptive text.

Great news! well done!

Same here, I also have Studio One but don't use it anymore because I hate the interface, never really got on with it. Too dark and you can only change that a little, I don't like the flat interfaces. The industry seems to be moving towards dark and flat interfaces, I hate them. At 7.00am in the morning if I am working with audio, I don't like to be confronted with a black interface. I use the Mercury and then late at night maybe switch to the Tungsten (sometimes). I do have to have Studio One on the laptop because as pointed out, Cakewalk will not run properly on a small interface. Still both these are better than Cubase that will not even run unless you have the aero running (which i don't like). I don't know if Skylight is obsolete but I hope that whatever changes they do make, they retain the option of a lighter colored interface.

All DAW forums have feature request or suggestion sticky topics. This makes the DAW more complicated as hard core users are usually the ones posting for more technical advancement of the DAW. It can mean that new features are continually added to the DAW. No-one seems interested in keeping track of and removing obsolete features, duplicated features or just features that didn't work out or were unpopular. What about having a "Feature Dequest" sticky topic where people can ask for certain features to be removed.

I certainly wasn't impressed by my experience with Cubase, terrible support and gangly unworkable DAW that was supposed to be easier to use on the UR44 but didn''t integrate at all, I was better off using Cakewlk with the onboard DSP rather than Cubases "integration" but aside from that, it is not for me. I have found Cakewalk to be my DAW and am in the process of moving my projects from other DAW's into Cakewalk. I have no need for orchestral arrangements and use it for singer/songwriter functions, Just being able to sit down and write in lyrics and chords etc and I love the immediate analogue sound of the Prochannel. I also use it with other projects. I am aware that Orchestral's like Cubase, so do those scoring to film but they do not represent the majority of people using DAW's. EDM would probably win that one these days. I was with Studio One and that moved away from being a singer/songwriter DAW and is more like EDM/technicians DAW. You want console emulation etc that's extra, you want to write in lyrics and chords, have to buy another program for that etc and it is more complicated. I much prefer the simplicity and features in Cakewalk. Even Cubase cannot do this for me. You have to write your lyrics somewhere else and then import, and you cant just write simple chords and staff it becomes much more complicated. No use to me. It's alleged great midi functions are of little use to me, I have more than I need already in Cakewalk. I did not find Cubase very intuitive to use. It's a workflow issue rather than a psychological one. Cubase does not and cannot suit my workflow, it's disjointed and complicated, whereas in Cakewalk, everything is there that I need in one program. Except the instruments of course but I have plenty of those. I have not had any trouble getting videos to help learn Cakewalk, the old Sonar videos are fine for most of it, I think I have about 40 hours of videos now from Groove 3, lynda.com, the ones here on the tutorial site and youtube videos also. I haven't experienced any problem with getting videos to explain each function and have renamed them so now my video library is like a visual help file, I can scan through the list on the TV to find exactly what I'm looking for. I have had to do this though because of a lack of an offline help file. So I would say you are correct, I do have a grudge against Cubase and no, I don't like it. And I hope to god that Cakewalk doesn't become anything like it.