mettelus

+1, I retired a 2600k a year and a half ago that stills runs fine, but that machine above is a little light for power supply and has no HDMI video connection. I am assuming you are planning to use hardware from an older machine with it? Can you share what you are using now?

You may be confusing that with Speed Comping as mentioned previously. Shift-dragging moves clips vertically while keeping time (the CTRL makes a copy), but that process is all manual and to be fast you need to have some mouse precision depending on track height. Speed Comping does have all of the "assembly" functions you speak of and has gotten a little more polish with even recent updates. It would be worth kicking the tires on Speed Comping with an open mind. The work flow is different than doing the same with tracks, but the tools it offers are worth knowing. Below is the original introduction of Comping with X3 from 6 years ago (6 minutes), but the assembly features you are asking for existed then.

The newer versions do have EQ matching, but you need to repeat the process each time and have the reference available. They will not save/load "snapshotsets" like O5 did though, which is a reason I keep O5 installed as well. O5A was the last "fully loaded" version, reverb, insight, etc., which sort of fell apart until the bundles upgraded. If you still have the reference material, a trial of a newer version would also work, just be sure to bake it if you go that route. Melda also has a few plugins with this feature you could also trial.

Pete Brown chimed in on this other thread with an interesting comment about NVIDIA. Doing a "Custom" installation of the most recent NVIDIA drivers will allow you to only install the Graphics and PhysX drivers (which has been common practice for a while now for non-gamers). After seeing a lot of "protected" activity on NVIDIA's telemetry stuff, I went and disabled that a year ago or so now. I just updated to 1903 yesterday, and the "KB4505903" reference was already baked in, but that is the first thing I would check (it will tell you it is not applicable to your machine if you have it and try to run it). After that, re-installing NVIDIA with only the Graphics and PhysX options selected may be helpful. His post was a nice confirmation that NVIDIA includes a LOT of bloat in their generic installation package (ShadowPLay, 3D stuff, User Experience, etc.), which is not useful for a DAW.

