Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Firmware V1.14
#1
Minor update which fixes a small issue:

When creating new patches the init value for tempo was 128 bpm. Now there is no init value anymore for the tempo.
Patches from old projects will be updated automatically.


Attached Files
.hex   nerdseq.hex (Size: 1,27 MB / Downloads: 29)
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#2
Updated to V1.14A. Removes a small visual glitch when being clocked externally.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#3
I seem to be having an issue with this firmware. When muting, it seems to only mute the trigs from the track the pattern is on, so trigs in the FX section of the pattern continue even when muted. I don't know if this is intentional but it makes for some slightly confusing behavior (even when everything is muted sound is still being generated in some patches).
Reply
#4
(03-20-2018, 01:30 AM)uniquepersonno2 Wrote: I seem to be having an issue with this firmware. When muting, it seems to only mute the trigs from the track the pattern is on, so trigs in the FX section of the pattern continue even when muted. I don't know if this is intentional but it makes for some slightly confusing behavior (even when everything is muted sound is still being generated in some patches).


Hey,
i will check this issue and get back to you. The patches should also be muted then.

However, CV/Triggers or Gate can still be manipulated from another track and then the outputs could still be changed anr/or turned on/off, triggered. Because the mute is not output based but track based. Just to be sure that this is not your issue.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#5
Hi,

i checked all screens for keyboard operation inconsisties as i am preparing a list of all possible keys and shortcuts in all screens.
These are my findings, which differ from the normal <SHIFT + CURSOR KEY> for changing a value:
Project screen: EDIT MODE: changes only with <OK>
Project screen: MIDI INPUT: changes only with <OK>
Setup screen: SHOW DECIMAL VALUES: changes only with <OK>
Setup screen: SAVE WITH BACKUPS: changes only with <OK>
Setup screen: DEBUG: changes only with <CURSOR RIGHT>
Reply
#6
(03-27-2018, 07:26 AM)ollim Wrote: Hi,

i checked all screens for keyboard operation inconsisties as i am preparing a list of all possible keys and shortcuts in all screens.
These are my findings, which differ from the normal <SHIFT + CURSOR KEY> for changing a value:
Project screen: EDIT MODE: changes only with <OK>
Project screen: MIDI INPUT: changes only with <OK>
Setup screen: SHOW DECIMAL VALUES: changes only with <OK>
Setup screen: SAVE WITH BACKUPS: changes only with <OK>
Setup screen: DEBUG: changes only with <CURSOR RIGHT>

Thanks for the reports,
Thats all the things i don't see anymore Smile

All correct and will be fixed for the usability consistency. It suppose to be OK to enter a possible menu, SHIFT LEFT/right to change a value (for menu based screens).
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)