marcL

Yes, exactly! And therefore it's even worse if the new recording goes up to the end of the loop region, instead of the punch out (if this is before the end of the loop)! And this is the new default ("Extend Takes to Punch Out Time" = off)! But anyway a lot of thanks for improving it! If I set the flag to ON it runs perfectly! 😊

This is one of the best bug fixes I have ever seen!!! 👍 (I have complained about it more than once) It improves working with Clip Gain a lot! It works now correct also in the Event Inspector (as @Panu Pentikäinen mentioned)! Thanks! Also this change makes life much easier! Great improvement! 👍 The only criticism (IMO): The setting "Extend Takes to Punch Out Time" should be default! Though anyway, I don't understand the need of this setting to be off, because if you set a punch region you NEVER expect recording out of its range IMO!

I had comparable issues with CbB on my major pc (unfortunately I don't use the newest CbB there). It happened several times that when I moved the first transient in an audio clip to the left that the clip contents disappeared. First I tried undo to no avail! Then I thought it could be the wave image problem only, but there was also no sound from the clip at all! Very annoying! ☹️ Luckily the clip was available somewhere else (1000 copies that's the solution!), but I had to redo all my Audio Snap changes again!

For me this one is €39.54! Don't drive me crazy! 😄

This update mania! 😉 It seems that WE all are not of value anymore, because we're not updated! 😆 And the Ferrari of the 60ties, the stradivarius violin, they have no value anymore, because they are not updated! How crazy is this kind of view? Modern times! I have a lot of plugins and other software that have not been updated for years, and I can tell you that I have less problems with them than with "modern, updated" software! But YMMV!

This reminds me of a similar bug in the Event Inspector Module! It does not work there either (and it is essential to be able to change values of multiple clips). But for me it is not that much a big deal, because meanwhile I've got used to press the U.S. key combination for CbB on my Swedish keyboards (does not match the lettering though). 😆

If I did not have Insight (1) Ozone 8 Standard RX7 Standard most of the PA plugins above then this would be an interesting deal! But just for the sake of the update it is not worth IMO. This is the crux with iZotope, they really don't value what you have. And updates/upgrades are so expensive!

I do this very often, I like to have my specific clip names! The only issues I have with this: Sometimes when I bounce a single clip (e.g. with Clip Gain or FX added) the clip name disappears (=empty). This happens very often, but not always (I had it today minimum 10 times). If I split a clip, move the contents in the parts, cross-fade and then bounce it to a single clip again, then the track name gets the new clip name, although all its parts had the same name. This is a bit annoying!

Wow, great! Many thanks! This is (was) a real big issue for me, because it has happened all the time!

Sometimes me too! But in other situations, especially for non-drums instruments I prefer using AudioSnap, because it does stretch the audio between transients. If you want a proper result, then the speed is not that much better IMO! But the difference is the stretching.

Some time ago I thought also that it should be possible to detect such transients properly! 😆 But my experience in the last years showed me that transient detection is an extremely difficult thing (in particular for non-rhythmic stuff). Yet there is not only one correct way to set transients, in general. Thus, other programs like Reaper, Samplitude, Melodyne, ... have their difficulties, too (they are also not perfect)! IMHO there is no way to get around manual correction when using transients. If you zoom in heavily (I always do when using transients) you recognize more obviously that a lot of manual work is required! 😉

I think this is not the problem, because if I remove the 2nd clip in the example above, then it works properly! This indicates that it has something to do with multiple clips in the same lane. Also if I temporarily move a clip to another, free lane, then it works most of the time. But the only way that works always properly, is to move the clip to an empty track and do the gain changes there (By the way this is a work-around that helps not only for this particular lane problem. Sadly, there is a couple of other issues in take lanes!) I have to add that this work-around is very inconvenient, because to be able to listen a lot of settings have to be the same as in the original track and also soloing gets more complicated.

