We figured out an issue with magnet regions. Sometime the transition between two magnet regions playing twice an we don’t under stand why. We have thought maybe it’s a scattered instrument not finished playing, but set them to cut doesn’t change anything. It’s reproduce able but random.
I’m afraid we’ll need more information to diagnose this issue. What’re the trigger conditions of the magnet region pairs this happens with? Are you able to upload a copy of your project for us to examine in detail?
Thank you very much for the fast response. Can I have an Email to send you the download link for the project. It’s not possible to do this public.
It’s uploaded. Thanks for the help.
Thanks for uploading your project! Seeing it helped us work out what was happening.
There’s a simple solution that will allow you to get the behavior you want: For each of your magnet regions with a transition timeline, add a loop region to the event, set that loop region to the same length and position as the magnet region, and set its priority (i.e.: its vertical position) to be between that of the transition marker and magnet region. This will ensure that a magnet region’s transition timeline will only play once when you transition to that magnet region.
As for why this is happening, and why the solution I gave above works:
- Your magnet regions are quantized to the bar. This means that transitions from one magnet region to another can only start at precise 1-bar intervals.
- Your magnet regions’ transition timelines are exactly one bar long. This means that a transition via one of those transition timelines takes one bar to complete.
- Your magnet regions use the “relative” offset mode. This means that when you transition from one magnet region to another, the position at which the playback position arrives is offset from the start of the destination magnet region by the same amount it was from the start of the source magnet region.
- Your magnet regions’ transition timelines feature destination regions the same length as the transition timeline, i.e.: one bar. This means that the transition timeline begins playing content from the destination on the main timeline one bar before the playback position actually reemerges onto the main timeline, and that the playback position will reemerge onto the main timeline one bar to the right of the position it starts playing destination content from.
- Putting 3 and 4 together, when you transition from one magnet region to another, the position at which the playback position re-emerges onto the main timeline is offset from the start of the destination magnet region by the same amount it was from the start of the source magnet region, plus one bar.
- Because of 5, when a transition to a magnet region with a transition timeline is triggered exactly one bar before the end of the source magnet region, the timeline playback position will reemerge onto the main timeline at the exact end of the destination magnet region. This happens fairly often, because of 1.
- When inside a transition timeline, makers other than loop regions without transition timelines are ignored.
- When the situation described in 6 occurs, the transition marker arrives at the end of the destination magnet region, and because of 7, ignores the transition marker and magnet region end point at that position. Instead, the playback position moves beyond the end of the magnet region, and (as that magnet region’s trigger conditions are still met) is captured by the magnet region and starts going through its transition timeline. Since it just came out of that same transition timeline, this means it goes through the transition timeline twice in a row.
- Because (as per 7) loop regions without transition timelines are followed when inside a transition timeline, placing a loop region over the magnet region means that when the situation described in 6 occurs, the playback position will loop around to the beginning of the magnet region instead of going off the end of the magnet region and entering its transition timeline a second time.
And there you have it. Every component of the event is working as designed, but the specific combination can be a little surprising if you don’t realise why it’s happening.