from:"Sébastien BLAISOT"

Le 02/01/2016 12:24, zezinho a écrit :
> Anyway, it is ready for Mageia 6 :
>
> http://madb.mageia.org/package/show/source/1/application/0/release/cauldron/name/mixxx

Thanks.

However, it seems that the screenshots are from an older version.
Is it possible to update them ?

Thanks for your work to package Mixxx for Mageia

Best 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] TESTERS NEEDED: New windows installer



ok, I've done some more work on the wix installer.

Can you test with this version :
https://owncloud.blaisot.org/index.php/s/GXkJvExdwTOe0qT

It's not really polished, the main issue is that it forbid you to 
install if it finds an older installation to avoid the conflicts you've 
seen on former test.


I built english and french installers, but I will need more 
translations. Can somebody explain me how to extract strings and make a 
file suitable for transifex ?

We can maybe publish it to transifex as a new resource ?

Every feedback is welcome, I'll try to do my best to address them.

Thanks in advance,

Sébastien

Le 19/11/2015 10:56, Sébastien BLAISOT a écrit :






2015-11-19 1:14 GMT+01:00 Sébastien Blaisot <mi...@blaisot.org 
<mailto:mi...@blaisot.org>>:


Hi all,

I finally got wix to build an installer package for Mixxx and
with the
help of Pegasus, I have my build env fixed.

So here you will find installer for 2.0-rc1-1.12-git5627 :
https://owncloud.blaisot.org/index.php/s/nyEDsb0vEV7aa1m

There are 6 files.
The exe ones are old installers built with NSIS (same as what you can
download from the mixxx site except it was built on my own build env)
The MSI ones are new installers built with wix (a preview of what
could
be the future installer)

MSI installer are built in 2 languages (french and english, no other
translation made at that time) and 2 bitwidth (32 and 64 bits)

What I need is testers to tell me what needs to be polished in
the MSI
installers.

I need you to test all use-cases that you can have in mind, even
crazy
ones like installing 64 bits mixxx on a 32 bits system, installing on
top of a previous installation and so on.
And also testing bare-metal install on a computer without mixxx
installed, uninstalling (is there something left behind ?).

I also need to test it on older versions of windows, so if you
have an
old windows XP or even pre-XP system, please let me know how the
installer works on that system.

please let me know also what you think of this new installer.

These new installer won't be ready for Mixxx 2.0, but I need you
to test
it with Mixxx 2.0 because it will let me implement and test the
upgrade
path when time will come for a 2.1, starting from an older version.

Thanks in advance,

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] build on linux

Le 02/01/2016 17:03, RJ Ryan a écrit :
> Hm LIBDIR=/usr/lib64 isn't quite right since we join the prefix with 
> it so that would result in /usr/usr/lib64 

hummm, by default, prefix=/usr/local
https://github.com/mixxxdj/mixxx/blob/1.12/build/mixxx.py#L383

we use /usr in debian build rules
https://github.com/mixxxdj/mixxx/blob/1.12/build/debian/rules#L43

so it would, by default, result to /usr/local/usr/lib64 if I understand 
correctly.

so I think it should be
LIBDIR=/lib64 scons prefix=/usr ...

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] build on linux


it looks like our build script doesn't like filenames that contain a space :

grep: 
/home/iurt/rpmbuild/BUILDROOT/mixxx-2.0.0-3.mga6.x86_64/usr/share/mixxx/controllers/Hercules:
 No such file or directory
grep: DJ: No such file or directory
grep: Control: No such file or directory
grep: MP3: No such file or directory
grep: e2-scripts.js: No such file or directory
pcregrep: Failed to open 
/home/iurt/rpmbuild/BUILDROOT/mixxx-2.0.0-3.mga6.x86_64/usr/share/mixxx/controllers/Hercules:
 No such file or directory
pcregrep: Failed to open DJ: No such file or directory
pcregrep: Failed to open Control: No such file or directory
pcregrep: Failed to open MP3: No such file or directory
pcregrep: Failed to open e2-scripts.js: No such file or directory


I don't know if this is really a problem with the final rpm.

sb

Le 02/01/2016 20:58, zezinho a écrit :
> Em 02-01-2016 18:01, RJ Ryan escreveu:
>> A few notes:
>> * djconsole, script, midiscript, hifieq, tonal, and rawmidi no longer
>> exist as build flags
>> * please add build=release -- the default is a debug build, and in this
>> mode Mixxx performance suffers considerably as we have many debug
>> assertions in hot loops, etc.
>> * optimize=portable is the best optimize setting to use, optimize=0 will
>> also slow Mixxx down severely. We only use portable optimization flags
>> when this mode is enabled.
> Done, all this was good to know. Our build system also does some quality
> tests, maybe overlinking. Here is the warnings I get
>
>
> Warning: unused libraries in
> /usr/lib/mixxx/plugins/vamp/libmixxxminimal.so: libportmidi.so
> libQtOpenGL.so.4 libQtXml.so.4 libQtSvg.so.4 libQtSql.so.4
> libQtXmlPatterns.so.4 libQtNetwork.so.4  libQtTest.so.4
> libQtScriptTools.so.4 libQtGui.so.4 libQtScript.so.4 libQtCore.so.4
> libsndfile.so.1 libFLAC.so.8 libvorbisfile.so.3 libvorbis.so.0
> libogg.so.0 libvorbisenc.so.2 libGL.so.1 libGLU.so.1 libtag.so.1
> libprotobuf-lite.so.9 libchromaprint.so.0 librubberband.so.2 libmad.so.0
> libid3tag.so.0 libpthread.so.0 librt.so.1 libusb-1.0.so.0 libshout.so.3
> libopusfile.so.0 libopus.so.0 libdl.so.2 libX11.so.6 libfftw3.so.3
> libsqlite3.so.0
>
> Warning: unused libraries in /usr/bin/mixxx: libQtTest.so.4 libGLU.so.1
> libopus.so.0
>
>
> Full logs below for 48h :
>
> http://pkgsubmit.mageia.org/uploads/done/cauldron/core/release/20160102191456.zezinho.valstar.27580/
>
> --
> ___
> 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] TESTERS NEEDED: New windows installer

Hi jus,

Thanks for your pointers.

Yes, all translatable strings are in wxl files. They are located in
build/wix/Localization.

They are named mixxx_en-us.wxl where en-us is the language.

I also found
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-wxl-support-at-Transifex-td7517594.html
https://github.com/transifex/transifex/issues/59
so transifex doesn't have wxl support yet and I dont have the python
skills nor time needed to contribute that to transifex.

So we will need to use an intermediate format.

The format is really simple and it should be easy to extract the strings.
I didn't find at first look how to download and use okapi but I will
take a closer look.

regards,

Le 02/01/2016 21:36, S.Brandt a écrit :
Reading [1] and [2], i understand that we need the wix toolset to
extract *.wxl translation templates for each language to be supported.

Unfortunately, Transifex does not support the wxl format for import [3].
Might be possible to convert wxl templates to a format Transifex
supports, and vis-a-vis after translation, using the Okapi framework
[4] though.

Can investigate tomorrow (CET) if needed.

[1]
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/build_a_localized_version.html
[2]
http://wixtoolset.org/documentation/manual/v3/wixui/wixui_localization.html
<http://wixtoolset.org/documentation/manual/v3/wixui/wixui_localization.html%20,%20i%20understand%20you%C2%A0>

[3] http://docs.transifex.com/formats/
[4] http://www.opentag.com/okapi/wiki/index.php?title=Filters

jus

On Jan 2, 2016, at 6:38 PM, Sébastien Blaisot <mi...@blaisot.org
<mailto:mi...@blaisot.org>> wrote:

I built english and french installers, but I will need more
translations. Can somebody explain me how to extract strings and make
a file suitable for transifex ?

We can maybe publish it to transifex as a new resource ?

--
___
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] 2.0 RC2

2015-12-17 Thread Sébastien Blaisot

Le 18/12/2015 00:14, Be a écrit :
> What's going on with the RC2 release? And what is the target date for
> 2.0 release?

Do you mean this one: http://mixxx.org/download/#beta

Did you miss the anouncement ? :-p

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] TESTERS NEEDED: New windows installer

2015-11-19 Thread Sébastien BLAISOT

 

Thanks a lot daniel for your test. 

I will try to answer to all your points and will reorder them: 

* The setup seams to be not signed: "Unbekannter Herausgeber" 

Right. I will try to see if we can have it signed, but think this
involves having a mixxx-developper keypair to sign the package and I
don't think we have one 
 * Nice Artwork :-) However, it contains the 1.11 Deere Skin 

yes, this is only a quickly made test artwork. Controller photo also
needs to be changed by our own picture (or a free (as in free speech)
one) 
 * The XP warning feels to hard for me, compared to the fact that there
are no known issues. 

What will be correct wording for you ? 
 * The End-user license need to be polished. ** No pronotional Tracks 
** "You should have received a copy of" but the copy follows just after.

** It feels wired that the License starts with the external libraries 

The text is taken from the LICENCE file. If text update is needed,
please open a PR against this file. 
 ** Line breaks are looking missplaces 

yes, there are issues with linebreaks. starting from a text file with
linebreaks and transform it to RTF is not an easy task. so for now, I
just openned it with wordpad and saves it untouched as RTF. 
 ** Embedded links are highlighted but not clickable 

Windows installer framework limitation. Nothing I can do. 
 * Translations are a separate part, but there is no hint what will be
