mettelus

MS Edge is one of those apps that I disable religiously, but it also re-enables itself religiously (I am not sure who is the bigger zealot in this situation). Side comment: MS did deploy an update today, which primarily affected Servicing Stack Updates... not sure if that has anything to restrict a bad redistributable install though. I didn't dive into the details too much with it.

That is a good question. The only thing I have seen wonky with internal Normalization is reports of it not working on multiple clips at once (and not sure if that has been fixed). I have always used an external wav editor (launched from within Cakewalk) to do normalizations. As the clip being looped is actually referenced, once saved in the editor and closed, Cakewalk pops up a message "Audio content has been changed, would you like to reload it?" This doesn't change the project file in any way, just the audio it has been referencing for use.

Even not rendered, the data required to recreate the separations is saved in the project file (just takes a little longer for a project file to load and recreate them if purged out), so it might be better to think of it as a temporary working directory that doesn't self-purge. There is a setting in Melodyne to change that from the default 10GB to something more reasonable (but be sure it is big enough to house one active project). Two other folders that are temporary working directories that do not self-purge are: C:\Windows\Temp C:\Users\[username]\AppData\Local\Temp (this requires "Show hidden files, folders and drives" checked in Windows Explorer->Folder Options->View tab) Those two folders can also grow to rather large sizes (I always purge them before imaging). Anything that is in use by an active program cannot be purged, but the rest is safe to delete. The AppData Temp file is potentially also huge if you have never purged it out.

Can you check your installed apps quick to see if anything was updated after you did your repair? After reading recent posts I am wondering is something "innocuous" like a browser update is affecting the that Karl mentioned above. There have been enough folks chiming into this thread with the same issue that this is becoming concerning now.

Honestly, that is overkill... the DISM run compares your installed Windows verion versus the version it "should" be, referencing Microsoft's servers. It can take several minutes to run, but there is no re-installing anything (HUGE benefit).... it just compares all of your system files versus what should be there and replaces offenders as needed. DISM has saved me a lot of work more than once.

Quick overview for you... a clip is like a "window" in a DAW, so even if you reference only 6 seconds of a 3-hour wav file, the DAW is pulling in the entire wav file, but honing in on the "window" you want (very handy if you have multiple clips from the same wav, as it continuously references the original). This is also why you can drag the ends of a clip to reveal more audio. When you Bounce to Clip(s), that clip is then rendered as a new (smaller) audio file, and will then be the only one referenced by the project (you can tell because dragging the clip ends will now reveal no more data). Once bounced, there are two methods to deal with that original audio (Cakewalk will not delete it). You can manual delete it as are alluding to, but a much safer method is to File->Save As... and in that dialog, save to a different (new) folder and check "Copy all audio with the project" and (oftentimes) "Create one file per clip." If you have bounced religiously while working this will create a significantly smaller Project folder (so you can remove/archive the old one) that only references used clips and ensures all used clips are copied over. A word of caution with this... this only works on the cwp you are actively doing the Save As... with... if you have multiple cwps in that original project folder, you would need to repeat to get them all. In your case, if you have a MASSIVE wav file you want to address, the bouncing (verify the bounced audio file is present), and removing the original may be simpler. Just for safety sake, I would move or rename that MASSIVE file first, then check that the cwp is all happy with the bounce by re-opening it prior to deleting that original MASSIVE audio altogether.

MSVCP140.dll is associated with the C++ Redistributables. Here is an MS article on that (and VCRUNTIME140.dll) which recommends uninstalling them first rather than installing them over top a potentially corrupt version. With potentially corrupted system files, I would first do a SFC and DISM run (be sure to run the "DISM /Online /Cleanup-Image /RestoreHealth" portion per this article). That is quick to do, and can reboot and see if that addresses anything before tackling the C++ Redistributables again. As you have clients affected, and this has impacted more than just you, getting @Noel Borthwick involved would be warranted. IIRC, he pinpointed one bad C++ Redistributable was being deployed by DaVince Resolve previously.

If Melodyne was active in a saved project, the separations will be recreated when reopened. If the cwp seems larger than normal (in the MB range) it is a good sign that there are active Melodyne Region FX in it, and the cwp stores that information to pass to Melodyne when the project is re-opened. If you want to test this, do a test project, leave Melodyne active on some audio, save it, then rename your Separations folder and re-open the cwp. That cwp will open more slowly, and create the Separations when it does. As Jonesey said, if you bounced Region FX, those Separation files will never be referenced again. Either way, it is not necessary to maintain them; they just make cwp's with active Region FX load faster.

I had to research the TD-27, which will send audio over the USB. The issue with using ASIO is you now have two devices connected (TD-27 and Focusrite) which won't work. This same latency concern came up in another thread, and my experience with tracking is to ARM/Record the drums tracks but MUTE them. Use the headphone out of the TD-27 as your direct monitor and only have the DAW playing back the other tracks (via the Focusrite). You will have to use WASAPI Shared to do this, but it will let you focus on your performance. When finished tracking, you may need to nudge all of those drum tracks by a universal amount, but it should alleviate the latency for the tracking part of things. For most situations, you want to direct monitor audio from its source rather than through the DAW recording them.

That dmp is for "The thread tried to read from or write to a virtual address for which it does not have the appropriate access." Sometimes this can be helped by running programs as Admin (or vice versa). If you Google "Exception Code 0xC0000005" that may give you more insight on your situation. Some Kontakt libraries are also RAM intensive, so not sure if that is coming into play for you... when loading those is your computer becoming RAM limited at all?

Try this out first, there have been recent issues with other software installing improper C++ Redistributables. If CbB will not even load, that could be a reason.

