Hawkeye

Nah, don't sell the SEQ parts, my recommendation: get some cheap 40x2 LCDs from China first and start jamming. You'll love the SEQ, there is always a chance to upgrade/repair later on. If you want bling, you could also go for VFDs, loving mine since 2010, they are absolutely awesome and I'd prefer them over the Raystar OLEDs every time ;-). Of course, the best ones from Noritake are expensive as hell! ;-). So, visit your local trustworthy china outlet and get some cheap displays first, upgrade later ;-) Have a great rest-of-the-weekend! Peter

Hey Duggle, I've nothing set up with "set single_usb 0" here, but just tested again (thought it would be wise, after a million windows system updates in the last year or so), and Win 10 seems to be partially bad for me again - while all MIDIbox USB devices are properly detected and listed in MIOS studio, i can always only talk to a single device at a time (even when there are 12 usb midi ports visible, always the same unit will answer)... I also tried installing the ploytec gm5 drivers, but they would not even install (afterwards I read, they were not supported for STM32F4 anyways), so multi-MIDIbox-usb is still problematic in windoze land, sorry! For my usecase, win 10 it is still better than running windows 7, because at least all devices, when connected one at a time are always detected, i will simply switch off the other MIDIboxes i don't need to talk to. Maybe setting "single_usb 0" would help here. But, as a conclusion, if you only need to talk to a single MIDIbox device at a time, Win 10 works great (much more stable than Win 7 detecting stuff, i have two STM32F4s and one STM32F1 here and there was no problem yet. Only sometimes you need to "query" multiple times within MIOS Studio, until you get a response, but that is an old problem). For Win10, there are also auto-privacy tools, that let you disable all the "M$ talking home" stuff in a few minutes. Other than that, you might want to consider installing a Hackintosh or Linux (if you can get the software you are used to for these platforms). Many greets, Peter

Personally, i can recommend Windows 10 over Windows 7 MIDI-USB wise, i have a machine with a connected mbseq v4, the mbprogramma and the mbloopa, all can be used simulatenously, no additional USB drivers installed. Sometimes, there are some hickups during device detection in MIOS studio, port rescans help... No experience with GM5, though... A recommendation for the update, if you have another harddisk (even an old laptop drive), just clone your existing win 7 disk, then upgrade, the rollback is as easy as swapping the drive or cloning back :-). Many greets, Peter

Hi and welcome! unfortunately, Fairlightiii vanished from the forums a while ago and we have no gerbers to reproduce these PCBs. There are other community efforts to build similar boards though, just have a look around :-) Many greets, Peter

Hola, potentially it is a power-related problem... Can you check for clean power on the 5V rail? E.g. with an oscilloscope? I am using two OLEDs as well in my "flatsequencer mbseq v4" (i think with the power set to 5v) and i get trouble with screen garbage after a while, most likely due to a noisy (cheap) switching regulator i am using to bring down the battery power from about 9.6v to 5v. If you are using 3V to drive the displays and are using a STM32F4 core, the tiny onboard-regulator of the STM32F4 may be overloaded, imho it also only provides 3.0V, not 3.3V and the displays require 3.3V? Can you check the 3V supply voltage of the displays during operation? Voltage? Ripples? Sometimes a medium-sized cap (470uF) over the supply pins is sufficient to stabilize the OLED. Edit: sorry, just read that they are broken now, sorry. How did you break them? Many greets, Peter

Wow, that's a very nice build! Congratulations! :-) Many greets, Peter

Thanks a lot, man! Did not know that compilation, will have a listen! :-) Have a great time! Peter

Thanks a lot, guys! This one was literally made in two hours including sampling from youtube, entering a few lazy patterns in the SEQ and doing the video editing, so no effort at all went into it ;-). Will try to improve sampling (and would by now, after listening again, transpose the main melody an octave lower or so), but I seriously have to work on a project, Andy assigned me a few months ago, so there is not much time for music ;-) Hehe! Have a great time, y'all! Peter

Yo, in case i did not mention it during the last months: the MIDIbox sequencer is awesome! It allows you to flee reality (baby teething worries) for as little as half an hour and have fun, without pushing a mouse, without staring into a computer screen or getting involved in operating system updates at unpleasant times :-). It just works out of the box, the MIDI timing is way better than that of a multi-GHz multicore computer and everyone is happy with as little as 128kb ram (in the older cores)! :-) This one contains a few fun samples from an old car information system - 1980s era - and reminds me of childhood - i especially love the modulation on the "door is *open*" sample :-). Yes, bash it, hate it, do whatever, but thanks for watching and listening ;-). Have a great evening! Peter

As you are asking for cheap and there are already ebay.de links floating around this thread, i can recommend this seller and these ALPS EC12 encoders. Very good price, with pushbutton, used them in the Programma V1: http://www.ebay.de/itm/15x-ALPS-EC12-Profi-Encoder-24fach-isoliert-mit-Taster-Automotive-lw/302092634447?_trksid=p2047675.c100005.m1851&_trkparms=aid%3D222007%26algo%3DSIC.MBE%26ao%3D1%26asc%3D39075%26meid%3D3c4098fc5dd645f5a3fa41f6c783a391%26pid%3D100005%26rk%3D2%26rkt%3D6%26sd%3D302092627591 (Just remember to wire correctly, when installing in 16mm encoder slots, which is easily possible after a bit of pinbending) Best regards, Peter

Hi, the observed behaviour makes sense, then. Do format with FAT32 and all should work as expected! Many greets, Peter

