Hawkeye

And my favs are: Alpha RE160F-40E3-20A-24P (@ Kristal, if you order 1000pcs, 1.45€ pp@mouser, rock solid encoder, but no push function) and Alps STEC12E08 Many greets, Peter

Agreed, expensive, but excellent - would not want to miss VFDs in the SEQ or MB6582 anymore - once you are accustomed to their "instant" speed, you want to replace all displays in all synths and your car dashboard :) Many greets, Peter

Thanks for the info - the more i read about Bourns, the less I want them in the LEDring boards :). The Alpha Encoders are really solid, i´ve got them in the MB6582 and after heavy usage for some time, they still feel as good as on the first day. For the SEQ, I´ve got some non-Wilba-PCB size ALPS encoders - and they do also work flawlessly. Many greets, Peter

Yes, they are the same - sorry for not giving proper credit! It is looking very good! :) Many greets, Peter

Hi Thorsten, looking awesome, and very nice, that you support it! :) Schrab created a fine case: Many greets! Peter

Yes! It works perfectly now! Very, very cool! :laugh: I´m sure, others will love this feature as well! Many greets, Peter

Hi Thorsten, awesome, thanks for the fix! Just tested (with two synths each) - duplication (works fine) - note alternation (in order/random) with notes stuck (see below) ..and working with one minor issue left - the notes appear to be stuck in any alternation mode (behaving like active sustain pedal) - maybe the "note off"s are missing somehow? No hurries and thanks for that great feature! Have a nice weekend and many greets, Peter

Hi Thorsten, Thanks a lot! This is a great feature and frees up one MIDI OUT/IN port pair, that I used for this purpose (duplication via MIDI router listening on an IN port, that received notes from an OUT port, that was directly connected :smile:). But the duplication effect is so much more powerful - got to check out from SVN right now! :smile: Edit: tested it - and it works great for duplication, but I seem to have two minor issues: a) when in "Forward to all channels" mode, I only get duplication on the other device, when "non-notes are forwarded". If "non-notes are filtered", the other synth stays silent. b) when in "Alternate Channels mode", (and with non-notes forwarded), i was hoping to send only every second note to the other synth (kind of a ping-pong effect), but currently all notes are played on both synths (maybe this helps, i used a different output port than "same" for testing) Many greets! Peter

Very nice job! Well done! Many greets, Peter

:D Great, thanks for the update and looking forward to your vacations! Many greets, Peter

Hi Boom Shakthi, that is bad enough to hear. If possible, you should consult a lawyer and let him/her write a letter to them on your behalf, in which he tells, that you want your money back, asap... maybe this helps - you have rights as a customer... Anyways, I´d highly suggest you look into the MIDIbox line of SID synths. The best SID synths you can get on this planet! :) Many greets! Peter

Hi Thorsten, a) Wow! Thanks for your help, please tell me, whenever I can bring another crate of beer (and we play a bit of music)! :-D b) Just found the problem, thanks to your tool - all MIDI IIC modules thought they were module "0". Reason: because i just followed the "out only" schem here: http://www.ucapps.de/mbhp/mbhp_iic_midi_out_only.pdf without thinking... i soldered in the jumper headers for the selection, but without the necessary resistors R4 and R5 as seen in the "full" schem: http://www.ucapps.de/mbhp/mbhp_iic_midi_out_only.pdf After quickly soldering them in, it all works fine now, many thanks again! :-D Bye and many greets, Peter

Hi Thorsten, yes, you´re right, perfection or nothing :). Just checked the IIC modules, everything seems to be present, capacitors C1-C4 with the right values are there... As a further test, I just connected the MIDI IIC modules on my spare LPC17 core, which is now running the same version of SEQV4 (compiled with the same toolchain but with LPC17 target). The LPC17 core is USB bus powered and has nothing else (no frontpanel or displays) attached. Result: exact same behaviour - it sometimes detects both IIC 1 and 2, most often only IIC 1 (checked via terminal). I used the same IIC bus cabling (same wires and connectors). Then I uploaded a default build of SEQ V4 (and the newest bootloader just to be sure) downloaded directly from ucapps.de - no change.... It is getting late, thanks for your help, while testing I discovered that MIDI port rescan "Newbie Mode" easter egg in MIOS Studio, that made my day, thanks! :). Will report back with new findings, at the moment i would say something with my IIC cabling seems really messed up :) Many greets and have a nice evening! Peter

