SuburbanBoy

i made a parts arrangement: it should always be possible to see the part of the screen you're editing. myself, i have no need to see the whole display at any moment. what worries me more is that it's hardly possible to turn two adjacent knobs. i don't like push-buttons. and i prefer my ring finger. anyhow it's a good point, both could be implemented: pushbutton-datawheelexchangeable mapping of (UP/DOWN) and (FAST/ALL), though it would be preferably swapped around the display for the left-handed i haven't looked on the LED-details yet. the pcb would (i doubt it will happen) have one LED per button (except Step View has two or duo). the only thing i do with two hands is masturbating. actually, i'm not very well coordinated when it comes to the use of both hands.

thanks for your response. i modified the initial post in order to answer your points. i hope that clears some of them. have a nice day!

i'd like to order a pcb for a SEQ4 control panel i designed, but i would only afford it if others ordered one as well due to the discounts. one of the initial ideas is to build a layout around a 40x4-lcd. here's a conceptual draft to give you an idea: these are no exact positions of the elements, the drawing is a study on a ui-design leveltechnical requirements will certainly lead to minor design changesand there is still the opportunity to throw in great ideasthe button caps used here are 18,5x18,5mm/~0.73x0.73ini have some vintage RFT-button caps (i currently know one cheap source; 0,2€ per cap) i will connect to buttons with custom 3d-printed adaptersthe f-keys are quoting the C64-keyboardas this is certainly not a solution for everyone, i intend to design the pcd so that you can mount widely available button40x4 LCD paneldimension: ~330x240mm/13x9.45inthe red star sits on the data wheel encoderi would order at MakePCB, unless i find a less expensive opportunityprice per piece / number of pcbs: ~118,80€ / 1; ~27,70€ / 10; ~18,50€ / 20; 12,20 / 50; excluding shipping (i ship from germany)i'm aiming commitments for 10 pieces before i actually start layouting the pcbas Wilba's PCB it would include all elements to hook it as DIN/DOUT-module to a core modulea bulk order for associated parts may be organised as well, depending on the feedbacktime frame: none yet, but certainly not delivered this year to explain my motivation on this: as i have all parts for this, i will build it. propably it will be on breadboard connected to dio_matrix-modules. the only point that detains me from a pcb is the price. so if i can evaluate that there are chances to order this in bulk, i will work on a pcb. due to time limitations i cannot afford that otherwise. comments on the design are as welcome as questions and of course commitments of interest.

i know that. and there's definately hardly any blind spot in the documentation. but we all know (i guess there is a common sense about it) that the huge amount of data is not well structured. i don't blame anyone for that, i know how time-consuming such a task is. but you somehow have to cope with that fact, and leaving stuff out is an option. sometimes with unwanted side-effects. don't worry. i actually find the communication in the forums here to be very civilized.

i just realised that i shouldn't have stopped reading after "MIDIO 128 and MIDIBox " here.

nah, i owe you at least one nervous breakdown i'll miss while re-engineering. and thanks for the additional info, wilba.

och, ich schau da immer nicht rein. aus gründen. vielleicht sollte ich die überdenken. weren't you the one who designed a custom panel, too? ah, i see. simple answer: it's a matter of design. many thanks, i will study the source code and then have a further look onto the hardware design. btw, i noticed on the sammichFM it's the other way 'round. ten LEDs controlled by one of each chips.

i intend to design a pcb for a mbseq. i have some trouble understandung the following: acccording to this schematic (mbseq_v4_din.pdf) i would need 7 serial registers (74HC165) for 54 buttons, but wilba's pcb (wilba_mbseq_pcb.pdf) uses only 2 of them for 58 buttons. as i have problems to read the layout well, i can only see that 4 switches are connected parallel per shift register's pin. i guess there is some trick done with the diodes and the 74HC595 on the other side of the switch to achieve some kind of multiplexing, but i can't follow that path in the layout. is there some documentation on that? or can someone put it in easy words for the noobs. i haven't yet looked the source code about it. i just don't want to get lost looking for something that isn't there. so any feedback if i should follow that path is welcome. and: if i end up having enough space for 11 74HC165s to connect 53 knobs and 17 encoders on the pcb, would multiplexing be worth the effort, except for the gain of endorphines, serotoines etc. in the engineer's brain parts? (that's more or less a metaphorical question.) have a nice day!

i recently cleaned, sorted and restructured the midi interface blacklist on the wiki. i marked those interfaces for which i couldn't find a confirmation with a question mark. so, if you can confirm that a specific interface should be blacklisted, take some seconds and remove the question mark. any other corrections are appreciated as well.

this is great to hear news! while it smashes 50% of my current mb-project's concept, the ng will allow me to reconsider almost all of my postponed features and allow even more. is this the thread to watch for needed help and support to this? i would even come along, prepare you some meals and clean your toilet. but i guess you are in the far west. do you consider to design the software that allows to change the configuration of a group of (encoders, buttons, leds, lcds), while any other configs are untouched?

"That's a bingo!" well, i'd had to know that the point was something out of my autistic focus. so, everything is working fine and there are two happy silbings around: nILS! TK! Wilba!

hmpf, i meanwhile got a new interface (Midisport 2x2), but it turned out to be a step backward for the time being. the curiosity is, that when both cables - In and Out - are connected to corresponding ports (A or B), the sammichFM isn't starting up successfully at all. the LCD will only show a fully filled first line that is 'rendered' for a short time after power-on. voltages to the lcd are still fine. this will not happen if only one cable is connected or the cables are on different ports (A-In B-Out / B-In A-Out). anyhow, on any cable setup with a MIDI-Out connected, the upload request will not be monitored by MiosStudio. i think i remember of having read something similar in context of midi troubleshooting and was solved with a little hack, but i can't refind it now. i wonder what is hould do next, take a bang with a wall or smoke a sports cigarette.

if they work like paddles, it's probably 470Ohm.

afaik, there is no jumper to toggle on the sammichFM. i have a question regarding my understanding of a basic correlation: am i assuming right, that i would not only monitor the data transmitted to the sammichFM on the JUCE output, but on the corresponding output of the midi-interface too when using a tool like kmidimon? btw, i just noticed i posted in the wrong board. sorry for that. who may relocate this thread to the Troubleshooting board?

ciao tutti, after i assembled two sammichFM boxes - what has been a fun and didactic über-useful process fo far - i have trouble getting them to work eventually. i will start with the one i get the farthest with; let's call him Ebony. i hope in the end his brother - Ivory - suffers the same problems. after repeated successful voltage tests, i launch MIOS Studio 2.3.1, query the sammichFM and get the status of an up & running application. i can initiate an upload of the current MBFM software (setup_pic18f4685_sammich_fm.hex from midibox_fm_v1_4e.zip) which progresses without errors onto 100%. but after a reboot of the sammichFM - which isn't evoced after upload by itself, the expected software will not launch, but instead there still will be READY. message on the lcd again. also, querying the machine with MIOS Studio again will lead to the same output as before; there's no mentioning of any further software than the MIOS itself. unfortunately i can't be sure if my midi-setup isn't another one of these overbugged things in my life - and responsible for the above described. the point is, i can't even be sure whether the sammichFM will be recognized by the MIOS Studio every time. i didn't find a reproducity to gain success or failure fo far. at least it seems to me that restarting the MIOS Studio increases the chances of a successful query; but i haven't made a statistical evaluation yet. so far i used a M-Audio Audiophile usb-interface on WindowsXP and a borrowed Akai MPD24 on WindowsXP, Windows7 and Linux 3.2, with the latter combination turns out most solid. so, any hint on what i should check next will be highly appreciated. have a nice day!