Phatline

UPDATE 140720: still learning & its not so difficult at all, because of * I already know what I want * I already checked out for Years what Feature is necessery and what not, what has mass effect and what has to be left! * I already programmed it in MAX MSP years ago. https://vimeo.com/101245089 So now whats Working in this Video: * Velocity depinding NoteKill-Switches (kill notes under 46, from 46-96, greater 96, -this values can be Offset -+64 by an VelKillOffset-Encoder) * Velocity Offset -+64 - decrease encrease the Orginal Trigger Velocity Value in a Range from 1-127 --- so it is somewhat of CLIPPING * Random-Note-Kill --- by each new Trigger - a Random generator is startet - and kills the trigger or not... with the Modwheel I change the Random-Range. Challanges for the future (witout any clue up to now): Changeing Notelengths Midiclock-1n % debending doubling midiclocks, half midiclocks, start stop midiclock by beeing a slave(for the Synthesizer build in LFOs...) Output Inital MidiCCs to the BCR2000. Save and Load Presets Morph Presets Values Building a BLM16x16

looks perfect for my project! I am looking for the correct Gerber files, or maybe a prototype pcb, for me it is not clear which are the ones that are working for you. As far I found out, you shrinked Findbuddas Layout (no space between 8 and 9), but whre is your wiki page? thx for more info

UPDATE 140711: -oh yeah first part is running- https://vimeo.com/100537805 TM MBHP-Based-RETriggerpart UART0 IN1 = Korg Electribe Rythm = TriggerSource UART1 IN2 = Midi Keyboard = MelodySource Learned about arrays and matrices...: I have 2 IN-Ports, and when I write Code in: void APP_MIDI_NotifyPackage(mios32_midi_port_t port, mios32_midi_package_t midi_package) I always get triggering Events from both ports... thats blow up my code, since I have 2 independend TASKs. 1stTask: Save Melody Notes (UART0) 2ndTask: Trigger out the saved Melodys(UART1) the notify Package is somehow connected to mios32/trunk/programming_models/traditional/main.c - i am afraid if i change something there, it would be replaced by the next mios update...

thx for looking in > code works at google - quick shot, foul etc mentality: i even slept a night over it, printed some array courses to A3-Pack at work, searching google on this todays eveining and so on: i crossed a lession about how to initalze a 2D array... yes at this point only at declaration... http://stackoverflow.com/questions/1688741/initialize-a-2d-array-at-declarationtime-in-the-c-programming-language but here: http://stackoverflow.com/questions/4066522/setting-an-array-to-one-value - so I the idea there is some nice "Reset" or "Blank" function behind Array, but that dont work so my thougt was that there are differences by this uC-C?

I am new in C, but my code works, but to big to slow, time to use matrices and ARRAYS I declare and initalise a array: later I want to write a 0 in all Cells of the Array, e.g: "make" give me e.g. "expected expression before '{' token" also tried: {NteBuf0[] = 0;} {NteBuf0[] = { 0 };} {NteBuf0[10] = { {} };} memset(NteBuf0, 0, 10) {NteBuf0[10] = 0;} make: "warning: array subscript is above array bounds [-Warray-bounds]" and a view others that i dont remember (because of not working in this case) writing them one by on by one.... works of course What do i missed to know?

os ubuntu 14 mius studio 2.4.6 I changed the optocopler - DEAD! I now got midi from: usb midi 4x4 (2) so what I have learnd from this trlial and error session? The LCD now Print 32 for Midi1 and 33 for Midi2 so this is solved thx

1st port working 3rd port not working checking hardware...

ok first steps on the way to it https://vimeo.com/100044560D GREEN-LEDS: Inpuut Trigger RED-Leds: Output Trigger Buttons+LEDs: at the moment only Toogle the Variables for later Programming Stucking: dont get MidiIn2 on the LPC17 tu run...which i need for the Melody-Part

CORE LPC17 app: modified tutorial 004 I need both Midi Inports on the Core PCB (Midi IN1, Midi IN2) in 1 Application Midi IN1 = UART0 or 32 Midi IN2 = UART3? > I dont get something in there when I run this code: The display connected to the LPC17-Core now show "32" -when I send Data to Midi-IN1, but it dont change when I send Data to Midi-IN2 in the config mios32_config.h I addet this Lines: but that changed nothing I need both UART In-Ports for my TRIGGER-Matrix-Project where is my fault, what do i miss?

:pinch: autsch I thougt that it would apear in the folder project_built & the hex file outside where prebuild after have a look on the others tutorials I see there is no prebuild hexfile in - it ok got it - thankz - phat

I work thru the tutorials that are locatetd in the midibox toolchain. I use ubuntu, when i enter following lines into the linux console: it builds this: what i got is an .bin, elf, file I want to upload that application on my LPC1769 core, with mios studio - but mios studio wants .hex (on the core is up to now a SEQV4 application) do I need some kind of converter? or do I need change something in the "make"-thing - & how to change that.

