stryd_one

Absolutely killer!!! A huge congratulations to you on this TK, truly impressive in every way. You're an inspiration to us all.

RL sux. midibox FTW.

Ahhh resynthesis, one of my favourite toys! You forgot the partials' amplitude envelopes, and that's the bit you really want to know ;) That's why most wave editors do 3D FFT... Consider a textual representation of an envelope with some dozens of breakpoints, and maybe it won't be so 'digestible' any more... Guess it depends on whether you're digesting/parsing it by eye or by software or what... What's the plan exactly? Anyway to answer your question, 5 minutes in google got me these hints: max and pd and processing and matlab and octave do it... audacity does it... http://www.kvraudio.com/forum/printview.php?t=210852&start=0 I'm sure a few more minutes will get you something really useful :)

Hehehe no need for apologies man. It's good to feel confident, and if we can help...... Can't wait to see it running :)

Does it do this with the default configuration, or only with your ini file?

Check the datasheet and wire them correctly ;) Typically, yes - but if you get it wrong, you will fry things, so... see the answer to question #1 :)

Wilba' is the best source around ATM, but..... use the search on the wiki. You'd have found wilba's page, and this one: http://www.midibox.org/dokuwiki/doku.php?id=soundcards_with_ymf262_and_or_yac512_chips

Hmmmm, the 'black blocks' initialisation doesn't seem right, what's with all the missing blocks? Is that normal for that LCD? ... Doesn't look good :( (Perhaps a dead LCD...)

Nah, that's part of MIOS, and not the app - nothing you need to worry about. Look to the application files - in this case, its midio_presets.inc Again this is fairly easy to find if you just search through the application files (using grep or your IDE or similar) - I found it quickly in app_defines.h In the vast majority of cases (ie, unless you are doing something crazy/stupid/weird) MIOS can be ignored and you only need to worry about the app itself. Hopefully that info will save you from searching through so many files :)

I know this probably isn't the answer you were hoping for, but I think it would be much faster to re-do the ini file from scratch, than to try to recreate it from the chip and edit it :( Sorry mate.... FWIW, I tend to email files like these to my gmail account - makes for a nice offsite backup, and with such small files it's really easy.

Hah, they can't even spell unprosperous right.

I think lyle's just saying, that you'll need to use the SRIO for your project... but yeh, it's 'legal' to manipulate PIC pins directly, if you are careful - Take a look at the mios_pin_list to see how pins are assigned... Also search for J5_IO as an example. It's a MIOS module (software, not a MBHP module) that wraps all the ASM lyle already described, in convenient function calls to use the 8 pins of J5, usually used for the analog inputs - it also disables those analog ins, and if you wanted to do similar with other pins, you would need to disable any associated drivers. For example, looking at the pin list you can see that if you wanted to use RC0 (PORT C pin 0) then it would conflict with the AIN MUX. You can disable that driver by calling MIOS_AIN_UnMuxed, but of course there is the trade-off that now you may only use 8 pots connected directly to the core, and no AINx modules. Anyway, blah blah, that's just for educational purposes - in most cases, J5_IO would do the job.

Good news :) The reason I ask is, that you can't really use a PC to test timing, because the timers on them that would be used as the time reference...well... suck. Likewise they can't be trusted to generate the signals you're testing... fortunately we have midiboxes for that ;) Probably the easiest way to start a test, would be to push midi clock from a midibox, across the xbee link, and use your scope to measure the serial output pin on the receiving-end xbee. Because midi clocks are 0xf8, you should get a fairly decent square-ish pulse out of it every time a clock message is rec'd. Then I guess take a walk around with them and see how it fares...

That's pretty much right... In fact, the mainloop is in MIOS itself, and not the application. You don't really need to be concerned with MIOS, it 'just works' (like when writing an app for windows, you don't need to know about window's source code). Instead, the functionality you need is exposed via a handful of functions, which are the ones you can see in the application's main.inc (or main.asm / main.c in the skeletons, etc). The comments in those files explain what those hooks do; and you can combine them with the stuff from the function reference to make up your own app - or modification of an existing app of course :)

Welcome aboard urgon :) With some programming it could be possible to add an encoder for selecting preset banks, and a display to show the selected bank... I hope you know some PIC ASM :) I seem to remember seeing a layout for LEDrings posted not too long ago, perhaps it was by sasha? Try the search engine and see how you go... HTH!

Had a quick look at the specs... seems like a pair of unidirectional serial busses... If I were doing this, I'd be making the DCB-facing hardware a small PIC, and use it as IIC_MIDI, so the whole DCB thing would be transparent to the midibox core.

Nice work :)

Dr Seuss

Wheee I can haz cupcake? Boom bap sprinklez?

Welcome aboard LoneStar :) Try @Toggle in the ini file :)

Great work noofny :)

You didn't mention what app it is, I assume midio128 as we aren't in the HUI ar ASM forum? Regardless the answer is the same... Sorry mate, I don't believe there is.... I can think of a couple of ways at least, to find out what settings are on the box already, by reading from the PIC/banksticks - in case you weren't really sure how it was set up (eg fixing a box for a friend, or a friend set it up for you originally, etc)... but I can't think of any way to get that information into the original ini file format automatically :( Is this just for "because it would be nice to have those files back" or are you changing hardware and need to re-upload or?... I'm not sure whether I could maybe give you some more useful advice, than this verbose "no" :(

-> "MIDIbox SID" Pedantic == good :)

Sounds like a short between RS and something else....