Re: [Faudiostream-users] OSC support on M1

[Stéphane Letz]

> Le 10 janv. 2022 à 17:47, Alessandro Anatrini  a écrit 
> :
> 
> Hi everyone,
> 
> I’m facing an issue when trying to compile a faust project that I exported as 
> jucer file via the faust2juce tool.
> I’m on an M1 machine and the issue is related to OSC support.
> Although the build succeeds (Xcode 13.2.1), OSC does not seem to work at all, 
> the standalone does not receive or send any OSC message, same story if I 
> build the project as VST.
> The exact same project just works fine when compiled on another Mac (Intel) 
> with Xcode 11.3.1.
> 
> I'm using Faust 2.38.8 and I saw that the oscpack library is quite old and 
> just wanted to know if anyone is aware of similar issues on M1 machines, or 
> is able to compile with working OSC support. Any help would be much 
> appreciated.
> 

oscpack library  is not used in the JUCE exported project. We are directly 
using JUCE OSC implementation with some glue code from here: 
https://github.com/grame-cncm/faust/blob/master-dev/architecture/faust/gui/JuceOSCUI.h

Can you possibly debug directly in the JUCE generated XCode project?

Thanks.

Stéphane 

___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

[Faudiostream-users] OSC support on M1

[Alessandro Anatrini]

Hi everyone,

I’m facing an issue when trying to compile a faust project that I exported
as jucer file via the faust2juce tool.
I’m on an M1 machine and the issue is related to OSC support.
Although the build succeeds (Xcode 13.2.1), OSC does not seem to work at
all, the standalone does not receive or send any OSC message, same story if
I build the project as VST.
The exact same project just works fine when compiled on another Mac (Intel)
with Xcode 11.3.1.

I'm using Faust 2.38.8 and I saw that the oscpack library is quite old and
just wanted to know if anyone is aware of similar issues on M1 machines, or
is able to compile with working OSC support. Any help would be much
appreciated.

Thanks,
Alessandro Anatrini
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC Configure Ports

[Dominique Fober]

Hi Matt,

Have a look at the automatic port allocation scheme

You can also change the port numbers on the commande line (see the section
above)
--
Dom


Le sam. 24 juil. 2021 à 10:28, Matt Comeione  a
écrit :

> When compiling a .dsp file the documentation indicates that you can use:
>
> declare options "[osc:on]”;
>
> In order to enable OSC support in the build.  Is there a way to specify
> port numbers?  The use case would be to build different stand alone objects
> that could be reliably invoked without port conflicts.
>
>
> ___
> Faudiostream-users mailing list
> Faudiostream-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/faudiostream-users
>
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC Configure Ports

[Stéphane Letz]

Then start them with different input ports at runtime.

Stéphane 

> Le 24 juil. 2021 à 11:09, Matt Comeione  a écrit :
> 
> I realize both of those settings.  However if I’m building a stand alone 
> binary is there a way to configure that so it will statically assign the 
> listener? Use case is that if I’m running two binaries concurrently I would 
> like to have a way to predictably know the port numbers for each of the 
> binaries.
> 
> --
> Matt Comeione 
> 
>> On Jul 24, 2021, at 2:02 AM, Dominique Fober  wrote:
>> 
>> 
>> Hi Matt,
>> 
>> Have a look at the automatic port allocation scheme
>> You can also change the port numbers on the commande line (see the section 
>> above)
>> --
>> Dom
>>  
>> 
>> Le sam. 24 juil. 2021 à 10:28, Matt Comeione  a écrit :
>> When compiling a .dsp file the documentation indicates that you can use:
>> 
>> declare options "[osc:on]”;
>> 
>> In order to enable OSC support in the build.  Is there a way to specify port 
>> numbers?  The use case would be to build different stand alone objects that 
>> could be reliably invoked without port conflicts.  
>> 
>> 
>> ___
>> Faudiostream-users mailing list
>> Faudiostream-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/faudiostream-users
> ___
> Faudiostream-users mailing list
> Faudiostream-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/faudiostream-users



___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC Configure Ports

[Stéphane Letz]

