stryd_one

Patience, xarolium :) Hey Bill should I go ahead and start on this or should I continue to wait for your code so we can build from there?

What exactly does it do? I know it's erroneous, how so? Should you have an 'else' in a 'switch' statement?

Bingo. :)

I'm no *nix guru but ... I notice the I/O have the same addresses for both ports in the screencap but not the pasted console text... You might wanna take a look in the config file for the driver and see if you can force the 2nd port to 2,1 (or whatever is required to get them on the corrrect address)

Nah no hint, just a big pet-hate of mine :-\ My apologies, I must have mis-read the date on the previous post, I thought it'd been a couple of months since slcrz sent the first email... I didn't mean to seem impatient, I just screwed up :( sorry! But yeh, it's only been a week slcrz, you're not waiting long enough.

I've got an Echo and RME card and a DDX... Personally, I'd get rid of the PC and go with the DDX. If you don't like the behry converters, use RME's. Of course this is really about budget... I mean you could go with a RME converters attached to the DDX as an interface to the MADI card (IE get both). Keep in mind that an RME Adat converter costs more than the entire DDX3216... Heck if you like you could put apogee converters on the DDX, which would be funny, cause for the price of a DDX you get a whole 2 channels of apogee conversion. So the real answer to your question is how much money do you have?

Argh! I hate when DIY projects turn vaporware and the names disappear and stop returning emails :( It's such a wasteful loss not to hand the project over to someone else....Ah well.....

OK I'll post here and paste into the wiki...gimme a while :)

I'm going to address this "What's the maximum number of...." thing on the wiki tonight. It has to be the #1 most asked question and it's not there! :P

....can't be much worse than protools Yeh I said it! ;D PS How old is this thread!? hahahaha PPS Nice choice of first post! Welcome to the board hahaha

I feel like a SID-hog :( I might reduce my order to 8 so that you guys can all get in. This is, of course, assuming that slorrin is OK with that.

I was starting to think that might be the way to go too, but I wasn't sure if you could nest arrays of structs like that. It sure looks like what I wanted though! The scary thing is that that's a cutdown version and It'll probably be bigger than that... I've had a look at the other variables that I'll need to use and I think that I'll have to cut it down to 24 tracks in order to make it fit in the available RAM even on the 4620 :( That is, until I get the SRAM interface working, but that's a little while off (read: way above my skill level) at the moment! I was thinking about including some tracks of shorter lengths (3,4,5,6,8 steps) too, but now I'm getting sidetracked... (Hey, while I'm sidetracked, the vX is getting partial polyphony! woo!) When I get a break (yeh, right) I want to test the arrays with SDCC, to find out if the limitation is to 8-bit array sizes (as in, no arrays over 256k) or 8-bit addressing to the arrays. I reeeeaaaallly hope it's the latter!

Hey, you might call yourself inexperienced, but look at me! ;) LMAO ;D

Something that shouldn't be forgotten here is the big mistake a lot of DIY audio/MIDI newbies don't realise they're making... OK sure Smash's kit is 1/2 the price... Now add on all the tools you need.... DIY is NOT the cheap option....at least, not until after at least your third of fourth project. Check it: http://www.midibox.org/dokuwiki/doku.php?id=stryd_one_preparation#hardware This is a pretty comprehensive list, and some of these things can be done without. But some can't. I'd say even the most basic toolkit will push you over the cost of a commercial device.

If you ground all the pins except for one pot or fader, does it work OK?

LOL ;D Been there before!

Sorry, when I say "not designed for" I mean that in the context of a standard MBHP/MIOS configuration. I thought that doing this might be too complex but as you say, done it C, it would be very easy - just mixing a few of the example apps would have it 90% done.

I'm sure that's do-able.... http://www.ucapps.de/midifilter.html and the examples at http://www.ucapps.de/mios_c.html would be examples....

You could alter the application to use pins not really designed for that use, but that might make things a bit difficult... I probably shouldn't have suggested it, sorry! I would recommend using J5 for the switches (J5 as DIN) and one of the four parts of a DOUTx4 module. This will give you up to eight switches and eight LEDs, but with easy upgrade path to more LED's which might be handy in the future. This post might be useful, as well as the J5 as DIN/DOUT examples on the downloads page at ucapps.de: http://www.midibox.org/forum/index.php?topic=5898.0 Using that concept, you could have preset up and preset down pedals to scroll through the 5 presets, and have 5 LED's (or maybe even a seven-segment LED digit display?) to show which preset is in use... But the easier way if you're not too familiar with the programming would be as above with a single DOUT module for the LEDs.

Gday mate, welcome to the board! If you only need 5 switches and 5 LED's, you will only require a core module, no DIN and DOUTs. You might want an LCD there for debugging purposes but you probably wouldn't need it permanently. I hope this helps stryd_one

Thanks mate, I'll take that into account. This sounds like it would suit something like my original plan, which was the ASM-style way of defining a range of memory for the entire DB (using the above example, it would be 3 parameters x 8 bits=24bits x 16 steps x 32 tracks = 1.5kB) and using pointer math... I'm still stuck on the right way to section this memory off if not using arrays though :\ I think I know what you mean... As in, create the typedef for the step structure and on startup, run an initialisation which builds the database from multiple instances of that type? Again, guys I have to thank you for the advice. I understand if this is taking too much of your time and I totally understand if you have to tell me to go away and do some more reading :)

Thought I should mention... The amounts of data wouldn't change in my case, because there would be a fixed number of parameters available. Also, I wouldn't need to search for data, but I would need to jump to read or write random parameters. I feel maybe I should be more specific when the theory gets this technical. The data would be something like this: Track 1 | |--Divider |--Direction |--Mute | |------ Step 1 | |------Note | |------Velocity | |------Length | |------ Step 2 | |------Note | |------Velocity | |------Length | ... |------ Step 16 |------Note |------Velocity |------Length Track 2 | |--Divider |--Direction |--Mute | |------ Step 1 | |------Note | |------Velocity | |------Length | |------ Step 2 | |------Note | |------Velocity | |------Length | ... ... |------ Step 16 |------Note |------Velocity |------Length ... ... | Track 32 This is just an example of the layout but doesn't contain so many parameters as a full design. There are always 32 tracks * 16 steps * 3 7-bit values available, even if the track is not currently in use, so there are always a fixed number of variables. Sometimes the seq might read the note,velocity and length from a particular step (when it plays it), sometimes it would write all three (when you program the step) but sometimes it might just write the velocity of a step, or the track divider, sometimes it might write all 16 note values but not touch the velocity on any of the steps....So it would require random access, but not really searches. I'm sorry if I made things confusing, I'm not too good with the terminolgy it seems :-\ This thread is a real education :) Please don't be too concerned if we get a bit side-tracked, I'm sure that I'm not the only one who's finding all this interesting.... But I sure am puzzled about the right way to do this. It's a good thing that I enjoy a challenge ;) Edit: Ignore that part about 7-bit values, they can be 8-bit. I just read that thing about 8-bit fields. And yes please, I'm interested in everyone's personal opinion :) Re: 1 array for each bar, I was thinking something like that might be the go. I think it matches the drawing up there too - eg: Trk1Step[n].NoteNum .Vel .Length Trk2Step[n].NoteNum .Vel .Length Re: The bankstick - I'd like to use them if I can, but if not, it'll be saving dumps to PC/MIDI recorder

Awesome news!! Good on you QBAS, that's a real achievement :)

Thanks again OG :) I really appreciate all this help. Funny, I saw binary trees yesterday on that Stanford site too: http://cslibrary.stanford.edu/110/ and thought that they sounded like they might be useful. I'll have a thorough read on it tonight. I also read about doubly-linked lists, with a pointer to the previous node as well as the next, do you know if that be suitable?

That's a good point, those interfaces are reputed to be pretty dodgy... Better yet you could try a non-USB MIDI interface - Latency problems are inherent in USB's design but fortunately usb2 is fast enough that the overtheads often make the timing issues transparent....but not always...