[Mixxx-devel] GSoC Proposal Draft

If anyone could provide some feedback on my current proposal draft, I would appreciate it! My draft can be found at: Weeks - Mixxx GSoC Proposal_Draft Thanks! *Victor J Weeks* BS in Psychology vict

Re: [Mixxx-devel] GSoC proposal review

Hi Nimit, thank you for your first GSoC project draft. The proposed effects seams to be a nice addition for Mixxx's radio use case. Do you or one of your friends have any experiences with broadcasting? I am in doubt if we are able to understand and adopt the signal theory implemented in the eff

Re: [Mixxx-devel] GSoC proposal review

Hello, First chill. Everyone here doesn't have infinite time to get on things like this. But about proposal I don't think you can do that much in one summer. Four effects ain't going to happen in three months. You should add at least one to make sure you understand Mixxx inner things forehan

Re: [Mixxx-devel] GSoC proposal review

Please rate it, I want to know did I make the proposal correct, as I first time write the proposal I don't know much if its write On Wed, Mar 22, 2017 at 11:07 PM, Nimit Bhardwaj wrote: > Please rate my proposal for GSoC this year, I am going to code for the > microphone effects please see it a

[Mixxx-devel] GSoC proposal review

Please rate my proposal for GSoC this year, I am going to code for the microphone effects please see it and give me suggestions that things which can i add or remove. I hope that this is good proposal, and mind my english im not expert of english ;-) proposal.pdf Description: Adobe PDF document

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Man, these bugs go way back, all 0f these issues have been long awaited. I'm really excited that Joan has chosen this set of features. Thanks Joan!! I guess this old forum post tries to articulate the rationale for crates being the core developer's pr

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

Hi RAWRR, yes, right. Once we have the crates tree, we can also introduce Smart Crates (autogenerate by a rule) Related: https://bugs.launchpad.net/mixxx/+bug/661460 https://bugs.launchpad.net/mixxx/+bug/1228789 https://bugs.launchpad.net/mixxx/+bug/671632 Kind regards, Daniel Am 05.04.2016 u

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It does look exciting. However, if that feature cannot "autogenerate" crates according to artist (or genre or BPM or whatever is preferred) it 100% *does not* fulfill the same purpose. I have over a thousand artists in my collection. Making a Crate f

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

Hi, please Note, that there is an unfinished "Multilevel crates" branch the looks promising: https://github.com/mixxxdj/mixxx/pull/726 I like to see it in Mixxx and it should fit to Joan's proposal. Kind regards, Daniel 2016-04-05 0:42 GMT+02:00 : > -BEGIN PGP SIGNED MESSAGE- > Hash: S

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 04 Apr 2016 16:35:55 -0100 "Joan Marcè i Igual" wrote: >Hi RAWRR, > >Thank you for your suggestions. > >When you talk about the Browse PC view you refer to porting the >the >advantage of using folders elsewhere in the library. Do you mean >b

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

Hi RAWRR, Thank you for your suggestions. When you talk about the Browse PC view you refer to porting the the advantage of using folders elsewhere in the library. Do you mean by this adding also the folders feature to the current library and allowing the user to set the tracks on "virtual" folder

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I keep track of my own bugs and those I subscribe to best, so here are a few relevant ones juxtaposed with observations and suggestions: - - Library view v0.1.2 - This more or less offers a solution to "request filter system in browser on i.e. genre

Re: [Mixxx-devel] GSoC Proposal: Library Layout Redesign

Hi skin artists, IMHO Joan's proposals, will work good together with various future Mixxx features. But how about the beauty? Are there special demands, he has to consider to work smoothly with all sorts of skins and design aspects? Which part might become an independent widget? If Mixxx will h

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hi Sébastien, yes I'm aware of that. In fact I plan to reserve some time to see how to fit the new widget to Shade. LateNight and Deere are not a problem. In fact, my mock-ups are actually modifications to the Deere skin, and it works well with its minimum size. Thank you for your reminder. 2016-

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hi Daniel, Ferran and all the others, a grid layout is a nice idea, but keep in mind that we have users with a smaller resolution and we need to keep the default skin usable at such lowres. Hope you will find a way to add that button grid without increasing the minimum skin resolution. regard

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Nice to see we have similar points of view. About the grid layout I have to say I actually like it, supposing my proposal is chosen I'll ask to the community which layout they prefer and implement the one that has more support. I can do this while starting to develop the code changes, which don't

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hi Ferran, Yes, orphan cue point is it. I must have miss read it, since we already have this feature in the cue properties tab. A position and a hot cue number, where the later can be 0 = orphan. From this point of view your have proposed (1. from my mail below) a Skin integrated "Hot-Cue" wi

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Okay I think now I understand you. I think what you mean is the same thing that I called "orphan cue points support" in the proposal. In the current proposal, a cue point is always tied to a hot cue. When the hot cue is cleared, the cue point is deleted rather than simply unassigned. This means th

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hi Ferran, Your current proposal already works for me. My ideas came up when thinking about a slick controller intergeneration. After our discussion I am not sure if we need it at all, including the button grid. It can be probably overdone or hard to handle. But lets explain my original idea

