Sponsored Content
Full Discussion: linux xmms sound problems
Top Forums UNIX for Dummies Questions & Answers linux xmms sound problems Post 39881 by cbkihong on Wednesday 3rd of September 2003 07:11:16 AM
Old 09-03-2003
Do you experience the same problem using other apps like noatun or kaboodle? Which xmms output plugin are you using? You can find it out by going to preferences and you will find something called like "output plugin".

I have XMMS with an onboard sound card on SuSE 7.3 with no problems.
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

problems with sound card on FreeBSD 4.5

Hi,friends!!! I have a problem with my integrated sound card AC97 on i815 and my version of FreeBSD is 4.5.I know that there is a driver for it called ich.c.gz,but the site containing it is unavaliable now.And is there another driver or some other ideas ? z-z-z-z-z :: email removed :: (1 Reply)
Discussion started by: kruch
1 Replies

2. UNIX for Dummies Questions & Answers

Xmms Crash in Red Hat 8

I have a 500mhz K6 that I'm running Red Hat 8 on. I use xmms for all my music media playing purposes, but There seems to be an issue between xmms and volume control. Every now and then when I adjust the volume through aumix xmms freezes up and sends the sound into a runaway loop that I cant seem... (2 Replies)
Discussion started by: djtrippin
2 Replies

3. UNIX for Advanced & Expert Users

Sound Problems

Hi All I am having difficulty configuring sound on my system an wonder if anyone can help me. xmms refuses to play telling me that oss_open(): Failed to open audio device (/dev/sound/dsp): No such file or directory what I have done to try and fix this is 1. create /dev/sound/dsp ... (7 Replies)
Discussion started by: silvaman
7 Replies

4. Solaris

Sound Problems

My sound is messed up. All I get is white noise when I try to watch Youtube or something. I'm running Solaris 10 SPARC on a Sun Ultra 5, which has a built-in speaker. How do I fix it? (4 Replies)
Discussion started by: Bradj47
4 Replies

5. Red Hat

Wireless and Sound Problems with HP Pavilion dv7 and Fedora Core 10

I have just bought a new HP Pavilion dv7 notebook (17", AMD Turion) and installed Fedora Core 10. I would like to add that i installed a completely eyecandy-less base system, only then installed a naked x-org Xserver and mwm (Motif Window Manager) on top of it. There is neither KDE nor GNOME nor... (2 Replies)
Discussion started by: bakunin
2 Replies

6. Windows & DOS: Issues & Discussions

Sound Effects Dolby,SRS in Linux

Hello all. Can anyone tell me if there is any alternative to Window$ Media Player for LINUX(Linux Mint). What am searching for is a player with sound processing capabilities.(Bass,Equaliser,SRS,Dolby,etc..) Thanks. (1 Reply)
Discussion started by: coolatt
1 Replies

7. Linux

Can not play sound in Linux RHEL5.

Hi All, Recently I installed Linux RHEL5 on my machine. It seems that I can not play sound on RHEL5. I have real player installed along with RHEL5 but, when I try to play any song, the error message comes up saying "Can not open the audio device.Another application may be using it." Does any... (2 Replies)
Discussion started by: gydave
2 Replies

8. Red Hat

No sound in my Linux

I am not able to run any video file. Getting message something like : no audio facility. Is this may be problem of driver. If so please send me link for the same. I am working on Red Hat Fedora (Linux) (16 Replies)
Discussion started by: ravisingh
16 Replies
Jifty::Plugin(3pm)					User Contributed Perl Documentation					Jifty::Plugin(3pm)

NAME
Jifty::Plugin - Describes a plugin to the Jifty framework DESCRIPTION
Plugins are like mini-apps. They come in packages with share directories which provide static and template files; they provide actions; they have dispatcher rules. To create the skeleton of a new plugin, you can use the command: jifty plugin --name SomePlugin To use a plugin in your Jifty application, find the "Plugins:" line in the "config.yml" file: Plugins: - SpiffyThing: {} - SomePlugin: arguments: to the: constructor The dispatcher for a plugin should live in "Jifty::Plugin::name::Dispatcher"; it is written like any other Jifty::Dispatcher. Plugin dispatcher rules are checked before the application's rules; however, see "Plugins and rule ordering" in Jifty::Dispatcher for how to manually specify exceptions to this. Actions and models under a plugin's namespace are automatically discovered and made available to applications. new Sets up a new instance of this plugin. This is called by Jifty after reading the configuration file, and is supplied whatever plugin- specific settings were in the config file. Note that because plugins affect Mason's component roots, adding plugins during runtime is not supported. init [ARGS] Called by "new", this does any custom configuration that the plugin might need. It is passed the same parameters as "new", gleaned from the configuration file. new_request Called right before every request. By default, does nothing. template_root Returns the root of the "HTML::Mason" template directory for this plugin po_root Returns the plugin's message catalog directory. Returns undef if it doesn't exist. template_class Returns the Template::Declare view package for this plugin static_root Returns the root of the static directory for this plugin dispatcher Returns the classname of the dispatcher class for this plugin prereq_plugins Returns an array of plugin module names that this plugin depends on. version Returns the database version of the plugin. Needs to be bumped any time the database schema needs to be updated. Plugins that do not directly define any models don't need to worry about this. bootstrapper Returns the name of the class that can be used to bootstrap the database models. This normally returns the plugin's class name with "::Bootstrap" added to the end. Plugin bootstrappers can be built in exactly the same way as application bootstraps. See Jifty::Bootstrap. upgrade_class Returns the name of the class that can be used to upgrade the database models and schema (such as adding new data, fixing default values, and renaming columns). This normally returns the plugin's class name with "::Upgrade" added to the end. Plugin upgrade classes can be built in exactly the same was as application upgrade classes. See Jifty::Upgrade. table_prefix Returns a prefix that will be placed in the front of all table names for plugin models. Be default, the plugin name is converted to an identifier based upon the class name. wrap Takes a PSGI-$app closure and returns the wrapped one if your plugin wants to do something to the request handling process. See also Plack::Middleware. psgi_app_static Returns a PSGI-$app that serves the static content of the plugin if any. The default is a <Plack::App::File> app with root set to plugin's "static_root" perl v5.14.2 2010-12-08 Jifty::Plugin(3pm)
All times are GMT -4. The time now is 06:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy