solarlux

40 minutes ago, backwoods said:

protools has this and also aax has some kind of ability for third party plugin makers to make use of it too. that and the ability for EQ plugins to alter the channel strip eq representation- eg mcdsp, fabfilter, sonnox

Yes and would be cool atleast from one stock compressor posibility to see gain reduction meter in channel strip : )

1 hour ago, RobertWS said:

Future complaint:

Why is everything hard-coded in Cakewalk?   We have no flexibility and control. 

A scripting language would be great so we could customize and share the scripts to our hearts content!

Agree about flexibility and in future some easier to code scripting language like a Javascript or Python would be cool

2 hours ago, Cristiano Sadun said:

Ah, cool - no I haven't used FL studio but it's nevertheless more clear.

Yes for example you made pulse modulation automation and there is points with which you can control how frequent pulses and point for amplitude

1 hour ago, scook said:

I have not looked at it but a user posted a revised legato CAL on the old forum.

The file is still available.

Bakers need replace bugged CAL with This version : ) It would be nice if this version is fixed. Happy news now is original Legato Cal scipt uis bugged but here is what works. Nice we can use CAL scripts.

CAL-master.zip

3 hours ago, Bruno de Souza Lino said:

Do you have that on all compressors you run in Studio One or just the Stock ones?

Stock

1 hour ago, Cristiano Sadun said:

I guess what's unclear is what you guys mean by "control points". It's like in graphic programs' Bezier curves, where each point has handles that allow to change the slope locally?

Have u used FL studio? He thinks points which controls for example pulse frequency and amplitude of automations

11 minutes ago, Glenn Stanton said:

a number of software companies offer bounties for finding bugs... not a lot of money, but whatever gets people looking and reporting them. of course whether or not the bug is fixed remains to be seen 🙂 and then there are "spellcheckers and grammar checkers" (like auto-wreck, er, i mean auto-correct) which don't ever seem to care about getting things right...

i generally agree with what Craig was saying "Me: Doctor, every time i touch my rib, it hurts. Doctor: then don't do that" 🙂 

Yes but simple contest and can have a fun without prize : ) We can all trying all in unusual ways

Gain reduction meter from some compressors  on the channel strip, example compressor from pro channel or sonitus compressor.

Need contest who can find more bug he win. This can help in bug tracking CAL script bugs doesn't count . : ) Cakewalk works for me fine. I 'm joking about bug finding contest but it can help to list all bugs what happens  in unusual situations

This is good place for menu : )

57 minutes ago, Promidi said:

They might be obsolete, but they are still supported (to open).  While we wait for “some new alternatives”, I will continue to write and use them.

Yes but in future something like this can give big value. Many tools easy accesable for midi editing in menu like here in FL studio. This functionality that list in piano roll accessable menu would be huge value

legato, strum, chop.flip and some more : )

CAL scripts are obsolete and need some new alternatives : ) I agree about midi manipulation operations. All these little manipulation things can give very big value.

I 'm very happy about Cakewalk and all what Bakers do is insane and how they respond and are active on forums and also they are developing that all is insane how energetic CbB Team is and they compete with big brands like Ableton which have much bigger teams. Bakers are insane and i respect Cakewalk very much and also i know these small bugs will be fixed only need to be little patient because To do list is Huge.

Problem was when u started comparing Cakewalk with FL studio and Ableton. Don't need compare with children DAW FL Studio where everyone can start music without expierence but FL Studio lacks many proffesional users features, FL studio is good for fast scratching  ideas.

3 minutes ago, Craig Reeves said:

I've never been told by any of the staff people on this forum that my videos are unclear. My videos aren't unclear to the people that actually watch them.

All is good but you need write specs and project file under video and then Bakers can download project file and trying same and test it.

8 minutes ago, Lord Tim said:

 

I'm not really defending or condoning anything here, just to be clear - everyone's post and the tone of their post is their own. But the point he was making kind of is correct, regardless of how the tone is presented. 

But again, the videos can only go so far. That's showing that something isn't working correctly, not WHY. This is a peer-to-peer forum and we're lucky enough for the devs to stick their heads in fairly frequently and help when they can, but nothing we say here gets put into the system unless a dev happens to see it and log it.  Just looking at the bug list Noel was talking about from the last 3 years, if there's been thousands of long standing SONAR bugs address since then, think about how much is in the backlog they're getting to. If something isn't in the system and being allocated and prioritised, you don't know of anyone has logged your issue from a video on a user forum at all. Maybe it has? You just don't know.

