#19

It should be possible, yeah. You should be able to re-purpose one of the cv inputs as the audio input. Not tried it myself though…

#20

[quote=“zebra, post:14, topic:4894”]
it’s easiest to do as much work on the PC first. rick has also made fract_math primitives and an OSC test harness for emulating DSP. i do the same kinda thing with pd externals.[/quote]not anywhere near the top of your priority list but someday I’d like to see an example of this in pd compared to the migrated code

1 Like
#21

Can’t imagine it would be super loads of work to add a pd-external build target to existing aleph modules. I probably won’t do it because pd doesn’t play nice with my tiling window manager (pulls down my system when flicking from pd to a blank desktop), so I don’t use it much! Being able to ‘make pd’ from our existing modules would be pretty cool though, as would be an aleph serial PD external. Potential for many interesting things now, having finally merged some really tricky changes dating back to April…

PD would be a much handier test environment than straight linux/jack to quickly chuck together aleph module test scenes for complex modules, because it allows to quickly hand-roll GUI for two or more module params. Whereas for my linux debug harness there’s no infrastructure for GUI elements - usually end up settling for command line oscsend incantations, hardly possible to meaningfully debug larger modules.

Really we might want a pd external target which also checks/validates module params are self-consistent. How would that work?

Maybe pd external receives param-index bangs, which trigger param-name & current-param-value bangs so you can scroll down through params with one UI element, seeing what each param is called, and current BEES 16bit value, also the displayed BEES string for that value? Haven’t done enough PD to really know if this is possible!

1 Like
#22

add a pd-external build target to existing aleph modules

yeah i am thinking about doing this… it really wouldn’t be that hard. i would generate named methods for each parameter. but i also like your idea of having some introspection methods too (param_list [int], say) and dedicated outputs for param listings. i would also generate a (sub)patcher with sliders or whatever for every parameter.

aleph serial PD external

ok that does it, i’m working on the c serial host library today.

sorry, kinda OT. but maybe not really, since i did the exact same thing the last time i made a significiantly complex audio program for teensy. regretfully, i’m not at liberty to share that code, but it’s pretty much straightforward. the only point of minor frustration was figuring out how to make the pd side c++ friendly, but there are examples of that online.

2 Likes
#23

You’ll probably be done before lunchtime, really not much to it…

1 Like
#24

I’m still beavering away at this - having fun! I’ve upgraded to using the Teensy 3.6, which has more processing power, and a whopping 256k or ram, which gives me around 3 seconds of audio at 12-bit. I’m using the PCB board I designed for my AudioFreeze project which was designed for Teensy 3.2. The 3.6 is twice the length, but by crafting a tower block of female header (well 2), I was able to raise the Teensy over the height of the ribbon power connector!

IMG_0919.JPG2448×2448 1.08 MB

With all the extra processing power the 3.6 provides I was able to create 3 separate play heads, all looping audio at different pitches which is mixed together. One plays at 1/2 speed (1 octave down), one at normal speed, and one at double speed (1 octave up). Currently the mix ratios of these are fixed as I’ve run out of knobs on my board!

Here’s a very simple demo, you can hear the acoustic sound of the guitar in this video, normally I’d want the effect to be totally wet, but it does serve to show you what the original audio is doing…

I think I’m definitely getting closer to @dspk 's video that I originally cited. Next step is to add more pots to control all the parameters, and potentially add CV control for them all. I’d like to move away from using the audio shield, as I’m not really taking advantage of the 16-bit DACs/ADCs. I’m really only using it so I can use the Teensy ADC to read the pots. I’m planning on designing a new PCB and using a PIC chip to handle all of the pots and CV interface stuff and then connect that to the Teensy via I2C, but I’ve no experience of that, so that’s a whole new adventure!

8 Likes
#25

really neat stuff! it reminds me of some of the montreal assembly pedals, which i only recently discovered. your end result is a lovely collision of notes.

3 Likes
#26

Cheers! Haven’t really learnt to ‘play’ it yet, as I’ve literally only just finished the code, hence only playing 3 notes! Will check out that pedal company…

#27

Yeah I was thinking it reminded me of mode 3 on the count to five pedal. (My favorite)

3 Likes
#28

Here’s a more up to date video of where I am with it. Still a few issues to iron out (like the background noise), but I’m pretty pleased with it so far.

I’ve written a blog post with a bit more info http://www.cutlasses.co.uk/tech/glitch-delay/

9 Likes
#31

i2c!!! :heart_eyes: plus 20 char

1 Like
#32

This is super cool and very inspiring – I make a lot of software stuff, but I’ve been wanting to get into using the Teensy more. Really exciting!

I’m particularly looking forward to how you use a pic over I2C to communicate with the Teensy – I’ve heard a lot of people using that method for other DIY projects and I’m super curious about it. Thanks for being willing to share!

1 Like
#33

Thanks! It’s nice to know I’ve inspired people, as I’m always inspired by so much on this forum.

There is already a PIC chip on this module, that handles the interface side, and reads the pots. I’m hoping this should make implementing the expander module reasonable straightforward. I’ll try to write some more about the tech side of how it works soon…

1 Like
#34

This is a very inspiring project for me too.
Just came here to say this, and that I like the music I just listened to via your website. The first two tracks were great! (I’m looking forward to listen to the other tracks when I have the time). I apologize for being off-topic though.

1 Like
#35

Really nice sounding! I’m tempted to try to make something along these lines on Er-301. I used to perform guitar improv using something similar I built in PD many years ago, but had kind of forgotten about it.

Great work!

2 Likes
#36

Oh great, glad you like the music too. One of the side motivators to doing videos like these is to get a bit more exposure, and to draw people to my site and my music. Glad it worked!

For any others interested :wink:
www.cutlasses.co.uk

4 Likes
#37

I’m particularly looking forward to how you use a pic over I2C to communicate with the Teensy – I’ve heard a lot of people using that method for other DIY projects and I’m super curious about it.

FYI this is really easy to do on Teensy. You just use the Arduino Wire interface, here’s the bit in the code that does it (from https://github.com/cutlasses/GlitchDelayV2/blob/master/GlitchDelayInterface.ino)

  // start I2C with PIC chip
  Wire.requestFrom(I2C_ADDRESS, I2C_DATA_SIZE_IN_BYTES);

Happy to help if you have any questions about getting started with Teensy. They have a very helpful forum too.

1 Like
#38

Super nice !
I guess there is a lot to learn from your code, thanks for sharing !

1 Like
#39

Noticed I hadn’t actually put the schematics up on GitHub, they are there now https://github.com/cutlasses/GlitchDelayV2/tree/master/build

#40

Thanks for sharing this, it sounds lovely! :slight_smile:

I just started working on something similar (inspired by the count-to-five previously mentionned) as a first project for my axoloti, but now I’m also thinking of getting a Teensy as they can easily be turned/used in a eurorack module as you’ve done.

I’m following this with great interest, and might try to build one sooner or later, that i2c expander is a nice idea too !

PS: I believe your’re right about the sometimes-non-powering-issue, I’ve had the same problem with a RadioMusic module in my eurorack case, and it’s definitely related to the 12V power line (it works perfectly with other racks) so I’m also curious about your workaround :wink:

1 Like