Re: [Mixxx-devel] release progress

[Thorsten Munsch]

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é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&start=40
> https://bugs.launchpad.net/mixxx/+bug/1467196
>
> Also:
> https://bugs.launchpad.net/mixxx/+bug/1466966
> https://bugs.launchpad.net/mixxx/+bug/1296089
>
> --
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> ___
> 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
>

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
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

Re: [Mixxx-devel] release progress

[Be]

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&start=40
https://bugs.launchpad.net/mixxx/+bug/1467196

Also:
https://bugs.launchpad.net/mixxx/+bug/1466966
https://bugs.launchpad.net/mixxx/+bug/1296089

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
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

Re: [Mixxx-devel] release progress

[Ferran Pujol Camins]

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/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, 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 translation.
> > If you translate now, be prepared for additional work once the strings
> > have been updated (This is the reason de_DE translation is incomplete)
> >
> > The current number of available languages reflects the number of
> > requests we got for website translation.
> > Just added fr_FR.
> > Getting a request does not mean someone is doing actual translations,
> > see tr_TR
> >
> >> * manual updates => Does somebody work on this actually ?
> >
> > Afaik none
> >
> >
> >
> --
> >
> >
> >
> > ___
> > 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
> >
>
>
> --
> ___
> 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
>
--
___
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

Re: [Mixxx-devel] release progress

[Be]

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, 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 translation.
> If you translate now, be prepared for additional work once the strings
> have been updated (This is the reason de_DE translation is incomplete)
>
> The current number of available languages reflects the number of
> requests we got for website translation.
> Just added fr_FR.
> Getting a request does not mean someone is doing actual translations,
> see tr_TR
>
>> * manual updates => Does somebody work on this actually ?
>
> Afaik none
>
>
> --
>
>
>
> ___
> 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
>

--
___
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

Re: [Mixxx-devel] release progress

[S.Brandt]

> 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 translation.
If you translate now, be prepared for additional work once the strings have 
been updated (This is the reason de_DE translation is incomplete)

The current number of available languages reflects the number of requests we 
got for website translation.
Just added fr_FR.
Getting a request does not mean someone is doing actual translations, see tr_TR

> * manual updates => Does somebody work on this actually ?

Afaik none--
___
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

Re: [Mixxx-devel] release progress

[Be]

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 software such as Traktor will think Mixxx is unpolished.

On 06/14/2015 12:33 PM, Sébastien Blaisot wrote:
>
> 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 merged
> * (win) Incorrect preferences folder path => PR606 merged
>
> Remaining:
> * critical Windows bugs => RJ told he will have a look at them. can we
> list the critical blockers here ?
> * skin polish (Jus has an active Deere branch) => bug lp:1454649
> remaining. Is there other work needed ?
> * website updates (RJ ryan is working on this). We also need to open
> more languages for website translation on transifex. it's actually
> limited to english, german, portuguese and Turkish. I can make french
> (france) translation.
> * manual updates => Does somebody work on this actually ?
> * avoid flanger warning message for shipped with mixxx controller
> mappings (hack it by making an ignore list) => Does somebody work on
> this actually ?
> * XDG folders under Linux : We have to decide if it is a 1.12 issue or
> if we postpone it. see lp:1463273 and PR622
> * Unstable broadcasting stream => lp:1277274
>
>
> Is there any other blockers ?
>

--
___
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

Re: [Mixxx-devel] release progress

[Sébastien Blaisot]

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 merged
* (win) Incorrect preferences folder path => PR606 merged

Remaining:
* critical Windows bugs => RJ told he will have a look at them. can we 
list the critical blockers here ?
* skin polish (Jus has an active Deere branch) => bug lp:1454649 
remaining. Is there other work needed ?
* website updates (RJ ryan is working on this). We also need to open 
more languages for website translation on transifex. it's actually 
limited to english, german, portuguese and Turkish. I can make french 
(france) translation.
* manual updates => Does somebody work on this actually ?
* avoid flanger warning message for shipped with mixxx controller 
mappings (hack it by making an ignore list) => Does somebody work on 
this actually ?
* XDG folders under Linux : We have to decide if it is a 1.12 issue or 
if we postpone it. see lp:1463273 and PR622
* Unstable broadcasting stream => lp:1277274


Is there any other blockers ?

-- 
Sébastien
圣巴斯弟盎




--
___
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

Re: [Mixxx-devel] release progress

[Be]

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 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 two of the decks to the top so they could be closer to
> their respective waveforms would help.
>
> I think only having two different colors for color coding four decks can
> get confusing, so I made a mockup with a color for each deck. I tried
> shading the background of all the deck controls with the waveform
> background color, which makes a clear visual connection between the deck
> controls and the waveforms because they are all contiguous. The colors
> are not the prettiest, but that would be a detail to work out later.
>
> Here is a mockup:
> http://i.imgur.com/XAE1ZKf.png
>
> It could be interesting to make the spaces between the decks
> individually swapable between effects and samplers.
>
> For two deck mode, either the top or bottom two decks could be hidden to
> make room for the small library. Hiding the top two decks would provide
> an interface similar to old LateNight skins.
>
> Thoughts?
>
> On 06/08/2015 11:42 AM, Markus Klösges wrote:
>>> 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 on, just
>> simple crossfading with external mixer and so on.
>> I would also prefer the option to have the (almost) screen-wide
>> waveforms. I liked the 'old' 1.11 Latenight. Clearly that doesn't work
>> out for 4 decks.
>>
>> I think one should not clutter a skin with dozens of config-options but
>> better fork that skin (or decide for one, better, solution maybe).
>>
>> The option to get the bigLibrary is a real benefit for me and results in
>> lesser need of a large library when everything is turned on.
>>
>> The only reason I have the mixer turned on is the crossfader and the
>> preview-Buttons. On my machine, in 4 and 2 deck mode without the mixer
>> there is some space where the mixxx logo is displayed. Would it be
>> possible to get the crossfader (and maybe the cue-buttons) there? That
>> would result in the big waveforms for me.
>>
>> Another option would be to make the waveforms (nearly) screen-wide and
>> place pitch, EQ, Volume, Cue, on the left and right (as pitch was in
>> 1.11). That would only leave crossfader, Master, Balance, HeadGain and
>> Pre/Main from the mixer-section what could eventually be placed like
>> proposed above where the mixxx logo is, in between of previewDeck and
>> maybe Mics.
>> [pitch/EQ/Vol Deck1] [Waveform 1] [pitch/EQ/Vol Deck2]
>> [--] [Waveform 3] [--]
>> [pitch/EQ/Vol Deck3] [Waveform 2] [pitch/EQ/Vol Deck4]
>> [--] [Waveform 4] [--]
>> [ Deck1 ]   [ Deck2 ] [ Deck3 ]  [ Deck4 ]
>> [PreviewDeck]   [   Crossfade/Master  ]  [Microphones]
>> [Samplers]
>> [Effects]
>> [Library]
>>
>> I've done a quick sketch http://imgur.com/MruunAd
>> I've not rescaled anything except some little changes and this dosn't
>> get bigger than the current approach but gives much bigger waveforms.
>>
>> But I am unsure if this is out of scope for LateNight and should better
>> be done in an other skin.
>>
>> What do you think?
>>
>> Cheers,
>> Markus
>>
>> Am 08.06.2015 um 03:44 schrieb Be:
>>> 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 challenges would take a lot of effort that shouldn't delay
>>> 1.12.
>>>
>>> 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]
>>>
>>> On 06/06/2015 01:04 PM, Owen Williams wrote:
 "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.  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
>>>

Re: [Mixxx-devel] release progress

[Be]

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 two of the decks to the top so they could be closer to 
their respective waveforms would help.

I think only having two different colors for color coding four decks can 
get confusing, so I made a mockup with a color for each deck. I tried 
shading the background of all the deck controls with the waveform 
background color, which makes a clear visual connection between the deck 
controls and the waveforms because they are all contiguous. The colors 
are not the prettiest, but that would be a detail to work out later.

Here is a mockup:
http://i.imgur.com/XAE1ZKf.png

It could be interesting to make the spaces between the decks 
individually swapable between effects and samplers.

For two deck mode, either the top or bottom two decks could be hidden to 
make room for the small library. Hiding the top two decks would provide 
an interface similar to old LateNight skins.

Thoughts?

On 06/08/2015 11:42 AM, Markus Klösges wrote:
>> 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 on, just
> simple crossfading with external mixer and so on.
> I would also prefer the option to have the (almost) screen-wide
> waveforms. I liked the 'old' 1.11 Latenight. Clearly that doesn't work
> out for 4 decks.
>
> I think one should not clutter a skin with dozens of config-options but
> better fork that skin (or decide for one, better, solution maybe).
>
> The option to get the bigLibrary is a real benefit for me and results in
> lesser need of a large library when everything is turned on.
>
> The only reason I have the mixer turned on is the crossfader and the
> preview-Buttons. On my machine, in 4 and 2 deck mode without the mixer
> there is some space where the mixxx logo is displayed. Would it be
> possible to get the crossfader (and maybe the cue-buttons) there? That
> would result in the big waveforms for me.
>
> Another option would be to make the waveforms (nearly) screen-wide and
> place pitch, EQ, Volume, Cue, on the left and right (as pitch was in
> 1.11). That would only leave crossfader, Master, Balance, HeadGain and
> Pre/Main from the mixer-section what could eventually be placed like
> proposed above where the mixxx logo is, in between of previewDeck and
> maybe Mics.
> [pitch/EQ/Vol Deck1] [Waveform 1] [pitch/EQ/Vol Deck2]
> [--] [Waveform 3] [--]
> [pitch/EQ/Vol Deck3] [Waveform 2] [pitch/EQ/Vol Deck4]
> [--] [Waveform 4] [--]
> [ Deck1 ]   [ Deck2 ] [ Deck3 ]  [ Deck4 ]
> [PreviewDeck]   [   Crossfade/Master  ]  [Microphones]
> [Samplers]
> [Effects]
> [Library]
>
> I've done a quick sketch http://imgur.com/MruunAd
> I've not rescaled anything except some little changes and this dosn't
> get bigger than the current approach but gives much bigger waveforms.
>
> But I am unsure if this is out of scope for LateNight and should better
> be done in an other skin.
>
> What do you think?
>
> Cheers,
> Markus
>
> Am 08.06.2015 um 03:44 schrieb Be:
>> 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 challenges would take a lot of effort that shouldn't delay
>> 1.12.
>>
>> 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]
>>
>> On 06/06/2015 01:04 PM, Owen Williams wrote:
>>> "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.  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 save some vertical space without eliminating the whole
> mixer.
>

 Thanks:)

