Hi Mel, these would all be great features. 1. Two other students have proposed related projects for expanding on Mixxx's cue point functionality further.
2. How would you go about doing it? How would you detect the time signature of a track? What if the track changes time signatures? 3. Owen has started work on exporting crates that is available in the current master branch. I'm not sure what his plans or timeline are for expanding on that. See also https://blueprints.launchpad.net/mixxx/+spec/portable-library On 3/1/2016 11:39 AM, Mel Grubb wrote: > > I see some others throwing around ideas / wish list items, and thought > I’d throw a couple out as well in case they seem like good candidates > for GSOC assignments. > > 1)Marker Cues: > > These are pseudo-cue points used solely to mark interesting points in > a song, but not to jump to them. I’m talking about decorating songs > with arbitrary markers such as the number of measures remaining. There > are plenty of times I’ve known that a song has a long “bail-out” > section that would be handy to mark, perhaps with a simple number > indicating how many measures from that point until the song kicks back > in, at which point it would be too late to bail. I’m an Industrial/EBM > DJ, and generally do not play planned sets. My home town crowd is too > fickle for that sort of thing. I have to change direction constantly, > and over my entire collection. Leaving myself these kind of notes > would be very handy. > > 2)Beat numbers > > Most DJ software marks off the beatgrid in a way that lets you know > where “1” is. It takes some hand-curation to correctly align the grid > in some cases, but it would be very useful for songs whose lead-in is > not always obvious to the ear. There are plenty of songs I’ve played > for which “1” isn’t immediately obvious until some of the other rhythm > tracks get added in. Having the visible cheat-sheet for these tracks > would be extremely helpful. > > 3)Database location > > I’ve brought this up before, but the ability to change the database > location would help me out a lot. I have a tendency to pave my > computer perhaps a bit more than most. Positioning the database in the > root of my music folder would make it much easier to survive these > rebuilds since I could simply store the database on an external drive > along with my music library. As long as the database could be > persuaded to store relative paths, this would allow me to simply move > the whole thing to a different system and not lose my metadata. This > would also go a long way toward a reasonably portable installation. > Even if the installation itself isn’t total portable, I could at least > move the portable hard drive from one computer to another (e.g. Gig > laptop vs daily driver), and work on set lists at work over lunch. > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > > > _______________________________________________ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
