All Activity

This stream auto-updates   

  1. Yesterday
  2. Mbox SID LCD "freezing" because of Bankstick?

    Great that you soved it!
  3. Oops, Silly me, an issue was already opened on the GitHub repo site : Maybe better to focus efforts there. Julien
  4. Hey Phatline, Thanks for the quick answer. No, I just tried to compile the first tutorial project in apps/tutorials/001_forwarding_midi and the app skeleton in apps/templates/app_skeleton. Both projects give the same error. Thanks, Julien
  5. do you compile a standard app? or some own programmed? (> you get that message by every app you want to compile?) (i also use ubuntu - and for me its always pain in the ass - to get it running > all the librarys you have to install... luckely i dont have to fresh install my OS only once a few years...)
  6. Hello everyone, I am completely new to MIDIbox. I am trying to get the first tutorial to compile under Ubuntu 18.04 for Core 32 STM32F4 and get the following error message :   > make -s Creating object file for strtol.c /home/sojastar/Documents/Programmation/MIOS32/mios32/programming_models/traditional/strtol.c:147:19: error: expected ')' before '(' token  _DEFUN (_strtol_r, (rptr, nptr, endptr, base),                    ^~                     )   This is from a fresh ( probably faulty ) install of the toolchain : I first cloned the git repo for MIOS32 then installed the latest arm toolchain following these instructions : I did add the toolchain path to my PATH. Any advice or pointer would be greatly appreciated ! Thanks ! Julien
  7. Adding CS-line to AINSER8

    Thank you very much! I'll give it a try. 
  8. Affinity designer Ipad - using for panel design?

    Solved, either they implemented it with the last update, or I was to stupid to scroll. Now it's a perfect app for designing cases or panels without an ipad.
  9. Mbox SID LCD "freezing" because of Bankstick?

    Nee das is nich das Problem steht auch auf der Bankstick Seite, lag doch an meinem DinX. Solved, Bankstick not the problem, seems like some bad DinX contacts 
  10. Adding CS-line to AINSER8

    Additional notes: could be that you rely on 5V output - in this case change MIOS32_BOARD_PIN_MODE_OUTPUT_PP to MIOS32_BOARD_PIN_MODE_OUTPUT_OD, and add a 1k pull-up to 5V to this pin. And if J10A is already used for SCS inputs (standard), just take J10B.D0 (pin index #8) Best Regards, Thorsten.
  11. Adding CS-line to AINSER8

    Another modification in mbng_file_c.c is required where the number of CS lines is hardcoded (actually you should have seen the error message...) I put an example which works at my side into the demo/mbng_ainser_with_3_cs branch, see: Best Regards, Thorsten.  
  12. Mbox SID LCD "freezing" because of Bankstick?

    I guess the easiest solution would be to put in the other six missing banksticks!? At least on my MBSID that seems to work just fine...
  13. First I have to told you that I am using 2 Banksticks, just the first(A0 512) and the last(A7 256) I did this to store ensembles in the last one and it didn't seem to be a problem. Both BS are recocgnized, for the last I just have to scroll trough the empty banks. This seemed to be all working fine til the point I play the patch via Menu and scroll between the patches in the first Bank. The LCD freezes (and it looks like the whole Box freezed) but the sound is still playing and I can still change the patches via the Jogwheel/poti. For recreating the issue I turn the Mbox on and play with the Menu, if I plug out the Bankstick-module, nothing freezes. 
  14. Why does the HC165 even work?

    I did some tests with this. I connected a DIO-Board to my keyboard and the DIO-board to the core with jumper wire => no HCT541. I powered the DIO with 3V3 from the DISCO-Board. The result: It's running fine. No issues. I checked the clock with my oscilloscope. It looks very clean. Also no issues here.  So, I think I'll leave away the HCT541 for my applications and run everything from 3V3.  //edit: I've connected an encoder to the DIO-board. Works also fine.
  15. Adding CS-line to AINSER8

    Dear TK, I undo all changes and added the lines as you suggested. Unfortunately I can not get it working. I edited the ainser.h like this: s32 AINSER_Init(u32 mode) { MIOS32_BOARD_J10_PinInit(0, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); s32 status = 0; int module, pin; // currently only mode 0 supported if( mode != 0 ) return -1; // unsupported mode #if AINSER_SPI_OUTPUTS_OD // pins in open drain mode (to pull-up the outputs to 5V) status |= MIOS32_SPI_IO_Init(AINSER_SPI, MIOS32_SPI_PIN_DRIVER_STRONG_OD); #else // pins in push-poll mode (3.3V output voltage) status |= MIOS32_SPI_IO_Init(AINSER_SPI, MIOS32_SPI_PIN_DRIVER_STRONG); #endif // SPI Port will be initialized in AINSER_Update() num_used_modules = AINSER_NUM_MODULES; #if AINSER_NUM_MODULES > 8 # error "If more than 8 AINSER_NUM_MODULES should be supported, the ainser_enable_mask variable type has to be changed from u8 to u16 (up to 16) or u32 (up to 32)" #endif #if AINSER_NUM_MODULES > 8 # error "If more than 8 AINSER_NUM_MODULES should be supported, the ainser_muxed_mask variable type has to be changed from u8 to u16 (up to 16) or u32 (up to 32)" #endif for(module=0; module<AINSER_NUM_MODULES; ++module) { num_used_pins[module] = AINSER_NUM_PINS; // ensure that CS is deactivated AINSER_SetCs(module, 1); AINSER_EnabledSet(module, 1); AINSER_MuxedSet(module, 1); AINSER_NumPinsSet(module, AINSER_NUM_PINS); AINSER_DeadbandSet(module, MIOS32_AIN_DEADBAND); // clear all values for(pin=0; pin<AINSER_NUM_PINS; ++pin) { ain_pin_values[module][pin] = 0; } previous_ain_pin_value = 0; } return status; } [] static s32 AINSER_SetCs(u8 module, u8 value) { switch( module ) { case 0: return MIOS32_SPI_RC_PinSet(AINSER_SPI, AINSER_SPI_RC_PIN_MODULE1, value); // spi, rc_pin, pin_value case 1: return MIOS32_SPI_RC_PinSet(AINSER_SPI, AINSER_SPI_RC_PIN_MODULE2, value); // spi, rc_pin, pin_value case 2: return MIOS32_BOARD_J10_PinSet(0, value); #if AINSER_NUM_MODULES > 3 # error "CS Line for more than 2 modules not prepared yet - please enhance here!" #endif } But when I now connect the Chipselect to PE8, which is D0 on J10A, nothing happens. Any idea? Thanks, Chris
  16. what would your perfect control surface look like and do?

    Sorry. forgot. I would also like a control surface specifically for the tasks that you do while tracking  live performances such as in a live room or isolation booth. as again the type of plugins and controls you use doing this job will often be different to that when doing other things. for example. when tracking you may want just a little amount of processing and estimated effects but not all the bells and whistles that you may need when mix engineering also for live performance, you will have much of the effects and processing jobs done and will not always need that much control over many of the plug ins that you use during tracking or mix engineering so sure, different console for each would make more sense  but perhaps not that easy to design as each individual has different preferences but also due to the limitations of what protocols are available
  17. Last week
  18. Troubleshooting midiphy SEQ v4+

    Hmm, 2000 posts    How is pin 1 bodged? Do you measure +5V to it? I would bridge to the empty J89 socket, pins 3/4. You can see the wider trace to it in your image.
  19. Troubleshooting midiphy SEQ v4+

    You'll get it, don't worry :).
  20. Troubleshooting midiphy SEQ v4+

    @latigid on Hi, I did swap cables but it didnt change anything for the better. Suddenly also de Leds on the JA Pcb started to flash randomly O.o. So maybe the cables are the reason but with only the Lemec LH connected they work fine and dont do anything bad (will check them again). Here are some pictures of the ICs. For IC 1 i had to scrape the protection away because i removed the pads (rings) on 3 pins of the resistor network (Pin 1 (dot) ,5 ,7) Will check the parallel inputs on  IC3 now but its so strange that suddenly the JA board leds begin to do crazy stuff :) pretty confusing for a noob like me :D Thanks for your help - will definitely have to tip you some beer when I have finished this beatuy - already learned a lot about this project...
  21. what would your perfect control surface look like and do?

    Ideally ii prefer to use control surfaces to control the many features in DAW   perhaps one for composing / sound design, that has controls for my favorite synths / samplers / virtual instruments another for mix engineering, using absolute rotary encoders that use LED rings for visual reference and another for live performance (as i can't afford some of the classic synths / organs etc.   I would like the option to be able to control all my favorite plugins which i generally use while mix engineer  perhaps another one that i can use for mastering if all is done inside the box that is   That would be my ideal studio  control surfaces that i use every time, so i get used to how they look, how they feel and each element that is used to control      
  22. Adding CS-line to AINSER8

    Thanks for chiming in!  Is it really so easy? :-) Thanks! I'll try it!!
  23. Troubleshooting midiphy SEQ v4+

    As before, the common cause here is floating DIN inputs resulting from poorly soldered resistor networks (cold joints or incorrect polarity). Another possibility is that pins of the 165 are shorted together. Imagine if the clock line was shorted to an input, like pin 2 to pin 3, then you might get a weird feedback loop, or if pin 1 was shorted to pin 2, which would shift in the inputs on every clock. Did you swap the cables?
  24. Troubleshooting midiphy SEQ v4+

    A personal taste thing, but you can always make it your own :).
  25. Adding CS-line to AINSER8

    You don't need to enhance mios32_spi, just control the additional pin directly from AINSER_SetCs E.g. let's assume that J10.D0 is unused so far, then add to AINSER_Init(): MIOS32_BOARD_J10A_PinInit(0, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); and to AINSER_SetCs: case 2: return MIOS32_BOARD_J10_PinSet(0, value); Best Regards, Thorsten.
  26. what would your perfect control surface look like and do?

    control sourface for what? DAW? Synth? Record-Session? Ableton? ... it depends...   For in Depth Edit: Endless-Encoders with "end-break" + 2toRGB Color Ledrings with at leas 16 LEDs + LCD above it to show the parameter-name + CC-Automation + CC-Patch-Storage. or Normal Mouse and or Touchscreen if its for example Ableton   For Live Play: (all 8 or so most used Parameters for a gig) Potis and Faders for Liveact-Action well arangent and unique in feel look and size ---so you can drive it blind... i found out that there are only a few importent Parameters, to mouch of Parameters, make it to complicated...  
  27. what would your perfect control surface look like and do?

    I've made it already :-) 9x Encoders + 1 Potentiometer for master-volume 9x OLEDs 9x Faders 3x9 Button-rows 9x RGBLED-bars next to the faders 9x RGBLED underneath each encoder I don't need anything more!
  28. Load more activity