Strange absolutepath behaviour with umenu/coll
I am retrieving pictures within a Max project via a [umenu] whenever the onset of incoming audio is detected. Which picture is retrieved depends on the analysis of another audio signal.
I noticed strange behaviour where the paths are not found with this mechanism, however, when I select elements in the umenu manually or send in ints with a number object manually, it works. The messages that come out of umenu are the same in all circumstances though.
I made a test project and the same behaviour occurs. Does anyone know why this happens? I suppose using a umenu for this is not best practice, but I tried with a coll and it causes the same problem...
Problem is that you create too many ints.
And that is caused by onset output
I added another change after the [int] object and printed the results. The method with the onset bangs that is not working is creating less output through the switch than when I route through the decide immediately, which is working. Doesn't this prove that it is not a matter of too much output?
you can proove what you want to.
Too fast input to absolute path
is your problem.
what shoud change help there ?
if input changes too fast, and it does
because you have 2 trigger sources, absolute path gives up.
I see, the time between two bangs is sometimes too small. I just hadn't expected it to fail every single time becaue of that.
A [change] object decreases the amount of input to the umenu or coll. So the same picture isn't retrieved multiple times.
Thanks for your solution.
reading or writing files = not threadsafe. so sometimes it is possible that commands are queued, but sometimes things break.
where you can, wait for a file beeing loaded and then trigger the next load command from there.