Jump to content

Lewis Dixon

  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

Recent Profile Visitors

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

  1. i actually did, and it fixed it. No idea why a metronome count in causes this, i would still say this is a bug, since i now know when it occurs, and i cant see any logical reason for it occurring. This is a pain now, so i have to faff about without countins now for recording, though, its less of a pain than out of time automation.
  2. I can only assume this is a bug, as ive tested it in every way possible, an no-one else seems to have a solution. Automation lanes sending MIDI CC to external gear are delayed ONLY when recording a sequence to an audio track. So, for example, I have a midi sequence sequencing a MODX, in addition to this, I have an automation lane controlling filter cutoff. If I monitor the audio track the MODX outputs to and hit play, everything is in time, the filter opens when i want it to, HOWEVER, if I then proceed to arm the audio track to record, then hit 'R' to start playback recording, the automation is late, delayed by about 1 or 2 bars (at 128 bpm). I have also included an image for reference to explain what I mean: using the image as reference, the red lane is the filter cutoff for the midi sequence (green notes). If the audio track for the external synth is monitored, and simply 'play' in cakewalk is hit, the gear is sequenced perfectly, that curve is at that exact point, HOWEVER, should the audio track then be armed for recording, and recording started using the midi sequence, the automation is sent late, approximately where I have marked. Ill include an example of the 'late' automation: late_automation.mp3 Combined with this image, you should be able to hear the difference between when the automation is sending, and when it should actually be sent. the filter should open up BEFORE the lead starts playing, as sequenced (and which it does do if you simply hit play and monitor the audio), however, it doesn't, as can be heard, it opens AFTER the lead starts, which is later than it is sequenced. This ONLY happens when recording the audio from the external synth when sequencing it from cakewalk. I have checked everything, timing offsets, buffer sizes, nothing is wrong, I even looked at the midi events cakewalk is sending, and the times for the start and end of curves etc... for envelopes are sent at exactly the right time (though, I was using the cakewalk event viewer). This is also not exclusive to just my MODX, every synth I have ever sequenced with cakewalk has experienced this. I have tried multiple different audio drivers, including those for the interface in the MODX, with no change. EDIT: So after some digging around, it turns out this happens ONLY when a count in for recording is set, this suggests to me its unintentional, and certainly a bug, but should also be a quick and easy fix.
  3. yep, not correct, everything is programmed on the piano roll in cakewalk, including midi CC perameters, along with notes, this is being sent to the synth, to record, ill arm the audio track for recording, make sure the midi track is sending to the synth then hit record, saves me having to potentially make mistakes playing the synth live recording. the notes are sent and recorded fine, but the CC is sent late, and in the recorded audio is late, this is not the case if i just hit play in cakewalk (still sending midi from the midi track to the synth though, just this time its realtime audio rather than recording it)
  4. Been having this problem for a while now, and it's a massive pain. I can send midi notes to external gear with no problem, but when I try to send midi CC (using the CC control lanes in a track) it's delayed but 1 - 2 seconds. This ONLY occurs while recording the synth, NOT when I hit play, so for example, I have a piano roll with a sequence, and with that MIDI CC controlling the filter, setting the audio track to record, and hitting record will record notes as programmed, but the MIDI CC is later than programmed. This does not happen with soft synths, and neither does it happen if I just hit play in cakewalk and have the audio live, it ONLY affects external gear MIDI CC, and ONLY recorded audio. It's impossible right now for me to record any audio in where I need to modify synth parameters in real-time while recording .
  5. So, seems cakewalk somehow messed up my ACT settings, decided that the argon8 should be the output device, removing it fixed most issues.
  6. definately nothing to do with the controller, i just unplugged it, and its still happening, when i open projects, start new projects, switch tracks a note on signal is triggered, and when i hit play, what ive mentioned above happens.
  7. how can it possibly be the controller, if ive got it disabled. and the note on messages arent anything to do with the modwheel.
  8. so, this has been happening a while but has got significantly worse lately. cakewalk seems to be sending completely random midi CC and note data when i hit play/stop, switch tracks, enter and exit the preferences, basically when i do pretty much anything. Iv'e checked my midi inputs, none of them are sending anything (in fact, i disabled all of them and it still happened). iv'e run midiox and it doesn't show anything, so i'm totally lost as to whats going on. my only potential idea is that iv'e got my keylab mk2 set up as an ACT controller, and potentially that's causing an issue, but it used to work perfectly. i checked the midi monitor on my argon8, and when i hit play in a completely empty project with no midi inputs or midi tracks, this is the result (2 videos, i hit play then stop in both of them, turn your volume down): https://photos.app.goo.gl/Q6d7ceZnHFdpUMWB8
  9. Got no idea whats going on, I have multiple automation lanes on multiple tracks and its only 2 lanes that have an issue, both are controlling the dry/wet mix on reverb 2 cakewalk. When I export the mix, the automation for these lanes occurs later than its programmed to, then after a while, snaps back to what is supposed to be, not following the automation curve at all. However, the automation behaves absolutely fine when the track is played in cakewalk before export. the automation in the image is used to build up reverb before a drop, however, the reverb builds up approximately 4 bars later than displayed then approximately 4 bars later (so, in the middle of the section after) it snaps back to the level set. I've tried restarting cakewalk, removing muted recordings on the track, removing missing automation sections, checked everything to do with the export, and i cant fix it. interestingly, should I export just the section after the automation (the 8 bars at the end in the image) the automation behaves fine, if i export the loop, the automation is late, but only by a bar or so, the more before this i export, the larger the offset.
  10. Managed to get latency down to 8.7ms now, might be able to get it a bit lower, need to fiddle around a bit more
  11. So, i fixed it, it was due to audio latency, seems the realtek asio driver isnt around anymore, but i'll keep looking for it, managed to get my full sample delay to 10.9ms (480 samples) trying to decrease it more is causing the audio to pop and crackle, but it has effectively fixed the timing issue! maybe i should invest in a better interface...
  12. So, did a bit of checking... I feel like an idiot... Turns out I don't have any asio drivers installed, I've been using WDM, and somehow not noticing a delay, I guess there is one... Maybe I've got into a habit of playing early, i don't know, but I'll install the realtek asio drivers, set voicemeeter to use that as its output and see if that helps. Voicemeeter seems to act like asio, but isn't truly an asio driver, guess that's where I'm going wrong, I'll fiddle around with stuff and report back.
  13. Makes sense, however, I feel like I'd notice the latency when playing live? There isn't any, as soon as I hit a key on the keylab (or the XD) there is sound, I'm not directly monitoring the XD, I'm inputting the audio into an audio track in cakewalk then monitoring that. Unfortunately, the interface I've got doesn't have any drivers itself, on behringers site they say use asio4all (which I didn't like). My other option is to try the realtek asio drivers for my audio chipset. Buying a different interface is out of the question currently, I could try fiddling around with buffer settings in voicemeeter to decrease latency. Still think there's some midi latency issue here, because I would expect exact symptoms playing live, which doesn't occur.
  14. i'm using an ASIO driver otherwise there is loads of audio latency, voicemeeter, the total latency is 1536 samples, output is 1024, input is 512. but if this was actually a problem, wouldn't it be obvious when i play live, and when i use soft synths. the fact that its only an issue for sending a midi sequence to the minilogue from the piano roll implies otherwise. i'm using the metronome built in to cakewalk, my audio interface is an el cheapo behringer UCA222, so I can't do midi with it (not that i need to), but as iv'e said, there's no latency issues playing live. There are no FX plugins in the project other than some sidechaining on the audio track and transpose on the midi track for live midi through, these are not causing problems since with them off it still persists. as for latency in the midi input, the latency only exists when recording midi, hence the timing offset iv'e got set, not when live playing an instrument using midi in (or through). i'm pretty sure the root cause has nothing to do with timing offset as iv'e already tried changing it to 0 already, which made the problem worse, as i said earlier, changing it to 100ms basically fixes the issue, but breaks soft synths. also, i'll attach the cwp file in a second post, theres not much in it, just a midi track and a drum track (using sitala and some samples, which obviously wont work on another system)
  15. iv'e got a 40ms offset for the midi sync, because if i set it any lower (though, i think i need to set it a bit lower...) notes i play are placed on the piano roll after they should be, i set this when i was working with soft synths, like i said, if i set the offset to 100ms, notes sequenced are on at the correct time. anyway, as promised, 2 badly recorded samples of the issue to try to demonstrate it, sample 1 is just me playing in time to the drum beat, sample 2 is the exact same thing i was playing, but programmed into the piano roll in the same midi track, note how the synth is note on late in the second sample, strangely though, if i record the audio out from the XD using the programmed sequence, its perfectly in time to how i would play it, so it seems the only delay occurs when sequencing the XD live (not recording the audio). sample 1: https://drive.google.com/open?id=121CI8JDDuVbN5W7uN-U-whKcf4qUhnkd sample 2: https://drive.google.com/open?id=121FDZB3JLnxBuXEk5ted-Muvk3mxUwi4 hope the samples help identify the issue --edit-- did a bit more fiddling around, turns out when playing a piano roll sequence, the midi notes are 1/32 off from when they should be, so i can *fix* the issue by moving all the notes 1/32 forward, but its not really a fix, and the first note is still too late, but of course, when i actually record the audio from the XD for this sequence, its 1/32 ahead of when it should be.... aaaaaaaaaaarghhhhh
  • Create New...