Read the OSC documentation here: 
https://faustdoc.grame.fr/manual/osc/#osc-support

Especially the "Automatic Port Allocation » section: 
https://faustdoc.grame.fr/manual/osc/#automatic-port-allocation

And ports can possibly be selected also at runtime.

Stéphane 

> Le 24 juil. 2021 à 09:57, Matt Comeione  a écrit :
> 
> When compiling a .dsp file the documentation indicates that you can use:
> 
> declare options "[osc:on]”;
> 
> In order to enable OSC support in the build.  Is there a way to specify port 
> numbers?  The use case would be to build different stand alone objects that 
> could be reliably invoked without port conflicts.  
> 
> 
> ___
> Faudiostream-users mailing list
> Faudiostream-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/faudiostream-users



___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC Configure Ports

[Matt Comeione]

I realize both of those settings.  However if I’m building a stand alone binary 
is there a way to configure that so it will statically assign the listener? Use 
case is that if I’m running two binaries concurrently I would like to have a 
way to predictably know the port numbers for each of the binaries.

--
Matt Comeione 

> On Jul 24, 2021, at 2:02 AM, Dominique Fober  wrote:
> 
> 
> Hi Matt,
> 
> Have a look at the automatic port allocation scheme
> You can also change the port numbers on the commande line (see the section 
> above)
> --
> Dom
>  
> 
>> Le sam. 24 juil. 2021 à 10:28, Matt Comeione  a écrit :
>> When compiling a .dsp file the documentation indicates that you can use:
>> 
>> declare options "[osc:on]”;
>> 
>> In order to enable OSC support in the build.  Is there a way to specify port 
>> numbers?  The use case would be to build different stand alone objects that 
>> could be reliably invoked without port conflicts.  
>> 
>> 
>> ___
>> Faudiostream-users mailing list
>> Faudiostream-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/faudiostream-users
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

[Faudiostream-users] OSC Configure Ports

[Matt Comeione]

When compiling a .dsp file the documentation indicates that you can use:

declare options "[osc:on]”;

In order to enable OSC support in the build.  Is there a way to specify port 
numbers?  The use case would be to build different stand alone objects that 
could be reliably invoked without port conflicts.  


___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC

[Henrik Frisk]

Ah... great, thanks!

/Henrik

On Sun, Mar 25, 2018 at 6:06 PM, Stéphane Letz  wrote:

> Read de documentation  here http://faust.grame.fr/images/
> faust-quick-reference.pdf, chapter 6 OSC support
>
> Command lines options to be used when stating the application, p72 :
>
> -xmit 0|1|2 turn transmission OFF, ALL or ALIAS(defaultOFF)
>
> Stéphane
>
> > Le 25 mars 2018 à 16:10, Henrik Frisk  a écrit :
> >
> > On Sun, Mar 25, 2018 at 9:22 AM, Henrik Frisk  wrote:
> > HI,
> >
> > Relatively new to Faust so apologies if I am overseeing something
> obvious.
> >
> > I can't get my compiled faust code to send nor receive osc. Compiling
> with 'faust2jaqt -osc ' works fine but the resulting binary doesn't respond
> nor send osc. The same code loaded in FaustLive works as expected with osc.
> Have I missed some dependency? I have liblo installed with brew.
> >
> > After som more testing I can now receive OSC on my faust program
> compiled either with faust2jack or faust2jaqt, but it still doesn't send.
> I'm monitoring with oscdump which receives the parameter space as expected
> from sending a "get" message, but moving the knobs in the program doesn't
> yield any output.
> >
> > Thanks for great software!
> > /Henrik
> >
> > 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot__
> _
> > Faudiostream-users mailing list
> > Faudiostream-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/faudiostream-users
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC

[Stéphane Letz]

Read de documentation  here 
http://faust.grame.fr/images/faust-quick-reference.pdf, chapter 6 OSC support 

Command lines options to be used when stating the application, p72 :

-xmit 0|1|2 turn transmission OFF, ALL or ALIAS(defaultOFF)

Stéphane 