Re: [Mixxx-devel] Gsoc Proposal

Hi, Sorry I sent a private reply to Be, rather than a reply to the thread. I have no problems in discussing my proposal in public. I saw that the features Ferran is suggesting are not conflicting with mine. Rather if both the projects selected can actually improve the cue features in mixxx by a gre

Re: [Mixxx-devel] Gsoc Proposal

Hi Be, both proposals are concurrenting for a GSoC project. They are two among others, where the students decide to keep it private. Am 22.03.2016 5:17 nachm. schrieb "Be" : > Hi Kartik, can you describe how your proposals could work together with > Ferran's proposed new cue list widget? > > On 0

Re: [Mixxx-devel] GSOC proposal: cue points revamp

2016-03-22 17:44 GMT+01:00 Be : > Another idea: the status of the cue list edit mode could be a CO that is > accessible by controller scripts. Although I think in most cases it would > be easiest to do most editing of cue points with a mouse, some users may > want to do that with a controller. Y

Re: [Mixxx-devel] GSOC proposal: cue points revamp

On 03/22/2016 11:18 AM, Ferran Pujol Camins wrote: > 2016-03-22 16:59 GMT+01:00 Be mailto:b...@gmx.com>>: > > 4. I think cues should be able to be dragged and dropped on the > overview as well as the detail waveform. Perhaps this should only > work while the cue list is in edit mode t

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Another idea: the status of the cue list edit mode could be a CO that is accessible by controller scripts. Although I think in most cases it would be easiest to do most editing of cue points with a mouse, some users may want to do that with a controller. On 03/22/2016 06:19 AM, Ferran Pujol Cam

Re: [Mixxx-devel] GSOC proposal: cue points revamp

2016-03-22 16:59 GMT+01:00 Be : > 1. Cue colors: How to represent these? HTML/CSS style RGB codes? Integers > mapped to specific colors? I think it would make sense to use RGB codes in > the backend for maximum flexibility in the future but only present the > options for a handful of specific colo

Re: [Mixxx-devel] Gsoc Proposal

Hi Kartik, can you describe how your proposals could work together with Ferran's proposed new cue list widget? On 03/15/2016 04:06 PM, kartik gupta wrote: > Hi, > I have added a proposal related to addition of cue related features > in mixxx. I am providing a link to the draft below. I would

Re: [Mixxx-devel] GSOC proposal: cue points revamp

This is turning into a nice proposal :) Some comments and questions for this new draft: 1. Cue colors: How to represent these? HTML/CSS style RGB codes? Integers mapped to specific colors? I think it would make sense to use RGB codes in the backend for maximum flexibility in the future but only

Re: [Mixxx-devel] GSOC proposal: cue points revamp

2016-03-22 16:14 GMT+01:00 Daniel Schürmann : > IMHO it is not required to reflect the exactly the controller layout. > It was only my thought about how to reflect a static button grid with > probably multi layers and labels on the controller in your GUI. So would a 2x4 (2 rows 4 buttons per row

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hi Ferran, IMHO it is not required to reflect the exactly the controller layout. It was only my thought about how to reflect a static button grid with probably multi layers and labels on the controller in your GUI. If I got it right, the first four Cue-points are tied to the hot cues. If a user w

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hey Daniel, Good point, a cue grid would better fit current controllers. There are some complications: Different controllers have different have different button layouts. Yours is 2x2, a MidiFighter or Kontrol F1 is 4x4 and DDJ-RZ is 2x4. Furthermore, if a User splits a 4x4 controller between two

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hi Ferran, the new hot cue list looks really nice. I am just worrying if this will meet the design of recent DJ controllers. On My RMX 2, I can switch four button per deck to be loop or hotcue buttons. Idea (not sure if good): A button Grid view of the Cue widget, that represents the Hot-Cue COs

Re: [Mixxx-devel] GSoc Proposal

Hello,m It think your third proposal is already proposed please see backward from the list history are you having same kind of thoughs. For the first and the second you should give some visual/text hints what you want to do before they can be reviewed. There is lot left with metadata handling

[Mixxx-devel] GSoc Proposal

Hello, I am Joan and I am currently at my third year of engineering in Computer Science and Mechanical Engineering at UPC, Barcelona. I am interested in applying for GSoC 2016 under Mixxx for Meta Data tracking editor. While I was reading the idea list, I found three improvements that can be very

Re: [Mixxx-devel] GSOC proposal: cue points revamp

On 3/16/2016 3:28 PM, Daniel Schürmann wrote: > > * Recall loop cues: > IMHO DJSally jump mode requires, that the jump happens on cue button > press and not after release. > If you distinguish, the activate mode by a long press, you can't jump > mediately, which is probably required to mix beat s

Re: [Mixxx-devel] GSOC proposal: cue points revamp

You made some interesting observations, so long mail :) : 2016-03-16 21:28 GMT+01:00 Daniel Schürmann : > * Recall loop cues: > IMHO DJSally jump mode requires, that the jump happens on cue button press > and not after release. > If you distinguish, the activate mode by a long press, you can't

