Milton Sica

After tireless testing with old projects and some new ones, I am very clear that this version is much slower in operations, opening, closing, saving.

I cannot conceive that this will be the last free version and, above all, there will be no rollback to the last version.

These facts are fully reported by several forum friends in their comments.

I installed Next, but I've since uninstalled it, as I didn't think it was settled enough for a more consolidated approach to professional/creative use.

I'll wait for the official publications.

21 hours ago, David Baay said:

Not sure why the error detection code would mis-report the cause, but if you were already running a higher MIDI buffer size, I'd recommend going back to something more typical like 50-200ms and looking for related possible causes like misbehaving MIDI FX, Algorithmic MIDI-generating plugins or audio plugins that have excessivly high look-ahead buffers. Maybe start by bypassing all FX and see if the problem persists. And, of course, try to correlate the appearance of the issue with one of the last few major changes you made to the project content/routing.

Thanks for the help, but unfortunately I made several changes of this size and didn't get very acceptable plugin performances. The audio engine keeps crashing.

I started to receive audio abandonment (9) more consistently, which is recommended to increase the MIDI preparation buffers.
However, I am already at the maximum allowed (1000) and I continue to receive such abandonment.

This now happens with this version.

54 minutes ago, msmcleod said:

Sending to a compressor is something I rarely,  if ever do.  Effects such as compressors/EQ's are almost always inline.

Once you get beyond the entry/prosumer mixers, a lot of the pro mixers have dynamics processors on each channel for this reason.

The exception is when you're doing parallel compression, but since most software compressors have a dry/wet mix control, even that isn't needed any more. 

I guess you might want to do parallel compression on many sources (e.g. all the parts of a drum kit), but even then I'd be more inclined to do it as an insert on a drum bus than as a send effect.

The most common send effects in the old days were Reverb and Delay, and occasionally something like chorus for a thickening effect.

 

Thank you very much.

In fact, I thought that, like CHAINS OF EFFECTS, I could also use CHAINS OF SENDS.

For the voice, for example, I direct via send to 3 AUXILIARY TRACKS. One of them has a Reverb Room, the other has a Reverb Hall that has its own auxiliary track that contains a SIDECHAIN compressor and, finally, the 3rd track that has a DELAY effect.

This way I can, individually, work better on the environments.

This technique has been very useful for me.

I thought maybe this could exist in CHAINS OF SEND.

As I said: I have the NEUTRON UNMASK the Guitar and KEYBOARD Bus. So, from the MAIN VOICE BUS I make a send to each BUS (GUARTARS and KEYBOARDS).

I thought that maybe it would be possible or useful to be able to generate this CHAIN OF SENDS that I make one by one and, when clicking on ADD SEND: call this chain.

I don't know if this would be a "trip" of thoughts, but I thought.

These SEND CHAINS would be something:

FREQUENCY UNMASK SEND CHAIN.

SEND 1 - SEND TO GUITAR UNMASK
SEND 2 - SEND TO KEYBOARD UNMASK.

In such a way that the operation could be carried out just like the EFFECTS CHAIRS.

23 minutes ago, JohnnyV said:

(....)


 

Thank you very much.
In order to improve more knowledge and improve the production of my own songs, I am going through old projects.

Coming up against my own ignorance when I started the journey and envisioning improvements I could put into my future creation flow.

Most of the projects I've been working on are already on social media and, when I listen to them, I actually see myself in so many things I've learned since then.

In this case, I thought I could use the EFFECT PRESETS model, too, instead of referring to SEND one by one.

For example: Send to a COMPRESSOR, then to the NEUTRON UNMASK and so on.

21 minutes ago, msmcleod said:

No - nothing like that.

The nearest thing to it would be a track template,  either save a single track with all those sends on it as a template, or alternatively save an Aux track with all of those sends on it as a template (then your existing tracks could just send to that Aux track).

Yes. I thought about that too, but not whether there would be any loss or type of problem in the treatment of what you receive and send.

Not to mention monitoring issues.

What do you think ?

The use of chains of effects has been a very productive way of working.

A little while ago, after having the need to make several SENDs, I reflected that, if that were the case, I could also create SENDS Chains to, in a single insertion, send them to several paths.

An example of use that would have to send:
UNMASK plugin on the Guitar bus
UNMASK plugin on the keyboard bus
MCOMPRESSOR plugin on the drum kick bus.

The question is: Is there a way to create a CHAIN OF SENDS?

19 hours ago, Jim Fogle said:

...

I made this alert as soon as the original post was released and there was no such detail that was only included after my post.
It would be important that the comments made about the first EA were removed to avoid this type of approach or even the insertion of a mark by the development team so that the problem alert brought by the user could be viewed by those who enter.
This way we would avoid citations and approaches about something that has already passed or been corrected.
Something like my comment about the truncated help URL that was corrected by EA 62.

19 hours ago, Michal Mikulski said:

I tried it, I wrote ExceptionHandlingSeverity and value to 7 yet I still wait for it to load past Preparing project... a long time.

Thank you though for your efforts! I appreciate it. 

7 is the value I use. There are other values contained in the documentation that, perhaps, can help you identify.

https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=INI_Files.4.html

Many messages

This is the same error that was already reported by another friend on the forum. In my case when loading a project into the ElectraX Plugin.

On 8/31/2023 at 3:59 PM, Morten Saether said:

Misc.:

• Help URL in crash notification displays invalid legacy subdomain

 

For me this error remains.

7 hours ago, Michal Mikulski said:

Unfortunately I don't understand what you mean.

 

If i don't mistake....

2 hours ago, gustabo said:

If that were so, opening a project on another machine would cause an issue.

Take your tests and evaluate.

44 minutes ago, Steve Moddelmog said:

Noel, can you explain what you mean by that?  If I load an existing project, CbB knows what preset I used for each plugin and properly loads those presets.  And if I have modified them in some way without saving over the existing preset or saving as a new preset but then saved the project, I'm pretty sure those modifications get loaded with the project too. So I'm sure I'm just not understanding what you're saying.  Thanks.

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.

12 minutes ago, Michal Mikulski said:

When opening a project, I'm stuck on this step for a very long time. I wonder if it has anything to do with melodyne? When I opened a project without melodyne it opened quickly. Weird... Might be something else though it's just a hunch.

 

Regards

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.

?????

21 hours ago, Noel Borthwick said:

@Max Arwood we have verified that this issue is specific to saving to a UNC path and its definitely a preexisting issue. We'll fix it in the Sonar codebase but the fix will not be in CbB for this reason.

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

1 hour ago, Glenn Stanton said:

because buss 2 has those in its FX?

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

On 9/9/2023 at 8:00 PM, arvmetal said:

Pretty crappy update, is unusable, as I open any plugin starts to flickering and slows down my PC. Does anyone know how can I revert to the old version without uninstalling?.

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 !

8 hours ago, Will. said:

Well, dont expect any update and bug fixes for this version. It is sadly in the process to collect its 401k. An early retirement. 

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?

4 minutes ago, Noel Borthwick said:

@Harley Dear thanks for bringing this to our attention. This is the whole point of early access so we can squash any unnoticed issues.
Even bug fixes can expose problems so its critical to have a bigger pool of users such as you do final tests.

My only request is that rather than making new threads, any EA related issues should always be reported in the main EA thread. Otherwise we risk not seeing it.

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.