Feature/bela #7
Feature/bela #7
Conversation
bela/render.cpp
Outdated
| * | ||
| * render.cpp | ||
| * | ||
| * This exemple sends "Hello World !" when it starts and decodes it at the same |
| #include <Bela.h> | ||
| #include <stdlib.h> | ||
| #include <string.h> | ||
| #include <string> |
There was a problem hiding this comment.
The second one is the C++ one to get the std::string type
bela/README.md
Outdated
|
|
||
| Use the connector shipped with Bela to connect a speaker to the LEFT OUT connector. | ||
|
|
||
| This is an example of how the montage should look like : |
There was a problem hiding this comment.
Is montage the right word here?
There was a problem hiding this comment.
I couldn't find any other word X) Any idea ?
There was a problem hiding this comment.
I thought a montage was a selection of pictures or footage cut together with some epic music. Probably something more boring like, see the image below for an example set up
| /* | ||
| * Start the auxiliary tasks | ||
| */ | ||
| if ((chirp_auxiliary_input_task = Bela_createAuxiliaryTask (&chirp_process_input_audio, 80, "chirp-auxiliary-input-task", connect)) == NULL) return false; |
There was a problem hiding this comment.
Should the input task have the same priority as output?
There was a problem hiding this comment.
❓ They have the same priority
There was a problem hiding this comment.
Just curious, I would have thought that maybe the output processing should have a higher priority to avoid any audio glitches.
There was a problem hiding this comment.
It's okay, the environment is already made for optimised audio processing, and 80 of 99 is already a high enough priority, didn't have any glitches 😄
|
By the way, I think It'll be good for you to test it to be sure I didn't forget something obvious in the readme @joextodd |
|
@LittleMonsterFr you can include the |
|
And add the empty |
|
@LittleMonsterFr you can also commit the |
What : New example - Chirp used with Bela
Why : To give more content