Antichambre
-
Posts
1,291 -
Joined
-
Last visited
-
Days Won
101
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by Antichambre
-
-
On 03/10/2019 at 2:54 PM, TK. said:
A downstripped MBHP_CORE_STM32F4 module in Eurorack format would be nice-to-have as an alternative solution to the Euroreceiver - maybe with a SCS (6 buttons, encoder, display) - this would allow to run MBCV which gives us a lot of LFOs, Envelopes, sequencers, modulation matrices, etc.
Best Regards, Thorsten.
On 03/10/2019 at 11:09 PM, TK. said:Must-have requirements:
- STM32F407VG (1MB flash)
- SCS with 6 buttons, 1 encoder and 1 GLCD (so that we can also use the display as a scope)
- 1 MIDI IN, 1 MIDI OUT
- USB Device
- SD Card
- SRIO (J8/9)
- J19 for AOUT
- 50mm depth
- HP doesn't matter as long as it still fits into the Pod40X case together with the Expander modules
Optional:
- up to 3 additional MIDI IN/OUT (could also be provided as an optional module)
- USB Host
- 4 on-board LEDs
- Audio-DAC
Potential extension modules:
- SRIO based encoder/ledring modules
- AINSER64 module (with at least 8, but maybe 3x8 INs?) - inputs should be buffered, protected and maybe also amplified and level-shifted for +/- 5V
Such a module could also cover MBNG for script based processing.
Best Regards, Thorsten.
On 03/10/2019 at 4:04 PM, Antichambre said:I'm working on something like this, I try to do not exceed 50mm depth. I need it for the HAARP,
And adapt the SCS to the euro format is also a good idea, @latigid on ?
I plan to create another CS based on the work I made for @Phatline with a pot for each parameter and TFT screen, like I did for the HAARP.Best regards,
BrunoI did it... And it works.
- STM32F405RG (1MB flash), dipCoreF4 based.
- 2 MIDI IN, 2 MIDI OUT
- USB Device/Host(OTG FS)
- USB Host(OTG HS in FS mode)
- SD Card(Micro)
- SRIO (J8/9)
- J19 for AOUT
- J15A for serial LCD, 2 CS lines.
- J18 CAN
- J4 I2Cx2
- J5 ADCx2
- 2 Leds
- User/Reset Button.
- USB/EURO Power, auto switching with Euro Prior.
- Power switch acts on both power source.
- 44mm depth
- 12HP
Voilà!
Best regards
Bruno
-
The infamous ADSR bug of the SID ! ;)
-
1
-
-
-
A clearer log:
Quote^C
inet-stick@inetstick:~/c/CCL-V0$ make
rm -f project.hex
Creating object file for app.c
Creating object file for seq.c
Creating object file for main.c
Creating object file for strtol.c
Creating object file for tasks.c
Creating object file for list.c
Creating object file for queue.c
Creating object file for timers.c
Creating object file for port.c
/home/inet-stick/midibox/MIOS32-master/FreeRTOS/Source/portable/GCC/ARM_CM3/port.c: In function 'prvPortStartFirstTask':
/home/inet-stick/midibox/MIOS32-master/FreeRTOS/Source/portable/GCC/ARM_CM3/port.c:282:1: warning: stack usage computation not supported for this target [enabled by default]
Creating object file for heap_4.c
Creating object file for startup_stm32f4xx.c
Creating object file for mios32_srio.c
Creating object file for mios32_din.c
Creating object file for mios32_dout.c
Creating object file for mios32_enc.c
Creating object file for mios32_lcd.c
Creating object file for mios32_midi.c
Creating object file for mios32_osc.c
Creating object file for mios32_com.c
Creating object file for mios32_uart_midi.c
Creating object file for mios32_spi_midi.c
Creating object file for mios32_iic_midi.c
Creating object file for mios32_can_midi.c
Creating object file for mios32_iic_bs.c
Creating object file for mios32_mf.c
Creating object file for mios32_sdcard.c
Creating object file for mios32_enc28j60.c
Creating object file for mios32_timestamp.c
Creating object file for mios32_bsl.c
Creating object file for mios32_sys.c
Creating object file for mios32_irq.c
Creating object file for mios32_spi.c
Creating object file for mios32_i2s.c
Creating object file for mios32_board.c
Creating object file for mios32_timer.c
Creating object file for mios32_stopwatch.c
Creating object file for mios32_delay.c
Creating object file for mios32_ain.c
Creating object file for mios32_usb.c
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:75:9: note: #pragma message: USB HS Host supported
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:84:9: note: #pragma message: USB HS Host supported
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:79:11: warning: 'USB_HOST_Process_Delay' defined but not used [-Wunused-variable]
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:101:12: warning: 'USB_HS_HOST_Process_Delay' defined but not used [-Wunused-variable]
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c: In function 'USBH_InterfaceDeInit':
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:1921:9: warning: 'class_status' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c: In function 'USBH_InterfaceInit':
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:1887:10: warning: 'class_status' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c: In function 'USBH_ClassRequest':
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:1963:9: warning: 'class_status' may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c: In function 'USBH_Handle':
/home/inet-stick/midibox/MIOS32-master/mios32/STM32F4xx/mios32_usb.c:2002:9: warning: 'class_status' may be used uninitialized in this function [-Wmaybe-uninitialized]
Creating object file for mios32_usb_midi.c
Creating object file for mios32_usb_com.c
Creating object file for mios32_usb_hid.c
Creating object file for mios32_uart.c
Creating object file for mios32_iic.c
Creating object file for mios32_can.c
Creating object file for printf-stdarg.c
Creating object file for misc.c
Creating object file for stm32f4xx_adc.c
Creating object file for stm32f4xx_can.c
Creating object file for stm32f4xx_crc.c
Creating object file for stm32f4xx_cryp.c
Creating object file for stm32f4xx_cryp_aes.c
Creating object file for stm32f4xx_cryp_des.c
Creating object file for stm32f4xx_cryp_tdes.c
Creating object file for stm32f4xx_dac.c
Creating object file for stm32f4xx_dbgmcu.c
Creating object file for stm32f4xx_dcmi.c
Creating object file for stm32f4xx_dma.c
Creating object file for stm32f4xx_exti.c
Creating object file for stm32f4xx_flash.c
Creating object file for stm32f4xx_fsmc.c
Creating object file for stm32f4xx_gpio.c
Creating object file for stm32f4xx_hash.c
Creating object file for stm32f4xx_hash_md5.c
Creating object file for stm32f4xx_hash_sha1.c
Creating object file for stm32f4xx_i2c.c
Creating object file for stm32f4xx_iwdg.c
Creating object file for stm32f4xx_pwr.c
Creating object file for stm32f4xx_rcc.c
Creating object file for stm32f4xx_rng.c
Creating object file for stm32f4xx_rtc.c
Creating object file for stm32f4xx_sdio.c
Creating object file for stm32f4xx_spi.c
Creating object file for stm32f4xx_syscfg.c
Creating object file for stm32f4xx_tim.c
Creating object file for stm32f4xx_usart.c
Creating object file for stm32f4xx_wwdg.c
Creating object file for usbd_core.c
Creating object file for usbd_ioreq.c
Creating object file for usbd_req.c
/home/inet-stick/midibox/MIOS32-master/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c: In function 'USBD_GetString':
/home/inet-stick/midibox/MIOS32-master/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c:845:18: warning: comparison between pointer and integer [enabled by default]
/home/inet-stick/midibox/MIOS32-master/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c: In function 'USBD_GetLen':
/home/inet-stick/midibox/MIOS32-master/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c:863:17: warning: comparison between pointer and integer [enabled by default]
Creating object file for usbh_core.c
Creating object file for usbh_hcs.c
Creating object file for usbh_ioreq.c
Creating object file for usbh_stdreq.c
Creating object file for usb_core.c
Creating object file for usb_dcd.c
Creating object file for usb_dcd_int.c
Creating object file for usb_hcd.c
Creating object file for usb_hcd_int.c
Creating object file for usb_otg.c
Creating object file for diskio.c
Creating object file for ccsbcs.c
Creating object file for ff.c
Creating object file for file.c
Creating object file for seq_bpm.c
Creating object file for seq_midi_out.c
Creating object file for mini_cpp.cpp
Creating object file for freertos_heap.cpp
arm-none-eabi-gcc: error: .ld: No such file or directory
/home/inet-stick/midibox/MIOS32-master/include/makefile/common.mk:144: recipe for target 'project_build/project.elf' failed
make: *** [project_build/project.elf] Error 1
inet-stick@inetstick:~/c/CCL-V0$The problem is the red line, seems it doesn't find the toolchain or something with ".ld" extension from the toolchain, but PATH and GCC_PREFIX are set properly.
I tried to compile @Phatline's app on my OSX, worked fine, today I tried under Windows 10 Pro, works fine too.Quoterm -f project.hex
Creating object file for app.c
Creating object file for seq.c
Creating object file for main.c
Creating object file for strtol.c
Creating object file for tasks.c
Creating object file for list.c
Creating object file for queue.c
Creating object file for timers.c
Creating object file for port.c
/Volumes/DATA/Bruno/Developper/myMIOS32/FreeRTOS/Source/portable/GCC/ARM_CM3/port.c: In function 'prvPortStartFirstTask':
/Volumes/DATA/Bruno/Developper/myMIOS32/FreeRTOS/Source/portable/GCC/ARM_CM3/port.c:282:1: warning: stack usage computation not supported for this target [enabled by default]
Creating object file for heap_4.c
Creating object file for startup_stm32f4xx.c
Creating object file for mios32_srio.c
Creating object file for mios32_din.c
Creating object file for mios32_dout.c
Creating object file for mios32_enc.c
Creating object file for mios32_lcd.c
Creating object file for mios32_midi.c
Creating object file for mios32_osc.c
Creating object file for mios32_com.c
Creating object file for mios32_uart_midi.c
Creating object file for mios32_spi_midi.c
Creating object file for mios32_iic_midi.c
Creating object file for mios32_can_midi.c
Creating object file for mios32_iic_bs.c
Creating object file for mios32_mf.c
Creating object file for mios32_sdcard.c
Creating object file for mios32_enc28j60.c
Creating object file for mios32_timestamp.c
Creating object file for mios32_bsl.c
Creating object file for mios32_sys.c
Creating object file for mios32_irq.c
Creating object file for mios32_spi.c
Creating object file for mios32_i2s.c
Creating object file for mios32_board.c
Creating object file for mios32_timer.c
Creating object file for mios32_stopwatch.c
Creating object file for mios32_delay.c
Creating object file for mios32_ain.c
Creating object file for mios32_usb.c
/Volumes/DATA/Bruno/Developper/myMIOS32/mios32/STM32F4xx/mios32_usb.c:75:9: note: #pragma message: USB HS Host supported
/Volumes/DATA/Bruno/Developper/myMIOS32/mios32/STM32F4xx/mios32_usb.c:81:9: note: #pragma message: USB HS Host supported
Creating object file for mios32_usb_midi.c
Creating object file for mios32_usb_com.c
Creating object file for mios32_usb_hid.c
Creating object file for mios32_uart.c
Creating object file for mios32_iic.c
Creating object file for mios32_can.c
Creating object file for printf-stdarg.c
Creating object file for misc.c
Creating object file for stm32f4xx_adc.c
Creating object file for stm32f4xx_can.c
Creating object file for stm32f4xx_crc.c
Creating object file for stm32f4xx_cryp.c
Creating object file for stm32f4xx_cryp_aes.c
Creating object file for stm32f4xx_cryp_des.c
Creating object file for stm32f4xx_cryp_tdes.c
Creating object file for stm32f4xx_dac.c
Creating object file for stm32f4xx_dbgmcu.c
Creating object file for stm32f4xx_dcmi.c
Creating object file for stm32f4xx_dma.c
Creating object file for stm32f4xx_exti.c
Creating object file for stm32f4xx_flash.c
Creating object file for stm32f4xx_fsmc.c
Creating object file for stm32f4xx_gpio.c
Creating object file for stm32f4xx_hash.c
Creating object file for stm32f4xx_hash_md5.c
Creating object file for stm32f4xx_hash_sha1.c
Creating object file for stm32f4xx_i2c.c
Creating object file for stm32f4xx_iwdg.c
Creating object file for stm32f4xx_pwr.c
Creating object file for stm32f4xx_rcc.c
Creating object file for stm32f4xx_rng.c
Creating object file for stm32f4xx_rtc.c
Creating object file for stm32f4xx_sdio.c
Creating object file for stm32f4xx_spi.c
Creating object file for stm32f4xx_syscfg.c
Creating object file for stm32f4xx_tim.c
Creating object file for stm32f4xx_usart.c
Creating object file for stm32f4xx_wwdg.c
Creating object file for usbd_core.c
Creating object file for usbd_ioreq.c
Creating object file for usbd_req.c
/Volumes/DATA/Bruno/Developper/myMIOS32/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c: In function 'USBD_GetString':
/Volumes/DATA/Bruno/Developper/myMIOS32/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c:845:18: warning: comparison between pointer and integer [enabled by default]
/Volumes/DATA/Bruno/Developper/myMIOS32/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c: In function 'USBD_GetLen':
/Volumes/DATA/Bruno/Developper/myMIOS32/drivers/STM32F4xx/v1.1.0/STM32_USB_Device_Library/Core/src/usbd_req.c:863:17: warning: comparison between pointer and integer [enabled by default]
Creating object file for usbh_core.c
Creating object file for usbh_hcs.c
Creating object file for usbh_ioreq.c
Creating object file for usbh_stdreq.c
Creating object file for usb_core.c
Creating object file for usb_dcd.c
Creating object file for usb_dcd_int.c
Creating object file for usb_hcd.c
Creating object file for usb_hcd_int.c
Creating object file for usb_otg.c
Creating object file for diskio.c
Creating object file for ccsbcs.c
Creating object file for ff.c
Creating object file for file.c
Creating object file for seq_bpm.c
Creating object file for seq_midi_out.c
Creating object file for mini_cpp.cpp
Creating object file for freertos_heap.cpp
-------------------------------------------------------------------------------
Application successfully built for:
Processor: STM32F405RG
Family: STM32F4xx
Board: MBHP_DIPCOREF4
LCD: ili9361
-------------------------------------------------------------------------------
arm-none-eabi-size project_build/project.elf
text data bss dec hex filename
81854 136 64280 146270 23b5e project_build/project.elf
20000000 D __ram_start
2000fba0 B __ram_end
Seems to be a Linux subtlety... Someone?
-
Not sure for a 9090 but generally a drum sound has no sustain and triggers on NoteOn, Note duration does not matter, but NoteOff must be received between 5 and 10ms after, just to permit the same NoteOn to be received again.
-
Id pin(PA10) is floating externally but pulled up internally(cpu), connected to ground externally for host mode. Core must be restarted on each Dev/Host switching. There's no jumper or other option on PA10 it's directly connected to CPU pin.
So check continuity between R3(Dev/Host switch) and the Core, this line should be broken you just have to find where... R3 is not really necessary and can be replaced by a piece of wire. -
3 hours ago, Blatboy said:
I think I need to add a dedicated midi controller keyboard that has no internal sounds to keep it a little easier to manage. However, my SQ80 with it’s polyphonic after touch is pretty great as a master keyboard. It just gets a little confusing sometimes as it also makes it’s own sounds haha.
You can set your SQ80 in LOCAL OFF, Keyboard will act to MIDI OUT but not to SQ80 Sound engine. And use it as a Master Keyboard. Of course internal sounds can still be played from MIDI In and internal sequencer
MASTER PAGE > Set KBD=MIDI(instead of BOTH).
Best regards
Bruno-
1
-
-
Salut Thierry,
I'm not the best to answer this question, I don't know NG, but after reading its concept page, it seems NG supports up to 2 velocity sensitive keyboards (like known from MIDIbox KB)
So i will say NG ;)
Best regards
Bruno -
Hi,
Home-made desktop version finished.
It's not perfect, but it's a good idea of the final version.
Best regards
Bruno -
34 minutes ago, spinal said:
If it is configured as OFF it is just like I said (TRS ring is the 5V power supply).
If it's configured as OFF the signal just stays in idle state, it does not switch as a power rail, it stays a logic signal. I suppose this was made strong, depends on what is inside, logic buffer, transistor, cpu pin directly, depends on the current it can support;
What I wanted to do here, is avoid any interface box and get IN and OUT, and it works fine with a Merris.
With your solution you just recreate this interface box(regular optocoupled midi input) and power it with a logic line from the pedal and without Output.
Here the original and well known diagram of a regular MIDI IN and Thru.
Your diagram is just a part of it ;) -
9 hours ago, spinal said:
This post is just a feedback because I couldn't find anyone that actually built it.
I just built the midi din to TRS jack from this schematic: https://imgur.com/gallery/Md24LCE?s=sms .
The only information missing was that the 5V on the diagram must be connected to the ring of the TRS jack. 5v comes from the pedal receiving midi datas.
And yes, it works perfect with my Strymon Iridium.Hello, this diagram is a regular MIDI input stage, it's not a passive circuit and must be powered, if you connect the 5V to the ring you will get issue when the pedal send data. The ring is the TX point which has idle state at 5V but 0V on data transmit and use it as a power source is also not a good idea, it's a CMOS/TTL signal.
-
Yep, noise generator is right, the design for SID control is old but still very complete. If you follow the diagram and he "how to" you will quickly get some result, and get some good vibes from your SID, with CC etc...
You can also find some clean board at Modular Addict. CORE8 + SID Module.
Migrate the firmware to an ARM like arduino is an hard work, and you will not be able to use the MIOS Studio which is very usefull to program your patches etc...
Best regards
Bruno
-
IIC output is using 2 buffers, the STM buffer set to 1024, the 16F84 buffer which sized to 96 bytes.
I'm not sure but IIC is faster than MIDI then for a file size of 4104 bytes the STM will send 1024 bytes at a time and the PIC will overflow, not because of buffers sizes but just because it can't forward the data fast enough.
To check but the buffer of the PIC can't be bigger... You can try to reduce the speed of the IIC but not too much cause it will delay all messages, just enough to avoid overflow.
Or the best idea is to use a regular MIDI Out for your Yamaha FM ;) -
Good song and beautiful pictures...
Drones caused a lot of security issues some years ago. I can understand that rule too. Seven years ago here in my area a drone hindered rescue by helicopter from doing their job properly endangering the boat crew stranded on the coast.
But some have authorisation, those ones are friend of mines, from school. They are lucky people cause it's now their job ;)
https://www.pixnfly.com/en/
-
Hello...
I hope everyone who is stranded at home has found a good occupation!
Here some picture of the Desktop version enclosure.
Shape of the side face, I found some ebony for the wood sides ;)
Check of the assembly before paint.
Some more pictures in the HAARP album.Best regards
Bruno -
Hello,
I haven't got an Analog Four but based on the manual, you have to choose how velocity is affected to the volume VELOCITY TO VOL, page 16.
For CC the MIDI implementation is in the appendix D.
Have a good WE.
Bruno -
Just now, FantomXR said:
Superbe!
...Here you come a knockin knockin on my door... ;) -
So for a complete module it's 8+1+5(elastomer)= less than 14$ => 224$ for 16x16 matrix
Really Not Bad! Congrats...
-
Hi!
It seems great!
Can you share the links needed to build the whole thing and the BOM? To evaluate the the total price of 1 module.
Best regards
Bruno -
Hi All,
Here you can see all the necessary boards to build the HAARP.
Best regards
Bruno-
3
-
-
1 hour ago, SynthularModulus said:
who is actually still selling boards?
https://modularaddict.com/manufacturer/midibox
1 hour ago, SynthularModulus said:Is anyone selling flashed PIC chips?
Just ask someone here to do it for you when you're ready...
Best regards
Bruno -
Hi Mike,
I will ask for an UPS or DHL shipping on Monday, I know they continue to work...
Cause you really need it, it will be better for next demo ;)Do you intend to create a dedicated case or will you leave it like that?
I improved the VELOCITY part of the HAARP into an "ANIMATION" part which now applies to Velocity and CC but only 1 CC. So, as I suspected, the CC-Looper could be a very good partner for the HAARP.
I really have to make a video like this for the HAARP, but my English spoken will be a disaster lol.
Best regards
Bruno-
1
-
-
10 minutes ago, Zam said:
Hello Bruno
Look great !
If only I got this 4 years ago, my midibox design would have the core directly on the main board...
Bravo
Zam
Maybe time to update your design ;)
Merci!
Bruno -
Hi Mike,
There's no "switch" or define for this.
It was made like this to match the old PIC DOUT pinout.///////////////////////////////////////////////////////////////////////////// //! temporary help array to mirror a byte //! (could be provided as MIOS32 help function later) ///////////////////////////////////////////////////////////////////////////// // DOUT bits are uploaded in reversed order compared to PIC based MIOS, and // especially compared to the order on DIN registers // Most applications would have to convert this - therefore it's already done // by MIOS32_DOUT_* functions // mirroring could work with: // u8 mirror_u8(u8 b) // { return ((b&0x01)<<7) | ((b&0x02)<<5) | ((b&0x04)<<3) | ((b&0x08)<<1) | ((b&0x10)>>1) | ((b&0x20)>>3) | ((b&0x40)>>5) | ((b&0x80)>>7); } // bit this would be a bit slow, e.g. for SR copy routines - therefore we use a table based approached: // the table has been generated with: // perl -e 'for($b=0; $b<256; ++$b) { printf("0x%02x,", (($b&0x01)<<7) | (($b&0x02)<<5) | (($b&0x04)<<3) | (($b&0x08)<<1) | (($b&0x10)>>1) | (($b&0x20)>>3) | (($b&0x40)>>5) | (($b&0x80)>>7)); }; printf("\n");' const u8 mios32_dout_reverse_tab[256] = { 0x00,0x80,0x40,0xc0,0x20,0xa0,0x60,0xe0,0x10,0x90,0x50,0xd0,0x30,0xb0,0x70,0xf0, 0x08,0x88,0x48,0xc8,0x28,0xa8,0x68,0xe8,0x18,0x98,0x58,0xd8,0x38,0xb8,0x78,0xf8, 0x04,0x84,0x44,0xc4,0x24,0xa4,0x64,0xe4,0x14,0x94,0x54,0xd4,0x34,0xb4,0x74,0xf4, 0x0c,0x8c,0x4c,0xcc,0x2c,0xac,0x6c,0xec,0x1c,0x9c,0x5c,0xdc,0x3c,0xbc,0x7c,0xfc, 0x02,0x82,0x42,0xc2,0x22,0xa2,0x62,0xe2,0x12,0x92,0x52,0xd2,0x32,0xb2,0x72,0xf2, 0x0a,0x8a,0x4a,0xca,0x2a,0xaa,0x6a,0xea,0x1a,0x9a,0x5a,0xda,0x3a,0xba,0x7a,0xfa, 0x06,0x86,0x46,0xc6,0x26,0xa6,0x66,0xe6,0x16,0x96,0x56,0xd6,0x36,0xb6,0x76,0xf6, 0x0e,0x8e,0x4e,0xce,0x2e,0xae,0x6e,0xee,0x1e,0x9e,0x5e,0xde,0x3e,0xbe,0x7e,0xfe, 0x01,0x81,0x41,0xc1,0x21,0xa1,0x61,0xe1,0x11,0x91,0x51,0xd1,0x31,0xb1,0x71,0xf1, 0x09,0x89,0x49,0xc9,0x29,0xa9,0x69,0xe9,0x19,0x99,0x59,0xd9,0x39,0xb9,0x79,0xf9, 0x05,0x85,0x45,0xc5,0x25,0xa5,0x65,0xe5,0x15,0x95,0x55,0xd5,0x35,0xb5,0x75,0xf5, 0x0d,0x8d,0x4d,0xcd,0x2d,0xad,0x6d,0xed,0x1d,0x9d,0x5d,0xdd,0x3d,0xbd,0x7d,0xfd, 0x03,0x83,0x43,0xc3,0x23,0xa3,0x63,0xe3,0x13,0x93,0x53,0xd3,0x33,0xb3,0x73,0xf3, 0x0b,0x8b,0x4b,0xcb,0x2b,0xab,0x6b,0xeb,0x1b,0x9b,0x5b,0xdb,0x3b,0xbb,0x7b,0xfb, 0x07,0x87,0x47,0xc7,0x27,0xa7,0x67,0xe7,0x17,0x97,0x57,0xd7,0x37,0xb7,0x77,0xf7, 0x0f,0x8f,0x4f,0xcf,0x2f,0xaf,0x6f,0xef,0x1f,0x9f,0x5f,0xdf,0x3f,0xbf,0x7f,0xff };
This helper was not implemented. And the problem is that MIOS32_DOUT_SR_xx use this array but not the MIOS32_DOUT_Pin_xx
But you use the right method ;) except that it works only for pin 0 to 7.
If you want to do it on all the pins you have to include the SR number just implent something like this.
e.g.u32 PIN_REVERT(u32 pin) { u8 num_sr = pin>>3; // divide by 8 pin %=8; // modulo by 8 return (u32)((num_sr<<3) + (7-pin)); }
then use it:
MIOS32_DOUT_PinSet(PIN_REVERT(pin), value);-
1
-
midiphy Eurorack Expander Modules
in MIDIbox SEQ
Posted
It was to complete the discussion about an Euro Core module, discussion which was started here. There's no mix, just a parenthesis. This is fully compatible with your Euro Modules and even made for.
Have a good Sunday my friend.