All Activity

This stream auto-updates   

  1. Today
  2. understanding the .ngc code

    It's getting late now but... Can I apply two different sysex strings to a toggle switch? For example Select track 1= F0 00 01 06 16 E0 18 10 F7 Deselect track 1= F0 00 01 06 16 E0 18 01 F7 The switch is in the last 10/01 at the end of the string.   Having a look through the info in the morning. If I find what I need I will share how to apply it     (EDIT) just found this in "First steps"    Surprise me!  Our last experiment with a single button ends with a small surprise: change the EVENT_BUTTON statement to:  EVENT_BUTTON id=1  fwd_id=LED:1  button_mode=OnOnly \              type=SysEx stream="0xf0 0x00 0x00 0x7e 0x32 0x00 0x0d 0x40 0x57 0x6F 0x77 0x21 0xf7" \              lcd_pos=1:1:1 label="Button #%3i: %3d"  ...and have a look at the MIOS Terminal while pressing the button... ;-)  Ok, this demonstration should also show you, that it's possible to send SysEx streams, and that multiple lines in the configuration file can be concatenated to a single command with the backslash (\) character.  This needs to be expanded for a dual function toggle switch so it needs an on & off string.  
  3. understanding the .ngc code

    I have managed to set up bome's midi translator tonight and try a few things out as I built my mb_mf but the 10mhz crystal wont be here until next week. The correct sysex string for the oled coming from my daw software is this F0 00 01 06 16 12 00 00 00 73 74 72 69 6E 67 73 F7 this hex is ascii for strings: 73 74 72 69 6E 67 73 the header is different to what the pdf told me, however I will try this out next week as a command from mios studio.   I did see there was another thread asking TK if it was possible to map these sysex commands to individual oled displays but there was no follow up on this and I did post on that particular thread the other day to see if it had been resolved.  As i know the strings involved in generating the "track name" on the display it will allow me to use this on each new track.  i am hoping that when TK pops in again this weekend he may take 5 mins just to answer on this. I have most of the .ngc code down now and have been busy writing things ready to test next week. Most of the casework has been designed and i will cut it on the cnc machine and laser cutting system in work next week as well.   only a few holdups now!! Thorsten you crazy german genuis dude. what do you say??? sysex strings of track names to the displays...?? thanks
  4. Yesterday
  5. MIDIbox SEQ V4 Release + Feedback

    @lp1977thanks for the information! Problems are understood and fixed in: @sis.tmjust tried at my side, it works! (and sometimes I'm surprised what can be done without special consideration in the sources ;-) assign track to CV in LFO page, set the ExtraCC# to 16..23 16 will send to CV channel #1, 17 to channel #2, etc - which means: with the CC number you can address the CV channel you would like to use as LFO output Best Regards, Thorsten.
  6. Sammich UK PSU

    If the PSU is heavy, then it has a wound transformer in it, so it is a linear PSU. If it is light, then it is switching as the components are much smaller (also sometimes containing a small transformer). Very few of linear ones are also regulated, but they do exist. You should measure something near the rated voltage with a multimeter. Better to load it with a 1k THT resistor. If the voltage is wildly different then it is not regulated. The current capacity of a switching PSU is much higher than for a linear PSU of the same size. Anything over a few hundred mA will be a switching PSU.
  7. Sammich UK PSU

    How can i test if that power supply is linear and regulated ? They sent one, but it isnt the one in the image and it is pretty small too.
  8. Sammich UK PSU

    I use a 12/5v Iomega PSU and it works pretty well.
  9. Last week
  10. MIDIbox SEQ V4 Release + Feedback

    Hi @TK. I am having a blast with the Midibox and the cv expansion eurorack boards made by Midiphy. I was trying to get lfo working on a cv channel but it seems this can't be done at the moment? @Hawkeye had a check at the code and it seems that the current lfo is note based per step and can't be used for a lfo out to a cv channel i a nice flowing way. If this is possible i would really love to have this to get more fun with lfo's and CV to my eurorack in the future. Maybe i am doing somehting wrong and it already can be done but at the moment i am scratching my head :) Cheers, Niels    
  11. midiphy Eurorack Expander Modules

    Thanks Peter for checking this out. I will post a request for it :) Have a nice weekend/beer!
  12. midiphy Eurorack Expander Modules and @latigid on just had a look in the code to see what is really going on in seq_lfo.c - as a short conclusion, if a "note lfo" is used, the lfo value is rounded to an integer value between 1 and 127 to reflect a MIDI note - so even if this was put out via AOUT, that is probably not what you would want in a CV scenario (a more or less "stepless" continuous LFO waveform). Probably it would be best to ask TK. in the main SEQ V4 thread for a CV LFO expansion with non-note-steps, if possible, we'd also vote for that expansion, of course :)! Best regards and have a nice weekend! Peter
  13. midiphy Eurorack Expander Modules

    Evening Andy, Too bad, i thought it was something simple to fix. Yep tried notes, different CC values. It should be possible to implement because when i go to the CV calibration screen and set the calibration to wave then i get some kind of lfo and this works but not suited for my purpose ofcourse :) Cheers! Niels
  14. midiphy Eurorack Expander Modules

    Hi Niels, I am also confused, tried the other day with @Hawkeye to get an LFO going but I don't know how.  It would be interesting if you could get it working with a regular CC or MIDI note track then try to change the port to AOUT. Maybe a few notes are needed in the track? Sorry that I can't help! Best, Andy  
  15. midiphy Eurorack Expander Modules

    Hi All, I am breaking my head to get a lfo out to a cv port. I read the forum and this question has been answered earlier but still i don't understand. I am creatng a new CC track on AOUT channel 1 , i init the track and set FX -> LFO to on . I am wondering what the next step will be because whatever i try nothing happens with the CV on channel 1. Do i have to put the CC value to something on the track? I also read the manual but i am stil stuck. Many thanks! Niels    
  16. The HAARP, an Hardware Advanced Arpeggiator.

    Not easy to explain, but I can imagine it ;-) F.
  17. The HAARP, an Hardware Advanced Arpeggiator.

    Always about the RSF, there was already an OFFSET Pot which shift the notes over the timeline, it moves all the notes in the range of +/- the arpeggio length minus 1. It changes the starting Note. So I added an option for the RSF which is "RSF follows OFFSET". When enabled the RSF becomes relative to the OFFSET, it moves with the notes on OFFSET changes and each note value keeps its resting state , disabled the RSF is static and resting steps always the same independently from the OFFSET and it's not always the same notes which are off. Maybe not clear but video will explain all that better ;) Best regards Bruno
  18. The HAARP, an Hardware Advanced Arpeggiator.

    No hurry! Take care down there! F.
  19. The HAARP, an Hardware Advanced Arpeggiator.

    Yes but I left the country, I've got the HAARP with me to work on at night but I'm somewhere in an hotel in Africa, connection is not good. So when I will be back home...
  20. The HAARP, an Hardware Advanced Arpeggiator.

    Damn! You're lightning fast in coding! GREAT THING! Will you also demo this feature with a short video?! :-p Really really appreciate this! F.
  21. The HAARP, an Hardware Advanced Arpeggiator.

    Done! // Voice Structure typedef union { struct { u8 ALL[1+(sizeof(notestack_item_t)*ARP_NOTESTACK_SIZE)+8+1+7+6+3]; }; struct { u8 notestack_len; notestack_item_t notestack_items[ARP_NOTESTACK_SIZE]; u32 resting_steps[2]; // Resting Step Feature(RSF) requested by FlavioB ;) arp_par_func_t func; arp_par_timing_t arp; arp_par_trans_t trans; arp_par_vel_t vel; }; } arp_voice_t; Then this is how it works: The selected step for Resting Step Feature(RSF) is the one with grey background, you can move this selection with the encoder. (Initially the encoder was used for TEMPO, but tempo is the altered function of the encoder now(with ALT button), and RSF is the main function of the encoder) Pushing the encoder(switch) is toggling the RSF for the selected step. then a white bar appears at the bottom of the velocity and the semitone becomes grey. HOME button + Encoder Switch is clearing all the Resting Steps. Note: If an HID keyboard is connected: Left/Right Arrow for selection. Up/Down Arrow or Enter for Toggling Del/BackSpace to Clear All ... And this is not a legend, it already works ;) Voilà! PS: Shooting a picture of a TFT with an iPhone is a bad thing ;) Colors are really better in real :) Best regards Bruno
  22. understanding the .ngc code

    thanks thomas, i ordered the correct ones in the beginning, i got sent totally different things. I found some on ebay after got them coming tomorrow.  
  23. The HAARP, an Hardware Advanced Arpeggiator.

    Hey Bruno! That's very good news! And thanks for crediting me for the input :-) That's really sweet! I definitely want the desktop version of HAARP as soon as you release it. DIY or already assembled (preferred, but not mandatory, as I have a good friend who's doing DIY for me and himself). THANK YOU! F.
  24. MIDIbox SEQ V4 Release + Feedback

    Hi, I posted this in the Midiphy SEQ V4+ troubleshooting thread but after a bit of conversation, it seems the topic is better suited to this feedback thread, as it could be bug related.  Original post for more details:  Basically I've come across a couple issues: 1)  When removing the SD card while the SEQ V4+ is powered on, all of my push buttons become unmapped, losing matrix assignments, although the encoder turns do remain mapped. Since the MBSEQ_HW.V4 file is not reloaded upon SD re-insertion (according to the MBSEQ_HW.V4 section of the user manual at:, the push buttons remain unmapped and unusable until I reload the release package midiphy_rh MBSEQ_HW.V4 with MIOS Studio, issue reset command with MIOS Studio, or power cycle the SEQ V4+ with the SD Card installed.   2)  Exporting songs, tracks, groups, or patterns to .MID files (Utility -> Disk -> MIDI Files -> Export) causes a Hard Fault. Pretty much anything I try to export results in either a Hard Fault with an address such as "PC=0x08049b0c" or "08049b5e", or the unit will just freeze with the "Exporting G_T_ to /MIDI/___.MID" notification on the OLED screen. This requires a hard power cycle on the V4+. I provided an example session with basic generic patterns I whipped up, but the crash/freezing happens with any session, large, small, or freshly created.    I guess I'm just curious if these two things happen to anyone else with a standard issue Midiphy RH V4+ w/VGT6 chip, or if it is specific to my build.  Everything else seems to be working great.   MIOS Studio query data: Operating System: MIOS32 Board: MBHP_CORE_STM32F4 Core Family: STM32F4xx Chip ID: 0x10076413 Serial: #1D0027001851373337323532 Flash Memory Size: 1048576 bytes RAM Size: 196608 bytes MIDIbox SEQ V4+.095 (C) 2018 T. Klose   Thanks to everyone for their support and welcoming comments. I'm new to the Midbox forum and the Midibox universe, in general.    
  25. understanding the .ngc code

    Hi! I made the same mistake recently. If it helps, i found some on aliexpress which seems compatible with MidiBox_NG: I ordered a pair as samples 2 days ago. I don't expect them soon but i'll keep you updated when they arrive.   Thomas  
  26. Troubleshooting midiphy SEQ v4+

    Bruno is right; the 1MB flash confirms the correct VGT6 chip.
  27. Troubleshooting midiphy SEQ v4+

    It's a VGT6.
  28. Troubleshooting midiphy SEQ v4+

    The waveshare is installed in the case so I'd need to disassemble it to look at it.  This is what I see in MIOS Studio query window: Operating System: MIOS32 Board: MBHP_CORE_STM32F4 Core Family: STM32F4xx Chip ID: 0x10076413 Serial: #1D0027001851373337323532 Flash Memory Size: 1048576 bytes RAM Size: 196608 bytes MIDIbox SEQ V4+.095 (C) 2018 T. Klose       Thanks for the response. I'll get a sample together and post in the release feedback thread.
  29. Load more activity