User Tools

Site Tools


gsoc2011ideas

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
gsoc2011ideas [2011/03/29 13:26]
rryan [Deliverables]
gsoc2011ideas [2011/03/30 10:39] (current)
rryan
Line 7: Line 7:
 The Mixxx Auto DJ mode is very simplistic -- it mixes songs from the AutoDJ queue and crossfades them with a fixed overlap. This project aims to spruce up AutoDJ support to be much better. In particular, the fade-in and out points of songs should be configurable,​ as well as the crossfade length. More advanced use cases could  The Mixxx Auto DJ mode is very simplistic -- it mixes songs from the AutoDJ queue and crossfades them with a fixed overlap. This project aims to spruce up AutoDJ support to be much better. In particular, the fade-in and out points of songs should be configurable,​ as well as the crossfade length. More advanced use cases could 
  
-==== Deliverables ====  ​+==== Minimum ​Deliverables ====  ​
  
   * Implement ability for track cue-points to be designated as "Fade In" or "Fade Out" points.   * Implement ability for track cue-points to be designated as "Fade In" or "Fade Out" points.
Line 18: Line 18:
 Many professional DJs must report the songs they play at gigs to an organization like ASCAP. Other DJs would simply benefit from the ability to look at their past DJ and see a history of the songs they played. This project aims to bring a Sessions or History feature to the Mixxx library. This feature would show a running history of every song the DJ played with Mixxx, grouped by "​sessions"​ or times that Mixxx was run. Many professional DJs must report the songs they play at gigs to an organization like ASCAP. Other DJs would simply benefit from the ability to look at their past DJ and see a history of the songs they played. This project aims to bring a Sessions or History feature to the Mixxx library. This feature would show a running history of every song the DJ played with Mixxx, grouped by "​sessions"​ or times that Mixxx was run.
    
-==== Deliverables ====+==== Minimum ​Deliverables ====
  
   * Implement a new Library feature (section in the library) for displaying session history.   * Implement a new Library feature (section in the library) for displaying session history.
Line 37: Line 37:
     * Results in tracks with the name "Right Here" and a BPM greater than 140     * Results in tracks with the name "Right Here" and a BPM greater than 140
  
-==== Deliverables ====+==== Minimum ​Deliverables ====
  
   * Implement Full-Text-Search   * Implement Full-Text-Search
Line 49: Line 49:
 If you've used Mixxx, you know that our SYNC button does not work very well! All it does is match up the BPMs of the tracks that are being mixed. There is tons of room for improvement here. The goal of this project is to allow two decks to be synchronized such that they actively check whether they are in sync with the other, and make adjustments to stay in sync. Additionally,​ the creation of a master sync clock for decks to sync to would be great as well, because then the DJ could set the master clock at e.g. 130 BPM and all the songs they load would automatically sync to the tick of that clock. If you've used Mixxx, you know that our SYNC button does not work very well! All it does is match up the BPMs of the tracks that are being mixed. There is tons of room for improvement here. The goal of this project is to allow two decks to be synchronized such that they actively check whether they are in sync with the other, and make adjustments to stay in sync. Additionally,​ the creation of a master sync clock for decks to sync to would be great as well, because then the DJ could set the master clock at e.g. 130 BPM and all the songs they load would automatically sync to the tick of that clock.
  
-==== Deliverables ====  ​+==== Minimum ​Deliverables ====  ​
  
   * Implement a master-clock in the Mixxx engine   * Implement a master-clock in the Mixxx engine
Line 68: Line 68:
 This project will involve a lot of time thinking about use cases, dealing with users and understanding their requirements. It would be a great opportunity for a student to get involved with the Mixxx community. The student will also have the opportunity to borrow a MIDI controller from the development team for the duration of the project. This project will involve a lot of time thinking about use cases, dealing with users and understanding their requirements. It would be a great opportunity for a student to get involved with the Mixxx community. The student will also have the opportunity to borrow a MIDI controller from the development team for the duration of the project.
  
-==== Deliverables ====+==== Minimum ​Deliverables ====
  
   * Implement auto-selection of MIDI mappings based on connected MIDI devices.   * Implement auto-selection of MIDI mappings based on connected MIDI devices.
Line 82: Line 82:
 **IMPORTANT:​ You should [[gsocadvice|contact us]] first to get feedback if you're going to submit a proposal for your own project idea!** **IMPORTANT:​ You should [[gsocadvice|contact us]] first to get feedback if you're going to submit a proposal for your own project idea!**
  
-==== Deliverables ====+==== Minimum ​Deliverables ====
  
   * Something awesome. We will work with you to define the deliverables.   * Something awesome. We will work with you to define the deliverables.
gsoc2011ideas.txt ยท Last modified: 2011/03/30 10:39 by rryan