Re: [Mixxx-devel] Gsoc Proposal

Hi Sagnik Mondal, welcome to Mixxx. You will find most infos in our Wiki http://www.mixxx.org/wiki/doku.php/gsoc Apart from a high quality project proposal, you can increase a chance a lot, if you become an active part of the Mixxx community. * Help othe users in the forum * Find and report Bugs

Re: [Mixxx-devel] GSoC proposal

IMO further work to improve the keyboard mapping system should consolidate it into the controller mapping system so it can be scripted. Pressing a button on a controller should be able to do just as much as pressing a button on a keyboard. I'm not sure this is something that could fit into a GS

Re: [Mixxx-devel] GSOC proposal: cue points revamp

Hi Ferran, thank you for your real nice proposal. Here some unsorted comments: * nice Idea using personas for the use cases * Recall loop cues: IMHO DJSally jump mode requires, that the jump happens on cue button press and not after release. If you distinguish, the activate mode by a long press

[Mixxx-devel] Gsoc Proposal

Sir/Ma'am, I am a sophomore pursuing Computer Science Engineering and well versed in c/c++. I am really interested to work for Mixxx in GSOC 16. Can u please tell me how to proceed with the same so that i could prepare my proposal at the earliest. Also it would help if you could tell me what projec

Re: [Mixxx-devel] GSOC proposal: cue points revamp

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

[Mixxx-devel] Gsoc Proposal

Hi, I have added a proposal related to addition of cue related features in mixxx. I am providing a link to the draft below. I would like to have feedback on the same. Draft Link: https://docs.google.com/document/d/1naks-BN55n1VcLysBCg8r3owGznWoO7_kik8_aXMM2Y/edit?usp=sharing Thank you, Kartik

Re: [Mixxx-devel] GSoC proposal

Hi vilvaneshk, I have just read you proposal. It includes some good ideas. Especially I like the preferences search Idea and the mapping pop up. The later could also useful if it includes the controller mapping as well. Did you already try to map you keyboard? I am afraid it could be hard with yo

[Mixxx-devel] GSoC proposal

Hi Everyone , I have written a project proposal for GSoC — https://docs.google.com/document/d/1usyBgcI3ROTTJ9pPfkilEU70bvYf_aENaMYpKfIEVDk/edit?usp=sharing Since I’m new to the community and the user base , it is a hard for me to think of how exactly users will be benef

[Mixxx-devel] GSoC proposal - rates of effect oscillation

Hello!   I'm a student at University of Wrocław, Poland. I'm interesting in programming and music, especially electronic music and DJing. I have (I think) good knowledge about C++ and object-oriented programming, I wrote some code with GTK+ once, but I'm not much experienced and GSoC must be a g

Re: [Mixxx-devel] GSOC Proposal for Intelligent Track Suggestions

On Fri, 03 May 2013 14:05:55 +0200, Mina Nagy Zaki wrote: > Hello everyone! > > I'm Mina Nagy, from Egypt. > > I just submitted a proposal for GSOC for the Intelligent Track > Suggestions idea. I know this is so very last second but I've had some > college work preoccupy me. > > I'd like to

[Mixxx-devel] GSoC Proposal for Intelligent Track Suggestions

Hello! This is my proposal: https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/masetti/1 Giulio Masetti. -- Scrivo utilizzando Unicode UTF-8 "Credere a tutto e dubitare di tutto sono due soluzioni ugualmente comode poiché entrambe ci dispensano dal pensare" (H. Poincaré) -

[Mixxx-devel] GSOC Proposal for Intelligent Track Suggestions

Hello everyone! I'm Mina Nagy, from Egypt. I just submitted a proposal for GSOC for the Intelligent Track Suggestions idea. I know this is so very last second but I've had some college work preoccupy me. I'd like to also prove that I'm actually capable of coding by submitting a patch or tw