Information on new releases will be posted here with the newest release at the top. The firmware is available for download in Midi System Exclusive format at Github.com. The source code is available also but that’s only not needed if you are interested in developing. Otherwise follow the links to the latest release below.
Source code: https://github.com/Oortone/Nava-Oortone-Firmware
Happy programming!
********************************************************************************************************************************************************************
Nava Oortone Beta release 0.90 (February 2024)
Release name: 0tone_0.90b
Link to release: https://github.com/Oortone/Nava-Oortone ... e/releases
This is the first proper release. There was a pre beta available for a while but that has been removed. The biggest focus in this alternative firmware version is consistent behaviour when changing and chaining patterns and the ability to freely program pattern chains without having to hit Enter all the time, a feature already partly introduced in the Neuromancer version but now extended to the whole bank. The strain on the EEprom is also reduced considerably since save is only needed prior to changing banks, entering Track Mode or turning off.
The most important differences compared to the 2021Neuromancer Nava firmware are:
- Patterns are kept in RAM on a per bank basis. You only need to press Enter to save prior to switching banks or entering Track modes. Otherwise you can jump between patterns without the need to save. Switch bank without hitting enter to revert to the previously saved bank.
- Pattern chains (groups) can be freely programmed without the need to press Enter. This goes for both step and tap mode.
- Groups can not be saved in patterns. The whole group concept is completely different. You can chain patterns into groups playing patterns live interactively but groups can not be saved. I have posted the motivation for this at time mark: Jan 19th, '24, 11:56 below.
- Use Shift+Clear in Step and Tap Write to clear a pattern.
- In Track Write the Track End can be removed using Shift+Last Step.
- In Expander Mode there’s only one receiving midi number per sound. The erroneous duplicate triggering notes in earlier versions are removed. Note numbers can be found further down at time Feb 4th, '24, 23:43. Also note numbers for midi pattern change can be found there.
- Metronome now works in all modes.
- Strange behaviour in Mute Mode fixed.
- Bugs in External Instruments fixed, hanging notes and some more peculiarities.
Known problems in 0.90 beta:
- The stop button has no Continue function. This is intentional and hopefully a better designed continue function will be added in the next release.
- Patterns shorter than three steps will not work in Track Modes. This is due to a redesigned internal pattern change paradigm and will remain. In Pattern Play Mode patterns still can be as short as one step.
- Din Sync Out, Master mode: Lag on the synchronized slave unit seems to be a common problem. This might be fixed if it’s not too complicated. Problems in the code has been identified.
- Din Sync Out, Slave mode: In this mode the Nava could in theory work as a Midi Clock to Din Syn converter. However, Din Synced slave units often seems to play extremely slow. This problem looks difficult to solve and will most likely not be solved.
- There are still some unusual combinations where the Metronome doesn’t work. Try changing to Pattern Play and engage Metronome (Guide) and then it usually works. Hopefully this bug can be traced.
- Sysex is not working but the implementation on the 2021 version will be evaluated and maybe added if there are no serious bugs or drawbacks.
- Drum Notes Out (via midi) and Realtime Accent are removed. They will probably not be reinstalled. Realtime accent destroys Total Accent. Drum Notes Out occupy a bit too much of the sensitive time critical sections of the code. If there’s some reliable way to make it optional it might be reinstalled. In previous versions I believe midi channel could be changed to zero to disengage but the code was still executed to a great extent and I don't think that's a good idea.
