← Back to team overview

zeya team mailing list archive

Re: Working on MPD support -- interest and history

 

Noted. Thanks!

Phil
On May 31, 2011 7:14 PM, "Jonathan M. Polom" <s0nic0nslaught@xxxxxxxxx>
wrote:
> This is a little unrelated but also, the list browser is extremely slow
when
> handling a large list of songs. In my case I have around 15000 tracks that
> all consume one line in the table. The list is virtually unusable on
> Chromium on Ubunutu so I have to search for everything. Listing out each
> track is definitely convenient programmatically but doesn't make for a
very
> enjoyable interface. Listing out artists in a column on the left-hand-side
> of the page and showing the artist's tracks or albums on a panel to the
> right would be a bit better. If my JavaScript skills were better I would
> change this for you but unfortunately I'm not very adept at it.
>
> On Tue, May 31, 2011 at 10:08 AM, Phil Sung <philbert@xxxxxxxxx> wrote:
>
>> On Sun, May 29, 2011 at 07:45, Jonathan M. Polom
>> <s0nic0nslaught@xxxxxxxxx> wrote:
>> > Yeah, or I could just extend the decoders file. Have you ever used
>> subsonic?
>> > It has a fairly flexible multistep transcoder. The user can specify
>> decode
>> > strings and encode strings for streamed audio. For example, to convert
>> FLAC
>> > to PCM to mp3 for streaming:
>> > Step 1: ffmpeg -i %s -v 0 -f wav -
>> > Step 2: lame -b %b --tt %t --ta %a --tl %l -S --resample 44.1 - -
>> > and these strings are user changeable and accessible in a control panel
>> > provided by the streaming app. I don't necessarily like this method,
I'd
>> > rather it be in a config file, but perhaps an extendable transcoding
>> method
>> > might be helpful for zeya. I'd probably use a python config file where
>> each
>> > config block would provide the input and output mime types for the
>> > transcoder and a list of the decoder/encoder application names.
>>
>> That does sound useful. I will take a look when I get a chance.
>>
>> Thanks,
>> Phil
>>
>
>
>
> --
> Jon Polom

References