the language without it. 

ok, I will add that in the comment. 

* Clicking on "Disk Usage" stalls the setup with a pressed button for
approx 20 s 

Windows installer framework logic. It scan all drives to detect disk
usage => slow. 
The only thing I can do is to remove completely this dialog, but I don't
think it's a good idea. 

The following items are because you installed on top of a previous
installation: * Translations are 0 kB 

yes, the installer is smart enough to detect that you already have all
files installed in the destination path, so installing this will take no
additionnal space on your disk. 
Try installing on a mixxx-free system, you will see that size differ. 
 * After installation I have two "Manual" links in the start menu 

yes, old installer one and new installer one. 
 * The old uninstaller link remains in Startmenu 

yes 

* In control panel -> Software is a long list of Mixxx versions I have
testes. 

They were there before the installation with the new installer 

* Uninstall plain "Mixxx" entry works only partial 

can you explain a bit more this one ? 
I think it uninstalls correctly what it has installed, but former
installations let files behind. 

so not having a migration path from former installer to newer one seems
to be a problem. 
we have two ways of adressing this : 
1) detect if mixxx is already installed and forbid installation if a
former installation from the previous installer is detected 
2) write some (external and embedded) cleanup code that completely
remove all traces from a previous installation 

the second has my preference but seems harder as it involves writing an
autonomous cleanup executable and embedding it into the installer. 

---

Sébastien Blaisot 

Le 19/11/2015 08:44, Daniel Schürmann a écrit : 

> Hi Sébastien, 
> 
> Here my results from am instillation on a German Win XP using 
> mixxx-2.0-rc1-1.12-git5627-release-x86-en-us.msi 
> on to of an existing installation. 
> 
> * The setup seams to be not signed: "Unbekannter Herausgeber" * Nice Artwork 
> :-) However, it contains the 1.11 Deere Skin * The XP warning feels to hard 
> for me, compared to the fact that there are no known issues. * The End-user 
> license need to be polished. ** No pronotional Tracks ** Line breaks are 
> looking missplaces ** Embedded links are highlighted but not clickable 
> ** "You should have received a copy of" but the copy follows just after. ** 
> It feels wired that the License starts with the external libraries * 
> Translations are a separate part, but there is no hint what will be the 
> language without it. * Translations are 0 kB * Clicking on "Disk Usage" 
> stalls the setup with a pressed button for approx 20 s * After installation I 
> have two "Manual" links in the start menu * The old uninstaller link remains 
> in Startmenu 
> 
> * In control panel -> Software is a long list of Mixxx versions I have 
> testes. 
> * Uninstall plain "Mixxx" entry works only partial 
> 
> Kind regards, 
> 
> Daniel 
> 
> 2015-11-19 1:14 GMT+01:00 Sébastien Blaisot <mi...@blaisot.org>:
> 
>> Hi all,
>> 
>> I finally got wix to build an installer package for Mixxx and with the
>> help of Pegasus, I have my build env fixed.
>> 
>> So here you will find installer for 2.0-rc1-1.12-git5627 :
>> https://owncloud.blaisot.org/index.php/s/nyEDsb0v

Re: [Mixxx-devel] [Fwd: Re: [mixxx] Incorporate new mapping from bestdani on the forums. Thanks! (#780)]

2015-11-19 Thread Sébastien BLAISOT

 

from a phylosophical point of vue, the presets are bundled inside our
packages/installers and the licence agremment attached to that
package/installer doesn't make any difference between mapping and core
code IIRC. 

So making contributors sign the agreement doesn't hurt and avoid future
question that can be directed to this bundling. 

---

Sébastien Blaisot 

Le 19/11/2015 16:37, Sean M. Pappalardo - D.J. Pegasus a écrit : 

> On 11/19/2015 07:10 AM, Owen Williams wrote: 
> 
>> do we need to get this forum user to sign the contributor agreement?
>> Controller stuff is always hazy for me
> 
> The main reason for that agreement is to allow us to make license
> changes to the source code if needed without having to track down every
> past developer to get their permission. Since controller presets are
> sort of "at arm's length" (not compiled in, just distributed with the
> application,) they can have their own licenses. So we really just need
> permission to distribute them with the application, since if we ever
> change the application's license, it wouldn't necessarily apply to the
> controller presets themselves.
> 
> That said, it wouldn't hurt to have preset writers sign the agreement
> because it would avoid any future confusion. It's just not required.
> 
> IANAL so correct me if any of this is wrong.
> 
> Sincerely,
> Sean M. Pappalardo
> "D.J. Pegasus"
> Mixxx Developer - Controller Specialist
> 
> --
>  
> 
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org [1]
> 
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [2]
 

Links:
--
[1] http://mixxx.org
[2] 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] Old Windows versions: forbid installation or just warn?

2015-11-18 Thread Sébastien BLAISOT

 

Associated question is: If you choose to warn only, who is willing to
maintain legacy windows installer code and horrible hacks to make this
happen ? ;) 

I think that's not just a yes/no question, but is also a matter of
feature from windows installer we can use or not depending of the
minimal version we support (I can't tell which at the moment and need to
check the code against older versions). 

So, my vote goes to the first: don't encourage people to use outdated,
security-risky software and don't give them tools (like installers) to
use them. If they really want, they can try to compile from source or
use older Mixxx versions as well. 

This is better also for us because we can use modern and recent code. 

(in the same way, do we need to switch to c++11? people can't install
modern c++11-compliant compilers on their old OS :) 
---

Sébastien Blaisot 

Le 18/11/2015 18:01, Sean M. Pappalardo - D.J. Pegasus a écrit : 

> Hello everyone.
> 
> As Sebastien prepares a WiX-based Windows installer, (thanks for your
> work on this!!) the question has come up: What should we do if someone
> tries to install on a version of Windows older than we support? Do we
> forbid installation or allow it only after accepting a warning pop-up
> saying that there is no support and it may not work at all?
> 
> I vote the latter because people may want to try Mixxx on old surplus
> hardware that can't run newer Windows versions, especially in poorer
> countries. (Of course the case can be made that they should run Linux
> instead, but I figure, why artificially limit people from trying?)
> 
> Sincerely,
> Sean M. Pappalardo
> "D.J. Pegasus"
> Mixxx Developer - Controller Specialist
> 
> --
>  
> 
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org [1]
> 
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [2]
 

Links:
--
[1] http://mixxx.org
[2] 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] Old Windows versions: forbid installation or just warn?

2015-11-18 Thread Sébastien Blaisot

The PR I made is against master aka 1.132.1

I think we don't have enough background on this to make the switch to 
wix happen for 1.12 2.0

We need to test a lot before releasing an MSI installer.

so it could be fine to support only seven+.
Currently built MSI warn the user they use an outdated OS if he tries to 
install on XP.
And it is not possible to install with older than XP OS because of 
windows installer version compatibility.

To be able to launch the installer to older windows version, we need to 
support older windows installer versions, and consequently don't use 
windows installer features that are not included in such old versions 
(limiting our ability to implement the installer we want or needing to 
use horrible hacks which are difficult to maintain)

sb

Le 18/11/2015 19:26, RJ Ryan a écrit :

What release are you shooting for with the Wix installer?

Mixxx 2.0 supports XP/Vista but it is probably the last one that will 
do so.

Once we switch to Qt5 we lose Vista/XP support from Qt and so we'll 
probably rebuild all of our libraries without platform support for 
v120_xp (the last Windows platform SDK that supports XP). Which I'm 
pretty sure means Mixxx will fail to start completely on XP so it's 
not worth wasting the user's time installing the program just to crash.

It would still be possible with hacks but that would most likely 
require building from source so I'm not sure the installer is going to 
help.

On Wed, Nov 18, 2015 at 10:01 AM, Gavin Swanson 
<gavinswan...@gmail.com <mailto:gavinswan...@gmail.com>> wrote:

I suggest don't forbid, but also don't support legacy (non vendor
supported) OS's.

XP is dangerously unsupported at this point.

On Wed, Nov 18, 2015, 10:17 AM Sean M. Pappalardo - D.J. Pegasus
<spappala...@mixxx.org <mailto:spappala...@mixxx.org>> wrote:

On 11/18/2015 09:13 AM, Sébastien BLAISOT wrote:
> Associated question is: If you choose to warn only, who is
willing to
> maintain legacy windows installer code and horrible hacks to
make this
> happen ? ;)

To be clear, when we say an OS version is "not supported"
that's exactly
what we mean: we will not do anything to make it work on that
old OS. So
we need not maintain legacy code at all. So our attitude
becomes "You're
welcome to try it. If it works, great. If not, oh well."

Forbidding installation means we're saying "You're not welcome
to try it."

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
<mailto: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
<mailto: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] Old Windows versions: forbid installation or just warn?

2015-11-18 Thread Sébastien Blaisot


Hi Daniel,

we are not talking here about 1.12 nor 2.0

we are talking here about master, that is 2.1

There will be no installer change for 1.12

sb

Le 18/11/2015 21:03, Daniel Schürmann a écrit :

1+
Don't forbid to install.
Mixxx 1.12 runs and should run in Windows XP


Am 18.11.2015 um 19:01 schrieb Gavin Swanson:


I suggest don't forbid, but also don't support legacy (non vendor 
supported) OS's.


XP is dangerously unsupported at this point.


