Loading Profile...
My Editor Enhancement Requests
I know similar topics have been raised elsewhere, but here’s my 2p on the subject.
1) Allow manual setting of the first beat of the beat grid. All too often this is set incorrectly on beat 1,2, or 3 and it is extremely frustrating to work with such tracks.
2) Allow user to double or half the perceived BPM as the algorithm will occasionally get this wrong because of the nature of the track. EG I have several 140BPM tracks which are analysed as 70BPM by the editor.
3) Add a bit of intelligence to deal with breakdowns (where there is no beat during the track). The algorithm seems to keep trying to work out the BPM and therefore makes it drift up and down until the beat returns. This is the completely wrong process for 99.9% of dance music. Tempos rarely change radically mid track in music (I know some do, but these are few and far between when compared to the majority). The solution is to calculate the beat grid whilst there is a beat to work with. During a breakdown or other “beatless” gap, assume the BPM is constant as per the previous grid. It should match up perfectly when the beat begins again. If it does not you should be able to normalise it by a very small adjustment as an average between the last set of beats and the current set of beats. This would solve the massive swings in BPM that the editor thinks are happening during quiet periods.
4) The ability to set loop start and end points on individual tracks in the editor, just as you can with the default cue points.
5) Support for multiple cue points in a track, which could easily be defined in the editor. Holding Cue and forward or rewind on the device would make the next one / previous one “active”...
That is all :-)
1) Allow manual setting of the first beat of the beat grid. All too often this is set incorrectly on beat 1,2, or 3 and it is extremely frustrating to work with such tracks.
2) Allow user to double or half the perceived BPM as the algorithm will occasionally get this wrong because of the nature of the track. EG I have several 140BPM tracks which are analysed as 70BPM by the editor.
3) Add a bit of intelligence to deal with breakdowns (where there is no beat during the track). The algorithm seems to keep trying to work out the BPM and therefore makes it drift up and down until the beat returns. This is the completely wrong process for 99.9% of dance music. Tempos rarely change radically mid track in music (I know some do, but these are few and far between when compared to the majority). The solution is to calculate the beat grid whilst there is a beat to work with. During a breakdown or other “beatless” gap, assume the BPM is constant as per the previous grid. It should match up perfectly when the beat begins again. If it does not you should be able to normalise it by a very small adjustment as an average between the last set of beats and the current set of beats. This would solve the massive swings in BPM that the editor thinks are happening during quiet periods.
4) The ability to set loop start and end points on individual tracks in the editor, just as you can with the default cue points.
5) Support for multiple cue points in a track, which could easily be defined in the editor. Holding Cue and forward or rewind on the device would make the next one / previous one “active”...
That is all :-)
I’m Optimistic for the future...
7
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
-
-
Inappropriate?It's funny because I just logged in to raise those same issues and look for answers as well. For instance: After 2 tracks are beat matched together in the editor, how do you keep a track from automatically 'snapping back' if you try to move that track to the 2nd or 3rd beat?
EMPLOYEE
