Faust acting up on Windows
-
@aaronventure
I thinks that’s what happen to me..
And now I have all these dsp Networks with different names that are there in the folders but I thought they didn’t compile. -
@Christoph-Hart I was about to screenshot the funky change in the broken commit and post it for laffs but I guess it slipped past hah
-
@jeffd
ok,
I just deleted the hardcoded fx from the project and any files related to additional sourcecode and dsp networks.Plugin compiled and works as audio unit and vst.
phew!and ill just create the faust effect again and keep as sxriptFX in the project for now.
try the hardcoded effects as a test in another project before I try it on my main one next time.
-
@jeffd Yea this issue crops up every now and agian
https://forum.hise.audio/topic/9825/add-module-state-to-user-preset-help/3?_=1720037021620
-
@HISEnberg
heard -
@Christoph-Hart Still no code output from a Faust node on 2.74, but if I compile the network and load the compiled Faust file (not necessarily the network) from the Projects tab in Scriptnode, it works.
-
@aaronventure
Also, no.rnoise doesn't crash HISE anymore, but fails to build as a networkCrashes on 2.72 (probably due to arc4random missing).If I change it to no.noise, it goes through fine.
The warning on Faust website
Again, it works fine on macOS.
-
I talked to Stephane yesterday - the API changed from 2.72 to 2.74 so I need to update the HISE wrapper to reflect this.
I could get it to work here but it will break using previous Faust versions, so I need to think whether it makes sense to branch it or just tell people to download and use the lateat Faust version.
-
@Christoph-Hart said in Faust acting up on Windows:
just tell people to download and use the lateat Faust version
This - unless it breaks on older OS versions
-
@d-healey I‘m not aware of anything that breaks compatibility with older versions.
Alright then I‘ll move to the latest release and do a check that prints an error message if you use Faust <2.74 - currently it just crashes so that‘s not the world‘s nicest UX.
-
OK, so I've pushed the change that switched to Faust 2.74.6 - all older versions stopped working so you need to reinstall Faust if you want to use it.
@aaronventure that should solve all problems with the most recent Faust version, right? I don't care too much about
rnoise
something something, that's Faust territory :) -
@Christoph-Hart said in Faust acting up on Windows:
@aaronventure that should solve all problems with the most recent Faust version, right? I don't care too much about rnoise something something, that's Faust territory :)
Shouldn't you? It works on mac but doesn't on the Windows implementation.
It's a way to get true randomization in Faust because no.noise by default locks to a generated seed, so even if you call it twice or more times, once for each output, you're still getting a mono signal.
If you create two separate Faust files (different files with different names), put them in two different Faust nodes in a multi node, you're still getting a mono output because both are generating from the same seed.
The warning might be a clue but I have no idea what it means.
-
@aaronventure yeah, no idea why it crashes and how to solve it. I'm not the Faust maintainer :)
In order to get a stereo noise signal, just multiply it with a random number and then use fmod to fold it back into 0...1
// Faust Source File: rnoisefunk // Created with HISE on 2024-07-04 import("stdfaust.lib"); // booh! mono //process = no.noise, no.noise; // noice stereo noice noice noice process = fmod(no.noise * 139.2124, 1.0) , no.noise;
-
even better:
// additional delay by 32 samples. process = fmod(no.noise * 139.2124, 1.0) , no.noise @ 32;
-
@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
-
-