Phatline

its that: i can learn in Tutorial 28 that some Functions do the job for you, OSC_CLIENT_SendMIDIEvent(3, midi_package); - is that what you learn. But bevore the connections should be initalized or setupd. in this case #include "presets.h" has the data in it, and with Mios-Studio it could be setuped and stored in the preset file (as far i understand that...). but whats about if i dont want to have this preset file, and i dont want to use mios studio, in fact i want to fix the Adresses, to keep my application compact. So i take a look into "terminal.c" where all that Mios-Studio stuff happens... but here its getting complicated, since the whole thing is done for terminal work - and this terminal.c is not made for newbees, it looks like i missed some basics... i only learn them when i need them (elswhere i cant connect the dots) but i cant identfiy what i have to learn take a look what i have done: #include <mios32.h> #include "app.h" #include "uip.h" #include <uip_task.h> #include <osc_client.h> #include "terminal.h" void APP_Init(void) { // init terminal TERMINAL_Init(0); UIP_TASK_Init(0); //Connection Setup UIP_TASK_DHCP_EnableSet(0); UIP_TASK_IP_AddressSet(0,0,0,0);//app.c:17:16: error: too many decimal points in number Host IP-Adress? uip_ipaddr1(0.0.0.1); //pointer? app.c:17:16: error: too many decimal points in number uip_ipaddr2(0.0.0.2); //pointer? app.c:17:16: error: too many decimal points in numberor should they all be the same - the UIP_TASK_IP_ADress maybe? uip_ipaddr2(0.0.0.3); //pointer? app.c:17:16: error: too many decimal points in number uip_ipaddr2(0.0.0.4); //pointer? app.c:17:16: error: too many decimal points in number UIP_TASK_NetmaskSet(255.255.0.0); // error: too many decimal points in number OSC_SERVER_RemoteIP_Set(4, 1.0.0.0); // error: too many decimal points in number connections, IP OSC_SERVER_RemotePortSet(0, 1000); //connection, port OSC_SERVER_RemotePortSet(1, 1001); OSC_SERVER_RemotePortSet(2, 1002); OSC_SERVER_RemotePortSet(3, 1002); OSC_SERVER_LocalPortSet(0, 1000); //connection 0-3? those Remote Port? i dont understand that - this is most confuzing, OSC_CLIENT_TransferModeSet(1, 0); //selected_osc_con, ocfg_value UIP_TASK_GatewaySet(1.1); //ip UIP_TASK_UDP_MonitorLevelSet(1); //outputs data to Mios-Studio ---0 turn off //dont needed anymore if the Network setup is correct...just mess the usb bus.. OSC_SERVER_Init(0); OSC_CLIENT_Init(0); } void APP_Background(void){} void APP_Tick(void){} void APP_MIDI_Tick(void){} void APP_MIDI_NotifyPackage(mios32_midi_port_t port, mios32_midi_package_t midi_package){ MIOS32_LCD_Clear(); MIOS32_LCD_CursorSet(0, 0); MIOS32_LCD_PrintFormattedString("%u %u %u", port, midi_package.chn, midi_package.type); } s32 APP_SYSEX_Parser(mios32_midi_port_t port, u8 midi_in){return 0;} void APP_SRIO_ServicePrepare(void){} void APP_SRIO_ServiceFinish(void){} void APP_DIN_NotifyToggle(u32 pin, u32 pin_value){ OSC_CLIENT_SendNRPNEvent (0, 8, pin, pin_value);} //port, chn, nr, value;} void APP_ENC_NotifyChange(u32 encoder, s32 incrementer){} void APP_AIN_NotifyChange(u32 pin, u32 pin_value){} Question 1: no matter if i want to write a IP like 10.0.0.0 or a SubNetMast like 255.255.0.0 i get: "error to many decimal points in number" -- that says i should write a number here? but 10.0.0.0 is not a number - i understand but how to write it correct? confuzing.. Question 2: what do the server? do i need this once in setup? or is every Midibox a server? ANSWER: Any application that sends OSC Packets is an OSC Client; any application that receives OSC Packets is an OSC Server So a midibox that sends and receives is an server & client > thats what the OSC-Specifications says: .found @ http://opensoundcontrol.org/spec-1_0 Question 3: Do I have to setup all Midiboxes the same? except the local port? Question4:In Follwoing article, are 2 connections between 2 midiboxes http://ucapps.de/midibox_osc.html > just to understand the whole concept: Midibox A Setup: Remote 1: 0.0.0.1 1000 Local_port 1: 1001 Remote 2: 0.0.0.1 1002 Local_port 2: 1003 Midibox B Setup: Remote 1: 0.0.0.2 1001 Local_port 1: 1000 Remote 2: 0.0.0.2 1003 Local_port 2: 1002 so every Device has its own ip, the Port are swapping, but why i need two of them? why Remote 2? Is this just to say "hey you can take to ports @ the same time?" Remote means - that this is the client/send-Port? Local means - that this ist the Server/receive-Port? How to write that code in my code example above? What happens if i use more then 2 Devices, If i use 4 or more Devices that share data? the one that receives from any ip - and forces "void APP_MIDI_NotifyPackage" ? or where i can acces that osc datagram, by Midi_Notify_Package - as far as i see i get UART... and OSC0-3 (these have a definied ip, its not any?)

