Re: [Mixxx-devel] release progress

I forked the repository and made a few local changes to the LateNight skin. They should be in the 1.12 release in my opinion. Now I'm struggling with getting the changes pushed into my repository. Please give me a few minutes.. Am 22.06.2015 um 22:39 schrieb Be: > On 06/14/2015 12:33 PM, Sébas

Re: [Mixxx-devel] release progress

On 06/14/2015 12:33 PM, Sébastien Blaisot wrote:> Remaining: > * skin polish (Jus has an active Deere branch) => bug lp:1454649 > remaining. Is there other work needed ? Yeah, the effects GUIs are confusingly inconsistent across the skins. See http://mixxx.org/forums/viewtopic.php?f=1&t=5062&st

Re: [Mixxx-devel] release progress

In about a month or so I'll be able to actively work on spanish and catalan translations. I might also try to write something for the manual. 2015-06-14 20:07 GMT+02:00 Be : > I started working on revising chapter 3 of the manual and adding a > section describing how use a stereo splitter adapter

Re: [Mixxx-devel] release progress

I started working on revising chapter 3 of the manual and adding a section describing how use a stereo splitter adapter/cable now that Mixxx can output to single channels. There are still a lot of parts of the manual that need updating. On 06/14/2015 01:04 PM, S.Brandt wrote: > > >> On Jun 14,

Re: [Mixxx-devel] release progress

> On Jun 14, 2015, at 7:33 PM, Sébastien Blaisot wrote: > > We also need to open > more languages for website translation on transifex The available source strings are for the current v1.11. We need to update the website source for 1.12, then make the source strings available for translatio

Re: [Mixxx-devel] release progress

This isn't critical, but I would expect reviewers to write things like "The new key detection is a step forward, but it has some rough edges" unless this is fixed: https://bugs.launchpad.net/mixxx/+bug/1435628 I think users will expect meaningful key sorting and those who are used to it in other

Re: [Mixxx-devel] release progress

OK, trying to gather what we said about "1.12 release blockers": Done: * skin polish (Jus has an active Deere branch) => PR579 & PR608 merged. * (win) installing 1.12 on top of a previous version installation => PR621 waiting for merge * (win) Uninstalling Mixxx leave files behind => PR603 merge

Re: [Mixxx-devel] release progress

Oh, the three filter knobs next to each deck aren't meant to all be filter knobs. They could be effect superknobs and/or effect parameters. On 06/08/2015 05:13 PM, Be wrote: > Hmm, interesting sketch. I like the idea of having the EQs and volume > fader adjacent to the waveforms. That is a more e

Re: [Mixxx-devel] release progress

Hmm, interesting sketch. I like the idea of having the EQs and volume fader adjacent to the waveforms. That is a more efficient use of space than putting the mixer between the decks. However, in your mockup, I think it would be easy to confuse which controls are for which deck. I think moving t

Re: [Mixxx-devel] release progress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 08 Jun 2015 21:15:37 + "Daniel Schürmann" wrote: >If I recall it correct, it should help. >This has also the benefit that you can see more tracks in the >library. > And whatever other controls as well... interesting. > >Am 08.06.2015 um

Re: [Mixxx-devel] release progress

If I recall it correct, it should help. This has also the benefit that you can see more tracks in the library. Am 08.06.2015 um 23:10 schrieb re-cy...@hushmail.com: > Interesting re: CPU. What do you think about decreasing the height > but keeping the width re: CPU? > > ~RAWRR > > > On Mon, 08 Ju

Re: [Mixxx-devel] release progress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Interesting re: CPU. What do you think about decreasing the height but keeping the width re: CPU? ~RAWRR On Mon, 08 Jun 2015 21:00:52 + "Daniel Schürmann" wrote: >Hi Markus, > >Nice mock-up. > >In the past we had issues with four full size Wave

Re: [Mixxx-devel] release progress

Hi Markus, Nice mock-up. In the past we had issues with four full size Waveforms because the CPU usage increases with the size. So I am afraid that view does not suit to be part of Mixxx default skin. IMHO we have already more then enough view options in the LateNight skin. But there should be n

Re: [Mixxx-devel] release progress

