Stéphane, I just compiled the cpp files, and we are almost there:
I made two Ugens for comparison
{FaustHOATestEncoder1.ar(WhiteNoise.ar(0.1), azimuth_0: MouseX.kr(-pi, pi),
elevation_0:MouseY.kr(-pi * 0.5, pi * 0.5) )}.play
{FaustHOATestEncoderDebug1.ar(WhiteNoise.ar(0.1), azimuth_0: MouseX.kr(-pi,
pi), elevation_0:MouseY.kr(-pi * 0.5, pi * 0.5) )}.play
both throw at server boot the following:
Faust: supercollider.cpp: sc_api_version = 2
Faust: FaustHOATestEncoder1 numControls=6
Faust: supercollider.cpp: sc_api_version = 2
Faust: FaustHOATestEncoderDebug1 numControls=6
However, when I launch the individual Ugens they behave correctly, I get
for:
{FaustHOATestEncoder1.ar(WhiteNoise.ar(0.1), azimuth_0: MouseX.kr(-pi, pi),
elevation_0:MouseY.kr(-pi * 0.5, pi * 0.5) )}.play
> Synth('temp__33' : 1000)
and for:
{FaustHOATestEncoderDebug1.ar(WhiteNoise.ar(0.1), azimuth_0: MouseX.kr(-pi,
pi), elevation_0:MouseY.kr(-pi * 0.5, pi * 0.5) )}.play
> Synth('temp__34' : 1001)
Faust[FaustHOATestEncoderDebug1]:
Inputs: 7
Outputs: 4
Callback: zero-copy
can we still get rid of the debug message at boot time?
Best,
Florian
PS.: If faus2supercollider could have a way to easily return the cpp files
that would be great. Pierre Lecomte has made a project specific script that
digs through the temp folder to collect the cpp. But for other SC3plugins
developers, it would be great to have an easy way to get the cpp file
back.
www.grond.at
On Wed, Mar 8, 2017 at 11:48 AM, Stéphane Letz <l...@grame.fr> wrote:
>
> > Le 8 mars 2017 à 17:37, Florian Grond <floriangr...@gmail.com> a écrit :
> >
> > Thanks Stéphane,
> >
> > I installed the most recent faust version:
> >
> >
> > Thanks for changing the paths, please if you can adjust the order:
> >
> > in fact an include should possibly be behind each of the paths listed.
> >
> > if you compare with
> > https://github.com/supercollider/supercollider/tree/master/include
> >
> > this is where the plugin_interface resides no matter where you put the
> SC sources
> > #-------------------------------------------------------------------
> > # Need SuperCollider 'plugin_interface' include path to compile UGens:
> >
> >
> >
> >
> > SC0=$SUPERCOLLIDER_HEADERS
> > SC1="/usr/local/include/SuperCollider/include"
> > SC2="/usr/local/include/supercollider"
> > SC3="/usr/include/SuperCollider"
> > SC4="/usr/include/supercollider"
> > SC5="/usr/local/include/SuperCollider/«
>
>
> Done on GIT.
>
> >
> >
> > As far as the the -dm flag is concerned. I can set it and it compiles
> into the cpp files, if I also set the -d flag.
> >
> > I have not compiled the resulting cpp files yet, but they look pretty
> identical to me no matter if I set the -dm flag or not.
>
> Yes sure.
>
> >
> > I believe that if the -dm flag is not set the cpp file should feature
> the MACRO
> >
> > #define NDEBUG
> >
> > and if it is set this should be commented out
> >
> > // #define NDEBUG
> >
> > so that all the print messages show accordingly for debugging
> >
> > #if !defined(NDEBUG)
> > Print("Faust: %s numControls=%d\n", name.c_str(), g_numControls);
> > #endif // NDEBUG
> >
> > If there was an easy way for the faust2supercollider script to return
> the sc + (scx / so /dll) and optionally the cpp with or without debug mode
> that would be of great help for the SC folks.
> >
> > Thanks a lot,
> >
> > Florian
> >
> >
>
> The point of -dm is to define set DNDEBUG to that the code path in
> correctly compile in the cpp file.` Please test the cpp code first.
>
> Stéphane
>
>
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users
