AL10 BUG - Seg. BPM value not responding in clip view

[Doktor RyConn]

I am experiencing another bug with Live 10.

After you load in a clip, if you try to adjust the Seg. BPM in clip view of Live 10, the field is frozen and won't allow any adjustment until you either select another clip then go back to the first clip or Un-Warp then Re-Warp the clip.

Any work around for this bug?

[yur2die4]

Do you have a warp marker selected?

Seg, bpm is the bpm of a segment directly following a warp marker.

[Doktor RyConn]

Do you have a warp marker selected?

Seg, bpm is the bpm of a segment directly following a warp marker.

Thanks for the reply, yur2die4.

I'm not selecting any warp markers or changing anything when I load in a new clip.

I've gotten it to act a little more smoothly (for now). I believe it's been happening at the start of when I build a live set but then after loading a couple clips, the Seg. BPM field appears adjustable when I load in a new clip.

However, just a moment ago, I was building a set for about 25 mins. and then it happened again! It seemed pretty random and I've never seen this happen in Live 9.

I've included a screenshot to display the difference in the clip view displays:
https://ibb.co/jazTan

Additional Seg. BPM confusion/trouble
I think it's weird when my global Live set template is set to 95 BPM, and my Maschine plugin is set to 95 BPM, when I drag in the clips the Seg. BPM will default to something strange like 77.45 BPM. I know that the reverb/delay tails of the exported clip may play into this but - is there a best practice to importing clips and having them FIXED to the global BPM?

This is really why I'm fiddling with the Seg. BPM value. If there was a way to export my Maschine patterns as clips with global BPM, that would be great!

[yur2die4]

The image you shared shows zero context of what you have highlighted in the clip. So it doesn't mean anything.

[Doktor RyConn]

The image you shared shows zero context of what you have highlighted in the clip. So it doesn't mean anything.

Alright I’ll take the guilt there. I’ll try to post a new screenshot of this issue.

As I’m definitely no expert, the most I can say is that the Seg. BPM field just acts “wonky” and more stubborn than it did in Live 9.

I know - not the greatest description of my issue.

Updates to come...