> Any thoughts on the general outline I proposed? > > [master gain][balance][head mix][head gain][4/2 deck toggle] > [Deck 1][Deck 1/2 mixer][Deck 2] > waveform 1 > waveform 2 > waveform 3 > waveform 4 > [Deck 3][Deck 3/4 mixer][Deck 4] I'm using Mixxx without controller without scratching and so

Re: [Mixxx-devel] release progress

I tested it and it helps, but adding these options feels like putting bandages on a bigger design issues that are not very easy to solve. There are so many buttons for skin options at the top that it's kinda overwhelming. However, I think trying to implement better solutions to those design cha

Re: [Mixxx-devel] release progress

"thanks" as in, you tested it and it works well? I don't want to commit without someone taking a look at it. On Sat, 2015-06-06 at 09:30 +, re-cy...@hushmail.com wrote: > On Sat, 06 Jun 2015 00:29:14 + "Owen Williams" > wrote: > >I've posted a PR for some new LateNight display options.

Re: [Mixxx-devel] release progress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 06 Jun 2015 00:29:14 + "Owen Williams" wrote: >I've posted a PR for some new LateNight display options. I'm >definitely >running up against the limits of the skinning engine so I can't do >a lot >more than this. But it makes it possible

Re: [Mixxx-devel] release progress

I've posted a PR for some new LateNight display options. I'm definitely running up against the limits of the skinning engine so I can't do a lot more than this. But it makes it possible to specifically select the big waveforms if you want them. It also makes it possible to turn off the EQs to sa

Re: [Mixxx-devel] release progress

I also miss the wide waveforms. I think something like this would make a good 4-deck layout with tall and wide waveforms: [master gain][balance][head mix][head gain][4/2 deck toggle] [Deck 1][Deck 1/2 mixer][Deck 2] waveform 1 waveform 2 waveform 3 waveform 4 [Deck 3][Deck 3/4 mixer][Deck 4] If

Re: [Mixxx-devel] release progress

I think we should come up with some sort of standard effect rack template that all the skins can share (and theme as necessary) but I'm not sure we can do that in time for release. There is currently not enough room for big waveforms and the mixer and also 4 decks. At low resolutions, it's alread

Re: [Mixxx-devel] release progress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Owen, I've been using the LateNight resizeable skin and I have a couple of issues: Can we get a thing where the effects bank can optionally get minimized, possibly back to the simplistic dials existing previously? I'm running out of real estate on al

Re: [Mixxx-devel] release progress

On Tue, 2015-06-02 at 15:29 -0400, RJ Ryan wrote: > > * skin polish (Jus has an active Deere branch) > > The skins are in kind of bad shape at the moment. They really need > polish to bring them to design bar that we set pretty high with > 1.11.0. You mention skins are in a bad shape -- can yo

Re: [Mixxx-devel] release progress

Le 04/06/2015 19:11, RJ Ryan a écrit : On Thu, Jun 4, 2015 at 12:55 PM, Sébastien Blaisot > wrote: 3) Install Mixxx in a versionned directory (either "Mixxx $VERSION" or better "Mixxx\$VERSION") Pros - Let you install and use different versions at the

Re: [Mixxx-devel] release progress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 It will be pretty cool when those multiple versioned entries in the uninstall panel truly *only* uninstall the version they reference >_< !! And it's fine this doesn't solve for 1.12. As stated earlier, 1.13 won't be too far away. On Thu, 04 Jun

Re: [Mixxx-devel] release progress

On Thu, Jun 4, 2015 at 12:55 PM, Sébastien Blaisot wrote: > 3) Install Mixxx in a versionned directory (either "Mixxx $VERSION" or > better "Mixxx\$VERSION") > > Pros > - Let you install and use different versions at the same time > - no need to worry about files left from earlier version > > Con

Re: [Mixxx-devel] release progress

Le 03/06/2015 15:53, RJ Ryan a écrit : On Tue, Jun 2, 2015 at 7:13 PM, Sébastien Blaisot > wrote: Secondly, we have some anoying bugs with windows installer that should be resolved before releasing 1.12 or they will impact next version as well: - Wh

Re: [Mixxx-devel] release progress

