stryd_one

timo I don't mean to be rude but you really have to start searching the forum before you post! You're coming up with lots of good ideas and questions which have been done in the past. If you search, you'll find a link to wikipedia's page on sound chips, it has all the info on all the chips of interest ... I know it's there, cause I posted it :)

My condolences.

Search. It's an unavoidable part of DIY, searching high and low for elusive parts.

timo did you search before you asked that question? :P

Might as well make a dedicated synth out of those chips ...

Jokes aside, I have the same answer for both of these polls... Depends on the job.

Option Z... Drums :)

If you can do the code for the FPGA I'll happily volunteer to make MIOS talk to it ;)

MIDI_EVNT_Send call MIOS_MIDI_BeginStream ;; branch depending on MIDI status SET_BSR MIDI_EVNT0 swapf MIDI_EVNT0, W, BANKED andlw 0x07 JUMPTABLE_2BYTES_UNSECURE ; 8 entries rgoto MIDI_EVNT_Send_8x ; Note Off rgoto MIDI_EVNT_Send_9x ; Note On rgoto MIDI_EVNT_Send_Ax ; Aftertouch rgoto MIDI_EVNT_Send_Bx ; Controller rgoto MIDI_EVNT_Send_Cx ; Program Change rgoto MIDI_EVNT_Send_Dx ; Channel Pressure rgoto MIDI_EVNT_Send_Ex ; Pitch Bend rgoto MIDI_EVNT_Send_Fx ; AOUT ;; sending three bytes: MIDI_EVNT_Send_8x ; Note Off MIDI_EVNT_Send_9x ; Note On OK we start with MIDI_EVNT0 which has the 1st byte in it. The swapf swaps the low and high nibble, which moves the channel to the 'left' and the midi message to the 'right'. For EG a Note On on channel 5 is 0x94. After the swapf, it's 0x49 The AND 0x07 then clears the channel (that's the 0 in 07) and subtracts 8 from the event type (that's the 7). After this, our example would be 1 (Note it doesn't actually subtract 8, it ANDs with 7, but it has the effect of subtracting 8 ) This effectively makes the jumptable move down 1 extra line and then run the appropriate code. If the example were a CC on channel 15, the byte would be 0xBE, which would change to 0xEB, then 0x0B and 0x03, so the jumptable causes 3 lines jumped afterwards, which puts it on rgoto MIDI_EVNT_Send_Bx ; Controller Does that make sense? You might like to take a look at the Seq and MIOS source to see how the jumptable and the MIOS_HLP_GetIndex_2bytes work.

Jumping to any of the four of these does the same thing. All of these messages are 3 byte types. You can see 2 byte types next up.... ;; sending three bytes: MIDI_EVNT_Send_8x ; Note Off MIDI_EVNT_Send_9x ; Note On MIDI_EVNT_Send_Ax ; Aftertouch MIDI_EVNT_Send_Bx ; Controller movff MIDI_EVNT0, WREG call MIOS_MIDI_TxBufferPut movff MIDI_EVNT1, WREG andlw 0x7f call MIOS_MIDI_TxBufferPut movff MIDI_EVNT_VALUE, WREG andlw 0x7f call MIOS_MIDI_TxBufferPut rgoto MIDI_EVNT_Send_End The jumptable explanation will take longer to type so thats the next post

Those VIA chipsets have always been dodgy, and I mean always, not a single one has been any good with audio stuff... I highly recommend avoiding them.