> Le 25 mars 2018 à 16:10, Henrik Frisk  a écrit :
> 
> On Sun, Mar 25, 2018 at 9:22 AM, Henrik Frisk  wrote:
> HI,
> 
> Relatively new to Faust so apologies if I am overseeing something obvious. 
> 
> I can't get my compiled faust code to send nor receive osc. Compiling with 
> 'faust2jaqt -osc ' works fine but the resulting binary doesn't respond nor 
> send osc. The same code loaded in FaustLive works as expected with osc. Have 
> I missed some dependency? I have liblo installed with brew.
> 
> After som more testing I can now receive OSC on my faust program compiled 
> either with faust2jack or faust2jaqt, but it still doesn't send. I'm 
> monitoring with oscdump which receives the parameter space as expected from 
> sending a "get" message, but moving the knobs in the program doesn't yield 
> any output.
> 
> Thanks for great software!
> /Henrik
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> Faudiostream-users mailing list
> Faudiostream-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/faudiostream-users


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC

[Henrik Frisk]

On Sun, Mar 25, 2018 at 9:22 AM, Henrik Frisk  wrote:

> HI,
>
> Relatively new to Faust so apologies if I am overseeing something obvious.
>
> I can't get my compiled faust code to send nor receive osc. Compiling with
> 'faust2jaqt -osc ' works fine but the resulting binary doesn't respond nor
> send osc. The same code loaded in FaustLive works as expected with osc.
> Have I missed some dependency? I have liblo installed with brew.
>
> After som more testing I can now receive OSC on my faust program compiled
either with faust2jack or faust2jaqt, but it still doesn't send. I'm
monitoring with oscdump which receives the parameter space as expected from
sending a "get" message, but moving the knobs in the program doesn't yield
any output.

Thanks for great software!
/Henrik
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

[Faudiostream-users] OSC

[Henrik Frisk]

HI,

Relatively new to Faust so apologies if I am overseeing something obvious.

I can't get my compiled faust code to send nor receive osc. Compiling with
'faust2jaqt -osc ' works fine but the resulting binary doesn't respond nor
send osc. The same code loaded in FaustLive works as expected with osc.
Have I missed some dependency? I have liblo installed with brew.

Thanks,
Henrik
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

[Faudiostream-users] OSC: root path is 0x00 instead of application name

[cyberic]

Hi

This bug has been reported in a github issue here:
https://github.com/grame-cncm/faust/issues/33

But I think posting it here is more appropriate:

I'm following instructions in the tutorial here: 
http://faust.grame.fr/docs/faust-quick-reference.pdf, on page 52:
$ cat noise.dsp

declare name "noise";
process = library("music.lib").noise*hslider("level", 0, 0, 1, 0.01);

I'm using faust version 3cd7b7c

faust2jaqt -midi -httpd -osc noise.dsp

./noise -xmit 1

If I use oscdump:
$ oscdump 5511
and if I move the slider, I get:

Faust OSC version iii "0.96" "-" "'0x00'" "is running on UDP ports " 5510 
5511 5512
/0x00/level f 0.00
/0x00/level f 0.03
/0x00/level f 0.054700

With $ oscsend localhost 5510 "/*" s get
I get:

/0x00 si "xmit" 1
/0x00 ss "desthost" "127.0.0.1"
/0x00 si "outport" 5511
/0x00 si "errport" 5512
/0x00/level fff 0.00 0.00 1.00

If I try to send OSC messages with the /noise root path, I get nothing back. 
but with /0x00, it works:

oscsend localhost 5510 "/noise/level" s get:
nothing

oscsend localhost 5510 "/0x00/level" s get:

/0x00/level fff 0.00 0.00 1.00

The tutorial states that the root OSC path should be 'noise'
Why do I get 0x00 ?

Thank you
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] osc compilation issue

[Pierre Lecomte]

Hello,
> Probably « yet another lib++/libstdc++ or c++11 » related compilation issue
> : which OS X version? which Xcode/clang versions?

Linux Ubuntu 16.04
clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final)

Thanks.
Pierre

