Jump to content

Wong Jian Ming

  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

Recent Profile Visitors

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

  1. As the title suggest, found out that the volume automation in one of my tracks is causing Cakewalk to be extremely laggy and sluggish. After deleting the automation, it goes back to all being smooth. No plugins are enabled and there are only 3-4 audio tracks with no VSTis at all. The context is that I was editing a podcast using the ripple edit, which ended up making a bunch of nodes in a volume automation of another track. Somehow the project got more and more laggy as i continued to ripple edit more stuff down the timeline. The video below shows this behaviour: At the start, cakewalk is extremely unresponsive as i tried to move the playhead around and to zoom in. As soon as I delete the automation, its all smooth again. And when I brought it back using ctrl+z, the lag returns. Some kind of weird memory leak thing?
  2. There's definitely a better way than what you're doing. I've made a video specifically for you here: I've also got another video on the channel talking about editing multi-tracked drums in Cakewalk in a more efficient manner (its rather old now but I guess it may be still relevant for you):
  3. this solved the issue for me too! never knew this existed...
  4. Thanks for the clarification. Either way my issue clearly shows that the inspector is also not showing the track that is in focus.
  5. Thanks for the tip but it won't exactly work for me as I do have an entire album worth of songs in a single project file. So I wanna use task recall to export each song in the same project as its own audio file.
  6. I've noticed this issue with task recall, not sure if this is expected behavior: So basically I've got a task setup to export a certain time selection for the entire mix. However, if i make some new cuts on a clip, those clips with the new cuts wont have any sound. See my video below which shows this behavior. If this is the expected behavior, then it kind of doesn't make sense that everytime I make a new cut I have to recreate a new task to include the new clips. Is there a way to create a task recall that always renders out everything in that time selection?
  7. SOLVED: As the title describes, my inspector is not following my track selection in the track view or console view. See video below: It only happens in this project file, I've tried deleting all the tracks and buses and inspector is still not following the track selection. I have tried opening this project in safe mode with no plugins loaded and it works fine. Am I missing out on a setting that disables the inspector following track selection or something?
  8. Hey! Thanks for the detailed reply, 1) PDC is what I need and hence the PDC button is not activated. (hence PDC active) 2) this is what confuses me. One would think that playback and live monitoring should be the same, but it isn't the case. So I hope maybe the Cakewalk team can chip in here. There seems to be more happening than it seems. 3) I've learnt this the hard way trying to get band to play along with a backing track loaded up in Cakewalk while live monitoring is on. While they are playing live, they are all in time, but on playback, they are all definitely off with the backing track. I've overcome this by just feeding the backing track as a live input and going through the same live monitoring. Actually no musician is listening to the live monitoring feed except for me (where I'm controlling the livestream mix which is significantly delayed due to the latency). What I'm simply trying to do is to mix a live performance thru a DAW to be sent to a livestream, every musician is still listening to monitor mixes straight out of a Behringer X32 rack.
  9. I need some help on understanding Plugin Delay Compensation and how it works. Here's the setup, I am trying to run a band setup (16 channels of multi mic drums, gtr, bass and vocals) through Cakewalk with plugins on individual mics and sending this processed output (by turning on live monitoring) to my livestreaming software to stream online. There is obvious latency, but that is no problem as the video feeds are usually being received late by the streaming software too and I can just resync them by delaying the audio or video (whichever is later). Here the problem, by inserting different plugins on the different drums mics, some offending plugins are causing the live monitored signal to not be compensated correctly thus arriving later than expected, resulting in audible flam between drums. This only happens on the live monitoring, when playing back the same recorded tracks, it plays back with all the drum tracks in sync. So my hypothesis is that certain plugins are not reporting the correct delay for PDC to correct. Therefore my guess for a probable solution is to use a latency plugin (something like voxengo latency delay) to place on every track so as to make it the highest latency plugin on each track thus making all tracks being compensated by the preset amount in Voxengo Latency Delay. However, even after doing this, the obvious flam is still audible. Is my understanding of PDC or somewhere Anywhere is an excerpt of Voxengo Latency Delay function: Latency Delay is an auxiliary AAX, AudioUnit, and VST audio plugin which allows you to compensate latency produced by any audio plugins, instruments and processes which produce latency but do not try to report it to the audio host application. Latency Delay introduces 10000 samples latency itself and delays the audio signal by 10000 minus the specified amount of samples or milliseconds, thus eliminating the unreported latency. Please note that audio host application should support the latency compensation itself for this plugin to function properly.
  10. This is a great update especially the new export update will really save a lot of time! However I'm having some issues with my kontakt (midi) drum tracks actually speeding up (gradually) in relation to my audio tracks when exported... This does not happen when I'm using real-time bounce. Thinking its got something to do with the new bounce buffer size. edit: am using the latest build 99
  11. I've actually done that and stripped it down to only 1 track and the audio clip. I copied the audio clip into an entirely new project file on the same computer and observed two different behaviors (you can see from the video below): 1) if i were to bounce a specific range/region = the problem happens 2) if I were to select the affect clip and do the bounce = the problem disappears I've actually tried replicating this issue on another computer (Intel laptop i7 6700HQ) with this same project file, but could not replicate the issue. The problem still persists on the affected computer (Ryzen 3600). I've also tried resetting the config file in the affected computer but the problem still persists. I've sent the project file in question to Noel separately.
  12. I've actually checked this and tested stacking two clips on top of each other in the same take lane. When you do the mutes on the waveform, on playback the clips are actually muted. Even if there is a duplicated clip buried behind the real one, on playback I should hear something, but in this case, I don't and only hear the stacked sound on export.
  13. deleted the post-fader send on the bus but the issue is still there. Bounced to clip works fine, the section is now blank in the track and does not have any audio if were to export that same section out. I also tried moving the audio clip with the muted waveform to a clean, new track and tried bouncing that section out and it worked just fine. However, moving the clip back to the original track resulted in the same issue, seems there is something bugged out with these tracks that seem to ignore the waveform mutes only when exporting the audio out... edit: tried doing the above a few times but on some occasions, the audio is present despite being muted...
  14. Yup its definitely all checked, here's the screenshot from the video
  15. I'm back again with another bug/issue I found. I'm editing a podcast and I've noticed that there are sections of audio which are muted but are still being played back on export. On playback in the DAW, it sounds fine with the muted waveforms being actually muted, its only when its exported when the mutes no longer take effect. The below video demonstrates this clearly, and I've also attached the project file incase its of any use. Edit (28 Aug): the project file has been sent to the Cakewalk team and they were able to reproduce the bug on their end albeit being intermittent. podcast issue.cwp
  • Create New...