vcfool

This exact same thing happened to me with my STM32 SEQ v4 (first version STM32, not STM32F4). I actually solved it this way: I decided to upload the previous versions to check when the bug was introduced, but I ended uploading backwards to such old versions on which I was sure this didn't happen at the time of release. I think I got back to something like "midibox_seq_v4_074" and the bug was still there! So I gave up. Uploading such previous versions and the corresponding old "hwcfg" file made my configuration parameters not valid. So when uploading back to "midibox_seq_v4_094b" I had to manually reset all my MIDI Router parameters and other settings in the "Options" page which got deleted. After doing this, the BPM LED started blinking correctly on the beat again. So I am guessing that something was messed up in the MBSEQ_GC.V4 file or somewhere else. Hope I am making myself clear and that this will help.  

Yep, now it works. I just made a quick test and the IIC Outs work nice with v4.075pre2.   Thanks again.

Hi,   I just tried the above v4.075pre1:   The Seq seems to find the IIC outs. No more "*" appears next to them and I can see the the IIC out activity on the MIDI Monitor page. But still, there is no actual data coming out of the IIC Ports physical outputs.   Thanks again for the ultra-fast support!

Thank you so much! I knew I did something stupid that I shouldn't have done.   MIDI uploading worked fine. I plugged my GM5 and upgraded to v4.074 successfully again. Nice. :smile:   And now the 4x IIC_Outs are no longer recognised by the Core. :sad:

I think I messed up something in my SeqV4 (STM32): :sad:   A few days ago I succesfully uploaded from 4.065 to 4.074. I updated both the bootloader and the application and everything seemed fine.   But just tonight I noticed that none of the IIC Out ports were no longer seen by the Core. The "*" symbol appeared next to all 4 of them. I thought that before opening the machine to look for a hardware fault, I would check that it wasn't caused by the newly uploaded version 4.074 of the application. So I uploaded 4.065 again and the IIC ports came back to life. So now I have my IIC ports working fine again, but MIOS Studio is reporting an error every time I try to upload the application or the bootloader. No matter which version I try to upload it all seems to start fine, the Seq LCD's show Bootloader mode for some seconds, but then it just reboots and MIOS Studio shows the message: "Upload aborted due to error #14: Invalid SysEx command"   Now I see that I probably did something silly and maybe Bootloader 1.012 + v4.065 is not a good combination. This all happened using MIOS 2.4.4 on OS X 10.8.3   So I'd really like to know if there is a way to fix this and get the USB uploads working again or will I get stuck on 4.065 forever?   Thank you all very much!   And someone with 4.074 and IIC Out ports installed should check if they work. :smile:

Hi, I upgraded from v041 to v048. Something is wrong with my Drum tracks when played from an external MIDI keyboard: The Drum sounds appear repeated several times over the whole keyboard and some MIDI notes don't trigger the right sounds. Using the Live Play mode works fine. Sequenced tracks also work nice. Just direct playing/recording from the external keyboard seems to be affected. I just tried version 42 which is the last one I downloaded (but never really tried) and the problem is also there. Maybe I am doing something wrong. I went back to v041 and all is fine again. Thanks again!

Great! Thanks! :)

Just upgraded from Beta35 to 38. I am using Wilba's CS and found that BUTTON_PAR_LAYER_A is not working for me. I can confirm that it is not a hardware problem: MIOS Studio detects that the button has been pressed/depressed but says that it's not mapped. I went back to Beta35 and the button works fine again. Thanks! :)

Sorry if I am misunderstanding your idea, but are you aware of the "Scroll" function? I'm not sure that I do understand the differences between the already implemented "Scroll" and your "Cycle" idea. :)

Nice, thanks again! Been quick trying right now and I think there is a problem with the normal Step View Edit Mode: The lower line of the LCDs is always displaying the Notes for Steps 1-16, no matter which steps are selected holding the "Step View" button. The upper line of the LCDs and the GP LEDs do show the actual values and edit seems to work, but the lower lines always show the Notes and Lengths of Steps 1-16. Also Length Parameter Layer is showing the bars on non-gated steps: Clear the Track and all the steps will show a Length bar indicator. This didn't happen on previous versions. Maybe I am just doing something wrong... :)

I have been thinking that such a feature would be useful too. Maybe just adding an "Advance Step Parameter" like the one found on most Tracker style sequencers: Set it to "0" not to advance any step when inserting a note, set it to "4" and advance in quarter notes intervals... etc...

Not sure I completely understand you... There is a 3rd MIDI In/Out on the Core for the BLM now. But you can use it as a normal MIDI port. I have 2 keyboards and 1 sequencer connected to the MIDI INs of the MB-SEQ v4. Using all 3 Core inputs without any problem. Hope this helps.

Nice! My 2 cents: Would the extra resistors for the LEDs fit on the PCB? Maybe somebody wants to use them, so they may be a good addition. At least adding only a soldering pad next to pins 6 and 10 of each PIC, without resistors, so one can add the resistors and LEDs if needed. Just a thought... Then, looking at your PCB vs the schematics, I see you have connected pin 6 of the PICs to J2 (SV6 on your PCB). As far as I see, Pin 6 should be the "Power ON" LED, and pin 7 is the one that should go to J2. Am I wrong? :)

Well, so I have the same situation here. I have an AOUT_NG inside a MB-SEQ v4. I have been using Unipolar mode without any problems since I finished it some months ago. I have been following this topic and just now I tried the Bipolar mode. So far I have only tried CV1: On the Mixer Map I assigned a CC to the AOUT CV1 output and calibrated P9 to have 0V at a CC value of 064. And I have the same problem: the output range is only -2,7V to +2,6V.