Starship Krupa

Which suggests to me that the term "forum jerk" could be applied to the path of a discussion that goes off-topic. Heavy meta.

The fact that disabling all FX cures the symptom is a clue. I'll go with what others have said about trying enabling and disabling individual plug-ins to see if you can find one that is triggering the behavior. And it might not be just one, I've had it happen where it was two specific plug-ins in a specific order that caused trouble.

Ain't meanin' to be a jerk Just wanna know if it worked Got them single post blues again... .... Oh, mama, did their problem really end? Are they stuck inside of Cakewalk with the one post blues again?

Check your Ripple Edit.

I'm still investigating that. Just installing it in Ultra Analog's own user banks folder didn't result in it showing up in Player, but I haven't tried finessing it yet. Not holding out a lot of hope; A|A|S are pretty good at locking their stuff down to only do what they want it to do.

The A|A|S Ultra Analog pack is excellent. Really good retro arps and basses. It also eschews the usual A|A|S tendency to load up their presets with FX.

Perhaps so, but it may have exacerbated it.?

I think that the Sonar announcement maybe hit Mike kinda hard. He's built a career (or at least a revenue stream) out of his CbB tutorials based on it being a great FREE DAW. He's also been doing tutorials for Studio One, but if you look at the number of views he gets on his Studio One videos vs. the ones for CbB there's no contest. He invested a lot of work in building up his set of tutorials. Now he seems to think that the best way he can serve his audience is by helping them transition to a different DAW.

Cherry Audio have a holiday gift for all, Synthesizer Expander Module. ...."a free emulation of the classic Oberheim® self‑contained synthesizer module of the same name." It's a monophonic monster, should be great for classic leads and basses. It's a faithful recreation, so only one built-in effect, phaser. So it will require external FX to sound like modern synths.

Perhaps they mean "we who are experiencing issues with sidechaining in Cakewalk." Which doesn't include me.

If it's just the plug-in and loop browser that has disappeared, press B to bring it back. Check Preferences/File/Folder Locations and make sure that those are set correctly. Then Preferences/File/VST Settings and make sure that your VST scan paths are set correctly.

Maybe it was a mid-side conspiracy? ? I, too endorse the idea of refurbished Logitech input devices. 30 years ago, I had a consulting gig at The Learning Company (when Reader Rabbit walked the Earth). Their headquarters were in the same business park as Logitech, which had a factory outlet store. That's when I first fell in love with Logitech's (refurbished) products, a love that has endured to this day. My current daily driver mouse is a refurbished Anywhere 2. I've mapped the thumb buttons to Alt and Ctrl, which is tres handy when editing.

Good advice so far. This. The PS may have zapped the motherboard when the incident happened, and/or the power supply itself may now be incapable of supplying one or more of the clean voltages needed to boot and run the system, etc. Fortunately due to their being made of certain building blocks, PC's are relatively easy to troubleshoot via substitution. If you turn the system on and the fans come on but no video, it could be a problem with: monitor, video card, power supply, motherboard, or even a video cable. I just had a monitor "die," but it turned out that replacing the HDMI cable miraculously fixed it. Glad I checked. If you turn it on and get a logo and option to go into settings, that is what indicates either an OS drive failure or corruption. But it sounds like maybe you're not getting that far. So you can troubleshoot it by substituting those components. Presumably you have donor parts from your previous system? First thing I would try is connecting the monitor to the motherboard's video out. If that doesn't result in being able to get to a UEFI/BIOS screen, then substitute another power supply. If that doesn't do it....things will be looking worse, but not necessarily enirely lost. Your OS configuration and so forth may be happily intact. Fingers crossed that all that happened was that your brand new power supply suffered infant mortality and didn't take anything else out with it. If perchance you ARE getting as far as the logo and UEFI/BIOS screen, that means that PS, mobo, monitor, and video card are all okay. Then we'll check and see if your drive is being recognized by the BIOS. If it is, there are safe mode boot and a variety of recovery options for Windows that can take you further.

How did I know it was going to be Mike Enjo? ?

You need to switch the Browser to display instrument plug-ins rather than FX plug-ins in order to see TTS-1. If you want TTS-1 to play back from a multi-track MIDI file, you must create a synth track for TTS-1 then set the output of each MIDI track to TTS-1.

I've never had one fail, but I only started using them about a year ago. For this question, the experience of one single user isn't going to help. Check the reviews on Amazon or Google.

Same, except for location of lump.

Hmm, Last HB issue of these was Vegas Pro Edit 18 and Sound Forge Audio Studio 16. Worth it to me to update my Vegas to the later version. Odd to switch to Sound Forge Pro and drop it down a version. Since you're coming from a DAW skill set and familiar with the paradigm, Vegas Pro is worthy of your consideration. My video editing skills and needs are pretty light, and I find that Vegas scales down to my level while still potentially able to handle just about anything I can throw at it (although I haven't found a way to produce a slitscan effect). I know that I'll never outgrow it. It's probably not the easiest to use, but I've found it to be the one that's easiest for me to remember how to use when I go a long time between video projects, because its workflow is so DAW-like. It began life as a DAW and there are still people who use it as one. Its main working area has video and audio tracks, and fades and trimming are performed in a similar fashion on audio and video clips. VFX can apply to an entire project, a track, or an individual clip, just like with audio clips.