On Wed, Nov 18, 2015, 10:17 AM Sean M. Pappalardo - D.J. Pegasus 
<spappala...@mixxx.org <mailto:spappala...@mixxx.org>> wrote:




On 11/18/2015 09:13 AM, Sébastien BLAISOT wrote:
> Associated question is: If you choose to warn only, who is
willing to
> maintain legacy windows installer code and horrible hacks to
make this
> happen ? ;)

To be clear, when we say an OS version is "not supported" that's
exactly
what we mean: we will not do anything to make it work on that old
OS. So
we need not maintain legacy code at all. So our attitude becomes
"You're
welcome to try it. If it works, great. If not, oh well."

Forbidding installation means we're saying "You're not welcome to
try it."


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
<mailto: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



--
___
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] TESTERS NEEDED: New windows installer

2015-11-18 Thread Sébastien Blaisot

Hi all,

I finally got wix to build an installer package for Mixxx and with the 
help of Pegasus, I have my build env fixed.

So here you will find installer for 2.0-rc1-1.12-git5627 : 
https://owncloud.blaisot.org/index.php/s/nyEDsb0vEV7aa1m

There are 6 files.
The exe ones are old installers built with NSIS (same as what you can 
download from the mixxx site except it was built on my own build env)
The MSI ones are new installers built with wix (a preview of what could 
be the future installer)

MSI installer are built in 2 languages (french and english, no other 
translation made at that time) and 2 bitwidth (32 and 64 bits)

What I need is testers to tell me what needs to be polished in the MSI 
installers.

I need you to test all use-cases that you can have in mind, even crazy 
ones like installing 64 bits mixxx on a 32 bits system, installing on 
top of a previous installation and so on.
And also testing bare-metal install on a computer without mixxx 
installed, uninstalling (is there something left behind ?).

I also need to test it on older versions of windows, so if you have an 
old windows XP or even pre-XP system, please let me know how the 
installer works on that system.

please let me know also what you think of this new installer.

These new installer won't be ready for Mixxx 2.0, but I need you to test 
it with Mixxx 2.0 because it will let me implement and test the upgrade 
path when time will come for a 2.1, starting from an older version.

Thanks in advance,

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] Welcome Taglib 1.10

2015-11-17 Thread Sébastien Blaisot


ok, thanks all for the explanations.

Do we need to update our build envs ?
Maybe someone can update the wiki pages and instructions to migrate the 
build envs (especially for windows envs) ? ;)

sb

Le 17/11/2015 17:51, Owen Williams a écrit :
> This is a good reaction to have :).  We considered this addition
> carefully, and although upgrading a bundled library is always a risk, we
> felt the benefits were enough to make up for it.
>
>
>
> On Tue, 2015-11-17 at 08:10 +0100, Sébastien Blaisot wrote:
>> Le 17/11/2015 07:42, RJ Ryan a écrit :
>>> Windows / Mac build environments are now on taglib 1.10.
>> OMG! A library change just before a release.
>> We really need a release management policy...
>>
>> 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] Welcome Taglib 1.10

2015-11-16 Thread Sébastien Blaisot

Le 17/11/2015 07:42, RJ Ryan a écrit :
> Windows / Mac build environments are now on taglib 1.10.

OMG! A library change just before a release.
We really need a release management policy...

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] an intern program to consider

2015-11-06 Thread Sébastien Blaisot


I agree with sean and what I personnally understand by "leadership" are 
2 things  :
- We don't have a decision process published
- We don't have a release management cycle published (merge window, 
feature freeze milestone, string freeze milestone, release goals and 
decision, ...). Actually, I think no one can tell what work is needed to 
release 1.12

We should at least address this two things after 1.12 has landed before 
beginning to work on the next release.

see my post to the list on 22/07/2015 19:27

All is not always about coding, we also sometimes need to take in 
account project management.

This is my 2 cents and I would be happy to work with you on these issues.

regards,

sb

Le 06/11/2015 22:12, Owen Williams a écrit :
> I meant that reply to go to the list
>
> On Fri, 2015-11-06 at 16:12 -0500, Owen Williams wrote:
>> Well what do you mean by leadership in this case?  I do agree we have a
>> lack of people with time to manage interns, although I've not been doing
>> a lot of coding lately so I think I could do that next year.
>>
>>
>> On Fri, 2015-11-06 at 09:17 -0800, Sean M. Pappalardo - D.J. Pegasus
>> wrote:
>>> On 11/06/2015 09:09 AM, Owen Williams wrote:
 Aside from Google Summer of Code there are other internship programs
 that we could try to take advantage of.
>>> Interesting. Worth looking into for sure.
>>>
>>> But right now, I feel like our problem is one of lack of leadership. We
>>> can't effectively use interns if our core is lacking.
>>>
>>> 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

[Mixxx-devel] License/EULA translations ?

2015-10-18 Thread Sébastien Blaisot

Hi all,

While working on using wix to build Mixxx installer, I made it 
localizable (i.e. generate a localized installer).
I was wondering if it is a good idea to use a localized LICENSE agreement.

Our license agreement is mainly based on external licenses, like GPLv2. 
The only official GPLv2 is in english, and translations of the GPLv2 
license agreement are only unofficial translations for reader's convenience.
So my thought is that the license agreement should not be translated and 
only shown in it's original language unless we have lawyers to approve 
translations.

Is it ok for you if the license agreement is not translated in the 
installer ?

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] 1.12 windows build fixing

2015-10-16 Thread Sébastien BLAISOT

 

Hi all, 

Windows build is now ok on x86 and x64 

But there was a network error when transferring the builded x86
installer from the build server to downloads.mixxx.org 

see end of log in : 

http://builds.mixxx.org:8081/jenkins/job/1.12-release/architecture=i386,platform=windows/lastBuild/consoleFull
[6] 

the result is an incomplete package at 

http://downloads.mixxx.org/builds/1.12/release/mixxx-1.12.0-beta1-1.12-git5575-release-x86.exe
[7] 

can someone drop this file on the download server as it is incorrect
(it's only 7MB instead of 20+MB) ? 

Just to avoid someone downloading it and trying to install. I don't know
what can be the side effect of this. 

Thanks, 
-- 

Sébastien Blaisot 

Le 16/10/2015 00:35, Sébastien Blaisot a écrit : 

> I finally got it compile on my machine.
> 
> I sent a PR with all the changes I made :
> 
> https://github.com/mixxxdj/mixxx/pull/743 [1]
> 
> sb
> 
> Le 16/10/2015 00:31, Sébastien Blaisot a écrit : in fact, both of them need 
> to be replaced with
> TAGLIB_FILENAME_FROM_QSTRING(getFilename())
> 
> sb
> 
> Le 16/10/2015 00:24, Sébastien Blaisot a écrit : sorry, wrong line.
> 
> I meant
> https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L396
>  [2]
> 
> sb
> 
> Le 16/10/2015 00:09, Sébastien Blaisot a écrit : Probably you also need to 
> patch this :
> https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L105
>  [3]
> 
> I have a link-time error (unresolved external symbol) for
> soundsourcemediafoundation
> 
> sb
> 
> Le 15/10/2015 23:59, Daniel Schürmann a écrit : Nice! Then I will prepare a 
> commit, using this.
> 
> Am 15.10.2015 um 23:57 schrieb Sébastien Blaisot: I have no idea.
> It is available in Visual Studio 2010, 2012, 2013 and 2015
> https://msdn.microsoft.com/fr-fr/library/hh567368.aspx#featurelist [4]
> but I don't know if it is dependant of an option at compile time.
> 
> I know it works perfectly for me, out of the box (no special
> configuration for VC) using scons and mixxx 1.12 config ;)
> 
> sb
> 
> Le 15/10/2015 23:50, Daniel Schürmann a écrit : Is this available on VC 
> without c++11 support?
> 
> Am 15.10.2015 um 23:41 schrieb Sébastien Blaisot: As we are in a #ifdef 
> _WIN32, why not using native static_assert ?
> https://msdn.microsoft.com/fr-fr/library/dd293588.aspx [5]
> 
> sb

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

Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel [9]
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org [8]

Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel [9] 
--
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org [8]

Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel [9] 

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

Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel [9] 

Links:
--
[1] https://github.com/mixxxdj/mixxx/pull/743
[2]
https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L396
[3]
https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L105
[4] https://msdn.microsoft.com/fr-fr/library/hh567368.aspx#featurelist
[5] https://msdn.microsoft.com/fr-fr/library/dd293588.aspx
[6]
http://builds.mixxx.org:8081/jenkins/job/1.12-release/architecture=i386,platform=windows/lastBuild/consoleFull
[7]
http://downloads.mixxx.org/builds/1.12/release/mixxx-1.12.0-beta1-1.12-git5575-release-x86.exe
[8] http://mixxx.org
[9] 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] 1.12 windows build fixing


As we are in a #ifdef _WIN32, why not using native static_assert ?
https://msdn.microsoft.com/fr-fr/library/dd293588.aspx

sb

