[stryd_one]

Ahh yeh, it's kinda hardcoded...

You could move it around a bit though. The idea is that the buttons have to be in one series. By default it's button 1-30, and depending on which button it is, it jumps to the correct menu using the table below:

;; --------------------------------------------------------------------------
;;  This function is called by MIOS when an button has been toggled
;;  Input:
;;     o Button number in WREG and MIOS_PARAMETER1

USER_DIN_NotifyToggle
	movwf	TMP1			; save number of button in TMP1

.........snip........

	;; branch depending on pressed button
	movf	TMP1, W
	JUMPTABLE_2BYTES 30	; max. 30 entries
	rgoto	MMD_BUTTON_Delay0Down
	rgoto	MMD_BUTTON_Delay0Up

So if you wanted the encoders attached first, then maybe the first button might be on pin 8, then pin 9, pin 10, etc until pin 38, you could just subtract the 8 from the TMP1 variable before the table jump, and it'll work OK.

What'd you have in mind?

[dcer10]

Hey M8,

Sorry for the long delay! excuse the bad pun :)

Im not sure on what I want to do, looking for some suggestions from someone who knows more about it or has used it.

Basically I cant imagine how the interface would normally work ie is there a menu encoder, buttons under the screen like in the sid, would/could you use the 30 buttons and 8 encoders or whatever (and would that make sense??). How would it be laid out on a panel ie would 3 rows of 10 buttons and a screen be a good layout or are the buttons grouped by function etc??

I really want to buildone of these and ive got all the hardware ready, but I dont want to build a case etc not knowing how it would work.....

Obviously looking at the code hasnt revealed inspiration for a layout for me...Suggestions???

Cheers,

John

[dcer10]

Has anyone got any suggestions on the panel layout for this one? Ive got all the hardware ready to go but im not too keen on drilling into a box yet until I have an idea of the layout, which isnt clear to me from the software.

What I need to know is if there are particular menu controls (ie buttons for screen, menu encoder etc) and if there are logical groupings of the 30 buttons, and if the 8 encoders would replace or compliment the 30 buttons.

Anyone built one? If so got any suggestions, pictures, FPD files?

Thanks,

John

[dcer10]

Ok then, ive gone out on a limb and made a panel design for people to comment on as to if it would be enough to control all aspects of the MMD. Does anyone know what the 8 encoders would control and if they are needed to be added? This design is using all buttons only so all the holes are for momentary switches. I would have liked to add LED's too but im not sure as to what they may indicate other than that a button was pressed. It is also for a 20x2 LCD,

Would this configuation do? Any suggestions?

Cheers,

John

PS: This design was measured up for this enclosure (can be ordered easily in Australia and maybe elsewhere) http://www.jaycar.co...x=&SUBCATID=644

Attached File(s)

•  MMD_Prototype.zip (1.1K)
  Number of downloads: 6
•  MMD_Panel_Prototype.gif (8.88K)
  Number of downloads: 45

[dcer10]

Hi All,

Just incase anyone was interested I thought I'd post a couple of pics of the MMD so far. Not sure if its going to work, but it powers up and the screen comes on. Still have to cut the holes for the midi out and thru and wire up all the front panel buttons to the DIN board.

All the best,

John

Attached File(s)

•  MMD_1.jpg (26.97K)
  Number of downloads: 15
•  MMD_2.jpg (27.72K)
  Number of downloads: 32
•  MMD_3.jpg (38.13K)
  Number of downloads: 19
•  MMD_4.jpg (38.05K)
  Number of downloads: 24

[dcer10]

Im a bit lost as to where to actually connect up the buttons to now.. Is there anything like:

http://www.ucapps.de...dinx4_16enc.pdf

But for the buttons to connect to the DIN on this project, or at least somewhere that they are listed in the code?? I couldnt see anything logically telling me that button x is on SR x pin x.

Can someone help please?

Thanks!

John

[stryd_one]

This is related to my post from before about them being in series, button 1 is the first pin on the first SR, and count up from there :)

[dcer10]

Hey M8,

Thanks for the response, I dont think I was clear enough. I need some way to know what button 1 is ie:

SR  Pin  Name

1    1    BPM up
1    2    BPM down
1    3    Channel config up
1    4    Channel config down

etc etc (obvioulsy these ones arent right)..

Have I missed an area in the config files showing which pins go to which functions?

