Hi!

I'm experimenting with CV16 modulators, specifically LFOs.
I can set the LFO Speed from 00 to FF (256 different values). What I do not know and couldn't find in the manual is what the resulting frequency of a given speed value is.

For the Automator LFOs there is (or can be forced) a relationship between the length of a pattern and the length of a wave, thus the LFO frequency can be coupled to the song speed. Fine.

Is there a similar relationship for the CV16 LFOs and if not (my guess), how can I determine the precise frequency for a given Speed value?

The reason I wish to know these is that I'm trying to start several LFOs via FX with the same speed but with precisely determined phase difference. (i.e. at certain steps into my pattern/song). For that I think I need the LFO frequency (as I know the length/duration of a step).

Kind regards,
Michael

Quote:kriskeyman wrote: ↑Okay, I'm stumped. I have the trigger expander, and have a sequencer track designated to TR1-6 on the expander. I have entered triggers into the pattern, and inside the pattern view I expected to be able to move the cursor over a gate/trigger value of '10', and then press OK to send a manual trigger to the assigned output of the expander. But this doesn't work. Is there another way to trigger the outputs manually when the sequencer is NOT running?

Can a reset track FX or reset All FX option be added to the list of FX options? I think it would be a good option for controlling the FX you want only to be active for the sequences you are using them on.

When a sequence on an audio track that is set to use an oscillator wave (instead of a sample) is stopped or stop all sequences is initiated, the wave continues playing until you hit stop or stop all a second time. Can this be changed to stop the oscillator playing on sequence stop or end like the way samples stop playing?

I started using BRK FX set jump to 00 on tracks 1-6(BRK 0100) so that the sequence will infinitely loop and never move on to the next track when done. This way I can have sequences directly above and below each other without having a blank sequence in between to keep my project view tight. This works as expected on tracks 1-6 but tracks 7 and 8 seem to ignore the BRK 0100 command and just continue on to the next sequence in the track as soon as the last step is finished playing.

Is this a bug?

[repost from the General Questions section]

Q: Is there a way to have an island repeat x amount of times then proceed to the next adjacent island?

A: This can be achieved by using a dedicated control track. Here is how:

To further elaborate on the control track pattern:
On the control track you can use the SCLK 1XX function to slow down the control track and at the very end use STSP 0XX (as suggested by Thomas) to start your next island. Be sure to (re)set the clock of the control track to whatever is needed at the beginning of the new island.

Here an example:
if you have two islands on tracks 1-3, each two patterns long like e.g.


row T1  T2  T3  T4
00  00  01  02
01  03  04  05
02  --   --   --
03  10  11  12
04  13  14  15
05  --   --   --

and you want that repeated for 5 times you could denote track 4 as control track and add patterns like e.g.:

row T1  T2  T3  T4
00  00  01  02  06
01  03  04  05  07
02  --   --   --   --
03  10  11  12  16
04  13  14  15  17
05  --   --   --   --

and in the first row in pattern 06 you insert FX SCLK 105 (which is divide track clock by 5 immediately) and in the last row of pattern 7 you insert a FX STSP 003. The first line of pattern 16 should hold a FX SCLK 109 (normal clock) or whatever speed you'd need for that island's control track.

Kind regards,
Michael

OK, no one is posting tricks so far, so let me add one to get things started.

You want to sequence multiple notes but spreading this though multiple tracks or achieve this via the FX or patches is not your thing (though many ways are possible) and you don't have the CV16 expander.
Here is a quite nice and easy way to get there with the stock NerdSEQ (no expanders needed, not only the fixed chords functions).

Set the track to be a Midi track. You get the 4 midi columns now. The trick is that you can also sequence the CV/MOD/Trigger outputs from these Note columns and no Midi is involed at all.

Lets take the most silly chord in the western world: C - E - G with the use of one gate
In the Note columns you would fill in these notes and in the velocity columns of each you define the destination of this note. (Press SHIFT+OK in the velocity column to get to other destinations than midi velocity, browse through them with the regular increase/decrease control).
The note C would get a 'A1' in the velocity column which means gate on. (the current track is being used)
The other notes would be set to CV1..6 or MOD1..6 without the gate function.
A note off would be A0 then in the column where the 'A1' was.

You could use also one midi track to trigger up to 4 Trigger/Gate outputs directly = use it as a basic drum track.

They are more functions in there. Maybe this opens up new possibilities for you that you were not aware of.

Hi
I am relatively new with my Nerdseq so probably a simple problem
It turned up with Firmware 1.21. When I upgrade can I go straight to 1.25A or do I need to pick up all the features in order by going to 1.22, 1.23 and 1.24 first?
Secondly on the Sequencer screen it only allows 3 different sequence numbers of 00, 01 and 02.
Is that relative to the early firmware or is there a setting somewhere I need to change?
Cheers!

When I edit the user interface is there no capacity for the settings to persist on power on/off? Or is there something I need to do for my changes to persist?

Admittedly I don’t use the MOD outputs as much as I should, and I think this is mostly due to the vast range of value available: 000 - FFF 

I’m not sure if this is a typical tracker range so excuse my ignorance in advance! I’m still learning it. 
I often find the value range way too large to wrap my head around, the range really becomes abstract to me, and the difference between a value of 156 and 170 is soo precise that I’m often scrolling through random values to get the feel of what I’m after. 

From here I just go to the C-0 to A#9 as it operates in a more contained fashion, but I still don’t know what volts each value represents unless I measure it with another tool. Is there an option to display the volts being sent the the MOD output?

Why could we not have the option to limit the MOD value range of 0-100 for example?