The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.1.24 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



XOR Userforum
Firmware V1.28 Test Version - Printable Version

+- XOR Userforum (https://xor-electronics.com/forum)
+-- Forum: Products (https://xor-electronics.com/forum/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://xor-electronics.com/forum/forumdisplay.php?fid=6)
+---- Forum: Firmware / Manual (https://xor-electronics.com/forum/forumdisplay.php?fid=11)
+---- Thread: Firmware V1.28 Test Version (/showthread.php?tid=1604)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13


RE: Firmware V1.28 Test Version - septcercles - 09-01-2023

(08-18-2023, 03:50 PM)XORadmin Wrote:
(08-11-2023, 11:03 PM)trevormeier Wrote: I'm having lots of fun with 1.28 so far. It's a huuuuuuuge leap forward for how usable NerdSeq is with the rest of my rack.

I'd like to see more MIDI options in the mapping screen - for example gates (note on/off) and pitch bend. I often use MIDI to send gates, and pitch bend would allow some interesting things with MPE controllers.

In the interim I've been using the four CV inputs to receive triggers/gates... but I've noticed that the CV inputs have between 1-3ms of jitter when mapping them to trigger outputs. That's fine for most CV but quite a bit for gates & triggers (there's also ~1ms latency which is expected). The issue compounds with the 1.28 mapping screen: converting gates at the CV input to MIDI CC seems to add a little bit of jitter, and MIDI receivers tend to prioritize gates over MIDI CC data, so even more jitter is added on the other end of the chain.

All that to say: if note on/off (& pitchbend!) were available on the mapping screen it would make the most of the limitations of MIDI.

This firmware is really a big leap for the NerdSeq. I'm having so much fun playing with it. Thanks for letting us use it before it's 100% ready!!

Notes as gates should be possible though. But as I see it now it would be either only one defined note or a note in general. That should do the job, right? Also the note value and the velocity value could be a nice source.

There is by design a jitter of 1-2ms since the processing is each millisecond while the readout of the CV inputs (which is multiplexed) runs also around that speed (totally fine for recording etc). But indeed added up it might create a little jitter of 1-3 ms (hehe still much better than your USB Midi interface ;-)  ).
So nothing I can change about that.

Hi,
Thomas this is amazing,
So much looking forward for this huge update !
Talking about MIDI options in the mapping screen, could there be available in the sources of the mapping screen velocity, aftertouch, for interesting expressivity, and midi CC, to quickly add knobs and button to control envelops or lfo or whatever else ?
Heart


RE: Firmware V1.28 Test Version - XORadmin - 09-03-2023

(09-01-2023, 12:06 AM)septcercles Wrote:
(08-18-2023, 03:50 PM)XORadmin Wrote:
(08-11-2023, 11:03 PM)trevormeier Wrote: I'm having lots of fun with 1.28 so far. It's a huuuuuuuge leap forward for how usable NerdSeq is with the rest of my rack.

I'd like to see more MIDI options in the mapping screen - for example gates (note on/off) and pitch bend. I often use MIDI to send gates, and pitch bend would allow some interesting things with MPE controllers.

In the interim I've been using the four CV inputs to receive triggers/gates... but I've noticed that the CV inputs have between 1-3ms of jitter when mapping them to trigger outputs. That's fine for most CV but quite a bit for gates & triggers (there's also ~1ms latency which is expected). The issue compounds with the 1.28 mapping screen: converting gates at the CV input to MIDI CC seems to add a little bit of jitter, and MIDI receivers tend to prioritize gates over MIDI CC data, so even more jitter is added on the other end of the chain.

All that to say: if note on/off (& pitchbend!) were available on the mapping screen it would make the most of the limitations of MIDI.

This firmware is really a big leap for the NerdSeq. I'm having so much fun playing with it. Thanks for letting us use it before it's 100% ready!!

Notes as gates should be possible though. But as I see it now it would be either only one defined note or a note in general. That should do the job, right? Also the note value and the velocity value could be a nice source.

There is by design a jitter of 1-2ms since the processing is each millisecond while the readout of the CV inputs (which is multiplexed) runs also around that speed (totally fine for recording etc). But indeed added up it might create a little jitter of 1-3 ms (hehe still much better than your USB Midi interface ;-)  ).
So nothing I can change about that.

Hi,
Thomas this is amazing,
So much looking forward for this huge update !
Talking about MIDI options in the mapping screen, could there be available in the sources of the mapping screen velocity, aftertouch, for interesting expressivity, and midi CC, to quickly add knobs and button to control envelops or lfo or whatever else ?
Heart

Midi CC is already in there. Velocity and Aftertouch might be another thing, in fact velocity belongs to dedicated notes, so does polyphonic aftertouch. Channel aftertouch is a global one for the channel.


RE: Firmware V1.28 Test Version - Chess1 - 09-08-2023

I am not sure, but I am having some really weird issue where I think my internal clock is "broke". I was messing about with mapping and setting the global clock to be controlled by automater LFO. Now it seems like my global clock is 4x slower than normal...even when I create a new project ?!


Or maybe I am just tired and have forgot waht 120 bpm should sound like ( I do not think so though).


RE: Firmware V1.28 Test Version - XORadmin - 09-08-2023

(09-08-2023, 04:04 AM)Chess1 Wrote: I am not sure, but I am having some really weird issue where I think my internal clock is "broke". I was messing about with mapping and setting the global clock to be controlled by automater LFO. Now it seems like my global clock is 4x slower than normal...even when I create a new project ?!


