Gridracer

Sorry to disturb again, but I noticed anotehr issue with beta22 and the 4x16BLM: onyl on step 1-16 the LEDs for active steps get lit, on step pages 17-32 and higher the LEDs stay off whether the step is active or not. Chaselight and buttons work correct, also the GP LEDs Best Regards, Gridracer

I have a question regarding the arpeggiator (and transposer) I noticed that the arpeggiator (and transposer) behave different when they are contorlled from external eg. keyboard or from an internal track: - If the contorl notes come from external, the settings HOLD and RESTART work as they are described in the manual - If the contorl notes come from an internal track, the arpeggiator (and transposer) always behaves like if HOLD is ON and RESTART is OFF, no matter to which value they are actual set. Is this behaviour intended? Best Regards Gridracer

Hi SynGy7, to me it is not really clear what you described: * Do you gett all your LCDs working by connecting them to J15A, and none of them works at J15B ?? -> Then I would check all soldeing Joints and traces on J15B, also check if your DIL connector has propper contact. You could connect your LCD to J15B and then ping the connection to the solder pads on the display to the connector pins on J15A, only the enable line you have to ping to a solder pad on the PCB. This way you would also find a faulty connection on the LCD Side. * Or do you have one LCD that does neither work on J15A or J15B -> bad solder joint or DIL connector on the LCD side, or broken LCD? Good luck, and best Regards, Gridracer

WOW! TK, your speed in development is unbelievable! I am so happy to have the chaselight back, and it's also nice to be able to upload code via USB now... so much faster :) Thank you very much! Just tried creating a new session, works fine here. Best Regards, Gridracer

Hello Thorsten, I noticed that the chaselight is no longer working propperly with beta21 on my singlecolour 4x16 BLM: Active steps get inverted (LED goes off) when the chaselight passes -> OK But inactive steps are not inverted (LED stays off) -> NO CHASELIGHT VISIBLE. (On the GP LEDs the chaselight works well, also on the BLM if i upload beta20) Here if required my relevant settings in the config: BLM_ENABLED 1 BLM_DOUT_CATHODES_INV_MASK 0xf0 BLM_DOUT_DUOCOLOUR 0 By the way, i really enjoy having 4 transposer tracks since beta 21 :) Best Regards, Gridracer

I noticed some strange issue with the copy function: Setting the copy range with the rightmost and leftmost encoder does not work propperly (anymore?) : - When I first decrease the highest stepnumber to copy with encoder 16 and then try to increase the lowest stepnumber to copy with encoder 1, encoder 1 just behaves like encoder 16 and changes the highest stepnumber to copy. - When I first increase the lowest stepnumber to copy with encoder 1 and then decrease the highest stepnumber to copy with encoder 16, it works untill i do not change the lowest stepnumber to copy again, then, encoder 1 just behaves like encoder 16 again and changes the highest stepnumber to copy. THIS EFFECT ONLY OCCURES WHEN THE HIGHEST STEPNUMBER TO COPY IS> 16! Best regards Gridracer

I noticed that the new dedicated FOLLOW Button is not working in BETA18C. FOLLOW LED works, MENU+EXIT works also. I can exclude an hardware issue: button works when I assign it an other function. Really like the new session concept! No longer worrying about overwriting patterns or whether they are in use or not. :) Best Regards, Gridracer

Also works fine here :) But importing my old files did not work at once: I got an error message "invalid session" when i tried to open the "imported" sessions from Beta 15 I was missing the "MBSEQ_G.V4" file! I had no such file on SD card. Solved it by creating a new session and copying the file from there. Best Regards Gridracer

For me, 4 banks would be fine. This would match the number of groups so it's easy to remeber if you always store 1:1 Bets Regards, Gridracer

Hello Mastomo, I have build a V3 that i have updated to V4 and i can tell you that building a V4 is easier than a V3: -The display connection (common source of trouble) on V4 is much easier on V4 than on V3 as the pinning is 1:1 -You do not need an 8x bankstick SD Card instead -Despite that the V4 is much more powerful than the V3, it is also easier to customize as V4 has a config file for the hardware configuration that is automatically loaded, while you have to recompile the Hex File after changes on V3! -You can upload code over USB or Midi (Midi is more critical as your Midi Interface could cause problems, and the optocoupler on the MIDI in of the core seems to be a quiet fragile part) Best Regards Gridracer

Hello Robotfunk, you wrote so I guess you have no custom MBSEQ_HW.V4 file configured to work with only 2DIN boards? Does this mean that you connected DIN board one and two like shown in the shematic and just did not connect those buttons and encoders that should be connected to the third board? These would not work of course, but I would not be surprised if it would also cause software problems if you do not adapt the MBSEQ_HW.V4 file. But I do not know for sure, this is one for the experts. Have you added the RC Termination? Best Regards Gridracer?

