All Activity

I am here from the future to say this hardsid.dll crashes goattracker 2 consistently on w10, it does show in the system tray. Best I've got out of it so far is about 1 second of audio. Was there ever a version above 0.3 alpha?

By the way, when only one UART was enabled, is there any problem when RX and TX are both assigned to the same UART, or I should have one UART dedicated per RX/TX?

I guess so. I was going to ask you about the same thing. I've seen mutexes/semaphores used across the project for SD and midi out, but not midi in. I think I'll have to figure out how midi in is handled.

Alright, thank you for the follow up. A few insights/tips on the structure of MIOS32 would be more than enough for now. I do not intend to use BLM, ENCODERS, or any external hardware at the moment. I'm just trying to make my way and see how things work altogether inside MIOS32 core.

no clue... since my knowledge is need to know (me also having a hard time to absorb mios...coming more from a musical background then from programming...learnd c while exploring mios...) but maybe it is a midi mutex thing? combined with a buffer?

i dont have a generic midicontroller code for the blm... i run my project "triggermatrix" on it which is in first case a note processor, in 2nd a sequencer, in 3rd a midigroovebox(without audio). for the blm part i used the blm-scalarcode and stripped it down, and mooved it into the main.c. when the blm-pcb gets into its final revision (aka oneside is pick and place - and a bulk order is on its way) i can provide a skeleton project... i am a bit busy... so thiswill take a while

You're probably right. MIOS32 itself comes with plenty of tutorials and examples, yet I find it very difficult to absorb. By the way, I'm trying the Midi file player, and just implemented the TASK_MIDI_Hooks from the programming model, but only a fraction of notes (output from MIOS studio PC app) are received and the receive handler always times out on port 0x20. Any clues?

an arp needs the seq.c .. at least i would use it. in the seq.c i would build a simple counter 1 2 3... 1 2 3.... which only starts when aFLAG is high (aka note was pressed) ... where the max is (3) is set by a global variable which itself is set in the main.cin your UI depending on your arp steps (up dow up...upup up down)....the counters output in seq.c i would send into your arp task to trigger events.... if donewith arp stuff/or released the keypress then i would set the FLAG low, so the seq is stopped putting out triggers. i dont want to release the triggermatrix code since noone but me can understand - and the only usecase then left is thata company pirates it

By the way, I have been to your BLM matrix, but I couldn't see the project code. I'm trying to do an advanced ARP. and/or a pattern player. No step sequencing is involved. Any input is highly appreciated..

Well, I believe I found it. The "programming model" from main.c has to be always provided, thus the task TASK_MIDI_Hooks, which in its turn assigns/registers APP_MIDI_NotifyPackage. The separation between main (programming model) and the rest of the app modules had its pros and cons.

cant say... what are you trying.to do?

I just found your reply by coincidence. I was waiting for months and didn't expect to hear back from anyone. I have posted a new question regarding the programming model of MIOS and would love to get some feedback.

Hello, Could someone please tell me where APP_MIDI_NotifyPackage is used or assigned to its default handler, MIOS32_MIDI_Receive_Handler, in any of the projects? The only reference I found was in the main.c of the programming model, however, most tutorial apps, projects like Midibox SEQ, and LoopA, all of them had this function declared, but without assignment to a receive handler, as it is the case in the programming model where TASK_MIDI_Hooks assigns/registers it at line #257. The following from LoopA app.c: ///////////////////////////////////////////////////////////////////////////// // This hook is called when a MIDI package has been received ///////////////////////////////////////////////////////////////////////////// void APP_MIDI_NotifyPackage(mios32_midi_port_t port, mios32_midi_package_t midi_package) { // -> MIDI Router MIDI_ROUTER_Receive(port, midi_package); // -> MIDI Port Handler (used for MIDI monitor function) MIDI_PORT_NotifyMIDIRx(port, midi_package); /// -> MIDI file recorder /// MID_FILE_Receive(port, midi_package); // Record midi event in loopa loopaRecord(port, midi_package); // If we are in the MIDI monitor screen, output a packet dump MIDIMonitorAddLog(1, port, midi_package); // forward to MIDI Monitor // SysEx messages have to be filtered for USB0 and UART0 to avoid data corruption // (the SysEx stream would interfere with monitor messages) u8 filter_sysex_message = (port == USB0) || (port == UART0); MIDIMON_Receive(port, midi_package, filter_sysex_message); /* Output MIDI IN activity on the frontpanel LEDs */ switch (port) { case UART0: MIOS32_BOARD_LED_Set(0x0002, ~MIOS32_BOARD_LED_Get()); break; case UART1: MIOS32_BOARD_LED_Set(0x0004, ~MIOS32_BOARD_LED_Get()); break; case UART2: MIOS32_BOARD_LED_Set(0x0008, ~MIOS32_BOARD_LED_Get()); break; } /* // Draw notes to voxel space if( midi_package.event == NoteOn && midi_package.velocity > 0) voxelNoteOn(midi_package.note, midi_package.velocity); if( midi_package.event == NoteOff || (midi_package.event == NoteOn && midi_package.velocity == 0) ) voxelNoteOff(midi_package.note); */ }

