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)
|
Release Candidate Firmware V1.24 RC12 - 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: Release Candidate Firmware V1.24 RC12 (/showthread.php?tid=987) |
RE: Release Candidate Firmware V1.24 RC8 - depaffect - 02-21-2021 It would be awesome if the trigger info was displayed at the bottom of the screen in the trigger 16 patterns - like it is in the modular pattern screen! At the moment it just says "EXTERNAL TRIGGER 1" etc at the bottom of the trigger 16 patterns, rather than "Trigger 15ms" etc which is super helpful in the modular patterns, especially with the new trigger functionality. Similarly, having the FX info displayed down the bottom in table screens (like it is in the modular pattern screen) would be awesome too! RE: Release Candidate Firmware V1.24 RC6 - mgd - 02-21-2021 (02-19-2021, 03:39 PM)XORadmin Wrote: It is possible that you upgraded from an older version (below V1.22A) then you definitely need to calibrate the inputs once anyway. Do I understand this correctly: My NerdSEQ was on V1.21A when I bought it and I then upgraded it to V1.23A (currently V1.24RC8). Since it was on V1.21A I should calibrate it by following the advice as of the NerdSEQ User manual pages 75 (very bottom) through page 76 and ending on page 77? If that calibration is required, how would I have known about that? (I stumbled over the above remark kind of accidentially Kind regards, Michael RE: Release Candidate Firmware V1.24 RC6 - XORadmin - 02-21-2021 (02-21-2021, 07:59 AM)mgd Wrote:(02-19-2021, 03:39 PM)XORadmin Wrote: It is possible that you upgraded from an older version (below V1.22A) then you definitely need to calibrate the inputs once anyway. You only need to recalibrate the inputs, not the outputs. It is actually a 1 minute job. half a minute to connect the 4 patch cables from the output to the input and half a minute to get to the auto-calibrate inputs screen. And don't forget to use the offset switch to the right. Nothing else needed. I should mark this in the manual. I have a note with the release notes of the firmware that this was needed. RE: Release Candidate Firmware V1.24 RC8 - XORadmin - 02-21-2021 (02-21-2021, 12:32 AM)depaffect Wrote: It would be awesome if the trigger info was displayed at the bottom of the screen in the trigger 16 patterns - like it is in the modular pattern screen! At the moment it just says "EXTERNAL TRIGGER 1" etc at the bottom of the trigger 16 patterns, rather than "Trigger 15ms" etc which is super helpful in the modular patterns, especially with the new trigger functionality. Actually, the trigger expander doesn't have the new functions yet. That is another job on my 2do list. About the details in the statusbar, I know they are missing in some places. The fact is that they in the most cases share the same information, but i need to refactor actually quite a part of it to have these generic. For now I decided to skip it for this release. RE: Release Candidate Firmware V1.24 RC6 - mgd - 02-21-2021 (02-21-2021, 08:06 AM)XORadmin Wrote: You only need to recalibrate the inputs, not the outputs. It is actually a 1 minute job. half a minute to connect the 4 patch cables from the output to the input and half a minute to get to the auto-calibrate inputs screen. And don't forget to use the offset switch to the right. Nothing else needed.Ah. That was simple and took almost no time Kind regards, Michael RE: Release Candidate Firmware V1.24 RC8 - theotteryears - 02-22-2021 is it possible to repurpose unused CV outputs into Trigger outputs? Can we please be able to send out triggers on these? RE: Release Candidate Firmware V1.24 RC8 - mgd - 02-23-2021 To some limited extend this is currently possible. See last paragraph on page 45 ff of the manual. Kind regards, Michael RE: Release Candidate Firmware V1.24 RC8 - theotteryears - 02-23-2021 this refers to the CV16 expander though right? I was meaning the CV local outputs - setting a note value and using the KILL command doesn't seem to work for me here... RE: Release Candidate Firmware V1.24 RC8 - XORadmin - 02-23-2021 (02-23-2021, 01:38 PM)theotteryears Wrote: this refers to the CV16 expander though right? I was meaning the CV local outputs - setting a note value and using the KILL command doesn't seem to work for me here... The Kill command resets the trigger output and is not related to the CV or MOD outpus. I would either set a MOD to 800 en the next step to 0 (if the offset is on the right) or i would maybe put a MOD 800 in a FX and a MOD 000 in the same row. It might be enough to trigger something but might also be too short. Another option could be an envelope which can create also triggers of course (zero attack, Peak half way, sustain the same half way, zero release and the decay defines your time). And they are probably more possibilities...a table... just take care of the voltages. RE: Release Candidate Firmware V1.24 RC9 - XORadmin - 02-25-2021 UPDATE RC9 - refactoring of the statusbar view. Added now all missing details to the stausbar in the patternscreens, table and patch screen and some other little beauty fixes Files in the first post are updated. |