FrameLib
FrameLib copied to clipboard
AlexHarker
fl.interval~ cannot be connected to fl.frommax~ if it is connected to an fl.tomax~
Max disables the connection of the fl.interval~ in these circumstances, presumably taking the existing sane connection logic but missing this edge case where you want to go from a FrameLib network to max and then back.
Weird. Nice catch! I think it must identify the output of fl.tomax~ as a Framelib connection but it shouldn't!
I'm interested in why you want to do this though? You could do something similar using fl.register~ that would probably be better - am I missing something or a use case that is clearer?
(I'll fix it either way but I'm intrigued as to how you ended up trying this)
You have now seen the patch sent to you for another issue where I do some offline processing and pass the last frame along in this manner, so thats one use case, though you can patch around it as you've indicated above.
No - that's clear - this is for two different networks, which is not possible otherwise - needs fixing.