Jump to content

TK.

Administrators
  • Posts

    15,198
  • Joined

Posts posted by TK.

  1. It's working at my side when I'm using the v4_084_pre3 version.

    It behaves like at your side when I'm using the older v4_084_pre2 version.

     

    Could it be that you picked up the wrong one for upload?

     

    Best Regards, Thorsten.

  2. Hi,

     

    you are asking for a so called "Radio Button" functionality.

    Unfortunately it isn't supported by MIDIbox64, and I can't add such features anymore.

     

    If you would upgrade to MIOS32 (e.g. by using a MBHP_CORE_STM32F4) and MIDIbox NG, the configuration of such a function would be pretty simple.

    See also this tutorial: http://www.ucapps.de/midibox_ng_manual_fs.html

    (search for "Radio")

     

    Best Regards, Thorsten.

  3. An update is very easy: install MIOS Studio (if not done yet): http://www.ucapps.de/mios_studio.html

     

    Connect MIDI IN/OUT of your MB6582 to your computer, open MIOS Studio, select the MIDI interface, try the bidirectional communication with the "Query" button.

     

    If working, first upload the new MIOS V1.9h version, thereafter the new MIDIBox SID application.

    Both are linked in this posting:

     

    Best Regards, Thorsten.

  4. The problem with the MAP feature in MBNG is, that it only works with up to 256 values (8bit), but the faders are controlled with 14bit resolution, and you really want to keep this resolution.

     

    A 14bit map would consume 32k RAM - no way to implement this for the PIC, and even for the MIOS32 based MBNG not enough RAM is available for such a feature anymore.

     

    Therefore I think it would be better to do the mapping at the host side.

    Are you using a Mac? Do you know how to compile programs from a Terminal? Then I could give you a simple program which is doing the translation.

     

    Best Regards, Thorsten.

  5. Alright, I think (resp. hope) that I got it now:

    I used a GM synth to playback your song, and G2T1 (the bass track) selected the "Seashore" instrument which wasn't really audible.

    Together with your description I realized, that this is related to the new pattern load handling.

     

    Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_084_pre3.zip

     

    The "restart tracks on pattern change" should take place again regardless if the pattern has been reloaded from SD Card or not.

     

    Best Regards, Thorsten.

  6. The driver is selected and running.

    But it looks like two wires are swapped.

     

    Could you please take an hi-resolution picture of your HW mod, so that I can check if the cables are connected to the right pins?

     

    Best Regards, Thorsten.

  7. Learning Curve:

    |                **********       I'm working with a more complex framework
    |          ******                 I've implemented proposals from experts
    |      ****                       I understand proposals from experts
    |    *                            I'm getting some helpful hints from experts
    |   *                             I'm asking the right questions in the forum
    |  *                              I'm able to send some MIDI Notes based on tutorials
    |  *                              I'm able to read & understand Wikis
    | *                               I'm able to troubleshoot configuration problems
    | *                               I'm able to configure & recompile premade applications
    | *                               I'm able to upload prebuilt binaries
    |*                                I know the right end of the soldering iron
    +------------------------> time
     

    Best Regards, Thorsten.

  8. Fortunately there are no tracks routed to J16:D3..D0, therefore you can add the wires without special measures.

     

    I'm planning to update the firmware, so that a special flag can be set to enable the 8bit LCD interface option.

    I would provide you a special precompiled version for testing - but if you already able to compile by yourself, then this would help me (a bit less effort at my side, especially whenever I provide a new firmware)

     

    Note that I won't be able to test the enhancement at my side - I hope that it will work immediately at your side, otherwise I will need some time to buy & try the same OLED.

     

    Best Regards, Thorsten.

  9. No, touch sensors are not supported by MIOS32, they consume too much CPU time.

     

    Btw.: did you already found somebody who will program the firmware for you?

    It would be bad, if you build this expensive hardware and then expect that I would take over the development - actually I'm not really interested to provide private solutions.

     

    Best Regards, Thorsten.

  10. You have to remove the encoder entries at the bottom of the file:

     

    	;; additional CS encoders
    	;;        SR  Pin  Mode
    	ENC_ENTRY  0,  0,  MIOS_ENC_MODE_DETENTED3	; Osc delay/transpose/assign #1
    	ENC_ENTRY  0,  2,  MIOS_ENC_MODE_DETENTED3	; Osc attack/finetune/assign #2
    	ENC_ENTRY  0,  4,  MIOS_ENC_MODE_DETENTED3	; Osc decay/portamento/assign #3
    	ENC_ENTRY  0,  6,  MIOS_ENC_MODE_DETENTED3	; Osc sustain/release/assign #4
    	ENC_ENTRY  0,  0,  MIOS_ENC_MODE_DETENTED3	; Osc release/pulsewidth/assign #5
    
    	ENC_ENTRY  0,  6,  MIOS_ENC_MODE_DETENTED3	; LFO rate
    	ENC_ENTRY  0,  0,  MIOS_ENC_MODE_DETENTED3	; LFO depth
    
    	ENC_ENTRY  0,  4,  MIOS_ENC_MODE_DETENTED3	; Filter CutOff
    	ENC_ENTRY  0,  6,  MIOS_ENC_MODE_DETENTED3	; Filter Resonance
    
    	ENC_ENTRY  0,  0,  MIOS_ENC_MODE_DETENTED3	; Env depth/assign #1
    	ENC_ENTRY  0,  2,  MIOS_ENC_MODE_DETENTED3	; Env attack/assign #2
    	ENC_ENTRY  0,  4,  MIOS_ENC_MODE_DETENTED3	; Env decay/assign #3
    	ENC_ENTRY  0,  6,  MIOS_ENC_MODE_DETENTED3	; Env sustain/assign #4
    	ENC_ENTRY  0,  0,  MIOS_ENC_MODE_DETENTED3	; Env release/assign #5
    

    because they overrule the button assignments

     

    Best Regards, Thorsten.

  11. It's very likely a 4/8 bit thing.

     

    The solution would be a modified firmware (I could provide the modification if you are interested) and four wires to J16:D3..D0.

     

    Could you please already do this hardware modification?

    Connect:

    - PIC Pin RE2 to J16:D3

    - PIC Pin RE1 to J16:D2

    - PIC Pin RB1 to J16:D1

    - PIC Pin RB0 to J16:D0

    /edit: pinning corrected, this one is working (confirmed by RyuX)

     

    Compare following schematic for sammichFM J16 pinning: http://www.midibox.org/dokuwiki/lib/exe/fetch.php?media=sammichfm:sammichfm_base_pcb_rev_1.pdf

    And following schematic for PIC pinning: http://www.ucapps.de/mbhp/mbhp_core_v3.pdf

     

    Best Regards, Thorsten.

  12. Let's come back to these bizarre issues which I would like to solve :)

     

    Could you please describe in more detail, how I can reproduce and monitor the MIDI output based on the session that you gave me?

     

    Best Regards, Thorsten.

  13. The MIOS32 based solution is only experimental, far from completion (e.g. there is no UI yet).

    It was some kind of learning example for me some years ago, therefore you also won't find documentation - probably it will never be released to public.

    E.g. SID core connection is a difficult topic, probably it would only be possible via CAN, which means that PIC based cores are still required, which makes the project too complex for newbies.

    In order to download all files, use a SVN client as explained in the Wiki.

     

    Best Regards, Thorsten.

     

    P.S.: next reply next week - I'm on a weekend trip
  14. Then I also need exact instructions to reproduce this issue.

     

    Btw.: check the ensemble configuration of your MBFM, maybe multiple instruments listen to MIDI channels which are intended for other devices?

     

    Best Regards, Thorsten.

     

    P.S.: next reply next week - I'm on a weekend trip

  15. In assembly language it mostly isn't a single line, but there are many places which need to be changed and dependencies which need to be considered. Sometimes it's even impossible due to higher execution times or missing resources (RAM, Flash)

     

    Therefore I was carefully asking if you really want/need this, because normally it will be some effort (1..2 hours) to do & test the change.

     

    And one mistake can lead to even more time since debugging without knowing the whole code is extremely difficult (e.g. where would you start if MBSID crashes sporadically after your change...)

     

     If you really want to start with this, it could make sense to read & understand the C based version (for MIOS32) of the firmware first: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v3%2Fcore%2F

    Because here most of the functions are mostly only a single line...

     

    Then try to find the same function in the assembly based version, see how things are done (e.g. how to add + multiply 16bit variables), try changes.

     

    Best Regards, Thorsten.

  16. I still can't reproduce this problem.

     

    Could you please try the following: press the stop button two times before start - does this change something?

    Please try this with the same version like me (084_pre2 that is linked above)

     

    If this doesn't make a difference, I will need more specific instructions. So, every operation after power-on, like: enter song page, select song mode, press play, wait for 3 seconds, press stop, press play, look for MIDI events played by track 1

    (this is exactly what I'm currently doing and where I don't see a problem...)

     

    Best Regards, Thorsten.

×
×
  • Create New...