CbB and Ozone 11 - Stuck Instrument When Using Mastering Assistant

[Stephen Power]

Excuse the clunky jargon please...I'm trying to master a project in CbB, with Ozone 11 Standard. I've used Ozone 9 in the same project with no issues.

But, now I'm getting one or two tracks that continue playing when Ozone 11 (in Mastering Assistant) has completed the assessment. I've tried checking and unchecking 'Zero Controllers When Play Stops' in MIDI preferences - and that has worked with stuck instruments in the past, but not this time.

Does anyone know what might be the problem? Thanks for any suggestions.

[Amberwolf]

Which instruments?   Some plugin coders did/do things in ways that don't respond to the normal method of turning off notes. by sending a note-off, or an all-notes-off command. 

There are some that ignore those, and instead only respond to a note-on with a velocity of zero, so to turn them off you (or the host software) has to send one of those for every possible note.

My ancient version of SONAR can't do that, but CbB should be able to; there is probably a setting in there for the Panic Button to do this.  

 

There are also some plugins that "break" (all the RGC plugins I've got, like Z3TA / 2, etc) and get stuck notes all the time; in the ones with an arp I can toggle the arp off (or on) momentarily to stop it until the next time).  I suspect but can't test that the second method above would also turn them off--but it is annoying that they don't just respond normally to note-off messages like they should.     

 

Since the problem only happens with the new version of Ozone, you should contact Izotope to let them know about it, since something they changed is causing it, and it might be a bug they can fix. 

 

Edited November 16 by Amberwolf

[Stephen Power]

15 hours ago, Amberwolf said:

Which instruments?   Some plugin coders did/do things in ways that don't respond to the normal method of turning off notes. by sending a note-off, or an all-notes-off command. 

There are some that ignore those, and instead only respond to a note-on with a velocity of zero, so to turn them off you (or the host software) has to send one of those for every possible note.

My ancient version of SONAR can't do that, but CbB should be able to; there is probably a setting in there for the Panic Button to do this.  

 

There are also some plugins that "break" (all the RGC plugins I've got, like Z3TA / 2, etc) and get stuck notes all the time; in the ones with an arp I can toggle the arp off (or on) momentarily to stop it until the next time).  I suspect but can't test that the second method above would also turn them off--but it is annoying that they don't just respond normally to note-off messages like they should.     

 

Since the problem only happens with the new version of Ozone, you should contact Izotope to let them know about it, since something they changed is causing it, and it might be a bug they can fix. 

 

Thanks for your detailed reply. The main culprit, so far, seems to me the Harmon Trumpet in Lea Bertucci's Acoustic Shadows from Spitfire Audio, but I haven't tried others. There are about 20 tracks in the project I'm working on, and no other instruments get stuck, but some do seem to hold their echo longer than before I mastered the project.

If I've understood you correctly, maybe putting in a zero velocity note at the end of the trumpets might work? I'll try it.

[Amberwolf]

Assuming your plugin responds to zero velocity notes, and assuming you can create a zero velocity note in the host, you'll need one for every note that has been played that might get stuck, at the point the stuck notes should have ended normally.