mettelus

In addition to the above, volume automation is all you would need. When set to -inf, that is "mute." Keep things simple and just work with automated volume. @57Gregy's recommendation is even simpler (no need to mute things that are not there).

After looking this up again, there did seem to be a conflict with installing DimPro 1.5 over the version included with SONAR 8.5. This link walks through the clean uninstall of that older version (some regedit work to this). You may want to go that route, then walk through an install of whichever 1.5 version you prefer. Quick side note to the above... the MASSIVE amount of the DimPro download is the Multisamples directory (roughly 3GB). Prior to doing the above uninstall, I would copy that entire Multisamples folder to a safe place. The actual DimPro application is only ~30MB (no samples included). If you have a(ny) CCC download already, you can use 7-zip (or similar) to extract that app installer from the 3GB download (is the top-level file), run that installer, then move the Multisamples folder back. You will also need to hit F5 to refresh the browser directory so it can see the programs to complete. There were issues over the years of some samples/programs being bad, so having a backup of a properly reconstructed Multisamples folder is highly advised.

Try simply installing the CCC version over what you have first. Most installers verify files as they go, so it should make the installation "whole" as it goes.

+1 to this, definitely check it out to convince yourself. You can test it by loading as many Kontakt instances as you have instruments (sans loading the samples) and see what the Windows Performance Monitor is telling you for having multiple (empty) instances of Kontakt enabled.

OBS Studio is a free option to get loopback capability at a system level. It is a bit of a pain to get familiar with at first, but it does expose audio/video feeds to other apps. Or you can capture system audio/video with it and import that into a DAW/video editor for post-processing (that option may be simpler for you, depending on what your needs are). Quick edit: Also depending on your source, there are apps to simply download media from urls (e.g., YouTube) and bypass the "real-time" recording. Again, that depends on what exactly you want the audio from.

Have you tried installing it via the Cakewalk Command Center? For legacy products that you registered, that is probably the easiest way to install those legacy apps.

I had this happen and think the "solution" was an odd one. I needed to have both Native Access and the iZotope Product Portal logged into for the issue to reset for me. It seems those two apps are linked in some fashion, so the Product Portal alone wasn't resolving it. This was shortly after the merger, but may still apply in your case.

No worries, I hope you are feeling better soon!

This made me wonder... @azslow3 knows the construct of CWP files well, so he may have something already made for this. He could probably extract the tempo map from a CWP as well, since static tempos are not always applicable. I forgot offhand who made Project Scope, but it is worth shooting them a PM as well to ask.

Something to check real quick... Windows may be doing this to you. In Windows Search Bar, type in "Sound Settings" and at the bottom of that window there is an "Advanced Sound Options" at the bottom, click on the bar right below that. For sanity sake, check the volumes in the next popup (App volume and device preferences). and make sure your device is at 100%. Windows will let other apps adjust those (at a system level), so when things go wonky, that is something to check.

I have been meaning to submit a feature request, so just tried to post on the their forum, but the post button cleared the page in Firefox with no feedback (I did think ahead enough to copy that first). Ironically, it all fits into that tiny window in the "Feedback" within the app, so at least I got it off to them. Not sure if you re-tint things, but this was the crux of the request (for a "Clone Tinting Mode"): **** I have been using the water color brush for subtle (sometimes more extreme) clone tinting to often Paint/Mix/Blend. Most often this is done with very little opacity and water in the brush. However, to achieve this requires a bit of manual muscle memory (and the second one has bitten me more than once): Diffusion must be paused when doing this so that there is the precision required. When finished, the layer must be specifically dried (Shift-D) so that diffusion doesn't take over. Where this has bitten me is I am zoomed in while working, so if I move to another area and shift the brush (which re-starts diffusion), I do not realize this has happened until too late. My personal experience has been the watercolor brush is ideal for "clone tinting," so the feature request I personally would be to have: A specific "Clone Tinting" option (for me this could be locked to the watercolor brush). When in "Clone Tinting" mode, diffusion would be paused by default. After that initial mode selection, diffusion on/off would be at the discretion of the user, but entering that mode would always pause diffusion initially. When either exiting or changing brushes the layer would be dried. For me, this is more of the safety net, whereby changing brushes would automatically 1) dry the layer and 2) exit "Clone Tinting Mode." A big icon similar to the "Pause Diffusion" on the main work space would also be ultra-helpful. This feature could certainly be expanded in the future to include more brushes/options (other users may have more uses for this). For me, I have been bitten by forgetting to dry the layer, that this would be an immense help.

Escape Motions is having a 40% off "Back-To-School" sale across the entire site for those that are interested (including upgrade pricing I "assume"). All of the products with the exception of Rebelle 7 have been static for years, but Rebelle 7 (Pro) added some significant advancements when it was released last December.

Yeah, I am not sure if Notion has been touched at all since it was absorbed beyond the initial streamlining. Notion 6 has been static for years now.