Hi Thorsten, thanks for your time and your thoughts! I have four separate (old) MIDI IIC modules from SmashTV, all jumpered to different IIC addresses. When I install two modules on the IIC bus and power the SEQ up, normally only one (IIC1) gets detected. I can successfully output MIDI over it. When I remove this module from the IIC bus (and don´t change the jumper setting on the other module, its IIC address is not 0x10), the other module gets detected anyways and appears as IIC1 module. Now here comes the mystery: when the SEQ has been powered off for a prolonged time (say at least one minute), sometimes two IIC modules will be detected, but only, if there are only two modules on the IIC chain. If I have all four installed, only one will get detected (and is usable). If I do quick power offs/ons (less than 10 seconds of waiting), always only one module will be detected. Strange, isn´t it? Please don´t waste energy on that matter, it is not important, I just thought maybe someone has a clue and says... of course, you have to do this and that and it will work :smile: Thanks & many greets! Peter

Thanks for your feedback, ilmenator! It is good to know, that it should work, maybe it is because of my adaptations to get the VFDs running which required some (probably improperly done :)) driver hacking or the long SRIO chains I am using, or the old compiler toolchain i am using (did not manage to update yet, am compiling on FreeBSD, which complicates things :))... But no worries for now - will wait for the new core and then update everything properly :-). Am really looking forward to the STM32F4, awesome specs, cheap price :) Many greets, Peter

Hola Altitude! Thanks for your answer - yes, the bootloader is up to date. It is really not important, please don´t pull your hair :) - will upgrade to the new STM32F4 based core and check IIC MIDI again, when it is available - 192KB of RAM will allow for more SEQ goodness, maybe even 1024 step patterns as a Christmas present? :-) Many greets! Peter

Hola, me is extending my old Core32 SEQV4 for moaaar MIDI ports... :smile: Are there any known issues with the old IIC MIDI modules (MIDI out only) in conjunction with an old Core32/STM32 SeqV4 (running @ latest firmware, compiled with old toolchain, not newlib-nano enabled)? I installed four IIC MIDI modules, jumpered them to different IIC addresses and the SEQ only recognizes the first one, sporadically also recognizes the second one (in about one out of ten boot times). The 5V voltages seem ok (stabilized 2A 5V PSU, got around 4.75V at the MIDI IIC modules). I swapped through the IIC MIDI modules (installed every one as single first IIC1 module), and they all work individually. The IIC bus is also wired correctly, imho... Has anyone got any idea? It is not really important, I managed to get IN3/OUT3 and IIC1 running and thus already have two more out ports, am just curious, what is going on :smile:. Thanks and many greets! Peter

Does not technically fully qualify as chiptune, but nevertheless, it is one of the most awesome MODs evar, imho :smile: Have a great halloween, y´all! :-) Many greets, Peter

Looking sweet, congrats Mr. Schrab! :)

The multi engine is really cool! In the end, it all depends on what you are trying to achieve and which sound your are looking for. Personally, i like the lead engine a lot, because it gives me the chance to refine the c64-style sounds with sub-oscs, slight detuning, stereo fx and have one filter per engine at the disposal. If you have too many different sounds/patches active, there is a chance everything drowns and you are likely to get a frequency clash in your mix, exactly as monads said. But what it is all about, experiment and find what you like best! Enjoy! :-D Many greets, Peter

Hola :) Yes, imho you can limit patch responsiveness to a midi note / keysplit region: http://www.ucapps.de/midibox_sid_manual_fs.html search for SpL and SpU For your usecase, you would go with drums on the first engine, with a split region nailed to the lower keys, and three lead engines with a split to the upper keys, all engines on the same midi channel - that should work fine. An engine can only hold a single patch, but you have four of them ;-). You might want to try a computer editor (e.g. Rutger´s or Ctrlr) for Wavetable (also Bassline Sequence) editing - as there are a lots of parameters to be entered, it might be quicker with a mouse. Enjoy! :-) Many greets, Peter

Thx! Yes, the randomizer is great - by using it often, you will hear the fantastic sonic possibilities of the MBSID plattform - it can sometimes not sound very SIDlike, more like a full-blown synth, but some sounds, especially those with that that special raw Squarewave-SID-sound remind of the sounds of the old masters (Rob Hubbard, Chris Huelsbeck, Jeroen Tel, ...). They often added special programming to their "patches", which is not super easily to be reproduced (you would need to automate some CC comands to achieve the same effects or dive super-deep into the modmatrix). When I built my MB6582, I did not install the defaults bank on it at first, it was a jump into the cold water, and me was totally confused by all the possibilities... and I still haven´t explored them all, yet - by now I am on patch A86 and creating every new patch is just fun :smile:. So I would recommend to start with a fresh bank, and just experiment. I only use the nice knobby hardware interface, trying to avoid computers where possible :smile:. Also I only save the patches on the banksticks, no DAW integration. For a live song, I then write down, which synths need which patches for any given MBSEQ V4 song, even if changing to the proper patches could be automated within MBSEQ. One last tip - add a decent delay or chorus software or hardware effect to the raw sid sound - it will make a great difference :-D. Many greets! Peter