Jump to content

Matthew Carr

  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

Recent Profile Visitors

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

  1. Cheers All - to give an update I updated my live rig to CbB Version 2020.09, and haven't had the crash relating to Raum / Phasis etc In no rush to update the OS on my live rig to check further, but think that proves it's not an issue with build 2020.09
  2. As far as I'm concerned recent Dell laptops are a complete non-starter for audio work - especially live use. Just google 'Dell ACPI.SYS latency issues' and it'll become apparent you're better off going with another brand .It's endemic across all their models - even the XPS series, which is often touted for audio work
  3. Anyone else seeing this - I can't track down what the problem is. I think it maybe something to do with the latest version of bandlab / windows When adding Native Instruments effects (Raum, Phasis, Replica etc) to the FX bin, or attempting to edit them in an existing project, I get a complete crash However, it's not consistent: - I I do the same in an new empty project, then it seems I can add the effects to the bin / open the FX UI, no problem. - When I load an existing project, then opening the UI for the effect, sometimes it crashes, sometimes it doesn't Have tried re-installing the effects from Native Access, but no change. I have one particular project where the crash seems to happen pretty consistently. I copied this project onto my live rig (exact same hardware, but different builds), and haven't been able to get a single crash: Studio Machine (Crashing): Windows 10 Pro version 2004, build 19041.508; CbB Version 2020.09, Build 006, 64 Bit Live Rig (No Crash): Windows 10 Pro version 1909, build 18363.836; CbB Version 2020.04, Build 179, 64 Bit Which makes me think it's something to do with updates to windows or CbB? I need to bring my live rig up to date, but want to try and iron this out first - Is there a way of installing an older build of Bandlab on my machine that crashes? Thanks for any advice in advance, Matt
  4. Hi Jim, In my mind it would just be another option in the FX Bin context menu (of a Simple Instrument Track) shown below - "Insert Midi Plugin" i.e. the same as the option available in the FX Bin context menu for a midi track I use Midi FX a lot to condition data from external controllers; mainly the Event Filter, Transpose and Velocity plugins. Cheers, Matt
  5. Hi, Would be great if we could add Midi FX directly to the FX Bin of a simple instrument track. At the moment you have to either: a) Break the track into a midi track and an instrument track in order to add the Midi FX to the separate midi track. This seems unnecessarily complex b) Use the track inspector, switch to the midi tab, where you can then add the Midi FX for the simple instrument - but then the midi FX is kinda hidden. If it showed in the track FX bin, it would be more obvious, esp. when there are lots of simple instrument tracks. Instead, if the drop down on a simple instrument track FX Bin allowed selection of Midi FX, any midi effects would be obvious by looking at the track FX Bin, without having to split the instrument track and add complexity to the project. Behind the scenes I guess this would be the same as option b) above. Cheers, Matt
  6. Been seeing this issue few times in the arranger view: 1. Renaming a section (from within the arranger sections tab, or from the section along the top of the prv) can cause the program to lock. After typing the new name you can't submit the new section name by pressing enter - it's ignored, but then you can't move the focus to elsewhere in the program as the area to enter the new name is modal. Only way out is to force close the app Issue seems intermittent - some times it works ok, sometimes not. Version 2020.09 (Build 006, 64 Bit) Windows 10 Intel i7, 12 Mb Ram
  7. Personally I'd like to see the Staff view get some attention - it doesn't need to be a complete notation package, but just given some love so it works better. Perhaps even take Don Williams up on his offer to update the staff view based on overture. IMO Providing usable notation within a free DAW seems like a great idea for the educational market, and could be a fantastic way to add new users into the userbase
  8. Same here, think I mis-understood about the unlock code given before CbB came into existence - it wasn't forTH3 Full, but a code that allowed the bundled version to be run outside of Sonar - you had to pay more to get an upgrade to TH3 Full. Hence the current upgrade to THU is still expensive, as it's not an upgrade from TH3 Full. Thanks for the link Scook - made it all clear. Hmm.. I just contacted Overloud with my serial, and they gave me a voucher for 20% off TH3, meaning it would still be 183.04 GBP. @tonemangler - did you manage to get an upgrade to TH3 Full?
  9. Hmm.. I just contacted Overloud with my serial, and they gave me a voucher for 20% off TH3, meaning it would still be 183.04 GBP. @tonemangler - did you manage to get an upgrade to TH3 Full?
  10. I connect to a rack mount pc via remote desktop, and have the same issue - there are workarounds, but would be nice to see a fix
  11. Hi, Wonder if anyone can shed any light on this, I have a strange re-producible issue, but you'll need the Waves Tune Real-Time plugin. Create new project from the basic template 'Basic.CWT' Add Waves Tune Real-Time Mono in the FX Bin of the audio track Insert Rapture Soft Synth as a simple instrument track (not Rapture Session) Cakewalk crashes, UI of Rapture is white Only way out is to kill Cakewalk via task manager Rapture can be inserted without issue , if I: Don't add the waves auto tune audio fx Add the waves auto tune audio fx, but bypass it (i.e. click the off switch in fx bin, so it's greyed out), before adding Rapture Tried it on 2 systems, with the same results. Haven't used the auto tune plugin before, so maybe I'm missing something that is causing the crash - maybe? Seems like it causes issues with other synths as well if it's enabled in the fx bin (e.g. might cause some kind of audio feedback in the output of Air Xpand2 when selecting some presets), but Rapture seemed like the most clear cut issue. System is core i7, windows 10, CbB and Waves all updated to latest. Thanks in advance for any help, Matt
  12. I've also used a 404HD without issue, and for the money I think it's a great choice - latency is fine, and it's built like a tank with lots of IO I also noticed windows apps might have sound issues if sample rates not aligned between Cakewalk and Windows, so check that first.
  13. Hi HardDrive, Sounds like there's plenty going on in your setup, but my 2 cents on your points would be: 1) Make sure you always plug the same gear into the same USB socket on your PC every time, particularly any controllers and your sound card. The device and the port it's plugged into are used by Windows to identify the device. If devices are plugged into ports different to when the file was last saved, you will get CbB prompting you to assign ins and outs to devices when opening the file (even though they may have the same name in the dialog) 2) Try un-checking the Reset All Controllers to zero at start / stop option - sometimes these messages are interpreted by plugins as a controller change, so the project gets marked as dirty, and it has to be saved before closing. (Would be great if there was a command line switch to open a CbB project in read only mode - I did raise it as a feature request, but no traction so far) 3) No experience - sorry! Cheers, Matt
  14. Will we ever again reach the dizzy heights of 'It all goes crash in the loudspekah'....
  • Create New...