mettelus

Also be sure your Windows Sound Options are not giving exclusive control to apps. If another app sees it first, it may be locking the device so Cakewalk cannot access it.

A lightweight alternative to Task Manager is Moo0 SystemMonitor v1.83. The Portable version is the best option, since it installs nothing on your machine and you can simply run that when needed (and use it from a thumb drive as well). If you right click anywhere on the GUI you can choose to "Keep on Top" (option near the very top) while working. If your machine starts to get sluggish, pay attention to the [Bottleneck] and [Burdened By] at the top and what processes under [CPU Loader] and [HDD Loader] may be triggering them. Although it doesn't go into the detail of the Task Manager, the Bottleneck/Burdened By fields are handy for when they get triggered and it takes up far less screen space to use.

As Andres said, a lot of this is how the VST is scripted and how it loads samples (if used). There is no cut and dry answer for this unfortunately, but VSTis that load samples into RAM so that they are instantly accessible will often be smoother than ones reading from a disc, but that would also bring up a RAM concern to make sure you can load them all. Internally a lot of VSTs can be CPU-hungry even if they do not have massive size to them, so using only what you need is often best (akin to Ozone Standard is a mastering plugin, do not use that on all tracks). For some instruments it can be better to bypass internal FX, then use a lightweight chain on the output. A good portion is also the system, so do not forget old school things like freezing or bouncing tracks. CWPs themselves are rather small (as long as Region FX are bounced), so you can save things with a new name when you are "close" to committing, yet still back out to the previous version if you do have tweaks to make.

This used to be dependent on the card issuer, but there is now a federal law mandating this (12 C.F.R. § 1026.12). As most major issuers are based in the US, this will almost always apply, as most third party cards are actually issued by a parent company of VISA/Mastercard/Discover/American Express, but as Glenn mentioned it is definitely worth checking. PayPal is one I do not overly trust, but some vendors require it. You can actually make a transaction then unlink you card from the account right afterwards so that it doesn't stay on file. I have gotten into the habit of that simply because the phishing emails regarding "PayPal" are frequent enough they never fall off my radar.