Le 15/10/2015 22:05, Daniel Schürmann a écrit :
> Thank you.
>
> I have fixed the issue and have a working STATIC_ASSERT
> just build local, will commit next.
>
>
> Am 15.10.2015 um 22:00 schrieb Owen Williams:
>> Still failing:
>>
>>
>> cl : Command line warning D9002 : ignoring unknown option '/arch:SSE2'
>> soundsourcemediafoundation.cpp
>>
>> c:\mixxx\environments\2.0-x64-release\include\taglib\trefcounter.h(36) :
>> warning C4005: 'NOMINMAX' : macro redefinition
>>   command-line arguments :  see previous definition of 'NOMINMAX'
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(66) :
>> error C2614: 'SoundSourceMediaFoundation' : illegal member
>> initialization: 'm_wcFilename' is not a base or member
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(75) :
>> error C2065: 'm_wcFilename' : undeclared identifier
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>> error C2065: 'm_wcFilename' : undeclared identifier
>>
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>> error C2541: 'delete' : cannot delete objects that are not pointers
>> scons: *** [win64_build\plugins\win64_build\mediafoundation
>> \soundsourcemediafoundation.obj] Error 2
>> scons: building terminated because of errors.
>>
>> Build step 'Execute Windows batch command' marked build as failure
>> Recording test results
>> ERROR: Publisher 'Publish JUnit test result report' failed: Test reports
>> were found but none of them are new. Did tests run?
>> For example, c:\mixxx\workspace\1.12-release\architecture\amd64\platform
>> \windows\test_results.xml is 14 days old
>>
>> SSH: Current build result is [FAILURE], not going to run.
>>
>> Finished: FAILURE
>>
>>
>> On Thu, 2015-10-15 at 12:38 -0700, Sebastien BLAISOT wrote:
>>> NULL),
>>>
>>> You're missing a closing parenthesis
>>>
>>> —
>>> Reply to this email directly or view it on GitHub.
>>>
>>>
>>
>> --
>> ___
>> 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] 1.12 windows build fixing


Still failing:

cl : Ligne de commande warning D9002 : option '/arch:SSE2' inconnue ignorée
audiotagger.cpp
d:\mixxx-buildserver64\include\taglib\trefcounter.h(36) : warning C4005: 
'NOMINMAX' : redéfinition de macro
 arguments de ligne de commande : voir la définition précédente 
de 'NOMINMAX'
src\audiotagger.cpp(25) : error C4430: spécificateur de type manquant - 
int est
pris en compte par défaut. Remarque : C++ ne prend pas en charge int par 
défaut
scons: *** [win64_build\audiotagger.obj] Error 2
scons: building terminated because of errors.



Le 15/10/2015 22:16, Daniel Schürmann a écrit :
> New version is up:
> https://github.com/mixxxdj/mixxx/commit/316e7e9900e03a7c331db6ebdf03d5c16c323651
>
> Am 15.10.2015 um 22:00 schrieb Owen Williams:
>> Still failing:
>>
>>
>> cl : Command line warning D9002 : ignoring unknown option '/arch:SSE2'
>> soundsourcemediafoundation.cpp
>>
>> c:\mixxx\environments\2.0-x64-release\include\taglib\trefcounter.h(36) :
>> warning C4005: 'NOMINMAX' : macro redefinition
>>   command-line arguments :  see previous definition of 'NOMINMAX'
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(66) :
>> error C2614: 'SoundSourceMediaFoundation' : illegal member
>> initialization: 'm_wcFilename' is not a base or member
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(75) :
>> error C2065: 'm_wcFilename' : undeclared identifier
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>> error C2065: 'm_wcFilename' : undeclared identifier
>>
>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>> error C2541: 'delete' : cannot delete objects that are not pointers
>> scons: *** [win64_build\plugins\win64_build\mediafoundation
>> \soundsourcemediafoundation.obj] Error 2
>> scons: building terminated because of errors.
>>
>> Build step 'Execute Windows batch command' marked build as failure
>> Recording test results
>> ERROR: Publisher 'Publish JUnit test result report' failed: Test reports
>> were found but none of them are new. Did tests run?
>> For example, c:\mixxx\workspace\1.12-release\architecture\amd64\platform
>> \windows\test_results.xml is 14 days old
>>
>> SSH: Current build result is [FAILURE], not going to run.
>>
>> Finished: FAILURE
>>
>>
>> On Thu, 2015-10-15 at 12:38 -0700, Sebastien BLAISOT wrote:
>>> NULL),
>>>
>>> You're missing a closing parenthesis
>>>
>>> —
>>> Reply to this email directly or view it on GitHub.
>>>
>>>
>>
>> --
>> ___
>> 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] 1.12 windows build fixing


in fact, both of them need to be replaced with
TAGLIB_FILENAME_FROM_QSTRING(getFilename())

sb

Le 16/10/2015 00:24, Sébastien Blaisot a écrit :
> sorry, wrong line.
>
> I meant
> https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L396
>
> sb
>
> Le 16/10/2015 00:09, Sébastien Blaisot a écrit :
>> Probably you also need to patch this :
>> https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L105
>>
>> I have a link-time error (unresolved external symbol) for
>> soundsourcemediafoundation
>>
>> sb
>>
>> Le 15/10/2015 23:59, Daniel Schürmann a écrit :
>>> Nice! Then I will prepare a commit, using this.
>>>
>>> Am 15.10.2015 um 23:57 schrieb Sébastien Blaisot:
>>>> I have no idea.
>>>> It is available in Visual Studio 2010, 2012, 2013 and 2015
>>>> https://msdn.microsoft.com/fr-fr/library/hh567368.aspx#featurelist
>>>> but I don't know if it is dependant of an option at compile time.
>>>>
>>>> I know it works perfectly for me, out of the box (no special
>>>> configuration for VC) using scons and mixxx 1.12 config ;)
>>>>
>>>> sb
>>>>
>>>> Le 15/10/2015 23:50, Daniel Schürmann a écrit :
>>>>> Is this available on VC without c++11 support?
>>>>>
>>>>> Am 15.10.2015 um 23:41 schrieb Sébastien Blaisot:
>>>>>> As we are in a #ifdef _WIN32, why not using native static_assert ?
>>>>>> https://msdn.microsoft.com/fr-fr/library/dd293588.aspx
>>>>>>
>>>>>> 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


--
___
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] 1.12 windows build fixing


I finally got it compile on my machine.

I sent a PR with all the changes I made :

https://github.com/mixxxdj/mixxx/pull/743

sb

Le 16/10/2015 00:31, Sébastien Blaisot a écrit :
> in fact, both of them need to be replaced with
> TAGLIB_FILENAME_FROM_QSTRING(getFilename())
>
> sb
>
> Le 16/10/2015 00:24, Sébastien Blaisot a écrit :
>> sorry, wrong line.
>>
>> I meant
>> https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L396
>>
>> sb
>>
>> Le 16/10/2015 00:09, Sébastien Blaisot a écrit :
>>> Probably you also need to patch this :
>>> https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L105
>>>
>>> I have a link-time error (unresolved external symbol) for
>>> soundsourcemediafoundation
>>>
>>> sb
>>>
>>> Le 15/10/2015 23:59, Daniel Schürmann a écrit :
>>>> Nice! Then I will prepare a commit, using this.
>>>>
>>>> Am 15.10.2015 um 23:57 schrieb Sébastien Blaisot:
>>>>> I have no idea.
>>>>> It is available in Visual Studio 2010, 2012, 2013 and 2015
>>>>> https://msdn.microsoft.com/fr-fr/library/hh567368.aspx#featurelist
>>>>> but I don't know if it is dependant of an option at compile time.
>>>>>
>>>>> I know it works perfectly for me, out of the box (no special
>>>>> configuration for VC) using scons and mixxx 1.12 config ;)
>>>>>
>>>>> sb
>>>>>
>>>>> Le 15/10/2015 23:50, Daniel Schürmann a écrit :
>>>>>> Is this available on VC without c++11 support?
>>>>>>
>>>>>> Am 15.10.2015 um 23:41 schrieb Sébastien Blaisot:
>>>>>>> As we are in a #ifdef _WIN32, why not using native static_assert ?
>>>>>>> https://msdn.microsoft.com/fr-fr/library/dd293588.aspx
>>>>>>>
>>>>>>> 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
>
> --
> ___
> 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] 1.12 windows build fixing


Probably you also need to patch this :
https://github.com/mixxxdj/mixxx/blob/1.12/plugins/soundsourcemediafoundation/soundsourcemediafoundation.cpp#L105

I have a link-time error (unresolved external symbol) for 
soundsourcemediafoundation

sb

Le 15/10/2015 23:59, Daniel Schürmann a écrit :
> Nice! Then I will prepare a commit, using this.
>
> Am 15.10.2015 um 23:57 schrieb Sébastien Blaisot:
>> I have no idea.
>> It is available in Visual Studio 2010, 2012, 2013 and 2015
>> https://msdn.microsoft.com/fr-fr/library/hh567368.aspx#featurelist
>> but I don't know if it is dependant of an option at compile time.
>>
>> I know it works perfectly for me, out of the box (no special
>> configuration for VC) using scons and mixxx 1.12 config ;)
>>
>> sb
>>
>> Le 15/10/2015 23:50, Daniel Schürmann a écrit :
>>> Is this available on VC without c++11 support?
>>>
>>> Am 15.10.2015 um 23:41 schrieb Sébastien Blaisot:
>>>> As we are in a #ifdef _WIN32, why not using native static_assert ?
>>>> https://msdn.microsoft.com/fr-fr/library/dd293588.aspx
>>>>
>>>> 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] 1.12 windows build fixing


I have no idea.
It is available in Visual Studio 2010, 2012, 2013 and 2015
https://msdn.microsoft.com/fr-fr/library/hh567368.aspx#featurelist
but I don't know if it is dependant of an option at compile time.

