mettelus

I wanted to bump this one quick, because Chandler did a video when Scaler EQ came out to do basically the same thing with MDynamicEQ (currently on sale for $19 (regularly $76)). It is a little more involved to set it up with MDynamicEQ; however, this is very much worth noting since it uses functionality embedded into most Melda products that many folks either 1) do not use or 2) (more often) do not even know exist. I actually prefer videos that show this capability of the plugins over the "easy screen" overview, since the power of Melda plugins is in the editing view/multi-parameters. Unfortunately the number of tutorials covering editing view/multi-parameters rarely have "real world" examples included.

Actually docx were specifically designed to prevent that. A MS file needs to end in "m" to support macros... i.e., docm, xlsm, etc. As far as the OP, have you walked through the Quick Start tutorial on the Melda site? There are several instances where the looper will not do anything, and there are multiple ways to get it to record (a couple require the DAW transport to be in motion, and yet another doesn't start recording until bar 2). Try out the different methods in this video (also be sure the "play" button on the track you are recording to is lit up):

Boy, if they had a good set of lawyers, they could have trademarked the "subscription/membership plans versus perpetual license" long before it came into vogue! The casino aspect probably makes up for that lack of foresight and then some though.... shrewd diversification of assets there.

If those takes are really gone (i.e., you deleted them and rendered the file), check the name of the track you are working on, then see with a new cwp file if you can import an earlier version (same track name, but lower number on the end) of that track from the Project/Audio Folder. If you have not intentionally purged that folder, there should be track audio with the takes in it still there (probably the largest version of the track file in that directory). Be sure to do that search with a new cwp (project) first so that you do not mess up the work in your current project. Once you find it, you can replace the one in the actual project.

Also... two temp directories on your computer that always collect things while the machine is running, but never purge themselves on their own are: C:\Windows\Temp C:\Users\[username]\AppData\Local\Temp Everything in those two directories can be safely deleted (and ones that will not are being used by open programs... just "skip" those). Also, "AppData" is a hidden directory, so to view it, you need to change search options in Windows Explorer (View->Options->Change folder and search options... then at the top of that popup... View->then check "Show hidden files, folders, and drives"). If you have never cleaned those two folders, you may have GBs worth of temporary files in them.

Can you explain this further please? I am not sure what you mean with "link loaded files like in sound one"... both "link" and "sound one" (Studio One?) are confusing me. Also at the end when you say "it will bounce" makes its seem like "it doesn't work"... "bounce" is actually a rendering option (to bake FX permanently into a sound file), so it doesn't quite make sense in that sentence. However... That said, what I "think" you are trying to do is import audio into a project but not create a copy of it (meaning you have only one copy on your computer and Cakewalk will reference (link) it "wherever it is"). If that is it, then in Edit->Preferences->File->Audio Data... uncheck "Always Copy Imported Audio Files" at the top. Bear in mind that if you do any operation on that file that will bounce (render) it, you will get a new copy in the Project/Audio Folder. Also if you ever move the original file, when you open that cwp file later on, it will make you find that referenced file first, or it will not load into the project. This is why the Project/Audio Folder structure is preferred for housekeeping reasons.

Hmmm, so if walking only, you could either be on the "Sidewalk to Hell" or "Pathway to Heaven"?

That alone would be a reason to consider using only one Kontakt instance on SP and leave it at that. Unless you have finite control over those 5 voices, you could easily load a patch preset that is close to clipping already (a lot of presets default to "fairly hot" as it is). I do not own SP either, but if you have a solution that works, I would stick to that and not waste time trying to make it do something it doesn't want to do. There are a lot of VSTs that have quirky response under select conditions; some have solutions, others have workarounds. The ones that have neither are the ones to watch out for.

^^^^ Depending on what Kontakt is doing internally, you may just be adding sounds together (on the same output). Kontakt has its own internal routing and mixer, so even though you can literally do a lot with a single instance, it can be confusing as to what is going on unless you know the what the "guts" are doing. Because of this it is sometimes simpler limit instruments in each instance of Kontakt (and use more instances of Kontakt itself), depending on familiarity with Kontakt and how complex the project is. You just replied as I was typing... what are the meters on the outputs of Kontakt showing you?

Thanks for posting that. I had just used that as an example for someone who had no music theory knowledge to give them a visual demonstration. Getting through some of the terms initially was a bit rough, but Melodyne (Editor and above) is a useful tool to look at an entire song in a "score" fashion. That visual assist made explanation far more simpler once terms were out of the way. "Seven Bridges Road" was just the first song that came to mind, but was a good segue into more discussion.

I think Lukas owns the Studio One Toolbox site, and being a developer, he put a lot of handy tools there that are not available specifically within S1 (he just coded other tools people might find useful, like pulling track templates from other project files). Even the main page is a drag/drop interface to convert Cubase Expression Maps/Patch Scripts or Cakewalk Instrument Definition Files into S1 "Sound Variations" (which are beefed up "Articulation Maps"). He also has 400 tutorial videos linked on that site binned into applicable categories, which speeds up searching for things as an alternative to blindly YTing for answers.

^^^^ It is important to point this out, but it is also in the bold text at the top of the link in the OP in gory detail (for all DAWs). Unfortunately, folks who first came online with CbB do not qualify for a cross-grade, but S1 Artist is given away with a lot of PreSonus products.

It has been so long now that I cannot remember for sure, but didn't the demo "reset" annually so you can try things out once per year?

This is highly dependent on the original track and how it was mixed. Frequency overlaps between instruments can cause phasing issues (i.e., parts of stems end up in other stems), so if you (slightly) modify those and remix they can become transparent. However, if you remove a track entirely, that phasing will persist, and may not be usable even with more surgery. When you say "fairly dense," that is where you may find the limitations of un-mixing stems in short order. Almost every plugin that does this (and has additional repair tools) has a fully functional demo available (RX Standard/Advanced or SpectraLayers Pro), so if this is a one-off situation, you could demo one of those and see how it works for you with that specific track, and at least get that work done with the demo alone.

This is not technically a split (hence the confusion), but a lot of which method you are using depends on how far you need to zoom to see what you are doing. When that zoom makes the region larger than the track view, splits tend to be faster; but if the entire region is in view, ripple delete can be the faster method.

There is an option in Preferences for the which side of the split is selected by default. I forget what that defaults to but mine is set to left, so you can only hit the delete key every second split that way (split start, split end of silence, hit delete key). Also, bear in mind that there is a Process->Remove Silence that you may want to check out... you can set dB level/duration/tails for editing a track and it will remove all of those sections in one quick pass. It works very well for dialogue editing when you have only one track and no worry for alignment to other tracks.

The browser is text-searchable, so that will work most of the time, and a simple sort by vendor/type often gets the rest. I have a feeling that this will fall by the wayside for you over time. Getting caught up in organizing just ends up being a time sink for me.

+1 Unfortunately, the performance monitor doesn't deep dive into every plugin to look like this (I didn't embed the image because it is large and is from S1P), but something to bear in mind is that not all VSTis are created equal. Depending on how libraries are streamed and the complexity of the VSTi itself (about all of them have internal FX you cannot shut off via CbB), one or more of them can easily be giving you a nice latency hit that you are not able to see with the performance monitor itself. If you have shut off all FX in CbB (so you got busses too), then I would focus on VSTis... Look at disk usage in Windows Performance monitoring (this will also add another CPU hit, so be mindful of this, but can help to see). As CbB is the host, it will hide which VSTis are causing it, but will let you know if it is a streaming issue. Look for VSTis with internal FX that "could have" any look ahead associated with them on their audio processing. Many VSTis do have an internal FX bypass function, so rather than troubleshoot via freezing, you should also be able to bypass internal FX via that method. If there is a consistent point where the dropouts occur (especially if it is one instrument becomes "active" each time in the same place) that is a good place to focus. Before starting troubleshooting, be sure to save it as a new project first. *IF* you are lucky and it is isolated, deleting tracks (or ones associated to suspect VSTis) can help narrow down the root cause.

