• Lemon

    @whale-av yeah, being a portable effects processor for instruments, it needs to be very small and self-contained (in the sense that no peripherals should be sticking out like keyboards or audio interfaces) which is why I was wondering about implementing adc and dac with physical inputs and outputs into the actual thing instead of using peripherals.

    @bmd the Axoloti core looks like pretty much exactly what I was going for with hardware! Although missing an extra input and output. That said, I plan on dealing with two mono signals so perhaps I could use the single stereo input and then separate left and right into input 1 and input 2... Having a quick look at this though http://www.axoloti.com/axoloti-patcher/ suggests that it isn't as versatile as Puredata with not many objects available but maybe I'm wrong again. Definitely going to research more into this. It also sounds like it has an easier solution to my problem of not knowing how to physically implement my patch onto some hardware. Thanks for showing me that.

    Seeing as Raspberry Pi/Arduino/Puredata has a lot more support around it, plus the fact I wouldn't have to learn a whole new programming software for Axoloti, do you think I'd be able to make something very similar to the Axoloti Core using a Rasperry Pi? Or is this just overcomplicating things to the point where I might as well just learn how to use Axoloti? I'm struggling to find any appropiate ADC for the Raspberry Pi, but I'm sure there's got to be something high quality around, I mean, I find it hard to believe nobody has made a Raspberry Pi with at least 16 bit 44,1kHz audio input and output.

    Also, @whale-av made me think... If I'm not having any peripherals sticking out of my signal processor, a touchscreen might be a reasonable idea for this to simplify things and not take up space. It looks a lot more difficult to do this on Axoloti than Raspberry Pi who have their own touchscreens conveniently available, or the Odroid @alexandros mentioned which has a HDMI port. A touchscreen might not be totally necessary but now I've considered it I kinda want it.

    posted in I/O hardware diyread more
  • Lemon

    Ok, I've been looking into Raspberry Pi, Arduino and Odroid today, though my lack of hardware understanding is still leaving me a bit confused. However, from what I gather, Arduino is simply not capable of processing high quality audio (9.6kHz sample rate at best). Maybe I'm just reading things wrong. In any case, I'm looking for 24 bit, 44.1 or 48kHz sample rate audio processing.

    If I use the Raspberry Pi or Odroid as the main processor, I'm still going to need analogue inputs because I want to process audio from actual instruments, as opposed to synthesising. From what I understand, I'll need to buy a 1/4" jack as the input, connect it to something like this http://www.ti.com/product/PCM1803A/description and then somehow connect that to Rasperry Pi/Odroid. Then do basically the same thing backwards with a DAC instead of ADC for the outputs. Is that the right way of looking at this? Am I overlooking anything?

    posted in I/O hardware diyread more
  • Lemon

    I want to build a hardware device running on pd but I just don't know how to physically bridge the gap between hardware and software. I'm not even sure what kind of hardware I need, or how to map pd's inputs and outputs onto physical inputs and outputs.

    For example, if I wanted to make the most basic patch, where I just send three inputs straight into three outputs with a 100Hz hi-pass in between, how would I go about putting that into a hardware device that I could use away from my PC? and what kind of hardware would be most suitable for making a real-time audio processor (similar style to a guitar effects pedal)?

    Sorry if this is really basic, I'm kinda new to this.

    posted in I/O hardware diyread more

Internal error.

Oops! Looks like something went wrong!