>
> On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com wrote:
>> Owen,
>>>

Re: [Mixxx-devel] release progress

[re-cycle]

-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 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 Jun 2015 21:00:52 + "Daniel Schürmann"
>>  wrote:
>> > 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 no problem with a recent devices.
>> > If this is the perfect skin for you use case, you are welcome
>to
>> > fork it.
>> > Thats the benefit of our skin engine.
>>
>> > Kind regards.
>>
>> > Daniel
>>
>>
>>
>> > Am 08.06.2015 um 18:42 schrieb Markus Klösges:
>> >>> 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
>on,
>> > just
>> >> simple crossfading with external mixer and so on.
>> >> I would also prefer the option to have the (almost) screen-
>wide
>> >> waveforms. I liked the 'old' 1.11 Latenight. Clearly that
>> > doesn't work
>> >> out for 4 decks.
>> >>
>> >> I think one should not clutter a skin with dozens of config-
>> > options but
>> >> better fork that skin (or decide for one, better, solution
>> > maybe).
>> >>
>> >> The option to get the bigLibrary is a real benefit for me and
>> > results in
>> >> lesser need of a large library when everything is turned on.
>> >>
>> >> The only reason I have the mixer turned on is the crossfader
>and
>> > the
>> >> preview-Buttons. On my machine, in 4 and 2 deck mode without
>the
>> > mixer
>> >> there is some space where the mixxx logo is displayed. Would
>it
>> > be
>> >> possible to get the crossfader (and maybe the cue-buttons)
>> > there? That
>> >> would result in the big waveforms for me.
>> >>
>> >> Another option would be to make the waveforms (nearly) screen-
>
>> > wide and
>> >> place pitch, EQ, Volume, Cue, on the left and right (as pitch
>> > was in
>> >> 1.11). That would only leave crossfader, Master, Balance,
>> > HeadGain and
>> >> Pre/Main from the mixer-section what could eventually be
>placed
>> > like
>> >> proposed above where the mixxx logo is, in between of
>> > previewDeck and
>> >> maybe Mics.
>> >> [pitch/EQ/Vol Deck1] [Waveform 1] [pitch/EQ/Vol Deck2]
>> >> [--] [Waveform 3] [--]
>> >> [pitch/EQ/Vol Deck3] [Waveform 2] [pitch/EQ/Vol Deck4]
>> >> [--] [Waveform 4] [--]
>> >> [ Deck1 ]   [ Deck2 ] [ Deck3 ]  [ Deck4 ]
>> >> [PreviewDeck]   [   Crossfade/Master  ]  [Microphones]
>> >> [Samplers]
>> >> [Effects]
>> >> [Library]
>> >>
>> >> I've done a quick sketch http://imgur.com/MruunAd
>> >> I've not rescaled anything except some little changes and
>this
>> > dosn't
>> >> get bigger than the current approach but gives much bigger
>> > waveforms.
>> >>
>> >> But I am unsure if this is out of scope for LateNight and
>should
>> > better
>> >> be done in an other skin.
>> >>
>> >> What do you think?
>> >>
>> >> Cheers,
>> >> Markus
>> >>
>> >> Am 08.06.2015 um 03:44 schrieb Be:
>> >>> 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 challenges would take a lot of effort that
>> > shouldn't delay
>> >>> 1.12.
>> >>>
>> >>> 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]
>> >>>
>> >>> On 06/06/2015 01:04 PM, Owen Williams wrote:
>>  "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.
>> > I'm
>> >> definitely
>> >> running up against the limits of the skinning engine so I
>> > can't do
>

Re: [Mixxx-devel] release progress

[Daniel Schürmann]

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 Jun 2015 21:00:52 + "Daniel Schürmann"
>  wrote:
> > 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 no problem with a recent devices.
> > If this is the perfect skin for you use case, you are welcome to
> > fork it.
> > Thats the benefit of our skin engine.
>
> > Kind regards.
>
> > Daniel
>
>
>
> > Am 08.06.2015 um 18:42 schrieb Markus Klösges:
> >>> 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 on,
> > just
> >> simple crossfading with external mixer and so on.
> >> I would also prefer the option to have the (almost) screen-wide
> >> waveforms. I liked the 'old' 1.11 Latenight. Clearly that
> > doesn't work
> >> out for 4 decks.
> >>
> >> I think one should not clutter a skin with dozens of config-
> > options but
> >> better fork that skin (or decide for one, better, solution
> > maybe).
> >>
> >> The option to get the bigLibrary is a real benefit for me and
> > results in
> >> lesser need of a large library when everything is turned on.
> >>
> >> The only reason I have the mixer turned on is the crossfader and
> > the
> >> preview-Buttons. On my machine, in 4 and 2 deck mode without the
> > mixer
> >> there is some space where the mixxx logo is displayed. Would it
> > be
> >> possible to get the crossfader (and maybe the cue-buttons)
> > there? That
> >> would result in the big waveforms for me.
> >>
> >> Another option would be to make the waveforms (nearly) screen-
> > wide and
> >> place pitch, EQ, Volume, Cue, on the left and right (as pitch
> > was in
> >> 1.11). That would only leave crossfader, Master, Balance,
> > HeadGain and
> >> Pre/Main from the mixer-section what could eventually be placed
> > like
> >> proposed above where the mixxx logo is, in between of
> > previewDeck and
> >> maybe Mics.
> >> [pitch/EQ/Vol Deck1] [Waveform 1] [pitch/EQ/Vol Deck2]
> >> [--] [Waveform 3] [--]
> >> [pitch/EQ/Vol Deck3] [Waveform 2] [pitch/EQ/Vol Deck4]
> >> [--] [Waveform 4] [--]
> >> [ Deck1 ]   [ Deck2 ] [ Deck3 ]  [ Deck4 ]
> >> [PreviewDeck]   [   Crossfade/Master  ]  [Microphones]
> >> [Samplers]
> >> [Effects]
> >> [Library]
> >>
> >> I've done a quick sketch http://imgur.com/MruunAd
> >> I've not rescaled anything except some little changes and this
> > dosn't
> >> get bigger than the current approach but gives much bigger
> > waveforms.
> >>
> >> But I am unsure if this is out of scope for LateNight and should
> > better
> >> be done in an other skin.
> >>
> >> What do you think?
> >>
> >> Cheers,
> >> Markus
> >>
> >> Am 08.06.2015 um 03:44 schrieb Be:
> >>> 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 challenges would take a lot of effort that
> > shouldn't delay
> >>> 1.12.
> >>>
> >>> 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]
> >>>
> >>> On 06/06/2015 01:04 PM, Owen Williams wrote:
>  "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.
> > 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 save some vertical space without eliminating the
> > whole
> >> mixer.
> >>
> > Thanks:)
> >
>

Re: [Mixxx-devel] release progress

[re-cycle]

-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 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 no problem with a recent devices.
>If this is the perfect skin for you use case, you are welcome to
>fork it.
>Thats the benefit of our skin engine.
>
>Kind regards.
>
>Daniel
>
>
>
>Am 08.06.2015 um 18:42 schrieb Markus Klösges:
>>> 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 on,
>just
>> simple crossfading with external mixer and so on.
>> I would also prefer the option to have the (almost) screen-wide
>> waveforms. I liked the 'old' 1.11 Latenight. Clearly that
>doesn't work
>> out for 4 decks.
>>
>> I think one should not clutter a skin with dozens of config-
>options but
>> better fork that skin (or decide for one, better, solution
>maybe).
>>
>> The option to get the bigLibrary is a real benefit for me and
>results in
>> lesser need of a large library when everything is turned on.
>>
>> The only reason I have the mixer turned on is the crossfader and
>the
>> preview-Buttons. On my machine, in 4 and 2 deck mode without the
>mixer
>> there is some space where the mixxx logo is displayed. Would it
>be
>> possible to get the crossfader (and maybe the cue-buttons)
>there? That
>> would result in the big waveforms for me.
>>
>> Another option would be to make the waveforms (nearly) screen-
>wide and
>> place pitch, EQ, Volume, Cue, on the left and right (as pitch
>was in
>> 1.11). That would only leave crossfader, Master, Balance,
>HeadGain and
>> Pre/Main from the mixer-section what could eventually be placed
>like
>> proposed above where the mixxx logo is, in between of
>previewDeck and
>> maybe Mics.
>> [pitch/EQ/Vol Deck1] [Waveform 1] [pitch/EQ/Vol Deck2]
>> [--] [Waveform 3] [--]
>> [pitch/EQ/Vol Deck3] [Waveform 2] [pitch/EQ/Vol Deck4]
>> [--] [Waveform 4] [--]
>> [ Deck1 ]   [ Deck2 ] [ Deck3 ]  [ Deck4 ]
>> [PreviewDeck]   [   Crossfade/Master  ]  [Microphones]
>> [Samplers]
>> [Effects]
>> [Library]
>>
>> I've done a quick sketch http://imgur.com/MruunAd
>> I've not rescaled anything except some little changes and this
>dosn't
>> get bigger than the current approach but gives much bigger
>waveforms.
>>
>> But I am unsure if this is out of scope for LateNight and should
>better
>> be done in an other skin.
>>
>> What do you think?
>>
>> Cheers,
>> Markus
>>
>> Am 08.06.2015 um 03:44 schrieb Be:
>>> 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 challenges would take a lot of effort that
>shouldn't delay
>>> 1.12.
>>>
>>> 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]
>>>
>>> On 06/06/2015 01:04 PM, Owen Williams wrote:
 "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.
