Hawkeye

Thanks a lot, J! Hope all is well up north! Many greets! Peter

Hi there, that is good news, i will try it out soon! You should be able to rename the base USB portname by changing the MIOS32_USB_PRODUCT_STR variable, changing the individual port numbers might be possible as well, but that would need further investigation - for example, the final individual port names might be constructed in a"for loop" using the PRODUCT_STR as a base and an index counter as a suffix, you could have a look at mios32_usb.c, no guarantees that it will work, though. If you need fewer or more virtual USB ports, you can change MIOS32_USB_MIDI_NUM_PORTS. Many greets, Peter

You can change that in the source file "mios32_config.h", look for MIOS32_USB_PRODUCT_STR. It does not help the usb port enumeration problem under windows, though. Once multiple MIDIboxes are attached, they might get the same name or you cannot address them properly. Someone with windows know-how would need to step in and fix that problem... Many greets, Peter

Thanks, a lot Andy! :-) Snares = left out due to lack of time, hehe ;-). The sampler used was that good old E-MU Ultra 6400, just ripped the sample directly from Youtube to it and used the onboard fx for the (completely overdone) stereo ping pong delay ;-). Have a great day! Many greets, Peter

Hola, it is nice to see more posts in this section of the forums! So i did my best (...still quite limited on time) and posted a new one :-) Hope you enjoy and thanks for watching and listening! Many greets, Peter

tme.eu and this one? http://www.tme.eu/gb/details/rec004002agpp5n0/alphanumeric-oled-displays/raystar-optronics/rec004002agpp5n00000/

Ahhh, there is not thaaaat much diifference between javascript and PIC assembler ;-) You could still go for option 2: wire your CS like the MB6582 control surface... there is no voodoo involved, the MB6582 CS consists just of a lot of interconnections, diodes, leds, switches and encoders - it can be rebuilt on veroboard sections, that fit better in a C64C case! On the other hand, if you are strapped for time, the recommendation is to wait for the CS PCB to be available again and to build a standard MB6582 in a Pactec case :-). Going fully modular in a C64C case is of course still another option, but there will be a lot of spaghetti in the case! :-) Many greets! Peter

Regaring the code question: If you don't want to use standardized MB6582 CS switch/encoder/LED routing (which is expected by the supplied mb6582 hex on ucapps.de), you have to configure and build your own hex (there are include files that allow that modification). To do that, you have to get the MIOS8 toolchain up and running, it may take a bit of time before compilation works, but it is doable. E.g. check: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fsetup_mb6582.asm An alternative to modifiying that code is to map everything just like the MB6582 frontpanel did (you can omit the LED matrix for example), then you could run the standard firmware. Be aware, that everything is based on input/output matrices for the MB6582, so wiring might need to be rather complete to work. There should be a schem of the MB6582 CS floating around here somewhere! Have fun! Best regards, Peter

Imho: go mb6582 for the baseboard, it saves a lot of wiring madness and is just a clean solution (and it just became available again in Modularaddicts shop :-)). You can always build a custom CS from there, but might need to modify the code a little, but it should be possible to do so. You can also use the baseboard without CS and test it with software panels like the ctrlr panel, TK. made some time ago... Many greets, Peter

Very nice!

Imho, that is a good suggestion! There will be some discussions with TK. in the next weeks and hopefully this will make things more transparent, also please (and i should remind myself about that, sorry again to jaytee) remember, that this is about a hobby that should be fun and not stressful, if possible please don't give your fellow MIDIbox peers hell for anything, they are the good ones and are not using Arduinos! :-) Thread closed for now.

jjonas, Yes, you are right! It was unacceptable, and i openly apologize for the unnecessary attack on a personal level. I have also written a private message to jaytee apologizing again and explaining the background a bit.. You know me as a friendly and helpful guy, that usually does not react that strongly. Just to explain: what ticked me off in the end was the statement, that "waiting for an answer from TK. is not necessary". Of course it is. Regardless of all license texts, if they apply or not, it is just good conduct to wait for a reply from the project creator. Many greets, Peter

Absolutely. Jaytee, if you really want to discuss further, send me a message via the forum mailer so we keep this thread clean. But maybe better not. I really don't like discussing with people, who have done nothing for the community, but demand everything and quote license texts and stuff that did not even apply, when the boards in question were made. Regarding future PCBs and gerbers: if they are not open-sourced from the beginning, my old suggestion still stands: make it mandatory for MIDIbox creators to deposit gerbers @TK. (and TK. only), before any PCB is sold. This might solve a lot of problems in the future, while still protecting the hard work people put into their work. Using this method, we would not have the problem with the SEQ CS PCBs and still have the great MBLRE boards available for general use, they are now lost in time. Best regards, Peter

