Hi Ferran, this looks like a great start. My biggest concern is requiring another window to be opened for the fully featured cue point editor. I forsee a few issues with this. First, it would require duplicating a lot of design and functionality from the main window/skins. It would also present an issue for controller mappings as Daniel pointed out. Also, I think the workflow would be awkward for editing cues while playing. I think it would be better to implement the GUI features as a section of skins that could be toggled between showing and hidden. If all features can be intuitively controlled from the main window, I think the cue tab in the Track Properties window would be redundant and could be removed.
A feature that would compliment what you've proposed and be helpful for using controllers would be to create control objects that sequentially represent a specific type of cue. For example, setting loop_cue_1 to 1 would enable whatever the first loop cue is, regardless of what number hotcue it is assigned or what number cue it is in the database. This would allow controller mappings to have different layers for their pads/buttons for using different types of cues. All types of cues should be able to be mixed and matched in one big list as well. This would allow users to arrange different types of cues however they want in a way that makes sense for their use and on their controller. For example, a user could set cue 1 to a simple hotcue for a point and cue 2 to a loop cue starting at that same point, but the user might not ever want a loop at cue 3. The user could either press pad 1 or 2 depending on whether they wanted to loop without having to switch to a different layer of the mapping. Is there anything that should be done for "the" cue point? How does it fit into this expanded model of cue points? On 3/16/2016 2:19 PM, Ferran Pujol Camins wrote: > Hello! > This is my GSOC proposal for this year: Cue points revamp. It's all > pretty much explained in the document. > > The proposal is not complete. It lacks the definition of a couple of > features, the work breakdown + code analysis and timeline elaboration. > I have time to finish all this on time. > > But first I'd like to get some feedback on the features specification > I've got so far. There is a considerable amount of work, but it is a > collection of several features, so functionally complete merges to > trunk can be done. > > Let me now what you think. Specially things you don't like, things you > don't clearly understand or things you are not sure about. Comments > about the proposal text itself are also welcome. > > Best regards, Ferran. > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