> Thanks.
> 
> Stéphane
> 
> > Le 20 sept. 2016 à 13:10, Pierre Lecomte  a écrit
> > :
> > 
> > Hello,
> > I've got some issues when trying to compile some code with osc aliases :
> > 
> > test.dsp:
> > 
> > import("stdfaust.lib");
> > process=_*hslider("Gain[osc:/gain 0 10]", 0, 0, 10, 0.01);
> > 
> > faust2jaqt -osc test.dsp returns :
> > 
> > test.o: dans la fonction « void
> > oscfaust::FaustFactory::addAlias(std::__cxx11::basic_string > std::char_traits, std::allocator > const&, float*, float,
> > float, float, float, float, char const*) »:
> > test.cpp:
> > (.text._ZN8oscfaust12FaustFactory8addAliasIfEEvRKNSt7__cxx1112basic_string
> > IcSt11char_traitsIcESaIcEEEPT_SA_SA_SA_SA_SA_PKc[_ZN8oscfaust12FaustFactor
> > y8addAliasIfEEvRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPT_SA
> > _SA_SA_SA_SA_PKc] +0x25a): référence indéfinie vers «
> > oscfaust::MessageDriven::getOSCAddress[abi:cxx11]() const »
> > test.o: dans la fonction « void
> > oscfaust::FaustFactory::addnode(char
> > const*, float*, float, float, float, bool, bool) »:
> > test.cpp:
> > (.text._ZN8oscfaust12FaustFactory7addnodeIfEEvPKcPT_S4_S4_S4_bb[_ZN8oscfau
> > st12FaustFactory7addnodeIfEEvPKcPT_S4_S4_S4_bb] +0xbb): référence
> > indéfinie vers «
> > oscfaust::MessageDriven::getOSCAddress[abi:cxx11]() const »
> > test.o:(.rodata._ZTVN8oscfaust9FaustNodeIfEE[_ZTVN8oscfaust9FaustNodeIfEE]
> > +0x28): référence indéfinie vers «
> > oscfaust::MessageDriven::propose(oscfaust::Message const*,
> > oscfaust::OSCRegexp const*, std::__cxx11::basic_string > std::char_traits,
> > std::allocator >) »
> > collect2: error: ld returned 1 exit status
> > make: *** [test] Erreur 1
> > 
> > However, I've got the library file
> > 
> > /usr/local/lib/libOSCFaust.a
> > 
> > on my local installation..
> > 
> > Any ideas ?
> > 
> > Thanks,
> > Pierre
> > 
> > --
> >  ___
> > Faudiostream-users mailing list
> > Faudiostream-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/faudiostream-users



--
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] osc compilation issue

[Stéphane Letz]

Probably « yet another lib++/libstdc++ or c++11 » related compilation issue : 
which OS X version? which Xcode/clang versions?

Thanks.

Stéphane


> Le 20 sept. 2016 à 13:10, Pierre Lecomte  a écrit :
> 
> Hello,
> I've got some issues when trying to compile some code with osc aliases :
> 
> test.dsp:
> 
> import("stdfaust.lib");
> process=_*hslider("Gain[osc:/gain 0 10]", 0, 0, 10, 0.01);
> 
> faust2jaqt -osc test.dsp returns :
> 
> test.o: dans la fonction « void 
> oscfaust::FaustFactory::addAlias(std::__cxx11::basic_string std::char_traits, std::allocator > const&, float*, float, float, 
> float, float, float, char const*) »:
> test.cpp:
> (.text._ZN8oscfaust12FaustFactory8addAliasIfEEvRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPT_SA_SA_SA_SA_SA_PKc[_ZN8oscfaust12FaustFactory8addAliasIfEEvRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPT_SA_SA_SA_SA_SA_PKc]
> +0x25a): référence indéfinie vers « 
> oscfaust::MessageDriven::getOSCAddress[abi:cxx11]() const »
> test.o: dans la fonction « void oscfaust::FaustFactory::addnode(char 
> const*, float*, float, float, float, bool, bool) »:
> test.cpp:
> (.text._ZN8oscfaust12FaustFactory7addnodeIfEEvPKcPT_S4_S4_S4_bb[_ZN8oscfaust12FaustFactory7addnodeIfEEvPKcPT_S4_S4_S4_bb]
> +0xbb): référence indéfinie vers « 
> oscfaust::MessageDriven::getOSCAddress[abi:cxx11]() const »
> test.o:(.rodata._ZTVN8oscfaust9FaustNodeIfEE[_ZTVN8oscfaust9FaustNodeIfEE]
> +0x28): référence indéfinie vers « 
> oscfaust::MessageDriven::propose(oscfaust::Message const*, 
> oscfaust::OSCRegexp 
> const*, std::__cxx11::basic_string std::allocator >) »
> collect2: error: ld returned 1 exit status
> make: *** [test] Erreur 1
> 
> However, I've got the library file
> 
> /usr/local/lib/libOSCFaust.a
> 
> on my local installation..
> 
> Any ideas ?
> 
> Thanks,
> Pierre
> 
> --
> ___
> Faudiostream-users mailing list
> Faudiostream-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/faudiostream-users


