-
Posts
15,246 -
Joined
Content Type
Profiles
Forums
Blogs
Gallery
Everything posted by TK.
-
The gallery shows pictures of my first build, where I used dedicated DIN/DOUT modules. Meanwhile I replaced the modules by a MB6582 PCB Best Regards, Thorsten.
-
Hi Sauaen, Interesting find! Yes, please commit the changes, so that I can try them at my side. The change should be documented in http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2FFreeRTOS%2FREADME_1st.txt so that it can be reproduced on FreeRTOS updates. While I'm writing this, I noticed that we are using a 3 years old FreeRTOS version. I will update soon. Very likely the malloc handling has been improved meanwhile, so that the change becomes obsolete. But please commit anyhow so that in case of issues we are able to switch back. Best Regards, Thorsten.
-
Hurray, progress with the new frontpanel! :-) But from my point of view, the additional labels, and also the SEQ1/2 lines, are more confusing than helping. They are above LEDs which don't belong to the appr. functions. It would be better to remove them. Best Regards, Thorsten.
-
Good! ;-) To be clear on that: nothing will get lost (I've a TODO list) - but please accept that sometimes there are situations at my side which require higher attention. Best Regards, Thorsten.
-
No, it probably hasn't been verified and therefore probably won't work after the changes for somebody else who requested changes for the virtual interface... Patience please, the issue is noted, I need to schedule a review & code changes at my side - which probably won't happen in the next weeks! I guess that you can life with this limitation... Best Regards, Thorsten.
-
Yes, this should work fluently w/o hick ups. How can I reproduce this - which setup are you using? Best Regards, Thorsten.
-
I guess that after some changes requested by somebody else, this function isn't working anymore. Shows me that the "real" (not virtual) BLM16x16+X needs to be reviewed & improved, this task is already on the wish list. Best Regards, Thorsten.
-
Hi Kazik, to 1) I added this request to the MBSEQ V4+ wish list - to make this possible, more RAM will be required which is only available for the MBHP_CORE_STM32F4 to 2) this would require an interpolation algorithm, added this to the MBHP_CORE_STM32F4 wishlist as well (it will consume more compute power which should be available for this core - let's try it out!) Best Regards, Thorsten.
-
Sometime this year Best Regards, Thorsten.
-
Yes, I added it yesterday (the documentation was only in the source code) "binary logical" the first digits are at the right side, and the last at the left side. Best Regards, Thorsten.
-
I think it's related to a (known) limitation of the MBSID V2 system: during a patch change, the firmware has to read ca. 512 bytes from the bankstick, during this time a MIDI buffer overrun can happen if too many events are received. I fear that there won't be a proper solution for MBSID. On the other hand: due to the SID background noise, the usage of lower volumes shouldn't be preferred anyhow. It's better to lower the volume on the mixer. Best Regards, Thorsten.
-
Hi, according to the documentation following port mask should enable SPI1: ports=00010000000000000000 Best Regards, Thorsten.
-
A scale editor is still on the Wishlist: ---------------------------------------------------------- http://midibox.org/forums/topic/19701-blm-feature-requests/?do=findComment&comment=171522 Scale Editor ---------------------------------------------------------- it will probably be provided for MBSEQ V4+, since it will cause some additional RAM consumption. I guess that this will solve the request. Alternatively some additional scale entries could be provided for "flattened scales", but this approach would be less flexible. Best Regards, Thorsten.
-
Problems running app on new STM32F407G-DISC1 pcb
TK. replied to illogik's topic in Testing/Troubleshooting
According to the linked post, jumper SB10 has to be bridged with a solder blob. Could you please try this out - I guess that this will solve the issue. And could you please create a picture for documentation? Best Regards, Thorsten. -
Perfectly quoted - it gives all information :) Best Regards, Thorsten.
-
ok, I added this to the wish list CCs are actually not supported for drum tracks, it's an error in the UI that it allows to select this. The pattern structure has no free space to store the CC numbers (because the appr. slots are already used to store Note number, accented and normal velocity) Therefore I added to the wish list, that the UI shouldn't display the CC selection Only solution that I see at your side: use another track to play the CCs I know it's cumbersome, but there won't be a quick solution to solve this Best Regards, Thorsten.
-
A systematic approach to clarify the situation: record the MIDI output with a DAW and check the MIDI events there. Has the CC been sent (& recorded)? Best Regards, Thorsten.
-
The serial input of the WS2812 chip has to be connected to J4B.SC I'm not sure if I understand your question correctly. Each WS2812 chip drives one RGB LED, by default you can connect up to 64 WS2812 chips, but it's possible to increase the number (with the drawback of higher SRAM consumption). See also http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fws2812%2Fws2812.c The WS2812 based approach is not based on a LED matrix, it's a serial chain of (cheap) RGB driver chips Best Regards, Thorsten.
-
It works at 10bit resolution. Best Regards, Thorsten.
-
Should be easy, I added a reminder to the Wish List Best Regards, Thorsten.
-
The WS2812 chips can't be connected to a MBHP_DOUT module due to the different serial protocol. Best Regards, Thorsten.
-
Hi, problem is understood, but it requires a firmware enhancement. I added following to the wish list: ---------------------------------------------------------- Song Mode: when a new pattern is selected, it would be helpful to sync the appr. tracks to the measures, e.g. to reset the LFO Add option for this behaviour. Best Regards, Thorsten.
-
It would be inexpensive if we could define a rule which simplifies the algorithm. E.g. let's say: each instrument can be assigned to a group number x (x=0 for no assignment, 1..16) on each step, the sequencer will only play the last instrument which has been assigned to the group, all other instruments assigned to the same group won't be played Due to the additional RAM consumption within the pattern storage space, such a feature could only be provided by the MBSEQ V4 Plus firmware, which requires a MBHP_CORE_STM32F4 Best Regards, Thorsten.
-
Priority decisions are expensive (CPU wise)! :-/ Best Regards, Thorsten.
-
Here the documentation about the MIDI protocol: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fblm_scalar%2FREADME.txt However, maybe you missed the already existing BLM emulation software which is available for Win/Mac/Linux: http://www.ucapps.de/midibox_seq_manual_blm.html Best Regards, Thorsten.