Vojtech. It's time for MDaw.

[mevla]

MSequencerMB. Different sequence depending on where the note is located. Plus all kinds of MIDI note FX, a bit like Bitwig but more like Melda.

[Hexspa]

mdrummer has a pretty decent sequencer already and it has midi out.

Hah! It's unusable.

Once you try to incorporate more than one time signature in your arrangement, whole thing breaks down.

Since different time signatures have to go in different channels, they have to always line up (to be divisible with each other). And even then the navigation through arrangement falls apart.

Add single 2/4 bar in 4/4 arrangement, and MDrummers sequencer is incapable of playing that.

If there's a workaround I would love to hear that.

Really, I think for changing time signatures, I'd use the rhythm editor and trigger those with midi. If you're saying you can't do that on a single channel and this creates likely misalignments then you can try separate tracks. That would be annoying if you had to constantly copy and paste changes to the kit, etc. but could functionally work. I don't know because I haven't encountered this.

I think I've never made an arrangement that doesn't have at least two different time signatures. Basic rock/metal mostly, nothing fancy. If you listen any that type of music from the past, it's pretty standard stuff.

That's why it seems so big oversight to me. I registered to the forum 2021 to ask this, but never got an answer.

I've worked out a workflow, where I create the arrangement in Mdrummer sequencer, with empty spaces (a drum loop with single hihat at 0 velocity) separating each section with different time sig, then dump the whole MIDI track into Reaper, where I splice and align all the parts ("items" in Reaper terminology) where they belong.

Using triggers to change time signatures is a pain to align and keep track of in Reaper.

Oh for sure. Yeah, I think exporting the midi is your best option. For better or worse, we don't get all our feature requests fulfilled here or anywhere really. But, believe me, I'm no stranger to odd time! My singer quit because they couldn't write melodies in it. Actually, now that I remember, I wrote the melody for the part and no one believed it was me. Anyway, the singer got mad and quit then tried to rejoin later or something. But, you know, f**k that.

The perils of odd time are many: less audience, reaper's grid is shitty in 6/8 (not even that odd), etc. That's why I usually avoid it these days unless absolutely necessary. No offense to your tastes but, pretty much, a lot of what people think is odd time is just bad phrasing. Not always, of course, see Meshuggah, but you can definitely rewrite a lot of things to work in 4/4, 3/4, 6/8 or other basic time signatures rather than 11/16 or something.

[Jacew]

mdrummer has a pretty decent sequencer already and it has midi out.

Hah! It's unusable.

Once you try to incorporate more than one time signature in your arrangement, whole thing breaks down.

Since different time signatures have to go in different channels, they have to always line up (to be divisible with each other). And even then the navigation through arrangement falls apart.

Add single 2/4 bar in 4/4 arrangement, and MDrummers sequencer is incapable of playing that.

If there's a workaround I would love to hear that.

Really, I think for changing time signatures, I'd use the rhythm editor and trigger those with midi. If you're saying you can't do that on a single channel and this creates likely misalignments then you can try separate tracks. That would be annoying if you had to constantly copy and paste changes to the kit, etc. but could functionally work. I don't know because I haven't encountered this.

I think I've never made an arrangement that doesn't have at least two different time signatures. Basic rock/metal mostly, nothing fancy. If you listen any that type of music from the past, it's pretty standard stuff.

That's why it seems so big oversight to me. I registered to the forum 2021 to ask this, but never got an answer.

I've worked out a workflow, where I create the arrangement in Mdrummer sequencer, with empty spaces (a drum loop with single hihat at 0 velocity) separating each section with different time sig, then dump the whole MIDI track into Reaper, where I splice and align all the parts ("items" in Reaper terminology) where they belong.

Using triggers to change time signatures is a pain to align and keep track of in Reaper.

Oh for sure. Yeah, I think exporting the midi is your best option. For better or worse, we don't get all our feature requests fulfilled here or anywhere really. But, believe me, I'm no stranger to odd time! My singer quit because they couldn't write melodies in it. Actually, now that I remember, I wrote the melody for the part and no one believed it was me. Anyway, the singer got mad and quit then tried to rejoin later or something. But, you know, f**k that.

The perils of odd time are many: less audience, reaper's grid is shitty in 6/8 (not even that odd), etc. That's why I usually avoid it these days unless absolutely necessary. No offense to your tastes but, pretty much, a lot of what people think is odd time is just bad phrasing. Not always, of course, see Meshuggah, but you can definitely rewrite a lot of things to work in 4/4, 3/4, 6/8 or other basic time signatures rather than 11/16 or something.

Yeah, indeed I'm not that keen on really odd time signatures. Just switching around typical 4/4, 3/4, 7/4, 5/4, 7/8 etc...

