garageCube

Hi,

At the mo im just trying to get an external sequencer to trigger clips in M8, ive got the seqeuncer triggering the clips ok at first, however then when I go to add another controller to the 'Edit MIDI map' the setting 1/0 has appeared to the one I want to control, and I cannot get rid of it, only add to it, which seems to be causing conflict when I then trigger the clip.
If anyone knows whats going on could they please help, because this is the only thing standing in between me having some real fun with Modul8.

Why don't you assign the controler to a different channel, so you won't have a conflict? Sounds like that is what's going on.

J.

kikumoto wrote:Hi,

At the mo im just trying to get an external sequencer to trigger clips in M8, ive got the seqeuncer triggering the clips ok at first, however then when I go to add another controller to the 'Edit MIDI map' the setting 1/0 has appeared to the one I want to control, and I cannot get rid of it, only add to it, which seems to be causing conflict when I then trigger the clip.
If anyone knows whats going on could they please help, because this is the only thing standing in between me having some real fun with Modul8.

I got this trying to use an electribe. Dunno why, in modul8 version 1, it didn't complain much, but in version 2, the Electribe seems eager to keep sending this "1/0" value and never stops. This slows down EVERYTHING in modul8.

Even if I ssign the keys correctly using my MIDI controller and then let the Electribe sequence something in modul8, it seems like this constant "1/0" message slows down modul8 to a crwal.

Do you have any idea of what's going on? I could post here one of those MIDI dump datas.

Well, that's probably the midi clock coming from your midi device.
Try deactivating it, by putting the clock to 00 bpm (off).

That solves the problem when using my Korg MicroKontrol.

Then reactivate it if you need it for your Lvie, for example...

If, for some reason, that is neither the problem, nor the solution, use midipipe.

VJ-A2D wrote:Well, that's probably the midi clock coming from your midi device.
Try deactivating it, by putting the clock to 00 bpm (off).

Interesting, though It has two problems:

1 - I used the Electribe for sequencing videos. With this solution, it wouldn't sequence anything
2 - When trying to use it as a launchpad, it's strange that setting it as syncing to an external clock would STILL send MIDI clock,

Let me try it real quick...
Ack! Cannot set the clock to anything lower than 20BPM

These bloody electribes! will test MIDIpipe, hope iit filters it! Thanks for the data.

MIDIpipe worked a treat. Indeed it was the MIDI clock signal!!!

But I wonder why it slows down the system to a crawl, even if 1/0 is NOT mapped anywhere

Will we get proper handling of MIDI clock data in v2.5, garagecube guys?

cool, if that solves your problem...
the "crawl" you describe is, in my opinion, coming from some other issue...

Nope, it was that the reason. Been discussed here:
http://www.garagecube.com/forum/viewtopic.php?t=785

Akira wrote:But I wonder why it slows down the system to a crawl, even if 1/0 is NOT mapped anywhere

Please could you try with this application to see if it produces the same problem :

http://www.versiontracker.com/dyn/moreinfo/macosx/16812

Thank you.

I'll try it immediately and will report later