Milton Sica

PLUGINS PRESETs are not stored by the project, but by the plugin itself. So, when you open the project that contains the PLUGIN, it is its operation that retrieves the last PRESET used and not Cakewalk.

Have you tried using the plugin loading approach variables to check if there is a problem with this operation ? This only happened to me on the first load of a project the first time I ran that version. Afterwards, the projects were loaded again in the same acceptable time.

1) APPLY EFFECTS - NORMALIZE - MULTIPLE TRACKS - NEW OCCURRENCE - OLD PROJECT. I selected multiple tracks to normalize to -3 Db. Tracks 14,15, 16 before Normalization command Tracks 14,15, 16 after Normalization command Note: Note that the content of track 15 has been replaced by the content of track 16

I'm constantly testing the version, as I'm reevaluating some projects. Below are some observations I've made so far when approaching these old projects, generated in different versions of the application, so I can't confirm that they would be happening in new projects. I advance my evaluations to the developers' evaluations. 1) (SOLVED) - I HAVE TESTED WITH VARIOUS BUFFERS SIZES AS ADVISED IN THE DOCUMENTATION AND THE OCCURRENCES, ALTHOUGH THEY CONTINUE, ARE NOW IN SMALLER QUANTITIES. PLUGINS - PROCESSING - CRASH - I started using Ozone 10 for mastering. Until then I used Ozone 9 Elements. This accomplished his assistant quite quickly. Ozone 10 is slower, in addition to presenting several clicks in its process, when it does not present audio abandonment due to code (19). SCENARIO: Project I used the value 3. I recently changed it to 1 and will do more tests. 2) APPLY EFFECTS - NORMALIZE - MULTIPLE TRACKS - Occurrences no longer happen.

?????

Forgive me, but if we are in a moment where EA recognizes a BUG, even if pre-existing (????), it is difficult for me to understand that this is not corrected in the version we are testing, but only in the final product SONAR. So put it in your promotional post: "PREEXISTING BUGS, EVEN IF CHECKED IN THIS VERSION, WILL NOT BE FIXED." Even though it seems like a huge contradiction to say that more than 60 bugs were fixed, but this one no or other preexisting bug. @msmcleod @Jonathan Sasor @Max Arwood

The images are the send listings that are enabled when I click on + to make a send.

https://www.bandlab.com/products/cakewalk As far as I know, this is the link where you can download the previous version of this EA. I did the same and the installation didn't change my settings at all, but that was my experience. Good luck !

I have been reading other posts that address the topic in the new version. My opinions about prices and product defects were classified by some, including the software's Chief Engineer himself, as MEHHHHH (bad). However, when I read that bugs will not be fixed in this latest version before it is priced on the market, I question, it is not a criticism of what you said, but then what would be the point of bringing an EA for the community to test if not to verify it? developers to fix bugs? It's just an opinion on the topic and to be supportive at this very confusing time about the future of the tool.

From this EA. When trying to command SENDs on the BUS, for one a list of sending possibilities appears, for another another list. Any explanation?

I posted in the main topic that I started to face problems with normalization when performed on multiple selected tracks. I already reproduced the error in several projects. I gave up normalizing that way.

Yes. In all the projects that I have opened and tried.

Just read the release approaches.

Good thing we're not talking about cars. I don't know one person in the whole world who would buy an automobile knowing it has a known amount of defects/bugs. That's what I'm talking about. If it were a car, would you buy it and put your life/family in it? And I close my posts on the topic.

New SONAR ???? Older users, we are sure that this is not a NEW SONAR, but an application that has enjoyed all these years when it was sold as free and had the collaboration of the entire user community. What comes around, and I'm testing the early access version, is an attempt to sell something said to be new, but "current" as we know it to be.

Because I think it's a huge mistake in the company's strategy to go for a free-pay movement and an application that, we know, has numerous bugs. The question is quite simple and direct: who will pay for a tire that, at any moment, will present a puncture ???? The least one would expect is that the application delivers everything it promises without errors. You're talking about a "banana" as if nobody knows what's inside the skin. Excuse me, but your corporatism adds nothing to what we, users, want. If we're going to pay for the "banana" we want to know everything inside and how it works.

Because I think it's a huge mistake in the company's strategy to go for a free-pay movement and an application that, we know, has numerous bugs. The question is quite simple and direct: who will pay for a tire that, at any moment, will present a puncture ???? The least one would expect is that the application delivers everything it promises without errors. While it was presented as FREE, we users noticed some bugs, but I don't know of any that pay any dollar to receive errors.

I only showed the end of the wave in both moments. It's pretty easy to play. 1 - Select multiple audio tracks. 2 - Command NORMALIZE. I have normalized at -3 DB. I can't say that this happened in this EA, because I didn't previously normalize my audios. When I started to do it in this version this appeared. It was normalizing 5/6 audio tracks.

CONFIRMED CONFIRMED! When normalizing multiple selected tracks, a random track is out of sync in the project. This does not happen when normalizing track by track. I did it several times and noticed that this always happens on the last track selected. Original track After normalization

I started to notice that after normalizing a set of Audio tracks, some of them are becoming desynchronized in the project and inserting noise at the end. I'm going to try doing the normalization track by track and see if the problem occurs or if it's just in the multitrack normalization process.

@Noel Borthwick I have worked on several projects. I get some crashes on AUTOSAVING, having to end the process in the process manager. In some situations I have observed a slower performance, mainly when using the Ozone 10 mastering assistant, sometimes making the sound crackle and even crashing the audio engine. Something that didn't happen in the previous version.

Yes. In fact now this information is EXPLICIT in the post at my suggestion to @Morten Saether This information was not included in the first post made.

Yes. In fact now this information is EXPLICIT in the post at my suggestion to @Morten Saether. This information was not included in the first post made.

@Morten Saether So I think you should EXPLICITLY warn in the disclosure that this version, even though it is an early access version, will not have a reversal.

@Morten Saether There is no link to the rollback version for the version if any.