Starship Krupa

Follow these instructions to do a clean install of Cakewalk: https://help.cakewalk.com/hc/en-us/articles/360034066393-Clean-Install-Cakewalk-by-BandLab

Innit nice? Yeah, cool destructor effect. Noise Engineering's two freeware synths are pretty interesting too, although I haven't spent much time with them. A lot of big goth-y grind-y Darkwave pad sounds.

You can add me to the chorus of "I tried it and it works over here." However, the above statement jumps out at me. I haven't done any video for broadcast, never messed with SMPTE. Can you fill me in on the purpose of this? Does the client/instructor require a SMPTE marker at the start and end? Did you fiddle with the clock source settings? I've never chosen any clock source other than "internal" or "audio," but I can see where it might make a difference. I don't have much time to dive more deeply, but it might be helpful for all involved if you posted your version of this: Seems like there are multiple things in there that could result in what you're seeing if they were set a certain way. The documentation says that SMPTE/MTC sync is for when you have an external device generating either SMPTE or MIDI time code. Which clock source are you using? Also note the timecode format. As you can see, mine defaults to 30 FPS non-drop, while my video is, like yours, recorded at 29.97 FPS. The Cakewalk documentation says this about that: "29.97 FPS Non Drop-NTSC non-broadcast and short length video in North America and Japan. Used for some music projects. This setting synchronizes the video perfectly with Cakewalk, but the sequencer position displayed in the Now Time and Big Time displays will gradually drift and become incorrect over long periods of time. The audio and MIDI synchronization to the external device will not be affected by this discrepancy. "30 FPS Non Drop-Most music projects and some film in North America. This is the best choice for any music project and should be used unless the situation dictates otherwise." In oft-too-typical fashion, the documentation doesn't specify which music projects want which, just "some" and "most." Now, for the sake of confusion, because @Mark Mitchell posted in this thread instead of starting his own topic, we are dealing with two different users with two different computer systems and two different issues. @Malinois is running an onboard CODEC with WASAPI Shared and is having draggy video. First thing he needs to do is switch to WASAPI Exclusive and try it again. Mark Mitchell is having a different problem, he's running a MOTU interface with ASIO and his recorded audio cues aren't lining up properly with the video And fellow old dudes, you know I love ya, but as regards hating on onboard CODEC's please lighten up on that particular finger point. While, yes, it's best practice to use a good interface with an ASIO driver when recording, the facts of today are that way more people than in the past are using notebook computers to compose, mix and edit, using the headphone jack to monitor. You want to swear that Cakewalk doesn't play as well with onboard hardware CODEC's? Fine, but if that's actually the case in 2022, then Cakewalk sucks. What kind of hardware do you think schools use? Do their computer labs have Scarlett interfaces plugged into every computer? (my guess: probably not). What kind of computers do you think that 99% of college students living in their residential housing use? (my guess: laptops) How will someone who is completely new to DAW's initially try out different ones? (my guess is that most of the time, they'll just plug into the computer's headphone jack) Can Cakewalk afford to suck in those scenarios? BandLab's main page for Cakewalk by BandLab shows 3 computers running Cakewalk, two of them portables, no external interfaces in sight. Noel Borthwick, the man himself, tests Cakewalk's performance on a system using only the onboard sound chip. But if you want to create and reinforce a reputation for Cakewalk not playing well when using the onboard CODEC to monitor, keep it up. The word will get around eventually. All it takes is one snotloaf to quote a forum post out of context on Reddit for it to become an "issue to consider" when choosing a DAW (which I'll probably have to go on there and debunk once a week). In this day and age, it can't be a given that using onboard audio is going to cause problems with Cakewalk. If there are cases where it does, the developers need to know right away. What make and model of computer, what hardware CODEC, etc. It has to work well. I don't care how many systems worked better in 2000 once they put an Audigy or Echo card in. That's old information. WASAPI has been around for 15 years, longer than some Cakewalk users have been alive. Does the anecdotal information you're going by date back that far? I've had to adjust mine a few times over the years. Brands of video cards, brands of CPU, laptops vs. desktops, etc. From what I've observed across multiple systems in the many years I've been building them and using them is that onboard chips work just fine with Windows in WASAPI Exclusive. The playback is pretty much as smooth as using an ASIO-equipped external interface. On one of my systems, onboard chip with WASAPI Exclusive playback performs better than with my brand new Presonus USB Studio 2|4. I figured out why, too (using Resource Monitor and LatencyMon): the USB host can't keep us as well as the onboard chip's more direct connection to the rest of the chipset. For sure, it doesn't sound as good, due to better jitter control and supporting analog circuitry in the Studio 2|4, but it's easier on the audio engine. Believe it or don't. The USB driver goes nuts according to LatencyMon when using the external interface with its ASIO driver, and everything quiets right down when using the onboard sound. Which makes sense to me. Fortunately, with my ancient Dell Latitude E6410 (mfr date 2011), playback with the onboard sound chip works great (in WASAPI Exclusive, somewhat less so in Shared). When I want the best listening experience I plug in the Presonus, but it just doesn't work as well when mixing and editing. I get pops and clicks no matter how high I crank the buffers. Think about gaming, where you typically use onboard Realtek CODEC's. All the horsepower they use for audio and video processing, 60 frames per second of texture-mapped 3-D in real time, with whatever binaural or Dolby or whatnot fancy spatial audio processing in a situation where frame rate is paramount, and you can't have any bottlenecks. As we know, it's gaming that drives the development of cutting edge PC hardware. They're not going to put a bottleneck into those systems in the audio CODEC. Although there is a small market for internal PCIe sound cards for gamers, I've never seen a gaming enthusiast/system tuner say anything about Realtek's CODEC's being a possible drag on frame rates or overall performance. The usual word is that theoretically, a sound card can offload tasks from the CPU, but then the CPU has to manage the extra USB chatter so it's kind of a wash. Is it really too much to ask of Cakewalk to play back a video and an audio track and record at the same time on similar hardware without glitching or lagging or things getting out of sync? But it might work if I buy a nice audio interface? Please tell me, because if I can't expect to be able to mix and edit on my laptop without lugging an external interface around, I'm ultimately going to have to find a more capable DAW because I want to be able to go mobile in times when I don't have access to my studio system. If I shouldn't even bother trying to use onboard sound with Cakewalk, well then, shoot, I won't.

