Starship Krupa

Anyone else develop a resentment for Audified after jumping through all those hoops to download and register their tarted-up compressorwhatsit? They seem to kinda think they're hot doo-doo or something....

I have never gotten that, I guess I'm more stoic than you, or too busy writing my notoriously long-winded replies, but while we're on the topic of reactions, y'know how we all have our "Member's total reputation?" (huh-huh, huh-huh) I wanna know which reactions add and subtract to it so I don't accidentally step on some member's reputation when I didn't mean to. I'm free with the Like, because I really do think that anyone who participates in a discussion, especially new people who might be afraid to, contribute to it. Also the Thanks and the Good Idea when appropriate. But if someone posts about John Prine passing away and I react "Sad," I would hope that doesn't ding them, and similarly, if they were to post that, say, Pro Tools added pop-out channel strip plug-ins and Avid were crowing about how innovative that was, and I reacted "Meh," I wouldn't want that to ding them. Even if someone were to post that they only use WASAPI instead of ASIO because they had done A/B testing and it sounded better and I reacted "Confused," I still wouldn't want it to lower their reputation. I'm pretty sure that "Meh" is the "downvote," so I reserve that for people posting words in all capitals commanding that the developers get their act together or whatever, but I wanna know, I really wanna know. Not that anyone in this topic doesn't have rep to friggin' burn, I notice.

For me, the quest had always been for my single best go-to reverb that I could put on a send and it would sound the most like sending the track to a real or imagined 3-D space. I'd have that, and then a quiver of "character" reverbs like plate emulations, psychedelic space things, etc. When Phoenix first went on sale at PB for a tenner, I downloaded the demo, threw it on my send bus in an existing mix just with the default medium room preset and my search of 5 years came to a very abrupt halt as my mix expanded into this holographic soundstage. Yeah, forget it, every other room reverb. I'm willing to entertain the possibility that you might be able to do something as good with TrueVerb or one of Melda's M*Verbs, but preset after preset in this thing was just stunning. No grain in the tails, and I don't know what kind of processing he's throwing in there to get that spatial effect, but man oh man. In other words, get the dang thing, if you are in any way in the market for an algorithmic room/hall/chamber reverb. But you can test drive it first and see. Caveat: unlike most iZotope products, license allows for a single installation, not two. Also, the UI is not as pretty as its iZotope brethren.

I don't think my Firepods qualify me for this....?

Thanks for all the information. As I am wanting to explore more EDM production methods, I will be checking out the Matrix . I'll search YouTube for tutorials and check out Craig Anderton's articles.

I'm going to drop in again on the Matrix, thanks to the encouragement from @JoseC. I had just kind of poked at it, and looked at the documentation, and left it.

Thanks, Steve, for the reminder about Sitala. It looks like a nice little one-shot player, and TX16Wx can certainly fall into the category of "way more sampler than I need for this." Not sure why I didn't delve deeper, maybe it was the developer referring to all of their releases as "beta." I mean, at some point, release one that you're confident enough in to call 1.0. Opening the Ref Guide pages for Matrix View is frustrating because there's so much potential there. If it were better integrated with the other elements of Cakewalk. And not that better integrated, just basic stuff like being able to directly route MIDI inside the program, using FX in your cells, being able to drag and drop clips directly from Tracks without first rendering them, connecting the outputs of the MV to Console strips for processing, and recording from audio or MIDI devices into cells. Hooking up a few parts of the program to it, like you'd do with a ReWire object. It feels as if it was a big planned feature, they got it working, yay, the stuff I listed was going to be implemented in the next release, then some catastrophe happened, maybe it lost its advocate in management or something.

@Keisari, I think I know what you're trying to do: you want to take a single audio sample, like a hi-hat or kick sample, and have it play when a MIDI note sounds. As scook has said, the Matrix View is closer to what you're looking for, but at this time it's set up so that if you want to compose this way, the Cakewalk Track View and Matrix View are not integrated tightly enough that I would feel comfortable using both in a project. You can do a project in Matrix View using loops, clips, samples, and then get it over to the Track View, but for instance I don't think you can trigger Matrix cells from MIDI events in the Cakewalk Track View, if you have edited a clip using the Track View you must bounce it before importing it to the Matrix view, Matrix View cells don't have access to VST effects, etc. It's set up so that you can do a project/performance in Matrix View, then "capture" it to clips in the Track View. It's great for what it is, it's just not connected to the other areas of the program yet. If you want to be more tightly integrated with the Track View workflow, use a software sampler such as T16Wx, which is freeware, a favorite of Cakewalkers and works great as a Cakewalk plug-in.

