**** Thank you for the example you showed me concerning accelerometer (the
one I have lost). THe problem is that I never look at smartkeyboard
functions, as I've read this :
*"We don't provide information for Windows since faust2smartkeyb will
probably not work at all on this platform (sorry)."*
Still nothing for windows users with smartkeyboards ?
I understood that what did not work on my Android was the fact that two
parameters where always linked (del and q) ... maybe because they use the
same axis ! Sorry for that mistake ...
Thanks Romain, for the link to the free account for being an Apple
developper. I'll do that.
**** Letz, to answer your question (bold) :
*Me : 4) in Faust Playground (whichi is html based) on my Laptop, you
provided the possibility to EDIT the "blocks" (instruments or effects) and
choose if I want or not use the accelerometer... But, whatever I choose, it
doesn't change anything in the code. (and I did'nt find any parameters that
could be impacter by this). Letz : Do you mean the code you can edit in
Faust Playground? (I can see the change here that I’ve done in the
accelerometer editor)*
Yes, I meant : the "acc" is coded, and I can see it. But it works only if I
activate it in the Playground UI (via the EDIT BUTTON). I thought it should
change something in the code : a kind of Toggle or Condition "if the
accelerometer is clicked OK, then do that.... ", but before and after I
clic "activate the accelerometer, on the X axis, for example", nothing
changes in the code, and I don't understand why.
I would like to understand, because, if I want to create an application
that use the accelerometer, can I also use this "condition" (which is :
"use the accelerometer, only if the used has clicked on "activate the
accelerometer"). Am I clear ?
**** Finally, do you all meet the same problem as me, when using
FaustPlayground online with a smartphone (I know I can export the
application for an Android, or iOS, but I wanter to try, in order to bypass
being an Apple developper ;-) !!!
- on Android : it works but the sound is very bad (is it just because my
phone is a cheap one ????) "scrch" sound over all over sounds (pb of
smartphone, of connexion, of ???)
- on iPhone 6 : the sound is not very good (less than my Android
smartphone, but still not usable) and at the end of the course of the
sensor, it "breaks", I mean, it sounds nearly as noise
- on iPad : test on two different ones : on 1) there is just a "charging
page of faustplayground", during about half an hour !!!!! ; on the 2)
"webassembly is not supported by your brower" whatever browser I choose (my
iOS there is a 10.3.1... and I can't upgrade it as it's too old....)
Anyway, I must choose "not to use any online solution with my pupils", and
I'm a bit disappointed, as long as Faust offers so many functionnalities
and exports ....
Virginie
Le mer. 21 nov. 2018 à 17:58, Stéphane Letz <l...@grame.fr> a écrit :
>
> > Le 20 nov. 2018 à 15:26, Virginie YK <virginie...@gmail.com> a écrit :
> >
> > Hello,
> >
> > I'd like to create programs using accelerometer on many platforms, and
> there are many things that I do not understand.
> >
> > 1) why (test on a Android smartphone) does in this exemple, only 2 out
> of 3 parameters are moving with my movement, although 3 are configured in
> the code ?
> > (it"s one of the examples you give, but I can't find it anymore in the
> new documentation. It was in the "using built-in sensors" section).
> >
> > import("stdfaust.lib");
> >
> > // parameters
> > x0 = hslider("x0",0.5,0,1,0.01) : si.smoo;
> > y0 = hslider("y0",0.5,0,1,0.01) : si.smoo;
> > y1 = hslider("y1",0,0,1,0.01) : si.smoo;
> > q = hslider("q[acc: 0 0 -10 0 10]",30,10,50,0.01) : si.smoo;
> > del = hslider("del[acc: 0 0 -10 0 10]",0.5,0.01,1,0.01) : si.smoo;
> > fb = hslider("fb[acc: 1 0 -10 0 10]",0.5,0,1,0.01) : si.smoo;
> >
> > // mapping
> > impFreq = 2 + x0*20;
> > resFreq = y0*3000+300;
> >
> > // simple echo effect
> > echo = +~(de.delay(65536,del*ma.SR)*fb);
> >
> > // putting it together
> > process = os.lf_imptrain(impFreq) : fi.resonlp(resFreq,q,1) : echo :
> ef.cubicnl(y1,0)*0.95 <: _,_;
> >
> >
> >
> it works here on an Motorola smartphone we have : the 3 sliders are
> moving.
>
> >
> >
> > 2) (test on a Android smartphone) if I change acc with gyr and choose
> good parameters, nothing happens and the sensors do not work at all.
> >
> > 3) How do you link the easy [acc: a b c d e] with the fact that you want
> to use the X, Y or Z axis ?
>
> The ‘a’ parameter [between 0 and 2] describes the X, Y or Z axis.
>
> >
> > 4) in Faust Playground (whichi is html based) on my Laptop, you provided
> the possibility to EDIT the "blocks" (instruments or effects) and choose if
> I want or not use the accelerometer... But, whatever I choose, it doesn't
> change anything in the code. (and I did'nt find any parameters that could
> be impacter by this).
>
> Do you mean the code you can edit in Faust Playground? (I can see the
> change here that I’ve done in the accelerometer editor)
>
> > Anyway, whether I choose accelerometer or not, it doesn't work on a
> laptop.So, what is the use of it, and how does it work ?
> >
> > Finally, am trying to understand how does the accelerometer parameters
> work. Am I correct, if I say these statements :
> >
> > - the accelerometer does not work on Html,
>
> You are supposed to edit the accelerometer in the HTML code, the possible
> export the DSP on Android with the « Export » button
>
>
> > so not on my laptop, although you created an interface especially for
> that
> >
> > - the accelerometer could work on iOS if I were an Apple Developper...
> so, for me, it's impossible to test it.
>
> Tis is not strictly related to accelerometer: you have to open an
> developer account on Apple to become an iOS developer, then you can
> possibly export (from Faust Playground) and compile an iOSX project
>
> >
> > - the accelerometer works on Android ... but "sometimes" it doesn't work
> ???
>
> It way be related to your smartphone model ?
> >
> > I'm sure I missed something.... could you help me ?
> > Thanks a lot.
> > Virginie K
> >
> > PS : I must thank Julius for his last answer. Sorry for not having doing
> so before ...
> > _______________________________________________
>
> Stéphane
_______________________________________________
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users
