Setting up Bela for PureData

giuliomoro

if you are getting outputs on both boards with a single [dac~ 1] it may be that the jumpers on your two CTAG boards are not set properly (see this how to).

david Would the CTAG boards have been shipped with the connectors upside down?

I think they'd ship with those connectors loose in the box. Normally it's up to the user to connect them.

david

Thank you - I shall see whether we have a cape I can use. Really helpful Giullomoro. Incidentally, is there any sort of Bela conference or publication of projects that have been done?

bela_robert

david a Bela conference is something that we would love to do in the future but so far there has not been one. Maybe 2022 will be the year. We will hopefully be hosting at least one hackathon in the UK next year which we will announce on our mailing list closer to time.

In terms of showcasing projects built with Bela our blog is updated weekly with new projects from the wider community: https://blog.bela.io

There is now quite an archive of projects going back 5 years.

david

I now have a beast which gives a sound on 8 outputs. I want to have a volume control via an external potentiometer. Following the guidance above I found I had a Cape so I stacked it on the Beast with the pot connected to adc~ 17. On compilation I am getting this error:

Error: unable to initialise audio codec
Error: unable to initialise audio
Makefile:595: recipe for target 'runide' failed
make: *** [runide] Error 1

Do any jumpers need changing when stacking a Cape on a Beast perhaps?

giuliomoro

david Do any jumpers need changing when stacking a Cape on a Beast perhaps?

no, but make sure you rebooted after plugging in the cape if you did it "live".

Could you add --verbose to the Custom command line options and run again? that will print a lot of info that may give some more insights.

david

Sorry I am not clear about rebooting (not done this) or where to add the --verbose line as am working with Pd

david

I did not stack the cape with the power on (I assume that would be 'live') if that helps

giuliomoro

"User command line arguments" is the correct name, on the right hand side, see here:
alt text

david

Hi - this is what I get but I now do not see the error. The Pd patch in use should make a sound as the pot is ignored and it worked with the cape not connected

Building project ...
Build finished
Running project ...
Starting with period size 16 ;analog enabled
DAC level 0.000000 dB; ADC level 0.000000 dB; headphone level -6.000000 dB
Detected hardware: Bela
Hardware specified by user:
Hardware specified in belaconfig:
Hardware to be used: Bela
fifoFactor: 1
core audioFrames: 16
Project name: BeastSwitchTest
PRU memory mapped to ARM:
digital: 0xb60fc000 0xb60fc400
audio: 0xb60fd000 0xb60fd040 0xb60fd080 0xb60fd0c0
analog: 0xb60ed000 0xb60ed080 0xb60ed100 0xb60ed180
analog offset: 0xffff2000 0xffff2080 0xffff2100 0xffff2180
AuxTaskNonRT WSServer_5555 starting
AuxTaskNonRT WSClient_gui_data starting
AuxTaskNonRT WSClient_gui_control starting
Running Pd 0.48-2
AuxTaskNonRT WSServer_5432 starting
AuxTaskNonRT WSClient_scope_data starting
AuxTaskNonRT WSClient_scope_control starting
AuxTaskRT scope-trigger-task starting
Audio channels in use: 2
Analog channels in use: 8
Digital channels in use: 16
No MIDI device enabled
bonk version 1.5
fiddle version 1.1 TEST4
pique 0.1 for PD version 23
sigmund~ version 0.07
Using embedded PRU code
_________________Audio Thread!

giuliomoro

Detected hardware: Bela

means the two CTAG capes are not detected. You are probably getting the audio out of the Bela cape right now. Try rebooting and see if they get detected.

david

Sorry - how do I reboot?

giuliomoro

david there is a power button on the toolbar above the console

david

I only get audio if I remove the cape and the Pd read (adc~ 17).

david

OK so I used the
alt text
power button to shut it down which seemed to work. I then unplugged and replugged the USB. Then compiled again and it is the same - no sound. This is with the cape on top of the Beast. The Beast works but not with the cape on it. This is the Pd patch:

giuliomoro

Not sure how the +0.2 is sent to the [*~] objects. Is there a loadbang I don't see? And is the [s in [s 0.6( supposed to be there? If there is nothing like that , then the [*~] is effectively multiplying your signals by 0.

Can you run board_detect in the console at the bottom of the IDE? What does it return?

Something that could save us some troubleshooting time would be for you to update to the latest master branch as I tested the very configuration you have yesterday and it works fine for me. This at least should rule out one possible confounding factor.

david

board_detect returns 'bela'

The s is for 'set' in the message box. This Pd patch works fine without the cape attached so I was assuming it is all OK.

I am sorry but I do not understand 'to update to the latest master branch'

giuliomoro

david I am sorry but I do not understand 'to update to the latest master branch'

sorry here's a guide https://learn.bela.io/using-bela/bela-techniques/updating-bela/#updating-with-the-ide

david The s is for 'set' in the message box.

but it won't change anything in the object it is connected to, I think? Also now that I see your patch again and I see it's a [+~ 0.2] (and not a [+ 0.2] as I thought) so it doesn't need to receive any message for the patch to work.

Anyhow, the problem seems to be that for some reason your CTAG capes are not detected when the Bela cape is connected. You can run this in the console at the bottom of the IDE to force it being recognised:

echo BOARD=CtagBeastBela > /run/bela/belaconfig

(needs to be redone after each reboot).

Does it work after this ? Run it again with --verbose and post the result in case it doesn't, please.

david

OK so the sound now works but the potentiometer does not. I get very confused about the numbering - I think adc~ 17 should be used for the pin analog 1 (Pd adc~ 3) - is that right? Assuming it is nothing is happening when I turn the pot. This is the verbose output

Running project ...
Starting with period size 16 ;analog enabled
DAC level 0.000000 dB; ADC level 0.000000 dB; headphone level -6.000000 dB
Detected hardware: CtagBeastBela
Hardware specified by user:
Hardware specified in belaconfig:
Hardware to be used: CtagBeastBela
fifoFactor: 1
core audioFrames: 16
Project name: BeastSwitchTest
PRU memory mapped to ARM:
digital: 0xb6135000 0xb6135400
audio: 0xb6136000 0xb6136200 0xb6136400 0xb6136500
analog: 0xb6126000 0xb6126080 0xb6126100 0xb6126180
analog offset: 0xffff2000 0xffff2080 0xffff2100 0xffff2180
AuxTaskNonRT WSServer_5555 starting
AuxTaskNonRT WSClient_gui_data starting
AuxTaskNonRT WSClient_gui_control starting
Running Pd 0.48-2
AuxTaskNonRT WSServer_5432 starting
AuxTaskNonRT WSClient_scope_data starting
AuxTaskNonRT WSClient_scope_control starting
AuxTaskRT scope-trigger-task starting
Audio channels in use: 16
Analog channels in use: 8
Digital channels in use: 16
No MIDI device enabled
Using embedded PRU code
bonk version 1.5
fiddle version 1.1 TEST4
pique 0.1 for PD version 23
sigmund~ version 0.07
_________________Audio Thread!

giuliomoro

I think [adc~ 17] should be analog input 0.

david

Hang on - I made a Pd error by putting the adc~ 17 in a message rather than an object box. It is now working ....
I think it is OK. Thank you so much for helping out of hours like this - very much appreciated. David

« Previous Page