List of requests

[matsmile]

There are number of parameters that can be displayed in a decimal form as oppose to hex. I appreciate hex values in some cases but in many others they just make it more confusing.

1. Change number of steps in the pattern from hex to decimal (1-64) [Same goes for the Tables screen]
   
2. Change LFO speed to devisions/multiplications values as oppose to hex numbers, otherwise I have no idea what is going on especially when using synced LFOs.
   
3. Change offset and range of LFOs to voltage values.
   
4. It will be convenient if probability values could be 1-100% [PRTR 55%] {In general FX track values can be really confusing, maybe providing small description in the status bar what every number does can be helpful}
   
5. When manipulating automators via the FX column browsing through the ALS parameters is awful. Description in the status bar is helpful but damn I would prefer seeing the waveform (if I'm changing it) or seeing the devision (if I'm changing the speed) 
   

Next:

• Make values for duplets and triplets repeats in TR column more obvious. In many cases repeats I get are either too fast or to slow or last too long etc etc.
  
• Make notes in Tables automatically insert trig in the FX column. Inserting trigs by hand is tedious and if you don't have them there it's not triggering the envelope.
  

Further down the road:

1. Implement an arm recording function so it only starts recording when you start playing.
   
2. Add simple 4-8 step sequencer with clock divider to the automators list to enable internal modulation such as transposition.
   
3. Add clock dividers for patterns (and make them modulatable by the seq automator !)
   
4. And of course quantizer of some sort would be great.
   

Thank you !

[XORadmin]

Hey Mat,