Another thing you can try to confirm quick is another environment to confirm it is also persistent outside of the vocal booth to eliminate resonance in the booth as a factor.

In addition to "exclusive" modes that may exist within a DAW itself, there is also one within Windows specifically, so it is likely that Windows resorted to its defaults when it saw the new device. In Windows Sound Settings->Sound Control Panel->Select the device and then "Properties" (on the first "Playback" tab at the top). On the Advanced tab at the top of that next popup, be sure the "Exclusive Mode" settings are unchecked. You may also need to repeat this for the "Recording" tab in the Sound Control panel, as they are separate to Windows.

Do your audio device preferences for that project show the old device? Even if not, you may have to manually re-assign driver modes (something other than ASIO and then back to ASIO) to force the project to "forget" the old device ever existed. Projects try to maintain device info internally, so it might be trying to communicate even without the old device connected.

That is a real bummer... I thought they were actually closing shop so wondered why they didn't just unlock the last version to be perpetual, but alas they are still around and this blurb is right near the top of their page: "MakeMusic has partnered with Steinberg, the makers of Dorico, to offer exclusive crossgrade pricing on Dorico Pro." Since they are still around, the disabling of the activations of paid for versions is a bit odd to see, but they are forcing a new product onto people.

Cakewalk has the built-in drum replacer, but I forget now if you can use samples from outside that plugin. I seem to recall it could only use the sounds it came with and only covered a few kit pieces (kicks, snares, toms). As far as 3rd party plugins, MDrumReplacer offers all of the drum sounds from MDrummer (which is like 90GB of samples) and allows for fine tuning of blending, but is a bit pricey when not on sale. For what you are doing, try the internal Drum Replacer first and see if an FX chain on the blended replacement gets you want you want. Drum Replacer is a Region FX (like Melodyne), so can right click a clip->Region FX->Drum Replacer->Create Region FX. Quick Edit: What he did in that video above you can also do by dragging the audio onto a MIDI track then using the MIDI to drive a kit (very similar to what he did actually). The blending would then come from the faders between the associated tracks.

As mentioned above, you can simply insert virtual instruments and assign the outputs of MIDI tracks as needed to them. Also bear in mind that you can similarly point tracks within Guitar Pro to virtual instruments via LoopMIDI. I posted a discussion on that a while ago here. For jamming purposes, it may be simpler to stay inside Guitar Pro if that is your preference for composition (it also has more tools and playback options than you will find in a standard DAW as well). Quick edit from reading your other post. MIDI is simply note data (no audio), so you need to insert virtual instruments to play those notes so that you can hear them.

That is the only version guaranteed mpox-free... all other BLAHs use at your own risk.

Grab something like TreeSize Free and check your C drive. Many programs leave a massive footprint in the C:/Windows/Installer folder (that is a hidden system folder) by default. Folders that begin bubbling over 4GB are my candidates for junctions, but that particular folder cannot be junctioned or it disables the Windows Installer. Temp files in Windows/Temp and Users/appdata/Local/Temp also build up (those can be purged). The User/Downloads can be moved as well (or deleted depending on preference), but a utility that lets you see folder size is where to start.

Wow, I just found out they dropped the LP kits earlier this year (more rumor is that Gibson asked them to stop selling them). I am glad now that I didn't take the time to write a review up (did it on here instead)... they totally obliterated even any reference to them ever existing through StewMac. Quite a few Amazon links show, but those are all dead too.

+1 to both of the above comments. The embedded Windows defrag is actually sufficient for most instances, but it doesn't have the ability to "consolidate free space" on a drive that I am aware of. That routine is intensive and doesn't need to be run often at all (I run this about once per year), but what it buys you is massive writes (like a "Save As..." on a cwp project) will have enough space to write everything on contiguous tracks. That will cut down on fragmentation issues even occurring, since that is caused by the system filling "holes" that are available. Data management is far better than it used to be, so the system typically finds holes big enough to fit entire files in them when possible, but that doesn't prevent it from scattering associated files all over the place (even if individual files are not fragmented, the seek times will go up due to this).

They recorded Yoko Ono in 1970. Some are still not over that one. https://en.everybodywiki.com/List_of_recordings_made_at_Abbey_Road_Studios

I am not familiar with Monster Drums, so that may very well not be GM mapped. Another trick when mapping existing MIDI to a new instrument (I am "assuming" you have a single MIDI track with all of the kit pieces on it, i.e., one channel (?)... if not this gets more complex). If you expand out the Piano Roll View, you can run the mouse up and down the keys to fire off the kit pieces (to check what is where), and to move MIDI rows (kit pieces), you can 1) select the piano key (on the left) to select all of the data on that entire row, then 2) shift-drag (to preserve timing) that data selection onto the proper kit piece. When moving that row up/down, it should also be firing the kit pieces it passes over as you do so (be sure Input Echo is on). When working with multiple channels is where that can get tricky (why OMNI is the default mode), but OMNI can also cause grief because every instrument in a project may be fired off as a result.