Jump to content

Matthew Carr

Members
  • Content Count

    71
  • Joined

  • Last visited

Community Reputation

25 Excellent

Recent Profile Visitors

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

  1. Anyone use the new export function to export arranger sections? I just tried a large project with around 30 arranger sections and only 20 sections exported - they were all listed as a task, but the process completed without creating all the files (they were all exported as MP3) I then clicked on the arranger section of a missing file, to highlight that section, and then exported to audio using the drop down on top left 'Export' button - the audio of the missing section exported fine, so not really sure why it wasn't included in output from the new dialog. Anyone seen this, or have an idea what could be wrong?
  2. Gigperformer can play back audio, and now midi, but it's easier for me to use CbB as I can align any PC messages and DMX with the backing track easily on the timeline. In Gigperformer, I often select a different rack (collection of VSTs) for a different part of song.. there might be a way, but couldn't see a simple way of keeping the same backing track playing when moving to a different rack. Gigperformer is pretty awesome, and I'd highly recommend it - it is a bit pricey though. If you have Studio One then the Show Page could be worth investigating; it looks interesting, but don't think it's quite there yet feature wise - hopefully they continue to develop it. Sadly I think John is right, Live performance is a very small niche, in a very small market! So although CbB has the potential to be an amazing live performance tool, I doubt it will be developed in that direction - hence always good to hear other peoples solutions!
  3. I use CbB in a live setting, but over time I've moved away from using it for everything. The thing that hindered me most was the midi; inputs and outputs were forever being mapped to the wrong midi port at startup (because I'd move the file between my studio PC and performance PC, where slightly different things were plugged into different USB ports) - and then VSTs would start acting on CC / PC changes from the wrong source. That wouldn't become apparent until you played a song that used the VST, so it made for a nervous live performance. My best investment was Gigperformer, when on sale at Plugin Alliance. It hosts all my VSTs, has a rig manager for different PC setups, and just works. CbB plays back the backing track, shows notation, and sends out MIDI DMX (to QLC) and program changes (to Gigperformer) via loopmidi - virtualising the midi routes helps when moving project to a different PC. I use the arranger view as a setlist - each section in the arranger view is a song, so I can name them and jump around at will, or just play the set end to end. Each of the cover bands I play in has a limited number of songs (30 or so), so I can easily put all potential songs in one project.
  4. Yes, I can see that the automatic recall might be annoying, but at the moment it's hard to see many other reasons for clicking on a task, other than to delete it, rename it, or open the output folder , which could all be handled by the task drop down menu - meaning the default action of clicking on a task line would be a more natural paradigm of form and sub-form. As long there's a prompt to save or cancel any changes (if dirty) before any new task is recalled, then the recall / save could be automatic, and the options removed from the drop down menu. The double click is a handy shortcut, but perhaps not be best UI wise 1. Double clicking the task is a 'magic' action - you wouldn't know to do it unless you've been told 2. If you've double clicked the task, there is nothing to tell you that the dialog is now showing the details of the task that's been double clicked Not trying to rain on the parade - the new export dialog is a massive step forward and I'm stoked! Just from my perspective it could be slightly more consistent with the way other UIs work. Cheers, Matt
  5. Fantastic update, the new export system rocks! Didn't have time to participate in the early access, but one thing that would seem more logical to me is to automatically recall the task settings in the dialog when a task is selected (or have a checkbox somewhere that enables this behaviour), and also a prompt to save changes when selecting a different a task (if the current task is has been changed) The whole recall task settings / update task settings seems a bit cludgy to me - perhaps it'll be refined in a later update? Can appreciate the line would need to be drawn somewhere on this new dialog, as it's already got soo much functionality.
  6. All worked as expected, but no update as already on the latest version . My 2 cents would be: Include the reference guide as an add on Show add-ons that are already installed Show installed add-ons that have an update available (e.g. reference guide would go out of date over time)
  7. In my experience, using a loopback device as the midi input to a track which has input echo on causes no end of problems - there's definitely a bug with the way virtual midi ports are being enumerated. This causes midi inputs to be re-assigned in projects whenever the physical midi devices connected to the system changes (regardless of whether they are selected as midi inputs in the preferences tab) Bit of a long thread due to the examples, but it's conclusive that the bug is specific to virtual midi ports, and not physical midi ports Midi Inputs - Please Help! - Cakewalk by BandLab - Cakewalk Discuss | The Official Cakewalk by BandLab Forum Would be great if there was an easy built in way to send midi to multiple tracks, if just to avoid use of loopback software
  8. That is actually pretty genius scook, thanks for sharing! A really elegant solution
  9. @msmcleodGreat to see some fixes coming in on Midi input problems! If you're looking at the code for this, can you take a look at the bugs I reported when virtual midi devices are being used: Inputs from virtual midi devices are being changed on project open after a new physical midi controller is connected to the PC (even though the new device is not even checked as an input / output in the midi preferences box) 'Manage Presets' for Midi Inputs functionality has erratic behaviour Midi Inputs - Please Help!
  10. Cheers guys, the API looks interesting and started me wondering if I could write a small app to expose the controls I need via OSC (which can be sent from my setlist manager)... but it looks like AZController may have that covered! Will have a dig in over the weekend and see how I get on Thanks again for all your help!
  11. Thanks so much Bassman, that's pretty much exactly what I was looking to do.. and including a preset for AZController is great! Sorry for the late reply, my band performed our first post pandemic gig yesterday - good times! Lots of people commented how good it was to be able to see live music again. I'm wondering how AZController achieves it's integration, it seems to have pretty deep control over Cakewalk, so perhaps there an API available somewhere? My setlist manager has a scripting engine, so it might be possible to do this directly, and avoid another piece of software running on my live rig.
  12. The 'External' input will be from a setlist manager app, so basically I'm looking to send a message from the setlist app to move to a particular Now time in Bandlab. The 'Goto' command will allow me to type a bar number to go to, but I don't want to be typing in bar numbers - the external command needs to specify the bar number to move to. If I can control the Now time via an external controller, as you suggest, then this would be a great starting point - can you give a bit more detail please? Thanks, Matt
  13. Yes, sorry for not being clearer! That is definitely some lateral thinking! I hadn't really thought about using CAL - although the fact it's sort of deprecated and isn't always available to run is a downside Thanks for a great suggestion. It's a shame there isn't some sort of documented API for Cakewalk, or another way though.
  14. Using Arranger View to move sections around deletes the first tempo node in the tempo view
  15. An Unusual request perhaps - does anyone know of a way to send a command from an external device to CBB to move the timeline to a particular position? Similar to a Song Position Pointer MIDI message I guess, but I'm not having any luck in getting CBB to respond to those.. TIA
×
×
  • Create New...