mattias

I am having trouble to read the SD card on Mac OSX... reports 2 TB and unreadable?? Any ideas??

An A/B seq. select for fills maybe.. hmm.. it is probab doable now??!! And how about if internal loopback routing was on the recive channel (not the sending), that way one loopback could control more than one track.. just thinking here. Maybe alredy doable!!?

I think this is evolving just fine TK.. But I think every track should have a dedicated loopback track... were every loopback parameter is displaed in name not CC.

A Gate time Trigger or Layer to vary the time intervals between the steps. The steps can be set within the range from 1/384 to 16 1/1 notes. Like on the Scritty... or even higher resolution.. Midi processors for internal routing... with midi fx... LFOs and midi filters.... maybe the arp. should go there More random stuff... rotate....skip closed gates ... random move active gates selected and or random chance by percent... There is alot of crazy stuff that can be done here... Maybe 16 tracks for internal loopback so funktions can be muted / toggled on off. This would be like dynamic editing... the seq programning itself. So we can have tracks triggering Track directions, Track direction progressive parameters, clock divider for each track, normal and tripled, groove quantiasion start and stop of sequnces and loop points. I think all my ideas can be done with 16 internal loopback tracks like the 16 new drumtracks!! YES lan midi please.. wifi?? Possible?? I don´t mind features like 128 steps... but please keep it a stepseq... 64 steps is fine even 32 as it is now.. A memory place holder for timebase and groove... using gp buttons to change the tempo and groove quickly... Drummaps.. yes please!! Nameable!! More CC layers in the mixer map... Maybe a daw mackie/LC controller... maybe not keep it a seq... Midi sync. delay calibration.. Clock sync delay in ms... from say -30 ms to +30 ms Maybe my ideas are to crazy but think about it.

Ok TK.. get the picture now I thougt it was ment to stay in edit mode.... sorry.... still some weird things going on if you use the GP buttons/encoders in layer display! And I do use the edit button... ;) ...it´s a nice feature now that I got it explained.

I think i have noticed something that has changed! Maybe a bugg!! Goto layer asingment! Press Layer A Turn a GP encoder or push a GP button... Now you are back in layer asignments.... Think all menues work the same way... Think it would be nicer if you could jump to the track with Trigger and Layer!! Hope you gys understand what I ment!!

How about a drummode event 3 individual gates (notes) per layer!! I know this can be done but it is not straigtforward... And mybe a simple chord event mode wher you trigger chords insted of notes... Maybe a LFO event mode where you can trigger an LFO restart, sending CC, and LFO speed back to the LFO!! Just some ideaes!!

:-X Ok... I see it was in main.h...sorry! I am not at really a programer.

So I have to change things in the sourcecode? main.c? How do I set it up for MB seq. Mackie emu?? And change lc_dio_table_mbseq.inc to my needs. Make the hex file. But main.c is were I need help!

It works! Now all i have to do is map up buttons and encoders for ableton live and my workflow! :D Things were a litle wierd... what is mapped to what? :-\

Is it for PIC18F452 only? or can I use mb seq 3 as is?

Gould we get Gp butons to send CC in the midi map? It would be nice to have!! ;) And nrps so we could control MB sid 2!!

MBLC! Can I use encoders insted of motorfaders? ::)

Could it be done??

Any chance of getting some?