Re: [Mixxx-devel] Pioneer DDJ-SB mapping

2015-07-23 Thread Be
You can simplify your BindControlConnections function. See the connectDeckControls function in http://mixxx.org/wiki/doku.php/midi_scripting#turning_a_2_deck_controller_into_a_4_deck_controller for an example. On 07/23/2015 06:19 PM, Joan Ardiaca Jové wrote: > Hello, > > I just pushed the curr

Re: [Mixxx-devel] Pioneer DDJ-SB mapping

2015-07-23 Thread Be
Given how much is left to do, I think it'd be better for 1.12 to leave this out so users search for a more up-to-date version on the forum rather than load an incomplete one and not bother looking on the forum. On 07/23/2015 06:19 PM, Joan Ardiaca Jové wrote: > Hello, > > I just pushed the curre

[Mixxx-devel] Pioneer DDJ-SB mapping

2015-07-23 Thread Joan Ardiaca Jové
Hello, I just pushed the current state of my work on the Pioneer DDJ-SB mapping to my fork in github: https://github.com/jardiacaj/mixxx/commit/9f479f3e7d31b9faec755153cfe7a2f5f3f5de03 Please note this is unfinished work in a "works for me" state, I would like to continue working on it. I mostly

Re: [Mixxx-devel] 1.12 release progress

2015-07-23 Thread Owen Williams
Streaming instability: I agree that this is a blocker bug. We have a lot of users that rely on Mixxx for their streaming radio stations and it would be a huge problem if the new version makes their streams unlistenable. This is a bug I think we should focus on. We should either determine that t

[Mixxx-devel] Deere state

2015-07-23 Thread Ferran Pujol Camins
Hello, I thought I could put some love to Deere. But before I start to commit things that may not be appropriate, I would like to know if there are any specific plans for it. Whose the maintainer? Any suggestions? -- __

Re: [Mixxx-devel] 1.12 manual

2015-07-23 Thread RJ Ryan
We decided to use it specifically for the manual, website, etc. repositories. The overhead of making a manual/website/etc. project on LP just to track issues isn't worth the overhead. (we're treating the manual, website, etc. as separate projects from the mixxx main repo so it doesn't make sense to

Re: [Mixxx-devel] 1.12 manual

2015-07-23 Thread Sean M. Pappalardo - D.J. Pegasus
On 07/23/2015 01:58 AM, Max Linke wrote: See https://github.com/mixxxdj/manual/issues/24 Eehh, I wish you wouldn't start tracking issues in GitHub now too. We already use Launchpad. I suggest re-filing that as a bug in LP and targeting it to the 1.12 milestone so it shows up on that summa

Re: [Mixxx-devel] 1.12 release progress

2015-07-23 Thread Owen Williams
Thanks for all the PRs :). I will go through them as soon as I can. On Wed, 2015-07-22 at 17:02 -0400, Owen Williams wrote: > For PRs that people think are ready and would like to merge in, can you > list the actual numbers? Our PR list is very dense and fast-moving. > > I am willing to take

Re: [Mixxx-devel] 1.12 release progress

2015-07-23 Thread Max Linke
On 07/23/2015 01:29 AM, Sébastien Blaisot wrote: > > Le 22/07/2015 23:02, Owen Williams a écrit : >> For PRs that people think are ready and would like to merge in, can you >> list the actual numbers? Our PR list is very dense and fast-moving. >> >> I am willing to take a look at the PRs that ar

Re: [Mixxx-devel] 1.12 manual

2015-07-23 Thread Max Linke
See https://github.com/mixxxdj/manual/issues/24 We have started to list issues with the manual in github to make it easier to track them. best Max On 07/23/2015 09:32 AM, Be wrote: > The MIDI mapping GUI needs to be documented. Who wrote this? > > I think Chapter 5, the overview of the interfac

Re: [Mixxx-devel] 1.12 manual

2015-07-23 Thread Be
The MIDI mapping GUI needs to be documented. Who wrote this? I think Chapter 5, the overview of the interface, needs the most work to reflect the new skins. I think Chapter 10 could be split up into 2 or 3 chapters with some sections moved to other places in the manual. 17 sections in one chapt