Jump to content

anakin

Members
  • Posts

    28
  • Joined

  • Last visited

    Never

Everything posted by anakin

  1. Hi Thorsten It's all clear! I've just make the change in this way for the first Core that is the first in the chain directly connected to midi in: ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS after startup to initialize the // application ///////////////////////////////////////////////////////////////////////////// void Init(void) __wparam { MIOS_MIDI_MergerSet(MIOS_MIDI_MERGER_MBLINK_FP); // forwarding point // set shift register update frequency MIOS_SRIO_UpdateFrqSet(1); // ms // we need to set at least one IO shift register pair MIOS_SRIO_NumberSet(NUMBER_OF_SRIO); // debouncing value for DINs MIOS_SRIO_DebounceSet(DIN_DEBOUNCE_VALUE); MIOS_SRIO_TS_SensitivitySet(DIN_TS_SENSITIVITY); // initialize the AIN driver MIOS_AIN_NumberSet(AIN_NUMBER_INPUTS); #if AIN_MUXED_MODE MIOS_AIN_Muxed(); #else MIOS_AIN_UnMuxed(); #endif MIOS_AIN_DeadbandSet(AIN_DEADBAND); } Do you think it's right? Thank you very much and merry christmas!!! Anakin
  2. Just a precisation because, as it happens many times, I've red some posts... I try to explain my problem and my project: 3 cores chained together: first is running midimerge for scanning 2 midi in, second is running ain64_din128_dout128_v2_0 ( the C version ) and the third running midio128, all are connected via J11. The entire box is working good but the two midi in are dead, so I made some tests and finally see that the core running ain64_din128_dout128_v2_0 doesn't let data from midi in forward to the out so messages coming from the two midi in stops here! Questions: 1) How and where can I enable the merger in the codes of ain64_din128_dout128_v2_0? 2) It's safe using unly midimergeon feature or it's better using midilink forwardind-endpoint feature? in this case where and how can I activate the function? Do I have to activate it also in the core running merger? Any other suggestions? Thank you very much! Merry Christmas! Anakin
  3. Hi I've build up a midi controller using 2 cores in a chain the first running Midio and the second running ain64_din128_dout128_v2_0.zip: I have this problem, first core is the one running midibox with the ain64_din128 ecc...second core is the one for midio and after this I have the midi out. This is what happens: all events coming from the first core pass thru second core (midio) and go to midi out but, as I have also a midi in connected to the first core, when I plug something to the midi in and look for the messages to pass thru core 1, core 2 and coming out from midiout, this doesn't happens because the first core doesnt want to let pass messages from midi. Is it a software problem? I think I have to activate something in the Main.c (or wherever) in the ain64_din128_dout128_v2_0.zip...but how to do this? Thank you very much Anakin
  4. anakin

    PIC ID

    Thank you very much! I understand well and i've just done...it works! thanks a lot! Anakin
  5. anakin

    PIC ID

    Hi to all Just a simple question: How can I change the PIC ID in a chain configuration? I have a midibox with 3 cores chained together and I want to assign 3 different ID for the 3 different cores, is it possible and how? Bye Anakin
  6. Hi to all Ok, done, just adding the code you suggested me in my existing switch cases, so when I push one button or another button, after all the job and routine for these buttons, we have the reading of all the pots and pin connected. So it works! Just a suggestion from my part: It is a must to exclude from the pin_get function the two din that generate this function because there's no value to read from them and also, if you have some din leftover, exclude also them! Thank you very much!!! Anakin
  7. Hi I need just a little help for changing the ain64_din128_dout128_v2_0 apps handling of dout. I really want to know the right way for changing the din-dout relationship because I have 64 dins but only 4 led because I need to read the state only for 4 dins: But these dins are 20,21,22,23 and I don't want to plug 3 74hc595 for doin'g this because 1 74hc595 can do this...but I have to assign din 20 to led 1, din 21 to led 2, din 22 to led 3, din 23 to led 4. How and where can I do this mod? Thank you very much! Anakin
  8. Are you here talking about something like a "snapshot" function? If so Is the same thing I'm searching for: I build up a custom midibox running an hard custom version of ain64_din128_dout128_v2_0.zip basically changing din messages from note_on-note_off to CC events and splitting the AIN into 2 "Potrows" some kind of "twins" sending the same CC messages (AIN from 0 to 31 send CC from CC1 to CC32, AIN from 32 to 63 send CC from CC 33 to CC64) this two potrow are activated with two din (din 1 activate potrow 1 and deactivate potrow 2, din 2 activate potrow 2 and deactivate potrow 1), All is working good but I'm in searching of coding something like a snapshot function to send all pots position when changing from the two potrows...basically when press din 1 it must be (activate potrow 1 and deactivate potrow 2 + read potrow 1 potposition and send the relative CC values ), when press din 2 it must be (activate potrow 2 and deactivate potrow 1+ read potrow 2 potposition and send the relative CC values ). Any suggestion for how to implement this function? Thank you very much! Anakin
×
×
  • Create New...