newsAdvanced Gtk+ Sequencer - News: GSequencer v2.0.0 - forecast

 
 
Latest News
handling LV2 iriref posted by jkraehemann, Wed 13 Feb 2019 10:20:49 AM UTC - 0 replies
fixed ref-count posted by jkraehemann, Sat 09 Feb 2019 02:46:41 PM UTC - 0 replies
Problems with open GSequencer files posted by jkraehemann, Wed 06 Feb 2019 09:35:50 PM UTC - 0 replies
Constant CPU consumption by bisection posted by jkraehemann, Tue 05 Feb 2019 05:12:51 PM UTC - 0 replies

GSequencer v2.0.0 - forecast

Item posted by Joël Krähemann <jkraehemann> on Tue 06 Feb 2018 03:04:57 PM UTC.

The Advanced Gtk+ Sequencer branch 2.0.x was just created, few days ago. First a big refactoring will take place. I have tried to figure out common enumerations and specify them in ags/audio/ags_sound_enums.h. It looks currently like:

Resources only per ability

To distinguish what an AgsAudio or alike can do and what no, the AgsSoundAbilityFlags was created.

Behaviour of processing

Processing audio data has got many flavors and are updated, too.

The 5 scopes

The highlight are definitively the specified scopes. 2 of them are completely new: AGS_SCOPE_WAVE and AGS_SCOPE_MIDI. A scope is usually processed by its own thread. AgsWave has yet been added to the source code and is yet ready for use. But the addition of AgsMidi is still missing. It shall be able to record raw MIDI data and store it as SMF.

Staging specification

Better semantics of what is processed seems to be necessary as extending the capabilities of GSequencer.

State handling

An other common enumeration is done to tell what state the scope currently is in.

No messages in GSequencer v2.0.0 - forecast

 

Back to the top


Powered by Savane 3.4