I know it works perfectly for me, out of the box (no special 
configuration for VC) using scons and mixxx 1.12 config ;)

sb

Le 15/10/2015 23:50, Daniel Schürmann a écrit :
> Is this available on VC without c++11 support?
>
> Am 15.10.2015 um 23:41 schrieb Sébastien Blaisot:
>> As we are in a #ifdef _WIN32, why not using native static_assert ?
>> https://msdn.microsoft.com/fr-fr/library/dd293588.aspx
>>
>> sb
>>
>> Le 15/10/2015 22:05, Daniel Schürmann a écrit :
>>> Thank you.
>>>
>>> I have fixed the issue and have a working STATIC_ASSERT
>>> just build local, will commit next.
>>>
>>>
>>> Am 15.10.2015 um 22:00 schrieb Owen Williams:
>>>> Still failing:
>>>>
>>>>
>>>> cl : Command line warning D9002 : ignoring unknown option '/arch:SSE2'
>>>> soundsourcemediafoundation.cpp
>>>>
>>>> c:\mixxx\environments\2.0-x64-release\include\taglib\trefcounter.h(36) :
>>>> warning C4005: 'NOMINMAX' : macro redefinition
>>>> command-line arguments :  see previous definition of 'NOMINMAX'
>>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(66) :
>>>> error C2614: 'SoundSourceMediaFoundation' : illegal member
>>>> initialization: 'm_wcFilename' is not a base or member
>>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(75) :
>>>> error C2065: 'm_wcFilename' : undeclared identifier
>>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>>>> error C2065: 'm_wcFilename' : undeclared identifier
>>>>
>>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>>>> error C2541: 'delete' : cannot delete objects that are not pointers
>>>> scons: *** [win64_build\plugins\win64_build\mediafoundation
>>>> \soundsourcemediafoundation.obj] Error 2
>>>> scons: building terminated because of errors.
>>>>
>>>> Build step 'Execute Windows batch command' marked build as failure
>>>> Recording test results
>>>> ERROR: Publisher 'Publish JUnit test result report' failed: Test reports
>>>> were found but none of them are new. Did tests run?
>>>> For example, c:\mixxx\workspace\1.12-release\architecture\amd64\platform
>>>> \windows\test_results.xml is 14 days old
>>>>
>>>> SSH: Current build result is [FAILURE], not going to run.
>>>>
>>>> Finished: FAILURE
>>>>
>>>>
>>>> On Thu, 2015-10-15 at 12:38 -0700, Sebastien BLAISOT wrote:
>>>>> NULL),
>>>>>
>>>>> You're missing a closing parenthesis
>>>>>
>>>>> —
>>>>> Reply to this email directly or view it on GitHub.
>>>>>
>>>>>
>>>> --
>>>> ___
>>>> 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
>
> --
> ___
> 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] 1.12 windows build fixing


It seems to be compiling fine if you replace

STATIC_ASSERT(sizeof(wchar_t) == sizeof(QChar));

with

static_assert(sizeof(wchar_t) == sizeof(QChar), "wchar_t is not the same 
size than QChar");

and remove STATIC_ASSERT definition in src/util/assert.h

sb

Le 15/10/2015 23:41, Sébastien Blaisot a écrit :
> As we are in a #ifdef _WIN32, why not using native static_assert ?
> https://msdn.microsoft.com/fr-fr/library/dd293588.aspx
>
> sb
>
> Le 15/10/2015 22:05, Daniel Schürmann a écrit :
>> Thank you.
>>
>> I have fixed the issue and have a working STATIC_ASSERT
>> just build local, will commit next.
>>
>>
>> Am 15.10.2015 um 22:00 schrieb Owen Williams:
>>> Still failing:
>>>
>>>
>>> cl : Command line warning D9002 : ignoring unknown option '/arch:SSE2'
>>> soundsourcemediafoundation.cpp
>>>
>>> c:\mixxx\environments\2.0-x64-release\include\taglib\trefcounter.h(36) :
>>> warning C4005: 'NOMINMAX' : macro redefinition
>>>command-line arguments :  see previous definition of 'NOMINMAX'
>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(66) :
>>> error C2614: 'SoundSourceMediaFoundation' : illegal member
>>> initialization: 'm_wcFilename' is not a base or member
>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(75) :
>>> error C2065: 'm_wcFilename' : undeclared identifier
>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>>> error C2065: 'm_wcFilename' : undeclared identifier
>>>
>>> plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) :
>>> error C2541: 'delete' : cannot delete objects that are not pointers
>>> scons: *** [win64_build\plugins\win64_build\mediafoundation
>>> \soundsourcemediafoundation.obj] Error 2
>>> scons: building terminated because of errors.
>>>
>>> Build step 'Execute Windows batch command' marked build as failure
>>> Recording test results
>>> ERROR: Publisher 'Publish JUnit test result report' failed: Test reports
>>> were found but none of them are new. Did tests run?
>>> For example, c:\mixxx\workspace\1.12-release\architecture\amd64\platform
>>> \windows\test_results.xml is 14 days old
>>>
>>> SSH: Current build result is [FAILURE], not going to run.
>>>
>>> Finished: FAILURE
>>>
>>>
>>> On Thu, 2015-10-15 at 12:38 -0700, Sebastien BLAISOT wrote:
>>>> NULL),
>>>>
>>>> You're missing a closing parenthesis
>>>>
>>>> —
>>>> Reply to this email directly or view it on GitHub.
>>>>
>>>>
>>> --
>>> ___
>>> 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


--
___
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] 1.12 -> trunk merge needs help

Le 15/10/2015 08:42, Daniel Schürmann a écrit :
> Unfortunately I have no access to the build server (network timeout)
> Since there are no recent windows builds builds on
> http://downloads.mixxx.org/builds/1.12/
> I assume there is still an issue. Can one forward me the failing build
> message?

from 
http://builds.mixxx.org:8081/jenkins/job/1.12-release/architecture=amd64,platform=windows/129/console

soundsourcemediafoundation.cpp
c:\mixxx\environments\2.0-x64-release\include\taglib\trefcounter.h(36) : 
warning C4005: 'NOMINMAX' : macro redefinition
  command-line arguments :  see previous definition of 'NOMINMAX'
plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(66) : 
error C2614: 'SoundSourceMediaFoundation' : illegal member 
initialization: 'm_wcFilename' is not a base or member
plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(75) : 
error C2065: 'm_wcFilename' : undeclared identifier
plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) : 
error C2065: 'm_wcFilename' : undeclared identifier
plugins\soundsourcemediafoundation\soundsourcemediafoundation.cpp(80) : 
error C2541: 'delete' : cannot delete objects that are not pointers
scons: *** 
[win64_build\plugins\win64_build\mediafoundation\soundsourcemediafoundation.obj]
 
Error 2
scons: building terminated because of errors.

-- 
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] port windows installer to Wix

2015-09-05 Thread Sébastien Blaisot

Le 02/09/2015 08:38, Daniel Schürmann a écrit :
> 3. IMHO it is nothing wrong to install a 32 binary to a 64 bit Windows.
> So It should be possible to keep a degree of freedom in case of issues.
> However, we should encourage the user to use 64 bit binaries, since
> there should be a performance gain. It supports atomic access to the
> control objects and has core SSE instructions.

ok, I modified the installer to allow 32 bits installation on a 64 bits 
machine but print a warning message to the user that he will have better 
performances using the 64bits version.

I now have a conflict when installing both 32 and 64bits packages on the 
same machine because they install :
- same Mixxx startup menu shortcut
- same Mixxx desktop shortcut
- same Mixxx manual startup menu shortcut
- same Mixxx startup menu subfolder
- same uninstall entry in preferences->program uninstall


I have 2 ways to deal with this :

1) always append (64 bits) on 64bits shortcuts, directory and uninstall 
entry. I think this is a nonsense for 64 bits users that do not want to 
install 32bit version

2) forbid 64 bits installation if 32bits version is already installed 
and vice-versa. This will lead to the impossibility to install woth 32 
and 64 bits versions of Mixxx on the same computer.

My preference goes to #2 because I don't see any use case to have both 
32 and 64 bits installed on the same computer, except for a developper 
that can tweak his registry to allow this to happen.

Any thoughts ?


--
___
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] port windows installer to Wix

2015-09-03 Thread Sébastien BLAISOT

 

No matter if we will continue to build Mixxx for XP or not, the
installer will not enforce XP support drop, so you will be free to
support XP or not. 

That said, I personnally don't think it's a good think to passively
encourage people to keep XP. 
Keeping XP support will exponentionnaly increase complexity over time. 

regads, 

---

Sébastien Blaisot 

Le 03/09/2015 13:04, Daniel Schürmann a écrit : 

> We are free to decide when it is the right moment to drop XP since Microsoft 
> has reintroduced XP support into Visual Studio. 
> It also looks like that there is no issue to compile QT 5.5 for Windows XP: 
> http://doc.qt.io/qt-5/windows-issues.html [4]
> 
> IMHO we should not drop XP support for no reason. 
> 
> 2015-09-03 11:53 GMT+02:00 Max Linke <max_li...@gmx.de>:
> 
>>> 
>>> 4. Can we get rid of windows XP Support ?
>> 
>> 1.12 will be the last release supporting Windows XP.
>> 
>> It is also the last release were it is possible to have a
>> Windows XP build.
>> 
>> This is because Qt5 has dropped support for XP and the new
>> Virtual Studios that support C++11 don't support XP either.
>> 
>> So for anything after 1.12 you should be free to ignore XP.
>> 
>> --
>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>> Get real-time metrics from all of your servers, apps and tools
>> in one place.
>> SourceForge users - Click here to start your Free Trial of Datadog now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140 [1]
>> 
>> ___
>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>> http://mixxx.org [2]
>> 
>> Mixxx-devel mailing list
>> Mixxx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [3]
> 
> --
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140 [1] 
> 
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org [2]
> 
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [3]
 