A lot information: http://www.ucapps.de/midibox_osc.html but no information how to make a custom program, except this tutorial: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F028_osc%2F there are differnt modules out there , because i have to begin anywhare, lets start with the osc_client: http://www.midibox.org/mios32/manual/osc__client_8c.html lets try to send a nrpn, what say the "documentation": s32 OSC_CLIENT_SendNRPNEvent (u8 osc_port, u8 chn, u16 nrpn_number, u16 nrpn_value) aha, so then stripped down:: #include <uip_task.h> #include <osc_client.h> void APP_Init(void){ UIP_TASK_Init(0); OSC_CLIENT_Init(0);} OSC_CLIENT_SendNRPNEvent (7001, 0, 1, 127); //port, chn, nr, value compiler returns: - what is no surprise since the port is declared as u8 (0-256) - when i want to use port 7001 ---what brings me to the first question why ist the port declared as u8? --- or maybe there is no network port meant? - like in the tutorial: maybe meant OSC0 OSC1 OSC2 I cant find any Word like receive or observe - how to receive/listen to a port/ip? >>> Maybe i have to use the OSC_CLIENT as a Function inside the main.c? (simular use like the DIN or Midi-notifcation function?) it looks like the midi-notificaton-function do this job by putting OSC0 as port out instead of UART or USB... Network connection with deafault Network configuration: Before Connect a Core LPC17 with code from above: Knoten: fe80::214 ff02::fb Protokolle: MDNS Port 5353 1second after connection a Core LPC17 with code from above: Knoten: fe80::214 ff02::fb ip6-allnodes ff02::1 Protokolle: MDNS Port 5353 UDP-UNKNOWN 4second after connection a Core LPC17 with code from above: Knoten: fe80::214 ff02::fb ip6-allnodes ff02::1 0,0,0,0 255.255.255.255 Protokolle: MDNS Port 5353 UDP-UNKNOWN BOOTPS Port 67

ok got it: - i have to initalze every LCD/device once - then i have access to it - stripped down code: #include <mios32.h> #include "app.h" void APP_Init(void){ MIOS32_LCD_DeviceSet(0); MIOS32_LCD_Init(0); MIOS32_LCD_DeviceSet(1); MIOS32_LCD_Init(0); MIOS32_LCD_DeviceSet(2); MIOS32_LCD_Init(0); } void APP_Background(void){ MIOS32_LCD_DeviceSet (0); MIOS32_LCD_Clear(); MIOS32_LCD_CursorSet(0, 0); MIOS32_LCD_PrintFormattedString("DEVICE 0"); MIOS32_LCD_DeviceSet (1); MIOS32_LCD_Clear(); MIOS32_LCD_CursorSet(0, 0); MIOS32_LCD_PrintFormattedString("DEVICE 1"); MIOS32_LCD_DeviceSet (2); MIOS32_LCD_Clear(); MIOS32_LCD_CursorSet(0, 0); MIOS32_LCD_PrintFormattedString("DEVICE 2"); } void APP_MIDI_NotifyPackage(mios32_midi_port_t port, mios32_midi_package_t midi_package){} void APP_SRIO_ServicePrepare(void){} void APP_SRIO_ServiceFinish(void){} void APP_DIN_NotifyToggle(u32 pin, u32 pin_value){} void APP_ENC_NotifyChange(u32 encoder, s32 incrementer){} void APP_AIN_NotifyChange(u32 pin, u32 pin_value){}

