Olaf

Thanks for the suggestions. I've kept an eye out for alternatives, but everybody seems to be sold on this minimalist "modern" GUI look, which means a very caricatural, depersonalized, schematic look, with nothing to lean your eyes against. Very underwhelming. I'll just wait to see if Luna implements some of the major requests everybody's talking about, and, if it does, we've got a winner. I do like Luna's look, and they seem to release an update every month or so - though they also seem very slow in implementing major changes. If not, I really don't know what I'm gonna choose.

I guess i just kept hoping. When I like something, I don't give up on it easily - define "easily", right? It's the feeling that the problems will never get addressed that's the downer - that's when you give up. I like the interface of CW, I like the concept, the possibilities, all the integrated options. I have Reaper, too, but I don't like the interface, and if it doesn't inspire me when I open it up, that kind of settles it right there, for me. There are various skins, but still, plus there's no front console - that's a always great thing to have. I was looking at Mixbus, but it's too expensive, and the workflow, too complicated and unintuitive. It does sound great, though. Now, with Luna coming into the picture for Windows... I get that tingly feeling again. Still a lot of things to solve in that one, too - a few majors, plus a lot of minors - but I hope they're gonna solve them ?. Hopefully, not turning into a deja vu.

i've been waiting for this day ever since i've seen it. having it free was the only thing that could top that. already installed, made my first project in it, already sent them the first few dozen suggestions ?. biggest ones: multi-out instruments, mono inputs for stereo tracks, an additional insert section before the tape/pre extension stage - for amp sims, rooms, different pres when you don't want the api, etc., and (my favorite ?) option for control bar at the bottom.

unfortunately, cakewalk is a great concept, very poorly implemented. i won't go through the list of problems, they're countless, and i've talked about only a very few of them here - right now, for instance, i can't export a project, plain and simple, it crashes on every attempt - cakewalk.exe, defaulting module, i've tried reinstalling various vcredists, cakewalk itself, to no avail, i don't know what to do; i always find audio clips in different places than where i thought i'd placed them - because the timeline bar indicator popup is not accurate - i've figured out why there's always tons of useless and unintentional clip slices in the time line, which are a nightmare when trying to trimm or comp clips - cause the smart tool visual indicator does not match the action region it's placed in, and it shows trim when it slices, without you knowing; anyway, that's just the latest. editing is a nightmare, so is working with envelopes. can't work on a gain envelope when the clip is not enabled, can't enable without switching modes, then you need to switch back, at which point it places envelopes on all the rest of the clips, you've just deleted them from. stuff just doesn't make any sense. exporting a clip that is not active exports silence ?- so you need to activate it - freezing is, in fact, rendering, so on. i took a peak at sonar's new interface, vectoring aside, the look is not something to look for. basically the gui was one of the best things about cw, if the devs' idea of improvement is not to solve the major problems, but to give up the things that were good, that tops it for me. i'm getting the feeling i had when i gave up reason. i've updated to the latest edition, for various reasons - got a good deal on it - but i won't probably ever use it again. i'm one inch away from deciding that about cakewalk/sonar. i'm spending half my time doing damage control, in it, anyway - for instance, now, acustica black displays a... black window in some projects - works fine in others, have no idea why - and the worst thing is most of the damage you need to control you don't even know where it comes from. and i'm at a point where i don't even want to solve anything anymore. too bad. i was so excited about it in the beginning. so many good things about it. if only they worked. or were implemented intuitively. for instance, even now, after over 4 years, i can't get used to the midi editing right click thing for selections, the selections are not accurate as per the bar region, the copy-paste is always guesswork, pretty much instead of relaxing, i feel i need to be on my toes every time i work in it.

i agree. it's still got a little bit of a problem in the low mids - a bit of a thin tone, covered in honk, instead of a full body, on some models - and the (very little) spiky top end - but it's a nuance thing, it's not a majordown point. overall it does sound good, to, sometimes, very good - i love the hiwatts, i plan to buy them tomorrow - it's got all the controls you need, without going down the rabbit hole - which is important - and, best of all, it's permanently improving. i think it's made strides so far. i wish it switched to 0 gain input calibration, all amp simps i think should do that, that would eliminate the infinite input gain guessing/setting problem, and also make different plugins compatible to each other in the signal chain, gain wise, without having to guess/tweek the gain differences between them - when switching, or using different stages of each. tonocracy and nam have done that so far, i think everybody should follow their example. for instance, i don't know how the nam player input is calibrated in amplocker, but if it's at the same level at the rest, that would be too hot for most nam captures.

