[ChristianKeymaster]

I´m happy if you can see it that way, that is probably the best way to see it.

Well, as has come up a number of times, the pattern flash memory is full to the point where per-step features are quite impossible to implement. So, features that don´t need a whole lot of flash are way more likely to make it in.
In lack for a better term, I´d call them “behavioural” features, like the footswitches for example. Just adding a new behaviour by the push of a button, and not a different setting per step. But then these are limited by the use of buttons. I am really really happy now with the intuitivity of the interface, the direct access of every paramter. I think there might be room for a few more things without breaking it, but I´m really watchful about that and would rather leave out features than sacrifice ease of use at this point. Of course, some features will improve ease of use again, so …

As I wrote in the sticky of the feature request forum, I am sure to read every request and evaluate it. I can´t comment every request or promise specific features, but will continue working on it. Also, the development process might go slow at times, so if you can see new stuff as icing on the cake this is probably the best attitude towards new features in general.

[ChristianKeymaster]

Unfortunately this is not possible because of processing speed boundaries.

[ChristianKeymaster]

Hi Andrew,
the Zaquencer reacts to Midi Start (0xFA), Midi Clock (0xF8) and Midi Stop (0xFC) messages.
They all belong to “Midi Clock” or Midi Beat Clock type messages.

Can you check if your MC-909 sends these? E.g. with a connected Midi interface and a Midi monitor software on your computer.

Please keep us posted here.

[ChristianKeymaster]

alien is right, you cannot break anything by putting in the wrong numbers.

the inputting of the response code is not case sensitive, so for example you can put in “A” if the code if the code in the email says “a”.

most likely this is another issue and I´ve sent you an email to resolve it.

[ChristianKeymaster]

well I think by now you know how I´m not able to promise specific features
technically this should be possible. it´s more a conceptual problem, to cover all the scenarios, like what happens with legato mode when the sequence start and length parameters between the two patterns greatly differ. also in load menu I´m really running out of buttons!
there are the push encoders, but I don´t really like how they feel.
I like the idea and could imagine exploring it, but at the moment other features are more pressing in my book, so it would be a while anyway.

[ChristianKeymaster]

btw im always having strange behavior when a note is longer than the one that comes right after it… it seems the first note continues after the second note is done.

is this when the two notes have the same pitch? I have noticed that when this is the case and the notes overlap, the note off from the first note might actually turn off the second one, so that the first one continues longer. might that description fit what you´re experiencing? but this didn´t really strike me as a bug, more like how midi works…

[ChristianKeymaster]

I´ve checked this in the code and unfortunately the number of note length settings is limited to 16 (what we´re having now). The variable is only 4 bit, so it can point to 16 arbitrary lengths – this was already done to maximise the use of the flash pattern space.
It would be possible to sacrifice some of the longer noteLength settings for putting in shorter tick settings in between at the beginning.
Is anyony realisticly using 4 bars and 2 bars as note lengths?

[ChristianKeymaster]

That´s right, Midi Continue is not implemented so far.
It never seemed to play a role in the DAWs and hardware we tested it with, but we didn´t test them all of course. Shouldn´t be hard to implement, what would be the desired behaviour? Start playing if stopped? Do nothing if already playing?

[ChristianKeymaster]

I´ve just tested this again and for me it works like this
(very similar to what you´ve done actually).
For example:
- configure track 1 to play out on channel 1 on port A to your Synth
- configure track 2 to play out on channel 2 on port B and connect it to the midi in
- in global menu, choose setting for transpose 2.05 (this means that tracks 1-4 individually get transposed by midi channels 2-5, so track 1 will react to the channel 2 of track 2)
- make sure that both tracks are unmuted
- enable a touch of negative note delay on track 2, so that the transposing notes are generated before the actual note playing the synth on track 1

for troubleshooting: is the green “input” light flashing, so you see that the transposing notes are coming in? if not, maybe track 2 is still muted?

[ChristianKeymaster]

Hi Steve,
sorry to hear that you´re having trouble with the sticker.
I´m not aware of having had a bad batch. The stickers are individually packed by us, so I´m sure large deviations, if they existed, would have caught our eye.

It is a bit tricky to cover all the pre-printed writing on the BCR, but in our tests with the sticker we have found enough satisfactory positions to put it on.
I´ve just taken this picture, which is from the most recent batch of overlays (the one that went out to everyone so far):
https://flic.kr/p/pYUG5G

Please send an email to support@zaqaudio.com with your order number and we´ll see if we can do anything more for you.

• This reply was modified 11 years, 7 months ago by  Christian.

[ChristianKeymaster]

I think I understand the idea now.
To get more specific, would the gate you have in mind affect the notes generated on the respective track where the gate is placed, right?
The thing is, a feature like that would have to be coupled to every note generated. In midi you always have to know the note number for which you adjust velocity or note off.

You also already mentioned ratcheting in the first post. It might be more feasible to express the gate idea that you have in mind by ratcheting a note multiple times.
Should be similar, no? The note is being turned on and off in quick succession.

[ChristianKeymaster]

This feature is number 1 on our internal want-list.
I´ve run into technical difficulties when receiving very long sysex messages before, but there might, *might* be a fix on the horizon. So, at the moment I can´t say if this will be possible, but I can tell you that I am working on this with the highest priority right now.

[ChristianKeymaster]

great idea! but why stop there? I think it´s time to start working on my brain-implant midi step sequencer idea. don´t worry, it´ll be wireless midi, no need for an ugly din-sync midi jack on your forehead

[ChristianKeymaster]

You´re right, there is no dedicated function to clear a pattern included.
That came up in the beta as well and we´ve decided that recalling + storing an empty pattern from the back of the pages, just like you did it, would suffice.
It´s really just 3 clicks. Adding a special function for deleting the pattern wouldn´t be a lot easier to use and it would cost development time we´d rather spend elsewhere…

[ChristianKeymaster]

Happy to hear that! Thanks for the update and the kudos, very much appreciated

[Author]

Posts