Setting up Bela for PureData

david

I have never unplugged any of it - here it is:
alt text

giuliomoro

david I have never unplugged any of it - here it is:

That's upside-down indeed. Remove both and plug them back in so that the text on the PCB reads upside-up.

david I have not deliberately updated the board

great

I meant that if this was a recent issue following a recent update, that could have been a cause.

david

I do not understand the first part of "also if you have a v0.3.8c or updated your board in the past couple of days: CTAG was broken for a couple of days" and I have not deliberately updated the board

david

OK I have turned the connectors through 180 degrees and it is making more sense - still trying things out ... Would the CTAG boards have been shipped with the connectors upside down?

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

Our emails crossed. I am trying my patch again ...

david

OK the channels are making sense now so I can ask my Pd question which is making a gain control with an external potentiometer which is across 1V and 3.3V from the CTAG. Is it AC coupled - I ask because the gain changes and then goes back to where it was (equivalent to 0 volts I think but I have set a gain of 0.5 on each channel so still hear it). If so, how can one use the adc~ inputs for gain (I am right connecting this one to ADC3 on the board)?
alt text

giuliomoro

the CTAG audio inputs are AC-coupled, yes. To connect pots you should add a Bela cape on top and use its analog inputs (the audio I/O won't work). The pots should show up at channels adc~ 17 through adc~ 24 when using a CTAG BEAST with Bela cape or channels adc~ 11 through adc~ 18 when using a CTAG FACE with Bela cape.

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).

« Previous Page