2017-02-28 00:05 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001839MPDMixer - ALSApublic2013-08-04 23:47
Assigned Tocirrus 
Product Version0.14 
Target VersionFixed in Version 
Summary0001839: Professional fading using cut-in points
DescriptionHello everyone,

I would like to propose a new "professional fading"-feature - but only after saying thanks for a great piece of software to everyone involved!

Now, currently MPD supports crossfading, meaning that the currently playing song fades out and the next one fades in. That is not the way is is done in professional audio applications. These use cut-in and cut-out points. Let me elaborate on the theory using this graphic:

Every song has three distinct points associated:
Cut-In - This is where the sing actually starts. Everything before this point is simply discarded. Let's assume we have a song with a nice, but boring guitar solo "up front". We can simply skip this and come right to where the action is by setting this cut-in point accordingly.
Fadeout - This is where the fadeout would start (if any at all!).
Cut-Out - This is where the song ends "virtually", ie. everything after this point is not played either. Think of songs that slowly fade out into nothingness.
Now, it is important that Fadeout is an optional point! Mostly professionals will not use this as the sing might already contain some "hardcoded" fading.

So, this what I propose:

Minimal spec: MPD understands a (per-track!) Cut-Out point at which playing of the next song starts, no fading whatsoever. Also there should be a "default"-timing of n seconds, which will tell MPD "If no Cut-Out time is given, always start the next track n seconds before the currently playing track ends".
Much better spec: Support all three timings as stated above.

Now, I'm by no means a programmer whatsoever so I leave it up to you to start asking me questions Wink

Thanks in advance for listening,
TagsNo tags attached.
Attached Files

related to 0001575closedcirrus [PATCH] Add support for MixRamp tags. 



cts (reporter)

Originally posted on the MPD forum at


cirrus (administrator)

MPD has MixRamp tags, which should be enough for this, isn't it?

-Issue History
Date Modified Username Field Change
2008-11-26 15:36 cts New Issue
2008-11-26 15:36 cts Status new => assigned
2008-11-26 15:36 cts Assigned To => cirrus
2008-11-26 15:36 cts File Added: 2008 11 26 simple chart of professional crossfading.pdf
2008-11-26 15:39 cts Note Added: 0002481
2008-11-27 12:46 cirrus Relationship added related to 0001575
2013-08-04 23:47 cirrus Note Added: 0007820
2013-08-04 23:47 cirrus Status assigned => closed
2013-08-04 23:47 cirrus Resolution open => fixed
+Issue History