Release Candidate 1 Firmware V1.16 (RC6 UPDATE)

[XORadmin]

Rc4 looks like cannot load samples, I did something wrong? But Rc1 can before

Did you remove the sdcard and put it in again?
SD Cards with the NerdSEQ are not hot pluggable. So when removing and inserting a sd card you need to reset or power off-on the NerdSEQ. 
Pretty sure thats the problem.

Haha, I know that before I buy nerdseq because I visited user forum, so I know it's not the business of that, anyway It's ok now, may be I forget copy setting into the card or may be I also put another folder into the firmware folder.......

OK cool. It works now, thats the most important! Have fun!

[shledge]

It never fully drifts out, it's almost like there is a sync signal sent to it every few steps to "snap" it back.

I use it with 1, 4, 8 and 10 - all exhibit the same behaviour.

Can you send me the project please? So i can check the behaviour.

I just tested it myself and all seems fine. My guess is that the bitrate of the LFO is set to 4 or 2 maybe? Because then i get exactly the behaviour you describe. Speed 1 and bitrate to 16 and there should be no issue.

Bitrate set to 16 - the only difference was that I had them offset so they would be 0-5v.

I think the best way to show it is like this:

I  I  I  I  I  I  I  I  I
I   I  I I   I  I I   I  I

Top is the clock, bottom is the LFO - it's in "sync" but it slightly drifts every few steps.

[XORadmin]

It never fully drifts out, it's almost like there is a sync signal sent to it every few steps to "snap" it back.

I use it with 1, 4, 8 and 10 - all exhibit the same behaviour.

Can you send me the project please? So i can check the behaviour.

I just tested it myself and all seems fine. My guess is that the bitrate of the LFO is set to 4 or 2 maybe? Because then i get exactly the behaviour you describe. Speed 1 and bitrate to 16 and there should be no issue.

Bitrate set to 16 - the only difference was that I had them offset so they would be 0-5v.

I think the best way to show it is like this:

I  I  I  I  I  I  I  I  I
I   I  I I   I  I I   I  I

Top is the clock, bottom is the LFO - it's in "sync" but it slightly drifts every few steps.

How do you measure it? 
And please add or send me the project file so i can check it.

[shledge]

Checked on oscilloscope, compared to 16th clock out on nerdseq. Double checked with slaved PNW too.

I just got home from work so I'll send over project file

---

Here is the project file in question - I made it soon after upgrading to RC3.

[LowOveR]

the windows screen is really dangerous , nearly snort my beer in my rig ....

[XORadmin]

the windows screen is really dangerous , nearly snort my beer in my rig ....

Who what where how? Dunno what you are talking about 

[XORadmin]

Checked on oscilloscope, compared to 16th clock out on nerdseq. Double checked with slaved PNW too.

I just got home from work so I'll send over project file

---

Here is the project file in question - I made it soon after upgrading to RC3.

I can't see any issue. It updates around the tick. The only minimal difference in the update is a result of the LFO timings which has it's limits of course. I can't reproduce missing updates of the LFO of several ticks.

[shledge]

I think I'm probably hitting that limitation then - I brought it up because I was trying to use the LFOs as a clock source for other modules (eg. saw wave inverted and phased). Likely wouldn't notice it if I was just using it for modulation.

[XORadmin]

I think I'm probably hitting that limitation then - I brought it up because I was trying to use the LFOs as a clock source for other modules (eg. saw wave inverted and phased). Likely wouldn't notice it if I was just using it for modulation.

Yes possibly. Update time for the automators is 500 uS which gives a time window of 4mS for each automator. Most probably not fast enough for being a stable clock.

[shledge]

4ms sounds about right, that's around what I've estimated on the oscilloscope in terms of it's drift.