marcL

It is all about article lotion! No more about arrow ranger. Bag quickies have lost its way. The lone cowboy gets tired.

I say "yes, I am an idiot"! And I have been and still am really an idiot in many ways!

I would have preferred a simpler way to simplify the inserting of articulations. In my vision only the visibility of the articulations would be changed, i.e. they would stay MIDI notes in the clip. This would avoid all the trouble with editing and moving, because it would be apparently the user's job. And changing an articulation would be 100% the same as changing a common MIDI note (e.g. selecting shows the contents in the Event Inspector). So what do I mean with visibility? I imagine something like an articulation lane that is always above (or below) in the PRV. The user can define the note values that are displayed in the articulation lane (some kind of map as in the current implementation). But as I said the articulations would be treated as simple note values and thus behave the same when moving clips/notes, deleting/exporting/importing clips!

Exactly, and it gets even more complicated, because sometimes the articulation must be tied to a single note, sometimes to a chord, sometimes to a measure position, sometimes to a clip and sometimes to the track. It is all depending on the kind of articulation! I think the developers have created themselves a very complex and tough challenge! ? So I wonder if this kind of separate articulation setting is really a win for the users, 'cos so many things can go wrong if it is separate and you have it not in view. I guess I will prefer the old way of articulation setting that is full under user control! But first I will give the new "thing" a try. An additional thing that's come to my mind with the new articulation setting is whether it properly supports MIDI clip import and export!

This is exactly the point. Finally I have to clean up after each plugin installer, because they mess up my systems: Some install AAX (64 and 32 bit, with another interface I don't remember now) Some create additional copies in a Steinberg or VstPlugins subfolder (64 and 32 bit) Some create unnecessary program subfolders for documentation only, but I store all plugin documentation in one location only (no program folder), it is easier to find it. For many you cannot stop creating Vst3 even if you use Vst2 for some reason. This may cause issues, because the Vst3 folder is always scanned. Some create menu entries with some rubbish (like site link, uninstaller that can also be accessed in Windows, ...). If you have a lot of plugins, then you're menu tree gets full of rubbish for almost nothing (I excuse those that have an exe)! Many do not remove all installed files when you remove the plugin and more So in the end it takes more time to use installers and installation managers (if you want it to be clean) than when you install plugins by hand (zip files) like in the old days! ?

This sounds quite "hubby" to me! ?

We had this discussion once before! But the thing is I don't like to use a hub on my laptop. 'Cos another name for a laptop is "mobile computer" and with a hub it is not so mobile anymore! ?

This ^^^ and that you can only use the plugins on 1 single computer (I don't have any free USB's on my laptop and they don't support iLok any longer).

I like that it is now possible to move the clip split in a single track lane with the Alt modifier. But there is still this issue that in one situation it is not possible to make a cross-fade at the split point. And there is still this issue with the clip gain for a selection if you have multiple clips in the lane. 1.) Crossfade Problem: Split clips on 2 lanes at the same position Remove the rear part in the 1st lane Now it is not possible to cross-fade with Ctrl+Alt+Mouse in the 2nd lane (the cross-fade cursor does not appear), only if the split location is different to the 1st lane 2.) Clip Gain for selection: Insert an audio clip into a track lane Split the clip at any position Set the track to "Clip Gain" Making selections within the rear clip allows you to adjust the gain for the selection in the clip header as it should be. But trying to adjust the gain for a selection in the leading clip fails although the gain cursor appears on the header (in the popup appears "-INF" twice). To change the gain of the whole leading clip is possible though!

Waves? V12?

This is another bad example what installers can do! Something like this could never happen with a zip-installation!

IMO it's the "new" Middle Ages in software development and regrettably also in a lot of other areas in modern life (it is not allowed anymore to say your opinion, it's always the risk that it is interpreted racist, not eco-friendly or anti-women). I hate those plugin installation managers! Honestly, it would be much more user-friendly if we had zip-files to extract the contents with a simple readme instruction! It takes so much time to clean up what most of those silly installers do!