--
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] osc aliases

[Stéphane Letz]

You can specify "-xmit 2" at launch time like :

./your_faust_pgm  -xmit 2

or you can possibly send on OSC message to change -xmit to 2

Note that aliases work also at "-xmit 0" (which is the default value)

(anything new on the processing side ?)

Stéphane
 
Le 11 janv. 2016 à 14:21, pierre.leco...@gadz.org a écrit :

> It's working now  ! Thank you. 
> An other question  : is it possible to specify -xmit 2 at compilation time to 
> fix the default transmission mode i.e. something like
> $  faust2jaqt mydsp.dsp -osc -xmit 2
> Thanks for help
> Pierre
> -- Message d'origine--
> De: Stéphane Letz
> Date: dim., 10/01/2016 8:56
> À: Pierre Lecomte;
> Cc: faudiostream-users@lists.sourceforge.net;
> Objet :Re: [Faudiostream-users] osc aliases
>  
> Le 10 janv. 2016 à 00:34, Pierre Lecomte 
>  a écrit :
> 
> > Hello,
> > I'm a bit confused with the use of osc aliases in Faust :
> > Let's say i've a slider in code
> > 
> > hslider("volume",0,-5,5,0,0.1);
> > 
> > when I run
> > 
> > $ oscsend localhost 5510 "/*" s get
> > 
> > I see it but the osc adress is very long :
> > 
> > /the/osc/adress/is/very/long/volume fff 0. -5. 5.
> 
> Yes the parameter OSC address reflects the complete "hierarchy" of 
> groups..etc.. that your UI code is using
> 
> > 
> > So I try to use aliases :
> > 
> > hslider("volume[osc:/level 0 10]",0,-5,5,0,0.1);
> > 
> > now when I run 
> > 
> > $ oscsend localhost 5510 "/*" s get 
> > 
> > /level ffssff -5. 5. "alias" "/the/osc/adress/is/very/long/volume" 
> > -5. 5.
> > 
> > /the/osc/adress/is/very/long/volume fff 0. -5. 5.
> > 
> > but the commands
> > $ oscsend localhost 5510 "/level" s get 
> > or
> > $ oscsend localhost 5510 "/level" f 10 
> > don't work
> > 
> > why ?
> > Thank you
> > 
> > Pierre
> 
> Bug fixed in GIT, please try again and report.
> 
> Stéphane 
> 


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] osc aliases

[pierre.leco...@gadz.org]

It's working now  ! Thank you. An other question  : is it possible to specify -xmit 2 at compilation time to fix the default transmission mode i.e. something like $  faust2jaqt mydsp.dsp -osc -xmit 2Thanks for helpPierre-- Message d'origine-- De: Stéphane Letz<l...@grame.fr>Date: dim., 10/01/2016 8:56À: Pierre Lecomte;Cc: faudiostream-users@lists.sourceforge.net;Objet :Re: [Faudiostream-users] osc aliases 
Le 10 janv. 2016 à 00:34, Pierre Lecomte <pierre.leco...@gadz.org> a écrit :

