mettelus

I am not familiar with the new layout, but I assume the depth is the threshold (no idea, hopefully someone can chime in with the real answer)? That is simply what causes the gate to open and allow the signal to pass, so will vary depending on the level of the signal in. I am not sure what "pops and crackling" entails, as that seems more like a buffering issue (not sure), but what does stand out is the release time being so low for toms. I tom needs to ring out, or it will get chopped off (is that what you are hearing?). This is a nice "cheat sheet" I just found for gating drums, and without numbers on that "Release" knob I am assuming it is fairly low in value, which will make it chop off the tom unless the input gain is jacked up so it is basically always open.

I just checked my attachments and it includes PMs... I deleted 3 attachments that were in PMs so that space was recovered (same thread), but then went into the thread and they are still there.

Minimum tech specs (SDXL-Turbo) Operating System: Windows 10 or Windows 11 (64-bit, latest updates) Processor: Multicore Intel Core (11th Gen or newer) or AMD Ryzen (2 GHz or faster, 64-bit support) RAM: 16 GB GPU: Integrated or discrete graphics (Intel Iris Xe or newer) Hard Drive Space: 15 GB available (models downloaded separately) Monitor Resolution: 1280 x 800 Side note: It seems Intel is actually partnered with Distinct AI... I came across an article published by Intel on them while searching.

In replying on my cell the bottom of this box says 4.88MB max (total and file). Do you have other attachments taking up the missing space? (Reports of shrinking appendages are going to scare off forum members (for fear of their members)!)

Yeah, this has taken up the place of folks accidentally hitting O and enabling offset in the past... so many posts on that one until the keybinding was removed. A red halo effect around the entire GUI like when you are near death in a video game would be obvious too!

Interesting. Render FX doesn't even show on Distinct AIs product page (??), but it looks like a beefed up version of Vision FX from the teaser video. Their AI generation is based on local system generation, so it can get intense on your GPU. Between the last offering and this one, they also released GPU models to make generation faster and more efficient. Upside is no credits or storing ideas on a cloud server, but the downside is can be significantly slower depending on the detail involved. Still scratching my head on this Render FX (is definitely new), as it includes aspect ratio and more features that Vision FX does not (says post-processing, etc. in the teaser)... is just odd that it is not on their product page. Also of note is the lack of Painter, PaintShop Pro, and VideoStudio... both PaintShop and VideoStudio were suspended ("put on hiatus") in 2023 to focus on Painter, but Painter has not gotten an update since 2023 either. All three of those apps are now 3 years old.

Don't get wrapped around the wheel on this, just focus on describing the issue as much as you can (especially the OP title... you can also edit the OP to change the title as needed). As long as what is occurring is clear, folks will often respond with the terminology you need and even bold face that as @tparker24 did above. Once you have that, it helps you to search things on your own. It is all part of the learning process. What wraps us around the wheel is when OP has so little detail it could be a dozen things... and then the OP never returns!

Even Melodyne is working with the file written to disc during recording. If this is someone you work with fairly frequently, the goal of improving that recorded file (to minimize post-production) would be another focus to consider. If you Google "Apps to Train Voice Pitch," there are several out there, with some more like games to make them more fun. Some of those apps also focus on the unique range of the singer, which is another thing that should be taken into consideration with song choice/composition. As alluded to above, if post-production becomes tedious (with any instrument), a large portion of that falls back onto the performance, and the performer should also be improving their art rather than relying on you for post-production.

I have rarely seen this effective unless the correction is minuscule. The "real-time" versions tend to add CPU overhead and miss the mark with corrections farily readily. If you need to do significant changes, this is better to do in post-production with Melodyne, either the whole track in one go with its macros, or surgically for specific issues. Also bear in mind that if this is in an FX rack, it doesn't alter what was saved to disc (is simply processing that). You would need to bounce that FX to get the file corrected, unless you plan to run the FX forever (not recommended either).

I would recommend doing a cleanup of that project, especially if it is in its final stages. Before you start, do a File->Save As... with a new name (you can put it in the existing project folder). Once that is done, I would do the following: Delete all of the Archived tracks. If you are not using them, get rid of them. Trim off the right end of the project (unless your export end is really 321 bars?). Some of the tracks appear to have no data, but still go on (Tracks 5, 6, and 9 from the OP). If specific to only certain tracks, you can split those and delete everything to the right, especially if they are truly empty... is that automation data in those? Do a deep dive into what FX and automation you are using. Some FX are not CPU friendly at all, but unfortunately Cakewalk doesn't give you a list of FX running in the project and load/lag associated with them. As this is happening in the same place, I am highly inclined to assume it is an FX choking. When tracking, you want buffers low, but when mixing you want to bump those up in preferences (to 512, 1024, or sometimes 2048). This gives the CPU more time to fill buffers and is required if you have unbounced Melodyne Region FX in the project. Check the event list for where the crash is occurring just to see if there is something in there that is obvious (this is unlikely, but good to check anyway). If that will offload at some point, I would also consider creating a another project at 44.1/24 and drag/dropping the new cwp from your browser into it (that will populate the new project with the data from the cleaned up one), then do another Save to that second new one so it is in a 44.1/24 format. Just bear in mind, that even with a capable computer, the right recipe will drive it to its knees. Rather than save/keep everything (this is better done through saving versions as you go), try to keep things simpler in the working version.

When something is that repeatable, it is often something coming online (FX or instrument) at that point in time. Are there any other tracks that start where the glitch is occurring?

If you go into Preferences->Audio->Sync and Caching (be sure "Advanced" is checked at the bottom of the preferences window), do you have read and write caching enabled? For larger files, enabling those and setting either 512 (I think this is the default) or 1024 may help with disc reads/writes. Is the CPU meter in Sonar showing high usage during that export? Intense FX, especially ones with lookahead buffers can cause issues in larger projects. A notable example is iZotope's Ozone, that is a mastering plugin, so is not intended to be used on tracks.

I wanted to touch base on this at a high level for you quick. You cannot "add detail" to something that wasn't recorded, so larger sample rates will just add a CPU hit; and larger bit depth/word lengths will just add file size, but neither will give you more detail than you had in the project. By default, projects save at 24-bit, but the DAW process at 32-bit "under the hood" to allow more detail with calculations and prevent clipping inside the DAW. While you can increase detail with upsampling, it is actually the VSTi or FX used that are adding the detail, since they have more data points to play with. Regardless, the sample rate needs to be at least double what humans can hear (essentially 20KHz) to prevent audible distortion. 44.1KHz was chosen for CDs, but with video production becoming the mainstay, 48KHz is a better "default" just in case you want to use your work in videos at some point (it is easier to downsample than upsample). The debate on higher sample rates has been perpetual, but the reality is most young adults cannot hear over 16KHz, and it just goes downhill from there.

That was the other question I was going to ask earlier is if you had any VSTis kicking in where the glitch occurs, since your track count scrolled off the screen. This can happen when new samples are loaded during playback with some VSTis, other VSTis load the sample set into RAM when a bank is selected so there is no read delay. A couple things you can try with your situation: Play the song through before the export so samples are already in RAM (this is not always 100%, and adds time to the process). Bounce/freeze just those offending tracks so that they are now "just audio" rather than a VSTi processing samples (this should work and saves the time of having to play the track through).

Have you tried it with Global FX bypass enabled to see if that works? With such a high sample rate and bit depth going, your CPU may be struggling as well. If the project is set to 44.1K, why are you exporting to 88.2K? You could also try opening the Windows task manager during an export to check (will probably crash it for sure, but at least you would see what the computer is doing as it goes).