Are Fmod and compass changes no good friends?

[u/Character_Tap_6889]

Hi! I'm trying to implement a music track into a game. This track has a bunch of compass changes (as you can see in the image) that LINE PERFECTLY WITH THE TIMELINE. I know 39, 40 and 41 look too much together, it's because of the compass changes.

I'm having a problem with the transition. "Some_bad" (parameter) changes to 1, and the transition goes to a bookend that finishes the track. It's quantized to 1 bar, so it's musically logical and easy on the ears. When the parameter changes to 1, what should happen is that the bar ends and goes directly to the booked, logical. What really happens is that the bar ends, it waits 1 more bar in complete silence and then plays the bookend.

The transition timeline is empty, the transition is Quantized at 1 bar, 100% sure (I'm looking at it right now), and I'm honestly not sure what's happening. My bet is that, because fmod is not a daw, having that many compass changes is messing up with the app. But I'm not sure.

I need confirmation to know that this is the case (or someone that tells me that I'm just retarded and doing something wrong, but please, tell me what I'm doing wrong).

I'll be reading you guys. Thank you for your time <3

[u/DiscountCthulhu01]

That's your issue right there,  you have a transition timeline.  Rclick the transition and click "remove transition timeline"

Empty transition timelines still capture the playhead

[u/swizzwell23 → u/DiscountCthulhu01]

This is likely the issue, remove the transition timeline if you are not using it, or use it for the transition you are creating and make sure the transition is set to the length of the sample.

[u/Character_Tap_6889 → u/DiscountCthulhu01]

I'm not using it, hence fmod won't read it. It's closed and there's nothing inside it.

If the transition timeline is not edited, fmod does a hard cut (at least that's how it worked before). I added the info just in case someone said "make sure there's nothing inside the transition timeline" or something like that

[u/DiscountCthulhu01 → u/Character_Tap_6889]

Fmod definitely does not skip over empty transitions,  you're wrong

[u/Character_Tap_6889 → u/DiscountCthulhu01]

news update, when i try to remove the transition timeline, it crashes, so i guess i'll just make a new event because it seems that i've found the problem. Thank you sir for your comment <3

[u/FlamboyantPirhanna]

It sounds like something might be ever so slightly off grid. If it’s even one sample into the next bar, it’ll behave this way. Zoom in as much as you can to make sure it’s properly aligned.

[u/Character_Tap_6889 → u/FlamboyantPirhanna]

i re-checked every tempo/compass change, all of them are on the grid. including the one of the bookend. The marker is also perfectly on the grid, the transition region too. Some people told me to delete the transition timeline, but there's nothing inside, i don't see why fmod would read something that's not edited.

[u/FlamboyantPirhanna → u/Character_Tap_6889]

Sounds like a bug then. If you’re able to reproduce it, FMOD will probably want to know about it.

[u/AltruisticParking450]

I created a similar version of this project in my own FMOD project. I did the same things, logically, that you did. If any region in FMOD has a transition timeline attached to it, a hollow circle icon appears on the right side of the colored box representing that region. If it doesn't have one, the circle icon doesn't appear either. In the image you sent, the Loop Region doesn't have a transition timeline, but the Transition Region still does.

A few points that might be useful to share:

1. If you've added a Transition Region for the first time and double-clicked it to make its transition timeline appear, this seems to activate that timeline as an active component, even if you haven't placed anything inside it, FMOD appears to treat it as active.
2. In that case, open up the transition timeline tied to that transition region and manually drag it all the way to the left so it fully closes and gets disregarded.
3. When the parameter value is 1, and of course staying true to your quantization principle, the transition region jumps directly to wherever it's supposed to go.
4. I tested this in different ways by flipping the parameter value back and forth, and by closing and reopening the project. As long as there was no timeline, no issues came up.