> Hello,
> I'm a bit confused with the use of osc aliases in Faust :
> Let's say i've a slider in code
> 
> hslider("volume",0,-5,5,0,0.1);
> 
> when I run
> 
> $ oscsend localhost 5510 "/*" s get
> 
> I see it but the osc adress is very long :
> 
> /the/osc/adress/is/very/long/volume fff 0. -5. 5.

Yes the parameter OSC address reflects the complete "hierarchy" of groups..etc.. that your UI code is using

> 
> So I try to use aliases :
> 
> hslider("volume[osc:/level 0 10]",0,-5,5,0,0.1);
> 
> now when I run 
> 
> $ oscsend localhost 5510 "/*" s get 
> 
> /level ffssff -5. 5. "alias" "/the/osc/adress/is/very/long/volume" 
> -5. 5.
> 
> /the/osc/adress/is/very/long/volume fff 0. -5. 5.
> 
> but the commands
> $ oscsend localhost 5510 "/level" s get 
> or
> $ oscsend localhost 5510 "/level" f 10 
> don't work
> 
> why ?
> Thank you
> 
> Pierre

Bug fixed in GIT, please try again and report.

Stéphane 
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

[Faudiostream-users] osc aliases

[Pierre Lecomte]

Hello,
I'm a bit confused with the use of osc aliases in Faust :
Let's say i've a slider in code

hslider("volume",0,-5,5,0,0.1);

when I run

$ oscsend localhost 5510 "/*" s get

I see it but the osc adress is very long :

/the/osc/adress/is/very/long/volume fff 0. -5. 5.

So I try to use aliases :

hslider("volume[osc:/level 0 10]",0,-5,5,0,0.1);

now when I run 

$ oscsend localhost 5510 "/*" s get 

/level ffssff -5. 5. "alias" "/the/osc/adress/is/very/long/volume" 
-5. 5.

/the/osc/adress/is/very/long/volume fff 0. -5. 5.

but the commands
$ oscsend localhost 5510 "/level" s get 
or
$ oscsend localhost 5510 "/level" f 10 
don't work

why ?
Thank you

Pierre

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC interface becomes unresponsive

[Ben Burdette]

You're right, it didn't compile.  I did the make clean, and then 'make'
and it got an error because SetPriority() turns out to be a private
method.  So that tells me that it didn't compile before. 

According to the header calling Start(80) should do the same thing as
SetPriority(80) so I just did that.  Everything compiled and I did a
make install but its back to its old tricks with not receiving osc
messages.  The good news is if I start the faust program first, before
the sensor scanner, it seems pretty consistent about working correctly. 

Now that I typed that, it seems to be back to working ok in either order
of startup.  According to htop the sensor scanner is currently
distributed 70-30 between the two processors.

This seems a little like there might be a race condition in OSC startup,
and when the cpu is loaded sometimes it misses its 'window of
opportunity' to complete osc setup normally.  When the CPU is not loaded
(or perhaps when the sensor scanner ends up scheduled evenly on two
processors), there's time for OSC to get set up without missing its
window.  That's pure speculation though. 

If I end up using faust inside another program which handles the OSC
messages, or I embed the faust in the sensor scanner itself, then this
will be a moot point for me.  I wonder if it would be any different for
the raspberry pi 2, with its four cores?  Right now I can't try that
because I don't have the sensor hardware set up on the pi 2.  But I'll
probably give it a whirl sometime soon. 

- Ben


