Jump to content

Noel Borthwick

Staff
  • Posts

    4,195
  • Joined

  • Last visited

  • Days Won

    46

Everything posted by Noel Borthwick

  1. @pax-eterna thanks for your report. We were able to repro it and I have a fix. The problem only occured when "Allow Only One Open Project" was enabled which is why it wasn't spotted. We'll send out a build with this soon for you to try out.
  2. If you tried it in prior releases you will see whats new lol Drag and drop to lanes and tracks previously tried to match up to previous take lanes which resulted in potential overwriting of take data. Also dragging to the last lane would never add new lanes - rather it would round robin and overwrite earlier takes. In short it was not usable. As far as dragging takes to new tracks it would not create new lanes properly and would not retain the order of the lanes you dragged. Drag and drop and copy paste of lanes across projects was also not supported properly. The bulk of the work was ensuring all these operations are "lane aware"
  3. @Walter Treppler and @btbrock I understand where you are coming from. We thought a lot about this change because we understand that muscle memory can be hard to relearn. However one of the basic workflow's during playback is seeking visually to time positions and previously it required shifting your focus away from where you are looking at the clip to set the time. i.e. imagine you are trying to playback and jump to a peak in the waveform to audition from that point, you now have to travel all the way to the time ruler to set the time which can also be distracting. We have made a small change to help accomodate your workflow better. CTRL clicking will no longer set the time so you can ctrl click in white space and it will clear the selection. Alternatively you can do what btrock suggested and right click lasso whitespace to clear. If you still hate it after trying it out let us know.
  4. Hi @btbrock we added the ability to click to change the position during playback since that is the most intuitive and fast gesture to quickly change playback position rather than requiring the user to click on the timeline. Most other programs also do this. May I ask why deselecting during playback is more important than this in your workflow? Also you can deselect using the select NONE command or any keybinding for it. Currently you can press CTRL Shift A to deselect or press the numpad 5 key (with num lock off) to deselect all. There is no preference for this behavior...
  5. Do any of you with the issue have any control surfaces set up? If so does disabling it resolve it for you?
  6. @Promidi please check your PMs. We'd like to follow up with you.
  7. @Promidithe project file you sent loads fine for me - without all your plugins. Can you please send a Minidump so we can investigate the source of the crash?
  8. Thanks for your feedback. Some comments: As far as it appearing in real time it would be nice but not very efficient on a large project with hundreds of tracks and clips. Since the selection state has to be updated while you are dragging to add all those objects it would make selection very sluggish. Regarding snapping that is already possible. If you set the snap settings in the snap module as you want the selection will snap to that. Also make sure you turn on aim assist to show the edge of the selection. - The "Select From", "Select Thru" and "Select Lenght" times change IN REAL TIME as we drag the selection markers. Yes this will be helpful. We'll consider it in a future update.
  9. @Lemar Sain can you upload and send me a link to a crash dump for this? Also if you can include the project file with instructions to repro it will be useful.
  10. We have made some UI optimizations after EA 2 that might help a bit. However I haven't seen anything slower with closing projects.
  11. I have seen crashes with Ozone in the past - the crash dialog above shows that Ozone itself is crashing not CbB. So you can submit that error to iZotope. Please upload and send me a link to the dump file as well so we can check it out. More info on this here.
  12. We can give you a bigger file if you prefer - we'll just pad it with silence 🤣
  13. We were able to troubleshoot this and found that it is a bug in BIAS's use of the Chromium embedded framework. The plugin is launching several CEF (chrome embedded framework) web view processes when you create the plugin. These processes can be seen in task manager as CefSubprocess.exe instances. Apparently these CEF processes are hijacking wave files created when recording and changing the sharing permissions of them such that CbB cannot access our own recorded files! This is why recording fails. In fact even Windows explorer cannot access the files and you get this error if you try and copy and paste the recorded file to a different folder. A fix for this will have to come from BIAS. We will forward this information to them as well.
  14. @Sarah Rosen can you please share the project that exhibits the issue with us? You can "save as" a minimal version of the project to a new folder and zip it and send us a link.
  15. @msmcleod I think he's still using 05. How are you moving the tracks? Copy paste or drag move / drag copy? There are also lots of improvements for automation copy paste in the upcoming 07 release
  16. I replied in your other thread... I think you were asking about sound on sound recording. Takes are only committed on stopping record so you may not be able to hear the prior loop passes until you stop. I understand what you want though...
  17. Maybe we should allow ripple edit to be a one shot action
  18. I think you were asking about sound on sound recording. Takes are only committed on stopping record so you may not be able to hear the prior loop passes until you stop. I understand what you want though...
  19. Hmm next time your see it please save a dump from task manager so we can see the context. That error typically doesn't come from our code directly but from some UI component in mfc so hard to say what caused it
  20. Pretty sure this should be good now. there were a few cases of edit issues with clip envelopes that we fixed. Please check out our and let us know if you still see issues.
  21. I think you misunderstood. An early access build is no different from a normal release other than the fact that it isn't pushed to the entire world via BandLab assistant. Subsequent updates will work as normal as if you had a prior release.
  22. With this release we focused on allowing lanes to be used as an arrangement tool in addition to comping. Ideally I think the feature could be called something like "track lanes" as opposed to take lanes now, since its not restricted to the recording workflow. You are free to use lanes as a scratchpad for different variations of track ideas whether they come from actual recorded takes or from other sources (clips in project, imported files etc). With the enhanced drag and drop and copy paste functionality all operations are now fully integrated with lanes so should work seamlessly. When dragging in other data you can choose to disable the comping features and arrange the clips in any manner before you decide to start the comping process. You can also choose to layer and have audio clips in lanes sound simultaneously if that's what you want in this workflow. In fact for those who used the old pre-X series layers, you should now be able to do all of that and more by using the tools appropriately. There are also big improvements to automation lanes and clip envelopes when doing copy paste between tracks or lanes that should make editing with automation lanes a smoother experience. Additionally thanks to a report from one of our users, we fixed a longstanding issue with recording in take lanes that would end up with incorrectly cropped clips in lower lanes. Overall we hope you will find arrangement and comping in tracks to be a much more enjoyable and intuitive experience in this update. Let us know if you see any issues.
  23. Thanks Mark that really looks like there is some bad state management in the driver itself. When you stop and start the transport cbb goes through and starts and stops the driver. I've seen cases in the past where some drivers don't properly handle fast transitions and are likely failing one of the state transitions. I'll see if I can repro it with your recipe with the 6i6
  24. @Keni there is no need to roll back to install the early access since it updates the 05 release directly. The only mention of rollback was to inform people if they wanted to go back to 05 afterwards for some reason. Going to the final release from early access should be seamless. The only small downside is it will auto download the full installer. This is very stable at this point so it should be very unlikely.
×
×
  • Create New...