Ah, ok, this clears up some things! My impression was, that the escargot requested MIDI timecode interpretation. I don't think the SEQ handles MTC (for the reason listed) and thought the he wanted to scroll to any virtual song position in the DAW and continue playing from there... But as it seems, only pause/resume has been requested, that might be fixable behaviour, but it would be a new feature request, e.g. for the options menu. If that new feature would be activated, the SEQ could interpret midi beat stops as pauses, to be able to continue like e.g. the machinedrum does. You could add that idea as a feature request to the MBSEQ general thread and see what TK. has to say about it! Many greetings, Peter

Sorry for the late answer! I had a similar question when still using a DAW. Afaik, MBSEQ responds only to MIDI start/stop and tempo commands, but does not interpret song position. So, if i am right, there is no way to directly jump to a certain step/bar when starting DAW playback in the middle of a song. All is fine when you start at the beginning, of course. The reason behind this (i am not sure, but that's what I came up with then): it would be difficult for a step sequencer to interpret a given DAW song position - what if your DAW song is longer than any stored track, which is quite likely... Where to start each track? There is no way for the SEQ to know... Many greetings, Peter

Hi there and welcome! Unfortunately, for some users and years, windows USB MIDI is/has been a bit of a mess (windows 10 has been a bit better for me than seven). There have been many different problem reports and not all could be 100% solved, TK. said it is something about the windows USB MIDI stack implementation, it sometimes gives a lot of headaches. As your MIDIbox is detected fine under XP, there should be no hardware problem with the core module itself. You can try a few things: a) Press CTRL-SHIFT-R a few times, this will perform a Rescan MIDI devices command. Press "Understood", otherwise a funny dialog might lead you to the exit of MIOS studio :-). I have a PC, where this is indeed needed sometimes, before the core is detected. b) In the MIOS32 command window, type in "help" a few times, then rescan ports. This sends some characters over the MIDI USB stack, sometimes this helps and the device is detected afterwards. c) uninstall the GM5 driver and repeat steps a) and b) d) if unsuccessful, boot from a usb stick image of linux (use ubuntu) and use the linux MIOS studio Please report back, if any step a)-d) helped with your problem. Many greetings, Peter

Great job man, can't wait to get some boards soldered up! :-) Have a great day, Peter

Of course, for me the MB6582, have been a SIDhead for the last 30+ years, people don't change :). Also, the MBSID has a very complex synthesis/modulation engine, which is a big plus, you still discover new things after all the years :). Many greets, Peter

Interesting, that should work! Could you try to use all uppercase letters? Can you check with which FAT-type your SD card was formatted? FAT16 filesystems should convert lowercase characters to uppercase (lowercase letters would be forbidden, but i don't know how MIOS handles this, this might cause the error). BUT: nowadays it is really difficult to create a FAT16 filesystem, so i am not convinced, that that is the problem... Alternatively, just backup all data, then re-format the SD-Card with FAT32, restore data and try again...

Logical MBSEQ datastructures from top to bottom: * Sessions are saved to disk, another name for them would be project/song. * Patterns are stored within sessions. Every pattern always holds four tracks (sequences). Per default, four inital patterns thus hold the 16 tracks. A session can have many more patterns saved. This is useful to e.g. switch a group of four tracks at once (e.g. exchange a group of four drum tracks at once, you can do this in the "Patterns" screen). * Tracks are what we see in the mute/unmute screen and are the basic building block, that hold the individual sequence notes. You could totally ignore patterns and just use the 16 tracks (mapped to four patterns, but you need not care)... for my limited songs, i do the same, 16 tracks are enough, i mostly unmute/mute them, change tracklengths/fx and that is enough for me... Many greets and enjoy! Peter

Andy: AOUT_TEST.NGC probably was rejected or had problems, because it does not fit the original FAT 8.3 naming convention (only 8 characters ahead of the "." separator). While it might be possible to create files with extended lengths, different access methods (within MIOS Studio or the MIOS32 application) trying to open these files may fail, so it is probably best to stick to the original 8.3 restrictions. Escargot: here, the 8.3 naming scheme is explained, there is also a list of not allowed characters: https://en.wikipedia.org/wiki/8.3_filename Many greets, Peter

Nice explanations and perfectly understandable even for Bavarians, hehe ;-) Keep them videos coming! :-) Many greets! Peter

Yo, that should not be a problem and is expected behaviour, as the session name is also the filename on the sd-card FAT filesystem (which has certain limitations regarding allowed characters). Many greets! Peter

Hola and welcome :) Quick recommendations for shops in Europe: reichelt.de ("standard" service for germany, many parts on ucapps.de have reichelt partslists) tme.eu (good prices, quick shipping) mouser.com (quick shipping, a lot of parts, free shipping over 75€) Parts: there are many available brands, a good encoder brand for pots (also encoders) and switches would be Alps. Some very cheaply bought mechanical products from china can have limited lifetime, or wobbly shafts (encoders/pots), or for tactile switches, button presses won't be recognized anymore. But this can also happen with quality products, we had some problems with switches for Wilba's MBSEQ control surface, and these were manufactured by a "quality brand" :-). Many greets and have fun! Peter

If it is a midi sequencer, just hook it up via midi, yes... Have fun and many greets, Peter

not possible without coding a bit... that means either some in-depth mios32 studying (it is possible!) or the (faster) hardware way: just chain up another core running e.g. a seqv4l based firmware...

Sounds good! Minimal comments: * you probably only need a single DOUTx4 board for 16 digital outputs. * best to put the TPD at the end of the SRIO chain, as it has an uneven amount of shift registers. * you might need to change the firmware for 8 IIC MIDI ports (imho only 4 supported in the standard firmware, allowing an already plenty 4+4 out ports) * start with the smallest possible setup (no aout, no digital out, no tpd), then extend... this allows for quick endorphin release (not necessary to solder up everything) and to test early :) Have fun building it! :) Peter