Jump to content


  • Posts

  • Joined

  • Last visited


17 Good

Recent Profile Visitors

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

  1. I just make sure those two busses are always last. Then they never really interfere.
  2. Thanks Noel. The aud.ini entry is set to 1. Importing and recomputing works fine. The time I saw it only doing one waveform at a time, I had just used AudioSnap to time correct about 8 tracks of drums. After Bouncing to Clips, the resulting waveform redraw happened one track at a time. I'll try and see if I can reproduce it.
  3. I'm not sure if this is particular this version or not... but I just noticed that Cakewalk is only computing waveforms for one clip at a time. It used to be that, if you had the multiprocessing engine enabled, it would compute waveforms for as many clips at once as you had cores. No longer seeing this... so waveform drawing takes a lot longer than it used to.
  4. Offset mode should handle this. Press "O" on your keyboard, and now you have a separate control that is not tied to the envelope.
  5. I haven't found a way to reproduce this consistently... but after installing the EA build today (was on the latest release build before that), I have had three crashes to desktop during playback. Two times just pressing play, and once a crash just in the middle of playback... with Cakewalk just disappearing.
  6. Just installed the EA build and it appears to be fixed. Thanks!
  7. Try this: 1) Open Cakewalk and start a new project 2) Insert two MIDI tracks 3) Record some MIDI notes onto the first track 4) Double click on the resulting clip to open Piano Roll View 5) Draw a box around some (not all) of the notes to select them 6) In the Track View, drag the selection down to the second track I get a crash to desktop every time. If I select all of the notes... no crash.
  8. Try choosing "forgot password" and reset it. No problems logging in here.
  9. An Aux Track is really just a bus that sits in the tracks pane. In a perfect world, they would simply load as busses when opened in older versions... but I doubt that happens.
  10. This is good stuff... but a bit unnerving that almost every tempo change does not occur right on a beat.
  11. It's not complicated at all. One pass and you are done. I guess I could see it not going so smoothly for those who have no MIDI input device. You mentioned lag. What is your ASIO latency in Preferences? Did you try using a smaller buffer size?
  12. I don't think he is looking to alter the audio at all. Looks more like he wants to create a tempo map that matches the existing audio. "Fit Improvisation" in the Process menu is what you'd want if that is your goal. Create a MIDI track, use a MIDI controller to tap out the tempo as you listen to the audio. Then use "Fit Improvisation" and the Tempo Map will be created matching your input. *Way* easier than doing it all by hand.
  13. Ah... thanks. That makes sense. I did try moving the patch change to a later time (1:01:003), but it still does this in that case. Wouldn't that be a situation where the .mid file is no longer consistent with the .cwp file? The patch change would not be sent at the same time in both files... and I would want it sent at the specific time I set it to.
  14. I'm noticing this consistent behavior today. I have multiple projects that have a MIDI track setup with patch changes only. If I export this track to a Standard MIDI file (or drag the clip onto the desktop), the first patch change is not included. If I duplicate the first patch change first (so that there are two of the same patch changes at the exact same time), the export includes only one of them (this is my sort-of workaround for the moment). I've attached the .cwp file as well as the .mid file that is generated by an export. OFAWtest.cwp OFAWtest.mid
  15. Update on this... I contacted AMD support and they have been of little help. I've received two responses from them which suggest they aren't really reading what I've written them - directing me to use manufacturer supplied drivers when I've been very clear (twice) that I have been, and that the issue is the same using drivers from both ASUS and AMD. ASUS, on the other hand, has been more responsive. They've requested a video showing the problem. Thought I'd post it here as well so you guys can see what is happening:
  • Create New...