thanks for the heads up Miller, i found it
sudo amixer cset numid=3
where is 0=auto, 1=headphones, 2= HDMI
pp
From: pd-list-boun...@iem.at [pd-list-boun...@iem.at] on behalf of Pagano,
Patrick [p...@digitalworlds.ufl.edu]
Sent: Friday, May 17, 201
I would love to find that! i assume it's not an alsa thing since the HDMI audio
is different. Hopefully someone here has already found this. I am going to
start looking around
pp
From: Miller Puckette [m...@ucsd.edu]
Sent: Friday, May 17, 2013 7:06 PM
To:
In raspian there's some way to select whether audio goes out the line out
jack or the HDMI port - I can't remember but that should be findable.
cheers
Miller
On Fri, May 17, 2013 at 10:54:19PM +, Pagano, Patrick wrote:
> Hi everyone and thank you for the help and links. I got wheezy up and ru
Hi everyone and thank you for the help and links. I got wheezy up and running
and installed pd-extended. I could not get audio out of the headphone jack on
the Pi, but it comes out of the monitor that has HDMI on it. I then of course
got greedy and over-clocked it and corrupted the file system.
Yep. Here's a diagram that shows the wiring.
Martin
On 2013-05-17 11:42, Julian Brooks wrote:
Aargh - you're right, I am confused (so very)...
So, to be clear
#define SENSOR_SELECT_PIN 11
should be
#define SENSOR_SELECT_PIN 17
After all?
It is then going to pin 11 on the 4051.
Running as roo
Aargh - you're right, I am confused (so very)...
So, to be clear
#define SENSOR_SELECT_PIN 11
should be
#define SENSOR_SELECT_PIN 17
After all?
It is then going to pin 11 on the 4051.
Running as root so need for sudo (yes I know)
As Max Romeo said:
"One step forwards, two steps backwards" :)
J
It looks like you're confused about the GPIO pin.
SENSOR_SELECT_PIN should be 17 because that's what the ARM chip calls
it. The fact that it is on pin 11 of the header is irrelevant to the
program.
The next confusing thing is that GPIO17 on pin 11 of the header connects
to pin 11 of the 4051.
I
Hey Patrick,
I guess the standard most up to date raspbian wheezy is the best place to
start.
For me what's worked best is to find a super-minimal install and then build
requirements on top of that.
With the project I'm working on atm I couldn't get my pmpd patch to even
run with the standard in
Sorry meant to attach the code (doh!).
My compadre has all the photo's on his phone so will give him a nudge now
and get back to you when I hear from him...
(hey George:)
Thanks for the testing tip - of course, seems so obvious now that you've
said it.
And I guess we can't definitely confirm th
On 2013-05-17 09:39, Julian Brooks wrote:
Hey Martin,
Can I please peck your head hopefully one last time?
Sure.
We're so close, got the hardware for the installation up and running,
box made etc etc.
Could you have a once-over of our code:
Still only seeing one sensor though all of our mu
Hey Martin,
Can I please peck your head hopefully one last time?
We're so close, got the hardware for the installation up and running, box
made etc etc.
Could you have a once-over of our code:
Still only seeing one sensor though all of our multimeter testing says
sensor 2 is fine and ready to go
Let's put it in another way:
is anybody running Pd-extended 0.42.5 on ubuntu 12.04 "precise"?
Thanks
Ingo
> Betreff: [PD] Last Ubuntu version for Pd-extended 0.42.5
>
> Hi!
>
> I'm running into a "new hardware" problem. My old system won't boot up
> anymore with the new mainboard (amd fm2 ch
On 16/05/13 23:39, Max wrote:
hi patrick
Why don't you just use millers images with vanilla or the satellite-ccrma with
pd-ext, both linked here:
https://puredata.info/docs/raspberry-pi
Both images are very close to 8GB (though much of that is empty space) ... the
CCRMA one did fit my SD card
13 matches
Mail list logo