looks like I cant use the 3rd Display normal: A: Thats right, you have to select a Display first. "MIOS32_LSCD_DeviceSet (0); MIOS32_LCD_CursorSet(0, 0); MIOS32_LCD_PrintFormattedString("MUTE Drum1 HOLD Drum1 MUTE Drum2 HOLD Drum2 MUTE Bass MUTE Chord"); give me: ok what the Function Describtion says, that i Have to setup the lcd as GLCD: do i have to change the local mios-config-file in some way? A: Change it with the Bootloader app and Mios-Studio - and its don: Upload the Bootloader.hex, open Mios-Studio, typing in Mios-Terminal: Now i see that all 3 Displays are Working (hardware is ok) aha there are special commandos for GLCDs: maybe this will help: A: Definitvly a good start MIOS32_LCD_DeviceSet (0); MIOS32_LCD_Clear(); MIOS32_LCD_GCursorSet (0, 0); MIOS32_LCD_PrintFormattedString("DEVICE 0"); MIOS32_LCD_DeviceSet (1); MIOS32_LCD_Clear(); MIOS32_LCD_GCursorSet (0, 0); MIOS32_LCD_PrintFormattedString("DEVICE 1"); MIOS32_LCD_DeviceSet (2); MIOS32_LCD_Clear(); MIOS32_LCD_GCursorSet (0, 0); MIOS32_LCD_PrintFormattedString("DEVICE 2"); 3rd Display is blank (by the way the 3rd displays first Row is filled with Black Rectangels (like a PIC without Bootloader...) A: The 3rd LCD has to be initalized first: "MIOS32_LCD_DeviceSet (2); MIOS32_LCD_INIT(0);" - more see next post --- what brings me to the point that this 3x Display Setup in Bootloader mod must be overwritten when i upload my code....so search in a nother way...: A:NO, Bootloader is fine. Do I have to change this "universal" to something other? or is GLCD also "universal" and i have to change something somwhere other? A: NO, Universal is fine.

good input ... in the meantime i asked for Android Drivers for the panels...

no need for those extra transistor and Pots... it runs without problems, the transistor is warm, not hot.

you are welcome.. what i also like is to change the the gatetime off all Gate-Outs by turning a Gate-Time-Offset-Knob --- it is a so nice live feature, to blow up the beat to maximum and visaversa get into short clicks... but this will only work on grown up Drumsynthesizers (i programmed Maxmsp drumvoices with fully stuffed ADR for pitch and AMP) that can handle gate times... most of them old drumvoices are trigger only, and Decay is changed via Potentiometer which make it impossible to do that for all tracks @ once. but maybe this is an idea: make a Master-Trigger-Gate-Track on your Device, on that that track you route all Trigger outputs (software side of course). now connect a ADR stage on the gate, and then connect the ADR to an AMP - the Amp is feedet with the sum of your drumset.... also > on the same manner do some Master LP-HP-Filtering with all that you have not change the seqeunce so much... most of the time you will tweak this and that, and after 15minutes you realize you are still on the same rythm pattern