I am not quite sure why those would be locked, @David Baay would be better to answer that one. As far as the easiest way around, as long as you are working in new cwp file (so you are not modifying the old one), you can delete everything but the guide track to set the tempo map. Once that is complete you can then drag/drop the old cwp into the new one (from the Browser->Projects).... this will import all of the instruments, so you can retain the instruments/settings, but the MIDI notes will need to be redone since you have changed the tempo map and the duplicate guide track will need to be deleted. Save the new cwp before that drag/drop just in case... I do not recall offhand if that actually overwrites the tempo map or not, but is another one David would know better. If it does (but I think it doesn't), you can open two cwps side-by-side and drag tracks between them as well as an alternative.

I admit it will be interesting to see how this all plays out. There have been numerous instances over the years where the VST3 fails, but the VST2 works. Perhaps this is PreSonus' way of holding the developers' feet to the fire (who knows)... I can only imagine a host developer's nightmare of having to "accommodate" VST3s that don't conform to spec (Noel has invested a lot of time troubleshooting 3rd party VSTs over the years). It has been over a decade already, yet still some still shoehorn a VST2 into a VST3 package and assume it works until the bug reports start streaming in.

I do not own Diva, but I opened a project quick with Scaler 2 in it and can confirm the issues posted in this thread. The simplest check is clicking the settings/gear icon in the upper right and that it is unresponsive, but the other noted issues exist as well. Quick Edit: One post sums it up on there. "Studio One v6.6 features the very latest updated VST SDK and is now exposing a number of existing plugins out there that either do not conform OR need some TLC - OR Studio One v6.6 needs some TLC as well." I am not sure what other VSTs are affected, but guess I need to roll this one back. Just makes me think of the folks who onboarded with Studio One+ Hybrid into this... surprise!

This is actually a situation where SM/BAN would be worth learning (will explain that after the "why" part... David replied as I was typing this as well). If you think of putting pins/needles into a bolt of cloth from left to right (what inserting tempo changes or SM/BAN is doing), then if you go back to the left and insert another pin to make a portion shorter/longer, it will pull all of the pins right of it along with it. You must work left to right when setting a tempo map to prevent this, and why the very first pin (the "anchor point") is crucial (the very beginning of the song), where everything to the right is attached to that and will move accordingly if you ever move it. To use SM/BAN: File->Save As... your current project with a new name (can just add SMBAN to the end for the name to make it simple). This way you can work with another project and not make any changes to the one you have now. Open the Tempo Track in the Track View (ALT-T) and expand it enough so that you can see the content. Also, click the "Show/Hide Tempo Inspector" (metronome icon) at the top of the Inspector (I) if not already open so you can see tempo mapping points. Disable Snap to Grid at the top. If you already have tempo map points showing in the inspector, right click in the left side of the Tempo Track and select "Reset Tempo Map" near the bottom. This will flat-line the Tempo Track and leave you with one tempo insert (the project tempo) at 1:01:000 in the inspector. Since you know the project is 150 bpm, rewind to the start of the project (CTRL-Home) and type 150 in as the project tempo. If your project starts at 4:1, and you have a defined drum track, focus the drum track and zoom in (Z-click drag) enough to see that first downbeat. ALT-Z resets your zoom level, so you can bebop in and out quickly with that. CRTL-A to select ALL track clips (this is important), and drag that first downbeat to 4:1. It doesn't need to be perfect, since you need to drive your anchor in here anyway. Click on the first downbeat and hit SM/BAN (Shift-M). This defaults to the closest beat, and the measure is highlighted already, so you can set them by typing the measure (if needed), then TAB to shift to the Beat, enter that, then ENTER to quickly work them through. Hit ALT-Z to do a sanity check and make sure you moved all clips when you scooted them, then ALT-Z to zoom back in. From there, tempos that are pretty tight only need to be checked every bar or so (I would not go any finer resolution that a Beat even if it is all over the place). Focusing on SM/BAN with the drum track zoomed in, CTRL-Scroll wheel to move right and SM/BAN as needed as you move left to right on the track on places where it begins to drift, and work that through to the end of the song. Once you get the hang of this, you can tempo map a song in pretty short order. Again, if you are ever going to "insert" a soft synth on a pre-recorded song, this is of utmost importance before doing any MIDI work.

David introduced me to SM/BAN years ago, and with a small learning curve it is one of the fastest and easiest built-in methods to map tempo to pre-recorded material. It doesn't alter the track material (just the tempo map itself) and can be better visualized as "anchor points" in the tempo map... be sure to also anchor the start point. As David mentioned above (and it is important enough to reiterate), MIDI/Soft Synths will want to align to a tempo map, so be sure to do that tempo mapping before diving too deeply into work. Tools like "snap to grid" rely on the grid (tempo map) being accurate. Being new, another thing to be aware of is that the old forum is abundant with information, but the search engine on both this one and that are terrible (to put it mildly). Many posts try to drop the terms for things you are asking about (SM/BAN, nudge, etc.), and the forums tend to have better explanations than the User Guide in many instances. To that end, the best method to search each forum is to precede your search terms with "site:forum.cakewalk.com" (old forum), or "site:discuss.cakewalk.com" (this forum), and Google searches tend to be better at returning hits. As an example, if you type "site:forum.cakewalk.com SM/BAN" into Google, it will return hits on SM/BAN from the old forum. Some of the questions you are asking are for terms/functions that have been around forever, so both forums will have relevant hits, but the old forum will have better write-ups at times. Side note: If you get a response and the term/function is not obvious to you, do not hesitate to clarify so that you can get the info you need for a proper search into the forums (or User Guide, YouTube, whatever).

That is pretty much it in a nutshell, but the upgrade tends to be less than $60/year to keep SOP current (the major version upgrades always go on sale for $125 or less every 2+ years). However, what seems to get lost in the kerfuffle is that these products are now so mature that the average user could probably stay with SOP 6, never upgrade, and be none the wiser (and not really care) about features in the future. Notion 6 hasn't been updated in years (many do not even care it exists), and pretty much all add-ons have 3rd-party perpetual alternatives that can be used in any DAW. After the lessons learned from Gibson, I would never buy a VST(i) locked to a DAW, let alone subscribe to one. After seeing feature requests blown off for years, paying someone for "future work" that has a habit of not happening is a no-go. I pay for products, not promises.

This is helpful in a way, since it kept you from digging into the wood itself. Tru-Oil tends to excel in these situations, because it will apply as thin as you want/need to fill imperfections/scratches, or simply re-add a sheen to a surface. Just keep buffing it as it dries to fill and match the original contour. Ironically, some of the cheapest final polishing solutions come from the automotive industry (ultra-fine polishing compounds, waxes, etc.)... once "guitar" gets applied to its use the price goes up dramatically for the same product.

Check in Preferences->Customization->Display quick. I am not sure if that affects the Audio->MIDI conversion though, but worth try. This thread has a little more info on that specifically. This is another thread discussing the same issue with alternative workarounds, but they are not all simple ones.

I forget where the setting is now offhand, but there is a preference setting to select the default octave. The SI bass needs that adjusted to talk properly with GM format (unless you want to manually transpose each time). Hopefully someone can chime in and tell you where that is at. It has been like that forever (the default) for some odd reason. Quick edit: It is worth mentioning that the AmpleSound Bass P Lite (is nerfed a bit), is one of the best free bass VSTis out there.

Yeah, I was searching for what "Lead Architect" even was, and there is absolutely no information on the PreSonus website about it (yet). As far as VSTis go, I do not find that video demo very appealing at all for some reason (there are a bunch of similar VSTis not DAW-locked or requiring a subscription to use). It did make me find an odd nugget right at the very beginning of the MSoundFactory tutorial video though (never watched it before). The second sentence in the video... "Most likely our last instrument..." It has been out 3+ years already and didn't know that.

I have been fortunate enough not to need a drill press (yet anyway), but one thing I blew off for years and shouldn't have was a table router. For precision edge work (especially bindings) it has saved so much time and effort on doing things I always used to do with hand tools.

I had a friend the same way, he would touch strings and you could almost watch them rust. Something simple like a thin sock with baking soda in it might be enough to neutralize your hands by rolling it around in your palms, but you want the fabric thick enough so it doesn't create a dust cloud on you. The pH is around 9, and it is not abrasive enough to do more than polish something.

It seems highly probable that you may have an installation issue, since as you have seen in videos, the audio->MIDI conversion should just work. Another thing to try is to check out the DAW-specific information on Celemony's support page. If that also fails, use their contact support form on the top of that page... they tend to respond to support questions by the very next day, and Melodyne is doing the "grunt work" for the audio->MIDI conversion so they would have much better insight into the "why" and also recommended solutions. While you are at it, I would throw in, "I am burning off my trial period and unable to use Melodyne because of this, can I also get my trial period reset?" The Melodyne folks are a good bunch, and their product is incredibly powerful, so do not hesitate to reach out the them as well. Quick edit: You can also save a little typing with their support form by inserting the link to this thread if they need more detail of what is going on so they can read it. This link is what I would insert for the original post you made (you can get links to posts by right clicking the post time/date to the right of the author for each post in case you didn't know that).

