newsAdvanced Gtk+ Sequencer - News: Development insights of 0.9.0

 
 
Latest News
GSequencer 1.2.x goals posted by jkraehemann, Wed 18 Oct 2017 08:27:54 PM UTC - 0 replies
GSequencer gets triple-sync and additional dialogs posted by jkraehemann, Fri 13 Oct 2017 04:28:05 PM UTC - 0 replies
GSequencer first major release 1.0.0 posted by jkraehemann, Sun 01 Oct 2017 05:41:43 AM UTC - 0 replies
Reduced latency of JACK posted by jkraehemann, Fri 22 Sep 2017 12:37:27 PM UTC - 0 replies
Advanced Gtk+ Sequencer v1.0.0-beta posted by jkraehemann, Thu 31 Aug 2017 06:14:22 PM UTC - 0 replies
[Submit News]
[41 news in archive]

Development insights of 0.9.0

Item posted by Joël Krähemann <jkraehemann> on Sun 30 Jul 2017 03:21:47 AM UTC.

libags.so.0 has got extended unit-test coverage which is now approximately at 95%. Currently, I do work on unit-tests of libags-audio.so.0. The goal is to achieve same coverage.

This is a lot of work to do. Especially as figuring out some gaps in the API. The API to convert GSequencer's AgsNotation to Standard MIDI Files is tied to the UI. This shall change.

That's why I have introduced new prototypes:

  • ags_notation_to_raw_midi()
  • ags_notation_from_raw_midi()
  • ags_note_length_to_smf_delta_time()
  • ags_note_smf_delta_time_to_length()
  • ags_note_to_raw_midi_extended()
  • ags_note_to_seq_event_extended()
  • ags_note_from_raw_midi_extended()
  • ags_note_from_seq_event_extended()

Intending to complete the missing implementations of:

  • ags_note_to_seq_event()
  • ags_note_to_seq_event_extended()
  • ags_note_from_raw_midi()
  • ags_note_from_raw_midi_extended()
  • ags_note_from_seq_event()
  • ags_note_from_seq_event_extended()

Thought the following function is implemented but may change its result after refactoring it.

  • ags_note_to_raw_midi()

Refactoring GUI related code

For a later goal it seems evident to do a refactoring of the GUI related code. Especially with the dialogs and windows I am not happy. More properties would be neat, too.

The editor is another work needing part of the code base.

As extending unit-tests it is a great occasion to identify missing implementations and to clean things.

It is a fact that there exists only one unit test for the UI. I would say it is related to the development history.

Writing the docs

I have added some documentation in chapter 3 of the developer's book. However the user's book should be updated soon. In order to contain descriptions of the newly added move and crop dialogs. The chapter about the automation editor sucks, also.

Want you to provide feedback

After release 0.9.0 I am going to attract actively man to provide feedback. I am looking for musicians and serious amateurs.

by Joël

Comments:

No messages in Development insights of 0.9.0

 

Back to the top


Powered by Savane 3.1-cleanup1