Links:
--
[1] http://pubads.g.doubleclick.net/gampad/clk?id=241902991iu=/4140
[2] http://mixxx.org
[3] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
[4] http://doc.qt.io/qt-5/windows-issues.html
--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien BLAISOT

 

The main benefit in switching to wix is to support clean upgrade pathes
between versions the same way they are handled by deb packages or macOS
packages. 
Actually, If you install 1.12 on windows and have 1.11 already
installed, this leads to 1.12 installed on top of 1.11 with the
following caveats: 
- Old 1.11 and new 1.12 skins present in the skins folder 
- 2 entries in settings pannel -> software uninstall (for 1.11 and
1.12), but both entries will uninstall mixxx and keep the other entry
orpheline. 
- Files manually added to Mixxx installation folder being deleted on
uninstall even if not installed by Mixxx's installer (except for
controller mappings) 

The other benefit is to support autorepair functionnality of windows
installer framework. 

regards, 

-- 

Sébastien Blaisot 

Le 02/09/2015 08:43, Tuukka Pasanen a écrit : 

> Hello,
> What are main benfits of porting to WIX and yes XP in oboslette but many 
> people still use it. Biggest problem will be with QT5 or the future when 
> it's dropped.from QT.
> 
> Tuukka
> 
> 02.09.2015, 09:38, Daniel Schürmann kirjoitti: Hi Sébastien,
> 
> Thank you for all your work on Windows!
> 
> I'll try to answer some of you questions:
> 
> 1. ?
> 
> 2. it should be $(WIX) according to
> http://stackoverflow.com/questions/2375322/variable-for-wix-bin-directory-path
>  [1]
> 
> 3. IMHO it is nothing wrong to install a 32 binary to a 64 bit Windows.
> So It should be possible to keep a degree of freedom in case of issues.
> However, we should encourage the user to use 64 bit binaries, since
> there should be a performance gain. It supports atomic access to the
> control objects and has core SSE instructions.
> 
> 4. Can we get rid of windows XP Support ? Is there a strong technical need to 
> drop XP support?
> Win XP is still the second often used desktop operating system after Win 7. 
> It is common to use recycled laptops for parties where a beer shower may 
> happen.
> https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10=0
>  [2]
> Lets keep it!
> 
> 5. actual installer creates empty directories "promo" and "sqldrivers". Are 
> they still required or just oldies that we can forget?
> 
> They outdated and can be removed.
> 
> Kind regards,
> 
> Daniel
> 
> Am 01.09.2015 um 23:05 schrieb Sébastien Blaisot: Hi All,
> 
> I'm in an effort to port Mixxx's windows installer to Wix.
> I really have hard times because windows installer framework is...
> well... you know.
> 
> I primarily focused on the reproduction of the existing operation, with
> some gain in this migration (working upgrades primarily).
> 
> I am now able to build 32 and 64 bits MSI for Mixxx manually and
> installing it to my computer leads to a working Mixxx \o/.
> 
> My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer 
> [3]
> All changes has been made under build/wix
> 
> What's left on my TODO list :
> - include VCredist in the package (seems possible to use VCredist merge
> modules if we have visual studio installed on the build server)
> - Add QT's translations that I left appart from the installer now
> because it's not possible to include a subset of the files in a source
> directory
> - Integrate with SCons
> - test, test and test again
> 
> I have a few questions to achieve this goal :
> 
> 1. Can someone with an access to the build server show me what's in
> C:\Program Files (x86)\Common Files\Merge Modules ?
> 
> 2. When we will have Wix installed on the build server, is it acceptable
> to add the Wix installation directory to the %PATH% of the build server
> and rely on it ? I didn't find a way to automatically determine where
> this folder is located like we actually do in scons for NSIS.
> 
> 3. Installation of 64bits package on 32bits machines is of course
> forbidden. I'm not sure if we need to permit 32bits mixxx installation
> on 64bits computer. Is anyone aware of such a use-case ?
> 
> I really appreciate all comments about this.
> 
> regards,
> 
> sb
> 
> --
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org [4]
> 
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [5] 
> --
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog n

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien BLAISOT

 

 I'll try to answer to all points. 

1. Mixxx needs VCredist libraries. The actual NSIS installer embed
vcredist.exe and launch it in the background based on a registry key.
The clean way to do this in Wix is to embed mergeable modules of
vcredist in your installer. mergeable modules are modules that you can
embed in your installer. They are usually installed in C:\Program Files
(x86)\Common Files\Merge Modules when you install visual studio. 

2. I'm afraid $(WIX) is a locally defined variable from the blog author.
in fact $(WIX) is not a windows variable format, it should be %WIX%. I
didn't find any environment variable nor registry key telling me where
WIX it installed. so I don't see any solution appart asking the
developper to manually set it somewhere, either as PATH or environment
variable or as a compilation switch. The same way we do it for
WINLIB_PATH path in
http://www.mixxx.org/wiki/doku.php/build_windows_installer#make_the_package
[7] 

3. Ok, so I will need to handle : 

 - warning message when installing 32 bits on 63bits system 

 - installation of both 32 + 64 bit mixxx on a 64 bits OS. This should
be the tricky part. 

4. ok, I'll keep XP compatibility 

5. ok, I'll drop sqldrivers but keep promo as pointed by Sean. 

regards, 

-- 

Sébastien Blaisot 

Le 02/09/2015 08:38, Daniel Schürmann a écrit : 

> Hi Sébastien,
> 
> Thank you for all your work on Windows!
> 
> I'll try to answer some of you questions:
> 
> 1. ? 
> 
> 2. it should be $(WIX) according to 
> http://stackoverflow.com/questions/2375322/variable-for-wix-bin-directory-path
>  [4]
> 
> 3. IMHO it is nothing wrong to install a 32 binary to a 64 bit Windows.
> So It should be possible to keep a degree of freedom in case of issues.
> However, we should encourage the user to use 64 bit binaries, since
> there should be a performance gain. It supports atomic access to the
> control objects and has core SSE instructions. 
> 
>> 4. Can we get rid of windows XP Support ?
> 
> Is there a strong technical need to drop XP support? 
> Win XP is still the second often used desktop operating system after Win 7. 
> It is common to use recycled laptops for parties where a beer shower may 
> happen. 
> https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10=0
>  [5]
> Lets keep it!
> 
>> 5. actual installer creates empty directories "promo" and "sqldrivers".
> Are they still required or just oldies that we can forget?
> 
> They outdated and can be removed. 
> 
> Kind regards, 
> 
> Daniel 
> 
> Am 01.09.2015 um 23:05 schrieb Sébastien Blaisot: 
> 
>> Hi All,
>> 
>> I'm in an effort to port Mixxx's windows installer to Wix.
>> I really have hard times because windows installer framework is... 
>> well... you know.
>> 
>> I primarily focused on the reproduction of the existing operation, with 
>> some gain in this migration (working upgrades primarily).
>> 
>> I am now able to build 32 and 64 bits MSI for Mixxx manually and 
>> installing it to my computer leads to a working Mixxx \o/.
>> 
>> My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer 
>> [1]
>> All changes has been made under build/wix
>> 
>> What's left on my TODO list :
>> - include VCredist in the package (seems possible to use VCredist merge 
>> modules if we have visual studio installed on the build server)
>> - Add QT's translations that I left appart from the installer now 
>> because it's not possible to include a subset of the files in a source 
>> directory
>> - Integrate with SCons
>> - test, test and test again
>> 
>> I have a few questions to achieve this goal :
>> 
>> 1. Can someone with an access to the build server show me what's in 
>> C:\Program Files (x86)\Common Files\Merge Modules ?
>> 
>> 2. When we will have Wix installed on the build server, is it acceptable 
>> to add the Wix installation directory to the %PATH% of the build server 
>> and rely on it ? I didn't find a way to automatically determine where 
>> this folder is located like we actually do in scons for NSIS.
>> 
>> 3. Installation of 64bits package on 32bits machines is of course 
>> forbidden. I'm not sure if we need to permit 32bits mixxx installation 
>> on 64bits computer. Is anyone aware of such a use-case ?
>> 
>> I really appreciate all comments about this.
>> 
>> regards,
>> 
>> sb
>> 
>> --
>> ___
>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>> http://mixxx.org [2]
>&g

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien BLAISOT

 

I already did a search on Wix in my registry with nothing standard found
to tell me where wix is actually installed. I will take another look
tonight. 

(Wix is not a microsoft product, it's an open source project that
compiles an xml description of your installer into an MSI package). The
microsoft part is the installer engine that let you install MSI's on
target computers. 

Sadly, Desktop and Start Menu shortcuts are not separated, so I need to
handle the case... 

Same apply to uninstall entries. 

so, we will need to append (64bits) to each shortcut or uninstall entry.

--

Sébastien Blaisot 

Le 02/09/2015 17:27, Sean M. Pappalardo - D.J. Pegasus a écrit : 

