Posted
20 days
ago
buzztard
As can be seen on our roadmap
sample support is scheduled for 0.4. As this
is the major feature, we started working on it. I have to
say that building
buzztard on top of GStreamer was definitely the right
... [More]
thing
to do. We can now
load whatever GStreamer can handle. FSM did a nice
cairo-based waveform widget.
Right now I am working on the code that allows plugins to
access the wavetable.
It will hopefully be ready real soon.
Besides that I've started to restructure the gst-buzztard
package a bit further.
I also plan to merge the buzz wrapper plugin into it. The
aim is to reduce the
number of packages that one needs to build. [Less]
Posted
20 days
ago
by
ens...@users.sourceforge.net (Stefan Kost)
hi,
As can be seen on our roadmap [1] sample support is scheduled for 0.4. As this
is the major feature, we started working on it. I have to say that building
buzztard on top of GStreamer was definitely the right thing to do. We can
... [More]
now
load whatever GStreamer can handle. FSM did a nice cairo-based waveform widget.
Right now I am working on the code that allows plugins to access the wavetable.
It will hopefully be ready real soon.
Besides that I've started to restructure the gst-buzztard package a bit further.
I also plan to merge the buzz wrapper plugin into it. The aim is to reduce the
number of packages that one needs to build.
[1] http://www.buzztard.org/index.php/Roadmap
buzztard core developer team
--
http://www.buzztard.org (0 comments) [Less]
Posted
about 1 month
ago
by
ens...@users.sourceforge.net (Stefan Kost)
hej,
After the release I demoed it some friends and obviously found some issues. Now I
spend the rest of the month tracking then. Its mostly ref-counts issues. Why are
the so nasty? Well unlike memory leaks, they are anonymous.
... [More]
Memory is allocated
once and should be paired by one free. The id of the resource is the memory
address. Now every ref should be paired by an unref, but all the refs and unrefs
share the same id (address of the object). So how to figure which ref is not
having the unref? Refdbg [1] can trace object and gather backtraces for
ref-count operations. So one has to go through the list one by one, remove pairs
and study whats left. Its not easy, but it works.
Now why is this so important. If the refcount never reaches 0, the object is not
disposed and occupies memory (until the application exits). Under valgrind it
would appear under reachable memory usually. For most apps it has no immediately
visible effect. For gstreamer app it has. In buzztard I do dynamic stuff with
pipelines, like adding and removing elements. If you get the ref-counting wrong.
The element is unlinked but not disposed. If the pipeline is set to PLAYING one
gets data flow errors. But then its not a gstreamer only problem. E.g. icon theme
pixbufs in gtk. If the are not unrefed, gtk cannot unload the theme. Means if
you try a bunch of themes, none of the is unloaded if even just one panel
applet has a ref-count issue. The sad thing is that the gnome libraries have
quite some ref-count leaks. I've started to track and fix them as its hard to
see something within all this noise [2][3].
I've released buzztard-0.3.1 with the fixes. A few more developments to mention:
Waffel started a demo for the zip loader based on libgsf, Deloun made great svg
designs for the machine view canvas and the tabs and Herzi send me a patch to
add native scrolling in the pattern editor. Now back to new features, yah!
[1] http://refdbg.sf.net
[2] http://bugzilla.gnome.org/show_bug.cgi?id=525815
[3] http://bugzilla.gnome.org/show_bug.cgi?id=66513
buzztard core developer team
--
http://www.buzztard.org (0 comments) [Less]
Posted
about 1 month
ago
After the release I demoed it some friends and obviously
found some issues. Now I
spend the rest of the month tracking then. Its mostly
ref-counts issues. Why are
the so nasty? Well unlike memory leaks, they are anonymous.
Memory
... [More]
is allocated
once and should be paired by one free. The id of the
resource is the memory
address. Now every ref should be paired by an unref, but all
the refs and unrefs
share the same id (address of the object). So how to figure
which ref is not
having the unref? Refdbg
can trace object and gather backtraces for
ref-count operations. So one has to go through the list one
by one, remove pairs
and study whats left. Its not easy, but it works.
Now why is this so important. If the refcount never reaches
0, the object is not
disposed and occupies memory (until the application exits).
Under valgrind it
would appear under reachable memory usually. For most apps
it has no immediately
visible effect. For gstreamer app it has. In buzztard I do
dynamic stuff with
pipelines, like adding and removing elements. If you get the
ref-counting wrong.
The element is unlinked but not disposed. If the pipeline is
set to PLAYING one
gets data flow errors. But then its not a gstreamer only
problem. E.g. icon theme
pixbufs in gtk. If the are not unrefed, gtk cannot unload
the theme. Means if
you try a bunch of themes, none of the is unloaded if even
just one panel
applet has a ref-count issue. The sad thing is that the
gnome libraries have
quite some ref-count leaks. I've started to track and fix
them as its hard to
see something within all this noise
(#525815,
#66513).
I've released buzztard-0.3.1 with the fixes. A few more
developments to mention:
Waffel started a demo for the zip loader based on libgsf,
Deloun made great svg
designs for the machine view canvas and the tabs and Herzi
send me a patch to
add native scrolling in the pattern editor. Now back to new
features, yah! [Less]
Posted
2 months
ago
by
ens...@users.sourceforge.net (Stefan Kost)
The buzztard team has released version 0.3.0 "a tale of ice and darkness" of its
buzz-alike music composer. All modules got extensive improvements over the last release from almost a year ago. It is usable now and fun to play with. Give
... [More]
it a try and report bugs.
bml
Support for native machines. Better emulation. Can be build on 64bit x86.
bsl
Support for pre 1.2 buzz songs. Handle volume and panorama on wires. Several bug
fixes.
buzztard
Improvements in all areas. We now have native buzzmachine support and better
compatibility. The buzztard editor got an own pattern editor widget. The ui got
lots of keyboard commands. We have settings for default directories used. The ui
has dialogs for recording mix-downs and also single tracks.
gst-buzztard
Improvements on the preset interface. Support for sparse streams (GAP flag).
gstbml
Sparse stream handling. Better compatibility. Bug fixes.
project-page: http://www.buzztard.org
screenshots: http://www.buzztard.org/index.php/Screenshots
downloads : http://sourceforge.net/project/showfiles.php?group_id=55124
buzztard core developer team
--
http://www.buzztard.org (0 comments) [Less]