Thank you for the .bashrec thing :santa: --- eclipse thing is still unsolved I changed your command to: cd /home/wermitgeht/mios32/apps/sequencers/midibox_seq_v4 (dont get trunk, hold hirachy low...) and hit "make" YES it is Working gave mi this: in eclipse i still get some missing Folders/Files when i build: grüße von "nähe Linz" nach München :phone:

-I restardet the laptop- gave me this i also addet the other lines to the .bashrec file (i wrote them at the end of the file after "fi" then I deletet all Variables in eclipse then i build - i become following error:

set grep Path give me this: i found the .bashrc file in /home/wermitgeht (=home/username) I addet in there the string export PATH=$PATH:/home/wermitgeht/mios32/bin at the end of the file: then I restardet the engine still the same problem... in aclipse I ereased then the Path Variable - because it override the system Variables (i read that anywhere) So have to clear this variable in Eclipse? but error is still the same:

> in Linux console - or anywhere in eclipse (eclipse console only show data, i cant write anything in there)? In this Tutorial http://www.midibox.org/dokuwiki/doku.php?id=eclipse is written: my "arm-none-eabi-gcc" is under: /home/wermitgeht/mios32/bin So how to write the Value of Variable "PATH" correct? ${HOME}/mios32/bin:${env_var:PATH} ${HOME}/wermitgeht/mios32/bin:${env_var:PATH} ${HOME/wermitgeht/mios32/bin}:${env_var:PATH} $HOME/wermitgeht/mios32/bin:${env_var:PATH} HOME/wermitgeht/mios32/bin:${env_var:PATH} ${HOME/wermitgeht/mios32/}bin:${env_var:PATH} I dont have a glue - because of not understanding this $ ( ): $ (env_var:Path) thing I dont have to set this in Linux when I set in Eclipse (thats what the Tutorial says)? (I will not set this temporary Thing every time i restart the Laptop, and for set this for "always" i dont have the linux knowledge to do that-as already said) greets phat

command line = console? console says: Kommando nicht gefunden = (command not found) > as I thougt the Path-setting is not right, but I am not able to interpret the Manual that give us a screenshot for windows, TUTORIAL SCREENSHOT from: http://www.midibox.org/dokuwiki/doku.php?id=eclipse like on my very 1st picture my Path is: /home/wermitgeht/mios32 I come from max-msp - so i may know some stractions, may know that $ give us something like a variable --- but I am absulutely new to C for uC and of Course Eclipse.

OS: ubuntu 14.04 LTS (I am the only user who use this Computer... no multiuser needet) DO YOU SEE ANY FAILS ON THE SCREENSHOTS: I put the mios32toolchain to: /home/wermitgeht/mios32 these are the write read rights: in eclipse i set this settings: & this: then I imported the app_skeleton_cpp after right-click on the skeleton - then leftclick on "project build" I got error 127 I gues it has something to do with the PATH -I will defentivly not modyfie the operating system, - because I tryed and I dont get it work - as described in: http://www.midibox.org/dokuwiki/doku.php?id=linux_mios32_toolchain_core after one nigth googling and searching i gave it up... this sentence is definitivly not enough describtion for a newbee. but hey dont need... written in this Tutorial: http://www.midibox.org/dokuwiki/doku.php?id=eclipse up to now hardstuff that everyday when I try to get this run - ends by NOTHING, end by the frustrationt "to not wrote a single code line"... I have tryed it on a windows computer, and also get sucked on this variables, i finally made a Batchfile... in ubuntu i get sucked by trying to do the same (scribt). please take a look on my screenshots - do you see any Fails? do you need more details - what?

good answer :smile: > ok on my way into it. greats phat

touch: so may then tactial again program: i think here and there from anaywhare - help would be enough. no need that someone programm this for me - learning to do it on my own - learning from others - hopefully there are People on this forum that understand that "Mios" May stupid sounding Question about Prgramming - and maybe it was asked frequently: Can I handle this idea of routing triggers and combine it with notes change gatelength kill notes out and so on - by using MIOS by studing learning combining and changing codes from this: http://www.ucapps.de/mios32_c.html or do will go better on things like that http://www.instructables.com/id/Send-and-Receive-MIDI-with-Arduino/6/?lang=de by beginning with basic 8bit mididata and µC-Registers- because of may missing things in mios for that application for that to program I (maybe) not have enougt life time to change on my own - what do you think? whats the learning curve here (max msp was high... and then when i passed to docomentated it took a long while to get into it again ) hardware: the hardware must be built anyway - even when it is "only" to controll my max msp programm with it. you: would be enough to watch in here from time to time - and do what you da > tips > about what ideas cant works or not - what will troubles in your expirience. (eg.8x8 brightness, and so on) greats

Buttons and PCBs for the "Matrix": 2 PCBs - 1x for LED 1x for Buttons > Reasons why: -to get all Routies on a Single Sided Board (Garage-CNC Friendly) -to replace the whole Button board if they buttons are going "dead" > resolder them is horror... the livetime of the cheap Tactial-Switches is short, but when I do LEDs and Buttons on seperate boards, i could change the whole button board when its "done" Maybe I find any with better lifetime-cycles "Dead Solutions" by the search off different button-systems, i tried a layout for my DTL Switches: but it´s to big and not a SQUARE-because the buttons are not SQUARE....I had byed 300 of them years ago in a even bigger Bulk-Order.... --- but for this Matrix? nope! for a nother one. is such a matrix also possible with "touch sensors" like shown in this diagram: http://www.ucapps.de/mbhp/mbhp_din_touchsensors.pdf ?

is there a possibility to change the Note/Frequency Calculation? Change to a indian System where the Octave is splited in 22 Tones, where the notes and its frequencys are stored in tables - not all of the 22notes are used, some are taken for a song - this selection is for playing a "Raga"... In which part of the Application is this Calculation, and where I could put tables instead (note 1 is predefinied frequency > variable > integer...)

THE MATRIX PART: First i will build the matrix, because its the main function of this, & without any hardware to get into Program is boring --- so build the hardware in order to get a 10x10 Matrix i need 2x mbhp dio_Matrix_modules? --- i have troubles with this shemata: http://www.ucapps.de/midio128/midio128_v3_dio_scanmatrix.pdf > is it wright that the diodes that are shown are 1n4148 & not LEDs > so the leds get driven by a seperat DOUT module? in a way of "LEDRING" > http://www.ucapps.de/mbhp/mbhp_doutx4_ledrings.pdf?

have intrest in 2boards a.4x16 or maybe 3 depends on price

ok split

i have made a wiki for this: http://wiki.midibox.org/doku.php?id=triggermatrix You have spend time to program a cool rythm, and you already know which chords/melodys you want to play, and now its time to programm the timing/steps/the rythm in the melody... after quite a while of trying and looking on your drumline you have a fitting melody line for your drums... now you change the drums a bit... o no i also have to change the melody now... i make a break, a intro...oh no so much work and time...and all because, the melody is fixed in arrangement, you want a melody line that goes with beat? you want to change the beat note stream also (noteprocessing)? > read more... i have a tool for you!!! it will change your live!!! really! hear that track: Phatline -the king will go it is played with a static drumline, and a static melody line, all other is live... you hear it? thats trigger matrix - get ready for JAM! Basic Idea: Merge a Drumsequencer with a Melodysequence so the melody only sounds when a specific Drumtrigger comes > like a arpeggiator on a keyboard, but not fixed > trigger relativ and doe that changing with the drumline The Drumsequenc give the timing the velocity and the Sustain > the tribe. The Melody only give the chord notes., instead of a drumsequencer you could use a human drummer with triggerpads, instead of melodysequencer you could play a keyboard, a guitar synth, a flute controller, a theremin... how ever - you get it? awsome is?t it? yeah! of course there is not only the melody output, of course also the trigger output for more Drum-synth modules... so you drive your whole setup with that, also a Programchange for 16 Midichannels is integrated as well 512 Songs (routings) with each 8 songparts (intro outro break), i have tried chordsets, but i dont found it usefull, also it consume more CPU and RAM... with the LPC uController i use all of it with 5 Melody tracks(with 128 chord notes) and 3 Drumtracks... so back to a drumsequencer, you should use some playable, realtime changeable drumsequencer, or you use the functions of the triggermatrix > note processing! track rolls, main rolls, velocity depending trigger kills, velocity offset, velocity invert, random note kills, matrix routing song presets, sustain length, track mutes, and a whole array off trigger in and output LEDs, and a of course matrix 8x8 up to now, 16x16 at the end off 2015 - so the plan (build for the 16x16BLM...) so i can say all is done up to now, go ahead with 16x16 Growing Details > TriggerMatrix for Drummachines Triggermatrix built in a analog 70s E-Home organ "CRUMAR 198": or as Drum-Trigger-Matrix built in a 80s Analog Drumexpander "Tama Techstar 306" a talk about making live music, and what the trigger matrix do for me (german > austrian): Drumnote retriggert Synthnotes: https://vimeo.com/98954975 (For that i have more ideas like Note-Random-Kill, Velocity Kill, Accent) UPDATE 140720: https://vimeo.com/101245089 So now whats Working in this Video: * Velocity depinding NoteKill-Switches (kill notes under 46, from 46-96, greater 96, -this values can be Offset -+64 by an VelKillOffset-Encoder) * Velocity Offset -+64 - decrease encrease the Orginal Trigger Velocity Value in a Range from 1-127 --- so it is somewhat of CLIPPING * Random-Note-Kill --- by each new Trigger - a Random generator is startet - and kills the trigger or not... with the Modwheel I change the Random-Range UPDATE 140711: https://vimeo.com/100537805 TM MBHP-Based-RETriggerpart UART0 IN1 = Korg Electribe Rythm = TriggerSource UART1 IN2 = Midi Keyboard = MelodySource GREEN-LEDS: Input Trigger RED-Leds: Output Trigger Buttons+LEDs: select the triggersource=triggernote