Noel Borthwick

Ah I see - I missspoke. What its doing is when lanes are open it treats a browser double click the same as a drag and drop to the master track for the lane. This results in the drop occuring to the FIRST lane not the current lane. I suppose we can consider trying to special case the browser and make it always append lanes if you double click.

I wouldnt worry too much about that toast. All it means is that the system was busy enough that the time to process a single audio buffer exceeded the threshold and caused the engine to stop. The reason it drops out even when not playing is likely because you have synths in your projects or you have "always stream audio through FX" enabled. So its telling you that realtime playback has been stopped. I'm sure there is room for improvement, but it can happen with some more intensive edit operations.

@winkpainThe file menu issue will be fixed. The other behavior of double clicking files in browser when lanes are open is that it will insert to the active lane. I think that is expected today. Its also how it works with tracks - it will insert into the current track. When lanes are closed there is no active lane so it appends...

I can decipher it if you send me the dump file.

Haha no that's fine I just don't receive those directly so asked you to PM me to expedite it. Thanks to the help of @spiffo and @M.O.S.T. Music I got dump files and finally now have a project file that can reproduce a crash with sidechaining. We should be able to address this once I figure out whats going on.

Who did you send it to? Can you forward the project file and minidump to me? PM me.

I was able to reproduce it in the NFR they sent us so it happens in the latest plugin I had in July. I'm not sure if its fixed since then. Both @Jonathan Sasor and I were able to reproduce it.

I was referring to double clicking in the clips view within the lane to select it. I was able to repro your issue. We didn't test importing from the file menu so missed that case. It will be fixed in the next update.

Esc is used for other operations as well such as cancelling a mixdown, so it may be unexpected to make it cancel a selection...

Seems pretty unlikely that this would be related to the driver unless some dependency for that plugin got removed somehow. Does the plugin itself scan ok? What if you switch to the onboard audio device (WASAPI) and try loading the plugin - does it work?

@Christian Jones I think there may be a disconnect. Can you please notify the rep you are speaking to that I sent them very detailed technical information about this problem with BIAS FX 2. Yes it also happens in the new version. The information was sent on July 24 to Joe Kuo from support there and he acknowledged receipt and said it would be forwarded to their engineers.

Reminder - last few days to apply for the Cakewalk and Synchro Arts competition! Winner will be announced around Sep 1.

@RobertWS make sure that num lock is OFF before doing that. Its the "gray" num-5 key that unselects. I use it all the time.

Dragging from the browser respects the drop location and will insert clips contiguously on lanes. If you drop on a lane that has data it will autocrop it like this. If you drag to to the main comp track it will drop starting from the first lane and crop any data that lives there. This is by design. If you want to insert new lanes just drop to the last lane or insert a new lane and drop there. EXAMPLE: Dragging MIDI and audio clips from Browser to add take lanes EDIT: I see you mentioned the import audio menu. Make sure that the target lane you want to import to is selected by double clicking the lane. I'll check if the import audio menu respects the selected lane position.

Thanks! Please also send the minidump for the crash.

Do you still have the project that crashes? If so please send it to me.

Yes you can turn off the click behavior not the selection handles. See the feature overview topic. Regarding unselecting there are hotkeys to do that. Num-5 or CTRL-Shift-A will deselect.

@Cosmo Kramer which behavior are you referring to? If its the click to set now time that is already configurable..

It is indeed a melodyne issue and happens in all ara2 hosts. I reported this while we were working on ara2. I imagine celemony will fix it in a subsequent melodyne update. It's just a minor ui issue since closing and opening the view fixes it. Feel free to report it directly to celemony as well.

Lol I just ran into this Ironic that I come to our forum to find the solution.

Hi @Peter - IK Multimedia we've received a few crash dump files from users that confirm that the crash site is within the Modo Drum plugin. If you don't have a dump file contact me and I can send it to your developers. The problem also occurs in all prior versions of SONAR and is not specific to CbB.

Revoice Pro and VocALign now support ARA 2 and work seamlessly in CbB through our partnership with Synchro Arts. To celebrate their latest update, together with Synchro Arts we’re giving Cakewalk by BandLab users the opportunity to win Revoice Pro and VocALign Project! These powerful industry standard tools for vocal production now work even better in CbB as a result of our ARA 2 integration.

Revoice Pro and VocALign now support ARA 2 and work seamlessly in CbB through our partnership with Synchro Arts. To celebrate their latest update, together with Synchro Arts we’re giving Cakewalk by BandLab users the opportunity to win Revoice Pro and VocALign Project! These powerful industry standard tools for vocal production now work even better in CbB as a result of our ARA 2 integration.

Perhaps the behavior of prefader sends being fully independent is too advanced for be a default behavior? The problem is if we change it some projects may sound different and unexpected for someone who actually has set up for headphone mixes. We could try and expose UI to select the pre fader send behavior...

Thanks for the video @Gswitz The behaviour you demonstrate is expected. At 3:25 in the video the main reason why the export doesn't include the doubled reverb from the pre fader send is because you SELECTED track 2. When you do that the bounce is omitting track 1 completely from the mix as if it didn't exist. (Behind the scenes bounce actually makes a copy of just the elements of the project that are selected) If you did the export with all tracks selected you would get identical behavior to playback. The reasoning behind prefader sends working independently even when a track is muted (in this case as a result of another track being soloed) is rooted in use cases such as setting up headphone mixes. Suppose the engineer has set up prefader sends for headphone mixes to the musicians. i.e. In this scenario you don't want the act of soloing or muting another track in the control room to cut out the sound from the headphones. IOW the engineers mix needs to be independent from the cue mix. The ability to select elements for export is powerful but can be confusing if you don't follow the underlying routing.