From the video, I get the impression that they mostly modeled the analog circuitry surrounding the converter itself, with the exception of the rate reduction knob. Fair enough. The sample sound files of course had that same problem that a lot of such things do: the "after" examples were louder, so impossible to tell exactly what the thing is doing. As for MWaveFolderMB....ugh. I just took the non-MB version for a spin and it sounds like total crap, and not in a good way. I'm not afraid of sound destruction; one of my favorite plug-ins is Freakshow Dumpster Fire, and I have both of the other Freakshow FX as well. But MWaveFolder sounds like someone trying to play music through a toy walkie-talkie with a half-dead battery. Which seems on paper way better than it actually sounds. I can't imagine that multi-band would help it be more appealing. I know it's supposed to be harsh, and believe me, I used to go to shows that Survival Research Labs and Poison Gas Research used to put on in San Francisco, I am not averse to creative applications of noise. This doesn't sound cool, it just sounds like....crap. I'd love to hear someone using it just to see if I had the application wrong. If I wanted that "musical greeting card with dying battery" sound, I'd use MBitFun or MWaveShaper before that thing. Noise Engineering Ruina is even better. Also: notice how there are no videos or sound samples on their website for this effect.

Hidden gem: if you have your eyes on a Meldaproduction bundle that includes MWaveFolderMB, they'll give you €24 credit toward the bundle if you have a license for this. They assume that if you bought it from a 3rd-party vendor that you got it for 50% off list, So, maybe worth it for that alone even if, like me, you never even touch the FreeFX Bundle version. As for the others....yet another fake sidechainer? And the very idea of a DAW plug-in that emulates the flaws of an early converter is....I don't have the word for it. Unfathomable? "Make your sounds really not pop in the mix! Add fabulous 'digititis.' No JetPLL!" Still, every Meldaproduction plug-in is....precioussss, yes? My precioussss Meldaproduction FX. We loves themmm.

Whytse did a funny Snake Oil? video on it. He didn't seem to get the joke, though. The detailed "retro" visuals seem to me to be an obvious pee-take on the plug-ins that have "wear marks" and rack screws in their graphics. Like, you want retro, we'll give you retro. And the graphics showing the compression actually look useful. If I didn't already have a zillion good compressors, I might spring for it at that price.

Wow, great mic for anyone who managed to get the deal. I got a crazy deal on a pair of them years ago, used. It's an industry standard, like every studio starts with a 2020 and a 57.