They ARE on fire, but when you choose to ignore it I guess you can invent a parallel reality designed just to contradict. Not to mention a lot more people would probably come up, if it weren't for individuals just like yourself, and if they thought their input actually solved anything. Anyway, thanks for your guessing intervention with no accuracy, intention to help, or info on the matter whatsoever, for the exclusive purpose of invalidating other people's experience. I guess people should return the favor sometime, it would be just fair. Since it appears it's ALL you do.

It sounds like every single intervention you have on this forum is to put someone down, or negatively comment, without any special reason, intention to help, actual interest in the problem, or info on the topic. It seems there's a lot of people with "seriously screwed up systems" on this forum, and the observation has already been answered. It doesn't help anybody if you always make it personal, about specific users, which seems to be your "style", and it certainly won't help Cwk.

Sure, but looking around the forum, you can see there's many such reports, from many people. I don't have a dedicated system for music, that I keep in a "sterile" environment, software wise, I have all kinds of programs installed, plus anti-viruses that constantly mess with legit software, so on. So, it's a general purpose system that I use for music, but not only. I constantly install and uninstall a ton of plugin, try out stuff, etc. - thousand of titles over time. I understand that can mess with your system, sure, but a DAW is not supposed to only work in certain, very controlled, "pristine" conditions. And I've been through about 4 OSes during these 4 years, starting with Win 7 - now I'm on 11, tried about 4-5 interfaces on it, and in time changed every piece of hardware inside it. These issues have been constant throughout.

I said it myself, a few days after the announcement was made that I didn't think Cwk, as it stands today, was even remotely ready to be commercially released. And the thing is, if it fails for a second time, commercially, I think it might be the end of the road. So, hopefully the mystery is about fixing the hundreds of bugs and reliability problems it has - plus maybe a few dozens intuitiveness and ergonomic problems. Having newcomers that aren't as prone to finding excuses to it, no matter what, out of habit, sympathies or misunderstood gratitude, might be a good idea, in that regard. Cause one thing I've said from my early days with Cwk, about 4 years ago, was that the moment Cwk become a paid application, all that predisposition for lenience will vanish overnight - and it's not doing anybody any favors, as it exists today. I do believe people on this forum would be good testers, subjectivity aside, but, for one, I've signalled dozens of problems during these 4 years, and none of them seems to have been addressed. Some suggestions did make it, though, and I appreciate that. I still have about 30-40 pretty big issues captured, right now, which I'm not putting out because it would take a lot of time, to very little hope. For instance I can't trust Cwk with my audio clips. I don't think there's worse you can say about a professional DAW. And it crashes a few to a few dozen times a night, for the most diverse reasons. It can't find, now, plugins it had loaded 5 minutes before. It handles RAM and registry entries badly, and there always seems to be some conflict with the video side in the VC redists - to my very limited understanding of media frameworks. That's just counting a few issues. And I do like Cwk, don't get me wrong, I want to work in it - love the interface, the PC, what it can do, the sound, etc. - but objectively speaking. It's got a lot going for it, if the problems were solved, I think it would be stellar. But the problems are great, and have persisted for years. So... For a commercial release, i believe the most important factor, before any interesting functions, is that it be reliable, and work as intended - basics first - also consistent and intuitive - which it doesn't right now.

I've got a new one in the same series - the bit depth and noise parameters of Witch Pig Nevermore SPX get reset when the plugin is switched on/off, from the FX bin box. Don't know if it started with this version or not, it's the first time I've used it. Based on experience, I'd say not. Nevermore Witch Pig Gets Reset on Engage.mp4

