Milton Sica

I liked the comparison to a bad cake and its frosting. I would say that Mastering is the "yeast" that makes the cake rise, not the frosting.

@gustabo what makes you laugh so much? Can you explain something technically or contribute something positive?

I didn't understand the "language expression accent" if you were being ironic, sarcastic or joking. What I meant is that it would be great if I could have access to this documentation.

Where is this specific topic, because this topic too, as far as I understand, is in the wrong place.

I thought it would be better to post it here, since you've already been following the problem. I just installed version 105 and what surprised me is that, unlike the previous versions, which kept my Templates settings, etc., in this installation they disappeared as if I had nothing. In this installation it seems like a clean install was done.

How wonderful it would be if you could have access to this documentation.

Could you explain how the "ROBUST SUPPORT THAT SONAR GIVES TO WASAPI" works? I believe this would be important to dispel many of the doubts we have about the use of this or that driver. Thank you!

I would like to thank everyone who has contributed to this topic and, at the same time, invite you to share your thoughts with the FlexAsio developer, who has been very open and responsive in addressing the various concerns I have raised with him. I believe it is very important that the tool he created be developed and improved, especially since we, Third World users, have a lot of difficulty, due to financial issues, in continually improving our hardware/interfaces/modernizations. From my own experience using a Tascam US 600, I have found it to be a great advance for my production work. Thank you all and here is the link to my topic there. https://github.com/dechamps/FlexASIO/issues/246 The link below is documentation that the developer provides us about the backends. https://github.com/dechamps/FlexASIO/blob/master/BACKENDS.md

I posted your considerations in the issue item I opened on FlexAsio and the developer made these considerations. I don't see how this has anything to do with the issue at hand, but I'll just comment on a few points to set the record straight. It shows in the Reg Edit app under ASIO. Just incase it causes trouble easy to delete. FlexASIO has an uninstaller. There is no need to mess with the registry. Flex ASIO came in at 263 ms so only 9 ms late. Depending on the FlexASIO config used, especially the backend, the behavior of FlexASIO can vary drastically. For this reason, just saying "FlexASIO" without mentioning the config used is almost meaningless. It is impossible to reproduce these results without knowing which FlexASIO config was used. WDM mode was always a little worse than WASAPI shared and this is why Asio4all sucks. This is surprising as WASAPI Shared uses WDM behind the scenes (with additional latency on top of it due to buffering). Maybe the particular WDM client implementation in ASIO4ALL is not behaving optimally with their particular hardware, I don't know. So I would conclude that unlike Asio4all, Flex ASIO is an ASIO driver. This is obviously false. ASIO4ALL and FlexASIO are both ASIO drivers. It is possibly invasive if you have a interface you connect from time to time. Like the Steinberg Generic, Magix etc. Generic ASIO driver have been know to take over the Sync and Caching dialogue and only way to stop this is deleting in Reg Edit. I don't know what this is supposed to mean, but there are indeed cases where ASIO drivers can interfere with each other, especially if the ASIO Host Application attempts to initialize several drivers at the same time. See for example #86. I don't know if Cakewalk is susceptible to similar issues.

I believe so, because he has been very responsive to a call I opened there.

Very good. I'm testing it, but I haven't reached that level of depth. It would be great if you could send your report to the developer. Thank you very much for your availability.

Anyone else using this ASIO driver called FlexAsio to share their experiences? The project can be found at: https://github.com/dechamps/FlexASIO @Noel Borthwick @msmcleod

Hey there. I didn't know about Ardour. I'll try to use it. With REAPER it took me a while to understand the workflow, but now I understand and produce well with it. If Ardour is open source, even better. Thanks for the tip.

With all this discussion about SONAR's pricing and the fact that the paid tool clearly still has many errors. Many of them already exist in the free version, I decided to continue using the free tool and to use others that have free versions and are more consistent. That's why I started eliminating all plugin presets, ProChannel, etc. from my Cakewalk productions, using only the plugins individually. This has already given me a great advantage in migrating a project from Cakewalk to Reaper, which was the one I chose for this new stage.

Hello, thank you for your interest. In fact, simply turning off the PC did not solve my problem, because if you put a series of plugins on the PC, even if it is turned off, that is, not "used", the application loads them ALL waiting for the possibility that the user turns it on again. I discovered that the only plugin/module that does not allow deletion from the PC is the Equalizer. So I am solving my problem by creating an "empty" preset and distributing it to all the TRACKS/BUS