Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Phatline last won the day on May 29

Phatline had the most liked content!

About Phatline

  • Birthday 02/04/1983

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  • Interests
    Jam, Soundmorph, Subtraktiv, Program, Design, soldering, and all else about frequency > live > life > nature > earth > building

Recent Profile Visitors

6,854 profile views

Phatline's Achievements

MIDIbox Guru

MIDIbox Guru (4/4)



  1. ok next step... "Mute" & Solo Buttons needs some external DINX and DOUTX boards (in order to make the SRIO-Gain short)
  2. interested in stm32f4 and discovery.
  3. interested in tms32f4 and 2 midi io . rest i dont need.
  4. pcb arrive, soldered 4 off them (12 channels) - the 4 others i make a nother time. (24ch in total) the display drivers from Andy work great again! the midibox code is working, the max for live patches too. (at least for this state i am happy to get automaticly the Channels names, and the Macronames!!! hell yeah!)
  5. Lets get started... Goal is a midicontroller for Ableton live, at the beginning as simple midicontroller, maybe later to transfair Labels via max4Live to the controller... it will not a midibox-ng script, it will be a own program based on the MIOS-platform. Hardware first, i designed a 6xSSD1306 + 9 Encoder Board, that is scaleable --- i will use 8-10 off it, its documented here (incl gerbers): http://wiki.midibox.org/daw-encoder-display i already have the Motorfaders and the ready soldered and flashed mf-ng boards, i will controll them with a stm32F4 board... which also handles the encoders and displays. in order to drive the displays stable, i use latigid-ons display driver board. - this is also the offical discuss topic for this project (which is linked in the wiki)
  6. i guess not the pyboard uses a 12Mhz external crystal? and Mios32 needs? look at the Pinout: http://wiki.midibox.org/lib/exe/fetch.php?media=antichambre:pinout_compare_chart2.png a quick look at for example the SD-Card Pins - of the pyboard and on Dipcore or Discovery stm32F407VG - says that the use other GPIO to do things... So yes you may flash that pyboard, but the Mhz might not be right (aka need to replace the oscillator) So yes you might run MIOS afterwards... but you cant use for example the onboard SD-Card - because it is wired to other pins... you have to DO the work that antichambre did (change the GPIO ports in MIOS, make a new toolchain, and that is a Job for someone who knows what he does - i would be very happy if i could do that - or someone introduce that skill to me- but i dont have any glue about that)
  7. recently i had 3 days free, to make music eat sleep, and do it all again....
  8. i am on work the last years, on my own midibox CV- project... since i am a one man show, and there are a lot of projects running in paralell - and money is aviable only all "holy times"... it is not finished, and will not be in near future, but it will be in far future, since it is a core thing in my setup. (since i am on the way to modular...) http://wiki.midibox.org/doku.php?id=cv1 it has not much to do with a NG, or MB-CV2... but it is a CV-Envelope Generator, Recorder and Looper, LFO, and Mixer, and the future goel is to have one UI that remotes a lot of Core-Modules which are connected to independend Midibox-AOUT-Modules, so you could use One to build up a complete midified (so you can save and load presets) Analog-Synthesizer - a drumsynth for example, and multiply that by for example by 8 so you have a 8part Drumsynth with one UI - so you save space in your eurorack... how ever not finished - if interestd follow this topic:
  9. @RIO linker? this is not a software swich/link... its a hardwareswitch, and if he had that switch in the firstcase, he might have solved the problem already. Since he was talking about a new SD-Card, and of corrupted Files, i thought there is maybe no hardware-config file (or 0kb file) on the new card. --- later on he posted a picture of the SD-Cards filestructure... and yes i now see there is a 22kb File on it > so yes he dont need the Hardwarefile because there is one - congrats! wilba: http://wiki.midibox.org/doku.php?id=wilba_mb_seq&s[]=wilba
  10. " you may also need to put the hardware config file on the root of your new sd-card: i guess its a wilba without track-position LED-Matrix? then this is the hdwg-file: /midibox_seq_v4_096/hwcfg/wilba/MBSEQ_HW.V4 (is in the zipped firmware) " i already wrote where it is (read! and take it serios), it seems that you dont have a Wilba-Interface, looks like a standard DIY-Interface? i would first try to go into bootload mode via.: http://wiki.midibox.org/doku.php?id=home:mbhp:module:bootloader-switch build this switch, set the switch to bootload mode, reboot the core, then open mios studio, upload new SEQV4 code.
  11. you may also need to put the hardware config file on the root of your new sd-card: i guess its a wilba without track-position LED-Matrix? then this is the hdwg-file: /midibox_seq_v4_096/hwcfg/wilba/MBSEQ_HW.V4 (is in the zipped firmware)
  12. ok i am in austria... so maybe a other one?
  13. I tryd this Variant for Midi-OUT Activity LEDs... as it works with NoteON-OFF Messages, it comes to its limits when transfairing high datarate - like midiclock. The steady Charge and discharge of C5, messes up the Datasignal, so it cant be used. Since i already used all Pins of 74HC14, i now need a second HC14, or some other Buffercircuit (for 2x Midi-OUT Activity LED) - any Ideas for that are welcome!
  • Create New...