While I don't remember touching the sample handling, it's been a while so things are hazy If I had to guess a theory, it might be an artefact of the linker script? My LXR is still taken apart, but let me know if I can help...
What I've been experimenting with is pieces of tape on the inside, minimally overlapping two opposite edges, so it forms a shim when the window is inserted (also from the inside). Small pieces in a/the corner/s might also work. Glue and I usually en…
That's close to what I did, I used ADC_STEPS_PER_NOTE/2 as the magic number. Except I also only saved lastInput when an input value causes a new note to be quantized, but I think that might be too much. Changes are here, or there's a .wav with some …
While pondering during the morning traffic jam, I think my changes will avoid the jumpiness but can actually make the current note a bit too sticky for certain boundary cases. Which may or may not be wanted But all I can come up with are increasing…
So I've tweaked my version a bit and it seems to be a lot less sensitive to this issue.I'll run the changes by Julian, but if anyone is feeling adventurous, drop me a line...
I'd noticed some weirdness occasionally but was never sure if it was the source (Turing), Penrose, or whatever oscillator that was the issue.
Using Shades as a CV source into Penrose (only the IN patched) I got two LEDs red and the gate permanently …
How recent is your build? I vaguely remember the value of a resistor was changed to raise the gate output voltage...
Aha, found it on muff:https://www.muffwiggler.com/forum/viewtopic.php?p=1883785#1883785
I'll give it go on the weekend.Now that you mention it, I might have noticed slewed transitions but was testing something else at the time so didn't follow up on it ">
Although I can't map inputs to outputs, the Penrose tiling looks like it could be used for generating patterns (inflating/deflating to make them more complex?) But honestly you can pretty much take anything from the articles and re-word it to sound …
@brendanclarke Can you try the looping with a sample of length 32768? From a quick read of the code I think the phase/lookup is calculated for that length, same as for the internal crash sample...That might be intentional so I'll check agai…
IIRC it gets called every 44.1kHz/32 samples and calculates the next 32 samples. I can take a look on the weekend, but off the top of my head two things I'd check are when osc->phase gets reset, and how osc->phase, osc->phaseInc, 2*PI and i…
Doh, I looked in the avr config.h...
The gcc assembly is usually ok, but I did some experiments (with the preenfm2 code) re-implementing functions in assembly and got up to 40% faster -- sometimes even more but with wrong results :x I guess first we…
Is the only sample-related UI still just the "load" entry? Maybe it would make sense to expand that to allow setting of a loopable field in the SampleInfo struct, instead of making it a per-oscillator parameter.Or just load from a "loops" directory …
@egnouf has been working on some effects in his custom firmware.
As a purely technical exercise I've been meaning to get a delay going for another project with the same CPU, but haven't gotten around to it yet since I'm bogged down with work. Hopefu…
fabs should be 1 cycle for m4, and IIRC there's no integer abs instruction so it's probably comes out about the same. But as you say it will be pretty negligable since log10 and pow will be the bottleneck by orders of magnitude...
LUT might work, ev…
I'm not sure what the default C is these days since gcc isn't strictly anything until you tell it. But I think that method of stack-allocating an array doesn't work everywhere, so it may break. But you don't really need inp/outp anyway from the look…
Two ideas:Stack overflow because you are allocating inp & outp on the stack (float inp[size] which I think is only allowed in C99)Division by 0, not sure how arm handles that (probably can be configured)
The compiler will already use shift instructions, so you probably don't have to use an intrinsic for that. But the only way to know is to check the assembly output The main gains to be had are by better grouping of memory accesses and loops (gcc se…
Well you have good goals, I'm more driven by implementation details than actual features
By where we are I mean how many cycles are being used for specific operations, not necessarily the more philosophical question The other project was the Preen…
I hope to deliver new FXs to the machine thanks to your trick ! I want as well to use the DSP math (LSR, LSL, QADD, etc...). let's see!
Let me know if/when you start with this, I've done some cortex assembler re-writes in another project but haven'…