Does the whining stop when you stop playing? Does the whining only occur when other people are in the room? Does it only occur when you play with a door or window open? But seriously, folks.... My understanding of what your setup is is that you are using an SL-990, which is an 88-key weighted piano action MIDI keyboard controller, to play a piano sound on Cakewalk's TTS-1 softsynth. Am I correct? Your Studiologic MIDI controller doesn't have any practical limit to its "polyphony," BTW, it just puts out MIDI notes as fast as any human can possibly play them. I also own one, and I also have an owner's manual. Not much to it except for how to set the velocity curves and set up splits, stuff that most people don't bother with. It has no sounds in it, it must be hooked up to a sound module or a computer to make any sound at all. Polyphony limitations are in the synth itself, which would be the TTS-1. Polyphony limitations don't show up as "whining," you just get notes cutting off short or not sounding. TTS-1 is more than adequate to the the task of a bit of piano practice, unless your practice involves holding down the sustain pedal and running down the keyboard to make all the notes sound at once. A "whining" sound would seem to indicate some kind of feedback/loopback somewhere in your audio routing. What you're doing should work fine all day long. The SL-990 is a fine controller for piano. What does the rest of your setup look like? What audio/MIDI interface are you using? You must be using an external interface, because the SL-990 is 5-pin DIN. Are you using the external interface to monitor your playing? And although I asked the question I jest up above, does the whining sound stop when you stop playing? Just curious: can you go into Cakewalk's Preferences and in the Audio/Configuration File section, check to see what your ThreadSchedulingModel is set to? It should be set to 2. If it's set to 3, set it to 2 and please reply quoting me so that I get a notification. Also, while you're poking around in the Audio section, check in Playback and Recording and see what Driver Mode you're in, and in Driver Settings to see what Latency you are running at.

I have it on good word that since the man from Mars stopped eating cars and eating bars, he is only eating guitars. BandLab support have been known, as a courtesy service, to help Cakewalk Inc. customers who have valid serials and registration codes and whatnots with their validation issues. As you pointed out, they're not parties in your license agreement with Cakewalk, Inc., but Cakewalk's licensing server seems to be one of the assets they acquired, and apparently the support staff knows how to get it to behave. Ask them.

You must select a MIDI or Instrument track before you may access the Step Sequencer. This is the message you would get if you dragged an audio clip to a MIDI track.

I don't have any ideas about top hits from today, as I went underground some time ago, but I have some fun suggestions about older hits that people might find useful if broken down using your methods. All have iconic drum, synth, and guitar (and sometimes bass) sounds: New Order "The Perfect Kiss" Rush "Tom Sawyer" Van Halen "Panama" Michael Jackson "Beat It" Tom Petty and The Heartbreakers "You Got Lucky" Billy Idol "Rebel Yell" Prince "1999"

I really have to hand it to the devs, though, for so far spending two full years polishing and tuning, smashing bugs, adding long-requested "featurettes" as I found out they used to call them. And I think we've seen some fairly big updates, it's just that they were ones that expanded upon existing features rather than being new features of their own. There was that thing with adding colors to tracks that happened in one of the first releases that sure helped make the program more visually attractive. How many people were clamoring for the Ripple Edit Indicator and now take it for granted, because of course it should have been there from the start? How about the brilliant changes to the Smart Tool and Take Lanes workflow to open the way for another type of comping workflow? Note names on MIDI notes? Fab! Those are a few things that I consider "big" updates that have a huge impact on the ease of use and the way I use the program. Ah, how about for the new users (like me) the release of the Cakewalk Reference Guide? I think we kind of take these for granted because they were such good ideas, they fit right in. Well of course we have the names of the notes in the Piano Roll. But a couple of releases ago they were just blank rectangles. Well, sure, I can change the behavior of the Smart Tool, but I remember when I couldn't and it would just choose a tool that I didn't want to use. That's why I just don't get the "still using SONAR" crew. There's so much good stuff in the new program.