Again, sorry if anything I've posted is coming across as antagonistic or patronising at all - it's really not the intent. I just think there's other avenues you need to go down before you up-end your desk and write stuff off.

Yes and Cakewalk now is in new Home and new priorities and main priority is bug fixes but Developers need more info than video where bug showed. Here also people mostly with expierence and they don't need ableton or something like that Cakewalk in my eyes is much better than ableton and in future it will become more stable because we users need report bugs and help Bakers to know what need to fix with detailed information about all of bugs with what we encounter.We all need to be involved and that is very good.

Just now, Craig Reeves said:

As I mentioned before, that's not necessary if the developers can reproduce the error themselves. That means it isn't specific to one's system. Stuff like that only really needs to be done if others can't reproduce the problem. If everybody no matter what system they're on can reproduce the error, that means it doesn't matter what system they're on. Noel nor any of the developers have ever asked me to provide details on my system. But they have asked me to provide instructions on how to reproduce the problem, which I provide.

Yes but would be cool project file with all what you tryed reproduce this in video. Need constructive report. I understand them and they need project file and info about your envrionment and some other aspects.

We all here good community and we can help eaqch other and also glad to see some bug reports because bug tracking is very valuable thing because bugs can be listed and fixed later.

Just now, Craig Reeves said:

Which is exactly why I post videos on how to reproduce the bug. Notice that I never actually say that I am CERTAIN it is a bug. That's the whole point of providing instructions on how to reproduce the error. Because if others are unable to reproduce the bug, then it is something local to my system or user error that is the cause. For instance, the bug with quick-group latch automation I have tried on four different systems and multiple different versions of Cakewalk. I was able to reproduce the problem. But you cannot dismiss the problem I'm having as specific to something I'm doing wrong until it is demonstrated that others cannot reproduce the error. 

And as far as finding out why a bug exists, you don't do that until you have tried reproducing the error. 

And I honestly can't believe you're defending @bdickens either. Dismissing someone expressing legitimate concerns about Cakewalk as "bitching" is toxic. And he was "getting at" anything but being an *****. I've seen some of his past posts. He's like that toward others, not just me.

You need also project file and system specs, : )

5 minutes ago, Lord Tim said:

There's nothing wrong with venting when things aren't working for you - we all do it - and it's certainly fair enough. I've seen you post enough stuff around the forums to definitely not discount what you're saying as a troll, or the rest of us just sticking our fingers in our ears and going "lalala not happening, this guy doesn't know what he's doing."  I believe you're genuinely having some issues there, but I also think  that because you're frustrated that you're not taking all of the steps to fix stuff either. Not having a dig or trying to be insulting here, apologies if it comes off that way.

There's been a few guys with some horrible problems that a lot of us haven't seen before that weren't able to be reproduced, but if you have a scan through the product release threads, because they were reported and documented correctly (not just videos, but environmental settings such as hardware, drivers, installed software, etc.) then it was sorted out - you'll even see Noel mention how he's hopped on to a Teamviewer session to to run tests to get to the bottom of it all, and yes - sometimes this HAS turned out to be an obscure bug or something else that's exposing a problem that most of us aren't seeing. I don't know any other DAW company that does anything like that without charging you a crazy premium for it.

Showing the result of something only helps so much. "Check it out, when I press Alt+A the entire screen turns purple - this is buggy!!" only shows that - yes, that's really weird and looks like a bug - but not WHY. I think this is what @bdickens was getting it - if you don't work with support to get to the bottom of it and just complain about the outcome, how could they know what the issue is?

That sndfile.dll Waves issue I mentioned was a good one. On first glance, CbB is rubbish because it's not able to copy over a file properly and you have to tell it to skip a file during installation. Looks like a bug or horrendous UI programming. But in actual fact, it was a bug in a specific product that is only triggered by a certain sequence of events, and it it's actually getting fixed by the people who can actually do anything about it - the CbB team have no control over it.

You see what I'm getting at?  You have real problems there (outside of certain shortcomings with things that need to be looked at, eg: Audiosnap, CAL, etc.) but whatever is going on in your environment won't get fixed if all we see is the result, and not able to get to the cause. Like I said, I'd be gone if my system was anything like you're experiencing, and if CbB was the app I would really prefer to use, I'd be making Support absolutely sick of my name in less than a week.  