C'mon, fellow Meldamoonie, Vojtech has been using this model for years to great success. It gets attention and warm fuzzies for the brand "if their free stuff is this good, the payware stuff must be fantastic." The responses I got at VI-Control when I mentioned that I cut my teeth on MCompressor were very interesting: turns out that many people (and Vi-Control attracts a lot of pros) also did so and therefore became hooked on Meldaproduction products. MCompressor is a truly great effect. It's a freebie, but if someone trips on using a freebie effect, they can even make it payware if they want. ? And you and I both know how hooked you can get. I've spent more with them than any other software company, including the pile of reference credits I've earned. The ref credits I've earned over the years is well over 100 euros, which means that I've been responsible for well over 1000 euros in sales for them. As are you, even more so. And as far as buyer bitterness, I've pointed this out before: you had the use of the FX for years before us cheapskates. The idea that we're somehow being cheated when a product that we bought later becomes much cheaper is a fake idea. We had use of it when we were hot for it. The purchase gave us a dopamine squirt (and it's usually a bigger squirt than when you get it for free). Your licensing bucks helped make them successful enough that they can now give things away for free, and you get the new freebies to put in Snap Heap or use standalone like I do (Limiter sees a LOT of use around here). But you know that. You'll also of course benefit from their new approach as they seem to be into continuing to release cool little toys like this dual delay. I'm a sucker for interesting delays.

Agree totally. Feature Request it in Feedback Loop. My favorite Useless Cakewalk Tooltip is when you hover over the note duration buttons in the Piano Roll. Over the quarter note symbol the tooltip says...."quarter note." Unless this is some kind of teaching device, how many people know what a quarter note is without also knowing what one looks like?

Sorry, I had it mixed up. If you look closely at that Record button, it has a little arrow in the lower right corner, which in Cakewalk's iconography, means "more features are available under this button." The only way to figure out which button, click and hold, whatever, is unfortunately just by experimenting. But at least you know that's what the little arrow means.

Dawg, chill. ? While you apparently weren't looking (as I wasn't for a while, the 80's? Really?), there started to be a thing called "soft samplers." Sonar at one point even included one. While some emulate those old Akai or whatever hardware ones, there are others that are much simpler samplers, they use features that can only be available on a computer. The idea behind these soft samplers is that rather than copying and pasting your hi hat sample 100X, you can trigger the sound with a MIDI note. Or in another case, rather than trying to stack samples of different pitches to make chords, you can spread them out on the keyboard. These allow you to even play in real time where you want the sample to sound. Yes, if you have an audio event that only repeats once or twice (see the dialog samples in "Sensation" from the link in my sig), it's easier to just drop them on the timeline where you want them. But if I were using a rhythmic element like someone shouting "yeah!" 10X in the song, maybe stuttering it, it's much easier to just assign it to a soft sampler slot and trigger it with a MIDI note at the appropriate times. Bottom line, most (if not every) other major DAWs include a soft sampler instrument of some kind. Why would they do that if the "premise" were "wrong?" It's a popular workflow. Sometimes us auld fahrts gotta get used to these things. Different features for different creatures.

You're not missing a step, you're doing one that makes your tracks play at the wrong tempo. Why are you telling it to import at the project tempo rather than leaving the clip at its original tempo?

What you have been fiddling with is bit depth. Bit rate is the selection for 44.1KHz, 48KHz, 88.2KHz, etc. A good tool for checking bit rate and depth of files you're working with is the freeware MediaInfo.

If you right click on the Record button you will get an option to set the record mode to step. Off the top of my head, I can't think of a way to make it more front-facing, although there might be. How were you expecting to find it? Cakewalk is a huge and venerable beast, and for some things, you really do need to RTM, as you did. Have you downloaded a copy of the Reference Guide? That's a good one to have on your phone for when you're waiting in line or at the doctor's office.

Especially when bx_cleansweep is also free. Lamest PB freebie in years.

Support: "Where did you purchase the interface?" Erik: "From some sketchy dude in what looked like it might have been a meth house in East Palo Alto." I didn't read the fine print, but if it says "original purchaser," then I don't technically have the right to any of the licenses. Fortunately, Sketchy McMethhouse hadn't registered it. I'm fine with how the cards fell. If I ever have need for Studio One, I'll drop the 50 on the current Artist.

If there's a license for 5 or 6 somewhere in my account, I sure haven't been able to find it. These licenses in question where you "should" get the current version, are you sure they were referring to licenses that came with the purchase/registration of an interface? I always just figured that they handed out v. 4 licenses so that they would be immediately upgraded if the user had an interest in actually using the software. If I had the right to the version that was current when I registered the unit, that would be v 5.

That is the way it should work. Unfortunately, when I registered my Studio 2|4 back in February, what I got was a license for Artist 4. Obviously, at that point, 5 was the current version. I like Studio One, to the point where I was considering dropping the $49 to upgrade my Artist to 5 in order to get the VST support. Still waffling about that. I already have a secondary DAW in the form of Mixcraft.

Yeah, that designation is confusing, especially in light of the fact that many of their deals are free trials of services and bundles. It should more properly say "limited time offer" or "time-sensitive deal." Anyway, about Massive. I was psyched to get it, and I guess I still am, but.... The past few days I've been running through the amazing number of presets it comes with (apparently NI have released multiple expansion packs for it that are included in this version). No end in sight there, as so many may also be downloaded for free. They're not exactly inspiring me, though. I do not like "Car Alarm Trance" and most of the patches seem designed for that sort of thing, like the sort of "exciting electronic dance music" one hears in commercials for water parks. Every so often I need to take a break because I can't stand to hear another stacked unison sawtooth blast. I am hoping that somewhere in there will be some deep house/ambient fodder.

I can't say what's exactly going wrong in your case, but I have had it happen that I was accidentally using the VST2 version of an instrument on system A, then built system B and (as one does) installed the VST3 version of the instrument. At which point Cakewalk complained that the synth was missing when I tried to load a project (that used the same synth) from the old system on the newer one. This is even though Cakewalk is supposed to automatically substitute VST3's in when both versions are available. Apparently the rule (if it's a rule and not a bug) is that if you start a project using the VST2 version, your project is going to need to continue using the VST2 version. My guess is that it probably goes the other way, too. So check and make sure you have the same configuration of VST2 vs. VST3 installed on both systems.