>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 save some vertical space without eliminating the
>whole
>> mixer.
>>
> Thanks:)
>
>> On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com
>wrote:
>>> Owen,
>>>
>>> That mockup was poorly thought out re: mixer, sorry. I
>never use
>> 4
>>> decks :/
>>>
>>> If you aren't sick of my backseat driving yet, I just had
>> another
>>> slightly radical idea - make LateNight's library "toggle
>only",
>> so
>>> that the "big library" button becomes the only way to see
>it.
>> This
>>

Re: [Mixxx-devel] release progress

[Daniel Schürmann]

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 no problem with a recent devices.
If this is the perfect skin for you use case, you are welcome to fork it.
Thats the benefit of our skin engine.
 
Kind regards.

Daniel



Am 08.06.2015 um 18:42 schrieb Markus Klösges:
>> 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 on, just
> simple crossfading with external mixer and so on.
> I would also prefer the option to have the (almost) screen-wide
> waveforms. I liked the 'old' 1.11 Latenight. Clearly that doesn't work
> out for 4 decks.
>
> I think one should not clutter a skin with dozens of config-options but
> better fork that skin (or decide for one, better, solution maybe).
>
> The option to get the bigLibrary is a real benefit for me and results in
> lesser need of a large library when everything is turned on.
>
> The only reason I have the mixer turned on is the crossfader and the
> preview-Buttons. On my machine, in 4 and 2 deck mode without the mixer
> there is some space where the mixxx logo is displayed. Would it be
> possible to get the crossfader (and maybe the cue-buttons) there? That
> would result in the big waveforms for me.
>
> Another option would be to make the waveforms (nearly) screen-wide and
> place pitch, EQ, Volume, Cue, on the left and right (as pitch was in
> 1.11). That would only leave crossfader, Master, Balance, HeadGain and
> Pre/Main from the mixer-section what could eventually be placed like
> proposed above where the mixxx logo is, in between of previewDeck and
> maybe Mics.
> [pitch/EQ/Vol Deck1] [Waveform 1] [pitch/EQ/Vol Deck2]
> [--] [Waveform 3] [--]
> [pitch/EQ/Vol Deck3] [Waveform 2] [pitch/EQ/Vol Deck4]
> [--] [Waveform 4] [--]
> [ Deck1 ]   [ Deck2 ] [ Deck3 ]  [ Deck4 ]
> [PreviewDeck]   [   Crossfade/Master  ]  [Microphones]
> [Samplers]
> [Effects]
> [Library]
>
> I've done a quick sketch http://imgur.com/MruunAd
> I've not rescaled anything except some little changes and this dosn't
> get bigger than the current approach but gives much bigger waveforms.
>
> But I am unsure if this is out of scope for LateNight and should better
> be done in an other skin.
>
> What do you think?
>
> Cheers,
> Markus
>
> Am 08.06.2015 um 03:44 schrieb Be:
>> 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 challenges would take a lot of effort that shouldn't delay 
>> 1.12.
>>
>> 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]
>>
>> On 06/06/2015 01:04 PM, Owen Williams wrote:
>>> "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.  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 save some vertical space without eliminating the whole
> mixer.
>
 Thanks:)

> On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com wrote:
>> Owen,
>>
>> That mockup was poorly thought out re: mixer, sorry. I never use
> 4
>> decks :/
>>
>> If you aren't sick of my backseat driving yet, I just had
> another
>> slightly radical idea - make LateNight's library "toggle only",
> so
>> that the "big library" button becomes the only way to see it.
> This
>> wouldn't inhibit my personal use style, and it would free the
>> entire screen for controls.
>>
>> Possibly a complimentary idea is to let the search field remain
> in
>> the main window, and have "big library" open with the results,
>> either as you type or after hitting enter.
>>
>> Just for fun I've attached the Gimp .xcf layers I used f

Re: [Mixxx-devel] release progress

[Markus Klösges]

> 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 on, just
simple crossfading with external mixer and so on.
I would also prefer the option to have the (almost) screen-wide
waveforms. I liked the 'old' 1.11 Latenight. Clearly that doesn't work
out for 4 decks.

I think one should not clutter a skin with dozens of config-options but
better fork that skin (or decide for one, better, solution maybe).

The option to get the bigLibrary is a real benefit for me and results in
lesser need of a large library when everything is turned on.

The only reason I have the mixer turned on is the crossfader and the
preview-Buttons. On my machine, in 4 and 2 deck mode without the mixer
there is some space where the mixxx logo is displayed. Would it be
possible to get the crossfader (and maybe the cue-buttons) there? That
would result in the big waveforms for me.

Another option would be to make the waveforms (nearly) screen-wide and
place pitch, EQ, Volume, Cue, on the left and right (as pitch was in
1.11). That would only leave crossfader, Master, Balance, HeadGain and
Pre/Main from the mixer-section what could eventually be placed like
proposed above where the mixxx logo is, in between of previewDeck and
maybe Mics.
[pitch/EQ/Vol Deck1] [Waveform 1] [pitch/EQ/Vol Deck2]
[--] [Waveform 3] [--]
[pitch/EQ/Vol Deck3] [Waveform 2] [pitch/EQ/Vol Deck4]
[--] [Waveform 4] [--]
[ Deck1 ]   [ Deck2 ] [ Deck3 ]  [ Deck4 ]
[PreviewDeck]   [   Crossfade/Master  ]  [Microphones]
[Samplers]
[Effects]
[Library]

I've done a quick sketch http://imgur.com/MruunAd
I've not rescaled anything except some little changes and this dosn't
get bigger than the current approach but gives much bigger waveforms.

But I am unsure if this is out of scope for LateNight and should better
be done in an other skin.

What do you think?

Cheers,
Markus

Am 08.06.2015 um 03:44 schrieb Be:
> 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 challenges would take a lot of effort that shouldn't delay 
> 1.12.
> 
> 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]
> 
> On 06/06/2015 01:04 PM, Owen Williams wrote:
>> "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.  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 save some vertical space without eliminating the whole
 mixer.

>>>
>>> Thanks:)
>>>

 On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com wrote:
> Owen,
>
> That mockup was poorly thought out re: mixer, sorry. I never use
 4
> decks :/
>
> If you aren't sick of my backseat driving yet, I just had
 another
> slightly radical idea - make LateNight's library "toggle only",
 so
> that the "big library" button becomes the only way to see it.
 This
> wouldn't inhibit my personal use style, and it would free the
> entire screen for controls.
>
> Possibly a complimentary idea is to let the search field remain
 in
> the main window, and have "big library" open with the results,
> either as you type or after hitting enter.
>
> Just for fun I've attached the Gimp .xcf layers I used for the
> mockup, which can be used in a paper-doll fashion.
>
> ~RAWRR
>
>
> On Thu, 04 Jun 2015 19:01:55 + "Owen Williams"
>  wrote:
>> 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 already impossible to
 show
>> every
>> UI element, and the skin system is not flexible enough to allow
>> for
>>

Re: [Mixxx-devel] release progress

[Be]

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 challenges would take a lot of effort that shouldn't delay 
1.12.

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]

On 06/06/2015 01:04 PM, Owen Williams wrote:
> "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.  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 save some vertical space without eliminating the whole
>>> mixer.
>>>
>>
>> Thanks:)
>>
>>>
>>> On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com wrote:
 Owen,

 That mockup was poorly thought out re: mixer, sorry. I never use
>>> 4
 decks :/

 If you aren't sick of my backseat driving yet, I just had
>>> another
 slightly radical idea - make LateNight's library "toggle only",
>>> so
 that the "big library" button becomes the only way to see it.
>>> This
 wouldn't inhibit my personal use style, and it would free the
 entire screen for controls.

 Possibly a complimentary idea is to let the search field remain
>>> in
 the main window, and have "big library" open with the results,
 either as you type or after hitting enter.

 Just for fun I've attached the Gimp .xcf layers I used for the
 mockup, which can be used in a paper-doll fashion.

 ~RAWRR


 On Thu, 04 Jun 2015 19:01:55 + "Owen Williams"
  wrote:
> 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 already impossible to
>>> show
> every
> UI element, and the skin system is not flexible enough to allow
> for
> every possible combination of elements.  So the design is a
>>> best-
> effort
> at letting people choose a good layout.  Ultimately if there's
>>> a
> skin
> design you want that isn't possible, it may be necessary to
>>> create
> a new
> skin for it.  For a while I was maintaining LateNight-Wide,
>>> which
> had
> all four decks horizontally and the waveforms at the top,
>>> spanning
> the
> width of the screen.  Maybe it's time to resurrect that.
>
> On Thu, 2015-06-04 at 18:40 +, re-cy...@hushmail.com wrote:
>> 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 all of my
>>> screens,
> I
>> don't currently have any hi-res ones.
>>
>> Related, I kind of hate being forced to choose waveforms vs.
> mixer,
>> and the loss of big waveforms in that skin to begin with. It
> seems
>> to me the reason they got 86'd was the effects bank mentioned
> above.
>>
>> Didn't file a bug because this is just my
>>> experience/preference,
>> but thought you'd want feedback.
>>
>> ~RAWRR
>>
>>
>> On Thu, 04 Jun 2015 17:53:57 + "Owen Williams"
>>  wrote:
>>> 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 you file bugs
>>> for
>>> issues you
>>> know about?  I've been fixing the LateNight bugs as they are
>>> reported
>>> and I think things are in a pretty good state there.
>>>
>>> We really need to get the Deere stuff merged in, though.
>>>
>>>
>>>
>>> -
>>> ---
> ---
>>> ---
>>> ___
>>> Get

Re: [Mixxx-devel] release progress

[Owen Williams]