For me it is the contrary, because most of the plugins today allow to use the mouse wheel just by positioning the mouse over a control. Thus if it is required to click the control first to use the mouse wheel, I often forget the click and that causes sometimes that the previous clicked control is changed. The bad thing is also that this control is not in my current focus, i.e. in the worst case I even don't know what control I have changed, but in all cases I do not know the old value. That's why I prefer that the mouse position is relevant to change a value and not a click on the control!

Unfreeze synth this is a good point! Today I found out that all my settings were lost when I had unfrozen Strum Sesssion 2 in two tracks. This is really a pain! Good that I write down a lot of my settings in a text file for each song, so Iuckily I could recover the mess! But more and more I get the feeling that it is better not to use freeze for instrument tracks, but instead bounce to a new audio track and mute the instrument track. Like that you avoid to have those +3dB problems with mono tracks and it is always possible to redo the instrument without losing the settings!

I did this more than once!

This is true that if you have less transient markers the risk of problems is reduced! Me too, I reduce the automatically detected transients pretty much, but most of the time I cannot reduce it to only 1 marker per bar in my case. I also noticed that if the corrections (stretching/compression) are really minor, then there is often no problem. Again, I agree with this. It is also my experience. But if you do this, then you cannot use the automatic quantizing, i.e. you have to do it manually, since the automatic quantize tries to align it to proper beat positions (whatever you choose 1/16, 1/8, ...).

I am also not in love with the current export naming convention in CbB. For some time I did the renaming manually, how laborious if you often export tracks! Then I tried to use shell renaming and there was sometimes a whole mess, because the shell worked recursively. In the end I wrote my own rename program, because there was so much trouble! Also I do not agree that it makes sence to use the internal track number for export, because when you do not create your tracks in order, i.e. you insert new tracks in a later state or move them up or down, then you get a real mess if you re-export some tracks (track number may have changed)! Thus I support absolutely a track export name configuration in CbB! IMHO this would be a very valuable addition to make life easier!

There is the same behavior when I bounce a clip. Most time the solo and mute settings of tracks (other tracks?) get lost! But it is not just since the latest version.

I don't want to frustrate you, but for me the list of tweaks increases with each Windows update! For me Windows does not get better but worse! Since the start of W10 there was only 1 single tweak that I could cancel, because it had been fixed! ?

I cannot remember any Windows 10 update that had something new that I really needed! Most of the time the updates are only a pain, time wasted, settings reverted, some unnecessary cloud play things (child stuff), ... If I had the chance to choose, I would still use the first Windows 10 version!

In addition what @John said, if you use the right click menu to insert a new track, you can select one track in the same breath to define where the new track has to be inserted. I like to use it that way, because often you do not want the new track to be added to the end.

It's strange, the same thing happend to me, too!

Lately I wrote a harmless contribution and there was 1 word banned. For me with non-English mother tongue it is difficult to guess which words could be banned! ? This is why I made the precautionary measure to prevent that my "sentimental" message cannot be read! ?

No, absolutely not! I worked myself a lot with codesets/codepages... as a professional, but I saw in the 21st century that many big software companies (like MS) make a real mess with it! It seems they do not understand the concept, that's why they finally jump to unicode and that's better like that! ? Yes, Mac is definitely not an alternative! It's made by a similar dinosaur! This is the pain with those W10 issues, there is actually no real alternative!

In the Middle Ages people were tormented by Black Death. Today we are tormented by Microsoft! I think in no other company there work as many id###s in the software development! The last month I had dozens of problems with the awesome W10. The newest st###dness are their language and regional settings. It is a whole mess, they link everything that has nothing to do with each other. I envy the Americans for their simple language situation, everything English! Yesterday I simply changed my date/time display settings and see what happened? Suddenly all umlaut characters in non-unicode programs were displayed as garbage! So it seems for Microsoft engineers umlauts are date/time characters ?! The sad thing is that all the time it takes to solve those issues is lost for music creation! ?