Exactly, as with most things. Sort of like MS Word... fine and dandy for text... I only get irate when someone sends me a file that the headings are all FUBAR because they copied/pasted from numerous documents and Word pastes that formatting by default. So many programs have features you will never need or use.

This is also the reason why Reaper has one of the most liberal trial policies seen anywhere (by far).

John had mentioned this earlier, but since you mentioned CTRL-drag again (which is to copy) I am wondering if that is the underlying issue. What happens if you simply left click and drag (no CTRL or Shift) an audio file onto a MIDI track? To save time and also test other material, you could also use a simple audio loop from the browser (put something into an audio track first, then drag it into a MIDI track). Does that do anything differently?

This is probably why barre chords aren't as prevalent, since you only need to fret the strings being used and the guitar gives a lot of leeway to get intervals (what the listener picks up on) in various inversions all over the place. Unless strumming or using the full chord, you can get the gist of things often with simple intervals. The neck on my main is narrow, and when doing Bm at times I find myself with my ring finger anchored on the D note (I tend to do this a lot when working in GMaj) and use the tip of my pinky on both the B/F# on the 3rd/4th strings. As mentioned above, neither E string is used, but things like that are more what feels natural to you (probably the most important aspect, by far), and gets the point across. If you find yourself getting into oddball "contortions" just to play, keeping inversions and the fact that those notes also exists elsewhere may be the simpler solution at times.

Was there a MIDI clip created in the track? It is possible the notes created are out of the visibility range, so if there is a clip "without notes" expand the size of the MIDI track, or even double click it to open it in the Piano Roll View

Wow, that would be $1.5B per month with subscriptions... Unfortunately people bragging about "user base" are often on this path but rarely get slammed for it like Frank's did.

AFAIK, Audition CC still has no MIDI implementation so it has very limited usefulness as a DAW, but it does have features that make it a good wav editor (background noise removal, scripts, batch editing, and the like). I sampled a TD-9 sound module years ago and it took me 10 times longer to rename the samples than to create/run a script to isolate/save all of the samples from one massive recording. 99% of those features existed in Audition 3/4 before it went to CC, and not a lot of note has been updated since it did. Out of curiosity I checked program-specific updates on things within CC a few years ago and updates are not overly frequent. The simple fact that a couple apps have free alternatives (DaVinci Resolve for Premiere Pro, and Visual Studio Code for Dream Weaver) takes a lot of wind out of the subscription sails. The Studio One+ is an odd one (someone posted they jumped off and just upgraded Studio One Pro, which was a prudent move). Unless you are doing notation, Notion isn't required, and it will host VSTis to boot, so sound packs are unnecessary... and Notion 6 hasn't been significantly updated in years now. Portions of the FAT Channel comes with Studio One Pro, and it costs roughly $60/year to keep current, but even then SOP 6 might be all most would need for their foreseeable future... as with most things, the 80/20 rule applies, so roughly 20% of a program's features will let you do 80% of your work. When new features begin to fall into the minutiae bucket is when to re-evaluate things. Software is one of the few arenas where a product isn't just delivered (a lot is due to the internet, so they can rely on patches and updates). If people bought a car and the manufacturer said, "Yeah, we didn't think about headlights, but it is definitely on our upgrade radar! Just don't drive it a night." People would freak.

Be sure to match your intended arc to the rollers, then adjust the steps accordingly. The D and G strings are not on the highest point on the arc, they straddle it +/- roughly 5.2mm for that 52mm spread.