• Content count

  • Joined

  • Last visited

Everything posted by Antichambre

  1. Moving to STM32F7 core?

    Compare the diagram and if some peripheral don't perturb MIOS32 pinout. Seems compatible to DFU so USB pinout should be good but check. you use the DFU(IUSB) or SWDIO to upload bootloader?
  2. MB808 not saving drum patterns

    Yep! Seems to be that one! lol
  3. MB808 not saving drum patterns

    Hi, It should be a 'Bankstick' issue, the EEPROM(24LC256/512) which are inside your machine. check their connection or replace it. Best regards Bruno
  4. Special characters in Label

    Hi, What he wants is to print arrow for example, from the built-in char set. With MIOS function it's very easy, using Char Print and code number. With NG it seems only string are possible. But according to the C ascii table. the 'left arrow' code 0x7e is "~", so using: label="~ %e" works. But for the 'right arrow' the ascii code 0x7f correspond to DEL, which is not usable in a string. Is there a way to print a label using ascii code instead of string in NG? Best regards
  5. MB 6582 PCBs

    Moi je ne connaissais même pas cette petite perle kitch à la française! Un papayou de Carlos encore ouai! Mais ça !? Le plus étonnant est que ça ait pu être déterré depuis le Milwaukee. :)   Splendide! ...End of Off topic.
  6. MB 6582 PCBs

    No don't worry, some of us are in contact with them. Their last facebook post: " We're not dead, just rebuilding. Give us another two weeks or so - a little patience goes a long way. In the meantime: " LOL
  7. Moving to STM32F7 core?

    Direct Memory Access. A feature which permits a peripheral to automatically read/write from/to memory without cpu processing. Something very important for heavy data transfer, for example.
  8. Moving to STM32F7 core?

    It's a lot of work, first a correct Standard Peripheral Library for F7 must be found, on my last research they provided only HAL. According to Thorsten, setting all the DMA is a tricky thing, something I can believe. Best regards
  9. MIDI port name problem SEQ V4 GM5

    Hi Halvor, It's the same on my side. Except that it's not GM5 but HAARP. But peripheral manager is also good, only Mios Studio is wrong. Best regards Bruno
  10. Unable to build MIOS on ubuntu

    Check this refers to the valid repertories.
  11. (FS - EU) MB-6582s

    I don't understand why but I can't see the pictures. Got "Keine Fotobeschreibung Verfugbar" instead.
  12. Midification of a ordinary dj mixer

    Statistically you've got a very small percentage of chance that the mixer's pcbs are separated with Controls only pcb. Exception to the cross-fader which is more often separated to be easily replaced, and usually controls some VCA. All others mechanical controls are generally directly soldered on the active analog board. Like Peter said you will have to sacrifice some of the audio mixer functions for sure, but can be done without definitively destroy the traces and pcbs. With access to the service manual, it's possible to remove the parts(resistors, caps, ICs, etc...) connected to each mechanical controls(pots, faders, buttons) and indicators(Leds, VU, etc..). Next is to find the good candidate... Something like that for me Very cheap one, 99 € , service manual Then: - Separate the controls you need by removing connected parts and use AIN/DIN. - By removing IC13 you can take control to Leds, VU, digits, using a DOUT and the existing flip-flops which will hold the matriced datas. - You can disable or bypass the useless analog stages using wire and audio coupling caps pads, then keep a minimal audio functions and controls for monitoring/cue outputs. - With a AOUT or some CV Inputs, you can reuse the 4 internals VCA, 4 inputs + main/booth stages, then get 4 controlled/trimmed channels with mixed/trimmed outputs options. - You can reuse the internal 5v and embed the MIDIbox platforms and modules. Add USB/MIDI connectors on a separated back plate with 2 screws, that can hide a potential ugly cutout too. First to do is to print the schematics, get coloured pens and hack this behringer stuff on paper ;) Best regards Bruno  
  13. MIDIbox SEQ V4 Release + Feedback

    Another interesting idea would be to synchronize the fx loop as the mutes can be. But more precisely. With a variable rate from the loop length(steps) to the maximum number of steps in the sequence. And the possibility of synchronizing the entry and exit points independently(enabled/disabled). To be able to play with this effect and to always start or/and resume at the right time. Using 2 new parameters: In and Out rates,  value range from Off,1, 2...256. With In limited in software by the loop length and Out by the track length. e.g. Here Loop In is applied when Loop is activated(no sync) and resumed in sync to the measure(16 Steps) just after the Loop is deactivated. Then the Measure restart correctly. // layout: // 00000000001111111111222222222233333333330000000000111111111122222222223333333333 // 01234567890123456789012345678901234567890123456789012345678901234567890123456789 // <--------------------------------------><--------------------------------------> // Global Loop Mode Offset Steps Loop Sync In Sync Out // All Tracks/Step View 15 2 on Off 16 Best regards Bruno
  14. MIDIbox SEQ V4 Release + Feedback

    It's essential for me too. But we will let Thorsten decide and maybe he has a better way than me to get the same result, he knows this firmware by heart much better than me ;)
  15. MIDIbox SEQ V4 Release + Feedback

    In fact it's already the case, the legacy SOLO follows the Track Selection. So you've got it already now with my modifications. If you are talking about the SOLO which is on the BLM, it overrules the Legacy SOLO, then it will be complicated for the user to understand there's two solo system on the same machine. I think it's good like that. But tell me when you have tested it. Another idea is to disable the legacy SOLO for Midiphy version only and implement the second SOLO layer(BLM) by using the SOLO button. Then on a SeqV4+, Track Selection and SOLO will be unlinked. Best regards Bruno
  16. This has to be reported to the Waveshare team for their QC.
  17. MIDIbox SEQ V4 Release + Feedback

    Don't worry I didn't touch to the master version, it's an alternative branch, if Thorsten validates it, he just has to merge those changes to the master. And for the precompiled files I shared here I clearly mentioned that it's not an official version, in red with exclamation marks!!! ;)   @lp1977 Yep like Andy I filed the stem a few before inserting it the first time.  
  18. MIDIbox SEQ V4 Release + Feedback

    @lp1977 I forgot to apply the option#28(Invert Mute Leds) to the 2nd line when it indicates Tracks Mute in Layers Mute Page. I corrected it and refreshed branch and precompiled another time.
  19. MIDIbox SEQ V4 Release + Feedback

    Yep! If you ask yourself why... I'm also unable to give you an answer, I tried both and finally let it like that ;)
  20. Obviously ;) Anyway, this problem is fascinating to follow, what a suspense, we can not wait to discover the outcome ;) I hope it's not too much frustrating for you!
  21. Maybe stupid but... A faulty usb cable? The one you use with LoopA is necessarily different from the one you use directly with the waveshare, so... On sait jamais ;)
  22. MIDIbox SEQ V4 Release + Feedback

    @Rio The mute button behaviours is now an option. Old fashion(default), hold mute button to access Layer page or click alternates between the Tracks an Layers Mute pages. It's Option#34.   @latigid on The second row behaviour is improved for both mute pages access(Option#34). Second row indicates tracks selection for both pages by default and can be changed by option#35 for Layers Mute page , Rows are no more redundant. The branch and release above in the thread had been refreshed. Best regards Bruno  
  23. MIDIbox SEQ V4 Release + Feedback

    The advantage is to keep one hand free for something else during drum parts muting too. Question of taste and Live Act workflow habits, no worry.
  24. MIDIbox SEQ V4 Release + Feedback

    It should change the behaviour of the mute for your version too. Test it and tell me what happens. the 2nd row(Direct tracks selection buttons) workflow is not an issue for your version cause they don't exist on the wilba CS. There's no change for the 1st row(GP buttons) they show exactly the same thing as before.
  25. MIDIbox SEQ V4 Release + Feedback

    Full description is above in the thread ;) I didn't test it with a non Midiphy SeqV4! Here the whole release. !!! This is not official release !!!