Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral
  1. I reported the (admittedly minor) issues with the mixdown function - many thanks for looking at these. Two things to report back from my testing so far: - good news: the output location is now saved with the project and not replaced by the default folder each time the project is re-opened - not-so-good news: running a mixdown from a newly-opened project and not changing any settings still results in the project being flagged as 'dirty'. No changes are listed in history, but any time a mixdown is run the program seems to think it's necessary to save the project once more. Richard
  2. 500, 750, 1000ms makes absolutely no difference. Many times when I start a piece, it just picks any one of the drum patterns from somewhere in the song and starts playing it. Honestly, I really appreciate what BandLab has done by picking up the software and continuing to develop it, but I seem to be experiencing many more random problems now than I can recall in the last several years. Richard
  3. Thanks CJ and Bob... and many apologies for not getting back sooner. I have reply alerts turned on, but apparently didn't receive any. Yes - the buffer was set to 250, so I'll try it at 500 and see what happens. Richard
  4. Hi all. Having a problem with tracks using step sequencer clips. When I start playback, sometimes it plays correctly, but other times it starts playing some other step sequencer clip from a different part of the song. It even does that whether or not the instrument supposed to be playing. And sometimes it starts playing the correct clip and then stops, even thought the clip extends much further. The workaround is to stop and restart the song - not the end of the world, but can be quite frustrating at times. I can't find any references to this in here or the web generally - has anybody else ever come across this behaviour? Thanks
  • Create New...