No cant help by program it, dont know how to built a drum-sequencer on Mios... in max msp yes... some counter, some arrays, some matrix, some sync (well this would be the hardest...) some storrage some interface (touchsreen) and its done I also need a drumsequencer in the next time, but it would be built and programmed very pure-the ui will be 10-15" multitouch with OSC-Program on it, the hardware simply a mios core with ethernet, because my skills are not geek - and i need to be in sync i cant risk to overload such fundamental with to much stuff-that dont have much to do with something like a Trigger-Generator... these all additional features will be done by a other Device that is switched after the Sequencer, the Trigger-Matrix. - so if you find some, or get knowledge, write all in a tread, maybe i can learn from it :shifty: anyway here are some tips, from my grooveboxes and programs that i have programmed since 2008, the following features are for me a must, they do so much, and i do so less, so good for live : good live features that i have programmed in all my stepsequencers... and finally also in a midibox based project (trigger-matrix - tekkstar: Encoder for Velocity controller - for me: Velocity offset: in middle position=orginal velocity, turn left, all notes will be lowered by an amount, turn right all notes will be encreased by a amount (all are loud) Random Trigger Kill Encoder/Poti: Change the ammount of "how possible is it that a velocity comes out of your sequencer" --- the best feature ever - make breaks by turning a Knob 90°! 2 or 3 or 4 Velocity Kill-Buttons: That Kill a range of Velocity -- exactly, it kills notes that are below Velo64, the other Velo90 the other velo127 >>> thin out your Drumset >>> straightn it! Velocity Invert button: Loud will be not so loud, and not so loud very loud.... (all these Velocity Things are differ by turning your velocity Offset Encoder--- very much differencys....) OverRoll: route all Sequencer-output data to all DOUT-Trigger-Modules Individual Roll: Activate the roll on one Track, easiest solution: Overroll, better selution - the possibility to change what trigger will go to what Trigger output when you press the IndividualRoll-button >>> best to setup with a 8x8SID-Style Matrix, or over OSC with some tablet, or even with your Step-Sequencer Input (if you have enough rous) >>> the cheapest solution is maybe really a Touchdisplay with an microComputer with an OSC-touchscreen-Software on it.... Locost "See all Tracks"-Feature: Realised by a 8x16 LED Matrix over your Buttons (See Snare BD and all others...) -- a matrix is good for really much things like: deactivating some tracks from be-ing RandomKilled, or Overrolled, or invert... (Kick drum e.g.!) also very good to Route the different tracks of your sequncer to different Trigger outputs..., and so on.... i programmed a own app for this as i said the trigger matrix it is made to midipluged in after a drumsequencer... my pure programm-knowledge bring me to the point that i need a own lpc17 only for the trigger-matrix and all the features i explained... If you connect in Additon/or future some Midi Synths, maybe its a good idea to implement some bankchange send...(just to dont forget when you definie the Patch-structure on your SD-Card...)

hm it depends....if i would build something like that, and would sell it > 700 are hmm ok a bit to much.. how long whould i work for it? a month every view days a couple of ours? ... but of course i am not a chinese kid or a roboter... for chinese and automations scale way too much

thankz, very much, complettely overread

