julle

Members
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About julle

  • Rank
    MIDIbox Newbie
  1. Hi, i am trying to optimize something in the code of my midibox to be able to do some nice backspins with my dj-controller. It got the following setup: stm32f4 discovery board 1x DINX4 Encoders connected via DINX4 Custom written MIOS app I use encoders with mounted jogwheels to create relative CC-midimessages for usage in MIXXX. If i do a fast backspin (should be 30CC val1) with the jogwheel, the board seems to be not capable of processing these fast movements. It is only creating midimessages if the speed of the jogwheel already decreased. Additionally values for the wrong direction (30CC val127) appear: <<< Backspinn start >>> [9799.634] be 1e 01 Chn#15 CC# 30 = 1 [9799.670] be 1e 7f Chn#15 CC# 30 = 127 [9799.748] be 1e 7f Chn#15 CC# 30 = 127 [9799.807] be 1e 01 Chn#15 CC# 30 = 1 [9799.838] be 1e 7f Chn#15 CC# 30 = 127 [9799.878] be 1e 01 Chn#15 CC# 30 = 1 [9799.891] be 1e 01 Chn#15 CC# 30 = 1 [9799.926] be 1e 7f Chn#15 CC# 30 = 127 [9799.965] be 1e 01 Chn#15 CC# 30 = 1 [9799.980] be 1e 01 Chn#15 CC# 30 = 1 [9799.996] be 1e 01 Chn#15 CC# 30 = 1 [9799.999] be 1e 01 Chn#15 CC# 30 = 1 [9800.029] be 1e 01 Chn#15 CC# 30 = 1 [9800.047] be 1e 01 Chn#15 CC# 30 = 1 [9800.068] be 1e 01 Chn#15 CC# 30 = 1 [9800.091] be 1e 01 Chn#15 CC# 30 = 1 [9800.095] be 1e 01 Chn#15 CC# 30 = 1 [9800.116] be 1e 01 Chn#15 CC# 30 = 1 [9800.143] be 1e 01 Chn#15 CC# 30 = 1 [9800.178] be 1e 01 Chn#15 CC# 30 = 1 [9800.223] be 1e 01 Chn#15 CC# 30 = 1 <<< Jogwheel stopped rotating >>> I think the wrong values are related to the lack of debouncing of encoders as described in the thread below: thread I already tried some tweaks for some faster processing but these approaches are more trial-and-error based, as i think i havent understood all aspects of the scheduling via freertos. But i guess i understood the nice MIOS-Flowchart from the wiki. These were my approaches: Change priority of the TASK_Hooks to higher value (but I think it does not make sense...) Try to call vApplicationTickHook via a MIOS timer every 100us as it is usually only called every 1ms ( is this right?) Optimize SRIO for fast speed:  MIOS32_SRIO_ScanNumSet(3);  MIOS32_SPI_TransferModeInit(MIOS32_SRIO_SPI, MIOS32_SPI_MODE_CLK1_PHASE1, MIOS32_SPI_PRESCALER_8); As you can see i tried to some dirty things, but so far, there was no improvement. So i got two questions: Is it possible to put some more processing ressources on the processing of the encoder-signals? (Scheduling, using GPIO-Interrupts by connecting the encoders to J5, ... ) Or is the STM32F4 already running on fastest speed to process everything as fast as possible? Thank you,  Julian
  2. LEGO DJ-Midicontroller

    Just a simple DJ-Midi-Controller: 1xSTM32F4 Core 1xCustom Core Baseboard 1xCustom DINX4
  3. I compiled my own code from source and added these debug-commands... As u said i forgot to take them out... i think it will work if i take them out again. I was just confused as they didnt appear in MIDI-OX and they didnt confused traktor on my windowsmachine.   Anyway..Thank u TK!
  4. Hi !   im trying to build a cheap cdj-styled usb-mp3-player with a raspberry and i went into trouble with the midi-messages from my STM32F4-Core Midibox. I got some pitchfaders, buttons and encoders which i want to use to test MIXXX(a DJ-SW)-performance. On my windows-machine everything works like a charm with Traktor.   I receive the messages with the  amidi -p hw:1,0,0 -d command. hw:1,0,0 is the adress of the midibox. For the pitchfaders (midipitch-message) i receive 3 bytes as desired. I use the SendPitchBend-Command for that.   For Buttons (MIOS32_Send_CC) i receive lots of junk with the right message at the end: F0 00 00 7E 32 00 0D 40 42 75 74 74 6F 6E 20 38 20 67 65 64 72 75 65 63 6B 74 00 F7 BE 08 7F It should be (Channel 15 CC 08 Value 0x7F)   For encoders (MIOS32_Send_CC too) there are also lots of junk bytes in the message: BE 1E 7F F0 00 00 7E 32 00 0D 40 45 6E 63 6F 64 65 72 20 30 3A 20 31 00 F7 In this case the right Message is at the beginning: (Channel 15 CC 30 Value 0x7F)   How to get rid of that junkbytes? MIXXX works fine on the pitchfaders but it cant read the buttons and encoders. I already tried to compile my app without  MIOS32_USB_MIDI_USE_AC_INTERFACE 1 as i need that setting for windows but there was still the junkbytes in it.   Anyone experiend something like this on Linux? How to get rid of these junkbytes? For me the junkbytes doesnt make any sense. But they are always the same at the specific buttons and encoders....  
  5. (Beginner) Where is the hex-file?

    ah ok, sry , got it , thank you Thorsten
  6. Hi all,   just want to ask a basic question which isnt answered by the wiki... I successfully build the MIOS32-App-Skeleton in Eclipse: But im wondering where the hex-file is to upload it via the MIOS-Studio Or did i missed a step in the eclipse config? The Build-folder looks like this:   greets   Julian  
  7. Connecting encoders without DIN?

    Encoders should work directly on the DIN via this ngc script: ENC n=1 sr=1 pins=0:1 type=detented1 EVENT_ENC id= 1 type=CC range=0:127 enc_mode=Inc41_Dec3F ports=1111100000001000   Look at this topic:
  8. Help on Basic NGC Button-Events

    Thank you Thorsten for implementing this ! Its working like a charm and does exactly what i was thinking about ! :smile:   Tested it for all the pins with some buttons and encoders and its working. :phone: Sry i cant test the matrix-Scan as i dont have one...   But i got some questions left: 1. As the id-mapping for the scs-ports beginns now at 1 , what happens if i would connect additional DINs? Continuing at id=17? additional, not topic-related questions: ( 2. Dont want to ask for a new feature again, ... but is it possible to build a NG-Application with something like a default NGC, that the people at the workshop dont need to solder the sd-card interface? Of course i could compile one with some custom fixed-config code, but maybe i just overlooked that "Avoid-SD-Card"-Feature )  :pinch: ( 3. Got some odd connection Problems since yesterday, but they started BEFORE i installed your pre-Version. So they arent related to this pre-Version... )
  9. CORE_STM32F4 connection Bug?

    Hallo zusammen,   von einem auf den anderen Tag konnte ich mich vermeintlich nicht mehr mit dem MIOS-Studio  auf den STM32F4 connecten. Es erschien der "No response from MIOS8 or MIOS32 core! Check MIDI IN/OUT connections... " Fehler. Ich überprüfte alles, konnte aber auch keinen Fehler finden.   Im Midi-In erscheint: [40933.790] f0 00 00 7e 32 00 0f 4d 49 4f 53 33 32 f7 Ich tippte dann einfach mal "help" als Kommando ein und stellte fest, das der Hilfetext erschien. Weitere Tests ergaben das soweit auch alles andere funktioniert wie gewohnt. :question:   Woran kann das liegen? Hatt jemand ein ähnliches Verhalten bereits beobachten können? Bug?   Beste Grüße Julian
  10. Help on Basic NGC Button-Events

    I really understand this, as im not into the firmware you´ve wrote. I just looked after the shiftregisterstuff and saw that you wrote a superfast dma-based solution  :phone:     A DIN/DOUT Emulation for these ports would be nice. In my approuch i would like to use only DIN to connect as much as possible variable input stuff (buttons/encoders) to the core. So for "me" the best solution would be the possibility to choose if J10A/B would be DIN or DOUT. But, as you said before, im not sure if that would be easy to implement as J10A is usually the input and J10B the output of the SCS... The codesolution looks nice!   About the presentation: It will be a free presentation for the guys from http://studio-eins.net/ (with the credits to your page). My plan is to show/educate them how easy and cheap it is to build your own custom midi controler with just the STm32F4 board. Therefor it would be better if no DIN is needed.
  11. Help on Basic NGC Button-Events

    Yep, im going to build some DINs, but it would be nice if the build in IO could be used in a variable way too. ( Like Variable Encoders and Buttons on J10A/B ) This would be nice for very simple midi-controlers without the need for any additional boards. With the buildin DIN and AIN you could already build a nice controler: -16buttons/8Encoders -8Pots   Im going to a presentation about midibox for some non-electronics-people in nuernberg and it would be cool as start to use only the STM32F4-board,some wiring and a small NGC-Script to build a little and cheap USB-midicontroler. Just to get into the whole thing :smile:   ( I dont find any Feature Request List )
  12. Help on Basic NGC Button-Events

    Wohoo it works ! :) Thank you Thorsten.   For the wiring of the inputstuff im fixed to the SCS-schematic? So i cant put a encoder on the digital-Inputs of two buttons and vice verca? And how can i use the J10B for connecting Buttons/Encoders? Cant find any documentation about it. Otherwise i need to build a DIN...
  13. Help on Basic NGC Button-Events

    Hey Thorsten,   There is still no function :(   Normally there should be a feedback in MIOSstudio if a midimessage is sent, right?    My current Testcode: # Reset to default RESET_HW # the SCS should emulate button/enc functions in main page SCS soft1_button_emu_id=2000 EVENT_BUTTON id=2000 type=CC chn=1 cc=17 range=0:127 ports=1111000000000000 # Misc. Configuration DebounceCtr 20 I connected a button at D0 (PE8 at STM) according the SCS-Schematics: http://ucapps.de/midibox_ng/mbng_scs.pdf So Id=2000 should be PE8?   Any other ideas what could be wrong?   Screenshot of MIOSStudio: