Got the crystal and micro back on the breadboard with the rest of the oscillator components. Bit of clipping on the low notes, but I think that's due to the voltages I'm using vs the actual design (really gotta get a 12V supply)
We'll see if I can get a simple ASR working tonight, and try to integrate the VCA, and try to get the pi outputting cv & gate signals...
Pretty wiped out, so not a lot of work tonight, but I did find an old python script on the pi to generate pwm and I was able to get it varying the duty cycle. Slap a lpf on there and add a gate output and we've got a sequencer.
Modular meetup is on Sunday and I'm determined to have something to demo, even if it's super rudimentary. We'll see how much I can get done tomorrow
Pretty wiped out, so not a lot of work tonight, but I did find an old python script on the pi to generate pwm and I was able to get it varying the duty cycle. Slap a lpf on there and add a gate output and we've got a sequencer.
Modular meetup is on Sunday and I'm determined to have something to demo, even if it's super rudimentary. We'll see how much I can get done tomorrow
So I slapped the 20MHz crystal on the ATtiny84, but it turns out that I definitely forgot to set the fuse bits for the external oscillator when I flashed the memory. So now I gotta figure out how to so that (which is good because I completely forgot how avrdude works)
Y'all, the world is sleeping on what NASA just pulled off with Voyager 1
The probe has been sending gibberish science data back to Earth, and scientists feared it was just the probe finally dying. You know, after working for 50 GODDAMN YEARS and LEAVING THE GODDAMN SOLAR SYSTEM and STILL CHURNING OUT GODDAMN DATA.
So they analyzed the gibberish and realized that in it was a total readout of EVERYTHING ON THE PROBE. Data, the programming, hardware specs and status, everything. They realized that one of the chips was malfunctioning.
So what do you do when your probe is 22 Billion km away and needs a fix? Why, you just REPROGRAM THAT ENTIRE GODDAMN THING. Told it to avoid the bad chip, store the data elsewhere.
Sent the new code on April 18th. Got a response on April 20th - yeah, it's so far away that it took that long just to transmit.
And the probe is working again.
From a programmer's perspective, that may be the most fucking impressive thing I have ever heard.
Good news! I got the Arduino spitting out an 8MHz signal and I can talk to the chip again. Now I just gotta figure out the right fuse bits...
So I slapped the 20MHz crystal on the ATtiny84, but it turns out that I definitely forgot to set the fuse bits for the external oscillator when I flashed the memory. So now I gotta figure out how to so that (which is good because I completely forgot how avrdude works)
Y'all, the world is sleeping on what NASA just pulled off with Voyager 1
The probe has been sending gibberish science data back to Earth, and scientists feared it was just the probe finally dying. You know, after working for 50 GODDAMN YEARS and LEAVING THE GODDAMN SOLAR SYSTEM and STILL CHURNING OUT GODDAMN DATA.
So they analyzed the gibberish and realized that in it was a total readout of EVERYTHING ON THE PROBE. Data, the programming, hardware specs and status, everything. They realized that one of the chips was malfunctioning.
So what do you do when your probe is 22 Billion km away and needs a fix? Why, you just REPROGRAM THAT ENTIRE GODDAMN THING. Told it to avoid the bad chip, store the data elsewhere.
Sent the new code on April 18th. Got a response on April 20th - yeah, it's so far away that it took that long just to transmit.
And the probe is working again.
From a programmer's perspective, that may be the most fucking impressive thing I have ever heard.
Okay, so this is mostly on me for not reading the directions and verifying the output, but I ended up setting the wrong fuse bits for the clock because the calculator I was using has a bunch of check boxes and ☑️=0 and ⬜=1 (terrible UI design, why would you do that??)
Good news is I think based on the current (erroneous) configuration, I can run the chip off an external clock and reset the bits. I just need to set up the Arduino to output a MHz signal
So I slapped the 20MHz crystal on the ATtiny84, but it turns out that I definitely forgot to set the fuse bits for the external oscillator when I flashed the memory. So now I gotta figure out how to so that (which is good because I completely forgot how avrdude works)
whoops, wrong blog. I should probably go to bed, but I might have an idea of where I went wrong and a possible fix
So I slapped the 20MHz crystal on the ATtiny84, but it turns out that I definitely forgot to set the fuse bits for the external oscillator when I flashed the memory. So now I gotta figure out how to so that (which is good because I completely forgot how avrdude works)
So I slapped the 20MHz crystal on the ATtiny84, but it turns out that I definitely forgot to set the fuse bits for the external oscillator when I flashed the memory. So now I gotta figure out how to so that (which is good because I completely forgot how avrdude works)
I've been toying with the idea of making a fake game ost inspired by king's field and similar titles, here's a little jingle!
Obviously a theoretical game inspired by fromsoftware has to have a moonlight greatsword-like in it, so I wrote a little thing for when you find the Lunar Greatsword in Darkblade 2! (working title)
I gave up on Drezno/Jena as a wavetable voice once I learned that Piston Honda mk3 has the same external processing capabilities while hosting its own suite of additional features. Three body leaves the learning case for it and Daiko to enter.
That being said, it's not doing anything extra special in this patch - just acting as a normal thin digital oscillator, with a little morphing on the wavetables. It has a mix out through Ikarie droning and each individual osc enveloped through Data Bender, and Daiko provides percussion through Milky Way.
The real stars of the show are Tetrapad (Tete) and Quadrax, which are both such deep modules. Tetrapad is in combo mode supplying 1 LFO modulating Daiko (though tidbit mute switches), then 3 euclidian triggers - one for each channel of Taiko (1 on a straight 1/4 and 2 on a funky one, like 13/35), and another cleverly at 1/32 to act as a clock divider for Quadrax and Data Bender. Then I learned about internal triggering on Quadrax, where you can have a channel fire after the previous one's EoR of EoC - I'm using this to effectively get EoC triggers from channels 1 and 3 without the expander (I WILL pick one up, one of these days) to control a few other parameters.
All in all, a fun learning jam, but nothing too special. It honestly reminds me of some of my old recordings, with unison on PH3 sounding a lot like Telharmonic (but with a lot more range and controllability) - but ultimately it's dominated sonically by Data Bender.
9 notes ·
View notes
Statistics
We looked inside some of the posts by
synths-and-sensibility
and here's what we found interesting.
Average Info
Notes Per Post
174K
Likes Per Post
98K
Reblog Per Post
76K
Reply Per Post
151
Time Between Posts
10 hours
Number of Posts By Type
Text
16
Photo
1
Explore Tagged Posts
Fun Fact
The Tumblr app for Google Glass was released on May 16, 2013.