moebius

Hi, It's a clock noise, alright? doc? Strange.. I didn't figure out from the pics, how those two large supporting legs, connected to are connected? To the ground with separate wire, or getting ground connection from the case? A possible ground loop here :) Anyway - What a beauty.. Of my god ect. ect. ect. I love your design, Bye, Moebius

Hi, It's a clock noise, alright? doc? Strange.. I didn't figure out from the pics, how those two large supporting legs, connected to are connected? To the ground with separate wire, or getting ground connection from the case? A possible ground loop here :) Anyway - What a beauty.. Of my god ect. ect. ect. I love your design, Bye, Moebius

Sorry.. >:( (for being silly) If it compiles cleanly with default options by only using MPASMWIN I could give it a try.. (Little did I know, when I ripped Internet Explorer out of my system. For some probably very smart reason, Microchips MPLAB IDE is dependant on IE, so it quit working). So HEX will do, and you have got PERL?! setup_mbseq_vintage.asm - setup file for "Vintage", pot based MBSeq setup_mbseq_v2.asm - setup file for "new" encoder based MBSeq main.asm is common resource file for sequencer functions, "include"'d by both setups. Bye, Moebius edit: "The third setup "main.asm" is similar to setup_mbseq_v2.asm, but different encoders types are specified - this file matches with my own hardware."

Sorry.. >:( (for being silly) If it compiles cleanly with default options by only using MPASMWIN I could give it a try.. (Little did I know, when I ripped Internet Explorer out of my system. For some probably very smart reason, Microchips MPLAB IDE is dependant on IE, so it quit working). So HEX will do, and you have got PERL?! setup_mbseq_vintage.asm - setup file for "Vintage", pot based MBSeq setup_mbseq_v2.asm - setup file for "new" encoder based MBSeq main.asm is common resource file for sequencer functions, "include"'d by both setups. Bye, Moebius edit: "The third setup "main.asm" is similar to setup_mbseq_v2.asm, but different encoders types are specified - this file matches with my own hardware."

Yup ;) From the description given, it seems that edwardus uses another design with Atmel uC (what a shame ;)).. Bye, Moebius

Yup ;) From the description given, it seems that edwardus uses another design with Atmel uC (what a shame ;)).. Bye, Moebius

Simply: DOPE

Why doncha try a less messy Broccoli18? So, You haven't got a elco for a by pass cap, and that resistor.. you might have to calculate that.. SHIT ;) Or, maybe you could try to fry some of those samples??! Bye, Moebius

So, Did you fu*k it up.. or is it runnin'? Sorry, ask TK.. We'll be waiting. Bye, Moebius

So, Did you fu*k it up.. or is it runnin'? Sorry, ask TK.. We'll be waiting. Bye, Moebius

No such luck.. It's basicly a level converter and COM and midi have different baud rates. But there are many serial to midi DIY interface designs to be found on the Internet.. Bye, Moebius

No such luck.. It's basicly a level converter and COM and midi have different baud rates. But there are many serial to midi DIY interface designs to be found on the Internet.. Bye, Moebius

Well, and I wasn't aware of change_id soft.. :-[ Thanks, nomadic Whale.. I think that Interface ID flag sets "default" interface. As MIOS handles "low level" midi I/O it does it as it's told to (default speed), but with menu/LCD driven applications, there's MIDI config. page, where you can choose what interface you're using. Anyway, when switching between actual midi I/O and COM, don't you have to re-configure your hardware anyway?! I don't think that going thru some menu pages isn't that big job to do.. ;) Bye, Moebius

Well, and I wasn't aware of change_id soft.. :-[ Thanks, nomadic Whale.. I think that Interface ID flag sets "default" interface. As MIOS handles "low level" midi I/O it does it as it's told to (default speed), but with menu/LCD driven applications, there's MIDI config. page, where you can choose what interface you're using. Anyway, when switching between actual midi I/O and COM, don't you have to re-configure your hardware anyway?! I don't think that going thru some menu pages isn't that big job to do.. ;) Bye, Moebius