Any suggestions would be cool :)

Thanks,

John

[stryd_one]

Sorry I should explain better :)

The juice is in mmd_din.inc, right at the top. It uses TK's jumptable macro to jump through the code by X lines, where X is the number of the button which triggered the DIN_Notify.

In the code below, button number is in TMP1. It gets moved to W.
That value is used to increase the top of stack counter, which is effectively skipping X lines of code. (Note it is limited to jump 30 lines to avoid going too far)

;; branch depending on pressed button
	movf	TMP1, W
	JUMPTABLE_2BYTES 30	; max. 30 entries
	rgoto	MMD_BUTTON_Delay0Down
	rgoto	MMD_BUTTON_Delay0Up
	rgoto	MMD_BUTTON_Delay1Down
	rgoto	MMD_BUTTON_Delay1Up
	rgoto	MMD_BUTTON_Delay2Down
	rgoto	MMD_BUTTON_Delay2Up
	rgoto	MMD_BUTTON_Delay3Down
	rgoto	MMD_BUTTON_Delay3Up
	rgoto	MMD_BUTTON_Transp0Down
	rgoto	MMD_BUTTON_Transp0Up
	rgoto	MMD_BUTTON_Transp1Down
	rgoto	MMD_BUTTON_Transp1Up
	rgoto	MMD_BUTTON_Transp2Down
	rgoto	MMD_BUTTON_Transp2Up
	rgoto	MMD_BUTTON_Transp3Down
	rgoto	MMD_BUTTON_Transp3Up
	rgoto	MMD_BUTTON_Chn0Down
	rgoto	MMD_BUTTON_Chn0Up
	rgoto	MMD_BUTTON_Chn1Down
	rgoto	MMD_BUTTON_Chn1Up
	rgoto	MMD_BUTTON_Chn2Down
	rgoto	MMD_BUTTON_Chn2Up
	rgoto	MMD_BUTTON_Chn3Down
	rgoto	MMD_BUTTON_Chn3Up
	rgoto	MMD_BUTTON_ChnInDown
	rgoto	MMD_BUTTON_ChnInUp
	rgoto	MMD_BUTTON_ChnCfgDown
	rgoto	MMD_BUTTON_ChnCfgUp
	rgoto	MMD_BUTTON_BPMDown
	rgoto	MMD_BUTTON_BPMUp

So in English:

Function  	SR	Pin
Delay0Down	1	0
Delay0Up  	1	1
Delay1Down	1	2
Delay1Up  	1	3
Delay2Down	1	4
Delay2Up  	1	5
Delay3Down	1	6
Delay3Up  	1	7
Transp0Down	2	0
Transp0Up  	2	1
Transp1Down	2	2
Transp1Up	2	3
Transp2Down	2	4
Transp2Up	2	5
Transp3Down	2	6
Transp3Up	2	7
Chn0Down	3	0
Chn0Up  	3	1
Chn1Down	3	2
Chn1Up  	3	3
Chn2Down	3	4
Chn2Up  	3	5
Chn3Down	3	6
Chn3Up  	3	7
ChnInDown	4	0
ChnInUp 	4	1
ChnCfgDown	4	2
ChnCfgUp	4	3
BPMDown 	4	4
BPMUp   	4	5

Of course you could rearrange that order as required... If you want to wire it up differently just say the word and I'll post code :)

[dcer10]

Thanks M8!

Worked a charm. All the buttons etc are working fine now  ;D

My only real problem now is that the midi out wont work. Maybe its the wiring. The LTC lights up on midi in, but nothing on the out ever flashes, nor do the signals make it out of the box on out1 or out2.

So close to finally testing this thing out!!!

All the best,

John

[ultra]

i could possibly work that into my sequencer design.  hmmmmmmmmmmmmmmmmm.  does anybody consider this delay to be good enough to be permanently incorporated into a bigger, more expensive project?  i'm making a seq in a 19" rack, and at 3U height and even with the led matrix, it seems i'll have some space left over.  does this repeat any information sent to it?

on a side note, has anybody coded randomization into their midibox gear?

[dcer10]

Hiya!

Ill let you know my results as soon as I get my midi out working! It could be made smaller I think by using encoders if you needed it to. Theres nothing in the sequencer that will do the delays like this will. In fact I think building it into the same case would be a great idea and having one IIC dedicated to the delay out or switched between it and another output.

