Few Changes

June 28, 2013 - 3 minute read -
gsoc pep8 python

The entire code is now PEP8 compliant maing it a lot easier to view. I found out a plugin for my text editor and all my future code will surely be the same.

Earlier i wrote about how I was not getting output correctly. The video was not "pretty" and clear. I had given a screenshot for comparison. This was due to a typo in the caps. Now, the video is perfect.

You can have a look here. This file opens fine with vlc for me.

I have also made some changes in the code so that the major variables are distinguished from the unimportant ones. This will be helpful especially when debugging code.

Also as mithro pointed out, the path of executables is now passed as parameter to the Server. This path can also be made an optional argument in case all the executables are in some default location after build and install.

Also now with everything installed correctly in place, I get warnings both in the gst-switch-srv and gst-switch-ui like:

(gst-switch-ui:11231): GStreamer-WARNING **: gstpad.c:3677:gst_pad_chain_data_unchecked:<overlay:sink> Got data flow before stream-start event
 
(gst-switch-ui:11231): GStreamer-WARNING **: gstpad.c:3908:gst_pad_push_data:<overlay:src> Got data flow before stream-start event
	

Audio is another problem. I ran gst-switch-srv followed by gst-switch-ui. I then added a audio test source on port 4000. This resulted in crashing the gst-switch-ui. The log looks something like this. It seems that an element monoscope is missing. However according to http://gstreamer.freedesktop.org/documentation/plugins.html monoscope is a part of gst-plugins-good which is already installed.


Some things to do:

There is a need for a error reporting mechanism. This will be utilizing python's Exception class. Presently, I have little knowledge of using this. I am learning how to make use of this Exception class. I have a file exception.py where I will be defining some common exceptions. These will be raised at appropriate places. Work needs to be done here.

Comments Section

Feel free to comment on the post but keep it clean and on topic.

blog comments powered by Disqus