From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <33fa8d1671b63f63c5a473d29d7cfb81@mail.gmx.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] Ideas??? From: "Sascha Retzki" Date: Mon, 18 Sep 2006 15:15:39 +0200 In-Reply-To: <7d3530220609171310x1d709d5do7a25a599adfb395a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: b9a52218-ead1-11e9-9d60-3106f5b1d025 >> * port mplayer?? It's ugly code, but it works, and it works pretty fast ;-D >> >> > > I second the mplayer vote, because it's possibly the best (from a > user's perspective, I don't know what the code is like) media player > I've ever used. However, before mplayer is useful, I think we kinda > need some more sound drivers. > > John Mmmhh, man 7 juke # juke(7) man 7 playlistfs # playlistfs(7) I have not yet looked deeply enough into those, but as far as I recall, you create a decoder for each file-type as an external program. I have no idea how things like fast-forward/backward work, for instance (pause, etc). And I have no idea how I easily create playlists. It's shell magic for mplayer, and GUIs using mplayer may also provide ways - as I read the manpages, I am supposed to write maps myself. :-( Supposed those things are easily done, 'porting mplayer' becomes 'port the codecs, create a decoder for each of those'. At least for the audio-part. But imho it works for video, too. Speaking of those manpages, what is audio(7)? I don't have that manpage.