Jump to content

DESIGN FLAW: Joining midi regions that has equal delay compensation will move the actual midi data


snattack
 Share

Recommended Posts

My hands are tied here.

 

So I'm using Vienna Ensemble Pro the way I should: as a multi timbral instrument. This is to save resources since Kontakt takes up a lot. But Logic contains so much problems in this regard that I will open a separate thread about this.

 

Anyhow: Having two midi regions with equal delay compensation joined together should not move the midi data, it should instead transfer the same value to the field in the inspector. Now, when I have two separate delay compensated regions on a track, joining them together moves the notes screwing with the quantize settings. Currently, the only way is to first remove the delay, then join, then re-add the delay again.

 

We're forced to use the region delay because of a bug where delay on aux channels are randomly ignored. So – we can't use multi timbral instruments the way they should because of a bug. And the only workaround creates so much work that it's almost not worth it.

 

System: Macbook Pro 16", 64GB RAM, macOS Catalina 10.15.7.

Software Version: Logic Pro 10.6.2

Link to comment
Share on other sites

You are correct. When working with strings you have to use negative delay to compensate for the slow attack. Each time I copy/paste/merge regions the region delay setting is reseted but the delay ”printed” into the midi notes which is not what I want.
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...