Hi. This I'm not sure of. (Note to myself: MUST LEARN MIOS).. But I'm sure it won't affect performance anyway (?!) ;) Bye, Moebius

Hi. This I'm not sure of. (Note to myself: MUST LEARN MIOS).. But I'm sure it won't affect performance anyway (?!) ;) Bye, Moebius

Hi, No no no! There might be buffer circuit for piezos, but where's the software?! I would still recommend tried and tested desing by Admir: http://www.midibox.org/edrum/ Bye, Moebius (p.s .You can view .brd files with free version of a PCB-CAD Eagle: www.cadsoft.de)

Hi, No no no! There might be buffer circuit for piezos, but where's the software?! I would still recommend tried and tested desing by Admir: http://www.midibox.org/edrum/ Bye, Moebius (p.s .You can view .brd files with free version of a PCB-CAD Eagle: www.cadsoft.de)

Hi, It's a fast periodic DC pulse. Your multimeter doesn't have fast enough sample rate to capture that, but it might still show something, like variable results. Digital signals, datalines ect. are easily checked for apparent faults with a simple (and cheap) logic probe. It should be able to distinguish between logic 1 / 0 and pulse trains.. Hmm.. It seems that those shift registers corrupt the clock line. Unplug those, and check for shorts. Bye, Moebius

Hi, Check, calculate new placements in DIN chain and modify: mios_tables.inc (DIN_ENTRY = buttons, ENC_ENTRY = encoders) setup_mbseqv2.asm (same, plus DEFAULT_GP_DIN_SR* = GP buttons) and main.asm (for DEFAULT_GP_DIN_SR* = GP buttons) I hope I'm correct ;) (and you can make it) Bye, Moebius

Hi, Check, calculate new placements in DIN chain and modify: mios_tables.inc (DIN_ENTRY = buttons, ENC_ENTRY = encoders) setup_mbseqv2.asm (same, plus DEFAULT_GP_DIN_SR* = GP buttons) and main.asm (for DEFAULT_GP_DIN_SR* = GP buttons) I hope I'm correct ;) (and you can make it) Bye, Moebius

Hi, I think that doc would be better to answer this, but anyway: If your regulator can't supply enough power to the circuit, it overheats - and thermal protection kicks in, it starts to limit current, by droping output voltage. (remember your U/R=I) This probably leads to strange behaviour, random resets ect. If your transformer is underrated, then everything might seem like normal, as regulator can suck enough power out of it anyway, BUT transformer heats up, let's say more than in normal use.. (Or it might even have a fuse that blows.. but usually no thermal protection.) This shortens expected "life" of the transformer and in extreme cases can lead to fire hazard.. Bye, Moebius

Hi, I think that doc would be better to answer this, but anyway: If your regulator can't supply enough power to the circuit, it overheats - and thermal protection kicks in, it starts to limit current, by droping output voltage. (remember your U/R=I) This probably leads to strange behaviour, random resets ect. If your transformer is underrated, then everything might seem like normal, as regulator can suck enough power out of it anyway, BUT transformer heats up, let's say more than in normal use.. (Or it might even have a fuse that blows.. but usually no thermal protection.) This shortens expected "life" of the transformer and in extreme cases can lead to fire hazard.. Bye, Moebius

Hi, remix_me This link was posted a while ago to the forum: http://www.mars.dti.ne.jp/~ogura/e_hobby/midirec.html Site is in Japanese, but It's clear, that it's a really simple "midi recorder".. I'm not sure, if you can stop it, and then continue recording, for multiple takes.. but anyway.. Bye, Moebius

Hi, This means building 4 MB_USB modules and using commercial USB Hub hardware to connect those to the computers USB port. But, as doc said It's not the cheaper way than buying a multiport midi interface and MB_USB module isn't exactly for the beginners, as Cypress USB chip is surface mounted component.. Bye, Moebius