Ah I see now... I ignored the branches to SFB and meta handlers because I thought that they were internal functions only, which goes to show that it's a good idea to actually use a device before you try and figure out what it's sourcecode does (I've never even seen an MB64 heh)...and it also proves once again that assumption is the mother of all f*ckups ;D Edit: Check out mb64_meta.inc, look for MB64_META_Handler_DoubleNote for an example of how to handle different events for button in and out :)

I think you need bootstrap loader v1.2 for MIOS 1.9 no?

Well shut my mouth! Sorry for the bad info!

Yep it's not too hard. Joe, if you want to learn some ASM, I am positive that you could learn enough to do this long before the vX is ready. All you have to do it put multicolour LED's in the standard seq, and leave the 3rd leg free. When you've learned enough ASM just connect those legs to another DOUT and write the code as explained by TK :)

You probably killed the cap and the regulator mate... and quite possibly the PIC, and anything else that was in the short between that power lead and the +ve output from the PSU :\ You'll have to test them all to know...

Definitely get the standard one done. You shouldn't have to change the panel in order to add the extra LED's. I'm going to make a version of the vX that will run on the standard seq panel layout, but it's not a really high priority, just a way for people with an MBSeq to try it out and see if they want to build one. The idea is to have a button grid, something like the Doepfer Schaltwerk http://www.doepfer.de/sw.jpg . There's more info at http://www.midibox.org/dokuwiki/doku.php?id=midibox_sequencer_vx#user_interface Cheers

That or the PSU, hard to tell without knowing exactly where thatt wire landed... Good luck mate.

Hi tim' Cloning digital synths isn't really worthwhile, if you're going to build a digital synth then you're better off just making something new and if you're going to do that you'd probably want to start a synth manufacturing company ;) It's not really a DIY thing, although there is some - like the work done with the Alesis dev boards... But they're not quite on the scale of any of the synths you mentioned. Not to mention the real thing would be a damn sight cheaper and easier! :) The moogs might be possible, I'm pretty sure TK runs a moog ladder filter clone. There's a fair bit of info about midifying analog synths/fx on the wiki and forums and a lot of it is quite recent and advanced, there's a lot to read :) In time, I plan to modify some of the publicly available DIY schematics for specific control by a MIDIBox - I originally started looking at making FX, and then realised that I was basically designing a modular synth. There's a thread on this board about some drum cloning that's going on too, that should be a good source of inspiration. Cheers

http://www.midibox.org/dokuwiki/doku.php?id=questions_and_answers#what_s_the_difference_between_pots_sliders_motorfaders_and_encoders WIKIFest! Edit: Just updated.

Short answer no go Long answer you'd have to implement the minimum feature, currently it toggles between your value and zero... It'd be a global change unless you made changes to the DB, which wouldnt be too mega hard, but not so easy either. But it occurred to me, why not set the minimum on the synth? For eg: 'on' = 99 and 'off' = '23' increase cutoff on the synth to 23 and use: 'on' = 76 and 'off' = '0' ;) Edit: I never looked at the MB64(e) and I've gotta say I'm very impressed! I had no idea it had so many cool features :) Edit2: oh yeh...interesting bits (I looked these up, forgot to post them, then closed them, doh) mb64_midi.inc line 337 mb64_buttons line 246 Another way you could do it is set the value to match the value of a certain pot, so for example: Button1=120 Button2=70 Button3=90 Button4=20 You could make it so that they all reference Button1 as a minimum (instead of zero) so the max of each button is as you set it, but the min is always whatever you set button 1 to... or you could have many minimums by using neighbouring buttons values eg: Button1 On=120 Button1 Off=70 Button2 On=70 Button2 Off=90 Button3 On=90 Button3 Off=20 and so on.... You could do this by jumping through the table and getting the value of the next button and setting that instead of 0...

Sorry man I'd love to help out but in all honesty I can't be bothered trying to figure it out because I'm going to be doing it with the vX in a short while... TK's code is well commented and if you're keen enough you'd be able to do it, and hey if you screw up then just upload the app again ;)

Okey Doke I'm gonna go play "figure out what TK did in here"...Lord knows why I felt like doing this for my own entertainment! ;D

Good news, the parts aren't any more expensive down under or NZ than anywhere else. (I'm in Melbourne, it's a hop skip and jump from you) Anyway if you're really keen to do it on a PC you might take a look at some case modding sites. I know they use Parallel pins to drive HD44780 LCDs, and I've seen notes on how to do it. Word is that XP won't allow you to write direct to the port and you'll need a special API for it. Another alternative if you really want to learn about this stuff would be to use a smaller/older PIC or Atmel MCU and make a dedicated standalone box. If you go with a PIC with a UART you can adapt TK's schematics and use code from PICList, should be a piece of cake... Although you might miss having the bootloader!

http://cgi.ebay.com.au/LCD-Hitachi-LM018L-Display-2x40-Bastelware_W0QQitemZ8819156002QQcategoryZ38872QQrdZ1QQcmdZViewItem Non backlit 2x40's... Nothing special about them except the price...