Change midiclock sync and other midi questions

[jazzdoktorn]

Hola!

I have a few questions and stuff that i hop you can help me with:

Midi clock tempo

Is there a way to change the midiclock setting?
When i hook up one of my drummachines to mulab and set the sync to the right midi out the tempo is double when i press on start...
Is it a way to change the clock to half tempo?

Midi i/o

Could you consider to extend the midi i/o to more than 8x8 for Mulab UL?
16x16 would be more suitable.
My main midiinterface is 8x8 and my soundcard has 2x2 and to that i use usb drumpads and usb controllers to fill up at least 4 ins to.

Event input.

I come with this request every year in different shapes and i am well aware that it probably is getting quite annoying.
I need to record several midimachines at the same time.
The machines is sadly all sending at midichannel 1 and i would like to assign the machines to a dedicated track when i/we record midi from multiple machines at the same time.
It would be great to just press record and everything thats happening on machine "A" is going directly to track 1.
Machine "B" to track 2 ETC ETC
So i would like to assign every midi in on my midiinterface to a event input that is separated from the other.
I hope that you understand what im after here (english is not my first language and it is hard to be understandable sometimes).
If there is a way to do this without multiple assignable event inputs please tell me.

Midi clock out.

Is it possible to send clock out to several clock output modules?
It would be great to sync more than one machine at a time.


Thanks for your hard work on MULAB.
I have used it since version 2 and it is great in so many ways.
Thanks

[MuTools]

When i hook up one of my drummachines to mulab and set the sync to the right midi out the tempo is double when i press on start.

Is it with all of your drum machines/MIDI sequencers like this or only with a specific one?

Is it possible to send clock out to several clock output modules?

No, not yet. Can't you MIDI thru them?

[jazzdoktorn]

"Is it with all of your drum machines/MIDI sequencers like this or only with a specific one?"

The machines i am having trouble with for now is three midified Monotribes.
Somehow the sync from Mulab put them in double speed.
It would be great if there was a possibility to set halfspeed, doublespeed an somewhat untight swingsync.
If you are not interested in this solution; Is there anyway around this "doublespeed" in a setting somewhere in an .ini file or something?
That would be great.

"No, not yet. Can't you MIDI thru them?"

Sadly, Some of my machines are more or less homebuilt and do not have Thru..

How about my other suggestions about multiple event inputs and more midi I/O?
It would be great to get your opinion about them.

I am moving further and further away from softsynths an approaching hardware more and more and that has been good for my creative process.
Mulab is great and perfect for me in any way and is only a little limited in the midi area.

Thanks

[MuTools]

Is there anyway around this "doublespeed" in a setting somewhere in an .ini file or something?

No i don't see a way, sorry. Is that a bug in the MIDI sync processing of these machines?

How about my other suggestions about multiple event inputs and more midi I/O?
It would be great to get your opinion about them.

It sounds like a feature request to me.

[jazzdoktorn]

"It sounds like a feature request to me."

And with that i suppose its number 2001 on the list of feature requests...
I dont feel any interest at all about extending the mulab towards the midi functions i request.

[MuTools]

Did you read the linked text?

Here is the explicit link: http://www.kvraudio.com/forum/viewtopic ... 9&t=357048

[jazzdoktorn]

Yep i read it.

[jazzdoktorn]

Damn.
The thing is that i really love Mulad since version 2 when i got my eyes on it.
It has make wonders for me in my musical journey but now we might grew apart.
After i tried to get some good or at least workable workflow with my midi stuff i just feel to give up...
Mulab is great in many way but the midi routing with one event input is a disaster and
just one midi clock out makes me multitrack (and i really dont like that).
The very limeting 8x8 midi ins and outs is also frustrating because i dont se why its 8x8 instead of 16x16 or 32x32. Everything today conncts via Midi...I have to pull out one controller and plug in another when i need to... Not a good workflow,,,
I suppose its just me among the mulab UL owners having the same problems as i have, so priority is probably around zero for me to get something that i want.
And i get the impression that things not going to happen in a long long time.
I accept of course your creative process but at the same time i feel like i have to check around for something else to work with.
I think its going to be hard but the possability to have good midi routing, extended ins and outs and the ability to send midi clock to more than one output module..

