After a bunch of testing and recompilng i still got the excatly same linker error... I'm not sure but seens like some of the files are missing.

I also tried leave it uncompiled but it won't actually include in the compiled plugins even just a blank script with only one node inside. Also sometime it pops up sanity check failed too.

Has anybody successfully compile the stretch player node? It's all about this only one node so I think I probably missed something....

@Christoph-Hart said in Phase coherence broken when SendContainer comes before Sampler in the module tree:

Actually I can‘t think of a use case where having the container before the source would be useful

You may want the container to be after the source but not want it to be at the end of the chain. I can't think of a particular use case, but it may come up in the future.

@Lindon

This is good to know. Thanks!

@d-healey thanks, I’ll have a look

@teamallnighter What HISE are you running?

@alobassmann is GainEditor.cpp the Simple Gain effect?

@Christoph-Hart is there any chance to consider a feature where we can do a forever-export of a Faust file to a .cpp file that we can just save and forget about it? Then we can just plug it into any future project and it loads as a node with parameters (like it does when you compile it right now)?

I created some modules that are decently simple, do what I want them to do and sound great - I would be very happy if they kept doing that forever, wherever I pull the project on, without having to worry about the correct version of Faust being installed, about recompiling the entire networks and making sure it's all well when first pulling on a new system etc.

@d-healey see my other post - I cant even get to any code I've written for FAUST as HISE says Im still on the old version.

@d-healey I managed to bypass it by manually setting <ExportSetup value="Yes"/> in compilerSettings.xml

I just noticed a fix to the midi keyboard has been pushed, does it solve this?

For Reaper, you can change shortcut behaviour.

1 -For plugins you can send all keyboard input to the plugin ( this is done by FX menu.)

2- You can set the shortcut scope to global, normal and global+text field (this is done by actions - edit shortcut )

@bendurso I can't remember. It's been years since I dealt with sample libraries.

@Christoph-Hart said in Monlith reference sample start/end screwed up:

just check the monolithoffset property for differences between the two.

Running into issues with this again. One thing I noticed is I have a sample map, which was previously saved as its own monolith, contains monolith offset values, but when I redirect the sample map to another monolith, these offsets don't change. Should they?

Is it a case that both sample maps need to have the same mapping but the properties of the zones can be different?

@Christoph-Hart that's still hardcoded and all the node instances of that file will share the seed

but you have me an idea to just link the random node from scriptnode into the faust parameter, so that'll work as the random node gets instanced on startup

@d-healey Alright these are fixed now.