Jon, what's up with the rest of your system, your video driver and whatnot? Looking back over what I wrote, I hope I didn't come down too hard on Lynx. That bit in their manual that seems to be talking smack about the coding practices of Cakewalk and Ableton Live and Studio One rubbed me the wrong way. I just consider that sort of thing to be bad form. Full disclosure: I used to write user manuals for tech companies. I happen to know some of the history with Cakewalk's business practices, and one of the things we as users have going for us is that Cakewalk, Inc. always had a close relationship with Microsoft, one that Noel and co. have maintained into the BandLab era. They pay attention to standards and specifications, and while I don't know about Ableton, I do know the early history of Studio One. It started as a project of a couple of engineers who had left Steinberg, the company who wrote the ASIO specification in the first place. These people all very much know what they are doing. The above is what I would consider more professional language. If they fixed the issue with their "work-around," there is no need to name names and cause the kind of fear, uncertainty and doubt that resulted in this thread. BTW, I had it wrong when I said that MMCSS settings had no bearing on ASIO mode performance. In Cakewalk at least, they definitely do.

Yes, I am, and lest ye be of the perception that I speak for the company, I do not, I am merely sympathetic to their position and like to think that the many years I spent in the trenches at various multimedia software companies (Adobe/Macromedia, Learning Company, etc.) gives me some insight. What I meant to say was that it is entirely possible that Sequoia/Samplitude/Music Creator has a really good-sounding playback engine in comparison to other DAW's including Cakewalk. Fun hypothetical time, if I were setting up a professional studio, the kind with clients and deadlines and outside engineers and all that, I would have a different set of criteria for it than I would for my personal home studio. First thing I would do would be to ask around and see if Pro Tools was still the most popular tool for professional recording engineers, and necessary to be the primary DAW to build the studio around. Once I had that bit of information, I would order a couple of proper A/V computers from a system integrator such as Jim Roseberry. At that point I'd do the survey I do every few years by obtaining the free starter versions of the full-featured DAW's, Studio One, Cubase, etc. and trying them out to see how they stacked up against Cakewalk. At that point I would choose two DAW's to build the studio around, one of them probably still Pro Tools, the other likely Cakewalk because I'm familiar with it, but maybe not. I run Cakewalk here at home because the BandLab announcement came just as I was outgrowing Mixcraft and I checked it out and liked the feature set and the sound and saw that it had potential. I was and am very interested to see what happens under the BandLab stewardship. I predicted good things and am happy that so far I was right. I trolled the naysayers relentlessly and with great fury on the old forum, so I would have been kinda red-faced if things had turned to poo.? Even the forum is better and getting better all the time. I especially enjoy the relative lack of defensiveness, which may be down to the fact that there's not so much to be defensive about with CbB!

I guess it just needed cooling.

Why do you think your missing plug-in issue has something to do with "paid for life" or whatever? BREVERB as far as I know doesn't have a registration that expires. Have you gone into preferences and made sure that a plug-in path didn't somehow get deleted?

Jon, since you're obviously having some serious playback issues, as I've read in your other posts, could you do as I've done and put more about your system's specs in your sig? There are so many variables with hardware on Windows systems, I know you have more trouble than most and I seem to remember you are using a PCIe card for audio, but I don't remember what version of Windows, what video card, etc. Also, regarding Samplitude's playback engine sounding better to your ears, that is entirely possible. MAGIX claim to have completely overhauled their engine about a year or so ago up and down the line all the way down to Music Creator. There are some who will say "all DAW's sound the same, it's been proven," but that statement can't be true, it makes no sense. For it to be true, every DAW would have to use the same summing algorithms when mixing, use plug-ins the same way, implement panning the same way, and on and on. The statement could only be true as far as recording an audio test file with no effects, then playing it back with no effects, which is not what DAW's are for. I was a user of Mixcraft before I tried Cakewalk, and I noticed the difference immediately. Cakewalk sounded smooth and silky by comparison, Mixcraft harder edged. Also, there is playback and there is mixdown/bounce, which are two different processes. A DAW developer may choose to cut corners on the playback engine in order to make it more efficient, which could be why Mixcraft so seldom drops out on me compared to Cakewalk, but Cakewalk sounds better. I know from studying the two of them that Mixcraft isn't streaming audio from the disk during playback, unlike Cakewalk.

It sounds like ein grosse hassel, but A|A|S sound packs are pretty irresistible.

