stryd_one

*bump* Sorry I can't help cause I don't DIY my PCB's... Maybe someone else has some tips?

Derr! <Ramblings of a tormented developer> Why not just pick a reference clock for each step rather than the whole track? More info: the idea here is that each step will have a multiplier/divider of it's reference clock. So let's say the clock used as a reference is the master clock, there will be 96 master clock ticks as the base reference, and that can be bitshifted four bits in either direction to give 1/16, 1/8, 1/4, 1/2, or 2*, 4*, 8* 16*. This number is then used as a counter, and when the counter overflows it empties a buffer with the note off (or whatever) data. It's just like the MBSeq. SO the point of this, is that it has to use a reference clock, but it won't make any difference in processing to have the reference set per step rather than per track, because it will always have to fetch it. :) </sleepisgood> Man that was daft. This is why you shouldn't make important decisions when you have a fever hehehe

There it is man. This is cool, very original. I can move this to the midibox of the week forum if you like, or we can leave it here and you can post a link there, whatever you want. If you'd like to keep it here you should document it in http://www.midibox.org/dokuwiki/doku.php?id=user_projects first though :) Hey, if you sit it on that can then you've got yourself a magic mushroom hehehehe

Bon Voyage man :)

Did you rob a bank or something mate? LOL :D Nice toys!

I think that mios_pin_list.txt might have an error | | | | RC5 | G | J10:SO | O | free for applications without restrictions | | | | RD4 | E | J10:SO | O | touch sensor strobe signal, used by an | | | | interrupt service routine if MIOS_SRIO | | | | active and TS_Sensitivity > 0 | | | | I think that should be more like: | | | | RC5 | G | J10:SO | O | free for applications without restrictions | | | | RD4 | E | J14 | O | touch sensor strobe signal, used by an | | | | interrupt service routine if MIOS_SRIO | | | | active and TS_Sensitivity > 0 | | | | The wiki version is fixed...

Sorry my mistake! The C version would definitely be preferable as C is MUCH easier to work with... If you look in main.h (The Header file for the main.c program) You will find the same options with explanations in the comments also: ///////////////////////////////////////////////////////////////////////////// // Global definitions ///////////////////////////////////////////////////////////////////////////// #define AIN_NUMBER_INPUTS 64 // number of used analog inputs (0..64) #define AIN_MUXED_MODE 1 // set this to 1 if AIN modules are used #define AIN_DEADBAND 7 // define deadband here (higher values reduce the effective resolution but reduce jitter) // 7 is ideal for value range 0..127 (CC events) #define NUMBER_OF_SRIO 16 // how many shift registers chained at the DIN/DOUT port (min 1, max 16) #define DIN_DEBOUNCE_VALUE 10 // 0..255 #define DIN_TS_SENSITIVITY 0 // optional touch sensor sensitivity: 0..255

Hey AC I've been using a fairly new SDCC and it is using the MULWF instructions now, so it's not such a stress :D In fact I think the 2.6.0 release does it too?

D'oh. Wikipedia has spoken: hmmm... That's a small spanner in my works. No bit type, no binary. I feel __ASM coming on ;) Edit: well it'll probably be generated and read by bitshifting so hopefully it will be transparent and I won't have to learn hex by heart, but I'll probably see so much of it during debugging that I'll learn the hex anyway ;)

I hope this page is wrong: And yet you can still bitshift. WTF?

Hmmm... Newbie Qs Use binary instead of Hex Well that was entirely uninformative. LOL Edit: I'll save you a click:

Be careful guys. There is a page around, which includes a number of incorrect pinouts, and I'm pretty sure that one is in it... I remember the separate grounds... Yeh, my first link. this one mentions this pinouts history as one that was circulating usenet. I quote: The bold text is theirs not mine. Your call :)

ahhh am I doing something wrong? should this work? unsigned long MyVar; MyVar = 0b10000000000000000000000000000001; I get: Syntax Error: token -> b10000000000000000000000000000001 I hate learning new lingo.