RJ summarized my position correctly. As we increase the velocity of our releases it will get easier to allow a certain feature slip one release cycle. On Wed, 2015-06-03 at 16:11 +0200, Daniel Schürmann wrote: > Hi RJ, > > Thank you for the answer. I think we are on the same track. Releasing >

Re: [Mixxx-devel] release progress

Hi RJ, Thank you for the answer. I think we are on the same track. Releasing the Sound Source fixes and other fixes one or two month after the 1.12.0 release sound reasonable to me. The only thing we have to care about, that we not fail this target because of currently unfinished changes or change

Re: [Mixxx-devel] release progress

On Tue, Jun 2, 2015 at 7:13 PM, Sébastien Blaisot wrote: > Le 02/06/2015 21:29, RJ Ryan a écrit : > > I believe the blocking items are: > > > > * critical Windows bugs > > * skin polish (Jus has an active Deere branch) > > * website updates (I'm working on this) > > * manual updates > > Hi RJ and

Re: [Mixxx-devel] release progress

On Wed, Jun 3, 2015 at 4:06 AM, Daniel Schürmann wrote: > Sound Source refactoring release: > > > We are going on circles. > > We have argued three month ago that we do not want to delay 1.12 by three > month because of > merging the soundsource branch. > > Than Owen has proposed, that we can do

Re: [Mixxx-devel] release progress

Sound Source refactoring release: We are going on circles. We have argued three month ago that we do not want to delay 1.12 by three month because of merging the soundsource branch. Than Owen has proposed, that we can do an another beta after the API is stable. RJ has added +1 This was also a g

Re: [Mixxx-devel] release progress

On 06/02/2015 04:13 PM, Sébastien Blaisot wrote: Secondly, we have some anoying bugs with windows installer that should be resolved before releasing 1.12 or they will impact next version as well:\ I wonder if this is a good time to switch to using WiX to make MSI installers. These handle upg

Re: [Mixxx-devel] release progress

Le 02/06/2015 21:29, RJ Ryan a écrit : > I believe the blocking items are: > > * critical Windows bugs > * skin polish (Jus has an active Deere branch) > * website updates (I'm working on this) > * manual updates Hi RJ and all, I agree with your blockers. In my opinion, there are also two more bl

Re: [Mixxx-devel] release progress

Hi RJ, > Someone recently gave me a Windows laptop so I'm going to setup a Windows build environment to try and look at some of these. Thank you for looking at this. Would you mind to provide windows symbol files from the build server as well? This way we are able to get more infos directly

Re: [Mixxx-devel] release progress

On Tue, Jun 2, 2015 at 4:40 PM, Daniel Schürmann wrote: > Hi RJ, > > > Someone recently gave me a Windows laptop so I'm going to setup a > Windows build environment to try and look at some of these. > > Thank you for looking at this. Would you mind to provide windows symbol > files from the buil

Re: [Mixxx-devel] release progress

On Sat, May 23, 2015 at 8:40 AM, Max Linke wrote: > > > On 05/20/2015 12:40 PM, Daniel Schürmann wrote: > > Hi > > > > # Mixxx 1.12 beta # > > > > My Mixxx 1.12 beta experience on Linux is very good. I do not see any > > issue that > > justifies holding back the release any longer. > I believe t

Re: [Mixxx-devel] release progress

On 05/20/2015 12:40 PM, Daniel Schürmann wrote: > Hi > > # Mixxx 1.12 beta # > > My Mixxx 1.12 beta experience on Linux is very good. I do not see any > issue that > justifies holding back the release any longer. > > On the other hand Mixxx 1.12 beta still suffers 11 critical bugs. All of > them

Re: [Mixxx-devel] release progress

I think we should put out a call specifically for windows testers, and maybe as people to fill out a short survey. It could be that the number of affected users is a small percentage and it's good enough that we can release. Otherwise I agree, the number of bug reports has not been large and if w

[Mixxx-devel] release progress

Hi # Mixxx 1.12 beta # My Mixxx 1.12 beta experience on Linux is very good. I do not see any issue that justifies holding back the release any longer. On the other hand Mixxx 1.12 beta still suffers 11 critical bugs. All of them happen on windows only. My overall test experiences running Mixxx o