Almost always when I use "Clip Gain" in take lanes it leads to the following problem, if there are MULTIPLE clips on the lane. I select a region of the clip and drag the mouse up or down in the clip's title area and usually, it works perfectly. But sooner or later in situations like the one below, it suddenly rejects to work. I select an area, put the mouse over the clip's title bar (the correct cursor appears, see picture #1), but when I try to drag down or up only a rectancle with "-INF -INF" appears and the clip gain of the selection is not changed! (picture #2) Is there something that I do wrong, something that I don't consider? Any help is appreciated! By the way my work-around in such situations is that I move the clip to a new empty working track, do the clip gain changes there (this works always!) and then move the clip back to the old track/lane. But this is not very convenient! 😉 picture #1, the correct cursor appears: picture #2, CbB rejects to change the clip gain, only "-INF -INF" is being displayed:

The last months are depressing! The only good deals IMO are always for plugins that I already own! 😢 There were minimum 6 great deals like the one above, sometimes even for less than I had paid. This is good for my purse, but not for my soul! 😆

Unfortunately I have no solution for the problem! ☹️ But you are not the only one that has problems using Melodyne within CbB. When I create a region FX with Melodyne I have to scroll around to find the contents, the position is never where I have the now time! With the transport I experience unexplainable behavior, too. I think all this began when there was a change in CbB that all Melodyne regions are represented in the same Melodyne view. Before I did not have such problems! But maybe I am wrong! 😄

There are other (IMO better) delay plugins that are always free, like Valhalla Supermassive NastyDLAmkII (Variety of Sound) Leet Delay (Sonic Anomaly) DD Delay/DD MonoDelay (Dead Duck) DubStation 1.5 (Audio Damage) Tempo Delay (Voxengo)

List of plugin companies that support offline activation - Effects Forum - KVR Audio In addition to their list of plugin providers with real offline activation: Acon Digital Audio Assault Black Rooster Boz Digital Dymai Sound eaReckon GForce JoeySturgis Kuassa MeldaProduction Rayzoon Soundevice Digital SoundSpot TBProAudio ToneEmpire You see there are some! It's a pity that PSP turned iLok, because before the would also have been on this list (some older plugins of them are still).

This is exactly the reason why I dislike more and more all authorizations bound to the local system! Today it is a very negative point to me, if a software uses something like this. I prefer plugins/software with real offline authorization, like an offline key, a file, a registry entry. This has also the advantage that the software is still installable if a provider should say goodbye! 😉

Because I've heard that sometimes it is only a "visual effect", I tried to bounce and was frightened by the result: The contents had really moved! And because the project had just been created I exclude the possibility of a corrupted project! Therefore, as a work-around I moved the changed clips to another lane and changed the starts/lengths of all clips that they overlap (instead of moving the splits). And then I moved the clips of the second lane back. Like this I had much more success! But still there were some minor issues, the beginnings of the clips in between were not aligned, but the rest of the clip was. I also saw that in the original clips the end of the first clip was a straight line in the length that was the discrepancy. If I zoomed in I could see visually how a clip was moved just by coping (with Ctrl-Shift-drag). To cut a long story short: IMO it is nearly impossible in such situations to position the splits and the crossfades correctly. And it's really a pain if you did a long manual work (days) to align and quantize the clips properly and then the result is moved by shifting splits and making crossfades. I agree with you that in some cases they are not really moved, but it is not always like that! So more and more I lose my confidence to CbB edits and have to check each single step. This takes a lot of time! 😉 Also: I see that the behavior is not always the same. If it had only to do with the zooming level, then I would expect it always the same! E.g. with the current project above I imported one long clip and split 6 short sections from the rest that I edited with Melodyne. When I tried to move the splits afterwards and make crossfades to bounce it to 1 clip again, not all 6 clips were behaving the same. With some of them the moving effect was only at the end, with others it was already at the beginning. Very strange! IMO CbB is quite solid for working with MIDI, recording audio and mixing 👍. But I would be glad if editing would be equally solid, because I prefer some things of it over other daws (e.g. the great, professional Radius stretch algorithms with AudioSnap). Sorry, for writing that much! 😆

Simply reproducible bug: Import an audio clip Split a short section in between Edit this section in Melodyne (region FX) and render the Melodyne clip (region FX > Melodyne > ...) In the clip's lane: If you try to move the splits into the Melodyne clip to make manual crossfades, either moving the splits or making the crossfades moves the contents of the 2nd clip arbitrarily. I have tested this behavior also in the newest version on my laptop (2022-02 build 039), because on my daw pc I use 2021-01 build 098. But it does not make a difference, this does not work in both versions definitely! There are so many situations where I have those annoying contents moves (not only with such Melodyne clips)! This is something that makes me sick the last years! Clip editing with CbB is a real horror.

In this case you don't use any shell plugins like Wave, Presonus, ... ! Because e.g. Waves shell takes about the time of 100 light plugins IMO, even if you have only 3 plugs of them. Also there are some plugins that take eminent more scanning time than others, it is not only quantity, but also coding quality. But YMMV! 😄

Yesterday when I was working on some 2nd vocals it happened that moving a transient (I think it was the first one) caused to grey out the clip (not only visually, but also the audio). Neither with undo nor with moving it back I could make the clip contents appear again. The worst thing is that it happened in 2 other clips, too! As in your case I was working in take lanes. Even re-importing the clip(s) and doing it again led to the same undesired results. Only when I was inserting a new track, re-importing the clip to there and doing the edits again I had success. Anyway, I think there are issues with working on take lanes, specifically if I move the contents within the clip area (alt + shift + drag). Following operations lead to strange behavior (e.g. a crossfade may move the contents of the 2nd clip). It seems that with some operations the internal values of clips get corrupted! Such problems are documented back to the Sonar Platinum times! I have almost given up that this will be fixed one day! 😆

This one is really good, I like it. And it is one of the most CPU friendly delays that I have! I can recommend it.

Nothing for me! I prefer Bass and Drums more in the old style! 😄

I agree to this statement with regard to the new amps. The older amps like Dominator are better in respect to dynamics IMO. I absolutely agree! But like you I use an amp simulation more like a real amp, i.e. I set up manually by using the controls and not the presets. Generally I have the impression that factory presets for amps are not worth a lot, because the gain and response of each guitar is quite unique. Thus the presets may not match. It is even worse if you use a real stomp for the recording!