Revision [31640]

Last edited on 2017-03-29 15:50:32 by zigbert

No Differences

Revision [31639]

Edited on 2017-03-29 15:49:57 by zigbert
Additions:
~The pMusic play-engine is a separated module. You can play audio with it either using the commandline or the more common solution; operate it through a frontend. This is a graphical layer that manage input to the engine (backend). pMusic offers several frontends for specific targets. The default frontend is meant to offer all the goodies in one gui, while other frontends is specialized to do specific tasks better than the bloated default gui.
~You can choose another frontend in the View-menu or by using commandline attributes. To make your preferred frontend the default for next run, this can be set in the preferences.
~Let's take a look a the most common frontends:
~This is the default frontend you meet when choosing pMusic from the menu or executing 'pmusic' in a terminal. At first sight it might look as a simple player - because it is meant to fit the task as a default audioplayer. But the gui expands quickly to become a much more complex player. The Manager frontend supports most options you'll find in the backend and configuration. Hopefully, the dynamic behavior will make it fit both grandma and pilots.
~
~{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" title="screenshot" alt="screenshot" height="210"}} {{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" title="screenshot" alt="screenshot" height="210"}}
~A simple frontend to manage internet radio.
~
~{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_radio.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_radio.png" title="screenshot" alt="screenshot" width="300"}}
~pMusic offers all functionality of any average CD player/ripper. This frontend collects these functions.
~
~{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_cd.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_cd.png" title="screenshot" alt="screenshot" width="300"}}
~pMusic 5.2 added a heavily improved support of Podcasts, and version 5.4 naturally shipped a specialized frontend to manage this.
~
~{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_podcast.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_podcast.png" title="screenshot" alt="screenshot" width="300"}}
~If your system are low on resources this frontend might be worth checking out. It works like (and looks like) the Manager frontend, but skips the heavy functions. The LowPowered frontend can be downloaded [[http://www.murga-linux.com/puppy/viewtopic.php?p=313250#313250 here]].
Deletions:
The pMusic play-engine is a separated module. You can play audio with it either using the commandline or the more common solution; operate it through a frontend. This is a graphical layer that manage input to the engine (backend). pMusic offers several frontends for specific targets. The default frontend is meant to offer all the goodies in one gui, while other frontends is specialized to do specific tasks better than the bloated default gui.
You can choose another frontend in the View-menu or by using commandline attributes. To make your preferred frontend the default for next run, this can be set in the preferences.
Let's take a look a the most common frontends:
This is the default frontend you meet when choosing pMusic from the menu or executing 'pmusic' in a terminal. At first sight it might look as a simple player - because it is meant to fit the task as a default audioplayer. But the gui expands quickly to become a much more complex player. The Manager frontend supports most options you'll find in the backend and configuration. Hopefully, the dynamic behavior will make it fit both grandma and pilots.
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" title="screenshot" alt="screenshot" height="210"}} {{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" title="screenshot" alt="screenshot" height="210"}}
A simple frontend to manage internet radio.
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_radio.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_radio.png" title="screenshot" alt="screenshot" width="300"}}
pMusic offers all functionality of any average CD player/ripper. This frontend collects these functions.
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_cd.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_cd.png" title="screenshot" alt="screenshot" width="300"}}
pMusic 5.2 added a heavily improved support of Podcasts, and version 5.4 naturally shipped a specialized frontend to manage this.
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_podcast.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_podcast.png" title="screenshot" alt="screenshot" width="300"}}
If your system are low on resources this frontend might be worth checking out. It works like (and looks like) the Manager frontend, but skips the heavy functions. The LowPowered frontend can be downloaded [[http://www.murga-linux.com/puppy/viewtopic.php?p=313250#313250 here]].


Revision [31638]

Edited on 2017-03-29 15:46:58 by zigbert
Additions:
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" title="screenshot" alt="screenshot" height="210"}} {{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" title="screenshot" alt="screenshot" height="210"}}
Deletions:
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" title="screenshot" alt="screenshot" height="200"}} {{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" title="screenshot" alt="screenshot" height="200"}}


Revision [31636]

Edited on 2017-03-29 15:41:07 by zigbert
Additions:
This is the default frontend you meet when choosing pMusic from the menu or executing 'pmusic' in a terminal. At first sight it might look as a simple player - because it is meant to fit the task as a default audioplayer. But the gui expands quickly to become a much more complex player. The Manager frontend supports most options you'll find in the backend and configuration. Hopefully, the dynamic behavior will make it fit both grandma and pilots.
Deletions:
This is the default frontend you meet when choosing pMusic from the menu or executing 'pmusic' in a terminal. At first sight it might look as a simple player - because it is meant to fit the task as a default audioplayer. But the gui expands quickly to become a much more complex player. The Manager frontend supports most options you'll find in the backend and configuration. The dynamic gui should fit both grandma and pilots.


Revision [31635]

Edited on 2017-03-29 15:37:15 by zigbert
Additions:
The pMusic play-engine is a separated module. You can play audio with it either using the commandline or the more common solution; operate it through a frontend. This is a graphical layer that manage input to the engine (backend). pMusic offers several frontends for specific targets. The default frontend is meant to offer all the goodies in one gui, while other frontends is specialized to do specific tasks better than the bloated default gui.
Deletions:
The pMusic play-engine is a separated module. You can play audio with it either using the commandline or the more common solution; operate through a frontend. This is a graphical layer that manage input to the engine (backend). pMusic offers several frontends for specific targets. The default frontend is meant to offer all the goodies in one gui, while other frontends is specialized to do specific tasks better than the bloated default gui.


Revision [31632]

Edited on 2017-03-29 15:33:01 by zigbert
Additions:
pMusic 5.2 added a heavily improved support of Podcasts, and version 5.4 naturally shipped a specialized frontend to manage this.
If your system are low on resources this frontend might be worth checking out. It works like (and looks like) the Manager frontend, but skips the heavy functions. The LowPowered frontend can be downloaded [[http://www.murga-linux.com/puppy/viewtopic.php?p=313250#313250 here]].
Deletions:
pMusic 5.2 added a heavily improved support of Podcasts, and 5.4 naturally shipped a specialized frontend to manage this.
If your system are low on resources this frontend might be worth checking out. It works like (and looks like) the Manager frontend, but skips the heavy functions. The LowPowered frontend can be downloaded [[http://blog.puppylinux.com/?viewDetailed=00026 here]].


Revision [31631]

Edited on 2017-03-29 15:24:38 by zigbert
Additions:
If your system are low on resources this frontend might be worth checking out. It works like (and looks like) the Manager frontend, but skips the heavy functions. The LowPowered frontend can be downloaded [[http://blog.puppylinux.com/?viewDetailed=00026 here]].
Deletions:
If your system are low on resources this frontend might be worth checking out. It works like (and looks like) the Manager frontend, but skips the heavy functions.


Revision [31628]

Edited on 2017-03-29 15:20:18 by zigbert
Additions:
The pMusic play-engine is a separated module. You can play audio with it either using the commandline or the more common solution; operate through a frontend. This is a graphical layer that manage input to the engine (backend). pMusic offers several frontends for specific targets. The default frontend is meant to offer all the goodies in one gui, while other frontends is specialized to do specific tasks better than the bloated default gui.
You can choose another frontend in the View-menu or by using commandline attributes. To make your preferred frontend the default for next run, this can be set in the preferences.
This is the default frontend you meet when choosing pMusic from the menu or executing 'pmusic' in a terminal. At first sight it might look as a simple player - because it is meant to fit the task as a default audioplayer. But the gui expands quickly to become a much more complex player. The Manager frontend supports most options you'll find in the backend and configuration. The dynamic gui should fit both grandma and pilots.
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" title="screenshot" alt="screenshot" height="200"}} {{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" title="screenshot" alt="screenshot" height="200"}}
Deletions:
The pMusic play-engine is a separated module. You can play audio with it either using the commandline or the more common solution; operate through a frontend. This is a graphical layer that manage input to the engine (backend). pMusic offers several frontends for specific targets. The default frontend is meant to offer all the goodies in one gui, while other frontends is specialized to do specific tasks better than the bloated default gui. You can choose another default frontend in the preferences.
This is the default frontend you meet when choosing pMusic from the menu or executing 'pmusic' in a terminal. At first sight it might look as a simple player - and that is why it looks like it does. But the gui expands quickly to become a much more complex player. The Manager frontend supports most options you'll find in the backend and configuration. The following images shows how the simple pMusic becomes a pilot cockpit...
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_simple.png" title="screenshot" alt="screenshot" width="300"}}
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" link="http://www.01micko.com/zigbert/pmusic/wiki/frontend_manager_advanced.png" title="screenshot" alt="screenshot" width="300"}}


Revision [31627]

Edited on 2017-03-29 15:11:01 by zigbert
Additions:
If your system are low on resources this frontend might be worth checking out. It works like (and looks like) the Manager frontend, but skips the heavy functions.
----
==Categories==
CategoryMultimedia
CategorySoftware
Deletions:
If your system are low on resources this frontend might be worth checking out. It works like the Manager frontend, but skips the heavy functions.


Revision [31626]

The oldest known version of this page was created on 2017-03-29 15:09:49 by zigbert
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki