Here are ideas about Ubuntu that have been marked as already implemented by the moderators.
0
votes
0
0
0
Multiple Audio Output
Written by jokerinux the 21 Mar 11 at 12:57.
Related project: Mythbuntu .
Category: Additional software.
Already implemented
It would be great if Ubuntu will permit to stream audio through differente audio output at the same time.
ex: stream audio to the hdmi and to the home theatre amplifier at the same time (through optical or coxial).
It will make ubuntu the default distro to all the htpc solution.
(for example xbmc is based on ubuntu and this implementation would give a great help for everyone who wants to listen to their music on different rooms)
This is possible today only with alsa (and removing pulse) but it requires a lot oh hacker skill (that everyone don't have).
Easy screen-sharing and audio-chat for instant messengers
Written by jaenz the 7 Jan 09 at 15:49.
Related project: Pidgin Internet Messenger .
Already implemented
Yesterday a friend of mine asked for help in Photoshop. And instead of configuring my router, care for my IP or dyndns-stuff, he just called me via Jabber on iChat in OS X. That was - awesome -! One of the big, big time-saving things, Apple serves.
To cut a long story short: we definitely need an audio-chat possibility (at least for XMPP) in Pidgin or Empathy (speaking of gnome). Bundled with screen-sharing it's just perfect to solve problems over the internet.
767
votes
950
63
183
Solution #1:
Use vino
Written by
jaenz the 7 Jan 09 at 15:49.
You might say "this exists and is called ekiga". You're right, but it's complicated to run two programs, register a SIP-account AND (!) convert all your friends to ekiga. Ekiga is simply too unkown, to use it outside of the open-source world.
I actually don't know how much time the implementation would take. But I believe, vino offers an option to grab the screen and gstreamer doubtlessly provides streaming of audio and video.
Finally such a "bling-bling"-functionality is a great way to win new Ubuntu-users.
You might say "this exists and is called ekiga". You're right, but it's complicated to run two programs, register a SIP-account AND (!) convert all your friends to ekiga. Ekiga is simply too unkown, to use it outside of the open-source world.
I actually don't know how much time the implementation would take. But I believe, vino offers an option to grab the screen and gstreamer doubtlessly provides streaming of audio and video.
Finally such a "bling-bling"-functionality is a great way to win new Ubuntu-users.
226
votes
304
65
78
Solution #2:
Use empathy by default in Ubuntu
Written by
torkiano the 14 Jan 09 at 06:15.
Empathy can do audio AND video calls to other XMPP/GTalk users.
It has support for SIP too, and for the most important IM protocols: msn, AIM ...
Also, VNC over XMPP tunnels has been done with empathy.
I think use empathy by default is the first step to implement this idea
Empathy can do audio AND video calls to other XMPP/GTalk users.
It has support for SIP too, and for the most important IM protocols: msn, AIM ...
Also, VNC over XMPP tunnels has been done with empathy.
I think use empathy by default is the first step to implement this idea
-460
votes
96
36
556
Solution #3:
Use Skype
Written by
znupi the 14 Jan 09 at 18:13.
Why not use Skype? It's cross-platform, provides audio and video chatting and a lot of people use it (including me, my brother and quite a few other people I know). Although Skype isn't open source, that doesn't mean you shouldn't use it. It is still free, and it is well known for its high quality sound and video transmission even on poor bandwidths.
Personally, I really think Skype is the best option for audio and video chatting.
Why not use Skype? It's cross-platform, provides audio and video chatting and a lot of people use it (including me, my brother and quite a few other people I know). Although Skype isn't open source, that doesn't mean you shouldn't use it. It is still free, and it is well known for its high quality sound and video transmission even on poor bandwidths.
Personally, I really think Skype is the best option for audio and video chatting.
438
votes
502
39
64
Solution #4:
Add audio/video and screen sharing support to Pidgin
Since most of us are already using it. I don't wanna have pidgin running for text, empathy for voice and another app for screen sharing.
Since most of us are already using it. I don't wanna have pidgin running for text, empathy for voice and another app for screen sharing.
80
votes
108
64
28
Solution #5:
remote-help-assistant
promote use of https://launchpad.net/remote-help-assistant
86
votes
108
37
22
Solution #6:
Gitso
Written by
Baggers the 19 Jan 09 at 11:57.
Single click reverse ssh tunnel using VNC.
Works on Mac, Linux, and Windows
The non geek being assisted doesn't need to worry about opening ports or what their IP is, that is down to person giving the assistance.
Open Source, small and simple.
Obviously it would be great if it could be initiated by the popular IM clients though.
http://code.google.com/p/gitso/
Single click reverse ssh tunnel using VNC.
Works on Mac, Linux, and Windows
The non geek being assisted doesn't need to worry about opening ports or what their IP is, that is down to person giving the assistance.
Open Source, small and simple.
Obviously it would be great if it could be initiated by the popular IM clients though.
http://code.google.com/p/gitso/
2
votes
4
4
2
Solution #9:
use gitso + mid-way server
Written by
fdetienn the 12 May 09 at 10:24.
I work in tech support for a major. We use webex and webex is a bandwidth hog => not always good.
The problem with VNC (and hence Vino) is the initiation from support engineer -> customer as the customer would have to allow incoming connections. Most of the time, you do not have time to punch the holes or the customer's infosec department will not allow you or the customer will be too lazy/ignorant and will hide behind his infosec department. Pick one.
The problem with reverse VNC (Gitso) alone is the same on the support engineer side. Most IT departments in large enterprises like to justify their presence by blocking traffic, preventing engineers to work, make engineer yell so IT can look protective :-D. In a word: incoming reverse vnc sessions won't work.
What we all really need is this:
[engineer]---[ent fw>]--mws--[
I work in tech support for a major. We use webex and webex is a bandwidth hog => not always good.
The problem with VNC (and hence Vino) is the initiation from support engineer -> customer as the customer would have to allow incoming connections. Most of the time, you do not have time to punch the holes or the customer's infosec department will not allow you or the customer will be too lazy/ignorant and will hide behind his infosec department. Pick one.
The problem with reverse VNC (Gitso) alone is the same on the support engineer side. Most IT departments in large enterprises like to justify their presence by blocking traffic, preventing engineers to work, make engineer yell so IT can look protective :-D. In a word: incoming reverse vnc sessions won't work.
What we all really need is this:
[engineer]---[ent fw>]--mws--[<cust fw]---[cust]
where mws is a midway server to which the forward VNC (initiated by the engineer) and the reverse VNC (initiated by the customer) connect. The MSW would take some credentials from both sides and rejoin the sessions, outside of the firewalls (typically in a DMZ on the support company premises).
This would make IT, the support engineer and the customer happy.
Sound/Audio Subsystem in Ubuntu
Written by mydoghasworms the 17 Oct 09 at 07:42.
Global category: System.
Already implemented
It is difficult to configure audio in Ubuntu.
Some applications only support e.g. pulse or ALSA etc., but not everything.
For some applications it is difficult to configure audio, e.g. Skype, and there are too many options to choose from to know which works.
0
votes
0
0
0
Solution #1:
Common Audio Interface Library / Layer
Build a library and audio subsystem that serves as a common interface to various different audio libraries, e.g. pulse, ALSA, etc.
You can then create applications that are audio library agnostic.
Applications can use this common audio interface instead of providing support for a specific audio library, so that they do not need to be aware of which audio library they are using. Then, you can still switch between ALSA and pulse etc. without affecting any applications, because they only use the new common interface library layer and don't care what audio system is actually used underneath.
It will make configuration of applications that use audio easier.
Build a library and audio subsystem that serves as a common interface to various different audio libraries, e.g. pulse, ALSA, etc.
You can then create applications that are audio library agnostic.
Applications can use this common audio interface instead of providing support for a specific audio library, so that they do not need to be aware of which audio library they are using. Then, you can still switch between ALSA and pulse etc. without affecting any applications, because they only use the new common interface library layer and don't care what audio system is actually used underneath.
It will make configuration of applications that use audio easier.