Jump to content

Lord Tim

Members
  • Content Count

    1,433
  • Joined

  • Last visited

  • Days Won

    2

Lord Tim last won the day on August 25

Lord Tim had the most liked content!

Community Reputation

1,196 Excellent

6 Followers

About Lord Tim

  • Rank
    www.lordtim.info
  • Birthday April 2

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I never bothered to match audio exactly to video for an export to video in CbB, honestly. I'd export the audio only and then import that into my NLE for sync to picture later, so any padding was never much of a big deal to trim off if need be. So long as the sync doesn't drift during the program, I'm good with it. (Doing sync to some flavours of h.265, on the other hand... Argh. Good luck with that.) Should it export with no padding? Yeah, absolutely! But if you're not trying to do everything in CbB with the video export, it's personally not a big deal at all for me.
  2. I use h.264 720p/25 (or 30) MP4 and generally have no issues with sync. If you have a fairly beefy machine you should be able to get fine performance from 1080p or higher frame rates, but I'd be inclined to not go past 30fps anyway.
  3. Yeah, if you've set that then it shouldn't be happening. Like I said, I'm just making educated guesses at this point, honestly. Without looking under the hood or checking out a crash dump (or more precisely, someone on the dev team doing that so they know exactly what they're looking at) it could be any number of things, even a faulty audio interface, heat issue... you name it. Let's get some solid facts.
  4. The more I think about this now, the more I'm suspecting a power profile thing if it's happening after a specified amount of time no matter what. Something that may be hanging up the UMC's audio driver and Cakewalk is sitting there waiting for a response that never comes. If this was a busted library or something it'd crash either immediately or far more sporadically. OK, do this then: Work as normal, wait for it to hang. When it does, follow the instructions here: This will show exactly what's going on with the crash to the Cakewalk team and you'll have a place to start looking to see what's weird about your setup that's making this happen. Like I said, this isn't normal. I can leave my stuff powered up overnight with a project open and come back the next day and just keep working (mind you, I make sure I save if I ever do anything like that! Computers are computers after all 😒)
  5. It shouldn't, and for most people it doesn't. I've used Cakewalk stuff for many years and this is the most stable it's ever been for me, and most of us here on the forums, so there's something going on in your particular setup that's either broken, or is misconfigured, or is exposing some bug in Cakewalk that most of us aren't experiencing (not to say it can't be a bug at all - this could be something legitimately wrong inside Cakewalk, but something particular to how you have your system set up might be exposing it). So to help us help you, please tell us: What are the basic specs of your machine? CPU, RAM, etc. What OS are you running and what version of it? Are you running the latest version of Cakewalk? What plugins you're using in this particular project that's crashing, and what type are they (VST2, VST3, DX, etc.) What is your audio interface? And what driver mode are you running it in (ASIO, WASAPI, etc.) What other audio or video apps on your machine? Have you installed any generic drivers like ASIO4ALL or any "low latency" driver from Magix or Steinberg? As far as the crashing goes, my guess is it's almost certainly plugin related that's triggering it. You can set the error crash severity to catch more of these errors instead of Cakewalk crashing to the desktop silently, but let's start with the info above so we're not just pulling suggestions out of thin air for you.
  6. I was about to agree with Jackson but it looks like the Console Emulator Bus is doing that for me. If I instead put a Console Emulator in on a track it works as expected. I'd probably put that down to an oversight when it was made, where if it's off, why would you need the needles? But you're right, it probably should have them there regardless.
  7. ^^ Please don't follow this advice, folks. MME is the worst possible driver model that you can use (other than actually broken drivers like the Realtek ASIO driver or the Magix or Steinberg Low Latency driver), and is only there as a last resort if everything else fails. It will give you significant latency and poor performance overall. ASIO4ALL isn't a real driver; it wraps WDM up in a way that DAWs see it as an ASIO driver, which is entirely not necessary for Cakewalk since it supports WDM directly, and it can actually interfere with proper drivers. If you have a proper audio interface, it will come bundled with ASIO drivers, or have them available from the manufacturer's website. Always use this as your first option, it will give you the best performance in every way. WASAPI works well for in-built audio like Realtek, with the caveat that WASAPI Exclusive will give you better latency but may cause issues with other audio apps while Cakewalk is using the driver (and vice versa), and WASAPI Shared will always have at least 10ms latency. If you have a proper interface, WASAPI might work OK but ASIO is always going to be a better choice if there's a driver available. If the only thing that works on your system is MME, then you aren't running a proper audio interface. And then, if MME is working but WASAPI isn't, this is pointing to some other bigger problem that needs solving elsewhere, likely something else has control of the audio driver. Solve that and you won't need to resort to the worst driver model.
  8. They actually fixed that for the Gen.2 onward, which definitely made recording DI guitars much easier, especially if you use hot pickups like most artists I record do!
  9. There are some things that Cakewalk installs that MUST remain on the system drive because of certain conventions. In particular, some shared system libraries or the location of some plugins so it remains in compliance with the spec. What I'd recommend is setting up a junction point for your Cakewalk program folder so to the system it will still look like it's on your system drive for all intents and purposes, but the files will actually be on whatever other drive you prefer. Make a Cakewalk directory on your D drive, move all of the files over from C:\Program Files\Cakewalk to that Cakewalk directory, and then from a command prompt, do this: mklink /j "C:\Program Files\Cakewalk" "D:\Cakewalk" (or whatever folder you made) I'd probably recommend doing the same for C:\Cakewalk Content and C:\Cakewalk Projects too I personally have both of those folders on a different drive to my system using this method, but I decided to have the main files still installed on my system drive. I'm aware the question was "During the install" and for that, the answer is "no" (unless you set up those junctions first) but there's a good reason for that. I'd also suggest that if your drive is that low on space, it's asking for trouble going forward in general. That directory junction trick will get you out of trouble in the interim, but a bigger drive is definitely a good idea.
  10. This sounds like a broken system library or (although less likely) a hardware issue that's being exposed when something is stressing your system, like loading a DAW. The specs on your system are pretty borderline for running a DAW, honestly, so you might just be on the edge of things freaking out if something isn't playing 100% nice (I had a system not too far different to that for ages and it was always a big juggling act to see what I could get away with, especially for larger projects). What OS are you running? If it's not Windows 10 or later, there's a very good chance it's a system redistributable thing. Try Noel's suggestions here first: If that doesn't work, capturing a crash dump might be useful for support to have a look at:
  11. That's DC Offset. It's not particularly harmful, although it can affect how loud a track can be processed to a point as you mentioned. To remove it, I'd recommend using something like Audacity (which is freeware). If this is part of a project inside Cakewalk, do this: Find the offending clip by right-clicking it and choosing Associated Audio Files from the context menu, and make a note of the name and path to it. Close Cakewalk, then go to where the file is, open it up in Audacity, and follow the instructions in the manual here: https://manual.audacityteam.org/man/dc_offset.html Save the clip, re-open Cakewalk and it should load back in with the DC Offset removed. IMPORTANT: This is a destructive process though, so once you do this, you're stuck with it. What is probably a better idea is to bounce down the offending track as an audio export, do the DC Offset work on that, then reimport that back in as a new track, and then archiving or deleting the original track. That way you have a safety net in case anything goes wrong. ... or, you know, just go to Process > Apply Effect > DC Offset rather than going through all of that. I keep forgetting that's been there for decades. 🙄 Honestly though, there's a good chance you'd never notice the difference if it's just a part of a mix. I'd be inclined to not worry about it. Of course, if these are just exported stereo WAV files, it's easy just to open them up in Audacity directly and do the DC Offset work on them without needing to do most of those steps.
  12. That's how I'd do it, but if you don't want to create a new bounce, the other option is to do something like this: Make a new audio track, ensure it's track interleave is set to stereo. Then press the Take Lanes button, and add a lane so there's 2 lanes in the track. On your mono tracks, set your Edit Filter to Clip Automation > Pan Drag one of the mono track's Pan envelopes all the way to the top to set it 100% L, and do the opposite on the other track so it's 100% R. Then set both of those tracks back to Clips in the Edit filter. Then drag both of those clips into each of the Take Lanes you made in the stereo track you added. Now, are you saving any time doing this at all, compared to a track bounce? Nope! But if you don't want to make any new audio bounces, this gets you there.
  13. Use AudioSnap, Copy as MIDI: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioSnap.05.html Basically, detect your transients on a track, making sure that there's no rogue notes. Then click the Copy as MIDI icon. In your MIDI track that's routed to Session Drummer, set your Now Time to the start of the project and do Paste. You should have the MIDI paste into that track, in time with the transients you detected, and (if I recall correctly) will be MIDI note 36 by default, which should correspond to a kick drum.
  14. When your plugin doesn't come with an uninstaller, but instead comes with a penicillin shot 🤔
  15. No, as of today Cakewalk only supports VST (2 and 3), and Direct X. It looks like it's starting to catch on, so it's worth putting in a feature request to support it.
×
×
  • Create New...