Re: [MeeGo-dev] Technical Steering Group Meeting: New Day / Time
On Sun, Apr 3, 2011 at 6:21 AM, Thiago Macieira thi...@kde.org wrote: On Sunday, 3 de April de 2011 01:15:18 Jeremiah Foster wrote: By what measure? Most of the people on the mailing lists are from Europe and US. Are we talking corporate head counts or developer participation? Are you on the same mailing lists as I am? There are many Chinese names posting on these mailing lists... I mentioned specifically the MeeGo community list. I went through the archives for 2011 and saw very few Asian email addresses comparative to European and US based. Granted this is merely checking things like some...@somecompany.in or intel.com and not some...@gmail.com. There is no way to know just by name which region someone works in. This is why it is so important that those who want to attend the meetings speak up and address the community list. I saw not one single request for meeting times on that list. Shouldn't the TSG meeting times be supported by requests from those who want to attend? Where are those requests? Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Technical Steering Group Meeting: New Day / Time
On Sun, Apr 3, 2011 at 7:04 AM, Carsten Munk cars...@maemo.org wrote: On Sun Apr 3 2011 01:15:18 AM CEST, Jeremiah Foster jeremiah.fos...@pelagicore.com wrote: On Sat, Apr 2, 2011 at 5:23 PM, Foster, Dawn M dawn.m.fos...@intel.com wrote: On Apr 2, 2011, at 6:53 AM, Jeremiah Foster wrote On Fri, Apr 1, 2011 at 8:31 PM, Foster, Dawn M dawn.m.fos...@intel.com wrote: I wanted to let everyone know that we have a new time for our Technical Steering Group meetings. While the 20:00 UTC meetings were convenient for the Americas and Europe, it was very difficult for people in Asia to participate. [...] If you have a better time that works for more people than the current time, I encourage you to propose it. I propose we leave the time as it is until there is more open discussion about when these meetings should occur. I don't see a consensus forming around the time yet. Do those who plan to attend the TSG have opinions on when the meeting should be held? While it is my belief that the time schedules of the TSG meeting is up to the members of the TSG to decide The TSG unilaterally decides policy and process in MeeGo. This is a problem because those who sit on the TSG have their company's interests at heart (naturally.) This means that Nokia and Intel decide MeeGo policy along with a member of the Linux Foundation. Shouldn't that be solely the Linux Foundation instead which presumably will be less biased? Currently its just two companies business interests that shape MeeGo policy, one of those companies is scaling back its contribution significantly. Rotating the meeting from noon pacific, 10pm finland, 3am Asia to 11pm pacific, 9am finland, 2pm(?) asia seems like a fair time. If there is a topic you're especially passionate about, it's possible to post comments on mailing list/have someone be your proxy or show up - 3am in Asia made this impossible for many to show up. But there has been no presence of LG and China Mobile at the TSG meetings. They didn't show up at the nomination which is reasonable since it was at a ridiculous time for them. But there is no email from Yonghui Wang from China Mobile, for example, on any of the lists I follow or on the Handset list. Yet he's been appointed to the Handset WG. Your suggestion of sending mail to the list or sending a proxy to the meetings is a good one, why hasn't this been done? In fact, why don't we move the decision making process for the TSG to a mailing list where people from any time zone can participate and decision making is done in the open? Given we have two new players (at least) such as China Mobile and LGE in MeeGo, it is fair to schedule the meetings to allow them to participate properly. For those thinking they won't show up anyway, at least LGE guys (plus handset WG member) already hang out in the MeeGo IRC channels, so not a big leap to join another IRC channel. If by players you mean companies that will make decisions about MeeGo then I don't think it is in fact fair. I thought that participation in the workgroups was going to be contribution based; where is the contribution from these two players? What code has been contributed? What architectural decisions made? If positions in the workgroups are not contribution based, what are they based on? Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Added wayland packages to MeeGo
On Fri, Apr 1, 2011 at 3:38 AM, Liu, Xinyun xinyun@intel.com wrote: Hello, April fools' day. You can try wayland with MeeGo in console mode now. After login in via console, just type wayland-test, then you can try other wayland apps from wayland-terminal. (/usr/bin/wayland-*) Q: Any preparation? A: Yes. Change to console mode. sed -i s#id:5:initdefault#id:3:initdefault# /etc/inittab Q: How to install/run it? A: a. Install MeeGo[1] with a Intel gfx card. (GenX) b. Add the package repo[2] to /etc/zypp/repos.d/wayland.repo c. Install related packages: zypper in libxkbcommon mesa-libwayland-egl wayland wayland-demos cairo libdrm libX11 mesa-dri-i915-driver mesa-libEGL mesa-libGLESv2 pixman d. Run wayland-test Q: Can it use X as the backend? A: No. It can do so but there is some bug in my rpm packages. Q: Any more reference? A: http://wayland.freedesktop.org/ Q: Anything else? A: Yes. More packages need to be added, bugs to be fixed, X related packages to be cleaned up. The most important is to add devel packages to it. But no plan. This is fantastic, thanks for setting it up. What I'm working on now is to try to move over the tablet UX, bit by bit. I've just started, but the plan is use Qt lighthouse and the QML scenegraph. I'm using the qtquick2-integration branch of the Qt lighthouse repo: git://gitorious.org/+qt-developers/qt/lighthouse.git and the plan is to make meego-ux-daemon the compositor and display server, so the idea is that we can drop X and mcompositor and just fold the compositing functionality into meego-ux-daemon. meego-ux-daemon will use something like the EGL fullscreen lighthouse plugin and evdev input to run directly on KMS. For the clients, we'll have to port meego-qml-launcher to Qt lighthouse and QML scenegraph as well, but the launcher will use the Wayland lighthouse plugin to run as a Wayland client. We'll have to define a MeeGo Tablet UX specific Wayland extension, to replace the ad-hoc use of EWMH in mcompositor and clients. Later on we can look into how to handle classic (non-QML) Qt applications and eventually legacy X clients. Anyway, that's the hand-wavey plan. I expect I'll fork the meego tablet ux repos in question on gitorious once I have something that kinda works. But from a packaging point of view the next step is to figure out how we can package the qtquick2-integration branch of Qt and add it to the Wayland repo. Kristian ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Added wayland packages to MeeGo
On Sat, Apr 2, 2011 at 1:39 AM, Carsten Munk cars...@maemo.org wrote: 2011/4/1 Liu, Xinyun xinyun@intel.com: Hello, April fools' day. You can try wayland with MeeGo in console mode now. After login in via console, just type wayland-test, then you can try other wayland apps from wayland-terminal. (/usr/bin/wayland-*) Q: Any preparation? A: Yes. Change to console mode. sed -i s#id:5:initdefault#id:3:initdefault# /etc/inittab Q: How to install/run it? A: a. Install MeeGo[1] with a Intel gfx card. (GenX) b. Add the package repo[2] to /etc/zypp/repos.d/wayland.repo c. Install related packages: zypper in libxkbcommon mesa-libwayland-egl wayland wayland-demos cairo libdrm libX11 mesa-dri-i915-driver mesa-libEGL mesa-libGLESv2 pixman d. Run wayland-test Q: Can it use X as the backend? A: No. It can do so but there is some bug in my rpm packages. Q: Any more reference? A: http://wayland.freedesktop.org/ Q: Anything else? A: Yes. More packages need to be added, bugs to be fixed, X related packages to be cleaned up. The most important is to add devel packages to it. But no plan. [1] MeeGo Image http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-netbook-ia32/meego-netbook-ia32-1.1.99.0.20110330.3.img In fact, I used a smaller image to test wayland, I added zypper, vim and created the image with this .ks file http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-core-ia32-base-nodoc/meego-core-ia32-base-nodoc-1.1.99.0.20110330.3.ks [2] wayland rpm repo for MeeGo http://download.meego.com/live/home:/xyl:/wayland/Trunk/home:xyl:wayland.repo Hi, Thank you for kicking off a good initiative. I think there's many people and companies interested in this area - maybe we should propose a devel:wayland project in the MeeGo OBS? It is after all one of the important directions for MeeGo. I guess one of the steps would also be to have Qt Lighthouse packages there, enabled for Wayland? I'd be interested in ARM builds of the packages as well, to experiment early on on those platforms (probably similar challenges as with PVR in Intel devices). Hardware enabling is something that has recently come together pretty well. I just post a bit of documentation about the couple of things that Wayland needs here (scroll to the end): http://wayland.freedesktop.org/architecture.html It's still a bit open-ended with respect to how to bring up the compositor on the hardware, but that's technically not Wayland specific, it's something that each EGL stack solves in different, vendor specific ways. Kristian ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] migration (back) to EDS - contacts and calendar
On Fr, 2011-04-01 at 11:29 +0200, Patrick Ohly wrote:
I beg to disagree here. The MeeGo version of KCalCore is compiled
differently than the upstream version:
#if !defined(KCALCORE_FOR_MEEGO)
endDate = kdt.date().addDays( -1 );
#else
endDate = kdt.date();
#endif
Go to the kde git, and you will see those there. So the code, as I said, is
from upstream.
My point is that the MeeGo version of KCalCore is functionally different
from the one in KDE. That the code is upstream is irrelevant as long as
ifdefs are used for more fundamental changes than merely getting the
code to compile on a different platform.
My suspicion all along was that these defines around end date change the
semantic of KCalCore. To verify that, I modified the test program from
BMC #6050 such that it imports an iCalendar 2.0 all-day event and prints
its start/end date after importing into KCalCore.
Code attached, compile/run with:
rm -rf ~/.calendar \
g++ -g test-allday-semantic.cpp `pkg-config --cflags --libs libmkcal `
\
./a.out
In MeeGo with KCalCore 4.1.18 I get
start QDate(Wed Apr 5 2006) end QDate(Thu Apr 6 2006)
After recompiling that version without KCALCORE_FOR_MEEGO I get:
start QDate(Wed Apr 5 2006) end QDate(Wed Apr 5 2006)
In other words, the patch changes the semantic of dtEnd() for
applications. Upstream KDE uses dtEnd() is inclusive, the MeeGo
version uses dtEnd() is exclusive.
The latter is closer to iCalendar 2.0, but is that a good enough
justification to break compatibility with apps ported from KDE? I don't
think so.
Another possible justification would be that the original semantic
cannot express an empty all-day event (start == end). Again I would
consider not modifying the API as more important than this cleanup.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
/*
* Calendar - For testing adding alarm to an event
*
* Copyright (c) 2010, Intel Corporation.
* Author: Sirisha Muppavarapu (sirisha.muppavar...@intel.com)
*
* This program is licensed under the terms and conditions of the
* Apache License, version 2.0. The full text of the Apache License is at
* http://www.apache.org/licenses/LICENSE-2.0
*
*/
#include QtCore/QCoreApplication
#include extendedcalendar.h
#include event.h
#include notebook.h
#include sqlitestorage.h
#include kdatetime.h
#include duration.h
#include icalformat.h
#include QDebug
const char *item =
BEGIN:VCALENDAR\n
PRODID:-//Ximian//NONSGML Evolution Calendar//EN\n
VERSION:2.0\n
BEGIN:VEVENT\n
SUMMARY:all day\n
DTSTART;VALUE=DATE:20060405\n
DTEND;VALUE=DATE:20060406\n
UID:foobar\n
END:VEVENT\n
END:VCALENDAR\n;
int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);
mKCal::ExtendedCalendar::Ptr calendar(new mKCal::ExtendedCalendar(KDateTime::Spec::LocalZone()));
mKCal::ExtendedStorage::Ptr storage(mKCal::ExtendedCalendar::defaultStorage(calendar));
storage-open();
storage-load();
// import event
KCalCore::ICalFormat parser;
if (!parser.fromString(calendar, QString::fromUtf8(item))) {
qFatal(error parsing iCalendar 2.0 item);
}
KCalCore::ICalFormat formatter;
qDebug() formatter.toString(KCalCore::Calendar::Ptr(calendar));
KCalCore::Incidence::List incidences = calendar-incidences();
qDebug() incidences;
KCalCore::Event::Ptr event = incidences[0].staticCastKCalCore::Event();
qDebug() start event-dtStart().date() end event-dtEnd().date();
// MeeGo with FOR_MEEGO define:
// start QDate(Wed Apr 5 2006) end QDate(Thu Apr 6 2006)
// without define:
// start QDate(Wed Apr 5 2006) end QDate(Wed Apr 5 2006)
return 0;
}
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
After doing $ zypper ar http://download.meego.com/live/devel:/meego-ux/Trunk/devel:meego-ux.repo $ zypper zypper clean --all ; zypper --gpg-auto-import-keys refresh $ zypper in meego-app-camera meego-app-video meego-app-photos meego-app-notes meego-app-im meego-app-email meego-app-conacts meego-app-calendar meego-app-calculator meego-app-browser meego-app-clocks meego-ux-panels meego-ux-panels-photos meego-ux-panels-friends meego-ux-panels-music meego-ux-panels-mytablet meego-ux-panels-video meego-ux-panels-web meego-ux-panels-meta-tablet meego-ux-appgrid meego-ux-content meego-ux-content-socialweb which also installs dependencies: meego-handset-sound-theme meegolabs-ux-components meego-qml-launcher meego-ux-media meego-ux-media-models meego-ux-theme mkcal mlite qtgst-qmlsink telepathy-farstream I attempt to launch these apps with $ meego-qml-launcher --app appname which looks for /usr/share/appname/main.qml e.g. meego-qml-launcher --opengl --fullscreen --app meego-app-calculator meego-qml-launcher --opengl --fullscreen --app meego-app-calendar meego-qml-launcher --opengl --fullscreen --app meego-app-camera meego-qml-launcher --opengl --fullscreen --app meego-app-clocks meego-qml-launcher --opengl --fullscreen --app meego-app-contacts meego-qml-launcher --opengl --fullscreen --app meego-app-email meego-qml-launcher --fullscreen --opengl --app meego-app-im meego-qml-launcher --opengl --fullscreen --app meego-app-music meego-qml-launcher --opengl --fullscreen --app meego-app-notes meego-qml-launcher --opengl --fullscreen --app meego-app-photos meego-qml-launcher --opengl --fullscreen --app meego-app-tasks meego-qml-launcher --opengl --fullscreen --app meego-app-video meego-qml-launcher --opengl --fullscreen --app meego-ux-appgrid meego-qml-launcher --opengl --fullscreen --app meego-ux-app-photos meego-qml-launcher --opengl --fullscreen --app meego-ux-panels meego-qml-launcher --opengl --fullscreen --app meego-ux-settings Although many of the simple tablet-ux apps work on the Lenovo s10-3t running 1.2 netbook alpha, the one I really want to re-use (for http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego ) is meego-app-camera. Unfortunately, when I run it, I get the following: -- is this a bug or am I dong something wrong ? ... $ meego-qml-launcher --opengl --fullscreen --app meego-app-camera Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Adding ATTACHED touch device: Cando Corporation Cando 10.1 Multi Touch Panel with Controller ( 11 ) Skipping non-Touch device: SynPS/2 Synaptics TouchPad ( 14 ) loaded the Generic plugin Loaded the MeeGo sensor plugin Request for interface not granted... Request for interface not granted... Warning: Object::connect: No such signal QXIMInputContext::inputMethodAreaChanged(QRect) Warning: Object::connect: No such signal LauncherApp::localeSettingsChanged() Warning: Object::connect: (sender name: 'meego-qml-launcher') Warning: Object::connect: No such signal LauncherApp::windowListUpdated(QListWindowInfo) Warning: Object::connect: (sender name: 'meego-qml-launcher') Debug: Instantiating VolumeControlPrivate Debug: Settings* Debug: Flash Mode: 0 Debug: Capture Mode: 0 Debug: /dev/video0 Lenovo EasyCamera Debug: /dev/video0 Lenovo EasyCamera Debug: Setting camera to /dev/video0 Debug: Camera caps: 64 Debug: Supported maximum optical zoom 1 Debug: Supported maximum digital zoom 10 Debug: Metadata is not available Debug: Audio input: alsa:null - Discard all samples (playback) or generate zero samples (capture) Debug: Audio input: alsa:pulse - PulseAudio Sound Server Debug: Audio input: alsa:default - Default Debug: Audio input: alsa:front:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog Front speakers Debug: Audio input: alsa:surround40:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 4.0 Surround output to Front and Rear speakers Debug: Audio input: alsa:surround41:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 4.1 Surround output to Front, Rear and Subwoofer speakers Debug: Audio input: alsa:surround50:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 5.0 Surround output to Front, Center and Rear speakers Debug: Audio input: alsa:surround51:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers Debug: Audio input: alsa:surround71:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers Debug: Audio input: pulseaudio: - PulseAudio device. Debug: Default source: alsa:null Debug: Using default resolution Debug: Using default FPS Debug: Codec: video/theora Debug: Codec: video/mpeg2 Debug: Codec: video/mpeg1 Debug: Codec: video/mjpeg Debug: Codec: video/VP8 Debug: Codec: video/h261 Debug: Container: mp4 Debug: Container: ogg Debug: Container: wav Debug: Container: amr Debug: Container:
Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
On 4/3/2011 4:27 PM, Niels Mayer wrote: h wonder why you don't run the tablet/etc UX entirely ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
On 04/03/2011 04:27 PM, Niels Mayer wrote: After doing $ zypper ar http://download.meego.com/live/devel:/meego-ux/Trunk/devel:meego-ux.repo $ zypper zypper clean --all ; zypper --gpg-auto-import-keys refresh $ zypper in meego-app-camera meego-app-video meego-app-photos meego-app-notes meego-app-im meego-app-email meego-app-conacts meego-app-calendar meego-app-calculator meego-app-browser meego-app-clocks meego-ux-panels meego-ux-panels-photos meego-ux-panels-friends meego-ux-panels-music meego-ux-panels-mytablet meego-ux-panels-video meego-ux-panels-web meego-ux-panels-meta-tablet meego-ux-appgrid meego-ux-content meego-ux-content-socialweb which also installs dependencies: meego-handset-sound-theme meegolabs-ux-components meego-qml-launcher meego-ux-media meego-ux-media-models meego-ux-theme mkcal mlite qtgst-qmlsink telepathy-farstream I attempt to launch these apps with $ meego-qml-launcher --appappname which looks for /usr/share/appname/main.qml e.g. meego-qml-launcher --opengl --fullscreen --app meego-app-calculator meego-qml-launcher --opengl --fullscreen --app meego-app-calendar meego-qml-launcher --opengl --fullscreen --app meego-app-camera meego-qml-launcher --opengl --fullscreen --app meego-app-clocks meego-qml-launcher --opengl --fullscreen --app meego-app-contacts meego-qml-launcher --opengl --fullscreen --app meego-app-email meego-qml-launcher --fullscreen --opengl --app meego-app-im meego-qml-launcher --opengl --fullscreen --app meego-app-music meego-qml-launcher --opengl --fullscreen --app meego-app-notes meego-qml-launcher --opengl --fullscreen --app meego-app-photos meego-qml-launcher --opengl --fullscreen --app meego-app-tasks meego-qml-launcher --opengl --fullscreen --app meego-app-video meego-qml-launcher --opengl --fullscreen --app meego-ux-appgrid meego-qml-launcher --opengl --fullscreen --app meego-ux-app-photos meego-qml-launcher --opengl --fullscreen --app meego-ux-panels meego-qml-launcher --opengl --fullscreen --app meego-ux-settings Although many of the simple tablet-ux apps work on the Lenovo s10-3t running 1.2 netbook alpha, the one I really want to re-use (for http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego ) is meego-app-camera. Unfortunately, when I run it, I get the following: -- is this a bug or am I dong something wrong ? ... $ meego-qml-launcher --opengl --fullscreen --app meego-app-camera Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Adding ATTACHED touch device: Cando Corporation Cando 10.1 Multi Touch Panel with Controller ( 11 ) Skipping non-Touch device: SynPS/2 Synaptics TouchPad ( 14 ) loaded the Generic plugin Loaded the MeeGo sensor plugin Request for interface not granted... Request for interface not granted... Warning: Object::connect: No such signal QXIMInputContext::inputMethodAreaChanged(QRect) Warning: Object::connect: No such signal LauncherApp::localeSettingsChanged() Warning: Object::connect: (sender name: 'meego-qml-launcher') Warning: Object::connect: No such signal LauncherApp::windowListUpdated(QListWindowInfo) Warning: Object::connect: (sender name: 'meego-qml-launcher') Debug: Instantiating VolumeControlPrivate Debug: Settings* Debug: Flash Mode: 0 Debug: Capture Mode: 0 Debug: /dev/video0 Lenovo EasyCamera Debug: /dev/video0 Lenovo EasyCamera Debug: Setting camera to /dev/video0 Debug: Camera caps: 64 Debug: Supported maximum optical zoom 1 Debug: Supported maximum digital zoom 10 Debug: Metadata is not available Debug: Audio input: alsa:null - Discard all samples (playback) or generate zero samples (capture) Debug: Audio input: alsa:pulse - PulseAudio Sound Server Debug: Audio input: alsa:default - Default Debug: Audio input: alsa:front:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog Front speakers Debug: Audio input: alsa:surround40:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 4.0 Surround output to Front and Rear speakers Debug: Audio input: alsa:surround41:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 4.1 Surround output to Front, Rear and Subwoofer speakers Debug: Audio input: alsa:surround50:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 5.0 Surround output to Front, Center and Rear speakers Debug: Audio input: alsa:surround51:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers Debug: Audio input: alsa:surround71:CARD=Intel,DEV=0 - HDA Intel, CONEXANT Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers Debug: Audio input: pulseaudio: - PulseAudio device. Debug: Default source: alsa:null Debug: Using default resolution Debug: Using default FPS Debug: Codec: video/theora Debug: Codec: video/mpeg2 Debug: Codec: video/mpeg1 Debug: Codec: video/mjpeg Debug: Codec: video/VP8 Debug: Codec: video/h261 Debug: Container: mp4 Debug: Container: ogg Debug:
