Some thoughts on future possibilities

[XORadmin]

1. Page Up / Page Down button behaviour: Could this be the same as cursor behaviour? Long press cursor works (data changes fast and navigation changes fast) but long press Page Up Page Down does not have the same behaviour.

Yep, requested before and will do that at some point.

2. Can we have Basenote option in MIDI FX?

There is Basenote for all track types

3. Can we have more information in Current Values? Basenote would be very good to have there.

Basenote is not a value that stays. It is only valid until the pattern is finished. For now the current values screen doesn't have any scrolling and you can see the most important values. If it is gonig to scroll then you don't have that direct view anymore. But I'm going to check that in the future when more functions are included.

4. Copy Colours with Mark (copy paste etc.). This currently leaves colours behind and the only way I see to move colours with patterns in a sequencer window is to delete empty positions to move the patterns AND their colours together.

This is very specific. One would not like these to be copied since they mostly belong to 'blocks' for them while others would like your approach, where you give patterns a specific color. I got to see what I'm doing with it, but that at a very low priority.

5. Visualisation of Probability % in the empty space at the bottom right of the Pattern window. The No.1 issue I have when working with probability is troubleshooting why something is not playing or not changing in some way. Its almost always probability percentage but if I could see FX % value in a similar way to the note activity in the Sequencer window that would be so helpful. There is space!

Yep, definitely usefull and this space need to be crowded.

6. Mute / Solo behaviour in Sequencer window is Great! Can we also have the same behaviour in the four MIDI note column?

Could be possible.

7. I've mentioned this before but the copy and paste approach using MARK is for me very slow. I also know that this is likely to be evolved soon! 
I really think I'm actually finding the Mark system challenging and sometimes wonder am using it correctly. Look forward to seeing next update approach! 
But anyway... The approach that would work faster for me is: 


Shift Copy -> Shift Copy (simply puts entry into memory for a paste command using Shift copy again)
 
Shift Delete -> (removes entry but also places it into memory for paste command using Shift Copy)

What you should consider is that this is a 3 button option to do all this. With a regular computer you got more buttons to archieve these things.
You will for sure get used to it and it allows all kind of copy/paste situations. And in the new coming version it is copy/cut and paste.
I agree that the name copy is maybe not the perfect chosen word, but that is now what it is and in the end it does copy ;-)
Do you know that there is also a mark all option in patterns? (SHIFT + DOWN)

I am not going to change the behaviour as it is right now. The new coming version got some improvements but that is all I will do with it.

8. Clock multipliers that allow for different tupelos (triplets, maybe even quintuplets, septuplets. etc... but definitely triplets. I've searched forum for answers to this and have not found anything that works using multipliers. Groove for me is quite a slow solution.

Answered that already.

9. Okay this one may be impossible... BUT. How about an EVERY or MAX function that can supplement the generative side of things like probability? For instance, EVERY 6 would only play THAT entry every 6th pass. Or Maybe every even EVERY 0606 is every 6th pas and EVERY 0406 is a repetition between four and six times on every pass (just add a random between 0 and 2 to 4 every pass to determine when the next event takes place. Similarly a MAX entry could state that an entry occurs a maximum of N times (So MAX 0009 would meanthe entry happens 9 times and then stops).

That has been discussed as well. As much as I would like to have the conditional stuff, to get the functionality every cell would need it's own counters and there is simply no memory for that.


I got to say that these packets of feature requests are very hard to find afterwards.
I can't read all the threads deeply to see what was in there when I am adding features. (Sometimes I need to find time to develope stuff ;-)  ) The ones which point out that one function in the subject got a much higher chance because I recognize it fastly.