As Mark mentioned above, the download folder is sort of a temporary repository, so if you have installed things from it, those files are no longer necessary. The caveat is also what he mentioned - If you need to reinstall at a later date and do not want to re-download things, moving them to another drive will allow you to just install from that. I tend to keep mine so that I can rebuild my OS drive from scratch if needed. To your question specifically, you can delete the (#) files in your screenshot. Those are duplicates of the ones without any number at the end (keep the "ProducerX3ePatch.exe" and delete the other two). Same with Native_Access_Installer.zip (you have one duplicate), and ProducerX3bPatch.exe (also one duplicate). The thing to watch out for is you *may* get into a situation where they all end with a number (but be the same size), so for that situation, you can keep one of your choice, then rename it to remove the (#) at the end. Also in the downloads, failed downloads sometimes remain with a "_part" at the end (meaning a partial file). Those will not run anyway, so are safe to delete. The same name (without the (#)) and size are good indicators of duplicates. Smaller files are often a nuisance to track down without a "Duplicate Finder" style application and rarely contribute to space issues, which is why I suggested "huge" or "gigantic" (files >16MB) previously. Those will eat up hard drive space quickly. If you do not use Beatscape, you can delete those files (or move them if desired). The "Loops and One Shots" replaced it, as scook mentioned previously.

Barring the "how" you got there (which you would want to understand down the road), the easiest way to fix an already exported mix would be to start a new project, drag/drop that file into a track (either from the internal Browser (B) or Windows Explorer), trim/fade to taste, right click and "Bounce to Clip(s)" to commit changes to a new wave file, then drag/drop that file back to the Browser or Windows Explorer.

As John mentioned, unless you get heavy-handed with plugins or synths, using CbB as a "digital tape machine" isn't going to stress a system meeting the minimum requirements for CbB. Bumping up audio buffers for post-production is pretty standard, and if/when you begin to hit hurdles on the system, there are ways to reduce system load (bounce tracks and archive originals, freezing synths, etc.). If the work flow of tape is your preference (or what you are most familiar/started with), you are actually going to be less challenged than someone who is just starting with music on a DAW.

This is an interesting observation, and most recommendations have been to only install the Graphics and PhysX drivers for the NVidia installation (not the personal experience or 3D stuff). I have gone so far as to disable the NVIDIA Display Container LS and NVIDIA Telemetry Container services... I found that NVidia is quite adamant about that telemetry service, so much so that it will not allow users to do anything with the files that it creates. It removes all of the control panel drill downs into NVidia settings, but Win10 hasn't seemed to have any issues using the drivers.

LOL, yeah, I just perked up when it mentioned those two symptoms. The *real* condition is actually an extremely serious one, so that took the fun out of the whole situation as is progressed further. It went from funny to rather morbid in under two minutes.

Doctor's offices tend to run a lot of Discovery Channel style medical stuff in the background while waiting, but this morning I perked up as it was going over "blah, blah, blah [tuned that out until]... the confusion of common words, or the confusion of words with similar sounds..." I had never heard the term before, but made me think of the CH for some reason.

LOL, if I didn't already own Iris 2, I wouldn't care wasting the $2 to get it. Makes me wonder if Iris 3 is on the horizon now too.

Couple quick notes: 1. Installation files are safest to move to external media (or another internal drive that isn't the OS drive). That puts them in a safer place, and frees up space on your OS drive. The contents of the "Downloads" folder I move religiously, and then sort the important stuff. 2. Watch for files ending in (#). Those are created when you move/copy files and elected to keep both versions. You have 3 copies of the X3e patch showing in that screenshot alone. [Edit: Had to log into my computer since the mobile version is inserting annoying emojis.] You can find those files by: In Windows Explorer, if you type ~="(" into the search field it will filter the search for only things containing the ( character (i.e. what is in the quotes; you can chose other things). Another alternative is to search your OS drive for anything "huge" or "gigantic," then make the call on why they are there, and if they should be.

Not installed 1903 yet, so making a quick comment to find this thread for when that time comes.

My apologies if I threw a wrench in the thread, but I'll freely admit that given your modest needs that throwing a DAW solution out would probably not fix all of your issues (especially system ones). It would be worth getting ”Bandlab Assistant" and then the newest CbB release to kick the tires on it and get any system issues addressed. CbB also introduced WASAPI driver mode that would allow you to troubleshoot sans interface for things like DPC latency issues. There are plenty of folks here that will stick with you to iron things out if you are willing to give that a go.

Have you tried the new CbB release? I am more curious as to the issues you are having "making it work." For a few tracks with minimum plugins, just about any DAW *should* work, but each one has its own quirks. I have only tried a few others, and Samplitude "seemed" closest, but I couldn't get myself to like it. I use Studio One mostly these days, but again that falls into familiarity with the work flow and trade offs to other things. The few things I do miss most (track templates, Set Measure Beat at Now, Audio Editor integration) have workarounds or partial fixes. I have yet to install the new CbB, but it includes a lot of updates. If you are more familiar/comfortable with CbB's work flow, it might be more beneficial from a time perspective to get help with the issues that you have. Samplitude/Studio One it seems you have already used/tried, and I cannot really speak to more.

FX do not care what they take in nor what they pass on, so always be mindful of the signal you are sending from one FX to the next. A compressed signal is harder to EQ if it has unwanted content (like roll-off's mentioned above), and there is nothing limiting you from multiple steps (where more transparent changes can be made). Mild compression in -> EQ the proper content (for the instrument) -> compressing again to fit the mix is not uncommon.

Very nice piece Dave. I saw the "MIDI editing cheat" comment, but when started listening it became a "who cares?" for me. This quote gave me a smile. I have a classmate who used to play keyboards, got married, and then a grand piano. She has had zero interest in DAWs or mic'ing it... she just plays (20 years and counting...).

Ozone is also a bit CPU heavy and you cannot use modules separately without the advanced version. iZotope has done a lot of work to split their functionality apart since the Alloy days.

I see what you mean now. I renamed a .mid to .midi, and double clicking it launched CbB, but you are correct that the open dialog box does not recognize the .midi extension (it is not visible). That is a bug as far as I am concerned, since CbB can definitely open them.

How did you perform this? Reason I ask is twofold. First, many programs link to computer ID, so shifting hardware and OS could require a reinstall and/or reauthorization of those apps (Waves could be one, but I do not own any). Second, the VSTscan is a shared component, did you install an earlier SONAR version at any point after your shift to Win10?

That is cool that it got posted for future downloads. New folks can still apprectiate what it can do. That release is totally unlocked, so I am not sure if there is any issue with just sharing it with others.

Thanks for the response Craig. In concept it makes sense (the article reference in the OP); but for the price tag, I get concerned for a couple of reasons (pun intended), especially to new users: There are a lot of free (or cheap) VSTis out there; and while many users start with tweaking presets, there are also a lot of "sonic manipulation" tools (in the same price range) that can morph things into uncharted territory. For $400, someone with patience could rack up quite an arsenal of instruments and tools for use with CbB (or any DAW). In a similar vein, while the point is to take advantage of tools which do not have recording capability, that same $400 could buy a DAW which most certainly can and also includes adequate VSTis already. That would undermine the point of the article. New users are the my primary concern, since they really want 1) easy setup, 2) intuitive workflow, 3) not to have to invest large amounts just to get up and running. *IF* someone had those tools on hand, ReWire would make sense, but I am always hesitant to suggest a solution with a large price tag to folks needing help.

This will probably spin around and bite me in the butt down the road. I have stayed on a FireWire interface because it is dedicated and not managed by Windows as USB is. When the day comes that I switch to a USB interface, I will probably forget reading this advice.

I am not familiar with Reason, so had to look up the cost for an end user, and rewire has been a can of worms for me as well. Does the Reason Intro version include those features (full blown Reason is not cheap)? If not, some third party programs or even DAWs have these functions integrated under the hood which makes them simpler (and get fixes more readily). Being unfamiliar with rewire, I would be interested to hear the argument for a new user, since learning two DAWs is not as beneficial as sticking with one which already does what they need.

Wow, thank you for posting this. Resolve is one hard-core program. The initial setup even asks you what workflow you are used to so it will customize the layout to something familiar. I was tempted to say Premiere Pro, but then just chose Resolve's default. 2937 page manual... OMG, but it is nicely bookmarked and thorough that I can tell (and they even apologize for it being so big). I ran it enough to kick the tires a bit and the engine in it was smooth as silk for scrubbing, so I just added more and more till I got bored with effects. I hit the play backwards button by accident at one point (never seen one before), and that just gave me a chuckle. Now wondering why I never picked up on this existing. I downloaded the 16 Beta, and it didn't ask anything other than info prior to downloading... not sure if there is anything more to it after the fact?