n871

I made a super smooth 7-segment display patch. 

1. You can scroll the red num box with the speed of light and it works perfectly. 

2. Hit the red toggle, once a metro or tempo object is connected everything falls apart...

anyone an idea why this is? I'm having this issue in Max 8.1.8.

split

message

unpack

counter

metro

toggle

panel

number

I made a super smooth 7-segment display patch. 
1. You can scroll the red num box with the speed of light and it works perfectly. 
2. Hit the red toggle, once a metro or tempo object is connected everything falls apart...

I made a super smooth 7-segment display patch. 
1. You can scroll the red num box with the speed of light and it works perfectly. 
2. Hit th

can-someone-possibly-check-this-super-easy-7-segment-display-patch-why-is-metro-acting-this-weird

seems to work just fine for me in the most current version of Max👇

works.mp4

just update your version of Max and hopefully it works(?) 🍻

seems to work just fine for me in the most current version of Max👇


hahaha cool video : D much appreciated!!! Let's see if 8.3.1 indeed solves it for me.

you could also downgrade to older max version

m6.mov

nothing wrong with your patch, but it can be optimised a bit.

I inserted 7 segment code into menu instead of all that select objects.

change prevents resending result of /10 values 10 times instead of once.

nothing wrong with your patch, but it can be optimised a bit.
I inserted  7 segment code into menu instead of all that select objects.
change prevents resending result of /10 values 10 times instead of once.


Scrolling for me manually works fine, but the metro acts buggy. qmetro works alright, so it's likely a threading issue when being driven by something in the high priority thread. You can also try defer/deferlow.

here bgfillcolor message version for > max 6

here bgfillcolor message version  for > max 6


Thanks for all the replies! Max 8.1.3 didn't solve it for me, sometimes it works, sometimes it doesn't. Then I checked qmetro, and so far no more problems! I will also look into defer and deferlow. In Max 7 I don't have these issues with the regular metro object, but I couldn't use my patch there because none of my vsts are being loaded...no vst, no vst3, no components, older stuff yes, but none of the newer ones, is this normal?

EDIT: seems like I deleted my message by mistake. All replies are much appreciated. The qmetro object solved it for me. I need to check defer and deferlow as well. Thanks again!

Can someone possibly check this super easy 7-segment display patch, why is metro acting this weird?