I wouldn't say that. It's pretty simple, option wise, but it sounds great. If you're curious, open it during playback, the way you have it set up, and then press Stop - that's when it resets, in my experience. So, whatever instructions are sent to CW when you press Stop, one of them also instructs the plugin to reset. I've just exported a project, listened to it, the snare was immensely loud and low mid heavy. One band of REQ had jumped again. Now I'm re-exporting, had to redo the EQing on that band. Lucky thing I remembered the values.

A new occurrence - I can't say if it happened in previous versions, cause it's the first time I've used it - is that the Hornet SW34EQ plugin gets completely scrambled every time I open a project that includes it. All the gain knobs jump to max, the input-output link button gets engaged, the input and output settings are reset to 0, the hiss level is reset to default, and the plugin is turned off from the frame - even if it appears active in FX bin. This is very similar to things happening in the past - Softube Tape and Embertone Sensual Saxophone fully resetting on Stop/Play commands, or Waves REQ6 and H-EQ bands jumping to max value, on pressing the same. Additionally, the double arrows that open the Synth Rack/Browser/Help windows are missing - that's something I've reported a long time ago, not fixed, the toast notifications still don't go away by themselves, and the order of these three windows still gets reset, on some projects. The Arranger track always missing on open, even though it's saved with it on, so on so forth. That's just a small part of the minor stuff. Another thing that I've noted recently is that now plugins crash when i turn on/off other plugins up the chain - for instance Waves dbx crashes when I turn on/off the PA Helios Bus, in the bin, five plugins upchain, or PSP Delay crashes when I turn on/off the Reason Rack . Many times turning on/off makes pop sounds, some times the ML Drums channels start making this huge whistling/hiss noise that covers everything - not good when you're wearing headphones, I can tell you that - and a bunch of plugins keep crashing the DAW - if I remove one, another one crashes - I've gotten to 6 separate plugins crashing the DAW, on one project, at different times. Other times, CW just crashed by itself - CW core. The code is c0000005 or c0000005d. I've got all the VC redists installed. Virtual instrument outputs stops or it gets desynced every time I reposition the playhead in the time line or change the loop selection. That's some of the not so minor stuff. Not the worst. The more serious problems are wave clips that I find moved in the timeline - the contents of the clip gets repositioned when I trim the clip edges, other times various slices appear in various positions in the lane, hidden underneath other clips, so on. There's dozens of types of problems, in this department. This is the serious stuff. These are all old, and have never been fixed.

Sorry, I can't help. Just wanted to say that's a cool song name, though.

If you're talking about audio, it can be done, but it's a little more complicated. You need to select all the clips in the project - or only the section you want to change the tempo of - go to Clip properties and check the Stretch To Tempo box. As far as I'm concerned that should be checked by default, for any clip, cause I can't imagine a scenario where you'd want to change the tempo of the MIDI, but not of the audio. But you need to check it - before you apply the tempo changes. I hope this helps.

hi will, that is not an option. i don't have a system that i only keep for music, and don't touch with anything else, i have hundreds of plugins, and dozens of programs, i don't have stock settings on anything, everything on the desktop is personalized, a clean reinstall probably means a week to reinstate the computer to what it looked like before. i can't do that every few weeks, i'd kill myself. i do maintenance fur sure, updates, some registry cleaning - i don't how good that is, in itself, but it's necessary. i did it a few times - clean reinstall - during these almost 4 years now, probably, but it's always been just a matter of time before things get corrupted again - sometimes a matter of days. I've worked with 7 interfaces, and 4-5 OSes, from Windows 7 to, now, Window 11. And the rest of the system I've changed twice - motherboard, CPU, RAM. these problems have always been a constant. and most of them do not even involve plugins - although they sure do, many times. i think there's an issue with managing RAM, i think there's one with the way the registry is handled - including cleaned - by CW, and i believe there's an issue with the way it works with graphics. many times CW sees less available ram than there is, sometimes it loads on red the same project it usually loads on green, with room to spare, stuff like that, then the first affected is the night light - which i have on by default, it seems to not work with the graphics adapter very well. and OpenGL plugins seem to be a big problem for it. the plugins it seems to have a problem with most are OpenGL. couldn't tell you more about that than this. just reset the tape settings again. that's the third time for this project.