Phatline
-
Posts
1,280 -
Joined
-
Last visited
-
Days Won
71
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by Phatline
-
-
... and the names are taken from the liveracks macrocontrolls only-so you have to assign the ccs on one single liverack per channel. for things like sendreturn, i will use fader banks.
-
The names are done with max4live... i program max4live since it was first released, so no problem to make it better over time, how it works now is:
you put one master max-patch in one channel (for example in the Master-channel)
this master patch do the communication with my Midibox via Sysex.
it collects all Track names, and Macro names, and sends it out via Sysex to my Midibox.
The sysex protocoll i have made by my myself, so this can be emproved off course...
The collect of Names is done once, when the set is loadet, or with a button press, all the names are transfaired via sysex one time,
so there is no miditraffic while "jaming", all switching between the Encoder/button Banks does not force any sysex or CC dump,
all CC and Names are stored inside the Controller (while this session)
The Value displayed on the OLED is taken from the CC-Value (not via sysex)
In order to collect all the names from the tracks and Macros, i have to put an slave-Plugin in each Track off the Set, it collects the macro-names of the Live-rack wich it is placed in. And of course iot collects the Channel-Name.
All CCs have a unique Number/midichannel... via one USB-Midiport - the Midibox-USB off course have 4 Midi Ports, but i use only one for this task.
The Feedback is like on all other Midicontrollers, if you moove a Knob in Ableton, it transmit via normal CC to Midibox - in the Midibox the CCs value is then stored, and if the CC is in the actual shown CC-Bank the display will be updatet too (so you see the new value)
if the CC is in a other/non shown Bank, then it is stored only, and if you switch to its Bank later, you see the corrent CC-Value there.
no standalone MaxMSP patches are needet, because Max4Live can transmit sysex in the meantime!
The Name thing is the easyest thing, since it is automatic - in setup - just put in some plugins, and set the Channel number - done.
The CC-Assignment, is like on all other Midicontrollers, it has to be done by hand, so its a bit work because off the mass off CCs, but once it is done, you are fine.
When you load a new set, all Faders are jumping to the correct position, and the Displays are updatet.
At the moment i spare some money for the frontpanel, so no update up to now...
-
hmmm
Quoteallows to process SysEx streams - it's even possible to print LCD messages from SysEx dumps, or to map the SysEx dump of a MIDI device to multiple control elements to implement a "Synthesizer Programmer" (!)
taken from;
http://www.ucapps.de/midibox_ng.html
so should be possible with little knowledge of programming (midibox NG = scritping)
but i am the wrong person to ask for midibox NG How to.... i am more for for a custom thing - if Ng cant handle it (but i am pretty sure Midibox NG can do your sysex thing)
-
this will take a while - look into the forum in 5 weeks or so.
i need the PCB to make a new version off Triggermatrix (http://wiki.midibox.org/doku.php?id=triggermatrix4)
the Frontpanel is not a generic MatrixController thing - it has 17 Displays, 8 Faders, some rotarys and buttons, the Software for this is not a normal Midicontroller-code (aka Midibox NG) - its my own creation a sequencer based on MIOS.
- but if i not make a shematic mistake, the pcb should be usable like the orginal BLM16*16+X in other Midibox Projects.
-
1
-
-
8 hours ago, forestcaver said:
Nice! What are you planning on using for buttons/pads?
adafruit rubber button 4x4
-
1
-
-
hei
i am currently working on a BLM16x16+X.
based on the improvements released here: blm16x16_build_guide
Orginal-Circuit:
Improved Circuit:
The Kicad-Files for it: BLM-Scalar-einfach.zip
All shematic Symbols have SMD-Parts (with 3D bodys) assigned,
also MouserPart Numbers are assigned
---but: its not routed - since i will integrate this circuit (like LatigidON did) on the BLM-PCB itself.
- I have no interest to Route the Scalar PCB itself - but its a good starting point - if somebody want to make a own PCB.
based on that, i am currently working on a BLM16x16+X:
I hope i made no mistakes in the shematic...
-
i made a passive design, since the fan which came from mouser, was dead from the beginning... since it is a 6582, it was not going very hot anyway... but i drilled Holes into the pcb under the SID-Sockets, and cut aways some plastic from the socket too.
i too drilled some holes in the plastic body under the Main-PCB too, the backside off the SID should be enough to get rid off the hot air...
-
1
-
-
... and sound...
-
about MB-NET
http://www.ucapps.de/midibox_sid/mbsid_v2_communication.pdf
http://www.ucapps.de/mbhp/mbhp_core_v3.pdf
http://www.midibox.org/dokuwiki/lib/exe/fetch.php?media=mb-6582:mb-6582_base_pcb_r2_color.pdf
already resoldered all pins on core 3 and 4
replaced the pic 4 with a new pic...
measured the can bus wires and diodes, replaced the Diode for core 4
removed R6 from core 4
reuploaded code for core 1 (aka 0)
on the automatic reboot of mios, it didnt tell me that sid4 no mb-net... but after power off-on it says again: no response...
ok it also tells me on startup:
1st screen:
mios v 1.9h tk....2nd screen:
[not here!] version 2.044 launching cs(what is not here????)
3rd screen:
sid 4 not aviable no mb net response -
thx got it... it was the ground pins... which are surroundet wit massive groundplanes (without traces that could make a thermal decouple). i heatet the.groundplane.with hot airgun,.and soldered all groundpins.again... worked " now.it says "sid 4 not aviable no mb net response" core is working, checked it by connecting a lcd to it... also reuploaded the firmware with id3... is the net a com between cores or between sid and core?
-
hei.
i built the mb-6582 from an old kit...
the 3 slave cores, provides a working a LCD, but not on the Master-Core, there i only see black-blocks...
when i boot up the SID, i have Blocks all over the screen, then it refreshes, and i have blocks on first and third row off the display.
What can be the problem?
I already measured the connections from J15 to the PICs Pins.
checked all J15 and PIC pins for Shortens against Neighor pins, and to ground and to +5V
also removed all Shiftregisters, and Bank-sticks, and SIDs (is it necessery to have the Shiftregisters connected?)
I also checked the SI-Pin off the HC165 - but they are not grounded or 5V...
i also placed in a PIC from a working unit - and it is still black (so it is not the PIC)
I already replaced the oscillator
i checked all Resistors for their value - seems to be right...
(i can upload new code, so it boots up proberly... also newest bootloader is on the PICs)
- mike
-
thx
i am working on the Frontpanels now,
For the Button Board i use Aluminium
Clear Acrylic for Screen-Encoder Section
Opal Acrylic for the Motorfader Section -
+++because, i plan to make RGB-LED-Boards so light up the Channelstrips in the same Color as they are in Ableton Colored... so i see groups, and have overview....
i want to mount them lower to the Encoders and make a Aluminiumplate to block the LED-Light from lightning into my eyes directly.
i too make traces into the Acrylic, so i have less Illumination from strip to strip:
-
i use customcode based on mios32 - so i could enclude modified lcd functions (no midibox ng...)
-
i use J10 in combination with 74hc595 (latigidon display driver board)
it seems to work for 56 screens (+8 from J15)
how and where is the multiplexing logic for J10 programmed? and how to expand it to 80 screens? (hi update speed is not needet)
-
i tryd to midify a old home organ (where every key was wired to lots of voices - without any logic...) at least there i had a lot off noice from the microcontroller, and bleeding.... but it worked - except from the noise - it worked - maybe ti would helped to use a lot of capictors to LPFilter the shiftregister outputs....
i gues the Relays terminate the digital-noise/transistor bleeding - so you get a clean solution.
-
i am always interested into stm32F4 cores and stuff --- but RE_ take it - i am not interested into all off it --- but you will need all off it to build a seqV4 - so RE_ take it!
-
(at least he didnt answer me - i didnt bought it - so it may be aviable)
better you send him a PM - maybe he has no email notification for topics...
-
about the things above... well most of the things you dont need...
you need
3x DINX4
1x DOUTx4
2x 2x40 LCDs
17x encoders
a lot off buttons and LEDs
1x core
1x DIN MIDI
much wires...
a custom frontpanel
big breatboards - to build a custom UI
better go to V4, search the flearmarked forum for a "wilba" frontpanel pcb, and a stm32F4 core with discovery board, and a Midi IO Board
Frontpanels you can order from "the beast" from UK.
-
ok next step... "Mute" & Solo Buttons
needs some external DINX and DOUTX boards (in order to make the SRIO-Gain short)
-
1
-
-
interested in stm32f4 and discovery.
-
interested in tms32f4 and 2 midi io . rest i dont need.
-
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!)
-
1
-
-
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)
-
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)
-
1
-
Triggermatrix 5
in MIDIbox User Projects
Posted · Edited by Phatline
the next generation off Triggermatrix,
with insights to shematic, the board-files i will not set free... the Pictures from the Boards are for debugging reasons only.
where possible, i made pick and place ready boards - to reduce soldering time... at this point the big BLM16x16 board is not pick and place ready.
WIKI:
Triggermatrix 5
Display-Driver-SMD
BLM16x16-V2
Core 4 Discovery
Core 4 Disc - Midi Expansion
TM5-codeblock
TM5 Din Dout Gates
TM5 Gate - Breakoutboards
TM5 Gate - In
TM5-Housing