~again4you/+git/gst-shark:hotfix/fix-bitrate-tracer-definition

Last commit made on 2019-04-08
Get this branch:
git clone -b hotfix/fix-bitrate-tracer-definition https://git.launchpad.net/~again4you/+git/gst-shark

Branch merges

Branch information

Name:
hotfix/fix-bitrate-tracer-definition
Repository:
lp:~again4you/+git/gst-shark

Recent commits

ab490c0... by eramirez392 <email address hidden>

Bump version number

012509f... by eramirez392 <email address hidden>

Fix definition for bitrate tracer type

c62b8ab... by Michael Gruner <email address hidden>

Merge branch 'release/v0.6.0'

3712acb... by Michael Gruner <email address hidden>

Bump version number

7fee934... by Michael Gruner <email address hidden>

Merge branch 'feature/check-for-gst-debug' into develop

e9e5fdf... by Michael Gruner <email address hidden>

Check if GStreamer was built with debug enabled

Tracers require GStreamer debugging enabled. It doesn't make
sense to continue if GStreamer was built without debugging
support.

d0d5307... by Michael Gruner <email address hidden>

Use existing logger util to handle debug disabling properly

3e55d2f... by Luis Leon <email address hidden>

Merge branch 'feature/fix-fltk-bug-multiple-plotting' into develop

Fix a bug caused by FLTK and QT plotting tools

Octave usually takes either FLTK or QT for plotting; however, these plotting tools cause a crash in Octave when plotting more than one trace in gstshark-plot. In order to fix this crash, gstshark is now using GNU Plot, even though it is older, but this bug does not happen.

98983a6... by Luis Leon <email address hidden>

Change plotting tool from default to gnuplot

This is part of a fix to deal with a bug when gstshark-plot have to plot multiple traces. Octave uses FLTK by default as plotting tool, but due to a bug in this library, it makes the gstShark-plot crashes when plot_tracer.m tries to plot multiple traces. This bug was also found in http://savannah.gnu.org/bugs/?45298, where this phenomenom happens when plotting with Octave as well. In order to fix this bug, the default plotting tool is substituted by GNU Plot.

7d182f8... by Luis Leon <email address hidden>

Merge branch 'feature/fix_min_timestamp_plots' into develop

Add minimum timestamp to limit x axis when plotting traces

This solves the issue of having a time offset when the traces do not start from zero. So, gstshark-plot now computes the minimum x value and start plotting from it to the timestamp maximum. The changes were done in plot_tracer.m, adding timestamp_min and modifying xlim(...).