Especially in light of: ? All I can say is....bring a laptop with the entire set on it so that you can mime to it when your Cakewalk Pro Audio 9 setup finally packs it in for good. Which will be during a gig, after which you will then be forced to learn a new program in time for the next one. I suggest you not even bother trying to get it to work under Windows 10. Even if you got it to the point where it seemed stable, there's no way you can test it under every condition you might encounter on stage. This almost seems like an anxiety dream: I'm up on stage to do a set and I look down at the screen and it's Cakewalk 9! And I forgot to put on trousers before I left home. And all of my teachers and the cute girls from high school are in the audience. If what you're doing with Cakewalk is playing backing tracks, and you don't like the complexity of the current interface, there's a handy feature called workspaces that you can use to hide elements of the program that you're not using in a given context. It's very customizable. There's also a free program that's purpose-made for that scenario called Cantabile Lite.

You can either drop Cakewalk, crack your wallet, and get a DAW that comes with a sampler or do what the rest of us who want an integrated sampler are doing: pick Sitala or TX16wx and wait for the Cakewalk devs to implement it (and crossing our fingers that they do it in such a way that we find it useful). To me, the rest of Cakewalk's features balance the fact that for now I have to bolt on a sampler. I have a reasonable expectation that this highly-requested feature will eventually be delivered. If it's a simple phrase sampler with some built-in editing that you want, Sitala works pretty well. You can drag Cakewalk clips directly on to pads from the timeline and/or drag and drop samples from Cakewalk's Browser. As long as you don't stew about "oh noes, mys DAW haz no samplur" it'll work. I agree with the first half of your statement but there are no guarantees about the level of impact a sampler will have on CPU resources, whether it ships with the DAW or not.

I'm not sure if I understand your issues completely. Are they that you no longer see a Start Screen, and Cakewalk is launching a web page every time it starts? If you want to see your Start Screen, select File/Start Screen. To make this permanent, go to Preferences/Customization/Display/Other and check Display Start Screen. As for opening a web page every time it starts, I hope support were able to straighten that out for you. That's a new one to me.

This of course has nothing to do with activation, online or otherwise, lest anyone reading this get that idea. For people who suffer unintended consequences during comping, I always suggest switching tools to the dedicated (Edit, Draw, Erase) ones rather than relying on the Smart Tool to do what you expect. Yes, the Smart Tool is great, yes, you can access features with it that you can't with the dedicated tools, but with that great power comes greater ability to screw things up. You can switch instantly using the F8-9 keys, and if you hold the key down while you're doing your editing task, it will even switch back to whatever tool you were using previously.

That's like AIR pricing.