Faust acting up on Windows
-
@jeffd this is the last version that works, 2.68 is acting up as well.
-
Good to know. Thanks
-
well, now i cant get my plugin to export on mac with faust, even though the dsp network works as a hardcoded effect in the standalone.
it says the dspnetwork is not compiled when i try to export the plugin, yet im using the compiled dll in the hardcodedmaster fx module.
I must be misunderstanding what a dsp network is
no idea -
Interesting, I can reproduce this with the latest Faust 2.7.4.
What's weird is that if I close HISE and click on the
batchCompile.bat
file in theDspNetworks/Binaries
folder to manually launch the compile script in a separate cmd window, the compilation goes through fine (also when compiling it through VS2022). If I do the same thing while HISE is still open (after the export process) it also fails. Can you reproduce this?It looks like the Faust compiler is holding some kind of file lock that prevents the read access (I'm writing the faust files just short before the compilation).
BTW, do you guys have like, sound in Faust 2.74? It completely stopped working here and I'm not sure if I messed up the install or if there is something seriously wrong. The faust compilation goes through and I can step through the debugger so I know it calls into the Faust library, but there's no processing going on at all.
-
@Christoph-Hart I pulled the latest commit, still failing compiling networks on 2.74.
Also no output on 2.74 on Windows. But code output on 2.72 works fine.
2.72 fails to compile the network as well.
-
@Christoph-Hart
i also had no sound in 2.74,
but at the time i thought it was user error -
So 2.7.2 still produces output, but 2.7.4 doesn't?
-
@Christoph-Hart yes
but compilation fails from 2.68 onward
-
@aaronventure does it work if you close HISE, then double click on the batchCompile.bat file in DspNetworks/Binaries?
-
@Christoph-Hart 2.68 fails with the exact same error when launching the BatchCompile.bat
-
@aaronventure also when HISE is closed?
-
@Christoph-Hart yes, open or closed,fails.
-
@Christoph-Hart here's more fun for you: the latest commit
0b2885d - - fix faust code export with Faust versions > 2.6.0
fails to compile the network even with 2.60
reverting down to yesterday's
bb1a664 - - added setFFTSize() to timestretch API - removed dependencies from hi_streaming
works fine.
-
@aaronventure Another kicker.
On this commit
bb1a664 - - added setFFTSize() to timestretch API - removed dependencies from hi_streaming
compiling a network from HISE fails, but if I close HISE and launch the bat, it goes through and the compiled Faust file is visible as a node in the projects category.
So:
- your latest commit messes things up and even 2.60 doesn't work
- troubles started with 2.68.
- 2.74 breaks the Faust output entirely on Windows.
-
@aaronventure Ok I think just messed up epically with the last commit, I‘ll check when I get back.
-
That's a new low even for me.
-
Should wait and try to export my plugin after an update before I try to delete all these dsp networks and start over?
-
@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.