"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.  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 save some vertical space without eliminating the whole
> >mixer.
> >
> 
> Thanks:)
> 
> >
> >On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com wrote:
> >> Owen,
> >>
> >> That mockup was poorly thought out re: mixer, sorry. I never use
> >4
> >> decks :/
> >>
> >> If you aren't sick of my backseat driving yet, I just had
> >another
> >> slightly radical idea - make LateNight's library "toggle only",
> >so
> >> that the "big library" button becomes the only way to see it.
> >This
> >> wouldn't inhibit my personal use style, and it would free the
> >> entire screen for controls.
> >>
> >> Possibly a complimentary idea is to let the search field remain
> >in
> >> the main window, and have "big library" open with the results,
> >> either as you type or after hitting enter.
> >>
> >> Just for fun I've attached the Gimp .xcf layers I used for the
> >> mockup, which can be used in a paper-doll fashion.
> >>
> >> ~RAWRR
> >>
> >>
> >> On Thu, 04 Jun 2015 19:01:55 + "Owen Williams"
> >>  wrote:
> >> >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 already impossible to
> >show
> >> >every
> >> >UI element, and the skin system is not flexible enough to allow
> >> >for
> >> >every possible combination of elements.  So the design is a
> >best-
> >> >effort
> >> >at letting people choose a good layout.  Ultimately if there's
> >a
> >> >skin
> >> >design you want that isn't possible, it may be necessary to
> >create
> >> >a new
> >> >skin for it.  For a while I was maintaining LateNight-Wide,
> >which
> >> >had
> >> >all four decks horizontally and the waveforms at the top,
> >spanning
> >> >the
> >> >width of the screen.  Maybe it's time to resurrect that.
> >> >
> >> >On Thu, 2015-06-04 at 18:40 +, re-cy...@hushmail.com wrote:
> >> >> 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 all of my
> >screens,
> >> >I
> >> >> don't currently have any hi-res ones.
> >> >>
> >> >> Related, I kind of hate being forced to choose waveforms vs.
> >> >mixer,
> >> >> and the loss of big waveforms in that skin to begin with. It
> >> >seems
> >> >> to me the reason they got 86'd was the effects bank mentioned
> >> >above.
> >> >>
> >> >> Didn't file a bug because this is just my
> >experience/preference,
> >> >> but thought you'd want feedback.
> >> >>
> >> >> ~RAWRR
> >> >>
> >> >>
> >> >> On Thu, 04 Jun 2015 17:53:57 + "Owen Williams"
> >> >>  wrote:
> >> >> >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 you file bugs
> >for
> >> >> >issues you
> >> >> >know about?  I've been fixing the LateNight bugs as they are
> >> >> >reported
> >> >> >and I think things are in a pretty good state there.
> >> >> >
> >> >> >We really need to get the Deere stuff merged in, though.
> >> >> >
> >> >> >
> >> >> >
> >> >> >-
> >---
> >> >---
> >> >> >---
> >> >> >___
> >> >> >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
> 
> 



--
___
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

Re: [Mixxx-devel] release progress

[re-cycle]

-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 to specifically select
>the big
>waveforms if you want them.  It also makes it possible to turn off
>the
>EQs to save some vertical space without eliminating the whole
>mixer.
>

Thanks:)

>
>On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com wrote:
>> Owen,
>>
>> That mockup was poorly thought out re: mixer, sorry. I never use
>4
>> decks :/
>>
>> If you aren't sick of my backseat driving yet, I just had
>another
>> slightly radical idea - make LateNight's library "toggle only",
>so
>> that the "big library" button becomes the only way to see it.
>This
>> wouldn't inhibit my personal use style, and it would free the
>> entire screen for controls.
>>
>> Possibly a complimentary idea is to let the search field remain
>in
>> the main window, and have "big library" open with the results,
>> either as you type or after hitting enter.
>>
>> Just for fun I've attached the Gimp .xcf layers I used for the
>> mockup, which can be used in a paper-doll fashion.
>>
>> ~RAWRR
>>
>>
>> On Thu, 04 Jun 2015 19:01:55 + "Owen Williams"
>>  wrote:
>> >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 already impossible to
>show
>> >every
>> >UI element, and the skin system is not flexible enough to allow
>> >for
>> >every possible combination of elements.  So the design is a
>best-
>> >effort
>> >at letting people choose a good layout.  Ultimately if there's
>a
>> >skin
>> >design you want that isn't possible, it may be necessary to
>create
>> >a new
>> >skin for it.  For a while I was maintaining LateNight-Wide,
>which
>> >had
>> >all four decks horizontally and the waveforms at the top,
>spanning
>> >the
>> >width of the screen.  Maybe it's time to resurrect that.
>> >
>> >On Thu, 2015-06-04 at 18:40 +, re-cy...@hushmail.com wrote:
>> >> 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 all of my
>screens,
>> >I
>> >> don't currently have any hi-res ones.
>> >>
>> >> Related, I kind of hate being forced to choose waveforms vs.
>> >mixer,
>> >> and the loss of big waveforms in that skin to begin with. It
>> >seems
>> >> to me the reason they got 86'd was the effects bank mentioned
>> >above.
>> >>
>> >> Didn't file a bug because this is just my
>experience/preference,
>> >> but thought you'd want feedback.
>> >>
>> >> ~RAWRR
>> >>
>> >>
>> >> On Thu, 04 Jun 2015 17:53:57 + "Owen Williams"
>> >>  wrote:
>> >> >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 you file bugs
>for
>> >> >issues you
>> >> >know about?  I've been fixing the LateNight bugs as they are
>> >> >reported
>> >> >and I think things are in a pretty good state there.
>> >> >
>> >> >We really need to get the Deere stuff merged in, though.
>> >> >
>> >> >
>> >> >
>> >> >-
>---
>> >---
>> >> >---
>> >> >___
>> >> >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
-BEGIN PGP SIGNATURE-
Charset: UTF8
Version: Hush 3.0
Note: This signature can be verified at https://www.hushtools.com/verify

wpwEAQMCAAYFAlVyvcQACgkQzo/Gj4mkNMzvZwP9EeXhtEakplBGvjBZ2SPrReqyCut9
3MNiuW9460reiDChudi90Qq9X37uibO9enWoODMDzt9KaoRAT11/MNoVGVmLQAdVAa7b
v9wSTFCG5NbP9Q4Y5gD4Wd020MzJE4tRNyYMMToz1x8oUz3+zai5gq/1RU6loFUL2WPT
naYhhAg=
=jJDl
-END PGP SIGNATURE-


--
___
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

Re: [Mixxx-devel] release progress

[Owen Williams]

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 save some vertical space without eliminating the whole mixer.


On Fri, 2015-06-05 at 05:16 +, re-cy...@hushmail.com wrote:
> Owen,
> 
> That mockup was poorly thought out re: mixer, sorry. I never use 4
> decks :/
> 
> If you aren't sick of my backseat driving yet, I just had another
> slightly radical idea - make LateNight's library "toggle only", so
> that the "big library" button becomes the only way to see it. This
> wouldn't inhibit my personal use style, and it would free the
> entire screen for controls.
> 
> Possibly a complimentary idea is to let the search field remain in
> the main window, and have "big library" open with the results,
> either as you type or after hitting enter.
> 
> Just for fun I've attached the Gimp .xcf layers I used for the
> mockup, which can be used in a paper-doll fashion.
> 
> ~RAWRR
> 
> 
> On Thu, 04 Jun 2015 19:01:55 + "Owen Williams"
>  wrote:
> >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 already impossible to show
> >every
> >UI element, and the skin system is not flexible enough to allow
> >for
> >every possible combination of elements.  So the design is a best-
> >effort
> >at letting people choose a good layout.  Ultimately if there's a
> >skin
> >design you want that isn't possible, it may be necessary to create
> >a new
> >skin for it.  For a while I was maintaining LateNight-Wide, which
> >had
> >all four decks horizontally and the waveforms at the top, spanning
> >the
> >width of the screen.  Maybe it's time to resurrect that.
> >
> >On Thu, 2015-06-04 at 18:40 +, re-cy...@hushmail.com wrote:
> >> 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 all of my screens,
> >I
> >> don't currently have any hi-res ones.
> >>
> >> Related, I kind of hate being forced to choose waveforms vs.
> >mixer,
> >> and the loss of big waveforms in that skin to begin with. It
> >seems
> >> to me the reason they got 86'd was the effects bank mentioned
> >above.
> >>
> >> Didn't file a bug because this is just my experience/preference,
> >> but thought you'd want feedback.
> >>
> >> ~RAWRR
> >>
> >>
> >> On Thu, 04 Jun 2015 17:53:57 + "Owen Williams"
> >>  wrote:
> >> >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 you file bugs for
> >> >issues you
> >> >know about?  I've been fixing the LateNight bugs as they are
> >> >reported
> >> >and I think things are in a pretty good state there.
> >> >
> >> >We really need to get the Deere stuff merged in, though.
> >> >
> >> >
> >> >
> >> >
> >---
> >> >---
> >> >___
> >> >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




--
___
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

Re: [Mixxx-devel] release progress

[Be]

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 that's not clear, I can hand draw a sketch and take a picture of it.

I think there's a lot of room for saving space on the deck controls. The 
big grid of numbered buttons and + & - sign buttons could be replaced by 
a two digit display with up/down arrows for doubling/halving 
loop/beatjump size, which would also map well to controllers that have 
encoders for adjusting this parameter. See 
https://bugs.launchpad.net/mixxx/+bug/1429331 . The play/pause button 
could take half the width if it was replaced by a button that toggled 
between a play icon when the track is paused and a pause icon when the 
track is playing.

Shrinking the room taken by loop controls could make room for moving the 
hotcue buttons down to the row with the loop and playback controls. The 
effect superknob may even be able to squeeze there too. This would 
eliminate the need for the row above the artist text for those who do 
not need vinyl controls showing. For those who do, those vinyl control 
buttons with text labels could take up less space if they were replaced 
by icons.

I think the whole bottom row for the decks, or at least elements of it, 
could be hideable too because a lot of controllers show those on the 
controller surface. I'd like my 1366x768 pixel laptop screen be used to 
only to show what my controller can't with knobs and backlit 
buttons--which is mostly waveforms, track information, and the 
library--so I can make those things as big and easy to see as possible.


