I found this and its been great so far:
https://www.kadenze.com/courses/real-time-audio-signal-processing-in-faust/info
I imagine it has been shared on the forum before but here it is again for beginners like me.
free course.
I found this and its been great so far:
https://www.kadenze.com/courses/real-time-audio-signal-processing-in-faust/info
I imagine it has been shared on the forum before but here it is again for beginners like me.
free course.
@jeffd
ok i figured it out, for some reason my send effect wasnt connected to my send container.
no idea how that happened.
but works again
@d-healey yeah it must be that particular effect.
a tried an even simpler delay and it compiled and worked!
seems so odd. works on mac but not on windows.
it was just the smooth delay i am using found here:
https://faustdoc.grame.fr/examples/delayEcho/#smoothdelay
that is throwing the error.
doesnt seem that complicated but that is the problem.
Ill try to smooth out the other delay that works with some smoothing nodes in scriptnode to try to match my mac version i guess.
@d-healey got it working!
@d-healey
i always have another backup project on my pc,
so i started over with that.
so unfortunately, no idea of what was actually causing it.
@d-healey got it working finally
time to get off my computer now lol
happy holidays!
@clevername27
yes! i got it to work!
Do i need to update to sonoma on mac to get faust to work with the latest dev build?
i got it to "kinda" work on ventura with an older version of faust.
worked ok for the delay i built.
ok, im so dumb. I had the send container going back into channels 1 and 2 of container 1 and feedbacking on itself. So i added 2 other channels to container 1.
it works now!!
@David-Healey ah ok.
im guessing after ableton, logic, cubase, and reaper--
fl studio and studio one are the next 2 you should test with.
and looks like a fl studio trial can test thirdparty plugins, but studio one you woudd need a pro license or subscription. But I havent tried those 2 so I could be wrong.
and of course pro tools if you are doing AAX.
@David-Healey said in Testing before release:
Qtractor, Ardour,
wow, ive never even heard of these two.
Is there an affordable way to test all the different DAWS without having to spend all out on the pro versions?
I currently have logic and bitwig, and then some versions of cubase and ableton lite for testing, and of course reaper.
But the other daws I dont own. Do you use demo versions on each operating system to test?
The amount of permutations with vst, audio unit, DAW and operating system is overwhelming to say the least.
I use pluginval as well but im not sure if thats completely realiable.
@jeffd
ok that was my problem.
i needed to set the array for the channelIndexes
@jeffd ah that just changes the meters to 2 columns for stereo
@d-healey 
i had Channelndexes set to null.
the docs say Set to [0,1] for stereo.
so changed that to 1 but didnt make a difference.
also..i cant figure out what the "Index" is?
tried using just 1 and doesnt do anything different.
anything look strange here?
hold on let me try [0,1]
@d-healey got it working!
@d-healey
isnt the link file going to be located in a different location for each operating system?
Is there documentation somewhere on how to get HISE to find the path in the operating system?
@d-healey can i delete the link file via a script?
not sure i understand.