You got a wee bit more than just that though. It wasn't till I saw a Dolby Atmos VST in the deals forum a few months back that I realized there even was such a thing. That is baked into 6.5 (and you got a bunch of other goodies too... you just don't know it yet).

Silly me! In reality, since this is not specifically music-related and I am not an expert on the subject (or their product), that was intentional. I figured if typing 5 characters ("Fotor") was a struggle, then typing 3000 characters (2 pages of coherent text) would go far beyond their capabilities to use what I had mentioned in the OP. Finding 3000 characters of coherent text on an internet forum is a rarity as it is.

The image generator only has aspect ratios (1:1, 4:3, 3:4, 16:9, and 9:16) as selectable options, not pixel size. I have been only working with 1:1 so far, and it makes them 2048x2048. I suspect you could resize a 16:9 down if you wanted a perfect 1920x1080, but if using the image for something like a desktop image, Windows will automatically scale it and use a 16:9 image "as is." The 5 free credits for just making an account is still in place, so you can test that out... beware here... the AI image generator defaults to 2 images at a time (in the lower left), so if you are working with those 5 freebies, I suggest setting that to only 1 image per generation cycle. Again, be very descriptive on what you want to see, or the generator will just randomly assume "something" for what you left out. A lot of their editing tools are free (same tools available in many programs), so I have been focused on bringing those into Painter and repainting/modifying them.

The only feature that hasn't been added yet that I missed from SONAR was the ability to use a wav editor from inside S1P (I put that request in 5 years ago now). However, there are VSTs out that can do that functionality, so it "sorta" went away if you have one of those. The transition to S1P itself is best done to work a simple project start to finish to get acquainted with the GUI (the wheres, whats, and hows). Being a "one-page" default layout, there is a lot of keyboard shortcut activity involved to get speed proficiency, but there are also a lot of unassigned shortcuts for rather nifty features.

Have you considered a hardware VHS->DVD recorder as an intermediate step? I am not sure how easy those are to find anymore but left one sitting on a shelf just in case I would ever need it. Sheesh... I just looked them up and they are 3x the price they once were! That is nuts.

The routing can get complex, for sure, but the purpose is to specifically monitor (echo) an input signal so you can hear it while recording/tracking. When there is already data in the track it is no longer required. Where it is most useful is to help with gain adjustments, etc., prior to and when actually recording as well as letting you listen to VSTis while noodling around with presets (without needing to arm the track).

From that link check your preferences quick: "The Off position on a current MIDI track is only available if you disable the Always Echo Current MIDI Track option in Edit > Preferences > MIDI - Playback and Recording." That should be ON by default, and may be off by accident. That is required to monitor the input to a channel through a VSTi, and should automatically be on if the track is in focus to prevent what you were experiencing.