thanks for your input, long list of requests you got there, some things are already implemented, some i already planned, some i think about and some i will most probably never do (because they don't fit the concept)

Change number of steps in the pattern from hex to decimal (1-64) [Same goes for the Tables screen

Just enable the decimal view and most values will also be displayed in decimal.
The reason the values are in Hex is that you only need 2 digits up to 255 and 3 digits up to 4095 where the decimal view would need an extra digit. That would of course not fit to the screen as it would also destroy the format (and decimal values with leading zeros are ugly    )

Change LFO speed to devisions/multiplications values as oppose to hex numbers, otherwise I have no idea what is going on especially when using synced LFOs.

The LFO's don't have a divider or multiplier. they only have either a free running clock which you can change from min to max value or if syncronised to the mainclock it does multiply using the speed. But thats also only for the regular waveforms. The noise acts different as it is not periodic.

Change offset and range of LFOs to voltage values.

Don't think about voltages here. They are no voltages involved and the only voltage destination are the CV/MOD outputs. The rest are internal parameters which are not voltage related at all, so it wouldn't make any sense. And you wouldn't know anyway whats going on the output as multiple modulations and sequences can be added together.

It will be convenient if probability values could be 1-100% [PRTR 55%] {In general FX track values can be really confusing, maybe providing small description in the status bar what every number does can be helpful}

All is in hex. Again also here, one couldn't fit a 100 in here. And, if the decimal view is enabled you get your 55% additionally.

I could probably add some more info to the statusbar here and there. But the trick is to learn the numbers because it makes your workflow so much faster. Cheatsheet is in the making.

When manipulating automators via the FX column browsing through the ALS parameters is awful. Description in the status bar is helpful but damn I would prefer seeing the waveform (if I'm changing it) or seeing the devision (if I'm changing the speed)

I think it is the perfect solution that fits totally into the sequencer and it's concept and of course on the screen. You can manipulate every parameter of automators on every step (and more) and having abreviations (and sometimes semi-cryptic numbers with meanings) are the key to learn how to use a tracker.

Make values for duplets and triplets repeats in TR column more obvious. In many cases repeats I get are either too fast or to slow or last too long etc etc.

Actually the trigger (TR) are not related to the BPM which you would need to get triplets, duplets...or ratcheting in general. A special ratcheting command will be implemented in one of the next versions (high on the priority list). However, you can generate these also using the tables.

Make notes in Tables automatically insert trig in the FX column. Inserting trigs by hand is tedious and if you don't have them there it's not triggering the envelope.

Thats already implemented in the latest version. Just enable it in the setup menu.

Implement an arm recording function so it only starts recording when you start playing.

The recording functions will be upgraded and i will consider adding something like that.

Add simple 4-8 step sequencer with clock divider to the automators list to enable internal modulation such as transposition.

You mean like the tables? You can transpose already in a sequenced way with these. There will be some nice automators in future versions. One thing i could think about is to use the tables also as automator source....

Add clock dividers for patterns (and make them modulatable by the seq automator !)

Clock dividers/multipliers for patterns/tracks are already on my 2do list. Lets see how i will integrate it and if i also integrate it to the automators.(as the automators are only track but not pattern related)

And of course quantizer of some sort would be great.

Yes, this is also on my 2do list.


Cheers
T

[matsmile]

Hey Mat,

thanks for your input, long list of requests you got there, some things are already implemented, some i already planned, some i think about and some i will most probably never do (because they don't fit the concept)

Change number of steps in the pattern from hex to decimal (1-64) [Same goes for the Tables screen

Just enable the decimal view and most values will also be displayed in decimal.
The reason the values are in Hex is that you only need 2 digits up to 255 and 3 digits up to 4095 where the decimal view would need an extra digit. That would of course not fit to the screen as it would also destroy the format (and decimal values with leading zeros are ugly    )

Change LFO speed to devisions/multiplications values as oppose to hex numbers, otherwise I have no idea what is going on especially when using synced LFOs.

The LFO's don't have a divider or multiplier. they only have either a free running clock which you can change from min to max value or if syncronised to the mainclock it does multiply using the speed. But thats also only for the regular waveforms. The noise acts different as it is not periodic.

Change offset and range of LFOs to voltage values.

Don't think about voltages here. They are no voltages involved and the only voltage destination are the CV/MOD outputs. The rest are internal parameters which are not voltage related at all, so it wouldn't make any sense. And you wouldn't know anyway whats going on the output as multiple modulations and sequences can be added together.

It will be convenient if probability values could be 1-100% [PRTR 55%] {In general FX track values can be really confusing, maybe providing small description in the status bar what every number does can be helpful}

All is in hex. Again also here, one couldn't fit a 100 in here. And, if the decimal view is enabled you get your 55% additionally.

I could probably add some more info to the statusbar here and there. But the trick is to learn the numbers because it makes your workflow so much faster. Cheatsheet is in the making.

When manipulating automators via the FX column browsing through the ALS parameters is awful. Description in the status bar is helpful but damn I would prefer seeing the waveform (if I'm changing it) or seeing the devision (if I'm changing the speed)

I think it is the perfect solution that fits totally into the sequencer and it's concept and of course on the screen. You can manipulate every parameter of automators on every step (and more) and having abreviations (and sometimes semi-cryptic numbers with meanings) are the key to learn how to use a tracker.

Make values for duplets and triplets repeats in TR column more obvious. In many cases repeats I get are either too fast or to slow or last too long etc etc.

Actually the trigger (TR) are not related to the BPM which you would need to get triplets, duplets...or ratcheting in general. A special ratcheting command will be implemented in one of the next versions (high on the priority list). However, you can generate these also using the tables.

Make notes in Tables automatically insert trig in the FX column. Inserting trigs by hand is tedious and if you don't have them there it's not triggering the envelope.

Thats already implemented in the latest version. Just enable it in the setup menu.

Implement an arm recording function so it only starts recording when you start playing.

The recording functions will be upgraded and i will consider adding something like that.

Add simple 4-8 step sequencer with clock divider to the automators list to enable internal modulation such as transposition.

You mean like the tables? You can transpose already in a sequenced way with these. There will be some nice automators in future versions. One thing i could think about is to use the tables also as automator source....

Add clock dividers for patterns (and make them modulatable by the seq automator !)

Clock dividers/multipliers for patterns/tracks are already on my 2do list. Lets see how i will integrate it and if i also integrate it to the automators.(as the automators are only track but not pattern related)

And of course quantizer of some sort would be great.

Yes, this is also on my 2do list.


Cheers
T

Thanks Thomas!
I guess there is no way around learning the hex values. 
I think there is still a way to improve the UI of the FX columns. Some of them don't even need to be hex values (Such as automator on/off or inversion). 
I honestly didn't even know that TR columns are not related to the BPM of the sequencer. I will try using tables for ratcheting.
Regarding probability. Aren't there three digits available in the FX column? I don't see the point of having 4095 values of probability, 0-100 will suffice. 
The idea for internal sequencer comes from numerology software. They have this thing called modulation sequencer that allows you to manipulate main sequencer.

[XORadmin]

Thanks Thomas!
I guess there is no way around learning the hex values. 
I think there is still a way to improve the UI of the FX columns. Some of them don't even need to be hex values (Such as automator on/off or inversion). 
I honestly didn't even know that TR columns are not related to the BPM of the sequencer. I will try using tables for ratcheting.
Regarding probability. Aren't there three digits available in the FX column? I don't see the point of having 4095 values of probability, 0-100 will suffice. 
The idea for internal sequencer comes from numerology software. They have this thing called modulation sequencer that allows you to manipulate main sequencer.

I don't think it is a good idea to have different kind of input (decimal and hex mixed) in the fx or any other columns. All the same is the concept here and i will keep on that as much as possible. Also it (nearly) always has been this way with trackers. I think the additional decimal view will help already getting used to the numbers.
Probability values don't go up to 4095. They only go to 64 hex which is 100%. All main values got a limit.
Also the automators are much more than LFO's and stuff and all have to fit into the same User Interface. Doesn't matter if the max value is 1 or 255. ( Values from the Automator FX column are scaled anyway because there are only 2 digits left for the actual value...something that would even be more limited in decimal view). This is not a high level PC with graphical VSTi's. The user interface here is build up to be as generic as possible and the Automator FX is in my eyes the most logic implementation. (I am always open for input regarding a logic implementation of new functions. But it also have to make sense with the current workflow and philosophy). Though i agree totally that it hasn't the comfort of Software DAWs on gigahertz PC's/Macs with gigabyte of memory. But for embedded it is very flexible and compact. You can see and edit all the parameters directly, together with a good overview of sequences, patterns, notes etc. There is nothing like this out there. Compared to other embedded sequencers (being it eurorack or other hardware) this is more than luxus (without dissing other sequencers....all are good in their own way, but they also follow their own philosophy).
One should also forget about all the classic modular/eurorack sequencers with their limited 16 step sequencing and like ratcheting as a highlight. The NerdSEQ is so much more and it doesn't try to copy these (sometimes boring) features the others have anyway.
Sure someone got to learn some things to fully use it's capabilities. But as i always say, this is nothing compared to the learning curve of a real instrument which needs years of practising until one can play it well.

I still don't get the additional sequencer you ask for. You can already use the tables (which is a additional up to 16 step sequencer internally) to manipulate like the transpose of a track or any other FX functions of the main sequencer. It can be enhanced of course, so if you got any good ideas that would fit into the concept, let me know!

It might sound a bit harsh but that isn't my intention. I just want to clarify some things and defend my design strategy. Trust me, i check all the feature requests and think about like priority, usability, function, how i could fit it into the current workflow and if they are even technically possible, because we are still dealing with a embedded system with limits in power and memory. But i try to implement as much as possible of peoples ideas if they make sense and i will keep doing this. Many cool things are still to come, my list is still very long....And some of your requests are in there as well.

[matsmile]

Thanks Thomas!
I guess there is no way around learning the hex values. 
I think there is still a way to improve the UI of the FX columns. Some of them don't even need to be hex values (Such as automator on/off or inversion). 
I honestly didn't even know that TR columns are not related to the BPM of the sequencer. I will try using tables for ratcheting.
Regarding probability. Aren't there three digits available in the FX column? I don't see the point of having 4095 values of probability, 0-100 will suffice. 
The idea for internal sequencer comes from numerology software. They have this thing called modulation sequencer that allows you to manipulate main sequencer.

I don't think it is a good idea to have different kind of input (decimal and hex mixed) in the fx or any other columns. All the same is the concept here and i will keep on that as much as possible. Also it (nearly) always has been this way with trackers. I think the additional decimal view will help already getting used to the numbers.
Probability values don't go up to 4095. They only go to 64 hex which is 100%. All main values got a limit.
Also the automators are much more than LFO's and stuff and all have to fit into the same User Interface. Doesn't matter if the max value is 1 or 255. ( Values from the Automator FX column are scaled anyway because there are only 2 digits left for the actual value...something that would even be more limited in decimal view). This is not a high level PC with graphical VSTi's. The user interface here is build up to be as generic as possible and the Automator FX is in my eyes the most logic implementation. (I am always open for input regarding a logic implementation of new functions. But it also have to make sense with the current workflow and philosophy). Though i agree totally that it hasn't the comfort of Software DAWs on gigahertz PC's/Macs with gigabyte of memory. But for embedded it is very flexible and compact. You can see and edit all the parameters directly, together with a good overview of sequences, patterns, notes etc. There is nothing like this out there. Compared to other embedded sequencers (being it eurorack or other hardware) this is more than luxus (without dissing other sequencers....all are good in their own way, but they also follow their own philosophy).
One should also forget about all the classic modular/eurorack sequencers with their limited 16 step sequencing and like ratcheting as a highlight. The NerdSEQ is so much more and it doesn't try to copy these (sometimes boring) features the others have anyway.
Sure someone got to learn some things to fully use it's capabilities. But as i always say, this is nothing compared to the learning curve of a real instrument which needs years of practising until one can play it well.

I still don't get the additional sequencer you ask for. You can already use the tables (which is a additional up to 16 step sequencer internally) to manipulate like the transpose of a track or any other FX functions of the main sequencer. It can be enhanced of course, so if you got any good ideas that would fit into the concept, let me know!

It might sound a bit harsh but that isn't my intention. I just want to clarify some things and defend my design strategy. Trust me, i check all the feature requests and think about like priority, usability, function, how i could fit it into the current workflow and if they are even technically possible, because we are still dealing with a embedded system with limits in power and memory. But i try to implement as much as possible of peoples ideas if they make sense and i will keep doing this. Many cool things are still to come, my list is still very long....And some of your requests are in there as well.

All good Thomas.
I see your point. I'm just lazy. But the more I play with it the more comfortable I'm with the current UI.