Often a stuck plug-in, so test it with a project with no plug-ins. If you can open a project with no plug-ins and close Cakewalk and then open it again, work your way back from there adding your favorite plug-ins until you find which one Cakewalk is choking on. At that point, you may be able to switch to or from the VST3 or 2 version, contact support, etc. or at least rule out a plug-in as the source of your trouble.

Then you should have been around when the demise of SONAR and the entire Cakewalk, Inc. was announced. SONAR was a paid product. BandLab's Cakewalk, on the other hand, isn't dependent on the sales of licensing fees in order to thrive, therefore its survival is not as tied to the fluctuations of the economy as a DAW that depends on selling licenses for revenue. How many people are shelling out $300 licenses for DAW software right now? It's the payware titles that are going to be looking at trouble. Furthermore, AFAIK, Cakewalk's development team already mostly if not entirely work in home offices, so there likely hasn't had to be a large adjustment in terms of work logistics. They're already set up to handle a situation such as we find ourselves in. BandLab is a well-funded company who like to acquire and nurture much-loved MI brands. Cakewalk is one of four free DAW's in their portfolio. One of the side effects of not needing to grub for license fees is that when the developers want to really work on the product, they can hold the next release longer than usual to make sure that the new feature(s) are working properly, that whatever bug fixes are sound, etc. without worrying that the company needs upgrade license money to pay their salaries. So kick back, relax, learn something about Cakewalk you didn't already know how to use. Wait for the next Early Access release to ooh and aah over. Honestly, if I were a Logic X or Cubase or Studio One devotee I'd be much more concerned about disruptions in development.

Progress? Do you mean progress on learning whether Lynx are interpreting Steinberg's specification correctly when they say that no application should ever set the priority of the driver thread, and why they think they know that Cakewalk, Studio One, and Ableton Live! are setting the priority of the ASIO driver thread and if that's actually the problem when their card fails to work smoothly with these products? That is cause for pondering. It seems odd, PreSonus has more than a little bit of experience working with ASIO drivers and the hardware that uses them, and the team that started Studio One came to PreSonus from Steinberg. Shoot, my 15-year-old Firepods are still going strong, 4 versions of Windows down the line. With a product that whines right out of the box about having driver compatibility issues with 3 different popular and established DAW's I guess you're kind of rollin' the dice anyway. Is it too late to maybe find a card with more robust drivers? If not, it sounds like Jon's good at finding audio software that's compatible with their cards. I think he said that on his system it's a matter of course that Cakewalk's the only one that the Lynx chokes on. I presume there's no Studio One or Ableton Live! in the picture? @Jon White, if you were having problems this severe I'm sure you must have opened a ticket with BandLab's support about this issue, what did they say about it? Note: MMCSS and ASIO have nothing to do with each other. MMCSS is part of Microsoft's WASAPI specification. ASIO is a Steinberg invention and designed to bypass Windows' built-in audio driver systems.

Also, if you actually are running SONAR at this late date, give the latest version of Cakewalk by BandLab a spin. The audio engine has had some nice optimization performed on it in the 2 years since BandLab's been in charge of it.

To boil it down, the user tried a performance tweak that had unintended (and unexpected) consequences. To take a wild guess, I'd say that with the more aggressive thread scheduling, whatever thread(s) services MIDI interrupts somehow keeps missing the bus (so to speak) on certain systems, and the MIDI latency keeps adding up to the point where it's noticeable and then unusable. I think at this point it's a "doc, it hurts when I put my arm like this" issue. Works on most systems, just not on mine. My ThreadSchedulingModel only goes to 2, but I won't worry that someone else's can go to 3. The computer is a hand-me-down, Some might call it a throwback of sorts that Cakewalk uses and exposes such things as .INI files in this day and age, but I suppose it's the result of its long heritage. I don't know how other DAW's do it, maybe they have a program-within-the-program that scans the hardware and sets everything to what it thinks is optimal based on processor type, clock speed, amount of RAM, etc. or the engine adapts on the fly or it's just one size fits all or they do it the same way Cakewalk does, with config files. BandLab has a support staff to recommend necessary changes, anything else is optional on the users' part. It's like editing the registry: back it up and don't even try if you are not good and sure of what you are doing.

What he said. This is a known issue on some systems (including mine). If your ThreadSchedulingModel is set to 3, set it to 2 and I'm pretty sure your issue will vanish.