If you've never spent 10 minutes fine tuning a compressor only to discover that the compressor was either a: bypassed or b: on a channel other than the one you thought you were working on, then your ears are trustworthy enough that PD has little to offer you.

The use that I've found for it is to compare EQ and compression curves between various plug-ins. Out of curiosity, as a signal processing geek myself. It is interesting to take "emulations" from different manufacturers and set their controls similarly and then observe what they are actually doing. The variation between the half dozen "Pultec" emulations I have with all set up with the same settings was....quite interesting. It showed me that there are plug-ins with their own "bypass" switches where the signal is still being altered even when the bypass is engaged. It showed me that MCompressor, rather than the smooth curve I was expecting, actually has a bit of character. As far as whatever value it might have for musical production, sometimes I want to try using processors other than the ones I'm used to, and PD can help give an idea of how to set up the new ones to behave similarly to the old ones. It probably has little to offer the "trust your ears to tell you when your knob twiddling has produced a hit" crew.

I consider them to be, as their name suggests, essential. The one I use the most is KHs Limiter, first in line on every soft synth track to prevent the output of the synth from slamming the input of any subsequent FX. So multiple instances on every project I do. Pitch Shift is great in its straightforward approach, as are the rest. As with the MeldaProduction FreeFX bundle, there's no reason not to have this incredibly useful collection of plug-ins installed.

Am I the only one who picked up on the A|A|S $49 upgrade from Ultra Analog Session to Ultra Analog VA-3 w/Motion soundpack? I also dropped $10 to upgrade Loop Engine to 2.01. Still thinking about ChordJam w/Freezr for $32.

Once you've downloaded the .DLL, just drop it into your VST2 plug-ins folder and Cakewalk should scan it and add it to your plug-ins list. If you're going to check it out, I highly recommend also installing the extra patches linked from the site that John linked to. Installing patches for Synth1 is a little clumsy, IIRC, but also well worth the effort.

That is really odd and messed up. I've been thinking about creating projects that will allow me to change synth patches within the song, but it seems like this was made much more difficult. I also have so many soft synths that it would be nice to make "patch browser" projects that quickly step through the available sounds as a preview. This will be tougher to do as well. What are the workarounds?

The headquarters of both companies is in a tiny town just outside one of the entrances to Yosemite National Park here in California. Having participated in their beta program enough to get my name in the credits for the Mixcraft 7 release, something I can tell you about Acoustica is that they are one of the most quality-minded software manufacturers that I've ever dealt with. So please report your experience and findings about this performance issue to them. They will likely want to know about it and work with you and the BandLab Cakewalk engineers to fix whatever is. Good question, and one that I can't really answer. Without being able to read the minds of the folks at Steinberg, there's only speculation. It could be that there were starting to be too many extensions to the VST spec that weren't controlled by Steinberg, and they feared losing their grip on it. Maybe they thought that being able to announce a shiny new technology that their own DAW's would be the first to support would be good for marketing. Maybe the Cubase/Nuendo developers were having a hard time working out sidechaining support in their apps and wanted to force that work onto plug-in developers. Whatever drove the move, as far as I can see it backfired. Other manufacturers (correctly, IMO) saw little advantage to supporting the new format. Rather, it only increased their coding and testing burden. Adoption was slow. When they finally applied their legal muscle to force new developers to adopt the format by refusing to issue more licenses to develop VST2, it served as an alert to participating vendors that Steinberg had too much of the wrong kind of control and that a more open and flexible spec might serve the industry better. So now there is CLAP, a competing plug-in format. As for CLAP, as long as Steinberg continues to play nice, I don't think it will become the dominant format. But I'm glad it exists, because it serves to show Steinberg that if they do try any more funny business, the industry has other options My suspicion is that if you ask anyone in the business of developing plug-ins or hosts for them about VST3, they'll tell you that the canonical DLL location is the only thing that they benefit from. I'm sure it eliminated a LOT of easily resolved support issues. However, I was so used to using custom locations for my VST2 plug-ins that I initially tried doing the same with VST3's, which of course didn't work too well.... Is it that VST3 doesn't support it or is it that plug-in and/or host manufacturers stopped supporting it? Communication between host and plug-in regarding presets in general seems to have gotten lost along the way. Where it seemed like most VST2's relied on the host for preset management, and reported their own presets to hosts' preset managers, in the VST3 era, this isn't the case. Now it's unusual for a plug-in to use that part of the spec to report their presets, and every plug-in has its own proprietary preset manager. Which can be hard to find and quirky to navigate, depending on the developer. The VST3 spec does call for a canonical location for .vstpreset files, but few plug-in companies use it and Cakewalk's support for it is clunky. That's a drag, because I like using the host's preset manager more than the ones within the plug-ins, which have to be learned for each different manufacturer.