Jump to content

Olaf

Members
  • Posts

    281
  • Joined

  • Last visited

Reputation

86 Excellent

Recent Profile Visitors

1,394 profile views
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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
  6. 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.
  7. 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.
  8. Sorry, I can't help. Just wanted to say that's a cool song name, though.
  9. 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.
  10. 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.
  11. Hi everyone, Long time, no post. Installed the new release, first action was a crash on open - not finding Softube Tape activation, for some reason the activation gets reset randomly, usually after a few hours, sometimes after minutes, no connection to CW - for which reason CW reported a crash with Waves dbx - code c0000005, which seems to be related to VC++, even though everything is installed and up to date. Reinstalled iLok, loaded up fine, Tape working, except the settings of all its instances in the project were reset to default, as if they were never set up at all. All Waves plugins get scanned at each start, otherwise the project loads without them, so, if it crashes 10 times a night, which is not at all uncommon, 10 times I need to wait about 2 minutes for the scan to complete. The toast notification for the scan never goes away after the scan is complete. In all of these respects, seems that nothing has changed. I haven't participated in the discussion about the new planned releases for CW, but, in my opinion, CW is not remotely in the same league as being ready for a commercial release - and I'm only scratching the surface of the introduction here. I must have about 50 captures of things going wrong in the last few months - meaning 50 different issues, not repetitions of the same. I meant to send them to the developers, but never got around to it. Just my two cents. Will continue to work with the new release.
  12. Short interview about the technicalities of digital sound processing. Thought it was interesting for one paradox, and two misconceptions. Most people out there think digital sound is of "perfect" objective precision, whereas this interview, like the Rupert Neve interview of a few days ago, highlights two things: one, that it's not objective by default, it still involves a lot of choices, good engineering, workarounds, and, in the end, personalized algorithms, and, two, while most people think digital sound is superior in quality to analog, exactly the reverse is true. Not only is it not, but even today it's still struggling to equal the quality of good analog gear. It's true that you might get a lower noise floor - objectively, which is not automatically a good thing, subjectively, and even that's not a given - some analog gear had/has an incredibly low noise floor - but there're plenty of shortcomings. For the last few years I think it's come close, in some departments, and hopefully in the future it's gonna bridge the gap. I've talked to Jatin personally, about his Matrix delay, he knows his stuff, and he's a cool dude.
  13. fully agree! people have more and more tools, but less and less perspective of what to do with them, and why. info overload, but little knowledge.
  14. Ditto. I my experience, fast scale players, as a general rule, can't write squat. And the problem with practicing scales and riffs to no end is that you automatically form a reflex to revert back to them, instead of writing/playing/imagining lines. That's why I personally avoid it, and that's part of the reason. In honesty, I kind of avoid practicing, in general - what am I saying, I avoid it altogether - so I'm not fast at all - and don't miss it at all, except when I listen to Mike Oldfield, Eric Johnson, and John Petrucci, maybe Tony MacAlpine, in his early days - those are some of the very few guys i find can make music while playing fast, and not just play whatever, fast - so they actually make me want to be able to do that, instead of just ignoring them, which is the default mode for most. On the other hand, my favorite guitar players are Dave Gilmour, The Edge, Tony Iommi, B. B. King, so on. People who wrote music on guitar, not just played fast, to no apparent outcome .
  15. I'm curious about the negative side. Luckily, we can make music for ourselves now, and promote it oursleves - that's the bad part. For what I hear about the music business, I wouldn't sign up with a corporation even if they asked me to. The fascination is gone. And I would never give up the rights to anything I wrote. I'd rather be buried with it - hopefully not any time soon.
×
×
  • Create New...