Yes and I 'm very happy to see all these massive bug fixes what have already done. Bakers do work very well and i 'm sure also these specific problems will be fixed.

50 minutes ago, Craig Reeves said:

This is exactly what I was talking about in my post and also the reason why many people who have problems don't "bitch", they'll just find something else to use, which is probably at least one of the reasons Cakewalk did poor business (along with poor marketing) when it wasn't free. Most people don't "bitch", they just use something else, and as you can see I literally just got finished documenting every one of the bugs I brought up not only this time, but in the past as well. Every one of those videos I posted are videos I have posted before on this forum. I do not just come on here and "bitch", I give full details on how to reproduce the bugs, but I STILL get flack from at least one person every time I do. The problem is that people like you don't actually read the full context of a post before commenting.

There is a history of people expressing their frustration with this DAW but then getting attacked by people like yourself for telling it like it is. I suspect this is why some of these bugs don't actually end up getting addressed, because folks don't want to deal with the bullying, the gaslighting and the attacks for bringing up legitimate problems. Because rather than simply addressing the fact that yes, X issue is indeed a bug I was able to successfully reproduce and therefore needs to be addressed, people will either literally tell you that you're imagining it (gaslighting), tell you it's not their problem, or tell you to "quit bitching". That needs to end if these problems are going to get addressed.

I want you to notice that hardly any of the bugs I brought up have even been addressed in this thread. All I get is "well, it's not my problem because I don't care about X feature", or "Cakewalk works fine for me". As Noel mentioned, people use Cakewalk for many different reasons. If all you're doing is tracking vocals or guitars, you're not going to run into problems with VST instruments or MIDI. If all you do is compose film and game music, it is unlikely you will run into problems with the Matrix, etc. I produce R&B and pop music, so I'm probably not going to run into articulation map issues because I don't use the articulation map often. 

I've never said that Cakewalk doesn't work at all. I said compared to the other DAWs I use, it is much buggier than those DAWs. It crashes far more often, and has way more broken features. That is not to say that Pro Tools doesn't have bugs too, or Ableton. They do. But they are far more stable and have far fewer broken features that don't work. As I've said multiple times already, I still prefer Cakewalk to both those other DAWs, but that doesn't mean there aren't areas I feel Cakewalk is inferior. 

The reason I single Cakewalk's problems out is because I'm on Cakewalk's forum.

We have to face the reality that Cakewalk's future is uncertain, and I want to continue to use this DAW. I actually want Cakewalk to survive because I love it. But we have to be honest and live with the fact that it is not good enough that Cakewalk be AS GOOD as Studio One or Cubase, it has to be BETTER. Because in order to catch up you have to be going faster. That's a fact. Cakewalk is already 5 laps behind in a 30 lap race. And Cakewalk has the potential to be that good. It's only real flaw are the bugs.

 

Need to reproduce these bugs for Bakers than they maybe can fix them. But about CAL scripst its not bug but CAL scripts aren't developed and abandoned and will be better sulotion in future.

8 hours ago, TLO Productions said:

Yes, I tested dragging the selected arrangement into the matrix view.  It created the tracks, but doesn't maintain the arrangement of the clips rendering it unplayable.  For it to work, all clips have to be the same length.  This is not always the case in an arrangement, and that's additional work to make every clip the same length before dragging it into the matrix view.  

 

`Yes would be cool if it will work with arranger section drop and also would be cool when clicking on matrix cell where midi clip midi can be openen in independent piano roll for editing midi of matrix view cell. But anyway idea is very good to get working it properly when droping arrangement section to matrix view. : )

52 minutes ago, Kevin Perry said:

Half-baked may have been a bad choice of words, but if you have to go to 2 different places to adjust relevant parameters (and the places aren't immediately obviously linked without knowing how it works*), then it's a piece of bad UI in my opinion.

* And if you know you also need to go to the track's paramaters (CV or TV), then you know you need to go there, so why not just go there and not have the extra UI on the plugin 🙂

Yes but atleast visual representration with which channels compressor sidechained would be cool : )

About cut and paste i like in Studio one have Ctrl+L shortcut u need only select all what u want move and press ctrl+ L  and it locates struff to cursor 1 step instead of 2 steps cntrl+x and cntrl+v

@Craig Reeves Ablteon have big budget and development team but and also atleast 20 million budget  Cakewalk havent so big. But we all together can help to make it best of all