John E. Finster

No worries. I also like it better the usual way. Just for this special usecase it would be nice having an optional representation of the global velocity value of the track. But of course I manage well without it and I think there are more interesting feature requests out there.

Thank you for clearing this up. I suspected that the song mode and/or the guide track might work with a fixed divider. I also understand now why the track played back with the wrong division after I (allegedly) cleared all the song configuration. I didn´t deselect it as the guide track, so being a guide track in a song takes precedence over the regular divider settings. Just to be sure though: I then tried to use another (empty) track as a guide track, I left the divider at 16 and set the length to 64 steps which fit 48 steps with a division of 8T. I thought this way the guide track would give me the 64 16th steps (= 48 8T steps) I need for one loop of the 48 8T steps pattern. But when I select it as a guide track the length is automatically reset to 16. Am I doing something wrong or am I misunderstanding the idea of a guide track? I got it working another way: I set Option 1/33 and 2/33 both to 64 steps, so my song is working fine now.

Hi everyone, I may have found a bug in Seq4 version 096 (still present in 097). Problem: I have created and saved a pattern on track 1 (48 steps, divider 8T). Then I went into Song Mode and set song position A1 to 3 repeats. I also set track 1 as the guide track. Now when I hit play the song seems to be played with divider 16, the step counter increases faster than the steps of the 8T pattern. So when the song step counter reaches 48 the pattern is not yet finished and restarts prematurely when looped again. The worst thing is that this breaks the tracks divider settings. When I go back into Edit Mode, after I cleared all the song positions, the track is played back with the wrong divider. The track is still set to 8T but is played as 16, so the track is not played back completely anymore. Setting the divider to 16 and back to 8T does not solve the issue. I have to power down the Seq and start it again for the track to be played correctly again. I hope the description is comprehensible. Best Regards

TK, I have tried your suggestion and it works really well. But what I didn´t think about is that the velocity layer doesn´t display the vertical bars anymore. Apparently the velocity layer displays the note event of note layer A. Would it be possible to display a simple bar on the velocity layer like the one of the length layer?

Hi TK, great to hear from you again. That sounds like a very doable solution, thank you. I didn´t know that the notes already exist after initialization. It´s so great that after all that time there are still features of the Seq I haven´t used yet

Hi everyone, long time no see After a long break I unpacked my midiboxes and started making music again with my Seq. I want to trigger a guitar instrument and setup the track so that the first 6 note layers represent the six guitar strings. That way it´s relatively easy to translate guitar tabs. Now I´ve noticed that, whenever I enter a note on note layer 2-6, one is also entered on the 1. note layer automatically. I am able to deactivate those afterwards by pulling the note down to --- with the encoder, but this behaviour is quite irritating and the solution is not very comfortable. I´ve never noticed this behaviour in the past because I never used multiple note layers before. Is there some way to work around this? It would be ok to make changes to the source code, I can recompile. Any ideas welcome. Best Regards

Ok, so far nothing happened here. I will lower the price to 300,00 € plus shipment. Alternative offers are always welcome.

Hi, I am selling my Midibox Seq 4. Documentation and pictures here. (The yellow, green and blue buttons are now all black) Unlike the usual Seq 4 Model, this one doesn´t have the side panel, but it has 4 additional buttons on each side of the big data wheel. Also instead of step leds it has red and green illuminated encoder (green = activated, red = current step). The casing is a self-made wooden case, here is how it was made. It is usb-powered and works very well. I´m asking 450,00 € for this unit, plus suitable shipment to wherever it has to be sent. issues with the unit: The 15th encoder only lights up in green, the red led inside seems to be broken. But this encoder is available at many electronic stores (e.g. here) 4 Midiconnectors as well as an on/off switch are built in, but are not working. The wiring for those has to be redone, if needed (I didn´t :-) ). Please pm me for any questions.

Ah, ok. Thank you. Best Regards John

Hi, could anyone please delete my second Account "john doe". I´ve set it up years ago, when I first came in Contact with Midibox, but forgot about it and set up this account later. I noticed yesterday when I accidently logged in with the "john doe" account. Thank you. Best Regards John

Hi, I´d like to ask permission to sell my Custom SEQ4 and my Midibox NG / Mackie Control Clone. These days, I have to focus the little freetime I have on my family and I find less and less time to make music any more. Link to the documentation: http://wiki.midibox.org/doku.php?id=john_e._finster Best Regards John

