+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: Firmware / Manual (https://forum.xor.eu/forumdisplay.php?fid=11)
+---- Thread: Release Candidate Firmware V1.18 (RC3 UPDATE) (/showthread.php?tid=285)
RE: Release Candidate Firmware V1.18 (RC3 UPDATE) - XORadmin - 02-18-2019
(02-18-2019, 09:47 PM)theotteryears Wrote:(02-18-2019, 09:45 PM)XORadmin Wrote:(02-18-2019, 09:44 PM)theotteryears Wrote: Hey Thomas,
Just installed the Nerdseq - it is most excellent
great job on making this module. I love it.
One quick thing I've found (not sure if this is due to the new firmware or if this is a bug otherwise) but when you create a table and place it on the first 4 steps, it does not play the table on the first step.
I can attach screenshots if helpful - or make a short video?
Thanks,
Chris
Great timing! I just released this version as stable version ;-)
Maybe you attach the savefile, then i can check it myself....or a video is also always handy.
haha aw im sorry! I literally just put it in my rack
ok cool - ill see if I can attach the save file for you!
I think i see already after your edit your problem.
Tables and especially the FX section in the tables are smart in their way of not changing a value if it didn't change, to avoid too much internal (and external) data-flow.
And by putting in always the same trigger the table doesn't update it anymore, as it doesn't change. ( For the table a trigger is just another label... )
You can work around that by using something like 10 in the first for, 20 in the 2nd, 10 in the third....
It was discussed in some old thread and i didn't think about to change it yet.
Edit: didn't see your savefile yet, i will do that tomorrow morning.
RE: Release Candidate Firmware V1.18 (RC3 UPDATE) - theotteryears - 02-18-2019
I'll give that a try.
listening to it though it just seems the first step missed out a couple of beats from the table... the others play fine all set to the same value.
anyway take a look and let me know tomorrow! also thanks very much for sending the parcel so fast!
RE: Release Candidate Firmware V1.18 (RC3 UPDATE) - XORadmin - 02-18-2019
(02-18-2019, 10:01 PM)theotteryears Wrote: I'll give that a try.
listening to it though it just seems the first step missed out a couple of beats from the table... the others play fine all set to the same value.
anyway take a look and let me know tomorrow! also thanks very much for sending the parcel so fast!
Yes i will take a look to it for sure. Was just a blind guess.
RE: Release Candidate Firmware V1.18 (RC3 UPDATE) - theotteryears - 02-18-2019
on more investigation... if you delete the note value, everything works as expected.
RE: Release Candidate Firmware V1.18 (RC3 UPDATE) - XORadmin - 02-18-2019
(02-18-2019, 10:13 PM)theotteryears Wrote: on more investigation... if you delete the note value, everything works as expected.
If you keep the note value and add a Kill 000 FX command?
RE: Release Candidate Firmware V1.18 (RC3 UPDATE) - XORadmin - 02-19-2019
(02-18-2019, 10:13 PM)theotteryears Wrote: on more investigation... if you delete the note value, everything works as expected.
I checked your file and no issue at all.
The note inserted automatcally sets the gate and so the same trigger output. The tables running do the same and so they interfere with each other.
You can turn that auto gating off by adding the Kill 000 command in the FX column on the same step where the note is, and then they won't be any of the mentioned issues.
In fact: Kill 000 takes care that the current Trigger/Gate value doesn't change when a note is filled in. So it stays on if it was on and it stays off if it was off and only the note will change (if it was different).
RE: Release Candidate Firmware V1.18 (RC3 UPDATE) - theotteryears - 02-19-2019
Perfect, thank you for checking. I thought it would be user error