mettelus

Even people who live in areas that get snow often have no clue how to drive in it. My roommate in college had a saying that always made me laugh, more because of how/when he said it... "You can't push a rope!" I got to see quite a few vehicles spun out yesterday and could hear him saying that as I passed each one. Ironically, this weather was no surprise to anyone, but my local government neither prepped nor plowed side roads properly, so the amount of ice from the thaw/re-freeze was a bit over the top, even for here. It is a little different world when you have to remind yourself to take a chainsaw with you when you leave the house (I live between two state forests, so wet snow/freezing rain can bring leaning trees down with ease). It is cool the grand kids got to see it though! I often have people who have never seen snow say they are SO eager to see it... I just tell them, "Yeah, it is cool to look at and play around in for a bit, but that is often about it."

This is the crux of the OP's question, so a lot depends on how much the original audio was altered. About the best one can do in that situation is use an FX with upsampling that will alter the existing audio file (add content based on the FX), but even this is a hit-or-miss scenario depending on application. You can never recover the lost information, but can sometimes put it into a usable format.

Just bear in mind with a virtual audio cable (or loopback) scenario that two DAWs are going to default to main outs (i.e., hardware) and inherently want to output both there (hearing both the dry and wet signals). If SONAR is the feed, you will need to send the main output to the virtual cable (not the hardware) and use that as the feed to the second DAW to allow the second DAW ownership of the audio interface. In common loopback scenarios the final result is often best muted (will still record) with input echo off to prevent a feedback loop, but in your case that isn't a viable option (or really relevant) since you want to hear the second DAW's FX. Just be mindful of of doubling up the signal at any part of your cabling path (in your case, this isn't a true feedback loop, since the second DAW won't feed back into SONAR, but you would still risk the output being both outputs combined otherwise).

If you own other iZotope plugins, the biggest advantage is being able to use instances of iZotope's Relay to feed specific instances of Insight 2 when working at a buss or project level. Their overview video walks through a good portion of what Insight can do.

For offending VST(i)s that you have, go into the Plug-in Properties (via the dropdown in the plugin title bar or via the Plug-in Manager) and select the option "Always suspend on stop." That will force a VST(i) to stop when the transport does.

Just about all issues that have this response (crash on program load) have been associated with bad Microsoft Redistributables. Please refer to this post for more information and an installer that Noel made to ensure they are updated.

Audio Normalization is nothing more than raising/lowering the entire clip or track by a constant value to hit the target you specify. It does nothing to "smooth" or change the relative dynamics of the audio. Where this can be useful is to prepare tracks to a given level prior to mixing and/or so that they hit more common threshold targets for follow-on FX (specifically compressors) more consistently. Visually, normalization does essentially the same thing as applying clip gain (CTRL-click-drag) on the waveform in the Track View (just that with normalization you are specifying the target for the peak in the entire clip and a single gain is inserted on that entire clip to make it land there).

Initially when I loaded this machine 7 years ago I would track junctions pretty meticulously, then I started be-bopping things back and forth between the D and F drives as I swapped them out and ended up putting close to 50 junctions in place over that time. That is a little too much to track, but Windows has a built in way of tracking them for you. This page is a nice reference if interested, but essentially a simple command prompt will let you offload all of the junctions/symbolic links (and hard links in the "Option Two" section of that page). What is exceptionally nice about this is it offloads both the junction point and target locations in a fairly readable format. It may take a little while to process, but using the text offload version comes in pretty handy (I just command prompt DIR /AL /S "C:\" > "%UserProfile%\Desktop\Junctions.txt" to create a file called Junctions.txt on my desktop of the C drive, but please see the above link for more information or how to get hard links as well).

I am assuming you are allowing your system to sleep/hibernate (?), which Windows is notoriously bad at. Even though the intent is to wake up a computer in its previous state, there are other things in the background that can cause the interface drivers not to come back online properly. Letting the monitor sleep is fine, but the system should not be allowed to sleep/hibernate when using it as a DAW. Even with hibernation disabled, Windows will continue to build the hibernation file in the background, which consumes both resources and disk space. I posted this a couple weeks ago on how to disable Windows from creating the hibernation file completely if interested. If you have hibernation disabled, letting Windows build that file is a waste of resources.

Download the trial version of it and kick the tires on it. Insight 2 is actually a slick utility app with multiple ways of setting up and visually analyzing audio. The regular $199 is way steep for such an app (and it is often bundled with things that cost less), but this price is much more reasonable.

Gibson doesn't give away anything, so unless someone bought Z3TA+2 from them, Gibson still owns it. BandLab would be a better source if you can get a legitimate response.

That was very nicely done. The part that stuck out to me was the camera equipment when they showed it. A couple of those cameras are not cheap by any means, so they rival the cost of the gear that was used (not sure if they own them, or rented them for the video production). The lack of post-production is also very heartening this day in age!

This may be more convoluted than you realize, why reaching out to Gibson (if you get any response) was a good idea. There never was a clear definition of which IP was sold to BandLab (another company to contact). After the Gibson debacle, all of the Cakewalk extras ceased development, so it is probable that Gibson retained rights to everything except the DAW itself. No idea, just speculation; but if Gibson retained those rights, Z3TA+2 may be off the radar for good. Because all of those apps ceased development and were not even re-released in their "current form" which would have been simple to do, I am assuming BandLab was only interested in the DAW portion and Gibson still controls the extras, but that has never been confirmed or denied.

Try this, you need to have the CTRL button held down when you want to activate the same control in the group you have selected. IIRC, control groups were implemented in X3, so any version after that should work that way.

Did you check your legacy account? IIRC, Rapture (full) was its own product, so as long as you registered it, the download and serials would still be in your account information (and can install it via the old CCC). I forget if Rapture LE shows up in that account list, but I think it does as well.