Hi Marxon, I just converted your *.bmp to *.xpm with Gimp Portable 2.8.10 (see attachement). No problems here... Unfortunately I can´t tell what the problem might be on your end. I´ve not seen this error before. If I had to take a guess I would say maybe there is an issue with the file path (dots, exponents). I´ve encountered errors with paths like this before. Not necessarily with Gimp, but with other Apps. Other than that I´m afraid I can´t be of much help. Your *.bmp looks fine, the *.xpm I created seems to be in order and ready for further processing. Till you get around this problem I´m happy to convert your *.bmps. Just pm me. @mono: Nice work with the spreadsheet. I´m not that deep into excel, so I can´t entirely follow your process. Maybe you could upload a sample sheet, so I can have a deeper look. Greets knob48x48.zip

Nicely done! And it was build in a relatively short time. Much respect.

Thanks for these tipps. Both are very usefull apps. I included them in my tutorial und updated it. For other changes see initial topic.

Yeah, it is tough to create good looking fonts if they have to be a) this small and b) only black and white. If you´re looking on the internet, then try to find some dedicated lcd fonts or particular small or squared fonts as a template. I think the true potential here lies in creating nice icons or bars, especially since the original glcd fonts from TK are nice to look at and functional.

@FantomXR Glad you got it to work :happy: . Maybe you could post a picture of your work once you´re done, I´m pretty curious. @TK Thanks. I hope it will be of some help to others.

Hi, I finally came around and compiled a brief tutorial on how to create glcd fonts for Midibox NG. It can be found on my wikipage here. I hope it´s comprehensable. If any questions arise, don´t hesitate to ask. I will try to help as well as I can. Also, if you find any mistakes I might have put in, just tell me. Have fun! my regards EDIT: Update 01.05.2014: Small changes, mostly fixing linguistic errors and adding additional hints. EDIT: Update 11.05.2014: - Tutorial now on seperate wiki page - including "little helpers" section with usefull designing apps

I believe the STM32F4 comes with its own usb connector so the core board doesn´t have to provide one like the LPC17 core board.

If i´m not mistaken a STM32F4 core board is already available at Tim´s. I ordered one a few days ago. I don´t know if the current SEQV4 firmware supports the new core though,I´ve hadn´t have a chance to test it yet.

Thanks for considering this, TK. Looking forward to the new firmware. my regards

Nice work, mindjuice. Would you mind sharing the layout? Greets

Hi, I thought about this for a long time and want to throw some ideas around now. I really think this could be a very helpful feature. The feature I was thinking about is a dedicated expression layer within the parameter layers. This expression layer could provide fixed midi notes for keyswitching or note name maps. The notes showing in the edit screen could be named individually. The "expression maps" (hope this term is not protected by steinberg :happy: ) could be external text files stored on the sd card. They could be loaded when the expression layer is assigned to a parameter layer inside the track event page. Trk. Type Steps/ParL/TrgL Port Chn. Edit Layer controls Load Map G1T1 Note 256 4 8 USB1 01 Name A Expr Violin PRESETS INIT The corresponding text file ("Violin.txt" in my example) could be stored in a seperate directory on the sd card and look like this: // expression map for kontakt violin instrument // number name continuous 36 'sust' yes // sustain 37 'stac' yes // staccato 38 'pizz' yes // pizzicato .... In the text file there could be defined: - key - the name showing on the edit screen - whether or not the midi event should be hold until another event/switch takes over Possible usecases: - easier and more clear controlling of instruments with keyswitches without memorising hundreds of keyswitching notes for different instruments. - naming notes individually if an instrument is used that doesn´t require traditional notes (e.g. Reason Dr.Rex Loop Player. Instead of notes it could be more useful to see the slicenumber that is triggered, like 'sl01' for slice 1, 'sl02' for slice 2, ... Or maybe 'rev1' for reversed slices). - creating adapted note names for drum samplers which are more complex to be played with a regular drum track Like I said, these are just ideas, but I really believe many would benefit from this feature. Thanks for reading. my regards

Hey, thank you very much. I´m ok with changing bits of the code myself. my regards

Hi, thanks for the reply. I just found the entry in the changelog. I knew I overlooked something :-). I tried your suggestion but still, the sequencer isn´t stopping. It just loops the last (muted) patterns. I understand why this behaviour has been introduced, it is nice to have the sequencer looping the last patterns as a transition to other songs/patterns/... But on other occasions I would like to have the sequencer stopped at the end of a song (in practice sessions with others,....). Anyway, thanks for the advice.

Hi, I feel kinda silly to ask. I´m pretty sure I missinterpreted some of the infos in the manual or I overlooked a setting somewhere. My problem is that the action "end" is not stopping the sequencer. It displays the correct song position on the right side of the song page (the position i assigned the action "end" to) but it keeps playing the last song position over and over again. - I am using "song mode", not "phrase mode" - The sequencers clock is set to Master - the current firmware 4.079 is loaded on an LPC17 core - I am using a Guide Track since the length of the patterns are 96 beats What did I miss? Thanks and greets