On 06/04/2015 02:01 PM, Owen Williams wrote:
> 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 already impossible to show every
> UI element, and the skin system is not flexible enough to allow for
> every possible combination of elements.  So the design is a best-effort
> at letting people choose a good layout.  Ultimately if there's a skin
> design you want that isn't possible, it may be necessary to create a new
> skin for it.  For a while I was maintaining LateNight-Wide, which had
> all four decks horizontally and the waveforms at the top, spanning the
> width of the screen.  Maybe it's time to resurrect that.
>
> On Thu, 2015-06-04 at 18:40 +, re-cy...@hushmail.com wrote:
>> 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 all of my screens, I
>> don't currently have any hi-res ones.
>>
>> Related, I kind of hate being forced to choose waveforms vs. mixer,
>> and the loss of big waveforms in that skin to begin with. It seems
>> to me the reason they got 86'd was the effects bank mentioned above.
>>
>> Didn't file a bug because this is just my experience/preference,
>> but thought you'd want feedback.
>>
>> ~RAWRR
>>
>>
>> On Thu, 04 Jun 2015 17:53:57 + "Owen Williams"
>>  wrote:
>>> 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 you file bugs for
>>> issues you
>>> know about?  I've been fixing the LateNight bugs as they are
>>> reported
>>> and I think things are in a pretty good state there.
>>>
>>> We really need to get the Deere stuff merged in, though.
>>>
>>>
>>>
>>> ---
>>> ---
>>> ___
>>> 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
>
>
>
> --
> ___
> 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
>

--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net

Re: [Mixxx-devel] release progress

[Owen Williams]

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 already impossible to show every
UI element, and the skin system is not flexible enough to allow for
every possible combination of elements.  So the design is a best-effort
at letting people choose a good layout.  Ultimately if there's a skin
design you want that isn't possible, it may be necessary to create a new
skin for it.  For a while I was maintaining LateNight-Wide, which had
all four decks horizontally and the waveforms at the top, spanning the
width of the screen.  Maybe it's time to resurrect that.

On Thu, 2015-06-04 at 18:40 +, re-cy...@hushmail.com wrote:
> 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 all of my screens, I
> don't currently have any hi-res ones.
> 
> Related, I kind of hate being forced to choose waveforms vs. mixer,
> and the loss of big waveforms in that skin to begin with. It seems
> to me the reason they got 86'd was the effects bank mentioned above.
> 
> Didn't file a bug because this is just my experience/preference,
> but thought you'd want feedback.
> 
> ~RAWRR
> 
> 
> On Thu, 04 Jun 2015 17:53:57 + "Owen Williams"
>  wrote:
> >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 you file bugs for
> >issues you
> >know about?  I've been fixing the LateNight bugs as they are
> >reported
> >and I think things are in a pretty good state there.
> >
> >We really need to get the Deere stuff merged in, though.
> >
> >
> >
> >---
> >---
> >___
> >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



--
___
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

Re: [Mixxx-devel] release progress

[re-cycle]

-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 all of my screens, I
don't currently have any hi-res ones.

Related, I kind of hate being forced to choose waveforms vs. mixer,
and the loss of big waveforms in that skin to begin with. It seems
to me the reason they got 86'd was the effects bank mentioned above.

Didn't file a bug because this is just my experience/preference,
but thought you'd want feedback.

~RAWRR


On Thu, 04 Jun 2015 17:53:57 + "Owen Williams"
 wrote:
>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 you file bugs for
>issues you
>know about?  I've been fixing the LateNight bugs as they are
>reported
>and I think things are in a pretty good state there.
>
>We really need to get the Deere stuff merged in, though.
>
>
>
>---
>---
>___
>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
-BEGIN PGP SIGNATURE-
Charset: UTF8
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 3.0

wpwEAQMCAAYFAlVwm7MACgkQzo/Gj4mkNMwVPQP/T4GSAedflwhZVp+Bx+28dTfTXWJz
EXDacBGd7a868ARLi96XURem4fhnldjxbIrGLrklvczSlDL51YubSyoxxVfO0kqyg7zp
dx6FVwK1MJv5NVU6LzW7P93nhTA1Z+HTDLmzq0vMVFrdrS9w+3ZTBLUJrtNAEKcdz8hR
Y+swvy4=
=cRoG
-END PGP SIGNATURE-


--
___
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

Re: [Mixxx-devel] release progress

[Owen Williams]

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 you file bugs for issues you
know about?  I've been fixing the LateNight bugs as they are reported
and I think things are in a pretty good state there.

We really need to get the Deere stuff merged in, though.



--
___
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

Re: [Mixxx-devel] release progress

[Sébastien Blaisot]

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 same time
- no need to worry about files left from earlier version

Cons
- have forward and backward compatibility for preference folder
files (sqlite database) - seems complicated


I think this is the best option for now.

We already maintain backwards / forwards compatibility for the 
preferences and library SQLite database so user profiles are 
compatible across versions.


If we install to "Mixxx $VERSION" then the user won't see skins or 
other resource-path files from previous versions.


And best of all, it's only a few lines of code :).


Ok. I need to check wether it will later be possible for the user to 
uninstall each version or if there is another type of "conflict".


regards,

sb
--
___
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

Re: [Mixxx-devel] release progress

[re-cycle]

-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 2015 17:12:33 + "RJ Ryan" 
wrote:
>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
>>
>> Cons
>> - have forward and backward compatibility for preference folder
>files
>> (sqlite database) - seems complicated
>>
>>
>
>I think this is the best option for now.
>
>We already maintain backwards / forwards compatibility for the
>preferences
>and library SQLite database so user profiles are compatible across
>versions.
>
>If we install to "Mixxx $VERSION" then the user won't see skins or
>other
>resource-path files from previous versions.
>
>And best of all, it's only a few lines of code :).
-BEGIN PGP SIGNATURE-
Charset: UTF8
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 3.0

wpwEAQMCAAYFAlVwjeUACgkQzo/Gj4mkNMzTPQP+NGpvC9i2uLEeiN2vCAOzeYD+IeiO
F1m8XcZewDdz6EhoAAvdriv9CfMiYsiAgKT9cTkUHvADibXbMhB74JMxFHPWM6t1vdgy
y8gS+lBmByZinQc4nvAbErWzSEWcBmqdN+fNzMVTkLT29Y6ROm2s697l8+67CVIls7Kg
/sHgGrQ=
=sCEp
-END PGP SIGNATURE-


--
___
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

Re: [Mixxx-devel] release progress

[RJ Ryan]

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
>
> Cons
> - have forward and backward compatibility for preference folder files
> (sqlite database) - seems complicated
>
>

I think this is the best option for now.

We already maintain backwards / forwards compatibility for the preferences
and library SQLite database so user profiles are compatible across versions.

If we install to "Mixxx $VERSION" then the user won't see skins or other
resource-path files from previous versions.

And best of all, it's only a few lines of code :).
--
___
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

Re: [Mixxx-devel] release progress

[Sébastien Blaisot]

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:
- When installing 1.12 on top of a previous version installation, old
files from previous version are left. so skins from 1.11 shows up next
to new resizable skins and uninstall entry in the program
uninstallation
control panel shows up "Mixxx 1.11" as well as "Mixxx 1.12". selecting
one of them, regardless of which one, removes the Mixxx
installation and
let the other entry unusable. At least we should detect former
installation and deny installation until the previous version is
uninstalled or (best) add an upgrade path to the installer.
I didn't try, but I think we also have an issue when installing Mixxx
64bits on top of Mixxx 32bits or vice-versa (different installation
directories under windows).

Hm, yes those aren't ideal. I wonder if a quick fix would be to 
install to a "Mixxx $VERSION" folder instead of "c:\Program 
Files\Mixxx"? It wouldn't fix the 32-bit/64-bit issue but it should be 
enough to get us through this release until we can switch to Wix or 
something better.


Hi,
I've thought a little about it  and came to the conclusion that we have 
no easy workaround.

Situation (https://bugs.launchpad.net/mixxx/+bug/1457618):
Installing Mixxx 1.12 on top of Mixxx 1.11 (without uninstalling 1.11 
before) leave 1.11 files, especially 1.11 fixed skins, and you end up 
with a 1.12 Mixxx version with a mix of new and older skins. Really not 
ideal.
Uninstall entry is not cleaned either, and you end up with two Mixxx 
uninstall entries in programs control panel, each one removing mixxx and 
leaving the other entry non functionnal

What we can do :
1) Have a proper installer with clean upgrade path and modified files 
preservation


Pros
- Yeah, this is the cleaner solution

Cons
- This is a huge refactoring of installer, with probably a switch to 
Wix, and is not compatible with 1.12 release target

2) detect if mixxx is already installed and forbid installation if it is
We must define what we call "already installed". 2bis will focus on 
"installed == installation dir not empty". not ideal. Seems easier with 
$INSTDIR\mixxx.exe detection. not perfect but doable.


Pros
- clearly avoids two installation mangle each other, even with 32 and 64 
bits


Cons
- Is this at least doable with NSIS ? Not sure
2bis) after installation directory selection in installer, refuse to go 
further if directory is not empty


Pros
- No older files
- seems doable with NSIS : http://nsis.sourceforge.net/Check_if_dir_is_empty

Cons
- Due to the bug lp:1457624 it will need user to manually empty their 
directory in the 1.11->1.12 upgrade path. Is it acceptable or should we 
wait for 1.12 release (which will clean all files on uninstall) and make 
it land in next version. But if we wait, that doesn't solve the 
immediate problem :(


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

Cons
- have forward and backward compatibility for preference folder files 
(sqlite database) - seems complicated


4) "uninstall & cleanup" older version before installation

Pros
- solve the immediate problem

Cons
- a bit risky as it can delete user's files without notice. I don't know 
if we can detect and add a warning before removing file with a "cancel" 
button to let a chance to backup files.


My preference go to solution 2 with looking for mixxx.exe in the 
installation directory and stopping installation if found.

What do you think of this ?

sb
--
___
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

Re: [Mixxx-devel] release progress

