When is history required between objects?

nan's icon

Hi

I was struggling with a gen patch not compiling and i eventually realised that it was the connection between sah and slide. When I put a history object between the connection this problem was solved. Is due to a feedback loop being created?

I don't understand however why a similar connection between sah and < works without a history object in between. Is there a way to know which objects behave like the < and which like slide?

Cheers

Max Patch
Copy patch and select New From Clipboard in Max.

Alois Cerbu's icon

That's odd – I don't have any issue compiling the patch without [history] there.

Bradley Korth's icon

It compiles fine for me as well, with or without it. However, the error message you posted says compilation is trying to reference a nonexistent sah object. Perhaps try copying everything and repasting it? Perhaps try using this gen~ object outside your regular patcher?

👽'tW∆s ∆lienz👽's icon

i copied the patch into an empty gen~, i started the dac, and i got no error message, then i detached the patch-chord connecting history to slide and attached it instead to the outlet of the 'sah 0.1' just above the history op and then i got the same exact error(complaining about a non-existent sah). very strange. maybe this is one you need to contact support for since different people get different results(?)

nan's icon

@Bradley This is in a separate patch as i moved there to try and problem solve. Copying and pasting just seems to recreate the problem, as does building the patch from scratch.

@R∆j∆ That is interesting I initially thought it was a bug but, given my inexperience thought I must have done something wrong. I will contact support.


The interesting thing is it generates another phantom object every time I tried to recompile, you can see in the error message that this is sah_1182! The problem was also happening between scale and slide so I presume that it is something to do with the slide object.

👽'tW∆s ∆lienz👽's icon

ya, i feel the same: slide probably needs to keep a history within to do its thing, perhaps there's an unseen feedback loop created... not sure... in any case, when you contact them let them know your specs, too, mine were this in case it helps:
macOS Big Sur 11.1 - 15-inch MacBookPro 2015 - 2.8GHz i7 - 16GB RAM