Seems to work in every other way... But maybe this is the issue

I would have figured, though, that they would have written the code in a way that would account for differering amounts of pins. Arduinos dont all have the same number of pins right?

after further testing.... pins 8-13 also work fine as digital outs. pins 28-37 are the problem pins. they work as digital inputs without issue, but do not work as digital outs. I've also tried it with a second teensy to rule out a bad board... same problem

UGH

The title pretty much says it all. I have set the pinmode for pins 32-37 to digital out, yet they refuse to output any voltage when I send commands. It works fine for pins 0-7 so I'm kind of baffled. is there a maximum number of output pins with pduino or firmata? Or does anyone know what else could cause this?

I was able to solve my issue by using the Firmata-Analog example script rather than the Firmata-Standard. Not sure if it will work in your case but it did for me!

I am running this on a Raspberry Pi 4 model B with 2G RAM (latest Rasbian OS installed), with a Teensy ++ 2. I installed arduino IDE and TeensyDuino, and loaded the StandardFirmata firmware to the teensy successfully.However when I open Pd-L2Ork, and load the arduino-test.pd file from the Pduino examples, nothing is working, and I get the following error on repeat:

error: gatom_list: need float or symbol

If I delete the subpatch that is above the analog input numberboxes, those errors stop. Then, I am able to use the patch to select a comport. the comport opens successfully:

[comport] opened serial line device 1 (/dev/ttyAMA0)

But then, if I try to do anything like enable an analog input or request the firmware version, nothing works, and I get the following error:

error: [comport]: Write failed for 0 bytes, error is 2

And then... after trying one thing or another a few times, pure data crashes entirely. I have searched google for a solution but am coming up short. Does anyone have any idea what might be happening?

And thanks again for taking a look guys... I can work on it from here but if anyone has any ideas I'm all ears!

test.pd

here is a super-simplified version, with a waveform display and play/write head indicator sliders.. for diagnostic purposes

my god, you're right

<facepalm>

all day i've spent on this

well sorry for wasting your time on a nonexistent issue!

well with that figured out I'll ask a more general question..... does anyone have any suggestions for a way to make this so the echoes aren't interrupted when playback speed is less than 1?

And.... just as a side question, does anyone know why the buffer would clear just because of a read or write error? I could understand a click... but clearing the whole buffer?

Is there a possibility that this isn't even the reason this is happening?

jameslo--- unfortunately that still has the same issue.... the echoes cut out when the heads pass
Can I suggest a specific scenario to test---

I am running it with the play speed at 0.7, feedback around 50%, with a live microphone on input 1. I snap my fingers near the microphone, and it begins echoing, with each echo at a slower speed and lower pitch... then every time the heads pass and the edge~ sends a bang, the echoes cease

I should also mention, I am running this on a Raspberry 4 model B with 2G RAM, using pd-L2Ork.... Trying to create a physical device with it eventually. that shouldnt effect something like this though, right?