It's just irks me that I can't use the build in sequencer if I just add a single bar out of 4/4*, when it would be 3 times faster and half the work to do instead of repeteadly outing Midi, and cutting and pasting it in Reaper.

*(Think Livin' on a Prayer: Last chorus could never work as well, if they hadn't cut the previous bar short.)

[Hexspa]

I'm with you but the obvious counter to that is we're not far from the origin of drum machines and especially large multisamplers with sequencers in PCs. It's easier to request than develop, as you are doubtlessly aware. Regardless, I saw someone else post in another thread asking for MDrummer sequencer touch ups. Maybe your wish will come true.

[Jacew]

I'm with you but the obvious counter to that is we're not far from the origin of drum machines and especially large multisamplers with sequencers in PCs. It's easier to request than develop, as you are doubtlessly aware. Regardless, I saw someone else post in another thread asking for MDrummer sequencer touch ups. Maybe your wish will come true.

Yeah, I'm sure there's logical technical reason behind it.

It's just strange logic to employ in sequencer, because if it was less smart and would simply use triggers placed on a grid there would be no problem?

[sirmonkey]

Naive question on timing sigs:
If you start with 4/4 timing... couldn't you achieve 6/8 ot 7/8, or whatever,
using 2 or more bars of 4/4?

[Kalamata Kid]

Maybe better idea would be MSequencer ? I mean something like MSoundFactory (or MXXX) where you can insert many different "sequencer devices" to produce midi notes (and CC messages) Devices like HY-Plugins, Scaler 2, InstaComposer, UVI Sequencers or even Loomer Architect etc. In this way, we would have a full environment produced by Vojtech, which in a sense would "replace" the need for a new daw. Everything would then be consistent and uniform in operation.

Random Mthoughts:

MmidiMBmodularAIhostthirdpartypluginsFXsequencer

Make MSF into a DAW with third party plugin hosting capability.

What ever Vojtech does he should incorporate AI into the code. AI is the future.

A super modular midi plugin with sequencer and midi fx and third party midi plugins capability.

A super Unify/Mulab stand-alone and plugin with every midi idea that has ever existed. But my feeling Unify will eventually become a DAW and a be very capable and easy to use.

[Hexspa]

I'm with you but the obvious counter to that is we're not far from the origin of drum machines and especially large multisamplers with sequencers in PCs. It's easier to request than develop, as you are doubtlessly aware. Regardless, I saw someone else post in another thread asking for MDrummer sequencer touch ups. Maybe your wish will come true.

Yeah, I'm sure there's logical technical reason behind it.

It's just strange logic to employ in sequencer, because if it was less smart and would simply use triggers placed on a grid there would be no problem?

I'm not entirely sure what you mean; maybe because I don't use MDrummer that much. My suggestion is to write to Meldaproduciton with your ideas and try to be as clear and comprehensive as possible. Make a presentation with images and the whole nine yards. That's going to give you the best chance at having your idea implemented or at least considered - especially in a way that actually reflects what you want.

In principle, I'm open to developments in the sequencer or any MSequencer-type idea. I don't use sequencers that are subsidiary to the host's main one often but part of that is because they tend to be more limited. Sometimes that's good, I like XLN Audio's XO step sequencer, but sometimes it's not, XO's sequencer is really limited.

In summary, I can't help so good luck

[Jacew]

I'm with you but the obvious counter to that is we're not far from the origin of drum machines and especially large multisamplers with sequencers in PCs. It's easier to request than develop, as you are doubtlessly aware. Regardless, I saw someone else post in another thread asking for MDrummer sequencer touch ups. Maybe your wish will come true.

Yeah, I'm sure there's logical technical reason behind it.

It's just strange logic to employ in sequencer, because if it was less smart and would simply use triggers placed on a grid there would be no problem?

I'm not entirely sure what you mean; maybe because I don't use MDrummer that much. My suggestion is to write to Meldaproduciton with your ideas and try to be as clear and comprehensive as possible. Make a presentation with images and the whole nine yards. That's going to give you the best chance at having your idea implemented or at least considered - especially in a way that actually reflects what you want.

In principle, I'm open to developments in the sequencer or any MSequencer-type idea. I don't use sequencers that are subsidiary to the host's main one often but part of that is because they tend to be more limited. Sometimes that's good, I like XLN Audio's XO step sequencer, but sometimes it's not, XO's sequencer is really limited.

In summary, I can't help so good luck

Well, really I think whole reason sequencer in Mdrummer is what it is, because most use external triggers anyway for the program, so it's treated as it is for most; just low priority add on.

I think it's just up to Melda to decide whether it's reasonable to spend effort to. I'm certainly on the lowest possible tier as a client anyway. Only reason I'm bringing this problem up is, because no one else isn't and for the life of me I can't understand why?

[Hexspa]

Lowest possible tier? Nah, I don't buy that. Any company is lucky to have an influx of ideas.