Hello Stéphane,
Thank you for your answer. Yes, the default plugin setting works but the
standalone flag causes errors.
If I use the -standalone flag I see many errors in Projucer (5.0) that were not
there in 4.3.1
The first one:
error: : error reading
'/Users/jc/juce/examples/karplus32/JuceLibraryCode/include_juce_audio_basics.mm'
The file generated with the standalone flag builds fine in Projucer 4.3.1 but
not 5.0
jc
> On Apr 28, 2017, at 11:12 AM, Stéphane Letz <l...@grame.fr> wrote:
>
>
>> Le 28 avr. 2017 à 17:31, Juan Cristóbal Cerrillo <jccerri...@gmail.com
>> <mailto:jccerri...@gmail.com>> a écrit :
>>
>> Hello everyone,
>>
>> It seems that the fast2juce script longer works with juice 5.0 though it
>> worked fine with 4.3.1, or am I doing something wrong?
>
> Just compiled here on OS X and working (even it the new UI look is ugly…).
> What exact problem do you see?
>
> <Capture d’écran 2017-04-28 à 18.07.34.png>
>
>>
>> On another note, could someone offer guidance on how I could incorporate a
>> midi input selector to a faustApplication created with fast2juce?
>> I’m looking to incorporate something something similar to the juce Handling
>> Midi Events Tutorial, so that one can select the midi input in the
>> application.
>
> In plugin mode (the default), use the « Standalone Plugin » target, then
> Audio and MIDI selector can be opened using the « options » button in the
> running application.
>>
>> Any help would be greatly appreciated!
>>
>> All best,
>>
>> jc
>>
>
> Stéphane
------------------------------------------------------------------------------
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
