e-licktronic Forum

e-licktronic wrote:

Neuromancer wrote:Now that E-licktronic has opened the source to the v1.028beta there are still some bugs and wishes left for some of us.

I have created a github repository to which anyone can submit.
https://github.com/BenZonneveld/Nava-909-Firmware

The idea for this thread is to collect wishes and bug reports for all firmware releases from v1.028beta onwards.

Great job

Thanks for giving the community the source they've been asking for.

Neuromancer

Neuromancer wrote: Perhaps a task for someone who doesn't know how to write code ?

Yes - this is where I could eventually help. I only cannot guarantee any delivery dates as I'm not so often in my studio (during summer in general way less than usual).
But if you have some topics/features/functions that should be documented, you can list them already and also point to the actual documentation so that it's possible to work on it.

Thanks,
F.

FlavioB wrote:

Neuromancer wrote: Perhaps a task for someone who doesn't know how to write code ?

Yes - this is where I could eventually help. I only cannot guarantee any delivery dates as I'm not so often in my studio (during summer in general way less than usual).

Wuss

It's a "chill" 29.6 Celcius in my studio at the moment....

It should be possible to create a wiki page on github for the documentation but my experience with github is very little, I used gitlab before.
I have been using git professionally for several years as code management was part of my job as UNIX/Linux specialist.
At this moment I'm doing some re-thinking on source code version management using git.
My idea of managing it is:

* A branch with the original sources patched for modern Arduino environments.
* The Nava2021 branch which should contain all merged updates.
Also I think all new features should be switches in the define file or maybe a new file, you could enable or
disable features this way.
* a beta branch with new features that still need testing.

FlavioB wrote:

Neuromancer wrote: Perhaps a task for someone who doesn't know how to write code ?

Yes - this is where I could eventually help. I only cannot guarantee any delivery dates as I'm not so often in my studio (during summer in general way less than usual).
But if you have some topics/features/functions that should be documented, you can list them already and also point to the actual documentation so that it's possible to work on it.

Thanks,
F.

A start I made for the documentation, uploaded the images from the v1.015 manual for reference use in the manual.
Now it's just adding the info from the original manual as a starting point.
I also added a page with the build environment setup from sandormatyi and invited him to the repository to give him write access

https://github.com/BenZonneveld/Nava-90 ... ser-Manual

I've merged sandormatyi's features and my features and build a firmware release.

Provided in both .hex and .syx format.
https://github.com/BenZonneveld/Nava-90 ... a-20210619

Greetz,
Neuromancer

Short list of things I noticed:

Bugs:
* In mute mode the tempo display is not updated.
* In track write the pattern IMO should not be reset to A1 after pressing enter. Just advance the position and stay on the last selected pattern.
* EXT instrument should be able to have 2 velocity levels.

Planned features:
* SYSEX import and export
* Make the startup mode configurable.
* Make the sound levels user configurable. Keep in mind the patterns store the current instrument levels.
* Temporary change last step in a playing pattern (Pattern play only)

Things I'm not implementing:
* Sending swing over MIDI clock. A device should not abuse MIDI clock to send swing. A clock has to be a source of a stable timing, swing conflicts with stable timing.

Neuromancer wrote:I've merged sandormatyi's features and my features and build a firmware release.

Provided in both .hex and .syx format.
https://github.com/BenZonneveld/Nava-90 ... a-20210619

Greetz,
Neuromancer

is this already a fully working release?

does it build up on the latest official beta firmware with additional fixes/features or how can we understand the concept behind it?

thanks anyway for your efforts. nice to see the community keeping this project alive!

General_Midi wrote: thanks anyway for your efforts. nice to see the community keeping this project alive!

Yes, thanks from my side as well.
Just a tiny request: would it be possible to add a "releasenotes.txt" file for tracking the changes/fixes? Could be structured simply like the one for the Cirklon:
- fixed keyword for fixed bugs
- changed keyword for changes in existing features/functions
- added keyword for added features/functions

What do you think?
F.

FlavioB wrote:

General_Midi wrote: thanks anyway for your efforts. nice to see the community keeping this project alive!

Yes, thanks from my side as well.
Just a tiny request: would it be possible to add a "releasenotes.txt" file for tracking the changes/fixes? Could be structured simply like the one for the Cirklon:
- fixed keyword for fixed bugs
- changed keyword for changes in existing features/functions
- added keyword for added features/functions

What do you think?
F.

Like this ?
https://github.com/BenZonneveld/Nava-20 ... o-20210621

Neuromancer wrote: Like this ?
https://github.com/BenZonneveld/Nava-20 ... o-20210621

Dang! You're SPOT ON, Ben! Thanks
F.