> On 09/02/2015 08:11 AM, Sébastien BLAISOT wrote: 
> 
>> 2. I'm afraid $(WIX) is a locally defined variable from the blog author.
>> in fact $(WIX) is not a windows variable format, it should be %WIX%. I
>> didn't find any environment variable nor registry key telling me where
>> WIX it installed.
> 
> If it's present in Add/Remove programs, there's a registry key for it! :) If 
> nothing is mentioned on WiX documentation, look in the standard places 
> installed applications are registered. In the worst case, look around your 
> registry in HKLM/Software/Microsoft/Windows/Installer or 
> HKLM/Software/Microsoft/WiX.
> 
>> - installation of both 32 + 64 bit mixxx on a 64 bits OS. This should
>> be the tricky part.
> 
> Not really, since %PROGRAMFILES% will expand to "Program Files (x86)" in a 
> 32-bit process on a 64-bit system, and "Program Files" in other cases. This 
> happens automatically. The registries are also separated. (Wow6432Node)
> 
> Sincerely,
> Sean M. Pappalardo
> "D.J. Pegasus"
> Mixxx Developer - Controller Specialist
 --
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien Blaisot


oops, found it, there indeed IS a %WIX% environment variable set by 
installer.

sb

Le 02/09/2015 19:28, Sébastien Blaisot a écrit :
> Le 02/09/2015 17:27, Sean M. Pappalardo - D.J. Pegasus a écrit :
>>
>> On 09/02/2015 08:11 AM, Sébastien BLAISOT wrote:
>>> 2. I'm afraid $(WIX) is a locally defined variable from the blog author.
>>> in fact $(WIX) is not a windows variable format, it should be %WIX%. I
>>> didn't find any environment variable nor registry key telling me where
>>> WIX it installed.
>> If it's present in Add/Remove programs, there's a registry key for it!
>> :) If nothing is mentioned on WiX documentation, look in the standard
>> places installed applications are registered. In the worst case, look
>> around your registry in HKLM/Software/Microsoft/Windows/Installer or
>> HKLM/Software/Microsoft/WiX.
> I found it under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2A076531-42D9-4231-8A60-323EBE603E2E}.
>
> but first, I'm not sure the Guid part is fixed, and second the
> installation path is not in this key :(
>
> But I found HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows
> Installer XML\3.9
>
> unfortunately, the version number is in it, so I will have to include
> more logic :(
>
> sb
>
>
> --
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel


--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] port windows installer to Wix

2015-09-01 Thread Sébastien Blaisot


I have two more questions :

4. Can we get rid of windows XP Support ?

5. actual installer creates empty directories "promo" and "sqldrivers". 
Are they still required or just oldies that we can forget ?

regards,

sb

Le 01/09/2015 23:05, Sébastien Blaisot a écrit :
> Hi All,
>
> I'm in an effort to port Mixxx's windows installer to Wix.
> I really have hard times because windows installer framework is...
> well... you know.
>
> I primarily focused on the reproduction of the existing operation, with
> some gain in this migration (working upgrades primarily).
>
> I am now able to build 32 and 64 bits MSI for Mixxx manually and
> installing it to my computer leads to a working Mixxx \o/.
>
> My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer
> All changes has been made under build/wix
>
> What's left on my TODO list :
> - include VCredist in the package (seems possible to use VCredist merge
> modules if we have visual studio installed on the build server)
> - Add QT's translations that I left appart from the installer now
> because it's not possible to include a subset of the files in a source
> directory
> - Integrate with SCons
> - test, test and test again
>
> I have a few questions to achieve this goal :
>
> 1. Can someone with an access to the build server show me what's in
> C:\Program Files (x86)\Common Files\Merge Modules ?
>
> 2. When we will have Wix installed on the build server, is it acceptable
> to add the Wix installation directory to the %PATH% of the build server
> and rely on it ? I didn't find a way to automatically determine where
> this folder is located like we actually do in scons for NSIS.
>
> 3. Installation of 64bits package on 32bits machines is of course
> forbidden. I'm not sure if we need to permit 32bits mixxx installation
> on 64bits computer. Is anyone aware of such a use-case ?
>
> I really appreciate all comments about this.
>
> 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


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

[Mixxx-devel] port windows installer to Wix

2015-09-01 Thread Sébastien Blaisot

Hi All,

I'm in an effort to port Mixxx's windows installer to Wix.
I really have hard times because windows installer framework is... 
well... you know.

I primarily focused on the reproduction of the existing operation, with 
some gain in this migration (working upgrades primarily).

I am now able to build 32 and 64 bits MSI for Mixxx manually and 
installing it to my computer leads to a working Mixxx \o/.

My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer
All changes has been made under build/wix

What's left on my TODO list :
- include VCredist in the package (seems possible to use VCredist merge 
modules if we have visual studio installed on the build server)
- Add QT's translations that I left appart from the installer now 
because it's not possible to include a subset of the files in a source 
directory
- Integrate with SCons
- test, test and test again

I have a few questions to achieve this goal :

1. Can someone with an access to the build server show me what's in 
C:\Program Files (x86)\Common Files\Merge Modules ?

2. When we will have Wix installed on the build server, is it acceptable 
to add the Wix installation directory to the %PATH% of the build server 
and rely on it ? I didn't find a way to automatically determine where 
this folder is located like we actually do in scons for NSIS.

3. Installation of 64bits package on 32bits machines is of course 
forbidden. I'm not sure if we need to permit 32bits mixxx installation 
on 64bits computer. Is anyone aware of such a use-case ?

I really appreciate all comments about this.

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] build server is back

2015-08-19 Thread Sébastien Blaisot


That's good news. I was wondering today why we didn't have builds after 
july, 23.
Is your build server also building for windows ?

regards,

sb

Le 19/08/2015 20:21, Owen Williams a écrit :
 At least, it seems like it's working, there's a new file on the
 downloads server:

 http://downloads.mixxx.org/builds/1.12/release/

 The build server is now running in my basement on the same crappy
 machine it was before, but at least now it's easier for me to restart it
 when necessary.  We're limping along, but we're limping along with
 builds that we know are good.

 owen


--
___
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] PR#667 review merge

2015-08-10 Thread Sébastien Blaisot


Hi,

Can someone merge or comment PR#667 
https://github.com/mixxxdj/mixxx/pull/667 please ?


I missed HID mapping script in new mapping for Hercules DJ Control MP3 
e2. This PR corrects this.
MIDI driver for this controller is a real pain under Linux, so I think 
it is important to have correct HID support for it before 1.12 release.


Thanks in advance,

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] Deere state

2015-08-02 Thread Sébastien Blaisot



Hey, that's really cool ! I didn't even know this was possible with the 
skin engine.


Thanks.

sb

Le 02/08/2015 22:53, S.Brandt a écrit :
Once you configured mic 1-4, and aux 1-4 in the Preferences Sound 
Hardware, they become available in the Mic rack, and selectable in the 
FX section.



S.Brandt
Mixxx - Free Digital DJ Mixing Software
www.mixxx.org http://www.mixxx.org | Get Involved 
http://mixxx.org/get-involved/


On Aug 1, 2015, at 6:27 PM, Sébastien Blaisot mi...@blaisot.org 
mailto:mi...@blaisot.org wrote:



What an improvement ! I find Deere far more usable now.

However, it would be nice if the mic section could show 2 mic as well
as an aux section to control aux passthrough.

I will try to add that if I have some time after my vacations.

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] Deere state

2015-08-01 Thread Sébastien Blaisot


What an improvement ! I find Deere far more usable now.

However, it would be nice if the mic section could show 2 mic as well 
as an aux section to control aux passthrough.

I will try to add that if I have some time after my vacations.

regards,

sb

Le 30/07/2015 17:09, Owen Williams a écrit :
 I went ahead and merged in the deere-updates skin.  I took a look at it
 and it's definitely an improvement, and although it has issues I think
 we can open it up to the larger developer group now.

 Thanks for this work!  The menu is amazing.

 Owen


--
___
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] Advanced mapping questions

2015-07-22 Thread Sébastien BLAISOT

 

 ---
 
 Sébastien Blaisot

you can use : 
Low = engine.setValue([EqualizerRack1_[Channel1]_Effect1],
parameter1, value)
Mid = engine.setValue([EqualizerRack1_[Channel1]_Effect1],
parameter2, value) 
High = engine.setValue([EqualizerRack1_[Channel1]_Effect1],
parameter3, value) 

I don't have answer for the other questions. 

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] 1.12 release progress

2015-07-22 Thread Sébastien BLAISOT

 

Hi, 