hei i stripped down the BLM-Project (so it cant be cloned with out weeks off routing U B ;) ) BLM-how-to.zip and i wrote some explaination... basicly i made a Grid with a center-cross - so a single button-LED-Fottprint can be placed correct to the Rubber-Button-Grid... you may have to set a a new "zero position off the Kicad Grid" to this crosses when you place the Button-LED-Fottprint on them... this Grid also have the Holes for the PCB which are needet to hold the rubber in Position.. maybe you find a "Flip-Chip" Variant for your RGB-LED... it would be better... you should not place it on the TOP side off the PCB... because it will illuminate the Neightbar-Button-Rubbers... The Hole in the PCB where the LEDs shine thru, act as a Light-Shield... I too have to draw a RGB-LED board (for a other Task, to illuminate a Frontpanel...), since i dont have expierence with that RGB-LEDs... this will take a while... if you found a solution i would copy it from you.... At Kicad 7... didnt know there is a stable out... good to know... will update too (else i cant check your projects)

Here are some pictures: The gate connector was drilled out and replaced by the MIDI IN connector.

Thanks It's mostly to look at how you designed it. I would adapt it for the sparkfun 2x2 pads i would like to use it with rgb leds

Hi all, first I want to thank you TK and all the other friendly people here. And I know that I'm a little bit late... A few years ago I midificated (that means only a MIDI IN) a Crumar Performer string synthesizer with an old PIC (that was lying around from other midibox projects) and Midio128 old version. I designed a little PCB that houses the optocouplers and mounted some of those PCBs beneath the keybed. It workes fine. But when I used it yesterday controlled by another keyboard with a sustain pedal I remembered that the sustain-pedal-functionality doesn't work. And I would like to implement it. But after a look into the software code it seems that this will not be that easy for me. Is there anywhere a function implemented that buffers MIDI OFF messages for the DOUTs if the hold pedal ist pressed and sends them if it is depressed? Hope someone can help me. Best clem!

yes i can share it... will take a while... do you want to use it in a button-led-matrix "scalar" way?

Thanks a lot, m00dawg! :) Many greets, Peter

Thanks!

That's absolutely glorious Peter! Nice work (as always!)

You can leave off the USB, it's only an additional +5V power option selectable by jumper..

Hey there getting some more work done on my euro modules that I hope to connect to my MB-6582 (I know Ive been working on this for like three years, lmao, always something else I need to do first). Anyway, just trying to get a handle on the USB port on the euroceiver module. It is *exclusively* used as a 5V power input, correct? But...what is the intended use case for that scenario? with the onboard vreg *and* the option to get 5V from the euro power bus, I can't think of why anyone would ever want to pump in 5V over USB from the front? Can the gate/CV modules also run from the USB 5v or something? I'm designing my own panel that combines the euroceiver, one gate out module, and one CV out module. Is it chill to just leave the USB port off the board and close up that hole in the panel? or is there an important reason to keep it around that I'm just missing?

After too long time, finally a new track: Only SIDs make it possible (no other synths used for this one), listen loud, plz! :) Many greets, Peter

PM sent.