Antichambre

Programmer
  • Content count

    926
  • Joined

  • Last visited

Everything posted by Antichambre

  1. 19" Rack MBFM with extended frontpanel

    Better too if you're happy with it and want to share a few. Cheaper for everybody, and just the price of some cheap components more for you. SO package on bottom side sounds good for your CS.
  2. 19" Rack MBFM with extended frontpanel

    @Thomasch it's clear now... Rows are matriced, Columns are not.   I suppose you talk about Vs instead of Vc, and yes it's a ground, you can connect Vs bus to ground or Swithes pin directly to ground, it doesn't matter. You can maybe put all the ICs(DIN/DOUT) on this PCB, and connect your CS directly to the Core. It will be cheaper, it will take less space and limit the number of interconnections.
  3. 19" Rack MBFM with extended frontpanel

    Seems to be matricing... Could you explain how you connected the leds and switches, which example did you take?(There is a lot here, try BLM as keyword search). I don't understand why some of the switches are connected to 3 busses and Vc which seems to be... a ground? it can't be with a matrix connection. :/ There's maybe a misunderstanding, you don't need to connect both 'normally open' terminals, check the datasheet cause they are often internally connected and used for PCB routing ease, anyway you need only one terminal. Seems to miss some diodes for the switches too, there's no pull-up resistors but they are maybe close to the ICs and on an other diagram.   @latigid on is better than me for BLM stuff it might be more clear for him ;)  but @Thomasch better if you explain a few first... Best
  4. 19" Rack MBFM with extended frontpanel

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

      Thank you Guys! :)
  6. Hello, This is an introduction for my new baby, a really funny toy, the HAARP (yes I like conspiracy theory ;) It's a pure MIDIbox Project, just a dedicated CS and some coding. It works with any STM32F4 Core.   Why? Many synths have an integrated arpeggiator, the SH-101 is well known for that, but the available parameters are still limited. There is also some good plug-in I think especially of the Ableton live's one but it's software. So I designed an hardware one, "LIVE" oriented, starting from the @TK.'s arp example. No encoder(except for MENU section Data entry), all parameters are directly accessible and are potentiometers. The screen is a small color TFT with a resolution of 128x160(sorry for picture, colors are better in real). It's 8 independent voices. 8 banks of 8 Presets. Session are saved/loaded from the SD Card. The Arpeggio parameters are divided in 3 sections: First is the TIMING Section (Purple pots): On/Off button, HOLD Button, it holds or releases the Notes in the notestack. The MODE Pot, it's UP, DOWN, UP-DOWN and AS-PLAYED, fr the moment but I will implement more. The RATE, from slowest to fastest, from 4 Bar to 32nd with dotted and Triplet value. The RESYNC, it retriggers the arpeggio, values are the same as RATE parameter. The OFFSET, it will shift left or right the starting step(note). Is Note Stack and MODE dependent. The DELAY, it will delay the whole arpeggio within the step range(duration), is RATE dependent. The GATE, the length of the Note, max is STEP length, is RATE dependent. The SHUFFLE, it will delay all the odd steps, in the range of an half step, is RATE dependent. Second is the TRANSPOSITION Section (Yellow, Orange, Red): Simple Transposition On/Off (Yellow). Simple OCTave Transposition, +/- 10. Simple SEMItone Transposition, +/-12 Repeat On/Off. Repeat, LOOPS number, 1 to 8. Repeat, SHIFTing on each loop, +/-32 semitones. Force to Scale On/Off Force To Scale, SCALE, list is the same as the Force to Scale example from the repo. Force To Scale, ROOT from C to B semitone. Third is the VELOCITY Section. REGEN Pre/Post(Target process) button. REGEN, +/- 100% Target process On/Off. TIME, the time to reach the target value, in PRE initial value is the regenerated value. in POST initial value is the one stored in the Note Stack. TARGET is the targetted value, 0 to 127. RETRIG, if on the TIME is retriggered by the RESYNC parameter.   The main page of the screen represents an octave range, the note color changes depending on the octave, there's a Velocity section on the bottom, it's like a piano-roll. In the code, the arpeggio processing is ready, it remains me to complete the MENU section, I was waiting for the CS PCB to write it, now I can... ;)   This little guy is to much fun, so I can't keep it for me. Then i will propose it to you ASAP. and I hope it will help me to finance some other bigger projects I've got in my back-pocket ;) I will try to make it available in two format, I'm currently working on a PCB for USB host/device, sdCard MIDI etc.. which will fit for both version and will be reuse for other small toys like that. An Eurorack version for the patching addicts. I used a MCP3204(4 channels) instead of a MCP3208(8 channels) for the AINSER, it's an AINSER32. I use only 2 channels for the 16 pots(8Multiplexed lines * 2 channels), it remains 16 analog Inputs which are accessible to connect some CV In Modules, thanks to @Hawkeye for making me think about this. The SRIO Chain is available too, you can connect GATE In (DIN) easily. You will be able to connect the MIDIPHY CV/GATE Out Modules which will be available soon. @latigid on is working on it. MCAN will be available, for an internal MIDI bus within your Eurorack, I reuse the BUS1 and 2 from the Euro Power connector for that purpose.   A Desktop version, for MIDI purpose only(except if i find a way to add some CV/Gate without designing a too much big box).   Voilà! More information will be available soon. For the moment this is a small video I made, I seem a little febrile but it's because I continue to discover it every day.   I really love this little toy, it is very effective and musical, even in LIVE and if the Force To Scale is activated, there's no wrong note ;) Best regards Bruno  
  7. 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
  8. 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.  
  9. 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. https://www.dropbox.com/s/q8tais6dmtcnny8/force_to_scale.zip?dl=1
  10. 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
  11. 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
  12. 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  
  13. The HAARP Prototype #001

    From the album The HAARP

       
  14. The HAARP, The Front Panel Layout

    From the album The HAARP

     
  15. 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); } }  
  16. 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
  17. STP16 as alternative to HC595?

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

    Hot air station is enough.
  19. 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.
  20. 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  
  21. 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.
  22. 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.
  23. MCAN

    it would be great! :) ... I will definitely go in this direction. Thank you for your answer Best regards Bruno
  24. 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