Yeah, a benchmarking patch sounds quite useful for a lot of things.
About the ARM naming scheme there are two numbering schemes for ARM CPUs.
First, you'll see ARMv4, ARMv5, ARMv5TE, ARMv6, ARMv7, etc. Those are the
various instruction sets. Then you'll see things like ARM9, ARM11, ARM Corte
This reminds me - I don't know where to go for information on how fast
PD runs on various processors. For example, how does Raspberry Pi match
up against Beagleboard? (I believe RP is ARM v6 and BB is ARM v7 so it's
bpossible BB runs circles around RP - but the ARM model and instruction set
nami
Thanks!
we eventually got it working with a griffin iMic usb device, thanks for the tip.
Having some performance issues with Pd so going to try PDa now.
d
On 5 March 2012 02:09, Miller Puckette wrote:
> Could be a portability problem in Pd's audio I/O code or (more likely
> I think) some kind
Could be a portability problem in Pd's audio I/O code or (more likely
I think) some kind of limitation in the audio driver itself. Perhaps audio
input only works in one channel and Pd is tring to use it in stereo? It
migth help to use an external USB audio device if that's practical.
cheers
Mill
Hi all,
We're running Pd 0.43 on a Gumstix Overo Airstorm with Cortex A8
architecture, using Linaro 12.02 distribution (which is based on
Ubuntu 11.10 )
Pd seems to be working but audio input and output is displaying
strange behaviours and processing artifacts.
Simple osc~ objects play their tones
