Hawkeye

While it is not classic "pattern switching", I use the seq mostly by first creating 16 tracks, that can be combined via the mute/unmute menu. With delayed mute/unmute (Menu->Options), it works very nicely - I spend 90% of the time in the mute menu when using it "live". 16 tracks is also enough for me for one tune, but your milage may vary, depending on your needs. Also, although I am not using it this way, I am quite sure that you can switch to "a new pattern, aka four new tracks" in the pattern screen of the sequencer with synchronization (switching, when the old pattern ends). Greets, Peter

thanks and happy birthday, gtx! :-)

Thanks :) am still learning to play "theremin" style, so there are some glitches in the demo :). Btw, only tracks 9-16 are active in this demo, the upper four led rows would display tracks 1-8. Hope you like it - it is easy to build. Greets, Peter

Hi, Here is a small demo presentation of the new MBSEQ TPD, also showing the new tempo features of the MBSEQ. Thanks for adding them, TK! ´tis small track i haz made on todays rainy and coding-uninspired morning ;): If there are any questions regarding the TPD, this is the place :) Greets, Peter

Hi there - you can power it either via hub-powered USB, which is sufficient, if you don´t have too many LEDs/displays or use J2 and connect a stabilized 5V PSU - don´t forget to connect C8 to J2 for filtering. Yes, the LPCXpresso 1769 from In Bed With Artists (he he :-)) is required. Greets, Peter

Thanks, J! Schem: wire the 8 pins of one DOUT shift register (with 220R resistors) to LED matrix cathodes, wire the 8 pins of another DOUT shift register (with bridges, no resistors) to the LED matrix anodes. PS: tested the new dedicated bpm encoder function yesterday night as well and it works like a charm.. hands-on speed control, even when you´re e.g. in the mute menu :-)

Here is a short demo video of the relative track position display: The upper 8x4 LEDs of the matrix show the tracks 1-8, the dots "fall upward", every LED equals 25% of track length played. The lower 8x4 LEDs of the matrix show the tracks 9-16, the dots "fall downward". Muted tracks are not shown, so you can see at one glance, which tracks are currently unmuted and playing, even when you are not in the "mute" SEQ screen. This video also shows the new 4-digit BPM indicator and the currently-played-step (of the currently active track) LED indicator. All those features (BPM & step digits and the TPD matrix) fit on a DOUTx4 board (4 shift registers)... just make sure, that you use low-current LEDs, otherwise they might be too dim. If you are interested, you should be able to add this to a "standard" Wilba SEQ, if you can add a DOUTx4 module to the serial register chain. I´ve cables over 50cm long running from the shift registers to the LED digits and LED matrix, so you could add this as an optional breakout box somewhere in your rig. I hope to put on a better demo in a separate thread, when there is time for making some music... Edit: now, there is a better demo and room for TPD discussion available here: Thanks, TK.! Greets, Peter

Stimme Ilmenator völlig zu... habe die Kabel zu den Shiftregistern kurz gehalten und dann lange, verdrillte Kabel zu den Buttons/LEDs, klappt bis 60-70cm bei mir. Allerdings kann ich "Fehler" produzieren, indem ich die Kabel z.B. über die VFDs führe... Ausserdem sind DIN/DOUT Button/LED Matrizen anfälliger gegenüber Störungen als direkte "zwei-Draht-Verbindungen". Ciao, Peter

Yes, i know that great demo in and out... :-) You can employ a noisegate, which will create silence, when the sids are not playing... when they are playing, you won´t hear the chip noise... that is if there are no other problems... I once had a noisy PSU (due to a build error) which was not soo good, as it picked up stray noise from nearby switching PSUs from time to time. Have fun with your new synth! Bye, Peter

Hi and congratulations to your build! do you have standard 6581s? They are fairly noisy... It is normal, that you always hear the oscillators, even if there is no note being played (SID specialty :)). Also, depending on the patch/filter settings you can hear more or less noise, which is normal. It could, of course also come from the PSU, which is more likely, if you employ a cheap switching PSU. Greets, Peter

Well sorry, I was too fast promising things, that I cannot keep ... when building the ´lite for lpc1769, it says section .bss will not fit in region RAM region RAM overflowed by 11344 bytes I know as of this post that it is possible to send certain big arrays to other ram segments... how have you guys already using/testing it built it? Greets, Peter

Hi Paul, I haven´t found any downloadable binary versions of the seq lite on ucapps.de, so I assumed, that you checked out the source codes from the repository and built it by yourself... If you need it, just drop a line and i´ll send you the current compiled version for LPC17... Greets, Peter

Hi Paul, just checked it - works for me - all sources there and builds fine (edit: for STM32)... maybe re-checkout via svn? Greets, Peter

hm, i primarily use melodic anti-spam - it filters forum advertisements by same-day new members with a post count of 1, while playing honkey-tonk blues. It has been developed, because that well-known nILS app started to mess around with gravity on a full-time-basis, causing serious havok in all modern string theory models. *scnr* :D

Hi Thorsten, just continued to test... and found some things, that may explain the strange behaviour on my side... a) applying the inversion mask for a "pin" probably will not work (in case of shared anodes and inversion): unsigned char mask = 0xff; printf("%u", 1 ^ mask); yields 254 instead of 0 (app.c, lines 256ff) b) for the fourth digit, a float bpm is needed to render it successfully: the code was int bpm = (int)SEQ_BPM_Get(); ... u8 sr_value = SEQ_LED_DigitPatternGet((bpm*10) % 10); c) somehow the configuration of the segments register needs to be one value smaller than it is... i need to set BPM_DIGITS_SEGMENTS_SR 8, when it is 9... the register for the BPM_DIGITS_COMMONX_PIN is all right. Am not sure, if these observations are right, still testing, but I start to see numbers on the breadboard :-) Greets and have a fine weekend! Thanks for adding these features, again :) Peter Edit2: just saw in the code, that the currently edited step is displayed in the step display... uh- sorry, my fault, the feature request was ill-formulated... i meant the currently played step in the active pattern, when the sequencer plays... so that you know when to expect a track border... sorry for being such a pain in the ... :-)