Thanks for Mulab jo, it is a remarkable software.

Regards
Robert

[MuTools]

Robert, i can only hope you understand that there are many similar FR cases for other users too, for example users that request improvements wrt the MUX front panels, wrt audio parts, wrt more and extended MUX modules, wrt time stretching etc. etc. Even before your last post here i already had a draft look at increasing the num MIDI ins and outs and at first sight that's no prob. I did not impulsively add that to M6.3 as you never know it creates a complication (would need an extra test stage) and i wanted to release M6.3, didn't want to take the risk on a new complication, and thus having to delay the M6.3 release. I also realized that only increasing the num MIDI ins/outs would not be a complete solution for you. I'm sorry that i can't deliver all feature request of all users right now. I'm bound by certain realities. Said with all respect for your personal requests.

About using more than 1 MIDI clock out: I just had this idea:

* Create a Patch Point module in the session moular area
* Connect as many MIDI outs as you need to that patch point
* Now "Set MIDI Clock Out Module" to that patch point

That should deliver the clock messages to all MIDI outs connected to that patch point. I did not yet test this in reality, but there is a good chance that works. Didn't think of this before.

[jazzdoktorn]

Jo.
I understand that your up to your neck with FR that everybody wants right away or yesterday.
Probably a lot of the FR is already out there on the interweb, easy for everyone to buy and download themselfs.
Timestrech is a good example of that. Its hard to develop and expensive for you to buy in another solution...
I have also ideas about modules that i dont even want to put up as a FR because its just me that want them now.
For example a development of the " Midi controller generator" witch is a beast by the way , i use it a lot making midicontrollers for my synths.
A similar module where i instead of CC, could write down sysex strings.
That would open up the possibility to make synth programmers/controller in MUX and be a good sellingpoint among many others.
That is not a Feature request, its just a dream i have and i will say no more about it.

The Midi ins and outs and assignable events inputs on the other hand is something thats not an addon, its the program itself that are not complete and hard to work with. Im very happy that at least one of them is on its way. Thats a good thing indeed and thanks for that.
But i also really hope for the event input problem to be fixed. Workflow issues royale.

The patchpoint thingy is a good idea and i will try it as soon as possible. Thanks.

I got a little frustrated earlier when i posted my concerns and got a link to a post about feature request.
The post itself i read many times so there is no beef there but it would been more relaxing to hear " Take it easy its, on its way soon" or " Sorry that is not a part of my vision of the program".

And again, that the ins/outs is on its way is very very good. Thanks!

Regards Robert

[MuTools]

The Midi ins and outs and assignable events inputs on the other is something thats not an addon, its the program itself that are not complete and hard to work with. But i also really hope for the event input problem to be fixed. Workflow issues royale.

Having 8 MIDI input ports and 8 MIDI output ports resulting in 128 possible output channels is not too bad imho. Calling that incomplete or very limiting is exagerated imho, but opinions can differ of course. About how MIDI input works: It's not a problem, it's intended to work like this. That said, i have a note on the wishlist to also support a more modular use of MIDI inputs.

I got a little frustrated earlier when i posted my concerns an got a link to a post about feature request. The post itself i read many times so there is no beef there but it would been more relaxing to hear " Take it easy its, on its way soon" or " Sorry that is not a part of my vision of the program".

The problem is that if i have to answer each and every FR with an elaborated answer, which will most probably be replied on, and so the discussion then continues, then i'm loosing too much time to do so, each time again. That's why that "About FRs" topic is there to explain it once and i have to use that link to spare precious dev time.

And again, that the ins/outs is on its way is very very good.

Euh, i did not explicitly say so, but i understand your interpretation. If you could help testing it, then please email me about this, then maybe we can put a step forward.

[jazzdoktorn]

That was a good idea and im glad if i can help you in any way.
I will send you a mail about this in a day or two.

[jazzdoktorn]

I saw that you gave me 16x16 already!
This will help a lot.

Thank you!

[MuTools]

Yes but please properly test the 16x16 MIDI IO in M6.3.7 and let me know if there is any issue. Thx!

[jazzdoktorn]

Now i know what to do tomorrow:-)