i saw TKs Lemur SEQ app, and come to the idea that for my Project Trigger-Matrix in V2 it should work over OSC and LAN only. I want to fix the Touchscreen device in my Gig-Rack. Tablets: No Lan, but WLAN, Bluetooth, Akku, Camera... and other stuff that i DONT need in an Music device Normal Desktop - Multitouch-Monitors: starts with 19" and are a bit expensive. Screen/Touch-Combinations for self construction: Cheap small, thin... the way to go (in my case) what this guy did: http://www.heise.de/make/meldung/Edles-Selbstbau-Tablet-mit-Raspberry-Pi-2085593.html he got his disply/capacitives from here: http://www.chalk-elec.com/?page_id=1280#!/14-HDMI-interface-LCD-with-capacitive-touchscreen/p/36248806/category=3094861 ---not full hd! I will need a Android Computer for this because there are a fiew Multitouch capable OSC-Software out there: http://hexler.net/software/touchosc-android what brings me to Raspberry Pi: https://www.mepits.com/project/180/DIY-Projects/How-to-Install-Android-on-Raspberry-Pi-? 140$ for an 10" Multitouchscreen? ... well not Full HD, and 10" is a bit to small for an big Button Matrix... but cheaper then alot of leds and Buttons... and all the time to solder, etch, drill, screw, cable, wire... waaaahhhh. i am now surching for "over 10" and under 19" displays, full hd, with the possibility to connect with a raspberry pi, or simular device that can run a Android version that can handle Multitouch capable OSC-Software. @this point i have to write something.... because i found so much Troll Information outthere, by seeking a Tablett without 3G Bluetooth or WLAN... i got angry by so much stupidity, and now because it is a main task, its time to post a other point of view - for all the consume trolls: "why you say WLAN is useless stuff? and so on..." Well there is no short answer from me to you... if you really interestet in something that i call "what is right" (for me.. what not mean for you) then read on There are a few reasons for that. My grandfather was a electrician, after WW2, he was one of the pioneers in small villages that winding motors or trafos, help the energy to get into the houses, he was (is) a maker...and now old an ill because of technic and ill making livestyle (normal postwar americal like Austrian Livestyle) but bevore i can say for his village he was one of the the first man that have to do with current the last 300 years... (historry is written by...).... His 1st son died in current. after years I the grandson was born... grandpa infected me with the Frequency Power and DIY spirit... but there where not only him, there is also my father that have no glue about electronics at all, but about good pschodelic music, and beeing in nature beeing a real human working with mentally handicapped persons, and my mother open hearted thin sking person... and me that all comines that spirit into one new spirit, standing here haveng oversight about a postfaschism country where 60 years ago electrical power grows up until now where we are - a cyperspace non human robotic isolated steril antibiotic dieng world... i was in scholl for electronics, then electrics, was a lighting assistent, camera assi, event technician, old peoples nurse, electronic musican, even programmer, psychonaut, thinker, herbal assembler, gardener, writer, now cad electric and CAD planner for big Building complexes and much much more... I can be what I want to be, i have the power - and i have the power to combine all that to say "I know" - there are things that i Know because i am capable to think! not to believe or respeak what I heard in TV (what i dont have) or Radio (what i not hear" or read in Press (which i dont read), it was a hard way, from shool believer unawareness - to self thinker >>>> there are things out there they are clear! It dont matter what people in forum, wiki, neighbars, moderators, press and all the paid/stupid trolls are saying. I say: ;) Binarry Rightangle Microwave Signals are lightyears away from Natural Frequencys which most of the time are Sinus or in a way "Round" - like the way of the moon the star the sund the universe, spiral...the nature is easy going - as we are! All those metals in your teath, in your footh on your body in your body in your cells in your brain in your air, in your fry pain, in your drink... and even in your red metal blood. Flaming your intelect is also lightways away from me > now its time to promote your intelect: simply qestion you:, what happens if your metall come in a "low power" electro magnetic field? what happens in a alterned field? Are Metals affective to alterned fields? is your Own Cell-Frequency and current strong enough to be an selfstanding valid iland in the ocean of waves? Did you think you can avoid to go in resonance with it? What did you think can weak you that you go in resonance with the fields? With wich amount of current your neuronal network works? How many currenet can be induct in the rightangle technically binareey field of 50Hz-4000000000Hz? What is a overtone. What happens if frequency overlaps? what are peaks? Can you imageine that there is not only your tablett? can you image that there are milliards of tablets mobile phones cb, gps, fm mw lw elf radar out there, can you visualize them in your inner Eye, can you calculate there interactions its overtones and overlaps? Well we dont see, but try to visaulize it, look out of the window seen all the poles, and wire, now think. --- I not implicide that they kill you now, because it would not be true, i not say they kill you at all --- i simply know the abstinence of the ocean of waves - and see the power the mental strength focus the body healthness and self awareness of beeing free off AC. --- that just had to be said, because of the massive other believs out there. respect - mike

multitouch possible?

I have my own application based on MIOS32, i want to connect 3x 2x40LCDs What I found out: I can wire them paralell except one Wire "E", which stands for "enable signal, start data read/write" The E-Wire for the first 2 2x40 LCDs are located @ J15a & J15b looks like this: (found that under ng: http://www.ucapps.de/midibox_ng_manual_lcd.html) well i dont use ng... and this shematic for 2x 2x40 LCD http://www.ucapps.de/mbhp/mbhp_lcd_2x2x20_mios32.pdf app_lcd give me some tips... http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fapp_lcd%2Funiversal%2Fapp_lcd.c #elif defined(MIOS32_FAMILY_LPC17xx) # define APP_LCD_NUM_EXT_PINS 4 // at J28 what in my app.c means: #include <app_lcd.h> #define APP_LCD_NUM_EXT_PINS 3 //up to 4 extra LCD can be connected, here i use 3 now what about those 4x extra Pins @ J28 - take a look at the shematic: 2 better find the PIN1: The only Pins I see are: SDA, SC MCLK WS I dont want to damage my LCDs by "just try it out" - Question is: where to connect which "E"-Line? (but maybe i am on the complete false train...) I found in app_lcd.c: // pulse the RC line after a serial data shift .... #elif defined(MIOS32_FAMILY_LPC17xx) APP_LCD_ExtPort_PinSet(2, 0); // J28.WS APP_LCD_ExtPort_PinSet(2, 1); // J28.WS //serial datashift.... for(i=0; i<8; ++i, data <<= 1) { MIOS32_SYS_LPC_PINSET(2, 13, data & 0x80); // J28.SDA = ser MIOS32_SYS_LPC_PINSET_0(2, 11); // J28.SC = 0 (Clk) thankz

Here a Block-Diagram> How does the Melody Retrigger works? Here 1 Trigger-Voice: (all that *8 and you have the trigger matrix) EDIT- the Melody Retrigger now works in a ther way.... i use RTOS task for decay-time-not-off-things....