Jean-Michaël Celerier

hey! that looks like an interesting bug. I don't understand why specifically the first would cause this and not the subsequent ones. @avilleret if you happen to have an idea..

thanks for the repro!

> Decoupling namespace hierarchy from patching hierarchy. I mean, the *whole* point of ossia max is to create a hierarchy of objects from a hierarchy of patches, no? (and it...

giving ossia.cue the ability to enumerate / filter / list addresses for the sake of displaying inside jit.cellblock like the jamoma namespace / preset manager

Hello! I just noticed that the windows CI seems to be broken with the latest CMake version (it worked a week ago -_-). Did you try the build steps outlined...

> I just tried: I only managed to build ossia_cpp (not ossia itself) in 2.0RC1 and 1.2.9 with VS2022. if you build ossia_cpp you should already have the libossia library...

I guess there's an MSVC minor version bug as this works fine on godbolt with the exact flags we use for building https://gcc.godbolt.org/z/r44veq9rK

i'm at loss, even copying the ossia value.hpp code verbatim works here: https://gcc.godbolt.org/z/cqq857oYq

https://developercommunity.visualstudio.com/t/MSVC-143431933:-vectorgt;-with-B-a-fo/10232137 can't do much better than that :|

Can you folk check that you don't have ossia.attribute objects in there ? I think this is what we had found that was causing the huge load times