marcL

Setting the display language to e.g. Swedish does not only affect Windows, but a lot of programs set their translation also to Swedish and believe me there is so much inventiveness in translation that you often don't have a clue what some words mean in the programs' context! ? But on the other hand if I have a Swedish hardware keyboard (in the laptop even built in), then I do not want to set English to my keyboard language, because it is a nightmare to find all the special charaters! ?

It drives me crazy! All developers urge the users to use the newest versions of their software. The arguments are to prevent virus interaction, more stability, better experience, ... But my experience is completely different, especially with Windows 10 (but not only). From the beginning I had difficulty to define my language preference in Windows 10: English display language and Swedish keyboard language. Finally, some updates ago I managed to define this only language combination without any others that can be activated accidentally. But now those Microsoft development bastards have changed it again! And I have found no way to remove the language combinations with English keyboard without losing the English display language! Are they really so stupid or do they have fun to plague their users? In many programs (that use a modern layout) the settings get more and more stupid, intransparent, incomplete and illogical. I just hope CbB does not go this way! In any case the biggest virus to me is Windows 10, because it has stolen me so many hours with its problems and updates!

Antares ASPIRE Evo Aspiration Noise Processor and SYBIL Evo Variable Frequency De-Esser for $21.00 each on JRRshop (instead of $59.00).

Yes it is!

I tried all of these methods today with some frozen mono synth audio tracks (AD2). No success with #1 and #4, they did boost by 3dB in my cases! #3 was not my favorite one, because you need another program then to split the stereo files. So in the end there remained only #2. Or #5: I opened the audio files generated by the freeze in the audio folder with another program and exported them in my target format. Finally I must admit the whole thing is a PITA, because you either have to use an additional program or you have to do actions that have to be reverted manually! ?

Thanks scook, I never found this so clearly described! But nevertheless to me it feels a bit like a bug when exporting a frozen synth mono audio track (interleave=mono) or its clip copied to a usual mono audio track don't deliver the same result! It is exactly this inconstancy that confuses me. One time I think "Now I got it", but the next moment I get irritated because it does not behave as I expected! ? I have also observed that in some cases the indicated level on an instrument track (mono) had changed by +3dB after freezing when I reopened the project.

Me too! Working with mono tracks is sometimes very cumbersome in CbB. I have especially problems with virtual instruments that output to a mono audio track (e.g. bass). If you look at the peak during play, it is sometimes completely different when frozen and then when you export anyway! If you copy the frozen audio to a new audio mono track, then the export is no more +3dB, very strange! To me it is not transparent anymore in what case there is a +3dB gain! So I had invested some time in creating a sample project that shows the troubles and sent it to the support in December. They said they have logged it for review/changes and I still hope it is being fixed one day! ?

Don't understate! I would say after 25-30 years! ?

A lot of Plugin-Alliance plugins that use the standard preset setting (drop-down list in the plugin header). With these plugins it is painful to load presets with the VST3 version ?, because you always have to select the correct folder manually!! It is valid for bx_bassdude, bx_rockrack, Noveltech Vocal Enhancer, SPL De-Essers, SPL Vitalizer MK2, Lindell 254E, Millennia TCL-2, Vertigo VSC-2, bx_hybrid V2, bx_panEQ, SPL Transient Designer Plus, SPL Attacker Plus, bx_meter ... By the way this is also valid for other plugin manufacturers!

I avoided this, the PA deals were to expensive for me (with tax nearly $40)! ? Anyway I have almost all the plugins of PA that I am interested in.

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.

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!