• Content count

  • Joined

  • Last visited

Everything posted by Antichambre

  1. 19" Rack MBFM with extended frontpanel

    But he didn't reply after I don't know if it was working for him. Best regards
  2. The HAARP, an Hardware Advanced Arpeggiator.

      Thank you Guys! :)
  3. midiphy SEQ v4+

    That's what I finally did too, that's what I wanted, it's clearly enough. But it should not be done with the transparent Keycap, the result is bad and ugly. Yes #18 congratulation
  4. The HAARP, an Hardware Advanced Arpeggiator.

    Each panel parameter will have their CC number and an associated modulation CC number, all accessible from the CV In too, it's MENU things.  
  5. The HAARP, an Hardware Advanced Arpeggiator.

    @Hawkeye I just remember that I made the "Force To Scale" as a regular module, for quick implementation and use in any app.
  6. The HAARP, an Hardware Advanced Arpeggiator.

    I will make this code available on next commit, It's also a good practice for me to work on a personal repo before working on the MCAN branch of the official MIOS32 repo. Best Bruno
  7. crimic-live-at-JET-Benefiz-Concert-2019-06-07

    Nice, I remember doing it also in front of all my college for a end-year party, my friend, a very good guitarist, improvised while I had only a drum machine. I hope for you things have changed because for us everyone looked at us with big questioning eyes and the sound manager tended to put us in the wheels. lol Best Bruno
  8. The HAARP, an Hardware Advanced Arpeggiator.

    Hi Peter, There is really no problem. LOOPA and HAARP are more complementary than competitive. Both are "real time" oriented but have different use and operation. (I do not remember if you implemented the "Force To Scale" if it's not the case, it can be a good feature on your machine too.) Internally their process structure are very different, but if you want to know how I coded some parameters, tell me if I can 'help', even if I feel pretentious to say that to someone who codes better than me. There is no competing here, the important thing is to give life to all that and share it. But for sure, it's better if our machines or modules can be complementary. I also look forward to the @Phatline's CC-Looper, here again we are in the complementary. Best regards Bruno  
  9. The HAARP Prototype #001

    From the album The HAARP

  10. The HAARP, The Front Panel Layout

    From the album The HAARP

  11. AINSER sampling rate

    You can try to call the AINSER_Handler with a Timer set at the desired rate,but usually a freertos task is used to call it, and its minimum period is 1ms( 1 / portTICK_RATE_MS ) Check tutorial#012b_ainser_muxed: ///////////////////////////////////////////////////////////////////////////// // This hook is called when an AINSER pot has been moved ///////////////////////////////////////////////////////////////////////////// static void APP_AINSER_NotifyChange(u32 module, u32 pin, u32 pin_value) { // toggle Status LED on each AIN value change MIOS32_BOARD_LED_Set(0x0001, ~MIOS32_BOARD_LED_Get()); // convert 12bit value to 7bit value u8 value_7bit = pin_value >> 5; // send MIDI event MIOS32_MIDI_SendCC(DEFAULT, Chn1, pin + 0x10, value_7bit); } ///////////////////////////////////////////////////////////////////////////// // This task scans AINSER pins and checks for updates ///////////////////////////////////////////////////////////////////////////// static void TASK_AINSER_Scan(void *pvParameters) { portTickType xLastExecutionTime; // Initialise the xLastExecutionTime variable on task entry xLastExecutionTime = xTaskGetTickCount(); while( 1 ) { vTaskDelayUntil(&xLastExecutionTime, 1 / portTICK_RATE_MS); // scan pins AINSER_Handler(APP_AINSER_NotifyChange); } }  
  12. AINSER sampling rate

    This is something easy to do in a regular App, using the AINSER_Handler, but in NG I don't know. Best Bruno
  13. STP16 as alternative to HC595?

    Yes I soldered the TLC5958 (VQFN56) for the OLRE16 like that.
  14. STP16 as alternative to HC595?

    Hot air station is enough.
  15. STP16 as alternative to HC595?

    Yes it's a good chip, I already used it. I confirm it's 90mA for each output. But It's a on/off output. In this range I prefer the TLC5947, it's a 24 outputs(better for RGB leds), chainable, with a 12bits PWM outputs. But it's not the same in code for sure it requires a specific driver.
  16. MCAN

    Hi Thorsten, For the basic mode nothing more than the node number is necessary. It's 3 bits (0...7) then 1 byte is enough Something like this: # define MIOS32_SYS_ADDR_DEVICE_ID_CONFIRM (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd0) // 0x42 to confirm value # define MIOS32_SYS_ADDR_DEVICE_ID (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd1) # define MIOS32_SYS_ADDR_FASTBOOT_CONFIRM (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd2) // 0x42 to confirm value # define MIOS32_SYS_ADDR_FASTBOOT (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd3) # define MIOS32_SYS_ADDR_SINGLE_USB_CONFIRM (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd4) // 0x42 to confirm value # define MIOS32_SYS_ADDR_SINGLE_USB (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd5) # define MIOS32_SYS_ADDR_ENFORCE_USB_DEVICE_CONFIRM (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd6) // 0x42 to confirm value # define MIOS32_SYS_ADDR_ENFORCE_USB_DEVICE (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd7) # define MIOS32_SYS_ADDR_SPI_MIDI_CONFIRM (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd8) // 0x42 to confirm value # define MIOS32_SYS_ADDR_SPI_MIDI (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xd9) # define MIOS32_SYS_ADDR_MCAN_NODE_CONFIRM (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xda) // 0x42 to confirm value # define MIOS32_SYS_ADDR_MCAN_NODE (MIOS32_SYS_ADDR_BSL_INFO_BEGIN+0xdb) Let me 1 day or 2 and I will do the stuff for the Bootloader Updater, as you get the minimum to do, just valid/correct. Except if you really want to do it yourself. Best regards Bruno  
  17. Why does the HC165 even work?

    Yes of course, just check the levels from the datasheet. Just take care if you use encoders, for example I never tried a pec16 with a 3V3 voltage and they are given for 5V.
  18. Why does the HC165 even work?

    DIN and DOUT modules were made a long time ago with HC, more than that with HC and 541(forJ8/9 andJ19) DIN/DOUT modules stay compatibles to all SPI ports. J8/9 J19 and J16 included. HCT version are only 5V(Supply voltage) and J16 is a 3.3V SPI port. But you can use HCT595/165 and remove the 541 on your own design. Keep in mind HCT need 5V supply voltage.
  19. MCAN

    it would be great! :) ... I will definitely go in this direction. Thank you for your answer Best regards Bruno
  20. JU60

    @Zam I just restore then mod a juno 60 for a friend using the juno-66 from tubbutec, it works great! The only critic is that they provide not enough length cable, I was obliged to change them to follow the existing cabling path, I did not change the MIDI I/O cable then cable is straight from cpu to old DCB position(not very good too). But this mod is great and add a lot of features to the juno-60 I highly recommend it to you, do not reinvent the wheel, they made it very well. Best regards Bruno
  21. MCAN

    I decided to add a Basic Id field, 3 bits which will allow 8 Cores on the MCAN Bus. And remove the vman_prio field which was an optional feature. I think it's the best compromise.   struct { // extended u32 none:1; u32 is_request:1; u32 is_extended:1; u32 src_node:7; u32 dst_node:8; u32 app_type:3; // standard u32 basic_node:3; u32 cable:4; u32 type:4; // ports u8 src_port; u8 dst_port; }; } mios32_mcan_header_t; - Message types are always prioritized(type) - We keep the 16 MCAN ports (cable) - 8 chained cores max in the basic mode(basic_id), the basic_node field will not be used in extended mode and replaced by the src_node. Of course this basic_node id will have to be declared in mios32_config.h and different for each core on the buss, value from 0 to 7. Notes: the type of message is always a priority, the cable has priority over the id @TK. What do you think about? Best regards Bruno
  22. daisy chain USB Midibox control surfaces

    I still did not take the time for that... But if i remember well you already tried it ;) oh yes you need it in the NG.
  23. daisy chain USB Midibox control surfaces

    There's an other solution, try to contact @Zam here, he's working on something similar, chaining multiple Core with one Master connected in USB. Best regards Bruno
  24. midiphy SEQ v4+

    You can give him the number #0 not as a null one but as the origin, the source, the root, the base one!