Thanks for warm welcome. Actually I asked the same question on the IRC, and 
Rasi provided me with a link to crossfade code. Isn’t it quite a similar thing 
as crossfade implementation? Or I just underestimated it? I’m a self-motivated 
person, and the fade effect is so fascinating that I really like to delve in. 
Of course, those tickets are interesting as well, such as regex searching. : ) 
If I’m really want to kill the dragon, where shall I start from?

Sincerely,

Ted

> On Nov 13, 2014, at 4:46 PM, Max Kellermann <[email protected]> wrote:
> 
> On 2014/11/13 03:09, Ted Yin <[email protected]> wrote:
>> Hi everyone,
>> 
>> I???m a fanatic MPD user. Recently I???m interested in providing with extra 
>> functionalities instead of solely using the software. My first try is to 
>> write a client which triggers a command when MPD changes its state: 
>> https://github.com/Determinant/mpd_trigger 
>> <https://github.com/Determinant/mpd_trigger> It???s simple, actually I just 
>> spent two afternoon working on it. Now I???m motivated to try something more 
>> challenging. As I remember, since I started to use MPD, I have wished if 
>> there could be a fade in/fade out effect when a song starts to play or is 
>> being paused, which will definitely more comfortable to users??? ears. 
>> Actually, as I know, there is a ???cross fading??? effect already 
>> incorporated into MPD. However, the simple fade in/fade out effect is still 
>> missing. So I wonder if I could implement that. As a junior college student, 
>> I couldn???t guarantee being always working on it. But maybe when I get free 
>> weekends, things would be done very soon. 
>> 
>> Should I start from reading the doc inside the project root directory? 
> 
> I'm glad you want to help.  As with all (open source) software
> projects, there's always a lot to do, and work left undone due to lack
> of time, no matter how large the team.
> 
> However, maybe fading isn't the best thing to get started with MPD.
> It must be implemented in the core of the player thread, and the
> player thread is the most complicated piece of code inside MPD.
> 
> Pick something easier to get started to avoid early frustration.  For
> example, write a new plugin, or improve an existing plugin.  Refactor
> some code or write API documentation.
> 
> Some tickets you could work on:
> 
> http://bugs.musicpd.org/view.php?id=4212
> http://bugs.musicpd.org/view.php?id=1580
> http://bugs.musicpd.org/view.php?id=2343
> 
> Or write another resampler based on ffmpeg.
> 
> Max

_______________________________________________
mpd-devel mailing list
[email protected]
http://mailman.blarg.de/listinfo/mpd-devel

Reply via email to