[Owen Williams]

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
> 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 changes that requires a
> longer beta phase.
> 
> 
> 
> Kind regards, 
> 
> 
> Daniel 
> 
> 
>  
> 
> 
>  
> 
> 
> 2015-06-03 15:35 GMT+02:00 RJ Ryan :
> 
> 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 an another beta
> after the API is stable. RJ has added +1
> 
> This was also a good solution to me. 
> 
> So lets make it happen and let us not delay the
> important mp3 quality fixes by an other year. 
> 
> 
> 
> 
> Neither Owen or I said that. Owen said:
> 
> 
> > based on the risks and benefits and our experience with long
> debugging
> > periods after major feature merges, the prudent choice is to
> keep the
> > current soundsource API for the 1.12 release.  Once it's out
> the door,
> > then we can immediately look at merging the new API.  And as
> far as I'm
> > concerned, as soon as it's stable, we can do another beta
> right away.
> 
> 
> The "another beta right away" would be 1.13 beta. 1.13 will be
> a short cycle with cleanup, bug fixes and no new major
> features (since I don't see any that will be ready soon). I'm
> definitely interested in releasing 1.13 soon after 1.12.0.
> There's no reason it has to be a "SS refactor" release though.
> It can contain other features and fixes which is why we're
> going to keep it in master and cut a 1.13 release branch when
> other fixes have made it in.
> 
> 
> Daniel -- I don't have time or energy to continue arguing
> about this. The 1.13.0 release will be just like any other and
> we will try to get it out a month or two after the 1.12.0
> release. That's my decision and I won't debate it any
> further. 
> 
> 
> thanks,
> RJ
> 
> 
> 
> As already discussed, there are actually some
> important reasons to merge is soon: 
> 
> 
> Mixxx main propose is to play mp3 in time and sample
> accurate. 
> 
> The current master does not fulfill this requirement
> in any case.
> 
> 
> What is the worth of the new shiny sync feature if
> only the visual beatgrid is in sync after a backward
> seek? 
> 
> This most important issue is fixed in:
> https://bugs.launchpad.net/mixxx/+bug/1407394
> 
> 
> I really do not want to read a MIxxx review like that:
> "Mixxx: nice new features but still not usable for
> auto beat match" 
> 
>  
> 
> I have grouped all the important fixes under the
> "soundsource" tag:
> https://bugs.launchpad.net/mixxx/+bugs?field.tag=soundsource
> 
> 
> Decoding Quality:
> 
> #1407394 waveform and transport out of sync for mp3
> #580235 Stuttering at start of VBR MP3 playback 
> 
> #1156569 Change Soundsource API to reading float
> samples
> 
> 
> Bad file issues:
> 
> #178 mp3: files with changing bitrate are playing
> heavily distorted
> #1408100 soundsourcemp3 is clamping 
> 
> #1446931 MP3 files with varying sample rate are not
> supported! on Win7, NewSound

Re: [Mixxx-devel] release progress

[Daniel Schürmann]

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 changes that requires a longer beta
phase.

Kind regards,

Daniel






2015-06-03 15:35 GMT+02:00 RJ Ryan :

>
> 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 an another beta after the API is
>> stable. RJ has added +1
>> This was also a good solution to me.
>> So lets make it happen and let us not delay the important mp3 quality
>> fixes by an other year.
>>
>>
> Neither Owen or I said that. Owen said:
>
> > based on the risks and benefits and our experience with long debugging
> > periods after major feature merges, the prudent choice is to keep the
> > current soundsource API for the 1.12 release.  Once it's out the door,
> > then we can immediately look at merging the new API.  And as far as I'm
> > concerned, as soon as it's stable, we can do another beta right away.
>
> The "another beta right away" would be 1.13 beta. 1.13 will be a short
> cycle with cleanup, bug fixes and no new major features (since I don't see
> any that will be ready soon). I'm definitely interested in releasing 1.13
> soon after 1.12.0. There's no reason it has to be a "SS refactor" release
> though. It can contain other features and fixes which is why we're going to
> keep it in master and cut a 1.13 release branch when other fixes have made
> it in.
>
> Daniel -- I don't have time or energy to continue arguing about this. The
> 1.13.0 release will be just like any other and we will try to get it out a
> month or two after the 1.12.0 release. That's my decision and I won't
> debate it any further.
>
> thanks,
> RJ
>
> As already discussed, there are actually some important reasons to merge
>> is soon:
>>
>> Mixxx main propose is to play mp3 in time and sample accurate.
>> The current master does not fulfill this requirement in any case.
>>
>> What is the worth of the new shiny sync feature if only the visual
>> beatgrid is in sync after a backward seek?
>> This most important issue is fixed in:
>> https://bugs.launchpad.net/mixxx/+bug/1407394
>>
>> I really do not want to read a MIxxx review like that: "Mixxx: nice new
>> features but still not usable for auto beat match"
>>
>> I have grouped all the important fixes under the "soundsource" tag:
>> https://bugs.launchpad.net/mixxx/+bugs?field.tag=soundsource
>>
>>   Decoding Quality:
>> #1407394 waveform and transport out of sync for mp3
>> 
>> #580235 Stuttering at start of VBR MP3 playback
>> 
>>#1156569 Change Soundsource API to reading float samples
>> 
>>
>> Bad file issues:
>> #178 mp3: files with changing bitrate are playing heavily distorted
>> 
>> #1408100 soundsourcemp3 is clamping
>> 
>>#1446931 MP3 files with varying sample rate are not supported! on
>> Win7, NewSoundSourceAPI 
>>   #1448224 MP3: Varying number of channels within a file not supported
>> 
>> #1405832 wrong mp3 track duration and wrong crossfader time
>> 
>> #1450893 some MP3 could not loaded
>> 
>>
>> Other:
>>
>>   #697902 Strange Asian Characters in File Browser
>> 
>>   #726222 Flac files in library don't work well
>> 
>>
>>
>>   #1418083 Support -MM-DD + and any other string for year column
>> 
>>
>> @Uwe: Please add bugs the, I have missed.
>>
>> All reasons for a c++11 refactoring or switch to Qt5 are minor compares
>> to this.
>> So it seams to be reasonable to fix the pending issues of the list above
>> plus other important 1,12 fixes,
>> without risk regressions by other feature branches or refactoring.
>>
>>
>> > Why would we cut a release branch for 1.13.0 when we haven't even
>> released 1.12.0?
>>
>> Because we do not want to stop merging feature branches to master.
>> I if we have a common commitment not to merge features that will delay
>> the SS release
>> we can continue with the current situation. But than we will loo

Re: [Mixxx-devel] release progress

[RJ Ryan]

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 all,
>
> I agree with your blockers. In my opinion, there are also two more
> blockers.
>
> First, we should not sheep Mixxx 1.12 with controller mapping that use
> controls that are deprecated in 1.12. This shows an ugly warning box to
> the user when selecting such a mapping.
>

Oh yea, this happens all the time with the flanger controls. We could
either hack it by making an ignore list or we could try to connect the old
flanger controls to the new effects system. There isn't really a clear way
they should be connected that would make sense so I'm in favor of a hack.


>
> 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:
> - When installing 1.12 on top of a previous version installation, old
> files from previous version are left. so skins from 1.11 shows up next
> to new resizable skins and uninstall entry in the program uninstallation
> control panel shows up "Mixxx 1.11" as well as "Mixxx 1.12". selecting
> one of them, regardless of which one, removes the Mixxx installation and
> let the other entry unusable. At least we should detect former
> installation and deny installation until the previous version is
> uninstalled or (best) add an upgrade path to the installer.
> I didn't try, but I think we also have an issue when installing Mixxx
> 64bits on top of Mixxx 32bits or vice-versa (different installation
> directories under windows).
>

Hm, yes those aren't ideal. I wonder if a quick fix would be to install to
a "Mixxx $VERSION" folder instead of "c:\Program Files\Mixxx"? It wouldn't
fix the 32-bit/64-bit issue but it should be enough to get us through this
release until we can switch to Wix or something better.



>
> - Uninstalling Mixxx leave files behind. Especially some, but not all,
> controller mapping in the Mixxx installation directory. on 177 files
> installed in the controller directory, 77 are removed and 100 are left
> behind. This is not understandable for users. We should either remove
> them all or none. I understand some users can expect that changed/tuned
> controller mapping files are not removed,


I agree and I was mistaken when I commented on
https://bugs.launchpad.net/bugs/1457624 -- sorry about that! Left a comment
there.



> but the Mixxx preference
> directory is the place to install custom mapping, not the mixxx
> installation directory (at least in my opinion).


Yea, this is definitely the ideal. We haven't been good about this in the
past (suggesting to users to drop them in the Program Files directory). I
think part of the reason for that was that it's sometimes hard to instruct
to a Windows user where to go to drop the presets. 1.12.0 has buttons in
the MIDI preferences to open the preferences presets folder directly which
should make supporting these users easier.


> We must also be
> consistent across OSes on this behalf. Are modified controller mapping
> files left when purging package on ubuntu ? what happens on MacOSX when
> uninstalling ?
>

On OSX the situation is better due to it's "bundle" concept. You can't
install an app over another one. They are separate "bundles" in the
/Applications directory. There also isn't an installer or uninstaller --
the user drags the "bundle" from the install media into their Applications
folder (or wherever they want to store the app). It's not easy for a
non-developer-savvy user to get into the contents of the bundle or edit it
so there's also not the problem of users putting presets in the application
bundle instead of their profile presets folder.

And the Linux package managers typically do something sensible for us --
installing the files to /usr/share/mixxx as read-only and not letting the
user concurrently install two mixxx packages.


>
> Regards,
>
> sb
>
>
>
> --
> ___
> 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
>
--
___
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

Re: [Mixxx-devel] release progress

[RJ Ryan]

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 an another beta after the API is
> stable. RJ has added +1
> This was also a good solution to me.
> So lets make it happen and let us not delay the important mp3 quality
> fixes by an other year.
>
>
Neither Owen or I said that. Owen said:

> based on the risks and benefits and our experience with long debugging
> periods after major feature merges, the prudent choice is to keep the
> current soundsource API for the 1.12 release.  Once it's out the door,
> then we can immediately look at merging the new API.  And as far as I'm
> concerned, as soon as it's stable, we can do another beta right away.

The "another beta right away" would be 1.13 beta. 1.13 will be a short
cycle with cleanup, bug fixes and no new major features (since I don't see
any that will be ready soon). I'm definitely interested in releasing 1.13
soon after 1.12.0. There's no reason it has to be a "SS refactor" release
though. It can contain other features and fixes which is why we're going to
keep it in master and cut a 1.13 release branch when other fixes have made
it in.

Daniel -- I don't have time or energy to continue arguing about this. The
1.13.0 release will be just like any other and we will try to get it out a
month or two after the 1.12.0 release. That's my decision and I won't
debate it any further.

thanks,
RJ

As already discussed, there are actually some important reasons to merge is
> soon:
>
> Mixxx main propose is to play mp3 in time and sample accurate.
> The current master does not fulfill this requirement in any case.
>
> What is the worth of the new shiny sync feature if only the visual
> beatgrid is in sync after a backward seek?
> This most important issue is fixed in:
> https://bugs.launchpad.net/mixxx/+bug/1407394
>
> I really do not want to read a MIxxx review like that: "Mixxx: nice new
> features but still not usable for auto beat match"
>
> I have grouped all the important fixes under the "soundsource" tag:
> https://bugs.launchpad.net/mixxx/+bugs?field.tag=soundsource
>
>   Decoding Quality:
> #1407394 waveform and transport out of sync for mp3
> 
> #580235 Stuttering at start of VBR MP3 playback
> 
>#1156569 Change Soundsource API to reading float samples
> 
>
> Bad file issues:
> #178 mp3: files with changing bitrate are playing heavily distorted
> 
> #1408100 soundsourcemp3 is clamping
> 
>#1446931 MP3 files with varying sample rate are not supported! on
> Win7, NewSoundSourceAPI 
>   #1448224 MP3: Varying number of channels within a file not supported
> 
> #1405832 wrong mp3 track duration and wrong crossfader time
> 
> #1450893 some MP3 could not loaded
> 
>
> Other:
>
>   #697902 Strange Asian Characters in File Browser
> 
>   #726222 Flac files in library don't work well
> 
>
>
>   #1418083 Support -MM-DD + and any other string for year column
> 
>
> @Uwe: Please add bugs the, I have missed.
>
> All reasons for a c++11 refactoring or switch to Qt5 are minor compares to
> this.
> So it seams to be reasonable to fix the pending issues of the list above
> plus other important 1,12 fixes,
> without risk regressions by other feature branches or refactoring.
>
>
> > Why would we cut a release branch for 1.13.0 when we haven't even
> released 1.12.0?
>
> Because we do not want to stop merging feature branches to master.
> I if we have a common commitment not to merge features that will delay the
> SS release
> we can continue with the current situation. But than we will loose the
> build server to verify
> the new features.
>
> I have seen the build server is working gain for master. Cant we declare
> the current master build
> as next beta? This way we can announce a beta phase just after releasing
> 1.12.0
>
> I have also thought about the Version schema. What about just ditching the
> point version
> like Firefox and Chrome? This way we are able to publish a beta at the
> same time we publish a release
>
> Any other ideas?
>
> Kind regards,
>
> Daniel
>
>
>
>
> 2015-06-03 2:16 GMT+02:00 Sean M. P

Re: [Mixxx-devel] release progress

[Daniel Schürmann]

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 good solution to me.
So lets make it happen and let us not delay the important mp3 quality fixes
by an other year.

As already discussed, there are actually some important reasons to merge is
soon:

Mixxx main propose is to play mp3 in time and sample accurate.
The current master does not fulfill this requirement in any case.

What is the worth of the new shiny sync feature if only the visual beatgrid
is in sync after a backward seek?
This most important issue is fixed in:
https://bugs.launchpad.net/mixxx/+bug/1407394

I really do not want to read a MIxxx review like that: "Mixxx: nice new
features but still not usable for auto beat match"

I have grouped all the important fixes under the "soundsource" tag:
https://bugs.launchpad.net/mixxx/+bugs?field.tag=soundsource

  Decoding Quality:
#1407394 waveform and transport out of sync for mp3

#580235 Stuttering at start of VBR MP3 playback

   #1156569 Change Soundsource API to reading float samples


Bad file issues:
#178 mp3: files with changing bitrate are playing heavily distorted

#1408100 soundsourcemp3 is clamping

   #1446931 MP3 files with varying sample rate are not supported! on Win7,
NewSoundSourceAPI 
  #1448224 MP3: Varying number of channels within a file not supported

#1405832 wrong mp3 track duration and wrong crossfader time

#1450893 some MP3 could not loaded


Other:
   
  #697902 Strange Asian Characters in File Browser

  #726222 Flac files in library don't work well

   
   
  #1418083 Support -MM-DD + and any other string for year column


@Uwe: Please add bugs the, I have missed.

All reasons for a c++11 refactoring or switch to Qt5 are minor compares to
this.
So it seams to be reasonable to fix the pending issues of the list above
plus other important 1,12 fixes,
without risk regressions by other feature branches or refactoring.


> Why would we cut a release branch for 1.13.0 when we haven't even
released 1.12.0?

Because we do not want to stop merging feature branches to master.
I if we have a common commitment not to merge features that will delay the
SS release
we can continue with the current situation. But than we will loose the
build server to verify
the new features.

I have seen the build server is working gain for master. Cant we declare
the current master build
as next beta? This way we can announce a beta phase just after releasing
1.12.0

I have also thought about the Version schema. What about just ditching the
point version
like Firefox and Chrome? This way we are able to publish a beta at the same
time we publish a release

Any other ideas?

Kind regards,

Daniel




2015-06-03 2:16 GMT+02:00 Sean M. Pappalardo - D.J. Pegasus <
spappala...@mixxx.org>:

>
>
> 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 upgrades gracefully with less effort and offer
> more automation of which files to remove. Plus we can probably integrate
> WiX with SCons in such a way that SCons generates it for us as a build
> target.
>
> Sincerely,
> Sean M. Pappalardo
> "D.J. Pegasus"
> Mixxx Developer - Controller Specialist
>
>
>
> --
>
> ___
> 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
>
--
___
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

Re: [Mixxx-devel] release progress

[Sean M. Pappalardo - D.J. Pegasus]

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 upgrades gracefully with less effort and offer 
more automation of which files to remove. Plus we can probably integrate 
WiX with SCons in such a way that SCons generates it for us as a build 
target.


Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
___
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

Re: [Mixxx-devel] release progress

[Sébastien Blaisot]

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 blockers.

First, we should not sheep Mixxx 1.12 with controller mapping that use 
controls that are deprecated in 1.12. This shows an ugly warning box to 
the user when selecting such a mapping.

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:
- When installing 1.12 on top of a previous version installation, old 
files from previous version are left. so skins from 1.11 shows up next 
to new resizable skins and uninstall entry in the program uninstallation 
control panel shows up "Mixxx 1.11" as well as "Mixxx 1.12". selecting 
one of them, regardless of which one, removes the Mixxx installation and 
let the other entry unusable. At least we should detect former 
installation and deny installation until the previous version is 
uninstalled or (best) add an upgrade path to the installer.
I didn't try, but I think we also have an issue when installing Mixxx 
64bits on top of Mixxx 32bits or vice-versa (different installation 
directories under windows).

- Uninstalling Mixxx leave files behind. Especially some, but not all, 
controller mapping in the Mixxx installation directory. on 177 files 
installed in the controller directory, 77 are removed and 100 are left 
behind. This is not understandable for users. We should either remove 
them all or none. I understand some users can expect that changed/tuned 
controller mapping files are not removed, but the Mixxx preference 
directory is the place to install custom mapping, not the mixxx 
installation directory (at least in my opinion). We must also be 
consistent across OSes on this behalf. Are modified controller mapping 
files left when purging package on ubuntu ? what happens on MacOSX when 
uninstalling ?

Regards,

sb


--
___
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

Re: [Mixxx-devel] release progress

[Daniel Schürmann]

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 from the effected systems.

> Adding a 1.12.1 will likely cause more bugs in the wild than it fixes 
and that's not what users will expect from a point release.


The SS branch is in master since a while and I have a very good feeling 
for the quality but we do not know.
On the other hand, if we add Qt 5 and c++11 refactoring and upcomming 
and pending feature branches,
we will add a risk of an additional "ton" of bug and not the least a 
risk of an other year delay. So if we want an

SS release soon we should not do this.

It is OK for me to keep the 1.12 branch open for minor fixes towards a 
possible 1.12.1 version without the SS changes.


IMHO we need a separate branch for releasing the SS fixes. If it is 
called 1.12.1 1.13 or 1.12.2 does not matters to me.

The only thing that matters is that we can put it in a alpha state now.
This will us give the time we need to lift it up to release state, 
without blocking any other improvements for master.


I think it will not be a problem to release a "1.13.0 SS only" 
independent from a 1.12.1.

Is such a strategy OK to you?

What do the others think?

Kind regards,

Daniel








Am 02.06.2015 um 21:29 schrieb RJ Ryan:



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 the blocking items are:

* critical Windows bugs
* skin polish (Jus has an active Deere branch)
* website updates (I'm working on this)
* manual updates

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.


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.


>
> 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 on windows are also
bad, do
> others on the list share this experience?

I have problems with the cover-art feature using the release
builds that
we distribute. But I haven't been able to debug this because I can't
reproduce it in with my own builds. Do other people have problems with
the covers?

I haven't done much testing otherwise.

> For me those issues actually block a release.
>
> Unfortunately there is no notable progress on these critical issues.
> We need help! Is there anyone with a Windows build environment
on the
> list who can reproduce one of the critical bugs?
>
>
> # New Soundsource API #
>
> The master branch, including the mp3 seek and click issues and
floating
> point samples has reached a stable state.
> As discussed before it is planed to release a 1.12.1 or whatever
> version, including these
> important fixes. Since this will be a bugfix release, it should not
> contain new features,
> or other risky changes.
>
> We have also some pending pull request on Github, which may not
fit to
> such a 1.12.1 target.
> So I think we should branch a 1.12.1 branch right now.
> IMHO we can enter 1.12.1 beta stage after merging Uwes "SoundSource
> Plugin API: Version 8" branch.
> A release can be scheduled ~ two month after 1.12.0 to allow to
include
> add-hock fixes.
>


A 1.12.1 release is for fixing critical bugs that come up post-release 
and it will be released out of the 1.12 branch. If the number of bugs 
we hit right away after the SS-refactor merge is any indication there 
are tons of bugs we haven't yet hit out in the wild. Adding a 1.12.1 
will likely cause more bugs in the wild than it fixes and that's not 
what users will expect from a point release.


I totally understand wanting to get master into a release ASAP though. 
1.13.0 will come soon after 1.12.0. It will probably be a clean-up / 
stability improvements / refactoring release so it makes sense to 
include the SS refactor there along with other changes (c++11 
refactorings, Qt5 support).


It's fine to start merging the feature branches that are ready to 
master -- they can be part of 1.13.0.


> What do you think?
>
> Kind regards,
>
> Daniel
>
>
>

--
> One dashboard for servers and applications across
Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50

Re: [Mixxx-devel] release progress

[RJ Ryan]

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 build server as well? This way we are able to get
> more infos directly from the effected systems.
>

Yea, PDB bundling is on my list as well.


>
> > Adding a 1.12.1 will likely cause more bugs in the wild than it fixes
> and that's not what users will expect from a point release.
>
> The SS branch is in master since a while and I have a very good feeling
> for the quality but we do not know.
> On the other hand, if we add Qt 5 and c++11 refactoring and upcomming and
> pending feature branches,
> we will add a risk of an additional "ton" of bug and not the least a risk
> of an other year delay. So if we want an
> SS release soon we should not do this.
>

qt5 support has been in for nearly a year. The transition won't be too bad
there.


> It is OK for me to keep the 1.12 branch open for minor fixes towards a
> possible 1.12.1 version without the SS changes.
>
> IMHO we need a separate branch for releasing the SS fixes. If it is called
> 1.12.1 1.13 or 1.12.2 does not matters to me.
> The only thing that matters is that we can put it in a alpha state now.
> This will us give the time we need to lift it up to release state, without
> blocking any other improvements for master.
>

We already have master builds and the nightly PPA for this purpose.



> I think it will not be a problem to release a "1.13.0 SS only" independent
> from a 1.12.1.
> Is such a strategy OK to you?
>

Why would we cut a release branch for 1.13.0 when we haven't even released
1.12.0?

There's a lot of overhead involved in doing a release. There is no
compelling reason why SS-refactor needs to be in a release all of its own
other than that you want it to be released ASAP.

RJ


> What do the others think?
>
> Kind regards,
>
> Daniel
>
>
>
>
>
>
>
>
> Am 02.06.2015 um 21:29 schrieb RJ Ryan:
>
>
>
> 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 the blocking items are:
>
>  * critical Windows bugs
> * skin polish (Jus has an active Deere branch)
> * website updates (I'm working on this)
> * manual updates
>
>  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.
>
>  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.
>
>
>> >
>> > 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 on windows are also bad, do
>> > others on the list share this experience?
>>
>> I have problems with the cover-art feature using the release builds that
>> we distribute. But I haven't been able to debug this because I can't
>> reproduce it in with my own builds. Do other people have problems with
>> the covers?
>>
>> I haven't done much testing otherwise.
>>
>> > For me those issues actually block a release.
>> >
>> > Unfortunately there is no notable progress on these critical issues.
>> > We need help! Is there anyone with a Windows build environment on the
>> > list who can reproduce one of the critical bugs?
>> >
>> >
>> > # New Soundsource API #
>> >
>> > The master branch, including the mp3 seek and click issues and floating
>> > point samples has reached a stable state.
>> > As discussed before it is planed to release a 1.12.1 or whatever
>> > version, including these
>> > important fixes. Since this will be a bugfix release, it should not
>> > contain new features,
>> > or other risky changes.
>> >
>> > We have also some pending pull request on Github, which may not fit to
>> > such a 1.12.1 target.
>> > So I think we should branch a 1.12.1 branch right now.
>> > IMHO we can enter 1.12.1 beta stage after merging Uwes "SoundSource
>> > Plugin API: Version 8" branch.
>> > A release can be scheduled ~ two month after 1.12.0 to allow to include
>> > add-hock fixes.
>> >
>>
>
>  A 1.12.1 release is for fixing critical bugs that come up post-release
> and it will be released out of the 1.12 branch. If the number of bugs we
> hit right away after the SS-refactor merge is any indication there are tons
> of bugs we haven't yet hit out in the wild. Adding a 1.12.1 will likely
> cause more bugs in the wild than it fixes and that's not what users will
> expect from a point release.
>
>  I totally understand wanting to get master into a release ASAP though.
> 1.13.0 will come soon after 1.12.0. It will probably be a clean-up /
> stability improveme

Re: [Mixxx-devel] release progress

[RJ Ryan]

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 the blocking items are:

* critical Windows bugs
* skin polish (Jus has an active Deere branch)
* website updates (I'm working on this)
* manual updates

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.

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.


> >
> > 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 on windows are also bad, do
> > others on the list share this experience?
>
> I have problems with the cover-art feature using the release builds that
> we distribute. But I haven't been able to debug this because I can't
> reproduce it in with my own builds. Do other people have problems with
> the covers?
>
> I haven't done much testing otherwise.
>
> > For me those issues actually block a release.
> >
> > Unfortunately there is no notable progress on these critical issues.
> > We need help! Is there anyone with a Windows build environment on the
> > list who can reproduce one of the critical bugs?
> >
> >
> > # New Soundsource API #
> >
> > The master branch, including the mp3 seek and click issues and floating
> > point samples has reached a stable state.
> > As discussed before it is planed to release a 1.12.1 or whatever
> > version, including these
> > important fixes. Since this will be a bugfix release, it should not
> > contain new features,
> > or other risky changes.
> >
> > We have also some pending pull request on Github, which may not fit to
> > such a 1.12.1 target.
> > So I think we should branch a 1.12.1 branch right now.
> > IMHO we can enter 1.12.1 beta stage after merging Uwes "SoundSource
> > Plugin API: Version 8" branch.
> > A release can be scheduled ~ two month after 1.12.0 to allow to include
> > add-hock fixes.
> >
>

A 1.12.1 release is for fixing critical bugs that come up post-release and
it will be released out of the 1.12 branch. If the number of bugs we hit
right away after the SS-refactor merge is any indication there are tons of
bugs we haven't yet hit out in the wild. Adding a 1.12.1 will likely cause
more bugs in the wild than it fixes and that's not what users will expect
from a point release.

I totally understand wanting to get master into a release ASAP though.
1.13.0 will come soon after 1.12.0. It will probably be a clean-up /
stability improvements / refactoring release so it makes sense to include
the SS refactor there along with other changes (c++11 refactorings, Qt5
support).

It's fine to start merging the feature branches that are ready to master --
they can be part of 1.13.0.

> What do you think?
> >
> > Kind regards,
> >
> > Daniel
> >
> >
> >
> --
> > One dashboard for servers and applications across Physical-Virtual-Cloud
> > Widest out-of-the-box monitoring support with 50+ applications
> > Performance metrics, stats and reports that give you Actionable Insights
> > Deep dive visibility with transaction tracing using APM Insight.
> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> >
> >
> >
> > ___
> > 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
> >
>
>
> --
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> ___
> 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
>
--
___
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

Re: [Mixxx-devel] release progress

[Max Linke]

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 happen on windows only.
> My overall test experiences running Mixxx on windows are also bad, do
> others on the list share this experience?

I have problems with the cover-art feature using the release builds that 
we distribute. But I haven't been able to debug this because I can't 
reproduce it in with my own builds. Do other people have problems with 
the covers?

I haven't done much testing otherwise.

> For me those issues actually block a release.
>
> Unfortunately there is no notable progress on these critical issues.
> We need help! Is there anyone with a Windows build environment on the
> list who can reproduce one of the critical bugs?
>
>
> # New Soundsource API #
>
> The master branch, including the mp3 seek and click issues and floating
> point samples has reached a stable state.
> As discussed before it is planed to release a 1.12.1 or whatever
> version, including these
> important fixes. Since this will be a bugfix release, it should not
> contain new features,
> or other risky changes.
>
> We have also some pending pull request on Github, which may not fit to
> such a 1.12.1 target.
> So I think we should branch a 1.12.1 branch right now.
> IMHO we can enter 1.12.1 beta stage after merging Uwes "SoundSource
> Plugin API: Version 8" branch.
> A release can be scheduled ~ two month after 1.12.0 to allow to include
> add-hock fixes.
>
> What do you think?
>
> Kind regards,
>
> Daniel
>
>
> --
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
>
> ___
> 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
>

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
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

Re: [Mixxx-devel] release progress

[Owen Williams]

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
we can get windows to the place where linux and mac are, I'd be ok with
cutting the release.

On Wed, 2015-05-20 at 12:40 +0200, 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 happen on windows only.
> My overall test experiences running Mixxx on windows are also bad, do
> others on the list share this experience?
> For me those issues actually block a release. 
> 
> Unfortunately there is no notable progress on these critical issues.  
> We need help! Is there anyone with a Windows build environment on the
> list who can reproduce one of the critical bugs? 
> 




--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
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

[Mixxx-devel] release progress

[Daniel Schürmann]

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 on windows are also bad, do
others on the list share this experience?
For me those issues actually block a release.

Unfortunately there is no notable progress on these critical issues.
We need help! Is there anyone with a Windows build environment on the list
who can reproduce one of the critical bugs?


# New Soundsource API #

The master branch, including the mp3 seek and click issues and floating
point samples has reached a stable state.
As discussed before it is planed to release a 1.12.1 or whatever version,
including these
important fixes. Since this will be a bugfix release, it should not contain
new features,
or other risky changes.

We have also some pending pull request on Github, which may not fit to such
a 1.12.1 target.
So I think we should branch a 1.12.1 branch right now.
IMHO we can enter 1.12.1 beta stage after merging Uwes "SoundSource Plugin
API: Version 8" branch.
A release can be scheduled ~ two month after 1.12.0 to allow to include
add-hock fixes.

What do you think?

Kind regards,

Daniel
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
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