• Content count

  • Joined

  • Last visited

Community Reputation

50 Excellent

1 Follower

About Phatline

  • Rank
    MIDIbox Guru
  • Birthday 02/04/1983

Contact Methods

  • Website URL

Profile Information

  • Gender Male
  • Location upper-austria
  • Interests Jam, Soundmorph, Subtraktiv, Program, Design, soldering, and all else about frequency > live > life

Recent Profile Visitors

1,773 profile views
  1. WTB: MB-6582

    you have 110v? we have here 220v. so i think you have to check a c128 powersupply!
  2. WTB: MB-6582

    ok i make it that way.  
  3. WTB: MB-6582

    yes sorry. 8x8580. price then 900 incl postage when somewhere in europe . give me a week too finish it. i am located in upper austria.
  4. WTB: MB-6582

    i stuff it 8570 from bulk - so "new omes" or better not used ones...
  5. WTB: MB-6582

    hi still have mine... i can assamble it next friday... so if you have a little time it could be yours.... blue lcd orange leds black frontplate with with letters case like in foto... with original psu 8 xsid say a price - i say mine.
  6. does anyone already built a footprint for this?  
  7. if i had, i would, i could ... program something for it  - the code is pretty much done, on one place there is this "MIOS no FPU" float point math problem till now  (Velocity Offset Controller "0effekt - full effekt -scale") the 4row x 8 Format, i like, because in Overview-Map Mode/mixer-mode, i have 8Channels a 4 Controlls, which is pretty standart for many cases. when using 16x2 for example having only 2 Controls on 16 Channels - 8 are enough... 16channels are a bit to much... when thinking of the arrays in the background... a motionsequencer array for example [16][32][256] or [8][32][256]  - (channel, cc, steps) makes some difference in ram. - i had longer sequences with 512 steps - but ram say no... - so for me a olre8 make more sense. multicolor with much more segments led-rings, i would show the actual Velocity/MSQ Effect on CC in different color in realtime, also would give the different maping-modes different Ledringcolors (deep-edit/overview-mode), would also add oled display to describe the function of encoder - because when affort a  olre16 it makes sense to take a bit more money in hand to give them displays... but i have some finance crisis, because driving south with my girlfriend - eating my last money , dont think i can effort a olre16  
  8.   this video has 2 parts: 1: what the device is & does 2: a stop motion film -filmed while i was building and programming the device, with music from our band "crimic" track named "neruda" more info @ wiki:[]=msq MSQ_CC_LRE stands for Motion Sequencer for Midi-Control-Change  with the LRE8x2 Ledring-Userinterface there are more varations of this tool, one is with a generic BCR2000... there is a wiki for all necessery stuff:[]=msq this Variant is hardcodet for the Nordrum2, but since the CC-Maping is arranged in an Maping-Routing-Array, it can be changed via SourceCode - which is easy done when you know a bit C-Programming. there will be also a simple MSQ_REC - which is reduced to 4Channels, which only Records and Playbacks CC of 4 MidiChannels x 128CC - a CC-Looper, without the functionality of Storing CCs itself ... i will build it for the clavia Nord Rack III - since it has ledrings and encoders - its the berfect synth for that. 8Pushbuttons, 4Ledbars, 4 encoders and done.   so this is what have done, and what will be done ;)  
  9. hei. the only float calculation i have is - sadly on a frequently used place (every 32th step 32*8 values) ---   the calculation should add and substract Velocity to (all) CsC, depending on:   the currently Received Midi-Note-On-Value (Velo_From_Note)    the Assign-CC-Matrix: which and if a CC should be addet or subtract a specified ammount of Value.  where Value 63 should end up with +-0, and 0 to -64, 127 to +64 (beat[port].Velo_Morph[x]-64.0)    the Velocity Morph Offset Controller, which when turned of, should minimize the effect from above parameters to minimal, while on MAX the Offset should have full effect (beat[port].Velo_Morph_Offset)   working float code: static float value = 0; static float morph = 0; // calculate CC Value morph = (((Velo_From_Note[port]/127.0) * (beat[port].Velo_Morph[x]-64.0)) / 64.0) * beat[port].Velo_Morph_Offset; int morphint = morph; value = value + morph; if(value <= 0) { value = 0; } // only in a range of 0-127 if(value >= 127) { value = 127; } // only in a range of 0-127 int valueint = value;   i was trying out bitshifting in high atmosphares (S32 integers), but  in reality it did not worked out, i was in maths really bad, and up to now its a pain in the...for me. not working for example: static u32 value = 0; static s32 morph = 0; morph = // to get to full u8 range // no need to shift we need half (( (( (Velo_From_Note[port] << 1) * (beat[port].Velo_Morph[x]<<8) )>>8) * (beat[port].Velo_Morph_Offset<<9))>>24); value = value + morph; if(value <= 0) { value = 0; } // only in a range of 0-127 if(value >= 127) { value = 127; } // only in a range of 0-127 maybe there is some integer-expert workaround BRO out there who can help?
  10. xTaskCreate differ... Warning

    welcome to the club - i see it everyday... i did not solve the error, nor do i understand it. all i know that when i add additional my own task like xTaskCreate(TASK_FLAG, (signed portCHAR *)"FLAG", configMINIMAL_STACK_SIZE, NULL, PRIORITY_TASK_FLAG, NULL); // my own tasks jobs to do } i got the same error   argument 2 is only the name? and name no matters? (think i read that anywhere)... so stack size and priority should have effect. EDIT: but it still sucks that the compiler is crying each time i compile... when compiling 100 of times a day ...
  11. LoopA Side

    great work!
  12. LoopA Ports

    like the whole things, the foots! a blm port! even a Reset-Switch (bootloader?) and pedals (for record? while playing piano?)
  13. Core32F4 J5a Encoder

    ahhh sorry, may fault... what i have done with J10A-B (if you replace J10 with J5 i think its the same) @top of programm (declaration) // ENCODER SR begin with 1, ENC with 0) // setup the Pinout of Encoders const mios32_enc_config_t encoders[1] = {{ .cfg.type=DETENTED2, .cfg.speed=FAST, .cfg.speed_par=3,, .cfg.pos=0 }};   void APP_Init(void){ BLM_SCALAR_Init(0); // initialize BLM_SCALAR driver // Set GPIO @ J10A+B int pin; for(pin=0; pin<16; ++pin){ MIOS32_BOARD_J10_PinInit(pin, MIOS32_BOARD_PIN_MODE_INPUT_PU);} // Set Menue Encoder int enc; for(enc=0; enc<4; ++enc) { mios32_enc_config_t enc_config = MIOS32_ENC_ConfigGet(enc); enc_config.cfg.type = DETENTED3; // see mios32_enc.h for available types = 0; // must be 0 if controlled from application enc_config.cfg.pos = 0; // doesn't matter if controlled from application enc_config.cfg.speed = FAST; enc_config.cfg.speed_par = 0; MIOS32_ENC_ConfigSet(enc, enc_config);} }   void APP_SRIO_ServicePrepare(void) { // get current J10B value and update all encoder states int enc; u16 state = MIOS32_BOARD_J10B_Get(); for(enc=0; enc<4; ++enc) { MIOS32_ENC_StateSet(enc, state & 3); // two pins state >>= 2; // shift to next two pins } }  
  14. Core32F4 J5a Encoder

    This Settings in "mios32_config.h" are working for 0-7A (5a,5b) - i am on a stm32f4 #define MIOS32_AIN_CHANNEL_MASK 0x00ff // AIN define the deadband (min. difference to report a change to the application hook) #define MIOS32_AIN_DEADBAND 31 //7Bit