Jump to content

TK.

Administrators
  • Posts

    15,247
  • Joined

Everything posted by TK.

  1. I'm also out of ideas - I will try this by myself this weekend and share the code if it works. Best Regards, Thorsten.
  2. yes - as usual the encoder type is configurable, so that you could also use a non-detended encoder if you prefer. you will need 4 digits for the value after the dot (optional for higher precision). The size of the digits isn't standardized, please order them first from your favorite webshop. You will need two DOUT shift registers (two 74HC595) and one DIN (one 74HC165) Best Regards, Thorsten.
  3. TK.

    MIDIO128 V3

    All DOUT and DIN shift registers (SR) which are not assigned to a M8x8 matrix can be used as conventional DIN/DOUT operations (means: 8 pins per shift register). This also means, that if you would only use a single DOUT to drive the selection pattern for the matrices which are scanned by multiple DINs, you can use all other DOUTs for other purposes. yes! :) Thats correct. If a 32x32 matrix would really be required, I could add this as an additional option, but currently I don't see the need. With v3.005b we've two matrix modes. In normal mode ("Norm") the "Arg" (Argument) is used as note offset, the note number is calculated as "Arg + <pin-number>" In the new mapped mode ("Map") the "Arg" (Argument) isn't used, instead individual note numbers and channels are derived from tables which are stored in your DEFAULT.MIO file on SD Card. If you don't find the tables in the .MIO file yet, please store the current configuration from the control surface, or type "save default" in the MIOS Terminal. Best Regards, Thorsten.
  4. Hi, such LCDs are usually more expensive than LCDs with common parallel interface. Only advantage: it's easier to connect multiple LCDs Best Regards, Thorsten.
  5. TK.

    MIDIO128 V3

    Ok, so I understand from your reply that you are flexible enough to use 8x8 matrices. yes! To make it clear: here again the link to the beta version which supports note value assignments... http://www.ucapps.de/mios32/midio128_v3_005b.zip Please update to this version, otherwise you can't configure the note values. Best Regards, Thorsten.
  6. Alright, thanks! Btw.: for those who grew up with the metric system: cable length was 60 cm, now it's ca. 25 cm 38 cm, now it's ca. 17 cm Best Regards, Thorsten.
  7. yes, this would be very interesting! Which cable length did you use before, which length is it now? What is the difference between a TL07x and TL08x? Best Regards, Thorsten.
  8. These are good news! I haven't expected the bad solder joints, but they saved the life of your LCD! :) Best Regards, Thorsten.
  9. TK.

    MIDIO128 V3

    In order to avoid unnecessary confusion, I've to ask you some questions before answering your questions in detail. Since the firmware currently only supports 8x8 matrices, I would like to know why you are using a 32x32 configuration? I could add this as an option, but design wise this was probably a bad idea, since it increases the latency by factor 4 The 1024 inputs could be scanned much faster with 16 DINs (the DOUTs will output the same pattern in a 8x8 configuration and therefore could still be shared) The current version is v3.005 Only with the beta version v3.005b which is linked in the article above (and not linked at the MIOS32 download page) it's possible to configure individual note values. I'm still waiting for feedback before an official release... but you could try it as well. Configuration from the CS: change to the M8x8 page, select the matrix (1..16), and the input pin (1..64) - then you can set an individual note value and MIDI channel for this input. This approach could be helpful to find out the order in which the values have to be entered. But once you found out the order, you may want to enter the remaining values in the spreadsheet which is stored on SD Card (note that the values can also be entered in decimal format like in your table) Best Regards, Thorsten.
  10. Fine! :) No, this MIDI monitor function doesn't get use of the LCD, it optionally prints incoming MIDI events into the MIOS terminal for debugging purposes. no it's unlikely that the 74HC595 has been damaged if the LCD has been connected incorrectly. J15B is intended for a second LCD (e.g. as used by the MIDIbox SEQ application). MIDIO128 doesn't initialize the second LCD, therefore it won't work. yes! Yes, but from my experience it's more likely that the LCD won't work anymore, therefore I recommended to replace it. No, the pots control analog voltages, and it's normal that some squares appear after power-on, before the LCD has been initialized. My assumption is, that "something" has been fried in the digital logic, therefore just order a new one - it will save you a lot of unnecessary debugging time. Note that you could already configure the MIDIO128 application by editing the configuration file which is stored on SD Card. Best Regards, Thorsten.
  11. The bassline sequencer is up&running! :smile: Specs: each CV channel has a dedicated sequencer (-> 8 bassline sequencers are running in parallel) typical 303ish entry with Key/Octave/Gate/Glide/Accent optionally sequenced values can be entered directly (fader at the left side) for direct CV modulation independent from note values 8 sequences per channel, each sequence has 32 steps EnvMod and Accent are forwarded to the modulation matrix selectable resolutions (e.g. 96th, 48th, 32th, 16th... but also triple and dotted measures) selectable gatelength (used for all steps) The sequence can be entered with the Lemur template and it's transfered to MBCV via NRPN messages: The configuration is done on a special page: To ensure highest flexibility, VCF and VCA control for EnvMod and Accent isn't hardwired to certain CV channels. Instead, these parameters are routed through the modulation matrix. This has two advantages: any CV channel can pick up the current Accent and EnvMod value from any other channel (e.g. you could also control LFO modulation with this) And it allows to finetune the modulation depth - because depending on the analog synth which is used, this definitely is required for best results: Here a short demo (I removed the drums by intention): Again the Kraftzwerg is used with it's own filter; VCO, VCA and VCF are controlled by MBCV. And btw.: the digital background noise seems to come from the synth itself - it's time to disable the internal MIDI interface, because there is no need for it anymore ;) http://www.ucapps.de/mp3/midibox_cv/mbcv_seq_demo1.mp3 Best Regards, Thorsten.
  12. The voltages should be ok, and it's normal that the outputs are at 0V after power-on. Could you please continue reading here: Greevous had similar issues, I gave him some hints which are also relevant for you. He solved this by testing different cables (in general: than shorter than better), and it seems that also switching to 3.3V level (instead of 5V) helped, although I would recommend to test the 5V option first. Sidenote: this information is only relevant for MBHP_CORE_STM32 users. For MBHP_CORE_LPC17 I'm using a 74HCT541 based buffer which simplifies the level-shifting (makes it less troublesome) Best Regards, Thorsten.
  13. I'm missing some details... e.g. what did you already try out, which effects did you notice? In order to reduce the source of errors, I would start with a simple SPI transfer routine which neither uses the DMA, nor interrupts. Just poll for incoming bytes and send a debug message (to check the content). I would also add a possibility to observe the SPI Status register (SPI1->SR, called SPI_SR in the manual). E.g. you could print out the content with a MIOS Terminal command, or whenever a MIDI note has been received (from the MIOS Studio keyboard) - see tutorials how to implement this. Did you already check if the data pins are correctly configured? (e.g. no short circuit) I noticed a minor bug in your modifications: GPIO_InitStructure.GPIO_Pin = MIOS32_SPI0_MISO_PIN; GPIO_Init(MIOS32_SPI0_MOSI_PORT, &GPIO_InitStructure); [/code] MISO_PIN configured for MOSI_PORT and [code] GPIO_InitStructure.GPIO_Pin = MIOS32_SPI0_MOSI_PIN; GPIO_Init(MIOS32_SPI0_MISO_PORT, &GPIO_InitStructure); MOSI_PIN configured for MISO_PORT You haven't noticed an effect since MOSI_PORT and MISO_PORT are identical (GPIOA) Best Regards, Thorsten.
  14. First of all ensure that the AOUT_NG module is selected in the CV configuration page. You haven't mentioned this detail, therefore the reminder! I would like to know how you've configured the J19 port? It needs 1k pull-ups and the J26 jumper should be set to 5V Additionally: did you already try the "testaoutpin" command in MIOS Terminal? Just enter this command, it will output some instructions how to test each individual connection between Core and MBHP_AOUT module! :) Best Regards, Thorsten.
  15. Danke fuer den ausfuehrlichen Bericht! Der war auch wirklich noetig, denn erst jetzt kann ich mir ein genaueres Bild von dem Problem machen. Der PIC ist sehr wahrscheinlich defekt, zumal er auch noch heiss wurde (was nicht normal ist). Kann es sein, dass die digitalen Bausteine mit einer zu hohen Spannung versorgt wurden? Bspw. 5V und 12V verwechselt? Bevor Du nun einzelne Komponenten austauschst, sollte vorher die Ursache unbedingt aufgeklaert werden! Der Quarz schwingt nur zusammen mit dem Oszillator, der im PIC eingebaut ist - deshalb tut sich da wohl nichts mehr. Es stellt sich auch die Frage, ob die restlichen Chips ebenfalls einen Schlag wegbekommen haben. Moegliches Szenario: wenn bspw. die MIDIbox nicht lief wenn alle Module angeschlossen waren, koennte es sein, dass diese bei einer Ueberspannung einen Kurzschluss (zumindest auf auf 5V) erzeugt haben. Als Du dann die Module entfernt hast, hat zunaechst das LCD die volle Spannung abbekommen. Nachdem es dann ebenfalls entfernt war, hat es den PIC zerschossen. Ich wuerde Dir empfehlen, zumindest einen neuen PIC, den/die 74HC165 und vielleicht auch ein neues LCD zu bestellen. Die Teile gibt es am guenstigsten bei Reichelt, doch da der PIC auch noch programmiert werden muss, ist es wahrscheinlich einfacher, bei Mike zu bestellen (schreibe ihm einfach eine email) Ich druecke die Daumen, dass die DACs noch funktionieren (wuerde ich erst bestellen, wenn die restliche Schaltung wieder laeuft) Gruss, Thorsten.
  16. Hallo Bernhard, das Problem liegt entweder am Schwingkreis (Quarz oder 33pF Kondensatoren), oder am PIC selbst. Sobald Spannung anliegt, sollte an den beiden OSC Pins (13 und 14) eine 10 MHz Sinusschwingung zu sehen sein. Ueberpruefe nochmal die Loetstellen. Jenachdem, welchen Quarz Du verwendest, koennte es auch sein, dass die Beinchen das Metallgehaeuse beruehren? Falls hier alles in Ordnung ist, koennte vielleicht der PIC defekt sein? Was hast Du damit in der letzten Zeit angestellt? Bzw. hat die MIDIbox von heute auf morgen ploetzlich nicht mehr gebootet, oder setzte die Firmware aus nachdem Du etwas bestimmtes angeschlossen hast, oder es einen Kurzschluss gab? Eigentlich ist der PIC ja ein ziemlich robuster Chip, doch man kann ihn auch schnell mal zerschiessen, wenn man bspw. ueber laengere Zeit eine negative Spannung an die Pins legt... Manchmal laesst sich ein PIC wiederbeleben, indem man den Bootloader nochmal neu aufspielt, doch es koennte dann sein, dass einige IO Pins nicht mehr funktionieren. Gruss, Thorsten.
  17. Hi Johnc, in order to check which application is running, just press the Query button - it will display the application name + some additional infos. E.g. in the snapshot of your first posting, the application name was "Bootloader 1.007". Now it should be "MIDIO 128 V3.005" You can also type "help" in MIOS Terminal so that the application sends a list of available commands. Could you please try both and confirm that this is working? LCD: it can't be excluded that the LCD has been damaged while you connected the pins reversed! Beside of the polarity the only important things are the contrast pot, and that jumper J15_S is connected correctly (it should select the 5V option) Best Regards, Thorsten.
  18. Unfortunately the SHX8 module somehow doesn't fit into the concept of having the complete set of modulators for each CV. I would also have to reduce the update rate dramatically - regardless if CV outputs are modulated or not because each SHX8 output has to be refreshed each mS. So: no go for this project, it would be another project with limited capabilities, focused on more CV outputs. This is how the minimum hardware option could look like: ;) More advanced configurations will be demonstrated once this project leaves the alpha state. But I'm sure that no 8bit core will be involved - just connect an AOUT/AOUT_LC/AOUT_NG module to the MBHP_CORE_LPC17 module and you are already done. Another option will be to edit parameters via 2x20 LCD, 5 buttons and 1 encoder directly connected to J10 of the core module. More buttons/encoders/pots/faders/whatever etc...: I will plan this later once the sound engine is final! Best Regards, Thorsten.
  19. See also this topic: If you should notice some noise, just insert 10 ohm resistors between the PSU and the analog circuit + el.caps after the resistors. This seems to help! :) Best Regards, Thorsten.
  20. TK.

    MIDIBox 808

    Kogz23 currently works on a new "combined" PCB which can be used for a standalone version. In distance to the original MIDIbox808 design, it will support individual accent volumes (velocity) as well (e.g. for TR909 based drums)! :) Best Regards, Thorsten.
  21. A project with high aims! Hope that you don't expect too much help from my side, without the same hardware (infrastructure) I couldn't help you anyhow. ;) Although you can re-use many routines which already exist, merging and enhancing will be a challenge. You will especially need some good debugging skills to keep an eye on the performance, and I'm sure that you will reconsider some features once you hear the first audible results. Best Regards, Thorsten.
  22. Link to the reply: The reason is very likely because John is using an expired MIOS Studio version. Best Regards, Thorsten.
  23. Hi John, MIOS Studio 2.1 fails to parse the project.hex file and therefore outputs this error message. Could you please try the upload with MIOS Studio 2.2.2? Best Regards, Thorsten.
  24. I will fix this soon, because I would like to control the parameters from a controller (Lemur on iPad) as well! :) Best Regards, Thorsten.
  25. Hi Marxon, according to the way how you are asking I assume that you noticed that the current instrument selection isn't working in Multi mode? I looked into the source code - according to the comments I planned to add a special handling for Multi mode, but the code is missing (instead the L/R selection will be taken, but this makes only sense for Lead/Bassline/Drum engine). Or did you notice something else? The MIDI channel will only be considered during the SID selection. Best Regards, Thorsten.
×
×
  • Create New...