Re: [Mixxx-devel] sync button and LONGPRESSLATCHING for master sync

There are lots of situations where DJs just want a one-shot sync without locking two tracks together. This is especially true if they are going to do any scratching tricks like backspins or vinyl break stops. And, most DJ applications and hardware still operate on the "tap once to sync" and

[Mixxx-devel] [Fwd: Jason (@coolacid) mentioned you in conversation on Twitter!]

FYI: https://github.com/coolacid/Mixxx-Controllers-CMD Are these controllers we support yet?  Forwarded Message From: Jason (via Twitter) To: Mixxx Subject: Jason (@coolacid) mentioned you in conversation on Twitter! Date: Thu, 09 Feb

[Mixxx-devel] a note about package management

Does this apply to our home-rolled packages: """ Dear package managers: dependency resolution results should be in version control If your build depends on a non-exact dependency version (like “somelibrary >= 3.1”), and the exact version gets recomputed every time you run the build, your

[Mixxx-devel] forum registration? [Fwd: Jay Ashworth (@_Baylink) mentioned you in conversation on Twitter!]

Might be someone with firewall issues again. Should we add a message to explain what people should try? Forwarded Message > From: Jay Ashworth (via Twitter) > To: Mixxx > Subject: Jay Ashworth (@_Baylink) mentioned you in conversation

[Mixxx-devel] Introducing the Mixxx Code of Conduct

If you watch commits to master carefully, you may have noticed a new file appear recently, CODE_OF_CONDUCT.md. This is the first of what will be a series of documents establishing a more explicit set of community standards and practices for the Mixxx Project. Codes of Conduct are not just a fad

Re: [Mixxx-devel] garbage JACK client name?

It looks like we're taking a pointer to a temporary, maybe that's the issue? I'd be surprised if SetJackClientName doesn't make a copy, but it looks like it might not be. On Wed, 2016-04-13 at 10:03 +0300, Сергей (zezic) wrote: > I can confirm this. > > 13.04.2016, 02:50, "

[Mixxx-devel] garbage JACK client name?

I am using mixxx with JACK, and with 1.12 the JACK client name shows up as Mixxx, but when I use master, I get garbage characters. Has anyone else seen this? -- Find and fix application performance issues faster with

[Mixxx-devel] Hercules DJControl Compact progress update

Done: * Most basic knobs and pots * jog and pitch adjustment * loop, cue, and sample unshifted actions TODO: * shift actions * figure out how to use "fx" mode effectively (just on/off?) * record button * "automix" button (probably autodj on/off) * turn off lights on shutdown probably another

[Mixxx-devel] ubuntu build is... "unstable"?

http://builds.mixxx.org:8081/jenkins/job/master/architecture=amd64,platform=ubuntu/436/console looks like it's having trouble uploading or something? SSH: Connecting with configuration [downloads-hostgator.mixxx.org] ... SSH: EXEC: STDOUT/STDERR from command [cd public_html/downloads/builds &&

[Mixxx-devel] every build broken

ubuntu is just a buildbot error. windows -- oh hey that's my test! /IC:\usr\include\taglib /Ilib\qtscript-bytearray /Ilib\reverb /Ilib \hidapi-0.8.0-rc1\hidapi /Ilib\xwax /Ilib\scratchlib /Ilib \vamp-2.3 /Ilib\gtest-1.7.0\include /Ilib\gmock-1.7.0\include /Ilib \benchmark\include

Re: [Mixxx-devel] every build broken

. Pegasus wrote: > > On 01/29/2016 06:31 AM, Owen Williams wrote: > > Boo C++11 support on anything except linux. I'll fix these. > > Perhaps we should add tests for C++09, 11 and 13 support so we don't > have to find out by trial-and-error if/when they're supported o

Re: [Mixxx-devel] every build broken

I'm happy with the system the way it is. The only flaw is that we don't get automatic emails when a build fails. On Fri, 2016-01-29 at 08:41 -0800, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 01/29/2016 08:25 AM, Owen Williams wrote: > > The build server is the correct place fo

Re: [Mixxx-devel] every build broken

(emails with a link to the console output, particularly) On Fri, 2016-01-29 at 12:53 -0500, Owen Williams wrote: > I'm happy with the system the way it is. The only flaw is that we don't > get automatic emails when a build fails. > > On Fri, 2016-01-29 at 08:41 -0800, Sean M. Papp

Re: [Mixxx-devel] osx build failure

org:8081/jenkins/job/master/architecture=amd64,platform=macosx/423/ Revision: dbe26b37f80da13fc476e1cc2868aa072341c843 On Thu, 2016-01-28 at 20:38 +0100, Daniel Schürmann wrote: > Fixed in [master dbe26b3] > > Am 28.01.2016 um 19:27 schrieb Owen Williams: > > In

[Mixxx-devel] osx build failure

In file included from /Users/mixxx/buildserver/environment/intel-osx10.7/Qt-4.8.6/lib/QtCore.framework/Headers/QMetaType:1: /Users/mixxx/buildserver/environment/intel-osx10.7/Qt-4.8.6/lib/QtCore.framework/Headers/qmetatype.h:256:5: warning: 'register' storage class specifier is deprecated

Re: [Mixxx-devel] latest windows failure

dsourceproxy.obj] Error 2 scons: building terminated because of errors. On Mon, 2016-01-25 at 13:23 -0800, RJ Ryan wrote: > Sorry about that -- fixed > in > https://github.com/mixxxdj/mixxx/commit/20d7d532435a885f8bffe1b4ca1b7a3dda20db7d > > On Mon, Jan 25, 2016 at 1:14 PM, Owen William

[Mixxx-devel] latest windows failure

/Ilib\scratchlib /Ilib\vamp-2.3 upgrade.cpp src\preferences\upgrade.cpp(194) : error C2679: binary '=' : no operator found which takes a right-hand operand of type 'ConfigObject *' (or there is no acceptable conversion) c:\mixxx\environments\2.0-x64-debug\build

Re: [Mixxx-devel] Windows 10 warning

can you be specific? On Thu, 2016-01-21 at 17:21 -0600, Be wrote: > Many users have been reporting a variety of peculiar issues with > sound > in Mixxx on Windows 10. Would it be a good idea to make some sort > official recommendation to Windows users to not upgrade to Windows 10 > yet? > >

[Mixxx-devel] build server back up

sorry for the delay -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective

Re: [Mixxx-devel] Help to resize "Dark Metal" skin.

One big gotcha is that for resizing to work, the WidgetGroup *must* have a Layout, either horizontal or vertical, even if there's only one element inside it. feel free to ping me on IRC (ywwg) and I'll see if I can help On Tue, 2016-01-12 at 23:46 +, Jorge Rosa wrote: > Hello all, > > > I

Re: [Mixxx-devel] windows build failing on opus

b to the opusfile.lib > linker settings. > > Who can do this? > > > Thank you, > > > Daniel > > > > > > > > >

[Mixxx-devel] windows build failing on opus

win64_build\widget\wwidgetstack.obj LINK : win64_build\mixxx.exe not found or not built by the last incremental link; performing full link Creating library win64_build\mixxx.lib and object win64_build\mixxx.exp opusfile.lib(opusfile.obj) : error LNK2019: unresolved external symbol

Re: [Mixxx-devel] critical: 2.0 windows build broken

as failure Recording test results ERROR: Step ‘Publish JUnit test re On Fri, 2015-12-25 at 23:33 +0100, Daniel Schürmann wrote: > Fixed! > > Am 25.12.2015 um 20:55 schrieb Owen Williams: > > C:\mixxx\workspace\1.12 > > -release\architecture\amd64\platform\windows\src\contro

[Mixxx-devel] successful 1.12 build

jenkins just built all 1.12 targets successfully. Is git5752 the build we've all been waiting for? (Jenkins keeps hanging up on contacting IRC, btw. Thus all the builds were created but the job isn't "done") --

[Mixxx-devel] critical: 2.0 windows build broken

C:\mixxx\workspace\1.12 -release\architecture\amd64\platform\windows\src\controllers/midi/midic ontroller.h(66) : error C2061: syntax error : identifier 'int32_t' scons: *** [win64_build\controllers\controllermanager.obj] Error 2 scons: building terminated because of errors. Build step 'Execute

Re: [Mixxx-devel] Worxmas!

Yeah more like that, like just as the release announcement On Tue, 2015-12-15 at 08:58 -0800, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 12/15/2015 07:40 AM, Owen Williams wrote: > > It would be fun if we could work with DJWorx to have a Mixxx Christmas > > Present -

Re: [Mixxx-devel] Worxmas!

It would be fun if we could work with DJWorx to have a Mixxx Christmas Present -- free dj software for everyone! On Mon, 2015-12-14 at 22:47 -0800, Sean M. Pappalardo - D.J. Pegasus wrote: > Hello everyone. > > I just saw that DJWorx's "12 days of Worxmas" have begun and wanted to > pass along

Re: [Mixxx-devel] s4 wiki

Ah, sorry, I misread. Loop Move is working fine, it's only the loop size selector that's not. On Mon, 2015-12-14 at 06:48 -0800, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 12/13/2015 04:48 PM, Owen Williams wrote: > > the problem is the 7-segment digit readout, like I

[Mixxx-devel] s4 wiki

I figure a *lot* of traktor users will want to try out mixxx by way of this controller, so I'm trying to make the instructions a little more inclusive and introductory than usual. http://mixxx.org/wiki/doku.php/traktor_s4_mk2

[Mixxx-devel] softtakeover fails only on win32

[ RUN ] SuperLinkTest.Softtakeover ConfigObject: Could not read "C:/mixxx/workspace/1.12-release/architecture/i386/platform/windows/src/test/test_data/test.cfg" src\test\super_link_test.cpp(118): error: Value of: m_pControlValue->get() Actual: 0.55 Expected: 0.1 Warning: Test leaked

Re: [Mixxx-devel] s4 wiki

the problem is the 7-segment digit readout, like I said. I had to return the controller before I could implement that On Sun, 2015-12-13 at 16:29 -0800, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 12/13/2015 11:41 AM, Owen Williams wrote: > > http://mixxx.org/wiki/doku.php/tr

[Mixxx-devel] thread not dying

I see this every time I exit: Warning [Main]: DEBUG ASSERT: "isRunning()" in file src/engine/sidechain/engineshoutcast.cpp, line 107 Warning [Main]: EngineShoutcast:~EngineShoutcast(): Thread didn't die. Ignored but add this to bug report if problems rise! Since this is a debug assert, it will

[Mixxx-devel] downloads.mixxx.org down

as reported on twitter. returning 403 -- Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development

Re: [Mixxx-devel] First post and questions about translations

Please follow the unsubscribe instructions at: https://lists.sourceforge.net/lists/listinfo/mixxx-devel On Tue, 2015-11-24 at 08:09 +, Gontran Bonaert wrote: > Hello, > > I've requested to be removed from this group but i do still receive > emails. > > Could you please remove this

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

ixxxdj/mixxx +000d906cb90481ea05ca72d15572950b649327d02a502a1492cf00011265a65b92a169ce0705e...@reply.github.com> > To: mixxxdj/mixxx <mi...@noreply.github.com> > Cc: Owen Williams <owen-git...@ywwg.com> > Subject: Re: [mixxx] Incorporate new mapping from bestdani on the > forums. Thanks! (#780) > Date: Thu, 19 Nov 2015 07:01:47 -0800 &

Re: [Mixxx-devel] Welcome Taglib 1.10

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

Re: [Mixxx-devel] Mixxx releases moving forward

Also, builds will still appear in the http://downloads.mixxx.org/builds/1.12/release/?C=M;O=D and http://downloads.mixxx.org/builds/1.12/debug/?C=M;O=D locations, but the filenames will now say 2.0-rc1 On Tue, 2015-11-17 at 17:05 -0800, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 11/17/2015

[Mixxx-devel] new master failure: missing WAV files

tests are failing because the wave files are missing, not sure why that is -- could be a jenkins-specific problem: RUN ] SoundSourceProxyTest.seekForward ConfigObject: Could not read "C:/mixxx/workspace/master/architecture/amd64/platform/windows/src/test/test_data/test.cfg" Seek forward

Re: [Mixxx-devel] an intern program to consider

r. > >> > >> Do you plan to participate in the next round? > >> > >> Kind regards, > >> > >> Daniel > >> > >> > >> Am 06.11.2015 um 18:09 schrieb Owen Williams: > >>> Aside from Google Summer of Code there

Re: [Mixxx-devel] an intern program to consider

t; 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 r

[Mixxx-devel] an intern program to consider

Aside from Google Summer of Code there are other internship programs that we could try to take advantage of. For instance, Outreachy: https://www.gnome.org/outreachy/ It's a small program, but one that could be really useful.

Re: [Mixxx-devel] an intern program to consider

rtunately this seams to be only for US residents. > The student application process has already started, so it is a bit late > for this year. > > Do you plan to participate in the next round? > > Kind regards, > > Daniel > > > Am 06.11.2015 um 18:09 schrieb O

Re: [Mixxx-devel] an intern program to consider

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

Re: [Mixxx-devel] builds succeeded!

http://downloads.mixxx.org/builds/1.12/release/?C=M;O=D or http://downloads.mixxx.org/builds/1.12/debug/?C=M;O=D On Sat, 2015-10-31 at 18:39 +0100, Max Linke wrote: > Hi > > where can I find the current builds you produced? > > best Max > > On 10/30/2015 02:15 PM, Owen Wi

[Mixxx-devel] builds succeeded!

Due to now-fixed build server issues, for the first time in a long time, a round of 1.12 builds succeeded. I would like to get a set of builds to testers who can beat on the shoutcast functionality. If we get minimal reports of problems (e.g., the usual people who can't figure out how to set up

Re: [Mixxx-devel] builds succeeded!

On Fri, 2015-10-30 at 20:15 +0100, Daniel Schürmann wrote: > Hi Owen, > > very nice! It looks like Mixxx 1.12 will be under the Christmas tree. :-) > > > However I do not understand: > > > I would appreciate if everyone would put master branch PRs aside for > a couple weeks while we wrap

[Mixxx-devel] shoutcast build fail on windows

http://builds.mixxx.org:8081/jenkins/job/1.12-release/architecture=i386,platform=windows/144/console /IC:\usr\include\taglib /Ilib\hidapi-0.8.0-pre\hidapi /Ilib\xwax /Ilib \scratchlib /Ilib\vamp-2.3 engineshoutcast.cpp src\engine\sidechain\engineshoutcast.cpp(24) : warning C4005: 'WIN32' : macro

Re: [Mixxx-devel] 1.12 -> trunk merge needs help

should be safe if we just choose the > SoundSource and TagLib files from master in case of conflicts. > > On 10/15/2015 02:05 AM, Owen Williams wrote: > > Can someone carefully do a merge from 1.12 into trunk? There are a > > bunch of conflicts with the soundsource files. > &g

Re: [Mixxx-devel] wiki spam

I don't have admin access on the wiki. Anyone else? On Mon, 2015-10-19 at 19:17 -0500, Be wrote: > The same user has again vandalized the front page of the wiki. > > On 10/09/2015 10:02 AM, Be wrote: > > The user seoline has repeatedly been replacing wiki pages with spam. > > Could this user be

[Mixxx-devel] broadcast-fixes-1.12 build failure

RJ set up a special target in Jenkins for the broadcast-fixes branch. It is failing: http://builds.mixxx.org:8081/jenkins/job/1.12-broadcast-fixes-release/architecture=amd64,platform=macosx/9/console src/engine/sidechain/enginenetworkstream.cpp:226:19: error: use of undeclared identifier

Re: [Mixxx-devel] 1.12 -> trunk merge needs help

ows > (UTF-16/wchar_t) from > 1.12 to master separately. It should be safe if we just choose > the > SoundSource and TagLib files from master in case of conflicts. > > On 10/15/2015 02:05 AM, Owen Williams wrote: > > Ca

Re: [Mixxx-devel] 1.12 -> trunk merge needs help

tely. It should be safe if we just choose > the > SoundSource and TagLib files from master in case of conflicts. > > On 10/15/2015 02:05 AM, Owen Williams wrote: > > Can someone carefully do a merge from 1.12 into trunk? > There are a >

[Mixxx-devel] 1.12 windows build fixing

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

Re: [Mixxx-devel] 1.12 -> trunk merge needs help

On Wed, 2015-10-14 at 17:13 -0700, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 10/14/2015 05:05 PM, Owen Williams wrote: > > Until the > > release we need to keep incorporating 1.12 bugfixes into master. > > Uh, we need to keep doing that until 1.13 is released.

[Mixxx-devel] 1.12 -> trunk merge needs help

Can someone carefully do a merge from 1.12 into trunk? There are a bunch of conflicts with the soundsource files. We have to be very careful making changes to soundsource files because there has been so much divergence since the backend change. Until the release we need to keep incorporating

[Mixxx-devel] master branch builds fixed!

After much trial and error, the master branch is now building on all of our platforms with the Jenkins build machine. Thanks to Uwe and RJ for committing multiple speculative fixes while I addressed the machine's overheating issues. We are actively pursuing a long-term build solution that does

[Mixxx-devel] build server back up

I applied new thermal grease to the cpu heatsink and it is running much much cooler now. Hopefully the server will be more stable. owen -- ___ Get Mixxx, the #1 Free MP3 DJ

[Mixxx-devel] build server back down

I tried to improve the airflow / cooling situation of the build server, and made it worse. I think I can get it back to a working state if I get some arctic silver, but until then the build server is down. owen --

[Mixxx-devel] Mixxx call for photos

I posted a Facebook thread asking for pictures of DJs using Mixxx. I'd like to use them for the website when we make the release. Here is the post: https://www.facebook.com/permalink.php?story_fbid=10152941413860213id=21723485212 If you have facebook, please check it out and post a photo if

[Mixxx-devel] build server is back

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

Re: [Mixxx-devel] build server is back

/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

[Mixxx-devel] osx build failure in master

In file included from src/analyserqueue.cpp:12: In file included from src/library/trackcollection.h:27: In file included from src/library/basetrackcache.h:20: src/util/memory.h:72:10: fatal error: 'type_traits' file not found #include type_traits ^ 6 warnings and 1 error generated. scons:

[Mixxx-devel] windows build failure in master

can someone check this out? http://builds.mixxx.org:8081/jenkins/job/master/architecture=i386,platform=windows/372/console c:\mixxx\workspace\master\architecture\i386\platform\windows\plugins\soundsourcemediafoundation\soundsourcemediafoundation.h(76) : error C2526:

Re: [Mixxx-devel] Deere state

, Daniel 2015-07-31 2:34 GMT+02:00 Owen Williams owilli...@mixxx.org: I'm going to be pretty hands-off with Deere and I'm hoping other people can step up and make changes. Jus has veto authority with respect to style changes

Re: [Mixxx-devel] Deere state

On Fri, 2015-07-31 at 18:19 +0200, Daniel Schürmann wrote: I am trying to keep the amount of work to a minimum to expedite the release. How is this related to the view menu? Thanks to Jercaianu Adding a new view option is a 10 lines patch around

Re: [Mixxx-devel] Deere state

the same 2x2 fx approach Shade has. This way the skins will be consistent and we avoid space issues. 2015-07-31 18:44 GMT+02:00 Owen Williams owilli...@mixxx.org: On Fri, 2015-07-31 at 18:19 +0200, Daniel Schürmann wrote: I am trying to keep the amount of work

Re: [Mixxx-devel] Deere state

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 On Fri, 2015-07-24 at 16:11 +0200, S.Brandt wrote:

Re: [Mixxx-devel] Deere state

. There text is more readable, but it is still a bit too small. The buttons next to knobs are also too small. Gain should be renamed to Master gain for clarity. I feel that the skin options panel is awkward. Those controls should be moved to the global View menu. On 07/30/2015 10:09 AM, Owen

Re: [Mixxx-devel] Deere state

. Tooltips are not showing for the small buttons to the right of the overview waveform. On 07/30/2015 07:06 PM, Owen Williams wrote: Please remember that the global view menu is frozen for 1.12. From now on any changes to Deere should be restricted to the skin files only. One option

Re: [Mixxx-devel] Deere state

and add commits to this open PR. We do the same for the LibraryConcurentRefactoring branch. Am 24.07.2015 um 16:23 schrieb Owen Williams: How about we create a sub-branch of 1.12 and merge your work there, and then we can have others help out. When it's in good shape we can merge it back

Re: [Mixxx-devel] 1.12 release progress

at 13:51 -0500, Be wrote: https://bugs.launchpad.net/mixxx/+bug/1462061 https://bugs.launchpad.net/mixxx/+bug/1458380 (maybe an issue with the Windows build environment?) https://bugs.launchpad.net/mixxx/+bug/1277274 On 07/23/2015 01:21 PM, Owen Williams wrote: Can you link me to the bugs

Re: [Mixxx-devel] 1.12 release progress

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

Re: [Mixxx-devel] Latenight widgetgroup borders

to the view menu the missing layout options (show/hide crossfader, EQ, mixer, library, spinnies and 2/4 decks) and maybe find a more logical order and grouping for it. The next logical step would be to add hide/show EQ to shade (and Deere?) 2015-06-26 19:18 GMT+02:00 Owen Williams owilli

Re: [Mixxx-devel] Latenight widgetgroup borders

The top row of selectors is not ideal, I agree. But adding skin-specific options to app-wide menus gets painful quickly. If you add hide crossfader to the menu you'll also have to add support for hidden crossfader to Deere and Shade as well. Otherwise people using those skins will file bugs

Re: [Mixxx-devel] Latenight widgetgroup borders

I think if you make your own fork of LateNight you'll find it can be a little fiddly, but rewarding. I think we have consensus that LateNight has enough options as it is. The borders are defined in style.qss, using ObjectName to choose which css rule to apply. Use --developer mode and

Re: [Mixxx-devel] Latenight widgetgroup borders

There's a point at which it makes more sense to create a new skin than to try to have one skin that does everything. I think we are at that point :). On Thu, 2015-06-25 at 11:48 +0200, Thorsten Munsch wrote: Have a look into style.qss for the border. Btw. the idea isn't bad. Many people

Re: [Mixxx-devel] merging 1.12 - master

;) On 06/16/2015 08:29 AM, Uwe Klotz wrote: I may provide a resolution of the merge conflicts for the SoundSourceProxy tests. On 06/16/2015 03:13 AM, Owen Williams wrote: Master and 1.12 have diverged to the point where they are not merging cleanly. We need to make sure that bug fixes

[Mixxx-devel] merging 1.12 - master

Master and 1.12 have diverged to the point where they are not merging cleanly. We need to make sure that bug fixes that go into 1.12 get back into master. Can someone who is familiar with the soundsource changes do a merge from 1.12 and resolve the conflicts?

Re: [Mixxx-devel] formating source Code with clang-format

On Thu, 2015-06-11 at 14:08 +, Gavin Swanson wrote: Compromise = 120 Columns No, the people who prefer 80 columns have specific reasons for that value -- specific window sizes, compatibility with existing code, etc etc. My point is that this is a case where there is not a compromise and we

Re: [Mixxx-devel] formating source Code with clang-format

So we have people who prefer 80 columns, and people who prefer unlimited columns. There's not really a compromise position between these two options, so how do we choose? On Wed, 2015-06-10 at 09:28 -0400, Owen Williams wrote: On Wed, 2015-06-10 at 09:16 -0400, RJ Ryan wrote

Re: [Mixxx-devel] formating source Code with clang-format

On Wed, 2015-06-10 at 09:16 -0400, RJ Ryan wrote: The part of clang-format which frees you from having to talk about code style is that there is only one right way to format the code. Letting the developer have any choice in the matter goes against this. Agree. I don't really feel

Re: [Mixxx-devel] LateNight skin (was: release progress)

gain][balance][head mix][head gain][4/2 deck toggle] [Deck 1][Deck 1/2 mixer][Deck 2] waveform 1 waveform 2 waveform 3 waveform 4 [Deck 3][Deck 3/4 mixer][Deck 4] On 06/06/2015 01:04 PM, Owen Williams wrote: thanks as in, you tested it and it works well? I don't want

Re: [Mixxx-devel] formating source Code with clang-format

I agree that 80 columns is restrictive with 4-space tabs. I personally like a variant of the Go formatting rules, which are basically don't worry about line length. I aim for 100, but if something is a few characters over, I let it go long. No one wants to scroll horizontally, but I also

Re: [Mixxx-devel] release progress

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

Re: [Mixxx-devel] c++11 support is here

On Fri, 2015-06-05 at 08:14 -0400, RJ Ryan wrote: Which can pretty much be summarized as use auto to prevent repeating yourself. My rule of thumb is, use auto when the type is long AND easily understandable from the context. So don't use auto instead of QString just because, but do use

Re: [Mixxx-devel] -std=c++11 vs -std=c++0x

We would only be dropping support for this old OS for development, which I think is reasonable. We should be kind to users, but more strict with our developers :). On Fri, 2015-06-05 at 21:13 +0200, Daniel Schürmann wrote: It the c++0x support in gcc 4.6 of our white list is incomplete.

Re: [Mixxx-devel] c++11 support is here

On Fri, 2015-06-05 at 22:30 +0200, Daniel Schürmann wrote: CSAMPLE sample = 0.0; This one. auto should really only be used when assigning from a function whose return value is obvious. --

Re: [Mixxx-devel] release progress

, and have big library open with the results, either as you type or after hitting enter. Just for fun I've attached the Gimp .xcf layers I used for the mockup, which can be used in a paper-doll fashion. ~RAWRR On Thu, 04 Jun 2015 19:01:55 + Owen Williams owilli...@mixxx.org wrote: I

Re: [Mixxx-devel] c++11 support is here

That's what I said? The compiler is free to elide (remove) the temporary+copying whenever it can, but copy constructor must still be accessible On Fri, 2015-06-05 at 23:34 +, Gavin Swanson wrote: http://stackoverflow.com/a/4470763 On Fri, Jun 5, 2015, 7:21 PM Owen Williams owilli

Re: [Mixxx-devel] c++11 support is here

wrote: CSAMPLE sample(0.0); On Fri, Jun 5, 2015, 4:45 PM Owen Williams owilli...@mixxx.org wrote: On Fri, 2015-06-05 at 22:30 +0200, Daniel Schürmann wrote: CSAMPLE sample = 0.0; This one. auto should really only be used when assigning from

Re: [Mixxx-devel] release progress

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

Re: [Mixxx-devel] release progress

feedback. ~RAWRR On Thu, 04 Jun 2015 17:53:57 + Owen Williams owilli...@mixxx.org wrote: On Tue, 2015-06-02 at 15:29 -0400, RJ Ryan wrote: * skin polish (Jus has an active Deere branch) The skins are in kind of bad shape at the moment. They really need polish to bring them

Re: [Mixxx-devel] release progress

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

Re: [Mixxx-devel] Catch-all MIDI mapping

Hi Stephan, that's a good idea -- do you have a launchpad account you can use to file a bug? That's the best way to get this on the list of tasks. I can do it myself, but you'll get the email updates for sure if you do it. cheers, Owen On Thu, 2015-05-21 at 21:53 +0200, s...@cis.ch wrote: Hi

Re: [Mixxx-devel] release progress

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

[Mixxx-devel] Mixxx 1.12 Beta Released

Marcos CARDINOT Markus Kohlhase Matt Mikolay Max Linke metastableBarett Michael Sawyer midzer mutil Nazar Gerasymchuk Nazar tro Gerasymchuk Nico Schlömer Nicu Badescu Nils Goroll Nino Miškić-Pletenac Owen Williams Peter G. Marczis QuentinFaidide raulbehl RJ Ryan Ryan Kramer S.Brandt Sean M

Re: [Mixxx-devel] 1.12 release branch is cut

oh yeah that should be fine. On Wed, 2015-04-22 at 23:20 -0400, RJ Ryan wrote: I was thinking periodic merges from 1.12 to master would work? On Wed, Apr 22, 2015 at 11:13 PM, Owen Williams owilli...@mixxx.org wrote: What's the procedure for keeping bugfixes in sync? cherry

Re: [Mixxx-devel] 1.12 release branch is cut

What's the procedure for keeping bugfixes in sync? cherry-picks? On Wed, 2015-04-22 at 20:23 -0400, RJ Ryan wrote: Please submit all bug-fix PRs to 1.12, not master. Debug and release builds of 1.12 will show up here: http://downloads.mixxx.org/builds/1.12/

Re: [Mixxx-devel] beta deadline suggestion

Sweet! I will install these on my various machines as a sanity check. On Mon, 2015-04-20 at 20:39 -0400, RJ Ryan wrote: Release builds are showing up here: http://downloads.mixxx.org/builds/master/release/ The filenames a little wonky -- fixing that now. The latest release

Re: [Mixxx-devel] beta deadline suggestion

Ah, we still don't have https://github.com/mixxxdj/mixxx/pull/534 in, so the first-run UI experience is very bad right now. On Mon, 2015-04-20 at 20:39 -0400, RJ Ryan wrote: Release builds are showing up here: http://downloads.mixxx.org/builds/master/release/ The filenames a little wonky

  1   2   3   4   >