I strongly disagree with you. We have a wonderfull new feature with
resizable skins and this new feature is ruined by our windows installer
because if you install 1.12 on top of 1.11, you get the old skins :(
Upgrade is not rare. We already discussed about that, I proposed a PR
which is waiting review since 1+ month. Saying today that this is not a
blocker don't correct the real problem : nobody seems to care about
windows users. This is relatively easy to merge, we must improve 1.12
quality including this PR. 

In my opinion, the problems of the mixxx project aren't marketing or
software quality, but two others : 

- The lack of release management process. We need to know when are the
new functionnality merge windows, when we are in feature freeze, what
and how we should consider blockers, and so on. and we need someone / a
team that dispatch remaining work to achieve release with a clearly
stated date or quality and focus every developpers on correcting
remaining bugs when we are about to release (for example avoid wasting
time talking about coding style during beta cycle). With a release
managemen process, the goal won't shift, or only in a controlled way. 

- The lack of decision process. This project is only driven by strong
consensus. When we don't have an overall agreement, nothing is done. it
is normal, in real life, that different people have different opinions.
We need a way to choose between different opinions. Either with a strong
project leader, or with a published process (like voting for example).
This should be published. 

---

Sébastien Blaisot 

Le 22/07/2015 16:12, RJ Ryan a écrit : 

 Daniel/RAWRR are right -- the goal posts are moving slightly and we're scope 
 creeping. 
 
 Active, trivial / low-risk PRs can merge if they are ready but shouldn't be 
 blocking. 
 
 For me, the final blocker is the manual and website / press material -- which 
 we simply can't launch without. :) 
 
 Best regards, 
 RJ 
 
 On Wed, Jul 22, 2015 at 8:11 AM, Ferran Pujol Camins 
 ferranpujolcam...@gmail.com wrote:
 
 From my point of view, marketing wise, we could consider 1.12 a modest 
 release. Because despite the huge amount of work there's behind it, every 
 review out there will essentially say it is great and finally have FX, but 
 the built in FX are weak. 
 
 So my modest opinion is the same that Daniel. 
 El dia 22/07/2015 12:16, re-cy...@hushmail.com va escriure:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On Wed, 22 Jul 2015 06:28:38 + Daniel Schürmann
 
 dasch...@mixxx.org wrote:
 Hi,
 
 We have to be careful to consider what is a release blocker.
 Mixxx 1.12 beta is already so much better than 1.11 that it is not
 worth to
 block it at all from this point of view.
 
 Of cause we should try to fix all critical bugs before a release
 date, but
 in this stage I consider a
 release blocker only a regression that prevents one from using
 1.12.
 From this point of view only this one is a blocker:
 * flaky broadcasting connections: LP 1277274
 
 The other topics are its the over all quality issue.
 
 Everyone can already use 1.12 beta. What is the difference to a
 1.12
 release?
 IMHO it is all the shiny stuff that makes the difference from a
 project to
 a product.
 It is marketing, design, manual, advertising texts, screen shots
 and so on.
 A product with good maketing/design is always considered as high
 quality,
 regardless
 of the number of critical bugs.
 
 Unfortunately marketing experts are rare among our contributors.
 Any Idea to change this?
 
 
 Yeah.
 
 If the betas really are that close, arrive at a consensus regarding
 some reasonable candidate among these beta versions to designate as
 a release, publish it, and continue on behind the scenes
 developing, like you do.
 
 Mixxx is marketed really well already. If you are thinking
 representation to the public is unclear, consider that perception
 will be clarified when the download page has a release, and
 further accentuated with the usual rounds of well-crafted press
 submissions to various DJ industry and tech sites and magazines
 (which one of you folks usually does that anyway?).
 
 It seems like everyone in development wants 1.12 to be a singular,
 glorious debut - but I think looking for that misses the mark.
 There is an actual glorious debut, but it was and is the momentum
 in productivity that fired up six months or so ago and will push
 all the way through 1.12 to the continuing evolution of the
 project, and a more modern style of development cycle.
 
 
 
 Also my personal two cents about the roadmap (apologies if it is
 off-base): I think new feature sprawl might be happening? If so, I
 myself probably contributed to it. I know this observation won't be
 popular!! Everyone wants and loves new features. But I think many
 of the debates going on will be less exasperating and more
 manageable when there are fewer projects underway in general.
 Between

Re: [Mixxx-devel] 1.12 release progress

2015-07-22 Thread Sébastien Blaisot


Le 22/07/2015 23:02, Owen Williams a écrit :
 For PRs that people think are ready and would like to merge in, can you
 list the actual numbers?  Our PR list is very dense and fast-moving.

 I am willing to take a look at the PRs that are in flight, but I can't
 guarantee that I will agree that everything is low risk or ready to
 merge.  If people trust me enough to make that decision then the process
 can work, but if not then I'd rather not spend the time doing the
 review.  If someone asks for my review and they don't like the answer,
 then they didn't want a review, they wanted a rubber stamp :).  I am
 admittedly quite conservative when it comes to LGTMing a PR for the
 beta, but I'd argue that's what we need.

I trust everyone who is willing to take a look at the PR I make and give 
me some feedback, even if the feedback is we will not merge this crap ;)

PR621: The question is: is it acceptable to ship Mixxx with a faulty 
upgrade path between 1.11 and 1.12 which leads to 1.12 with 1.11 skins
PR627:  The question is: is it acceptable to ship Mixxx with the effect 
eject button replaced by a square in the default skin

Thanks in advance for reviewing 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] 1.12 release progress

2015-07-22 Thread Sébastien Blaisot


I agree, we should wait post 1.12 release to discuss this. at first, i 
wanted to wait for 1.12 release before talking about that, but todays 
discussion let me at least disappointed.

for the windows specific issue, absolutely no build env is needed 
because one PR targets the installer, the other one targets the default 
skin. You just need a windows machine to test. or at least discuss about 
the consequences of the change I propose.

but, yes, more windows compiling env would be better ;)

sb

Le 22/07/2015 19:47, Be a écrit :
 I agree. I think we should discuss these issues in detail after 1.12 is
 released. For now, let's focus on getting those active PRs merged and
 the manual.

 The long review time for Windows-specific issues is a problem. For me,
 the issue is how much of a hassle it is to compile on Windows. I'd be
 happy to borrow a computer with Windows for testing if that didn't
 require installing a bunch of stuff to compile an unmerged pull request.

 On 07/22/2015 12:27 PM, Sébastien BLAISOT wrote:
 Hi,

 I strongly disagree with you. We have a wonderfull new feature with
 resizable skins and this new feature is ruined by our windows installer
 because if you install 1.12 on top of 1.11, you get the old skins :(
 Upgrade is not rare. We already discussed about that, I proposed a PR
 which is waiting review since 1+ month. Saying today that this is not a
 blocker don't correct the real problem : nobody seems to care about
 windows users. This is relatively easy to merge, we must improve 1.12
 quality including this PR.

 In my opinion, the problems of the mixxx project aren't marketing or
 software quality, but two others :

 - The lack of release management process. We need to know when are the
 new functionnality merge windows, when we are in feature freeze, what
 and how we should consider blockers, and so on. and we need someone / a
 team that dispatch remaining work to achieve release with a clearly
 stated date or quality and focus every developpers on correcting
 remaining bugs when we are about to release (for example avoid wasting
 time talking about coding style during beta cycle). With a release
 managemen process, the goal won't shift, or only in a controlled way.

 - The lack of decision process. This project is only driven by strong
 consensus. When we don't have an overall agreement, nothing is done. it
 is normal, in real life, that different people have different opinions.
 We need a way to choose between different opinions. Either with a strong
 project leader, or with a published process (like voting for example).
 This should be published.

 ---
 Sébastien Blaisot



--
___
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] change importance and milestone for bug lp:1464975

2015-06-14 Thread Sébastien Blaisot

Hi,

Can anybody change importance to low and milestone to 1.12 for bug 
lp:1464975 ?

I can not do it.

Thanks,

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] mapping file name conventions

2015-06-14 Thread Sébastien Blaisot

Le 14/06/2015 18:24, Be a écrit :
 What about renaming all the MIDI scripts to end with .midi.js and the 
 HID scripts to .hid.js?

 On 06/14/2015 11:08 AM, Sébastien Blaisot wrote:
 Le 14/06/2015 17:59, Be a écrit :
 Do we really need the word scripts in the script files? Isn't that
 redundant with .js?

 We need a way to differentiate from hid.js.
 What about renaming all the MIDI scripts to end with .midi.js and the 
 HID scripts to .hid.js?

Usually, scripts.js are common for midi and hid usage. They are called 
by both midi.xml file and hid.js file.

scripts.js defines functions that are mapped to midi controls by 
midi.xml file and to hid controls through his.js file.

so, technically, scripts.js is in fact common functions.

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

2015-06-14 Thread 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] most wanted mappings

Le 12/06/2015 17:03, Be a écrit :
 The recent update of the hardware compatibility tables shows that we
 don't have many mappings for controllers have not been discontinued.

There is mapping for some of them in the forum.
Doing a simple search with mixxx + brand name + model name gives forum 
entries with mappings attached.
We should probably take them out of forum and include in mixxx
For example :
Electrix Tweaker http://mixxx.org/forums/viewtopic.php?f=7t=7189
Behringer CMD MM-1 http://www.mixxx.org/forums/viewtopic.php?f=7t=6201


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

[Mixxx-devel] change milestone for bug lp:1457618

Hi,

Can someone change milestone to 1.12 for bug lp:1457618

It seems I can't do that.

Thanks,

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

[Mixxx-devel] NSIS setup help

Hi all,

I'm trying to update my windows build env with NSIS to build packages 
(in order to test my fix for lp:1457618 before making a PR).

I've read NSIS wiki page, but it's a bit outdated
http://www.mixxx.org/wiki/doku.php/build_windows_installer

I have some questions :
* Do I need NSIS v2.46 or NSIS v3.0b1 ?
* Are there any plugin/complement I need to install to be able to build 
mixxx installer ?
* Where do I find needed vcredist (what version), and where do I need to 
have it saved ?

help will be greatly appreciated as I'm actually going around in circles

Thanks,

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] NSIS setup help