Or maybe I am just tired and have forgot waht 120 bpm should sound like ( I do not think so though).

It’s late and you don’t have a feeling for rhythm anymore! :-)

No just kidding. I will check it out.


RE: Firmware V1.28 Test Version - Morim - 09-11-2023

Hi.

I have some questions about the mapping matrix.
Is it possible to "mute" a row?
I found mapping for euclidian density (mapping CV in), but can you change the offset in the mappings?

The mapping is great Smile


RE: Firmware V1.28 Test Version - XORadmin - 09-11-2023

(09-11-2023, 07:53 PM)Morim Wrote: Hi.

I have some questions about the mapping matrix.
Is it possible to "mute" a row?
I found mapping for euclidian density (mapping CV in), but can you change the offset in the mappings?

The mapping is great Smile

It is not possible to mute a row.
The offset is currently not possible (except for manually or with the knob on the multi-io expander) but I plan this as well as a mapping destination.


RE: Firmware V1.28 Test Version - Chess1 - 09-14-2023

(09-08-2023, 05:11 AM)XORadmin Wrote:
(09-08-2023, 04:04 AM)Chess1 Wrote: I am not sure, but I am having some really weird issue where I think my internal clock is "broke". I was messing about with mapping and setting the global clock to be controlled by automater LFO. Now it seems like my global clock is 4x slower than normal...even when I create a new project ?!


Or maybe I am just tired and have forgot waht 120 bpm should sound like ( I do not think so though).

It’s late and you don’t have a feeling for rhythm anymore! :-)

No just kidding. I will check it out.

Still running at 4 times less than normal speed. Only thing that I have not done is re-flash 1.7...


RE: Firmware V1.28 Test Version - XORadmin - 09-14-2023

(09-14-2023, 12:53 AM)Chess1 Wrote:
(09-08-2023, 05:11 AM)XORadmin Wrote:
(09-08-2023, 04:04 AM)Chess1 Wrote: I am not sure, but I am having some really weird issue where I think my internal clock is "broke". I was messing about with mapping and setting the global clock to be controlled by automater LFO. Now it seems like my global clock is 4x slower than normal...even when I create a new project ?!


Or maybe I am just tired and have forgot waht 120 bpm should sound like ( I do not think so though).

It’s late and you don’t have a feeling for rhythm anymore! :-)

No just kidding. I will check it out.

Still running at 4 times less than normal speed. Only thing that I have not done is re-f
I was not aware that you are talking about a general malfunction?
So after power on and without loading of a project your internal clock is 4 times slower?


RE: Firmware V1.28 Test Version - schematicwizard - 09-17-2023

Hi!

Contrats for this fantastic firmware!

I've got a small question, there is something I've been willing to do since the day I bought the More CV 16 expander:
I'd like to use the FX columns of my patterns to be able to sequence the CV coming out from the CV16 expander outputs.
Tell me if I'm wrong, but there don't seem to be any FX in track in "modular" mode to control the CV16 outputs values, so I thought with this firmware I could use the Mapping Setup to implement this.

The 16 special variables #A-#P seem to be the perfect way to achieve this, mapping each of them to a individual CV16 output.
But I couldn't find the way to put CV values in those variables from the pattern editor.

I found a dirty cheat using "FX3-4 Probability" from each pattern as 2 assignable variables (with values between 0 and 64), assigning them with FX1-FX2 in pattern editor (or in patch menu).
It works... but it is less than ideal: burns 2 FX columns for nothing, and no precise CV assignment (only 64 possible values)

I am missing something easier?
Are variable and|or NSA values editing from (pattern FX columns + patch menu) something that you plan to implement in a future firmware?

Cheers!


RE: Firmware V1.28 Test Version - XORadmin - 09-18-2023

(09-17-2023, 05:19 PM)schematicwizard Wrote: Hi!

Contrats for this fantastic firmware!

I've got a small question, there is something I've been willing to do since the day I bought the More CV 16 expander:
I'd like to use the FX columns of my patterns to be able to sequence the CV coming out from the CV16 expander outputs.
Tell me if I'm wrong, but there don't seem to be any FX in track in "modular" mode to control the CV16 outputs values, so I thought with this firmware I could use the Mapping Setup to implement this.

The 16 special variables #A-#P seem to be the perfect way to achieve this, mapping each of them to a individual CV16 output.
But I couldn't find the way to put CV values in those variables from the pattern editor.

I found a dirty cheat using "FX3-4 Probability" from each pattern as 2 assignable variables (with values between 0 and 64), assigning them with FX1-FX2 in pattern editor (or in patch menu).
It works... but it is less than ideal: burns 2 FX columns for nothing, and no precise CV assignment (only 64 possible values)

I am missing something easier?
Are variable and|or NSA values editing from (pattern FX columns + patch menu) something that you plan to implement in a future firmware?

Cheers!

I had this already in mind to set variables from the Sequencer. The only and most important issue is here that the FX columns in the Modular and Trigger16 tracks got only 3 digits, but a 4th digit would be needed to define which variable and the values from 0 to FFF. Adding 16x FX for the 16 possible variables is not an option. I do plan a reorganisation for the modular tracks though (CV, TRIG, MOD, PATCH, TABLE, FX probably split up to different screens) and then it would probably fit with 4 digits on the screen.

For now as a silly workaround you would create some rows which set the CV output to some values you decide in the mapping and call this row from the sequencer. Not too pretty and very static, but it does work for a few fixed values.