Shhhh! You did it because it looks great and you're a design genius ;)

I thought that it might be unintentional, that's why I mentioned it :) We've done this before remember? :) My French is atrocious!

Shouldn't you be etching boards for me? Sheesh! ;D

I disagree. I almost stepped in to defend Smash but decided to mind my business. There was a definite stand-offish tone to the post, but as you and I know, sometimes English can cause these problems if you don't speak it as a first language. Ahhhh, ya think? It doesn't work like that unfortunately. People would still bug him, I can assure you. Also, every moment that smash spends, ether providing support or providing documentation to avoid providing direct support, is a moment that he can't spend for himself, or his family, or more importantly, etching boards for me ;D I think that he provides enough already. He's drawn the line where he is comfortable. I think he already explained that. I think that your situation must be really frustrating, and I also think that you might be unintentionally directing some of that frustration towards Smash. edit: typos

LOL It's true, I have been known to say that before :)

Well funny you should mention it, cause I went to make a demo and realized that a recent addition to the design introduced a problem that could be tricky... Handling Note Off events... :( D'oh <Ramblings of a tormented developer> Here's the thing... Master clock ticks (IE MIDI F8's or a timer) increment counters until they hit their limit, and send a tick to the subclocks. The subclocks (now) have a patchbay, for routing the ticks to any number of tracks... So when a step is triggered, how do we reference the length of the note? I've got lots of ideas but at the moment, it's undecided... If you're feeling imaginative... heheheh. Keep in mind that these might not be a Note Off event, but might be something like a command to mute a track (So you can use a step in one track to play another sequence of notes) A happy answer to this post would be good, then I can reverse-lookup the patchbay routings... of course then I have to figure out which subclock to use as a reference if there are more than one routed to the track, or finding a quick way to calculate a useful reference from a number of different step lengths...(Edit: that's not gonna happen. Thx AC :) ) Because of that, I considered just allowing to assign a subclock for each track to use as a reference, however that could mean dropped notes if that subclock is ticking slower than the clock which triggers the note-ons... And then what should the default be? I don't want to interrupt the flow of using the seq to question the operator if they want to set this subclock to be the reference for lengths, every time they change the subclock routings - and can't, when the patchbay is altered by an internal function. I think what I'll do is refer to the master clock by default, and allow the setting to be changed to reference any of the subclocks Argh! This whole modular design has turned out to introduce exponential levels of difficulty with every feature ::) This post is just a glimpse of it... </selfinflicted> While I'm asking for peeps to make a request on the implementation of note off (etc) events, I should also ask... What kind of control functions would you like to have? There are obvious things like sending notes and CC's to the outputs, or wierd sh!t like the abovementioned muting/unmuting tracks, changing notes on other tracks, changing track dividers, changing subclock routing to tracks, changing the current step on a track, etc etc etc... If you think of anything handy shout out :)

Not quite an answer but... Floating point math be mightily slow. Also, you should have a totalPossibleValues of 128, don't forget we're counting from zero. Aaaanyway... http://www.ucapps.de/mios_c_send_range.html Do it the easy way, steal it from TK hahahaha Post with an explanation.

Very nice :) Just needs labels... Although I'm guessing that you know it by heart. Are those LED bar graphs working as LEDrings? I love it! :D

If you start it at measure 3 or 4, does the track play from step 1 or step 17?

Saves an optocoupler and midi plug and cable :)

Re: PIC18F4620: new silicon revision B4 Use the search, luke. Click SEARCH, Search for : EUSART by user: TK Your bug is about 9bit mode, that's not us.

Hi beowulf. I don't want to be a downer, but..... did you know that these have already been done? You can download the brd files, open with Eagle Light, and print them out... For Eg mbhp_core_v3.brd As word .doc files do not always print the same size, word docs are not a suitable format to save these either :( (and they can sometimes transmit viruses) Anyway, it's nice of you to make this effort for us all. I hope this helps!