On 09/07/2015 12:46 AM, Stéphane Letz wrote:
> Not sure it actually did the job….
>
> Recompiling means in this case recompiling the OSC library. To be sure 
> everything is actually done, you can do:
>
> make clean && make && sudo make install
>
> Stéphane 
>
>
> Le 6 sept. 2015 à 23:07, Ben Burdette  a écrit :
>
>> Thanks Stephane! 
>>
>> Interestingly, it turns out that if I started the faust audio program
>> first, then I could start the sensor scanner afterwards at max scan
>> rate, taking 100% of one cpu.  Just not the other way around. 
>>
>> I put your change in and did a make, with results below.  Its not
>> obvious to me that it actually compiled, but it seems like it was
>> successful, since now I can start the two programs in either order and
>> they work.  Nice! 
>>
>> make -C compiler -f Makefile.unix prefix=/usr/local
>> make[1]: Entering directory '/home/pi/faust/compiler'
>> make[1]: Nothing to be done for 'all'.
>> make[1]: Leaving directory '/home/pi/faust/compiler'
>> make -C architecture/osclib
>> make[1]: Entering directory '/home/pi/faust/architecture/osclib'
>> make[1]: Nothing to be done for 'all'.
>> make[1]: Leaving directory '/home/pi/faust/architecture/osclib'
>>
>> I don't know if this is a change that you want for the main branch, but
>> I may include it in a future pull request.  I've also added an check for
>> armv7 in faust2alsaconsole, and the corresponding gcc flags.  That seems
>> to work on bananapi and raspberry pi 2, although I don't know if the
>> compiler flags are ideal. 
>>
>> Thanks again for the help,
>>
>> Ben
>>
>>
>> On 09/06/2015 01:44 AM, Stéphane Letz wrote:
>>> You may try to hack the "OSCSetup::start" method in 
>>> "faust/src/osc/OSCSetup.cpp" and add a "SetPriority" call like:
>>>
>>> fOSCThread = new OscThread (mp, port, fErrCallback, fArg);
>>> fOSCThread ->SetPriority(80);
>>> fOSCThread->start();
>>>
>>> recompile/restart and see if it helps.
>>>
>>> Stéphane
>>>
>>>
>>> Le 6 sept. 2015 à 02:41, Ben Burdette  a écrit :
>>>
 Hey all;

 I'm trying out faust for synthesis on an instrument, which uses a
 bananapi ARM computer.  On the banana pi there's a c++ program which
 continuously scans a number of sensors, and then faust which receives
 the osc messages to trigger audio.

 When the key scanner is run full blast it maxes out one of the two
 cpus.  This causes the osc interface for faust to be unresponsive, even
 though it apparently continues with audio synthesis.  If I throttle back
 on the scanner, the osc stuff starts responding - if I restart the faust
 program. 

 At certain rates I can start the faust program first, then start the key
 scanner and it works.  But the other way around doesn't. 

 Any ideas re this?  Maybe running faust with realtime priority? 

 thanks,

 Ben



 --
 ___
 Faudiostream-users mailing list
 Faudiostream-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/faudiostream-users


--
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net

Re: [Faudiostream-users] OSC interface becomes unresponsive

[Ben Burdette]

Thanks Stephane! 

Interestingly, it turns out that if I started the faust audio program
first, then I could start the sensor scanner afterwards at max scan
rate, taking 100% of one cpu.  Just not the other way around. 

I put your change in and did a make, with results below.  Its not
obvious to me that it actually compiled, but it seems like it was
successful, since now I can start the two programs in either order and
they work.  Nice! 

make -C compiler -f Makefile.unix prefix=/usr/local
make[1]: Entering directory '/home/pi/faust/compiler'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/pi/faust/compiler'
make -C architecture/osclib
make[1]: Entering directory '/home/pi/faust/architecture/osclib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/pi/faust/architecture/osclib'

I don't know if this is a change that you want for the main branch, but
I may include it in a future pull request.  I've also added an check for
armv7 in faust2alsaconsole, and the corresponding gcc flags.  That seems
to work on bananapi and raspberry pi 2, although I don't know if the
compiler flags are ideal. 

Thanks again for the help,

Ben


On 09/06/2015 01:44 AM, Stéphane Letz wrote:
> You may try to hack the "OSCSetup::start" method in 
> "faust/src/osc/OSCSetup.cpp" and add a "SetPriority" call like:
>
> fOSCThread = new OscThread (mp, port, fErrCallback, fArg);
> fOSCThread ->SetPriority(80);
> fOSCThread->start();
>
> recompile/restart and see if it helps.
>
> Stéphane
>
>
> Le 6 sept. 2015 à 02:41, Ben Burdette  a écrit :
>
>> Hey all;
>>
>> I'm trying out faust for synthesis on an instrument, which uses a
>> bananapi ARM computer.  On the banana pi there's a c++ program which
>> continuously scans a number of sensors, and then faust which receives
>> the osc messages to trigger audio.
>>
>> When the key scanner is run full blast it maxes out one of the two
>> cpus.  This causes the osc interface for faust to be unresponsive, even
>> though it apparently continues with audio synthesis.  If I throttle back
>> on the scanner, the osc stuff starts responding - if I restart the faust
>> program. 
>>
>> At certain rates I can start the faust program first, then start the key
>> scanner and it works.  But the other way around doesn't. 
>>
>> Any ideas re this?  Maybe running faust with realtime priority? 
>>
>> thanks,
>>
>> Ben
>>
>>
>>
>> --
>> ___
>> Faudiostream-users mailing list
>> Faudiostream-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/faudiostream-users