Ive added an LTC into mine for a second midi out for further layering of sounds from another source using the same delays.

On the down side it doesn't seem to have program memory so its a "jamming" tool only from what I can see.

All the best,

John

[stryd_one]

Quote

on a side note, has anybody coded randomization into their midibox gear?

AC and I have borrowed TK's code :)

Hey John did you use the right ID for LTC out? I'd have thought that the midi out would've given you trouble when uploading the app?

[dcer10]

Hiya Stryd_One

I think Ive done something like that wrong as I can see that the midi in is working and the LTC lights up ok, but the midi out isnt working, and also the midi out light isnt showing anything either. Checked and the midi wires are on ok in the right order, when Ive used the LTC board before I dont recall doing anything special to set it up, what have I missed and does it sound like the cause of my problem? Im getting no midi out from the core, no midi out or thru from the LTC, only in.

If thats not the problem, whats the most likey next thing? I do recall seeing the midi out work and the out light go on when testing with the Midi IO 128 test application. Maybe something got bumped since then??

Just curious... could this project be further enchanced to have program memory and sync to midi clock?

** Update - I uploaded the code on mac osx with the sysex file as I still cant get mios studio running on mac osx with plumstone, ive read everyones comments on how to do it but its not working still, most of the mentioned downloads for the java update are for 10.4 only and im 10.3. I guess with sysex it could work without the midi out??

Cheers,

John

[ultra]

using encoders to save space was exactly my thought.  a smaller lcd off to the right would fit into my seq, so i'm sure a few extra encoders underneath would work out too.  i guess i won't know until i've found the right switches to glue my rgb leds to for the matrix buttons and get going on the layout.

as far as outputting goes, i figured i'd have a second core inside the box, and instead of having four midi plugs available, i'd just have two and allow the delay to be bypassed and external gear could be midi'd through the seq and use it's delay (i'm assuming the seq has midi thru to the output).  if i understand midi correctly, there's two transmission wires and a ground so that could as simple as adding a dpdt switch.

memory and sync would be great.  i do plan on tinkering with some code once i get a midibox working, but all i've coded so far is in visual basic.  i've read that tk's code is well documented though so perhaps it wouldn't be too hard to figure out.

drew

[ultra]

as i finish my seq (no integrated delay :P), i'm planning on doing this project too.

two questions:

i would like to have this in a 1U rack, and of course with this being the case, the encoders that i'll use in place of buttons would have to sit to the side of the lcd.  i haven't seen any screenshots of this delay yet so i'm wondering if the position of the encoders relative to the display matters much?  such as like with the seq, the buttons and encoders below the lcd correspond with data on the screen.  is it such that it would be confusing if the encoders were set off to the side?  i suppose with such a short display (is it 2x16?) it wouldn't matter so much.

also, can the application be used without any modification to the code?

thanks,

drew

[dcer10]

Hiya Ultra,

I think putting this into a 1ru rack would be a breeze, however I cant say anything helpful about the encoders as I couldnt imagine how 8 encoders would run the whole show... Im sure they can, but it doesnt look like it would be a direct replacement for the 30 buttons as theres really 5 interface "groups" being the 4 delays with 3 +- settings each, and then 1 "main" settings with 3 sub settings with a +- each.... The screen does lay out with 4 settings across the 2x16 display (dont bother about a 2x20 as its wasted) but I couldnt imagine an easy way to group them all under the screen so I'd say put em where you like :) It wouldnt be confusing to have them to the side.

On another related note.. I thought I had midi I/O problems with this project, but I dont. I set it up with the default application, all the buttons work, the screen works, MIOS studio can upload to the box in interactive mode, but yet no midi out comes from the machine.. I havent seen much delay wise happening. I think I configured it correctly, and I did see some midi events coming out of it into midi ox, but I havent had the time to investigate fully.

All the best,

John

[ultra]

thanks for the reply, john.  i had actually figured 15 encoders based on your design.  this seems like it would be a really cool thing to have.  probably within the next month i'll be able to start on mine.  good luck with getting it working :).

drew

[ultra]

hi, have you ever completed this?

[dcer10]

Hi Ultra, I physically finished it but have never tested it properly. Moved studios since I started and im set up again now, Ill dig it up some time soon and post. Did you complete yours?

Cheers,

J