Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,206

  • Joined

 Content Type 

Posts posted by TK.

  2. Quad IIC board not working [solved]

    in MIDIbox SEQ

    Posted

    Hi Michael,

    caps should be ok, but I can't say if the pk2cmd will program the PIC correctly.

    Very important hint: don't forget to add the 10 uF cap between 5V and ground, otherwise the PIC won't boot.

    Only additional debugging help: the green power LED should turn on, otherwise the firmware isn't running...

    Best Regards, Thorsten.

  3. MIDIbox SEQ V4Lite

    in MIDIbox SEQ

    Posted

    I'm aware of your intentions, but it doesn't work for me.

    Putting labels at the wrong place leaves a very bad user impression.
    It's a no-go for a good frontpanel layout.
    It's clear that you intent to add them as a reminder for GP button assignment, but not there!

    For learning purposes somebody could just print out a template and place it over or under the device, but later he won't need it anymore (or only if he didn't use the device for a long time).

    Btw.: the labels will also reduce flexibility for future improvements.

    Best Regards, Thorsten.

  4. Can encoders send NRPN values with inc/dec?

    in MIDIbox NG

    Posted

    Hi,

    relative changes can be sent with the various relative value modes, example: 

    EVENT_ENC    id=  1  type=NRPN  chn= 1  nrpn=1  enc_mode=40Speed
EVENT_ENC    id=  2  type=NRPN  chn= 1  nrpn=2  enc_mode=40Speed
EVENT_ENC    id=  3  type=NRPN  chn= 1  nrpn=3  enc_mode=40Speed
EVENT_ENC    id=  4  type=NRPN  chn= 1  nrpn=4  enc_mode=40Speed

    Aside from 40Speed, there is also 00Speed, Inc00Speed_Dec40Speed, Inc41_Dec3F, Inc01_Dec7F, Inc01_Dec41

    These are all "relative values" (I guess that this is for what you asked for)

    Sending different NRPN numbers would be possible with conditional events.

    Best Regards, Thorsten.

  5. MIDIbox SEQ V4Lite

    in MIDIbox SEQ

    Posted

    I mean all helper labels.

    ARM selection labels at the top: don't belong to the top LEDs, they belong to the GP leds when ARM page is selected

    SEQ1/SEQ2 lines at the top: don't belong to the top LEDs as well

    Scale selection labels below above position LEDs: don't belong to these LEDs, they belong to the GP LEDs when the Scale page is selected.

    Remaining helper label line under GP buttons: under these circumstances doesn't make sense anymore... either all GP functions will be labeled at the right place, or they won#t be labeled at all, and users have to find a different way to memo the assignments - I would remove this line as well

    Summary: remove "helper" labels and SEQ1/SEQ2 helper lines

    Best Regards, Thorsten.

     

  6. SAVE ALL saves GROUP 4 to GROUP 2!!!HELP

    in MIDIbox SEQ

    Posted

    Hi,

    this could happen if the two groups are assigned to the same bank.

    Please ensure that

    - Group 1 is assigned to bank 1
    - Group 2 is assigned to bank 2
    - Group 3 is assigned to bank 3
    - Group 4 is assigned to bank 4

    (actually I should remove the bank selection, or make it only optional, because it's an obsolete legacy feature and not user friendly)

    Best Regards, Thorsten.

  7. Newbie question about SID V2

    in MIDIbox SID

    Posted

    On 30. Juni 2016 at 5:41 AM, ChinMuzik said:

    One thing I am confused a bit over...is the photo gallery of TK's c64 SID build. It shows a complete control panel but I don't see where the DINX4 and DOUTX4 modules are located. I see the CORE, MIDI and SID modules. I'm just trying to get a feel if I will be able to stuff all the modules in the case.

    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.

  8. Monitoring memory use

    in MIOS programming (C)

    Posted

    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.

     

     

  9. MIDIbox SEQ V4Lite

    in MIDIbox SEQ

    Posted

    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.

     

  11. Alt + Row does not equal octave shift

    in MIDIbox BLM

    Posted

    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.

  14. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    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.

  17. Volume management issue btw MB Seq v4 and MB6582

    in MIDIbox SEQ

    Posted

    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.

  19. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    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.

  22. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    Quote

    On drum tracks can we have (2*64/2*128), so 64 steps long, 2 parameter layers + 2 trigger layers with 8 instruments?

    ok, I added this to the wish list

    Quote

    Also, when I change a drum track (128/2*128) parameter LayerA to CC, GPK10 doesn't let me select the CC number. It just shows "---"

    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.

     

  24. RGB hue sweep

    in MIDIbox NG

    Posted

    The serial input of the WS2812 chip has to be connected to J4B.SC

    Quote

    is it possible to drive a rgb matrix ?

    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.

×
×
  • Create New...