jaytee: the "Wilba MBSEQ CS PCB" design, being cloned or not has never been "free" in any way before, so imho you are wrong on your assumption, that this is "free documentation", that could have been openly shared until now. If it would have been "free", it would have been given out by Wilba or SmashTV years ago, and i can tell you, there have been shortages of the board and users willing to go to extremes to get their hands on the gerbers. Due to a shortage of boards, i built my first SEQV4 on veroboard, too, and it was a long process (but a great experience, that i would not want to miss). The fact, that TK. now open-sources it is a big milestone for the community, that's why i think, that TK. must have the final saying in it. And his decision is good, it makes total sense to validate the board, before giving away potentially faulty gerbers to everyone - that would result in lots and lots of support work from active board members to help people with their messed up PCBs. (Again: i do not believe, that it is faulty, it is just good practice to test it). Many greets, Peter

lis0r: please ask TK. directly via forum message (these should be delivered again as email) to increase his response time on the open-sourcing request. jaytee: personally, i would think it is very necessary to wait for his response, even if "waiting for the response" is not explicitly stated in the license. Many greets, Peter

Very cool, if you are doing another run, i'd also sign up for it, autumn/wintertime sounds great! :-). The Atari 2600 was my first "computer", at age 5, the sounds from the TIA probably burned up a few neurons in my brain, it was a great time! :-) Many greets! Peter

I'd just recommend to test with a PSU with known behaviour, a linear comes to mind - in the end it would make sense to run the SEQ off a switching PSU, because it is far more power efficient. I'd just recommend to have a linear PSU ready for testing this stuff - because if you have one and the displays still show garbage after a while, you can be quite sure, it is not power related (ripples, noise, radio interference from the switching circuit). It should be possible to build one within reasonable time, too, it is just a few big input caps, the 7805 (if you are buying it new, buy a 78S05 with a huge heatsink), two caps close to the regulator and maybe an output cap and that's it :-). You can re-use the PSU for later projects. MIDIbox: keeping people off the street since 1998 ;-) Hehe, have a great weekend! Peter

Cool to hear, that reflowing helped! Glitching LCDs could also be because a lot of things, this comes to mind: a) too long display cables picking up noise, you could press on a ferrite core on the display end of the cable, it helped in some cases for VFDs in the forums. b) "unclean" 5v, especially from switching PSUs somewhere. Sometimes a stabilizing cap directly at the lcd +5v/ground pins helps (something like 100uF) - it did for my OLEDs. If you do suspect the 5V supply being noisy, you could create a "clean" (nonswitching) PSU using a heatsinked 7805 circuit (schems all over the web), that directly outputs into a micro USB plug (only connect the red and black wires after stripping the usb cable), test polarity first with a cheap usb device before plugging into the core! The 7805 could be supplied with a cheap 9V/1A (or so) wallwart. This would ensure a hot heatsink, but really clean 5V power. It is great to have such a supply as a tester for such problems, especially when components like displays freak out after a while, in my experience a lot of these problems are power supply related. Many greets and have a great weekend! Peter

Good call, Andy, +1 for the tiny disco 3v regulator or the usb cable being the problem, had both problems before! :-) Missing/misplaced buttons might be due to problems to access the SD card and being unable to load the configuration file, that would be another argument for a 3V regulation problem. Can you measure the stability of the 3V rail (there are top pins on the disco headers, that can be easily reached with a scope/multimeter)? But it might also all happen due to a soldering joint going bad on the core, you could visually check and reflow/resolder all of them. Good luck! Peter

Very cool, man! You really need a proper MBSEQ soon! :-) Many greets, Peter

Nice job! :-) I really like the lo-fi-ness of the recording, perfectly fits the genre! :-) Many greets, Peter

As you wrote, if the card itself is damaged (maybe too old, or too many write operations), the sequencer will have a hard time accessing or formatting it, which might lead to the crash. Can't you open up the SEQ, pull the card and see what a computer can do? There is a "SDFormatter" tool available for free for windows, which I use quite often to do a sector-by-sector format, it might help to recover your SD card. Good luck and many greets, Peter

No worries, it was not meant as a critique, and i like the ideas! :-) Yes, configuration via "Options" would be great! Personally, i will have to rebuild my primary SEQ CS (all built on verboard, handwired back in 2010/11) because of the failing switches soon, the Matias switches look awesome, but that belongs elsewhere. Have a great day! Peter

good suggestions, but regarding this point: I've grown very accustomed to do the muting and unmuting with the encoders instead of the GP buttons, and maybe other users have grown accustomed to this too, because some of the old-style Wilba tactile switches may go bad over time and trigger unreliably, which is not good during a live performance - the encoders are just working fine! :-) Many greets, Peter

nope, don't do that, please! :-) At some point in time you will have heatsinks flying around in your case, if they are conductive, they might short all kinds of things. You should be able to get adhesive thermal paste just about anywhere, it is worth the investment (or don't install heatsinks at all). Many greets, Peter