Re: [Mixxx-devel] 1.12 -> trunk merge needs help
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. (Speaking of the release, we're just waiting on the shoutcast fix and then we'll do it. How important to the release is getting my build server in production? I expect we'll need to keep the existing one around as long as 1.12 is supported so as not to change anything about the build environment during the support cycle. My preference would be to move to the new build server now, do a Release Candidate to verify nothing broke as a result of the build env change, then release from there so we can retire the old build server sooner. The only limitations are my availability to finalize the build envs and what to do about the OSX VM. I have more time now than I did before, so I figure I can get the Windows and Ubuntu builders going within the next couple weeks. Sincerely, Sean M. Pappalardo "D.J. Pegasus" Mixxx Developer - Controller Specialist smime.p7s Description: S/MIME Cryptographic Signature -- ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] 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. In general I don't think we'll be doing maintenance releases. If there are showstopper bugs that affect both branches, we can do individual cherrypicks of 1.13 back to 1.12. But my intent is, after we release 1.12, to immediately branch trunk for alpha of the next release. > > > (Speaking of the release, we're just waiting on the shoutcast fix and > > then we'll do it. > > How important to the release is getting my build server in production? I > expect we'll need to keep the existing one around as long as 1.12 is > supported so as not to change anything about the build environment > during the support cycle. We have a build server that produces correct builds, so for this release the new build server is not critical. But I'd like to move to the new server for the next release. > > My preference would be to move to the new build server now, do a Release > Candidate to verify nothing broke as a result of the build env change, > then release from there so we can retire the old build server sooner. I don't see a reason to throw that particular monkey wrench into the mix. For the current release let's stick with what we've got. However I would be in favor of getting master builds set up on the new server right away. We can even have the new server make 1.12 builds, but for now the current server will remain canonical. > > The only limitations are my availability to finalize the build envs and > what to do about the OSX VM. I have more time now than I did before, so > I figure I can get the Windows and Ubuntu builders going within the next > couple weeks. I see no reason to hesitate :). Two envs is better than none. 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] 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 1.12 bugfixes into master. (Speaking of the release, we're just waiting on the shoutcast fix and then we'll do it. It sounds like there's a freeze on shutdown we need to fix, but otherwise it's mostly good) -- ___ 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] OpenGLES2.0 accelerated Waveform on PI2
Hello everyone, thats my first post on the mixxx-mailinglist and i am happy to join you :) I am working on project which basicly wants to create a opensource CDJ-like USB-player with a raspberry pi 2 and mixxx (as the original CDJ is f***ing expensive). Thus i need to port mixxx to the pi and make some performance improvements to make it usable there. I am currently trying to get GLES2.0 working on the waveform, as the fps are really low with the current implementation. I already wrote some code for GLES2.0 waveforms: https://github.com/julled/mixxx But it looks like mixxx still uses a softwarerenderer via the "libgl1-mesa-dri" package. (info here: https://www.raspberrypi.org/forums/viewtopic.php?t=31972=290309) Any ideas how i could force to use GLES2.0?? I think this could involve a big recoding of the GUI to use a escontext for the waveform. Further detailed information and description of my plan is provided in that forumpost: http://www.mixxx.org/forums/viewtopic.php?f=1=7475 Cheers Julian -- ___ 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
Daniel has already migrated his changes for Windows (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: > 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 1.12 bugfixes into master. > > (Speaking of the release, we're just waiting on the shoutcast fix and > then we'll do it. It sounds like there's a freeze on shutdown we need > to fix, but otherwise it's mostly good) > > > -- > ___ > 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
