cheater

Hello! LC has an option of shifting the tracks by one. I'm wondering: does the controller actually "know" which track in the host each of the tracks on the controller is set to? Or is that host-side? Cheers!

Try this... http://www.ledidea.com/el_cat/117.html cheers :)

How about making your own topic for a start :P

Hey, I thought he might have actually wanted to make it the other way - modify the VCAs to support CV in, and then use that to feed the VCAs the correct automation. Your way of doing stuff seems much easier, of course. :) cheers, D.

Hey, why would you want to use P&G dj-style faders for your console? Seems like the wrong way to do things ;) You can automate your console using the motorfader module of the midibox. Note that those motorfaders are midi faders only! You will have to use the CV out module to make them work for your audio console!

Hi! I understand the problem with those sensors is that they are "disconnected" once you let go of them. So if there were a circuit which would let the core know of when we've let go of the pad, and when we're touching it, the core could know when to update the midi controller value. I thought of this, perhaps it could work... How I understand those pads (linear ones): when you're touching one end, the output is shorted with one pin (lessay A). When touching the other end, it's shorted with pin B. The output changes fluidly between pin A's and pin B's voltage. If we let go nothing is connected to the output pin. Idea: put +5V on pin A, +10V on pin B. Connect the output pin through a resistor to 0V. Now, if we touch the pad we get a voltage somewhere between +5 and +10 on the output pin. When not touching the pad, we get 0 volt and we could let the core know that it should remember the last position we have put in by touching the pad. Will this work? Of course, it would need a different module than AIN.... Is it worth ordering one of their samples to try this circuit out? Or is there some basic flaw I'm overlooking? cheers, D

I ;D

way to go atmel_fan! :D

My take on this is that stomp boxes are made for audio singals that are.. uh - unpolarised? don't know this word in english... generally the signal is different form the typical line signal. also guitars can achieve higher signal levels i believe? cheers, d. update: i listened to the mp3. it's a nice one! but notice how when the bassline goes up a few notes, it gets "nice".. the 303 would get squelchier instead! maybe the filter needs better tuned tracking. or the resonance is dropping on high notes? i like how blurby it gets at times. real nice! i think a 303 can't do that :) generally, i'd dirty up the sound by using a resonant high-pass with env follow... but i'm a freak.... speaking of env follow - try some envelope followers for generating cv, especially cutoff. it's real nice! makes the sound much more organic, "soup"-ish

it only stores and sends NOTES. those notes need to be interpreted by an external synthesizer module, which you connect with a midi cable. however, it does make nice percussive bashing sounds if thrown out the window ;)

Hello Andrew! Great job indeed. I'm sorry to hear about your personal problems :( Making progress with all that turmoil shows you're putting all your heart into this project. Way to go!

this could be nice with a wavetable for each oscillator. perhaps even a one- or two-index wavetable. You coul always add LFOs in the Midibox part of it.... Further, analog filters are successful (look at the new MB SID thingie :) ). Analog ADSRs are easy to make, too. 8) :D

I'd double-check if I were you - many synths (and most synths produced in the 90s) were actually produced with balanced 1/4" TRS.

i guess you got the glue on this one ;)

your biggest problem would be the mechanical side of things. making a beater that 1. can attain enough momentum to make a loud sound 2. can make a fluid move (for example, with drums you'd need it to jump away so it doesn't damp the drum) 3. has a correct, reliable range (so for example the stick doesn't go THROUGH the surface of the drum :P ) and 4. does it all responsively (notice that when you want to hit a drum in time, you have to start moving your arm LONG BEFORE you actually hit it *) can be really a hard task. *you might need to think of some kind of "compensation" for the lag made by the beaters. however, i do think it would be a great thing - you have a great idea. i can only imagine myself sequencing thirty hammers beating on trashcans :D!

pc speaker

hey andrew! great that you're making so much progress. yes, indeed, what i'm talking about would be a kind of slew-rate limiter, but are you sure it would be that cost-inefficient? IF the tables were stored in an "incremental" way, then you'd just need to 1. compare the "lag" factor to the increment of the next step of the waveform and 2. use the one that's smaller. however, i don't know how the internals of your code work, so i'm not going to leave the judgement of that idea to you. vca and filter: wouldn't that be done better outside? much more code-efficient ;) also, in my opinion some analog stuff would be nice in a synth like that - to keep the balance of the sound in a way. alternatively - do you think it would be possible to feed the VCOs to another pic where the filtering and perhaps other fx could be done? this could be great - this way, you could make the oscillators really powerful, i can already think of a few things you could do with wavetables :D (especially if you use two different waves as an input - basic operations like "use bigger" "use smaller" "use x samples of first and the rest from second wave" - but i digress, and i guess this last one could be done in the MIOS way you've been talking about, no?) length of waveforms: don't bother with that just yet - i'm sure there will be a way to load new wavetables on the fly :) (there must be! 8) ) cheers, and keep up the good work!

i vote moebius for moderator :D

i want it to have an integrated hdd. no, really :P

hey andrew, a very interesting and ambitious synthesizer indeed. this one surely has a lot of future! looking at the screenshot: am I right to think this filter you made is in the digital domain in some way? would you be kind enough to explain? :) some ideas from my side: 1. setting up the sample's length - go from 256 samples to 255, 254, ... (256 samples would be great from the point of view of a midi controller knob! coincidence? :) ) this would change the wave's length, so we'd have to think of a way to re-calculate the timings to keep the wave's frequencies. 2. two-dimensional, 3-dimensional or 4-dimensional WT index i guess this one would be easy? :) 3. "wave loops" - two shots of one wave, three shots of another wave, and you got a new waveform. 16 shots would be totally great. 4. "lag": when you play the wave you start out at the first sample as usually. but then, when changing to the level of the next sample, you can see if it's inside some kind of boundary: for example, if its level is 8 "units" higher. if it's less than 8 "units" higher, go to that level immediately. if it's over 8 "units" higher, go up only 8 "units" (and this is your "current" position which is output to the dac). then, do the same comparing that previous step's "current" position and the new step's entry in the rom. you could make those settings separate for the "up" and for the "down" motion. this could make the waveforms more like a "rising ramp" or "falling ramp" waveform. i'm extremely, totally curious of how this one would work out, sound-wise! perhaps like a low-pass filter? or a comb filter? what if you only lagged the "up" or "down" motion - would that only affect the odd/even harmonics of the wave? i surely wish i had labview (and most of all, knew how to operate it) to check it out myself! best regards, d.

Thanks for your work, Thorsten! :D

umm... obvious one here, but have you thought of using tri-colored leds, the second color being for each of the midi cores' midi activity? :) and seriously though, do you really need that? :P

Oh, I'm sorry, I missed your reply the first time around. I also should have been more clear. What I was talking about is setting an arbitrary BPM divider while the unit is working.

A big green bird comes flying down from the sky and takes away your newborns. Seriously though, dude, just wait. Don't be so hasty :) Just wait off. Try figuring out that stuff on your own, dang.. we both know you CAN :P

a PCB is a printed circuit board. it is what you thought it is. as for AIN and JDM - you can find the descriptions of the modules on http://ucapps.de, on the left, under "MB Hardware Platform" If you're buying the kits, just buy the PICs from SmashTV, burned. Less hassle for you.