--
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC interface becomes unresponsive

[Stéphane Letz]

You may try to hack the "OSCSetup::start" method in 
"faust/src/osc/OSCSetup.cpp" and add a "SetPriority" call like:

fOSCThread = new OscThread (mp, port, fErrCallback, fArg);
fOSCThread ->SetPriority(80);
fOSCThread->start();

recompile/restart and see if it helps.

Stéphane


Le 6 sept. 2015 à 02:41, Ben Burdette  a écrit :

> Hey all;
> 
> I'm trying out faust for synthesis on an instrument, which uses a
> bananapi ARM computer.  On the banana pi there's a c++ program which
> continuously scans a number of sensors, and then faust which receives
> the osc messages to trigger audio.
> 
> When the key scanner is run full blast it maxes out one of the two
> cpus.  This causes the osc interface for faust to be unresponsive, even
> though it apparently continues with audio synthesis.  If I throttle back
> on the scanner, the osc stuff starts responding - if I restart the faust
> program. 
> 
> At certain rates I can start the faust program first, then start the key
> scanner and it works.  But the other way around doesn't. 
> 
> Any ideas re this?  Maybe running faust with realtime priority? 
> 
> thanks,
> 
> Ben
> 
> 
> 
> --
> ___
> Faudiostream-users mailing list
> Faudiostream-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/faudiostream-users


--
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Re: [Faudiostream-users] OSC without GUI

[Yann Orlarey]

Hi,

Yes you can use : faust2jackconsole -osc foo.dsp
A user interface in Faust is not necessarily a graphical user interface. It
can be a command line, osc , http, etc. basically any implementation of
UI.h. Moreover different user interfaces can be combined.

Cheers

Yann

Le ven. 26 juin 2015 à 16:38, Julius Peters juliuspet...@gmx.net a écrit :

 For Linus-jack ...
 Is it possible to create an OSC-controlled device without using faust gui
 elements?
 As far as I understood OSC control is linked to gui elements. I.e. if you
 want a volume-control, you have to use a fader-gui-element and activate osc
 for compiling.
 If I now want a volume-control for the jack-console that runs without any
 graphical user interface - this seems not possible as I always have to use
 that fader-gui-element.
 How can I create osc-controlled devices without gui that can be run on a
 linux system without any graphical subsystem.

 Thanks for your answer
 Julius


 --
 Monitor 25 network devices or servers for free with OpManager!
 OpManager is web-based network management software that monitors
 network devices and physical  virtual servers, alerts via email  sms
 for fault. Monitor 25 devices for free with no restriction. Download now
 http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
 ___
 Faudiostream-users mailing list
 Faudiostream-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/faudiostream-users

--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

[Faudiostream-users] osc Problem

[Julius Peters]

I am using ubuntu studio 14.04.2.



Up to now I did not succeed in compiling of even a simple a .dsp file for jack and qt therefore I use the online compiler.

This works well until I mark the osc-checkbox. When I start a faust program that was compiled with the osc option it does not run.

Error message is (for the volume.dsp example, linux, jack-qt-64bit or jack-gtk-64bits):

./volume: error while loading shared libraries: libOSCFaust.so.0: cannot open shared object file: No such file or directory


What does the error message mean? I thought faust does not need shared libraries? What can I do?



Thank for the help

Julius Peters



Ps

Has anybody tried to to compile faust with jack, qt and osc on ubuntu?

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users