Release notes for
"Flight JL 412"
The Flumotion team is happy to announce
a new development release of the
unstable 0.3 branch
of the Flumotion Streaming Server.
This branch will lead up to the stable 0.4 series. It is not yet meant
for production purposes. People who want to run a stable Flumotion
should stick to the 0.2 releases, or wait for the 0.4 releases.
Flumotion is a streaming server for GNU/Linux
systems featuring an easy to use configuration and administration GUI.
Implemented using GStreamer as the processing backend and using python and
Twisted for the high-level operations and GUI, it combines a wide feature set
with ease of use.
Features of this release
- Greatly improved and more flexible http burst-on-connect
- Allow setting a maximum duration for http connections
- Add simple icecast-stream relaying component
- Add component that takes GDP-payloaded data from a unix socket
- ICal based bouncer, to specify that clients may only connect during a specific time of day
- Restarting a manager while a flow is running now works reliably
- The disker component can now be remotely controlled to start/stop recording, and to automatically maintain symlinks to the latest recording
- Many component propertiess were renamed to make them more consistent
- The http-server component is now more reliable, and has GTK UI
- Components in the GTK UI now show information about their feeders
- Network clock synchronisation now works in more cases
- Workers and their jobs can now have their logs rotated
Bugs fixed in this release
: when modules get renamed, and you do a new make install, you end up with two components of the same name
: automatically restart workers on connection trouble
: possibility for external (software) sources.
: a manager restart with a running worker config causes worker to lose its old children that get overwritten with new info
: go over all component properties in registry and unify naming
: Changing to a different connection and failing leaves the UI in a grayed-out state
: stopping all and starting all makes all components sad
: theora encoder uses bitrate in kbit/sec, unlike most other encoders
: result of <debug></port>
: Restarting a manager doesn't work properly
: flumotion-admin's name lookup doesn't always work correctly
: core dump by flumotion-job
: flow with an audio-source fails
: looper component stays waking forever if file does not exist
: workers that have their port range specified as x-x (to use only one port) make things go wrong
: reconnect when upstream components restart causes a bad stream, gdp issue
: Burst-on-connect by time
: empty .connections file breaks the greeter, creating a gtk.Label instead of the custom Connections
: we seem to be leaking file descriptors on reconnect
: leak in feedserver
: after component that is clock master reconnects, it is told to be a clock master again
: merge mike-http-improvements-1
: worker does not create job for a sleeping component that has a moodPending, also moodPending should get reset when stopping a sad or lost component
: add ability to stop recording to a disker
: disker should allow schedulable recordings
: make sure log rotation works both in the manager and in workers
: feed components should track information of the eaters connected to them
: every reconnect causes a new feeder to be added in UI for "plumbing"
: The BaseAdminGtkNode don't have setitem and delitem vmethod
: The Plumbing GtkNode is alway instantiated and failed when the component is not a FeedComponent
: Admin prints tracebacks for non-feed-components
: tracebacks in admin when stopping a component
: disker admin UI bug
: When the audiotest component admin interface is loaded it set the frequency to 1 making it "silent"
: admin's open connection, quit, and about menu items appear as gtk-open, etc
: flumotion-admin screws the pooch if it can't connect to the manager
You can find source releases of flumotion in the
flumotion download directory.
More details can be found on the project's website,
Support and Issues
We use an issue tracker for
bug reports and feature requests.
browse the flumotion git repository from our tracker.
The development version can be obtained from our git repository:
git clone git://code.flumotion.com/flumotion.git
Contributors to this release
- Andy Wingo
- Michael Smith
- Sebastien Merle
- Thomas Vander Stichele
- Zaheer Merali