Milton Sica

Thank you very much. I thought the DUMP was gone, but realized it's too big to post on the forum. I will send you a private message with the file in the folder I will share.

I need help about this. Please !

Error encountered when trying to delete tracks from the BBC Symphony Orchestra 1 64-bit version. Follow Dump. MM_Pelos caminhos_03142022_201528.txt

Attempting to convert Audio to MIDI is always running into an error that calls Melodyne.vst3 despite not having Melodyne installed on the system.

I'm afraid it might be something with a MIDI Clip that I imported into the project. Whenever I copy and paste it migrates from the original midi track. I'll attach the midi clip so if you can, check if that's it. Jorge_Ben_JorIve_Brussel.mid

Am I missing something from this update or has it made some different preference settings in the Copy - Paste and CTRL-Shift Copy MIDI operation? By doing such operations instead of copying, you are cutting.

@Noel Borthwick Very good your approach and also that of the other friends of the forum that are helping me a lot. In this line of thinking, it might be the case that the DAW itself increases in detail what it does by monitoring performance in execution and recording. Detailing better, if possible, the consumption of each plugin on the application and going further to allow the user in this future generated list to turn on/off plugins that are consuming more performance?

Thank you one more time. Your clarification was very important and I was able to isolate the problem that was happening with the Adaptive Limiter. I followed the steps performed in the IGNORE RACK FX operation and was able to isolate the problem.

Thank you very much for the clarification. So, to better understand, when I use the option IGNORE FX RACK does this? "The DAW recalculates PDC when effects racks are bypassed and when the audio engine is reset." My understanding is that turning effect to effect off the DAW, recognizing that ALL EFFECTS are turned off would execute the same IGNORE FX RACK rule. Interesting that latency is only reset when IGNORE FX RACK in MASTER. I end up identifying that one of the effects contained there is that it is causing latency. How to identify which effect is actually causing the latency. Turning off an effect and simulating the operation turns the audio engine on and off?

I use a Keystation 49es keyboard and experience latency when my master effects rack is on. As below... If I use the menu option "IGNORE FX RACK" I get "zero latency". Press the key and the note comes out immediately. But if I deactivate effect by effect, one by one, the same result is not obtained. Latency remains. My question is about what happens internally in each of the operations, because I think that turning off effects one by one until all are turned off, should be the same as when IGNORE FX RACK.

Thanks. I always record 44100/16 as I always export in that configuration; I didn't really understand the meaning of these 3 types of monitoring, because I didn't notice any kind of changes even increasing monitoring volumes via headphones or an external monitor. • USB/Direct Mono/Direct Stereo switch for monitoring mic, line or instrument inputs in stereo or mono I use active monitors, but the monitoring of the button itself, even at level 10, I found very low.

Thanks. Yes I record vocals and the virtual instruments with my keystation 49es keyboard. I only get "zero" latency when turning effects off. This on both interfaces. Both interfaces are connected to USB 2.0 ports. I don't know if in fact it's not a matter of Cakewalk integration with the Asio drivers of each interface.

Thanks a lot for the help. Yes I have the M-track drivers correctly installed. The video you attached is excellent and a tremendous way to get the interface installed. I don't really know what's going on. I thought the latency when recording instruments via my midi keyboard would be improved, but it remained the same as it had with the Tascam. I don't agree that the issue is just the price of the interfaces, because if the equipment establishes that it can record with the settings it says it has, there shouldn't be many of the problems I found. I don't know if it wouldn't be a matter of Cakewalk's own "relationship" with the Asio drivers of the interfaces. This is beyond my technical technical knowledge involved.

Thanks for replying, but do you think that's just the explanation: price?

I have a Tascam US-600 that has already been discontinued and I purchased this interface. I did some tests and comparing with the Tascam and I came to the conclusion that the Tascam, even discontinued, is much better and has much more features than the M-Track DUO. I have resumed using the Tascam in the studio and am using the M-Track Duo only to record external work and respecting the simple specifications of the equipment. Some problems I found in the comparison: 1) When commanding the recording of a track, a click is inserted. That's why I couldn't command the recording at a time closer to where it will start. I had to command before and after to remove the click from the recording. 2) In the middle of recording using a condenser microphone SAMSON - C01 Studio Condenser, noises are generated at random times, as a kind of saturation (all care with proximity, cables, etc. has been taken). It seems to be something from M-Track, because when I record with Tascam it doesn't happen. 3) I had a lot of problems recording instruments with my Keystation 49es due to latency when recording with effects. I was only able to "zero" the latency when recording without effects in the project. On the other hand, I started to verify that when recording MIDI, several Pitch and Modulation commands are inserted without me having moved any of the controls on the equipment. Anyway. I know there are several related situations, but they all appeared only after I installed the M-Track Duo whose hope was to overcome a discontinued interface like the Tascam US-600 to which I returned and resumed my projects. I appreciate if the friends of the forum can bring their opinions.

I was know about this notice. How is the opinion the friends this forum. https://www.gearnews.com/steinberg-discontinues-support-for-vst2-plug-ins/

I know this is not the best solution, but you might be able to overcome these crashes if you work with the error handler initialization variables. I think it's this one: ExceptionHandlingSeverity

Oh ! Ok.

For me, when I click "D" what appears is the screen to the side.

Thanks for your help. Can you attach the image where I can disconnect the synthesizers?

Why on my installation Cakewalk performance monitoring always puts one of the most demanded cores as shown in the image below? Is there a way to identify why the application is saturating only the same core always?

I enter this topic because I believe that a doubt about performance/CPU can also be clarified here. If not, I apologize and will create a topic of my own. My question: Why in my installation Cakewalk's performance monitoring always puts one of the cores being most demanded, as shown in the image below?

Thanks, 1. You can only do this from the FX Browser, not the console view. ------> It's a shame, because I think the operation in the console view would also bring a gain. 2. You can't, although I'm sceptical as to the usefulness of this in practice. It's unlikely you'd use exactly the same fx preset for any significant number of tracks. (...) -------> Because improbability happens to me in some situations. I have a preset that handles VOICE recordings, for example. They are different recordings of voices/vocals that I prefer to apply the preset to each TRACK than to put it on a BUS that will receive all the voices and whose mix I sometimes don't like. 2 (...) you can CTRL + drag the effect from one track fx bin to another track's fx bin. -------> that's what I've been doing.

Very good tip. Questions: 1) Can this operation be done only with the FX Browser? Not directly in Console view? 2) How could I do the same operation using my FX PRESETs?