That is a good question actually, since it might depend on your intended output format (if primarily for videos versus audio only). From a video-only perspective, Resolve Studio (perpetual license) includes essentially everything in one shot that people pay for Premiere Pro/Mocha Pro each year. Sales on Resolve Studio are quite rare, so is more a decision on your intended use. From a music perspective, surround has a little less applicability than for cinema/gaming, and can substantially increase file size. Gaming engines in particular have had bearing/range information with environments for years, but they really only use the same (small) sound file and adjust bearing and volume based on position/distance. Those are "mixed" by the engine dynamically versus a static output (like music or video creation).

The resolution in that video isn't the greatest, but she goes back and forth between palming that pick to finger-pick, then back to using it several times. The beginning is easier to see her do that, but that unto itself is its own art. It is unfortunate that so many schools are dropping music programs these days, but there are kids very much into traditional instruments out there. The upside with social media is they can find each other. Family encouragement probably helps the most, but I have seen that get overzealous too... when someone takes to something like a duck to water, let them run with it.

It still activates every 6 months. The activation window (and pop ups) are scripted into the app version. Only the final releases had that window shrunk and the pop ups embedded.

That was my assumption as well but not sure(?). The last version of CbB was pushed with such ferocity that I cautioned a few about installing it. The shortened activation window and advertising was baked into that in preparation for the NuSonar release (even with a timer for that pop up before it was released). I never updated CbB past 2022.06, so not seen either of those issues.

Are you planning to post them as MIDI? If so, a word of caution... Windows (and browsers) have been phasing out GM support, so it is possible someone will click on a MIDI file without being able to hear anything. If they then import that into a DAW, the VSTi(s) chosen can get you back into the same boat of the playback not matching. I haven't touched Win11 yet, so not sure if there is any default player available. Some sites do have a default player embedded into them though, so is more a consideration.

All MIDI is dependent on the VSTi playing them, so you are going to run into a wall of sorts trying to keep things 100% MIDI. Even with different players, the bank/patch information (i.e., the actual sound) from a MIDI file may be interpreted differently. I understand why you are doing it, but you can only go so far with making it "universal."

Be sure you are logged into Melda when checking prices as well. A lot of bundle pricing is updated to reflect what you already own so you are getting credit and not buying something twice (Melda is the only vendor I know of that specifically prevents you from buying the same thing twice).

This is most often the case by far; it is the middle-man, or end seller that is pawning them off as "real." I did get a chuckle with the $6000/guitar though... everyone wants to overplay what they did... even the nicely made ones are roughly $400, but $1.2M! wouldn't make the headline as catchy. The luthier who PLEK'd my main said the guitars he PLEK'd most were new Gibsons because they "really needed it"... I will always remember that. The kit I made (roughly $300 with added elbow grease), I was initially going to logo with "Not Gibson" or similar but didn't want Gibson associated with it in any way. Instead dedicated it to Tigger... the only cat that came running to guitar and would sit in front of the amp (he also spent time watching me make it). China has some of the best mahogany preserves in the world, so even kits from that wood are worth it (the wood is most important, everything else can be bought elsewhere). I have had Tigger out and about a few times and it is quite the conversation piece just because everyone wants to get a better look at it.

Wow, that is a rather brutal assessment IMO. Bandlab ignores him (i.e., "help me to help you"), yet Bandlab's competitors are reaching out to him.

TL/DR version... the "mapping by default" is internally hard-coded into Cakewalk to TTS-1 if no MIDI output is selected. Because that is hard-coded, you can only get this feature with TTS-1, but you can carry TTS-1 forward from any Cakewalk version that included it. The solution (feature request) would be to have that coding mapped to a generic/free sampler, but getting agreement on "which one" may be more of a challenge.

Most kits without a specific driver are going to be sending GM so they are "plug n play," but check the manual for the MIDI map just in case. Depending on the VSTi you use, the chokes may need to be set manually. While the headphone out "can" be used to record the sound module (not really necessary with the VSTis available today), it can also be used to "bypass" the DAW latency (if needed). Muting the drum track in the DAW while recording your MIDI and monitoring the kit via the sound module headphone out may give you the best MIDI performance.

+1, right after I posted that I took a look at the newer starter kits and the Alesis Nitro Max caught my eye quick. For $400, that is ideal for a beginner (comes with BFD Player and a kit, and 3 months of Drumeo) and there are loads of reviews on that model. I am at the point where I would never set up or mic a standard kit and "small yet functional" gets much more priority. In this age of really nice VSTis where you can swap kit pieces willy-nilly, you just need something to fire them off with the proper feel/playability to it.

Depending how much you like to tinker (BIG if), there are quite a few videos of folks converting cheap kits (like Guitar Hero stuff) with new piezo sensors and Arduino controllers. Evan Kale had one from probably a decade ago that I cannot find now with the code he used to make them velocity sensitive. The folks heavy into Arduino usually have the coding supplied and detailed build descriptions in their videos (what to really look for if searching them). The actual parts are fairly cheap for such projects, but the coding and soldering can be challenging (why the videos are nice resources when they are converting something or building from scratch). Those guys take things that have basic pads and turn them into something more usable. Complex kits have more sensors on the pads/cymbals (rims, bell, etc.) so a cheap kit is likely to have only one dead-center on the pad and less things you can fire off while playing.

I think everyone already hit on what I was going to say. MIDI and audio are separate devices, so if "MIDI compliant" there may be no specific drivers for it, it may just output GM. Unlike audio in ASIO mode, you can connect multiple MIDI devices, easiest to sort them on tracks by what channels you want to use if you have multiple MIDI controllers connected. Also be aware of the controller limit (10?), so if you get carried away with this you may get new devices overwriting the oldest ones (probably not applicable in your case, and not sure if this was changed for newer OS's). For devices that have audio and MIDI running down that USB cable, they will show up as separate devices as well in preferences.