marcL

I hope so at least, without any Lexicon I would be very sad! ? Essentially the 2 Lexicons and the Twin-L are my goals and if there are not 2 plugins in the end, then I am really disappointed! Still hope! ?

For me this is even the worse problem than to uninstall T-Racks that I don't have, because there is no work-around to avoid those silly messages! But in general I think both of these issues show that IK Multimedia is not really listening to customers, instead they think this is a good promotion for there products, but I doubt in that ?!

Here it still works! But I have experienced cases that plugins were listed that I have removed or moved to another location (including plugin rescan). Thus in those cases it did not work of course!

I worked a lot with software, professionally and for myself, and in my experience one of the most frequent problems is that the analyst(s) and/or engineer(s) forget to rule rare cases and exceptions as many topics are to complex. This even happens in software development for airplanes and fighters and leads sometimes even to their crashes, although that is one of the software industries that implies most money, manpower and testing cycles (but nevertheless it happens)! In other words IMO a real good online mastering or something else that is art-like is nearly impossible!

I like the tempo view as it is, because sometimes I transfer parts of a project into other programs/hardware or to friends and then it is comfortable to have a bunch of readable values that can be easily reentered in another system!!! Runs perfect that way.

And some is from MS propaganda campaigns!! ?

No, that is just a matter of the implementation!

I am pretty sure that in the end the creation of the VST3 standard produced more damage than benefit for the DAW users: A lot of development manpower has been exhausted to create and handle errors of Vst3 versions that could have been invested in improvements and in new plugins. A lot of development manpower has been wasted to adjust the DAWs for Vst3 and fix upcoming errors. Many users have a lot of trouble handling the double standards along with 32-bit plugins (some). The installations and configurations in the DAWs are actually more complicate than before Vst3! Plugin errors are sometimes not transparent, because it has to be checked which version(s) have been used. This is especially delicate if a Vst2 version of a plugin has been replaced by its Vst3 version in the same project or if both versions are used in the project. We all know far too well that the Vst2/3 versions behave not always the same! and so on ...

IMO this comparison by Musicradar is not more worth than toilet paper! There are so many arguments that are important for DAW choice and there are not 2 people that weight them in the same order. It is red-top press style to show a simple order without real detail comparison. I prefer extensive detail comparisons for buying/using anything, because it allows me to choose the criteria that is most important to me!

IMHO this is not really an advantage, because only the major location is specified. Whether a plugin provider defines a company subfolder or even an additional plugin subfolder is totally free. So in the end you get a real mess in the VST3 folder. If you want to improve this (I do, have them grouped by type), then you have to do a lot of stuff manually and for each version again, because only a few plugin provider support location configuration for VST3 as all of them do for VST2! Just a big step forward to the past!

This has to do with the very poor transient detection of Melodyne. You must know I like Melodyne and I often use it, but I have learned that I have to revise about 60 to 70% of the detected transients in the note assignment mode. Afterwards everything runs fine. But it is an illusion that the program itself detects the notes automatically (it's Celemony's fairy tale). Even when I've used a very simple and constantly played bass track I noticed that Melodyne sets the transients not at the same place for each note, it is very annoying!

If there is a Vst3 version, then I use that one most of the time. But there are some plugins that were developed to use the standard Vst2 preset handling (you can open a list box in most DAWs to select one) and this makes it very cumbersome in CbB to select presets in their Vst3 version (e.g. some plugins of Plugin Alliance). In such cases I prefer the Vst2 version over Vst3.

Each time when I lose the working flow/drive because something special happened that stopped me (my wife has broken her arm, so I must help now in the stable; last time when I was sick for 2 weeks) then I get into a real motivation slump for some weeks. It is hard to come out again!

But what's about the iZotope plugins? They come with a .vst3 file and a dll file starting with "i.....dll". Will they still run properly? ? It is always an annoying trap if some plugin providers tinker there own exotic solutions ? (like iZotope here, and especially Waves). I have separated all other plugins.

How? Sorry, but I cannot find it! ? Also I forgot to mention that you also have to select the/a mono input for the audio track. Both of these things I find in the inspector, but only if I split the simple instrument track!!! But I'd like to learn how to do it, because it would really simplify my work. ?

I had crashes and misbehaves with several versions of Hornet's TheNormalizer (not only in CbB also in Sonar/Samplitude/Audacity). Thus I uninstalled it, it's a waste of time IMO!

It is the same thing with the stereo/mono interleave setting, you have also to split and then re-combine. For guitar and bass instruments it is often preferable to have them mono.

IMO the only thing that is missing with this method: You cannot assign a senseful value range to the knobs, e.g. if you have a threshold, compression ratio, release value or whatever how can you know what 1-100% means??? Okay, you can say you have to listen, but that's not a quick starting point for a setting!

The only reason why I don't use normalize to approximate the level of multiple clips is because in many cases there are spikes that lead to a very different loudness result of the clips. Therefore I measure the LUFS integrated value of each clip (I use HOFA 4U Meter Fader, where I can just drag and drop the clip) and then adjust the volume with 'Process > Apply Effect > Gain...'. This is the way I do it, but surely there are many ways to come to heaven! ?

I had this problem several times (even today). The thing is if the Ctrl-Z command is sent to Melodyne only the last step in Melodyne is reverted, but if the Ctrl-Z command goes to CbB then the Region FX command (Melodyne) is reverted, so Melodyne is closed! But the good thing is that you can reopen Melodyne with Ctrl-Y (or redo) and the editing is still there! The first times I experienced this horrible close I thought the same as you that all my work was lost. But once I understood that it was the revert of the Region FX command I tried the undo and it worked. The problem is that when you press the space bar in between to start play (or click anywhere into CbB) the control goes to CbB and if you then enter any short-cut it is sent to CbB and not Melodyne. It's not so logical for the user, but it is program logic!

Yes! It is possible for all kind of clips.

I think I understand what you and some others here mean. I totally agree that each bass/guitar/keyboard player or drummer does play differently to the same song and I 100% agree that there are definitly songs that profit of a special, inventive instrument line (a good sample is the bass/drums of "Come Together"). I also agree that there are songs that would not be half of the value without some instrumentation or vocals. But nevertheless I think this is instrumentation and not composition! And it is wrong to believe that the composition is the thing with most value, in some songs the other parts of the whole process are even more important! ?

By the way it is not necessary to make a MIDI file/clip! You can simply select the measures of the tempo range that you want to copy in the timeline and then use copy special with only tempo changes activated. Then you can set the now time in the target project where you want to insert the tempo range and use paste (or paste special). Like that it is possible to copy a part or all of the tempo changes and insert them into any position in the target project!

IMO the easiest way is to select the clips you want to mute/unmute, open the clip properties and then toggle/set the Mute value.

Sorry, I don't agree at all! If I consider all the renowned songs that I like and where I know something about the composers, then I dare to say that most of the time there was/were only 1 or 2 persons involved in the composition of the songs! Only the arrangement was usually created by the whole band.