Hello Robotfunk, I guess, the problem could be that you are powering your SEQ over USB. If i remember right, there are some threads around here that recommend not to do so, but I could be wrong. From the STM32CORE WIKI page: And on a SEQ you have two displays and a lot of LEDs...... Hope this could be a hint. Best Regards Gridracer

I noticed another tiny issue: When "follow" is activated in the options menu, the paste function does not work correct: The paste offset value gets changed when the chaselight passes. Best Regards Gridracer

Hi gjvti, you do not have to modify the software. You just have to assign the additional buttons and led's in the configfile: "MBSEQ_HW.V4" In the file all buttons, LED,s and options are listed that are available without software change. The file is included in the release package: ucapp For the additional Buttons and LED's you will need additional DIN and DOUT modules. Best Regards, Gridracer

Hi gjvti, You will notice that on the third DINX4 Board only 2 shift registers are used so to the remaining two you can connect 2x8=16 Buttons, then you have to make the assignments in the "MBSEQ_HW.V4" file (which Button you have connected to which pin of which shift register) Yes, they can but you will need a second DOUTX2 or X4 Board and you have to use common cathode dual colour LED's The same as for the buttons, you have to make the assignments in the "MBSEQ_HW.V4" : (But only the shift Register has to be assigned, not the pins, here you have to follow exactly the schematic) # DOUTs for Dual Color option: GP_DOUT_L2_SR 0 GP_DOUT_R2_SR 0 Sorry, iam not aware of this -> cant't help. By activating "FAST" the encoders work faster for entering bigger value ranges exactly, the pages can be also assigned in "MBSEQ_HW.V4" I think this is what you are looking for: MIDI_REMOTE It's the same I absolutely agree! :drool: It's even more impessive to work with it than to read about it. Looking foreward to see another custom build MIDIbox SEQ! Best Regards, Gridracer

Just noticed some minor issues on the SONG and PATTERN screen which I want to report: I am not sure if the section in the manual is just not updated yet or if it is a bug in the current firmware or only not implemented yet: From the Manual: PATTERN screen: I can not toggle between capital and lower case characters, only capital characters are available SONG screen: The layer buttons do not move the cursor Best Regards Gridracer

Great news and a perfect start for the new year! Can,t wait to test it on the weekend. It is getting better and better and better: V4 lives on the fast lane... Once again, thank you TK and also a very happy 2010! Best regards Gridracer

Hello taximan, just as ROSCH wrote, WILBA's SEQ is what you are looking for: (As far as I know, the only open issue is the casework at the moment) In addition to WILBA's kit you will need in any case the core module: CORE_STM_32 But the most important at the end: You should read the WIKI page several times and also look at the schematics to learn more about MB SEQ and MIDIbox in general. MB_SEQ_V4 You won't dig into all this stuff over night, but be encouraged, it is much easier as it may look at the beginning. And your efforts will be rewarded by the most powerful SEQ on this planet. Not to mention this great comunity with all the other impressive projects. Go ahead! Greetings Gridracer

ALL BUTTON: would it be possibel to have the ALL BUTTON effecting really all steps of a track, not only the ones that are actually set? (Just like it was on V3, if I remember right) For me this would make much more sense, especially since there is the SELECT BUTTON to call and define a exclude pattern for the ALL function. At the moment it is hard to set, eg. the velocity, of all steps to a dedicted value. Or am I just missing something? Best Regards, Gridracer

I found no specs about this card on RadioShack's or SanDisk's web page. But Conrad Electronics also sells a 2GB SD Card from SanDisk and they specify the transfer rate with 3.5 MB/s read and write, which would be a speed factor of x23,3 which would be below the recommendation of at least x60 But I guess TK's test app. will show if your SD Card is too slow. Best Regards Gridracer

Hi, did you make sure that you have a SD card with an appropriate speed factor? FROM THE WIKI: (A speed factor of "1" equals 150 kB/s) I use a 2GB card with 20 MB/s read and 11 MB/s write without any problems. When i powered my box for the first time, i used an old 256MB card as a guinea pig. With this card i experienced real long waiting times. Best Regards Gridracer

Everything seems to work as supposed to, as far as I can tell from a few minutes of testing. I tried differernt TRACK lengths / play directions / LOOP mode and STEP VIEW -> everything OK Intensive testing latest on the weekend.... Best regards Gridracer

I toyed a little around with the SCRUB function as it works now for-and backwards in V4, which is real fun using the datawheel as some sort of scratchpad. (absolutely no sequencer hickups or anything, WOW!) Then I thougth I could stop or pause the sequencer and use the SCRUB function to scroll through the pattern. But I had to realize that using the SCRUB function always causes the SEQ to start. Is there a special reason for this behavior? If there is no conflict with an other usage concept and only if it would be really easy to change, I would suggest to prevent the scroll function from starting the sequencer. But to be honest, why would I ever want to stop the SEQ? as it it is one of the main features that you don't ever have to... :wink: Best regards Gridracer

Head up!! :) Regarding all the work and time you spend for all of us, I think there is no need to feel sorry for anything! Keep up your great work Gridracer