[Mixxx-devel] Announcement: 1.12 Feature Freeze
We are pleased to announce that Mixxx 1.12 has entered feature freeze. This means that alpha and beta releases are right around the corner, with the goal of releasing a new stable version of Mixxx by April or May. This will be a fantastic release -- check out the awesome stuff we have planned for 1.12: https://launchpad.net/mixxx/+milestone/1.12.0 == What this means for developers == >From now until release we will be focusing almost exclusively on bugs, skin design, and controller presets. There may be rare exceptions when we decide to break feature freeze, but the feature will have to be both extremely compelling and extremely low-risk for breakage. == What this means for designer contributors == We will be pushing out an alpha release as soon as possible so skin designers, control config writers, and translators can start updating their work for the new version. The first alpha will almost certainly have bugs, stability issues, and other problems. Please don't use the alpha for live gigs, and please do file bugs in launchpad. == What's next == If all goes well, we should be able to release a beta version on April 1st -- which should make for a humorous release date. Once we get feedback from the beta we should be able to push out a new stable version by May. Then we can get back to breaking trunk :). -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk ___ 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] mixxx 1.12 master soundclicks
all formats should be supported even without ffmpeg. Ogg should work. On Wed, 2014-03-26 at 23:23 +1200, Waylon Robertson wrote: > well, if i recall correctly, OGG format, with ffmpeg=1, would not read > completely. > > > On Wed, Mar 26, 2014 at 10:59 PM, Tuukka Pasanen > wrote: > Hello, > Just popping in to notice about FFMPEG problem. I haven't read > whole thread but is FFMPEG causing problem with specific > format or all formats? Do you use which version and do you use > AVConv (libav?). > > Thanks, > Tuukka > > > On 26.03.2014 00:30, Waylon Robertson wrote: > > > by not using ffmpeg, what formats do i lose the ability to > > read? > > > > > > On Wed, Mar 26, 2014 at 10:28 AM, Waylon Robertson > > wrote: > > it was ffmpeg. > > > > > > On Wed, Mar 26, 2014 at 10:12 AM, Waylon Robertson > > wrote: > > okay, will test. hoping its so, because ive > > got a set in 9 hours. > > > > > > > > On Wed, Mar 26, 2014 at 10:42 AM, RJ Ryan > > wrote: > > Thats what we'd like you to test :). > > The FFMPEG support is still > > experimental and not meant for live > > use. > > > > > > On Tue, Mar 25, 2014 at 5:38 PM, > > Waylon Robertson > > wrote: > > the clicking noise in > > playback, is caused by it? > > > > > > > > On Wed, Mar 26, 2014 at 2:36 > > AM, Daniel Schürmann > > wrote: > > Ah, then it become > > clear to me. Most > > likely Waylon sees > > the known seek > > issues from the > > FFMPEG branch. > > > > > > > > 2014-03-25 14:22 GMT > > +01:00 RJ Ryan > > : > > > > Waylon -- > > your > > compilation > > thread > > before > > implies you > > are using > > the new > > FFMPEG build > > option. Is > > that > > correct? > > > > > > Could you > > test > > building > > with > > ffmpeg=0? > > > > > > On Tue, Mar > > 25, 2014 at > > 7:22 AM, > > Waylon > > Robertson > > > wrote: > >
Re: [Mixxx-devel] Testing Portaudio Pulseaudio integration
Thanks! This will be great for usecases where latency doesn't matter, like using mixxx as a live-streamer. On Thu, 2014-04-24 at 13:31 +0300, Tuukka Pasanen wrote: > Hello, > First word of warning this is Beta code and It works for me but I don't > have any reasons to believe it works for you and don't eat your pet > gerbil after this you can read on. > > I've been developing Portaudio Pulseaudio hostapi to make my Mixxx > experience more pleasant (ALSA-plugin Pulseaudio integration have it's > weaknesses). Now I have reached the point where this code can be tested. > So if you are adventurous you can download binaries from: > http://download.opensuse.org/repositories/home:/illuusio:/portaudio/ > There is packages for Debian 7.0, openSUSE 12.2-13.1 (Should work on > Fedora also) and Ubuntu 12.04 and 14.04. Deb packages are build from > Debian packages dsc if you like to see patch it can be found on: > https://build.opensuse.org/package/show/home:illuusio:portaudio/portaudio . > > What works: > * Playing and recording in Mixxx > * Change samplerate > * Pulseaudio integration ;) > > What it not working: > * My USB sound card died so choosing sound card is not > working currently (use pavucontrol) > * If you have input and output enable it can crash Mixxx on > start I have nailed this down but haven't got time to fix it. > * Blocking API > > I like hear did it work for you, > Tuukka > > -- > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > ___ > 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 > > -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform ___ 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] Skin API updates!
The following features are now supported in skins:
* Persisting widgetstack state across relaunches of Mixxx. This means
you can save which page a stack is on or if a module is "open" or
"closed." Usage:
* Aligning words inside pushbuttons: left. Also
supports "right" and "center"
* pushbutton CSS styling per-state. Lets you use one CSS definition for
pushed and another for not-pushed, so you can change background or
foreground colors. Usage: In the CSS, do #MyButton[displayValue="0"]
{ } and #MyButton[displayValue="1"] { } where #MyButton is the object
name of the button in question.
I found these all really helpful in making my own skin.
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
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] Skin API updates!
I've updated the LateNight-Wide skin in the developer_skins repo as an
example. I haven't synced up LateNight-Stacked, though.
On Thu, 2014-04-24 at 09:04 -0400, Owen Williams wrote:
> The following features are now supported in skins:
>
> * Persisting widgetstack state across relaunches of Mixxx. This means
> you can save which page a stack is on or if a module is "open" or
> "closed." Usage: persist="true">
> * Aligning words inside pushbuttons: left. Also
> supports "right" and "center"
> * pushbutton CSS styling per-state. Lets you use one CSS definition for
> pushed and another for not-pushed, so you can change background or
> foreground colors. Usage: In the CSS, do #MyButton[displayValue="0"]
> { } and #MyButton[displayValue="1"] { } where #MyButton is the object
> name of the button in question.
>
>
> I found these all really helpful in making my own skin.
>
>
>
> --
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> ___
> 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
>
>
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
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] LateNight-Stacked skin imported
I've moved the LateNight-Stacked skin into trunk since we plan to release it with the beta. It has the following goals: * Usable at a minimum size of 1280x800 with four decks. * Resizes nicely to at least 1920x1080 with no ugly whitespace Right now if the skin is at 1280x800 and the user opens effects and samplers, part of the mixer gets shrunk in an ugly way. I'd prefer it if the samplers and effects were cropped instead, but I couldn't get that to happen. If anyone knows how to fix that, please submit a patch. Other than that I'm not totally happy with the mishmash of png buttons vs CSS buttons, or the positioning of the master sync controls. The waveform ordering might be confusing for some people, should we change it? Also, the highlighting in the library isn't great, but those are bugs in our code I think. Please give it a try and make comments! Owen -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ 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] LateNight-Stacked skin imported
I will make these changes. I also encourage others to start looking at it and figuring out how the new skinning system works and fixing parts that can be improved! On Sat, 2014-05-10 at 18:41 +0200, Daniel Schürmann wrote: > Hi Owen, > > > thank you very much. > > It would be nice if the skin will be usable at 1366 x 768 this is a HD > ready size and common for some laptops (and mine) Losing <40 pixels from the vertical shouldn't be too much of a problem, I'll change the minimum size. > The 2 deck view has a lot of empty space. It would be nice if we can > use it for the library somehow. Most of the height is in the mixer. Probably the best thing to do is make the mixer collapsable like the effects and samplers. > > Can you add a key widget and a clock widget? Finding room for a clock shouldn't be a problem. I'm not sure what a key widget looks like. And we should find space for the logo! > > > kind regards, > > > Daniel > > > > > 2014-05-10 16:13 GMT+02:00 Owen Williams : > I've moved the LateNight-Stacked skin into trunk since we plan > to > release it with the beta. It has the following goals: > > * Usable at a minimum size of 1280x800 with four decks. > * Resizes nicely to at least 1920x1080 with no ugly whitespace > > Right now if the skin is at 1280x800 and the user opens > effects and > samplers, part of the mixer gets shrunk in an ugly way. I'd > prefer it > if the samplers and effects were cropped instead, but I > couldn't get > that to happen. If anyone knows how to fix that, please submit > a patch. > > Other than that I'm not totally happy with the mishmash of png > buttons > vs CSS buttons, or the positioning of the master sync > controls. The > waveform ordering might be confusing for some people, should > we change > it? Also, the highlighting in the library isn't great, but > those are > bugs in our code I think. > > Please give it a try and make comments! > > Owen > > > > > > -- > Is your legacy SCM system holding you back? Join Perforce May > 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > ___ > 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 > > -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ 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] LateNight-Stacked skin imported
Yup that's what I ended up doing. It's not especially pretty but it's a start. On Sat, 2014-05-10 at 21:55 +0200, Daniel Schürmann wrote: > > > Most of the height is in the mixer. Probably the best thing to do > is > > make the mixer collapsable like the effects and samplers. > > > Will it be possible to move the volume sliders beside the eq-knobs for > the two decks case? > > > > > > > > > 2014-05-10 21:33 GMT+02:00 Owen Williams : > I will make these changes. I also encourage others to start > looking at > it and figuring out how the new skinning system works and > fixing parts > that can be improved! > > On Sat, 2014-05-10 at 18:41 +0200, Daniel Schürmann wrote: > > Hi Owen, > > > > > > thank you very much. > > > > It would be nice if the skin will be usable at 1366 x 768 > this is a HD > > ready size and common for some laptops (and mine) > > > Losing <40 pixels from the vertical shouldn't be too much of a > problem, > I'll change the minimum size. > > > The 2 deck view has a lot of empty space. It would be nice > if we can > > use it for the library somehow. > > > Most of the height is in the mixer. Probably the best thing > to do is > make the mixer collapsable like the effects and samplers. > > > > Can you add a key widget and a clock widget? > > > Finding room for a clock shouldn't be a problem. I'm not sure > what a > key widget looks like. And we should find space for the logo! > > > > > > kind regards, > > > > > > Daniel > > > > > > > > > > 2014-05-10 16:13 GMT+02:00 Owen Williams > : > > I've moved the LateNight-Stacked skin into trunk > since we plan > > to > > release it with the beta. It has the following > goals: > > > > * Usable at a minimum size of 1280x800 with four > decks. > > * Resizes nicely to at least 1920x1080 with no ugly > whitespace > > > > Right now if the skin is at 1280x800 and the user > opens > > effects and > > samplers, part of the mixer gets shrunk in an ugly > way. I'd > > prefer it > > if the samplers and effects were cropped instead, > but I > > couldn't get > > that to happen. If anyone knows how to fix that, > please submit > > a patch. > > > > Other than that I'm not totally happy with the > mishmash of png > > buttons > > vs CSS buttons, or the positioning of the master > sync > > controls. The > > waveform ordering might be confusing for some > people, should > > we change > > it? Also, the highlighting in the library isn't > great, but > > those are > > bugs in our code I think. > > > > Please give it a try and make comments! > > > > Owen > > > > > > > > > > > > -- > > Is your legacy SCM system holding you back? Join > Perforce May > > 7 to find out: > > • 3 signs your SCM is hindering your > productivity > > • Requirements for releasing software faster > > • Expert tips and advice for migrating your SCM > now > > http://p.sf.net/sfu/perforce > > ___ > > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > > http://mixxx.org > > > > > > Mixxx-devel mailing list > > Mixxx-devel@lists.sourceforge.n
[Mixxx-devel] [Fwd: Elapsed Automix]
Anyone know if we do this? Forwarded Message From: 'Jay' via feedback Reply-to: Jay To: feedb...@mixxx.org Subject: Elapsed Automix Date: Sat, 17 May 2014 18:02:15 -0400 Hello, Does your software have the option to automatically set the play length of songs to 3.5 minutes and then autofade and play the next song? Thanks in advance. Regards, Jay -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs ___ 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] Calling all OS X testers!
yaaay auto and for(:) and templatedclass>! On Sat, 2014-05-17 at 19:14 -0400, RJ Ryan wrote: > Also, this is exciting: > > $ gcc --version > Configured with: > --prefix=/Applications/Xcode.app/Contents/Developer/usr > --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1 > Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) > Target: x86_64-apple-darwin13.1.0 > Thread model: posix > > > Yes, that's right -- our build compiler is no longer GCC 4.2 -- we can > use C++11 now on OS X! > > > > > On Sat, May 17, 2014 at 7:07 PM, RJ Ryan wrote: > I'll start: > > > 1) Mac OS X 10.9.2 > 2) Intel Core i7 64-bit > 3) Works! > > > I'm particularly interested in whether this works on OS X 10.5 > and 10.6. > > On Sat, May 17, 2014 at 7:05 PM, RJ Ryan > wrote: > We have some new hardware on loan from Owen that we > can do builds on! I've created a brand new OS X build > environment and I need testers to make sure the builds > work. > > > Please install and test: > > http://downloads.mixxx.org/builds/master/mixxx-1.12.0-alpha-master-git4466-macintel64.dmg > > > > This is an Intel 32-bit and 64-bit build for Mac OS X > 10.5 and up. PowerPC is not supported by this > particular build. > > > Ideally, I'd love to get a tester on every version of > OS X and Intel 32-bit / 64-bit. > > > Please test this build out and report: > 1) OS X version from Apple -> About This Mac > 2) 32-bit or 64-bit > 3) Any problems, error messages, etc. you ran into. > > > Thanks a ton, > RJ > > > > > -- > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > ___ > 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 -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs ___ 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] debugging auto dj
I'm trying to debug a problem where certain files added to the DJ queue don't end up there. (specifically, .mp3 files in the Browse tree don't get added.) Where in the code would files be rejected from being shown in the view? -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs ___ 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.-alpha.
If possible, can you submit this patch as a Pull Request on github? That makes it much easier to review and integrate. http://mixxx.org/wiki/doku.php/using_git If you are unfamiliar with git that's ok, we can work with this patch as-is. Owen On Wed, 2014-05-28 at 04:04 -0500, Flats Fixed wrote: > added this to b0177d103adea46a9ced4c145f32069f4fc4b598 > > > > /src/engine/sidechain/engineshoutcast.cpp > > > > > > > > > Attached is a patch that will let the meta data update when songs > change. > > > > -- > FLATS FIXED Emergency repairs flatsfixedbicycles.com > This message has been sent by the most powerful bleeding edge > operating system known to man SLACKWARE64-CURRENT We Get The Slack > Back. It is free. Try it you will never go back just keep the slack. > > > -- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet ___ 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.-alpha.
oh, hm, this might already be fixed in trunk anyway. Check out http://downloads.mixxx.org/builds/master/ On Wed, 2014-05-28 at 04:04 -0500, Flats Fixed wrote: > added this to b0177d103adea46a9ced4c145f32069f4fc4b598 > > > > /src/engine/sidechain/engineshoutcast.cpp > > > > > > > > > Attached is a patch that will let the meta data update when songs > change. > > > > -- > FLATS FIXED Emergency repairs flatsfixedbicycles.com > This message has been sent by the most powerful bleeding edge > operating system known to man SLACKWARE64-CURRENT We Get The Slack > Back. It is free. Try it you will never go back just keep the slack. > > > -- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet ___ 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] load tracks in to playing decks
Why is it even possible to load a track into a playing deck? This setting somehow got switched on for me, and it messed up my set (partystopper) as well as someone else who was borrowing my laptop. I was having trouble thinking of a situation where anyone would want to preempt the current track. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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] load tracks in to playing decks
That's a pretty good use-case, but I would strongly argue that we should fix the preview deck instead of keeping this feature. It's just incredibly dangerous in practice, especially as the number of decks increases and you forget if you're playing deck 2 or 4. Or you load into deck 2 instead of sampler 2. Basically, I'm about to submit a pull request removing it, and I'm not convinced losing rapid previewing outweighs the safety benefit. On Sun, 2014-07-06 at 20:58 -0700, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 07/06/2014 03:18 PM, Owen Williams wrote: > > Why is it even possible to load a track into a playing deck? > > It's useful for rapid previewing. The preview deck only half eliminates > the need since you can't jump around the track with it. > > Sincerely, > Sean M. Pappalardo > "D.J. Pegasus" > Mixxx Developer - Controller Specialist > > -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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] load tracks in to playing decks
On Tue, 2014-07-08 at 08:09 +0200, Daniel Schürmann wrote: > What about only allowing to load a track in a playing deck which is > not playing though master? I think that's a good compromise, although that solution doesn't work for people who use bus outs or deck outs. But I honestly don't think it's too much to ask that the user pause a deck before loading a new track, since the new loaded track doesn't start playing by default anyway. I've done plenty of track previewing without a preview deck, and I never felt slowed down by having to press pause before loading the next track. > > > > Kind regards, > > > Daniel > > > > > > > 2014-07-08 2:54 GMT+02:00 Owen Williams : > That's a pretty good use-case, but I would strongly argue that > we should > fix the preview deck instead of keeping this feature. It's > just > incredibly dangerous in practice, especially as the number of > decks > increases and you forget if you're playing deck 2 or 4. Or > you load > into deck 2 instead of sampler 2. > > Basically, I'm about to submit a pull request removing it, and > I'm not > convinced losing rapid previewing outweighs the safety > benefit. > > > On Sun, 2014-07-06 at 20:58 -0700, Sean M. Pappalardo - D.J. > Pegasus > wrote: > > > > On 07/06/2014 03:18 PM, Owen Williams wrote: > > > Why is it even possible to load a track into a playing > deck? > > > > It's useful for rapid previewing. The preview deck only half > eliminates > > the need since you can't jump around the track with it. > > > > Sincerely, > > Sean M. Pappalardo > > "D.J. Pegasus" > > Mixxx Developer - Controller Specialist > > > > > > > > > -- > Open source business process management suite built on Java > and Eclipse > Turn processes into business applications with Bonita BPM > Community Edition > Quickly connect people, data, and systems into organized > workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > ___ > 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 > > -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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] load tracks in to playing decks
In my case, I was using keybindings to load tracks into decks. I currently use four decks as a kind of preplanning exercise, with a couple stopped tracks that I don't want to load over. So I was trying to load a track into a specific deck, whereas doubleclicking would have overwritten one of my stopped tracks. One workaround for me would be that doubleclick loads into the first empty deck, then the first stopped deck as a second choice. In the other case, the user tried to load into sampler 2 from the right-click menu and hit deck 2 instead. I will doublecheck the default setting for this option. It should definitely be off. On 2014-07-08 13:32, Sean M. Pappalardo - D.J. Pegasus wrote: > On 07/07/2014 05:54 PM, Owen Williams wrote: >> Basically, I'm about to submit a pull request removing it, and I'm not >> convinced losing rapid previewing outweighs the safety benefit. > > And we just heard from Lee Matos in the pull request that he uses it > all the time with vinyl control, which makes perfect sense in that > case. That's a very strong argument for keeping the feature so I am > (now) opposed to removing it. > > (His suggestion of moving it to a command-line option I am opposed to, > however. All configuration options should be in the same place.) > > Just ensure that "load tracks to playing decks" is de-selected by > default. Owen's original issue of "somehow it got selected" deserves > further investigation instead: is there any way the software could > have auto-selected it? Perhaps a corrupt config file? > > Sincerely, > Sean M. Pappalardo > "D.J. Pegasus" > Mixxx Developer - Controller Specialist -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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] Deck 2 quantize causing strange behavior - any ideas?
I think there is an off-by-one-buffer error in the sync code. When you push the sync button, it makes a difference if the deck being synced is processed before or after the deck being synced to. On Thu, 2014-08-07 at 11:07 -0500, Ryan Kramer wrote: > I made this code change > (https://github.com/default-kramer/mixxx/commit/aaf3e1c96dc1cb3d91fcb905570a9d1a65a33e3e) > and was playing around with it last night. (The feature description is here > https://bugs.launchpad.net/mixxx/+bug/1180052) Everything worked great with > one exception. I am hoping that a more experienced Mixxx developer will be > able to give me some insight. > > > I have two decks stuck in loops. Assume the beatgrids are already in > phase. Pushing the new function (which I named > "beats_translate_to_sync") should have virtually no effect. And in the > normal case, it doesn't - the beatgrid may shift by up to 2 samples, > but this does not produce an audible difference when you re-sync to > the new beatgrid. But only on deck 2, and only when deck 2 quantize is > turned on, it shifts by hundreds or even thousands of samples - this > is wrong, and very audible when you re-sync to the new beatgrid. > > > Any ideas? > > > (I'll be busy this weekend so apologies if it takes me a while to > respond - I'll be back at this next week for sure.) > -- > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk > ___ > 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] Deck 2 quantize causing strange behavior - any ideas?
Do you know if it's syncing forward or backwards, for instance? On Tue, 2014-08-12 at 18:43 -0400, Owen Williams wrote: > I think there is an off-by-one-buffer error in the sync code. When you > push the sync button, it makes a difference if the deck being synced is > processed before or after the deck being synced to. > > > > On Thu, 2014-08-07 at 11:07 -0500, Ryan Kramer wrote: > > I made this code change > > (https://github.com/default-kramer/mixxx/commit/aaf3e1c96dc1cb3d91fcb905570a9d1a65a33e3e) > > and was playing around with it last night. (The feature description is > > here https://bugs.launchpad.net/mixxx/+bug/1180052) Everything worked great > > with one exception. I am hoping that a more experienced Mixxx developer > > will be able to give me some insight. > > > > > > I have two decks stuck in loops. Assume the beatgrids are already in > > phase. Pushing the new function (which I named > > "beats_translate_to_sync") should have virtually no effect. And in the > > normal case, it doesn't - the beatgrid may shift by up to 2 samples, > > but this does not produce an audible difference when you re-sync to > > the new beatgrid. But only on deck 2, and only when deck 2 quantize is > > turned on, it shifts by hundreds or even thousands of samples - this > > is wrong, and very audible when you re-sync to the new beatgrid. > > > > > > Any ideas? > > > > > > (I'll be busy this weekend so apologies if it takes me a while to > > respond - I'll be back at this next week for sure.) > > -- > > Infragistics Professional > > Build stunning WinForms apps today! > > Reboot your WinForms applications with our WinForms controls. > > Build a bridge from your legacy apps to the future. > > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk > > ___ > > 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] [Fwd: Re: thanks for the update]
Forwarded Message > From: Owen Williams > To: Brent Racobs > Cc: mixxx-de...@sourceforge.net > Subject: Re: thanks for the update > Date: Wed, 13 Aug 2014 09:31:58 -0400 > > glad to hear it's working well! If you have any interest in helping to > roll packages please let us know. > > cheers, > Owen > > On Wed, 2014-08-13 at 04:15 -0500, Brent Racobs wrote: > > Like to let you know I finally started a git repo for my build script > > I been using for a long time. It is for Slackware 14.1 and current . > > It down loads builds all the dependencies. > > > > Then it grabs your latest mixxx-master.zp and builds and installs and > > updates it. > > > > https://github.com/Drakeo/Slackware-mixxx-devel-build-script > > > > > > Oh here Mixxx on kde5 Slackware current. > > > > Thanks for you hard work. > > > > Brent > > > > > > > > -- > > FLATS FIXED Emergency repairs flatsfixedbicycles.com > > This message has been sent by the most powerful bleeding edge > > operating system known to man SLACKWARE64-CURRENT We Get The Slack > > Back. It is free. Try it you will never go back just keep the slack. > > > > > > > -- ___ 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] Github milestones
I created two milestones in github, 1.12 and 1.13, and assigned a couple of branches to them. As the number of pull requests gets pretty huge, it might be useful to assign a milestone (similar to the bug reports) so we know what to prioritize. -- ___ 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] EQ consolidation and wish time
Can you make a design doc for how you plan to move the built-in EQs into the effect framework? ie where processing will move, any issues with existing CO / skin compatibility, etc. I'm very sensitive to EQ quality and while ours aren't The Best, they work nicely and previous changes have caused problems. So I want to be really sure we know what we're doing when we start rewriting such a core part of the engine. On Thu, 2014-08-14 at 08:22 +0200, Daniel Schürmann wrote: > Hi Mixxx Developers. > > > NIcu and I are working on a EQ Consolidation in Mixxx. We plan a pull > request, that removes the static deck EQs and replace this with an > effect slot dedicated for EQs and connected to the legacy EQ > controls. > > > This way you are able to individual load one of the Mixx EQs or later > a Plug-In EQ (Lv2/VST/Hardware) as Deck EQs. If yo need no Deck EQ, > you van use this slot together with the EQ knobs for any other > effect. > > > Since the EQs are Effects, you can place a EQ on every position where > you can place an Effect, Mic, Aux, Master, Sampler. > > > Currently there are some pending PRs for new EQ effects. They may > extend or replace the current Mixxx EQs. > > How many EQs are suit to Mixxx? Which types we need, which can be > ditched. > What are the usecses? Please consider a static Master EQ and a DJ EQ > used for Mixing. > It is wishing time! :-) > > We may add: > Pure Bessel (Round edged) > Pure Butterworth (Sharp edges / Flat top) > Linkwitz-Riley (Medium edges, linear group delay) > > Bessel LV MIx (Round edged / Minimum Phase / Bit-perfect at unity) > 8-Band graphic > ?-Band parametric > ... > wish/dream EQ > ... > > The Linear Phase EQ, actually works, but only for long buffer sizes, > so not that suitable for Mixxx. > > Which order makes sens, which roll-off is needed (order 8) = -48 > db/Oct? > What is the minimum suitable order in respect to CPU? > > Thank you, > > Daniel > > > > > > > > -- > ___ > 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] attn to our German speakers...
A question got posted on our facebook page, and the translation implies that there's a problem with cue points not getting saved. Can someone reply? https://www.facebook.com/permalink.php?story_fbid=10152206044245213&id=21723485212 thanks, 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] attn to our German speakers...
Can you reply that Mixxx supports 32 cue points, even if he can only see 4 in the skin? He can assign them to a midi controller or keyboard keys. Or he can edit the skin or find a skin that shows more cuepoints. On Tue, 2014-08-19 at 07:46 +0200, Musikpirat wrote: > Am 19.08.2014 um 07:08 schrieb Musikpirat: > > Am 19.08.2014 um 00:06 schrieb Owen Williams: > >> A question got posted on our facebook page, and the translation implies > >> that there's a problem with cue points not getting saved. Can someone > >> reply? > >> > >> https://www.facebook.com/permalink.php?story_fbid=10152206044245213&id=21723485212 > > > > That's indeed described there. Tobias says he uses a lot of cue points > > and they are not stored. > > Have to correct myself. He wants to store lot of cue points. As far as I > know, Mixxx supports one cue point and four hot cues. That seems to be > not enough for his needs. > > Christian > > > -- > ___ > 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] attn to our German speakers...
persisting on the same machine or is he moving to another machine? Obviously it won't work if he's moving to different computers, but they should persist if they are on the same machine. On Wed, 2014-08-20 at 07:13 +0200, Musikpirat wrote: > Seems he has problems with persisting the cue points. He also suggests > to store them directly in the mp3 file. He guesses that Tractor does so > to - if he opens a mp3 file on another PCs the points are still set. > > Christian > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > 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 > > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ 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] attn to our German speakers...
Tell him that :) (and that may not work if the music is not in the same place on both machines, right?) On Wed, 2014-08-20 at 17:26 +0200, Daniel Schürmann wrote: > You can make it work if you want move the machines. > just start Mixxx like that > mixxx --settingsPath /media/daniel/Musik/.mixxx > where .mixxx is a folder in your Musik directory on the external HDD. > > > Am 20.08.2014 14:48, schrieb Owen Williams: > > persisting on the same machine or is he moving to another machine? > > Obviously it won't work if he's moving to different computers, but they > > should persist if they are on the same machine. > > > > On Wed, 2014-08-20 at 07:13 +0200, Musikpirat wrote: > >> Seems he has problems with persisting the cue points. He also suggests > >> to store them directly in the mp3 file. He guesses that Tractor does so > >> to - if he opens a mp3 file on another PCs the points are still set. > >> > >> Christian > >> > >> -- > >> Slashdot TV. > >> Video for Nerds. Stuff that matters. > >> http://tv.slashdot.org/ > >> ___ > >> 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 > >> > >> > > > > > > -- > > Slashdot TV. > > Video for Nerds. Stuff that matters. > > http://tv.slashdot.org/ > > ___ > > 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 > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > 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 > > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ 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] spanish translation
Since the localization forum is very empty, you may just want to post in the General forum and let people know what you are doing. It may also help to watch Youtube videos teaching DJing in Spanish :). On Mon, 2014-08-25 at 17:45 -0300, Leo Combes wrote: > thanks for the reply! > > I am actively translating the application, but I reach one point where > I have too many words that I have doubts. These words are present in > several sentences and want to unify the criteria to be consistent, > then I need ideas. Some english words are too big in spanish or need > many words to be equivalent and probably no fit in the application. > Others not have a word in spanish and remain in original language. > So, I need some ideas and opinions (if I leave a word in english, the > spanish DJ community understand this?) > > Also, I think it is good idea to use the localization forum and allow > the "non devel" community to review this. > > Leo > > 2014-08-23 15:39 GMT-03:00 S.Brandt : > > Thanks for offering your help in translating Mixxx. > > > > Don’t wait, just go ahead and fill the spanish translations - participation > > is rather slow. Strings can always be changed later on by a > > translator/reviewer. > > > > Hints: > > The concordance search in the Transifex translation interface enables > > translators to search for a specific existing word or phrase to ensure a > > coherent translation. To use the concordance search, you can either press > > the ‘c’ key or click on the respective icon in the suggestions tab. > > > > You may also add some terms to the spanish glossary to help other > > translators. > > Glossaries and translation memory (suggestions) are shared across different > > projects (application < >manual). > > > > > > If you have any questions with regards to the Transifex translation service, > > ask away. > > jus > > > > > > On Aug 23, 2014, at 7:11 PM, Leo Combes wrote: > > > > Hola, > > quiero avanzar rápidamente con la traducción al español y necesito > > ayuda y revisión de los DJs de habla hispana. > > > > Hi, > > I want to advance quickly with the translation into Spanish and I need > > help and review of Spanish speaking DJs. > > > > http://mixxx.org/forums/viewtopic.php?f=10&t=6572 > > > > -- > > Slashdot TV. > > Video for Nerds. Stuff that matters. > > http://tv.slashdot.org/ > > ___ > > 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 > > > > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > 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 -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ 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] Debian 8 freeze - 5 November 2014
not so much forgotten as gave up. We're really only blocked on getting the builds made. On Wed, 2014-09-03 at 12:28 -0700, Sean M. Pappalardo - D.J. Pegasus wrote: > Hi everyone. > > I want to encourage the release manager (is that still you, RJ?) to get > v1.12 out by 5 October so that it can be included in the next major > Debian release which is set for 5 November 2014. (For those that don't > know, this is important because many major Linux distributions are based > on Debian, most notably Ubuntu.) > > Based on the activity I've been seeing on this list, the bug tracker and > git, it looks like people have kindof forgotten about the 1.12 freeze. > :) So we need to re-announce a freeze date I suppose and make a branch. > > Sincerely, > Sean M. Pappalardo > "D.J. Pegasus" > Mixxx Developer - Controller Specialist > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > 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 > > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ 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] Debian 8 freeze - 5 November 2014
It looks like we just had the port number wrong, I think the server is still working. On Thu, 2014-09-04 at 07:59 -0700, Sean M. Pappalardo - D.J. Pegasus wrote: > > On 09/04/2014 07:48 AM, Lee Matos wrote: > > We have a windows server but it appears to have gone down. RJ used to > > do builds and he hasn't had time to do them, so we have nobody doing > > builds for any platform. > > Beautiful. > > Well, I happen to have a spare server in my data center that isn't doing > anything at the moment, and I'm already paying for the power to run it, > so I can bring that up as a build server for the time being. I can > manage the Linux and Windows VMs but have absolutely zero experience > with OSX VMs so someone's going to have to assist with that. > > However, I have very limited bandwidth (it costs alot for > enterprise-class redundancy!) so will need to upload builds to somewhere > else for people to download. > > Is RJ still reachable or does anyone else have physical access to the > existing server? If I could copy the VMs and configs, that would be very > helpful. I also need license keys for Windows and OSX. (My agreement > with Microsoft would require me to pay if I use one of my keys.) > > Sincerely, > Sean M. Pappalardo > "D.J. Pegasus" > Mixxx Developer - Controller Specialist > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ 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] Cue points 2.0
These are all good post-1.12 suggestions On Tue, 2014-09-09 at 11:07 +0200, Ferran Pujol Camins wrote: > Done: https://blueprints.launchpad.net/mixxx/+spec/cuepoins-2.0 > > 2014-09-09 8:21 GMT+02:00 Daniel Schürmann : > > Hi Ferran, > > > > Yes! The best both, a bug for every single task and a blueprint to bind > > them. > > > > Some of you requirements are already on the way: > > > >> -Named cue points > > > > Available, maybe the workflow need some love. > > > >> -Unlimited (or huge number) cue points > > > > We have ~36 > > > >> -Loop cue points (stored loops) > > > > Carl Pillot, a GSoC Student was working on this: > > https://github.com/mixxxdj/mixxx/pull/45 > > > > Thank you for working on this! > > > > Kind regards, > > > > Daniel > > > > > > > > > > > > > > > > > > > > 2014-09-09 5:21 GMT+02:00 Ferran Pujol Camins : > >> > >> Mixxx 1.12 will come with 4 decks (n decks?) support. 4-deck mixing > >> requires deep control over what part of each track is playing. Thus, > >> Mixxx needs an improvement over its cue points features for a future > >> release (1.13?). I can think of: > >> > >> -Named cue points > >> -Unlimited (or huge number) cue points > >> -Loop cue points (stored loops) > >> -Cue points custom colours > >> -Cue points list skin widget > >> -Cue points copy, reorder... > >> > >> What do you think? Shall I file a bug for this? (blueprint?) > >> > >> -- > >> Ferran Pujol Camins > >> > >> > >> -- > >> Want excitement? > >> Manually upgrade your production database. > >> When you want reliability, choose Perforce. > >> Perforce version control. Predictably reliable. > >> > >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > >> ___ > >> 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 > > > > > > > -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ 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] Debian 8 freeze - 5 November 2014
Seeing as we're fairly close to being able to make builds for all platforms again, are there any blockers in trunk against releasing a beta as soon as possible? I think the skins are in OK shape, effects work well, etc etc. There's always stuff I'd like to include to make it better, but I can't think of anything that's inexcusable based on our goals for this release. On Tue, 2014-09-09 at 11:49 -0400, RJ Ryan wrote: > > > On Tue, Sep 9, 2014 at 11:42 AM, Sean M. Pappalardo - D.J. Pegasus > wrote: > Hello, RJ. > > That's excellent news all around! Given that, what do you > suppose the prospects are of doing a release as far before 5 > November as possible? (5 October would be ideal.) > > > > Given that we need to do an extensive beta (potentially multiple betas > given how much stuff we're adding) I think it's premature to shoot for > this deadline. > > On 09/09/2014 08:27 AM, RJ Ryan wrote: > The exciting thing about Windows right now is that I > have versioned and > scripted the entire build environment > > With one command you can generate a (x86|x64) > (release|debug) build > environment. > > That _is_ exciting. I assume this covers dependencies as well? > If so, this would finally allow the uninitiated to build Mixxx > from nothing on Windows. Please update the Wiki when you can. > > > Yep, this is every single dependency (and the depedencies' > dependencies -- e.g. zlib, fftw3, etc.). I _think_ it should work on a > fresh Win7 machine with platform SDK, MSVS 2013 Express and the > DirectX SDK installed. > > > Currently everything builds as a DLL but we can switch back to static > linking if need be. If/when we do that we could either add a new > target to every solution or just change it in bulk -- the nice thing > will be that it'll all be version-controlled so we can see what has > been done. > > > > > Sincerely, > Sean M. Pappalardo > "D.J. Pegasus" > Mixxx Developer - Controller Specialist > > > > > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > 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 -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ 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] Debian 8 freeze - 5 November 2014
Yeah it would be nice to include them but GSOC projects definitely shouldn't block any release. Until the work is actually finished the students can consider their payment thanks enough for now :) On Tue, 2014-09-09 at 18:19 +0200, Max Linke wrote: > I would like to include covers as well. It is close to being mergeable and we > kind of promised our students to merge their work into master with our new set > of rules. Besides they both did good work this summer and it would be a nice > thank you to include it into mixxx 1.12. I don't know when Nicu's work is > mergeable and what of his work is best suited for 1.12. > > > best Max > > > On Tue, 09 Sep 2014 12:14:20 -0400 > Owen Williams wrote: > > > Seeing as we're fairly close to being able to make builds for all > > platforms again, are there any blockers in trunk against releasing a > > beta as soon as possible? I think the skins are in OK shape, effects > > work well, etc etc. There's always stuff I'd like to include to make it > > better, but I can't think of anything that's inexcusable based on our > > goals for this release. > > > > On Tue, 2014-09-09 at 11:49 -0400, RJ Ryan wrote: > > > > > > > > > On Tue, Sep 9, 2014 at 11:42 AM, Sean M. Pappalardo - D.J. Pegasus > > > wrote: > > > Hello, RJ. > > > > > > That's excellent news all around! Given that, what do you > > > suppose the prospects are of doing a release as far before 5 > > > November as possible? (5 October would be ideal.) > > > > > > > > > > > > Given that we need to do an extensive beta (potentially multiple betas > > > given how much stuff we're adding) I think it's premature to shoot for > > > this deadline. > > > > > > On 09/09/2014 08:27 AM, RJ Ryan wrote: > > > The exciting thing about Windows right now is that I > > > have versioned and > > > scripted the entire build environment > > > > > > With one command you can generate a (x86|x64) > > > (release|debug) build > > > environment. > > > > > > That _is_ exciting. I assume this covers dependencies as well? > > > If so, this would finally allow the uninitiated to build Mixxx > > > from nothing on Windows. Please update the Wiki when you can. > > > > > > > > > Yep, this is every single dependency (and the depedencies' > > > dependencies -- e.g. zlib, fftw3, etc.). I _think_ it should work on a > > > fresh Win7 machine with platform SDK, MSVS 2013 Express and the > > > DirectX SDK installed. > > > > > > > > > Currently everything builds as a DLL but we can switch back to static > > > linking if need be. If/when we do that we could either add a new > > > target to every solution or just change it in bulk -- the nice thing > > > will be that it'll all be version-controlled so we can see what has > > > been done. > > > > > > > > > > > > > > > Sincerely, > > > Sean M. Pappalardo > > > "D.J. Pegasus" > > > Mixxx Developer - Controller Specialist > > > > > > > > > > > > > > > -- > > > Want excitement? > > > Manually upgrade your production database. > > > When you want reliability, choose Perforce. > > > Perforce version control. Predictably reliable. > > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > > > ___ > > > 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 > > > > > > > > -- > > Want excitement? > > Manually upgrade your production database. > > When you want reliability, choose Perforce. > > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > > ___ > > Get Mixxx, the #1 Free MP3 DJ Mixing
Re: [Mixxx-devel] Windows builds are back
Thanks RJ! On Tue, 2014-09-16 at 17:05 -0400, RJ Ryan wrote: > Jenkins: http://builds.mixxx.org/jenkins > > > Builds are uploaded here: > http://downloads.mixxx.org/builds/master/ > > > All non-release builds (e.g. nightlies) are debug builds -- built with > all debug dependencies, no optimizations, and debug symbols enabled. > > > More to come: > * Building pull requests and running the tests > * PDB files bundled with the installer > * mixxx-test.exe bundled with the installer > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ___ > 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 -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ___ 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] LateNight-Stacked toggle buttons fixed
I forget who had pointed out that LateNight-Stacked wasn't remembering the 4deck or mixer toggle button states. That has now been fixed, so now when you restart mixxx it will remember whether you had 2 or 4 decks, and whether you had turned off the mixer. At this point all of the important UI choices should be persisting, please let me know if not. Owen -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk ___ 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] Question about Mixxx
Why do we remove tracks from the queue at all? That's inconsistent with crates and playlists (not to mention winamp and itunes, right?). And the requeue thing is even weirder, why does that exist? On Fri, 2014-09-26 at 12:07 -0700, Sean M. Pappalardo - D.J. Pegasus wrote: > Hello. > > On 09/26/2014 11:44 AM, Seemanta Dutta wrote: > > My requirements are very simple. I am not a regular DJ in the sense that > > I do not have to 'mix' tracks and do any beatmatching or cueing. My > > music is mainly meant for dancing Tango where songs play one after the > > other in sequence, with 'break' songs every 3 or 4 songs where people > > change partners or go back to sitting on the side of the floor. The DJ > > is still deeply involved durnig the DJing process because he or she has > > to observe the dancers for changes in enerrgy and tweak the playlist > > accordingly. > > Not to deter you from using Mixxx, but it sounds like more traditional > play-from-a-playlist applications would better suit you, like > Clementine, Amarok, WinAmp, etc. Have you looked at those or am I > misunderstanding your use case? > > But to answer your questions: > > > 1. A means to play songs off of a playlist - this is something I need to > > fix and is the reason for my email. > > It sounds like something isn't working right because there shouldn't > have been a regression between 1.11 and 1.12. Please file a bug with > more details so we can track it down. > > > So I want to ask the developers and RJ if it will be too difficult to > > implement a feature wherein songs won't be knocked off the AutoDJ queue. > > That's certainly possible and I would even say easy, since it would just > be a matter of adding (yet another) preference option tied to a small > conditional code block in the play list handler that simply skips the > deletion or re-queuing. But I've never worked on the playlist code myself. > > You should do the work against master then submit a pull request in GIT. > That way the feature can be added to a future Mixxx version. (The 1.11 > code is quite old and much has changed since then.) > > > Sincerely, > Sean M. Pappalardo > "D.J. Pegasus" > Mixxx Developer - Controller Specialist > > -- > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > ___ > 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 -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk ___ 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] Question about Mixxx
On Fri, 2014-09-26 at 21:53 +0200, Daniel Schürmann wrote: > One idea is to implement a cursor that moves over a Playlist and copies > tracks to the AutoDJ queue. But that sounds hard to implement and hard > to use. We've already got that -- you can prepare a playlist and then right click and add it to the Auto DJ queue. As for finding files that were on the Auto DJ playlist, we have the history list already, but that might be too hard to find. Maybe we could just have the top level history item show the most recent history playlist. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk ___ 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] Question about Mixxx
l I need is a way to write my own code > for Mixxx to do what I want it to do. This is the spirit of > open source, after all, isn't it? > > Or is the issue more like to allow tweaking a playlist during > playing? > You can also just save the history as a new playlist after the > course. > Doing it live in the original play-list like in Clementine > does not > suite to Mixxx because it might destroy a well prepared > playlist because > of individual events in a current gig. > > > Yes, I am aware of the history feature. But again, it becomes > too confusing to mentally combine what is in the AutoDJ queue > with what is playing in the decks with the history queue to > figure out where I am with respect to the playlist. I want to > be simply able to manipulate a playlist without having to > worry about losing it. I can later save it after my gig and > start with a clean playlist for my next gig. Really, that's > all I want. > > > One idea is to implement a cursor that moves over a Playlist > and copies > tracks to the AutoDJ queue. But that sounds hard to implement > and hard > to use. > > Any ideas? > > > > Once I get past the problems of 1.12 and have a working setup > with 1.11 version of Mixxx, I would be happy to contribute > code. But getting a working 1.11 development environment on > the Mac is what I am struggling with right now. > > > > > > On Fri, Sep 26, 2014 at 12:53 PM, Daniel Schürmann > wrote: > Hi, > > The auto DJ is a waiting queue! > Knocking of played tracks from the Auto DJ, is the > essence from the > current implementation. > It follows precisely the workflow of a CD or Vinyl DJ > and works well > together with the History feature. > > I would strongly recommend to keep this model, because > it is highly > predictable what will happen next. > > But lets think about how we can support Seemanta > use-case. > > If I got it right, the issue is that the Auto DJ > "playlist" is destroyed > while playing. > Why is this a problem? Is is a problem for the next > course, or already > for the current course? > Do you wish to repeat a a dance during one course? > If you want to replay the set, you can just reload the > history to the > Auto DJ. > Maybe we need a feature to split the history without > restarting Mixxx? > > Or is the issue more like to allow tweaking a playlist > during playing? > You can also just save the history as a new playlist > after the course. > Doing it live in the original play-list like in > Clementine does not > suite to Mixxx because it might destroy a well > prepared playlist because > of individual events in a current gig. > > One idea is to implement a cursor that moves over a > Playlist and copies > tracks to the AutoDJ queue. But that sounds hard to > implement and hard > to use. > > Any ideas? > > Thanks. > > Daniel > > > > > > Am 26.09.2014 21:23, schrieb Owen Williams: > > Why do we remove tracks from the queue at all? > That's inconsistent with > > crates and playlists (not to mention winamp and > itunes, right?). And > > the requeue thing is even weirder, why does that > exist? > > > > On Fri, 2014-09-26 at 12:07 -0700, Sean M. > Pappalardo - D.J. Pegasus >
Re: [Mixxx-devel] Question about Mixxx
As with everything in software, what seems simple often is very much not :) On Fri, 2014-09-26 at 16:10 -0700, Seemanta Dutta wrote: > Good idea, I thought of that. Call me lazy or a slob, but I refuse to > do any sort of mental gymnastics during a dance. > I want the software to take care of everything for me, which in this > case is a simple expectation of being able to play music off of a > playlist. > > > Yet this might be a stop gap solution until I can figure out a proper > solution to this problem. > > > Thanks, > Seemanta > > On Fri, Sep 26, 2014 at 4:07 PM, Owen Williams > wrote: > One thing you might try is using the "requeue" feature, and > having a > special track that you always put at the start of your > playlist called > "---Playlist Top". This could be > a simple > silent mp3 for instance. Then after dancing when you go back > to your > laptop, you can immediately see where the playlist top is and > know how > far into your set you are. > > On Fri, 2014-09-26 at 14:55 -0700, Seemanta Dutta wrote: > > CCing the list. Forgot to include the list by mistake in my > original > > response. Sorry! > > > > On Fri, Sep 26, 2014 at 1:17 PM, Seemanta Dutta > > > wrote: > > > But lets think about how we can support Seemanta > use-case. > > Thanks, I really appreciate the support! > > > > > If I got it right, the issue is that the Auto DJ > "playlist" > > is destroyed > > while playing. > > Why is this a problem? Is is a problem for the next > course, or > > already > > for the current course? > > > > > > When I play Tango music, it follows a strict > pattern. > > > > > > Here are some characteristics of DJing during a > Tango dance > > party: > > > > > > - We play songs in sets of 3 or 4, called a 'Tanda'. > > > > > > - After each Tanda, we have a 'Cortina' which acts > as a > > separator to indicate the end the current Tanda and > beginning > > of the next. A Cortina is usually short, 30-40 > seconds and it > > is music distinct from Tango (Jazz, Pop etc.) so > that dancers > > can know that it is not meant for dancing and is > only for them > > to either change partners or go back to sitting. > > > > > > - Tango music can be of three types :Tango (4/4 time > > signature), Vals (3/4 time signature) or Milonga > (2/4 time > > signature). DJs usually play: TTVcTTMcTTVcTTM... > > Here each capital letter represents a Tanda with 3 > or 4 songs. > > The small 'c' represents a Cortina. So you get the > picture. > > > > > > Hence, TTV means 2 tango tandas followed by a Vals > tanda. The > > 'c' means a Cortina. TTM, similarly means two Tango > tandas > > followed by a Milonga Tanda. > > > > > > And here is the problem I have with Mixxx when I try > to use it > > for DJing Tango: > > > > > > I am also a Tango dancer. So when I DJ, I will > occasionally > > get off the DJ booth and dance with my friends. When > I come > > back to the DJ booth, I want my playlist to be > exactly as it > > was before so that I know where I stand with respect > to the > > songs. I should have a way to know whether I am in > the middle > > of my first or second Tango tanda. And within that > tanda if it > > is the first, second or third song. If the songs > keep getting > > knocked off, it becomes very difficult for me to > come back > >
Re: [Mixxx-devel] LateNight Skin and skining engine questions
Instances of "#FFF" shouldn't be committed -- they are used when I'm trying to figure out where a widget is so I want the white block to be obvious. In css, "#FFF" is white -- you don't have to specify all six digits, so #XYZ is the same as #XXYYZZ. On Wed, 2014-10-01 at 09:49 -0400, RJ Ryan wrote: > Hey Max, > > > Those FgColor/BgColor nodes and friends were part of the legacy > monolithic library widgets (search box, sidebar and table were all one > widget). > > > It's mostly done in the CSS now: > https://github.com/mixxxdj/mixxx/blob/master/res/skins/LateNight/style.qss#L28 > > https://github.com/mixxxdj/mixxx/blob/master/res/skins/LateNight/style.qss#L708 > > > On Wed, Oct 1, 2014 at 9:44 AM, Max Linke wrote: > Hi > > I wanted to look into these two styling bugs. > > https://bugs.launchpad.net/mixxx/+bug/1296308 > https://bugs.launchpad.net/mixxx/+bug/1201079 > > As a start I thought I could look into the new LateNight skin > and check out how > we set the BackGround and ForeGround color there. Ok so lets > look at the > `Library` node in the xml > > ``` /res/skin/LateNight/library.xml > > #585858 <-- gray > #fff <-- something pink > > ``` > > The colors that are defined here are never used in the skin. > From the looks in > our skin parser the colors defined here actually are never > parsed. > > So where do we usually parse the foreground and background > colors for the > library currently? I also noticed that we don't call > 'getLibraryStyle' anymore > for the new 'Library' node, but somehow the image for preview > column is set. > Where is this done? > > best Max > > > -- > Meet PCI DSS 3.0 Compliance Requirements with EventLog > Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI > DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White > paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog > Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > ___ > 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 > > > -- > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > ___ > 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 -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk ___ 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] Gnome AppData integration
Definitely not "2.0+", just 2.0. But we also have an App Store Exception in our license, so it's not even straight GPL-2.0. I'm not sure what the official term for it is. How big should the screenshot be? On Thu, 2014-10-16 at 10:00 +0300, Tuukka Pasanen wrote: > Hello, > Bug #1262882 and Bug #1334301 are about Gnome AppStream and Gnome > software center. I could do them and keep them up dated but then I > need good snapshot from someone who have 16:9 aspect ration and firmly > new Gnome installed (with cool bg image [so how 90' is that?]). > > More about details with screenshot could be found from > http://people.freedesktop.org/~hughsient/appdata/ > > Scroll little bit down and you see correct resolutions. Then is > correct license 'GPL-2.0+'. > > Thanks, > Tuukka > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > ___ > 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 > > -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ 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] Album Cover Support
That model has not worked well in the past. It doesn't matter how many warnings there are, people will see "album art!", turn it on, and then get angry if/when it crashes. The new model I'd like to propose is: * Enable an unstable-but-desirable feature (like cover art) by default in development and nightly builds. * Disable it for release builds. I think this will prevent code rot, which was the biggest problem in the past with optional compile-time features. Everyone doing development will be using the feature and seeing any bugs it has. But then the release is still pristine and won't be compromised. Once the feature is stable, we can flip the flag and allow the feature to go to release. This does require that the compile flag is robust. There have been problems in the past with vinyl control, which is enabled for most builds but disabled for App Store builds. Things work great in development, and then the release build turns out to be broken. Having the buildbot should help prevent that -- we should set up a target to create release builds and run the tests, but not actually make them available for download. Owen On Thu, 2014-10-16 at 09:53 +0300, Tuukka Pasanen wrote: > Hello, > Ok I'm totally with this but I also understand RJ concerns about > hitting unwanted behavior. > Could this be integrated and only turned on if user makes it with BIG > FAT WARNING about > it is little bit experimental and polish it to 1.13? > > Tuukka > > 2014-10-12 15:13 GMT+03:00 Max Linke : > > That is exactly how it works. Currently ew only support local covers. We > > have > > some code to also download covers from amazon but I'm not sure if that will > > make > > it. > > > > Here is the algorithm that decides which cover we are loading. > > > > // Search Strategy > > // 0. If we have just one file, we will get it. > > // 1. %track-file-base%.jpg in the track directory for > > %track-file-base%.mp3 > > // 2. %album%.jpg > > // 3. cover.jpg > > // 4. front.jpg > > // 5. album.jpg > > // 6. folder.jpg > > // 7. anything else found in the folder (get the smallest one) > > > > On Sun, 12 Oct 2014 11:22:17 +0300 > > Tuukka Pasanen wrote: > > > >> Hello, > >> Does this support scenario when you have used something like Beets > >> (http://beets.radbox.org/) and allready have cover.jpg (or something) > >> in every directory that contains music? It's nice to have somekind of > >> downloader but there should be also support people like me who like to > >> organize their music in specific way and have cover art in hand.. > >> > >> Tuukka > >> > >> -- > >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > >> http://p.sf.net/sfu/Zoho > >> ___ > >> 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 > > > > -- > > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://p.sf.net/sfu/Zoho > > ___ > > 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 > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > ___ > 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 > > -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing li
Re: [Mixxx-devel] Album Cover Support
Is taglib really that crash-prone? Is this really a common issue? I think crashing on totally crap data is not completely unreasonable as long as we can figure out some way of making it debuggable. I don't see how processing files for cover art is any different than processing files for audio data, and we don't process audio data in a separate kernel process. On Sat, 2014-10-18 at 15:09 -0400, RJ Ryan wrote: > The main limitation with QtConcurrent is that it uses a single global > thread pool -- and currently we use 4 worker threads in our global > thread pool (for parsing 3rd-party libraries, etc). There is no notion > of auto-scaling or the ability for sensing whether we are overloading > the system inherent in QtConcurrent -- it's just a wrapper around a > thread pool. For something as common and compute heavy as processing > cover art we need more deliberate control. > > TagLib crashes will happen given the extreme diversity of > library-from-hell files out there. We really do need a > separate-process isolation feature for processing untrusted data but > I'm pretty sure we don't have time for that for 1.12 if we want to > release in 2014 :). > > > > > On Fri, Oct 17, 2014 at 7:33 PM, Daniel Schürmann wrote: > > Am 18.10.2014 um 00:31 schrieb Max Linke: > >> I haven't noticed any taglib crashes with mixxx. Plus the covers are all > >> extracted in seperate threads. > > I have not experienced any crashes during the tests as well, so the > > issue is hopefully none. > > I was just trying to collect the point that might be risky. > > By the way: Segfaults in a extra thread will have the same effect than a > > segfault in the main thread, Mixxx will crash. > > So we can either rely on the quality of the new taglib version, or setup > > a quarantine process, that read the tags. > > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > http://p.sf.net/sfu/Zoho > > ___ > > 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 > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > ___ > 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 -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ 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] Album Cover Support
Please answer my second question about why we aren't parsing audio metadata in a separate process. On Sun, 2014-10-19 at 00:35 +, re-cy...@hushmail.com wrote: > "I think crashing on totally crap data is not completely > unreasonable as long as we can figure out some way of making it > debuggable." > > *raises hand* > > As someone who has used Mixxx for live gigs, where it crashed > enough times during various sets to sabotage my reputation as a > promoter and DJ, I want to remind people that software used in live > performances has to be held to the highest possible non-crash > standard. > > I don't care if the thing looks like it was made by kindergarten > students as a class project as long as it queues music properly and > NEVER CRASHES LIVE. > > ~RAWRR > > > On Sat, 18 Oct 2014 23:12:36 + "Owen Williams" > wrote: > >Is taglib really that crash-prone? Is this really a common issue? > > I > >think crashing on totally crap data is not completely unreasonable > >as > >long as we can figure out some way of making it debuggable. > > > >I don't see how processing files for cover art is any different > >than > >processing files for audio data, and we don't process audio data > >in a > >separate kernel process. > > > >On Sat, 2014-10-18 at 15:09 -0400, RJ Ryan wrote: > >> The main limitation with QtConcurrent is that it uses a single > >global > >> thread pool -- and currently we use 4 worker threads in our > >global > >> thread pool (for parsing 3rd-party libraries, etc). There is no > >notion > >> of auto-scaling or the ability for sensing whether we are > >overloading > >> the system inherent in QtConcurrent -- it's just a wrapper > >around a > >> thread pool. For something as common and compute heavy as > >processing > >> cover art we need more deliberate control. > >> > >> TagLib crashes will happen given the extreme diversity of > >> library-from-hell files out there. We really do need a > >> separate-process isolation feature for processing untrusted data > >but > >> I'm pretty sure we don't have time for that for 1.12 if we want > >to > >> release in 2014 :). > >> > >> > >> > >> > >> On Fri, Oct 17, 2014 at 7:33 PM, Daniel Schürmann > > wrote: > >> > Am 18.10.2014 um 00:31 schrieb Max Linke: > >> >> I haven't noticed any taglib crashes with mixxx. Plus the > >covers are all > >> >> extracted in seperate threads. > >> > I have not experienced any crashes during the tests as well, > >so the > >> > issue is hopefully none. > >> > I was just trying to collect the point that might be risky. > >> > By the way: Segfaults in a extra thread will have the same > >effect than a > >> > segfault in the main thread, Mixxx will crash. > >> > So we can either rely on the quality of the new taglib > >version, or setup > >> > a quarantine process, that read the tags. > >> > > >> > > >> > --- > >--- > >> > Comprehensive Server Monitoring with Site24x7. > >> > Monitor 10 servers for $9/Month. > >> > Get alerted through email, SMS, voice calls or mobile push > >notifications. > >> > Take corrective actions from your mobile device. > >> > http://p.sf.net/sfu/Zoho > >> > ___ > >> > 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 > >> > >> - > >- > >> Comprehensive Server Monitoring with Site24x7. > >> Monitor 10 servers for $9/Month. > >> Get alerted through email, SMS, voice calls or mobile push > >notifications. > >> Take corrective actions from your mobile device. > >> http://p.sf.net/sfu/Zoho > >> ___ > >> 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/l
Re: [Mixxx-devel] Album Cover Support
On Mon, 2014-10-20 at 09:01 +0300, Tuukka Pasanen wrote: > Hello, > Can't tell why no parsing in separate process but sound bit harsh to > me and doesn't really fix the problem of crashing.. That's my point, RJ's contention is that if we don't have a separate process, we will get crashes. So I am saying, is it so crashy that we have to delay this feature until we can isolate the process, or can we consider the rare crash due to bad files an acceptable risk. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ 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] Album Cover Support
So far so good! Too bad so few of my tracks have cover art. I'll work on adding cover art support to LateNight soon. Unrelated to the overall quality of the patch -- is there any way we can fix the bug where if the available library columns change, my entire column layout gets fucked up? It's really annoying to carefully lay everything out again. Also, is there any way we can have the full art pop up when the user mouses over the truncated version in the library? On Wed, 2014-11-05 at 20:38 +0100, Max Linke wrote: > I merged the cover art branch into master an hour ago. You can grab the code > and > try it out. If you start from an old config you will have to rescan your > library > to see the covers and likely also activate the column in the libraryview. > Deere > is currently the only skin that uses cover-art widgets outside of the library. > > Many thanks to Marcos for wokring on this during GSoC and Daniel and Ryan for > their help. > > The alpha build should be updated once rryan fixes the faulty OSX build, which > hopefully happens sometime next week. > > best Max > > On Sat, 18 Oct 2014 18:20:32 -0700 > Gavin Swanson wrote: > > > Crashing is not a reasonable response to a parse error, PERIOD. > > On Oct 18, 2014 4:13 PM, "Owen Williams" wrote: > > > > > Is taglib really that crash-prone? Is this really a common issue? I > > > think crashing on totally crap data is not completely unreasonable as > > > long as we can figure out some way of making it debuggable. > > > > > > I don't see how processing files for cover art is any different than > > > processing files for audio data, and we don't process audio data in a > > > separate kernel process. > > > > > > On Sat, 2014-10-18 at 15:09 -0400, RJ Ryan wrote: > > > > The main limitation with QtConcurrent is that it uses a single global > > > > thread pool -- and currently we use 4 worker threads in our global > > > > thread pool (for parsing 3rd-party libraries, etc). There is no notion > > > > of auto-scaling or the ability for sensing whether we are overloading > > > > the system inherent in QtConcurrent -- it's just a wrapper around a > > > > thread pool. For something as common and compute heavy as processing > > > > cover art we need more deliberate control. > > > > > > > > TagLib crashes will happen given the extreme diversity of > > > > library-from-hell files out there. We really do need a > > > > separate-process isolation feature for processing untrusted data but > > > > I'm pretty sure we don't have time for that for 1.12 if we want to > > > > release in 2014 :). > > > > > > > > > > > > > > > > > > > > On Fri, Oct 17, 2014 at 7:33 PM, Daniel Schürmann > > > wrote: > > > > > Am 18.10.2014 um 00:31 schrieb Max Linke: > > > > >> I haven't noticed any taglib crashes with mixxx. Plus the covers are > > > all > > > > >> extracted in seperate threads. > > > > > I have not experienced any crashes during the tests as well, so the > > > > > issue is hopefully none. > > > > > I was just trying to collect the point that might be risky. > > > > > By the way: Segfaults in a extra thread will have the same effect than > > > a > > > > > segfault in the main thread, Mixxx will crash. > > > > > So we can either rely on the quality of the new taglib version, or > > > setup > > > > > a quarantine process, that read the tags. > > > > > > > > > > > > > > > > > > -- > > > > > Comprehensive Server Monitoring with Site24x7. > > > > > Monitor 10 servers for $9/Month. > > > > > Get alerted through email, SMS, voice calls or mobile push > > > notifications. > > > > > Take corrective actions from your mobile device. > > > > > http://p.sf.net/sfu/Zoho > > > > > ___ > > > > > 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] New experiment modes for testing changes.
very cool! this will be great for A/B comparing things like effects
implementations and magic numbers.
On Fri, 2014-11-14 at 01:42 -0500, RJ Ryan wrote:
> Have you ever compiled two versions of Mixxx to run side-by-side to
> try and get a feel for whether your "smoothness" change is any good?
>
>
> Are you annoyed at having to continuously re-compile or re-run to test
> two different approaches you're considering?
>
>
> Are you bothered by sloppiness in our performance stat tracking -- how
> we include Mixxx startup and shutdown events (usually including
> mega-outliers) in all of our stat counters and then make decisions
> based on that?
>
>
> You may be interested in my latest commit!
> https://github.com/mixxxdj/mixxx/commit/25a5fef18eadece78e65390f808abdd66e359796
>
>
>
> This adds a lightweight "experiment" mode that lets you segment your
> measurements into a base bucket and an experiment bucket.
>
>
> Create your usual timers / counters / stats trackers as usual and gate
> your new code on the experiment flag:
>
>
> #include "util/experiment.h"
>
>
> void CoolWidget::paintEvent(...) {
> ScopedTimer t("CoolWidget::paintEvent");
>
>
> ... beginning of paintEvent ...
>
>
> // added this code
>
> if (Experiment::isExperiment()) {
> // Hope this speeds things up...
> QThread::msleep(1);
> } else if (Experiment::isBase()) {
> // Optional, you can leave blank / as the existing behavior.
> } else {
> // If you want you can really test 3 different pieces of logic
> // but you will only get explicit stats tracking
> // for BASE and EXPERIMENT modes.
> }
>
>
> ... rest of paintEvent ...
> }
>
>
> Compile and run Mixxx.
>
>
> After Mixxx starts up and stabilizes:
> Hit Ctrl+Shift+B (or Developer -> Base) to start recording BASE
> samples. Toggle to stop recording.
> Hit Ctrl+Shift+E (or Developer -> Experiment) to start recording
> EXPERIMENT samples. Toggle to stop recording.
> You can use this to capture exactly the time periods you would like to
> include in your sample of events (recording is cumulative within a
> single Mixxx session).
>
>
> When you quit Mixxx, where the stats are normally printed you now get
> a "BASE STATS" and "EXPERIMENT STATS" section.
>
>
> Key points:
> - No more startup and shutdown events included in your stats
> tracking!
> - Stats segmented into BASE and EXPERIMENT -- only for the times you
> choose to record.
> - Easily check anecdotal "feel" of a feature without re-compiling or
> re-starting Mixxx!
>
>
> Future work:
> - Automatic comparison of stats across base and test (with hints about
> whether you have enough samples and statistical significance?)
> - Automatic polling modes that regularly swap between base /
> experiment?
>
>
> Go forth and measure!
> RJ
> --
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
> ___
> 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
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
___
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] Deciding when to cut for Alpha2/Beta
We've been making really good progress recently (hurray covers!), and I want to get a feel for what other people think about the current status of the build as well as put some pressure behind a beta release. To that end, at some regular interval, maybe every two weeks, I'll send an email to the list asking "Why not now?" The idea being, the devs should provide a list of the fixes/features/work that they think are preventing a beta release. For myself, I'd say my only major blocker is that the Deere skin needs to be cleaned up. Max and I had talked about some things, and he mentioned some manual work that needs to be done. I need to flesh out the bits about master sync, the midi wizard, and the new skin system for example. The problem with this tactic is that I've been sitting around waiting for someone to pick up the Deere skin work. That creates a conflict between me thinking the skin needs fixing for the release, but nobody is doing it. So my controversial addition to this plan is: if you think something is a blocker, you do the work on it :). If you think someone else's PR needs to get finished, I think it's time to just pick it up and finish it. So this weekend I will start poking at Deere, removing all the crazy background colors and cleaning it up. (There has been some hesitation releasing a beta because a beta should be releasable as a proper major version if it goes well. I actually disagree, since that's what I'd call a "release candidate." But if we want to call the next release an alpha2 that's ok with me.) So like I said, here are my blockers: * Deere skin work * Manual updates So, why not now? -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ 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] Deciding when to cut for Alpha2/Beta
Yes, but the milestones are a passive system. My goal is to force people to actively talk about the release. On Fri, 2014-11-14 at 07:02 -0800, Gavin Swanson wrote: > I'd really like to see movement in the direction of release. Isn't > this what the milestone system is for though? Shouldn't issues/bugs be > getting tracked for a given milestone (or sub-milestone being > alpha/beta/RC/whatever) then everyone could see what were blockers for > any given point and then when all of them were cleared it could be > released (alpha/beta/...) at that point. > > > Just my thoughts. > > Gavin S > > On Fri, Nov 14, 2014 at 6:21 AM, Owen Williams > wrote: > We've been making really good progress recently (hurray > covers!), and I > want to get a feel for what other people think about the > current status > of the build as well as put some pressure behind a beta > release. To > that end, at some regular interval, maybe every two weeks, > I'll send an > email to the list asking "Why not now?" The idea being, the > devs should > provide a list of the fixes/features/work that they think are > preventing > a beta release. > > For myself, I'd say my only major blocker is that the Deere > skin needs > to be cleaned up. Max and I had talked about some things, and > he > mentioned some manual work that needs to be done. I need to > flesh out > the bits about master sync, the midi wizard, and the new skin > system for > example. > > The problem with this tactic is that I've been sitting around > waiting > for someone to pick up the Deere skin work. That creates a > conflict > between me thinking the skin needs fixing for the release, but > nobody is > doing it. So my controversial addition to this plan is: if > you think > something is a blocker, you do the work on it :). If you > think someone > else's PR needs to get finished, I think it's time to just > pick it up > and finish it. So this weekend I will start poking at Deere, > removing > all the crazy background colors and cleaning it up. > > (There has been some hesitation releasing a beta because a > beta should > be releasable as a proper major version if it goes well. I > actually > disagree, since that's what I'd call a "release candidate." > But if we > want to call the next release an alpha2 that's ok with me.) > > So like I said, here are my blockers: > > * Deere skin work > * Manual updates > > So, why not now? > > > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push > notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > 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 > > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > 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 -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ 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] Deciding when to cut for Alpha2/Beta
If there are any skin artists listening, please don't wait for the beta release to start working :). I don't have a good sense of where the EQ rack is at, but I saw the kill buttons go through so it does feel like we're almost there. Is there any chance of having it be switchable from the old style to the new style, or does that miss the point entirely? Why GUI elements does it need? I thought it would just plug in to existing skins (and crazy eqs with filters != 3 would be excluded from being used for main EQs to keep things sane). While I agree that segfaults and party stoppers are final release blockers, I don't actually think they should be beta blockers. It's a common practice to release a beta and say "here are the known issues" as long as it's a short and well-defined list. It sounds like we're pretty close. I would strongly urge everyone to focus on their own personal blocker list, even if there are eager new developers with PRs they want reviewed. We don't have a big team, and right now I think it's better to tell people "I understand you've worked hard on this, but right now I am working on XYZ to get mixxx released. Please be patient." On Fri, 2014-11-14 at 20:46 +0100, Daniel Schürmann wrote: > Hi Owen, > > the Deere skin is no blocker for me. I have got the feeling (or I hope) > that the skin artists are > waiting for the beta release. We can call the release: Interface fixes, > Ready for skinning. > > The EQ Rack is almost merged, it feels wired to release Mixxx in this > state. > I hope I fix the remaining known issues today. > Jus has done a GUI / concept review a second (code) review would be > nice, any volunteers? > > A blocker for me are the memory leaks an the re-producible segfaults and > other known party stoppers. > I can have a look on the problems on Linux once EQ Rack is merged. > Who will have a look on windows? > > A personal blocker for me is the missing non-chopped album art view for > small screens. > 100 pixel width is simply to much. An I can't deal with the upper > snipped :-/ > @Max, @Cardinot You have offered to work on it after merge. Do you make > progress > or should I jump in? > > Kind regards, > > Daniel > > > > > > Am 14.11.2014 um 15:21 schrieb Owen Williams: > > We've been making really good progress recently (hurray covers!), and I > > want to get a feel for what other people think about the current status > > of the build as well as put some pressure behind a beta release. To > > that end, at some regular interval, maybe every two weeks, I'll send an > > email to the list asking "Why not now?" The idea being, the devs should > > provide a list of the fixes/features/work that they think are preventing > > a beta release. > > > > For myself, I'd say my only major blocker is that the Deere skin needs > > to be cleaned up. Max and I had talked about some things, and he > > mentioned some manual work that needs to be done. I need to flesh out > > the bits about master sync, the midi wizard, and the new skin system for > > example. > > > > The problem with this tactic is that I've been sitting around waiting > > for someone to pick up the Deere skin work. That creates a conflict > > between me thinking the skin needs fixing for the release, but nobody is > > doing it. So my controversial addition to this plan is: if you think > > something is a blocker, you do the work on it :). If you think someone > > else's PR needs to get finished, I think it's time to just pick it up > > and finish it. So this weekend I will start poking at Deere, removing > > all the crazy background colors and cleaning it up. > > > > (There has been some hesitation releasing a beta because a beta should > > be releasable as a proper major version if it goes well. I actually > > disagree, since that's what I'd call a "release candidate." But if we > > want to call the next release an alpha2 that's ok with me.) > > > > So like I said, here are my blockers: > > > > * Deere skin work > > * Manual updates > > > > So, why not now? > > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___
Re: [Mixxx-devel] Deciding when to cut for Alpha2/Beta
What is the use-case of having different EQs per deck? On Fri, 2014-11-14 at 23:29 +0100, Daniel Schürmann wrote: > Hi Owen, > > Is there any chance of having it be switchable from the old style to the new > > style, or does that miss the point entirely? > > There is no reason to make it switchable, because there will no big > differences for the normal user. > They are: > * selectable EQ per deck > * New EQ types > > > Why GUI elements does it > > need? I thought it would just plug in to existing skins (and crazy eqs > > with filters != 3 would be excluded from being used for main EQs to keep > > things sane). > We need a new preferences GUI to select the EQ effect per deck. The > Button effect parameters are required to support the kill buttons since > the EQs are living in a effect Rack now. > > Kind regards, > > Daniel > > > -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ 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] Deciding when to cut for Alpha2/Beta
but deck EQs have to be three bands to work with the skins. When do you decide to change the EQs for "more precise cuts"? On a track-by-track basis? I can't imagine a DJ actually doing this during a set. On Sat, 2014-11-15 at 17:17 +1300, Waylon Robertson wrote: > a for instance might be, if you want to make use of a 4 band eq on one > deck, for more precise cuts, but a 3 band eq on another deck will do > fine. > four deck: low, low mid, high mid, high > three: low, mid, high > of course, what if you want to control the frequencies of each eq > band? some mixers have a freq knob linked to low mid and high mid's, > or just mid... freq sweep? > and what of this thing i have heard about, but know nothing about, Q? > what is Q? > > > > On Sat, Nov 15, 2014 at 3:59 PM, Owen Williams > wrote: > What is the use-case of having different EQs per deck? > > > > > On Fri, 2014-11-14 at 23:29 +0100, Daniel Schürmann wrote: > > Hi Owen, > > > Is there any chance of having it be switchable from the > old style to the new > > > style, or does that miss the point entirely? > > > > There is no reason to make it switchable, because there will > no big > > differences for the normal user. > > They are: > > * selectable EQ per deck > > * New EQ types > > > > > Why GUI elements does it > > > need? I thought it would just plug in to existing skins > (and crazy eqs > > > with filters != 3 would be excluded from being used for > main EQs to keep > > > things sane). > > We need a new preferences GUI to select the EQ effect per > deck. The > > Button effect parameters are required to support the kill > buttons since > > the EQs are living in a effect Rack now. > > > > Kind regards, > > > > Daniel > > > > > > > > > > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push > notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > 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 > > -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ 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] Deciding when to cut for Alpha2/Beta
For the record, I disagree strongly with 4+ band EQs for decks. Emphatically. It's a ton more work for skin designers to have to deal with some hypothetical variable number of eq knobs. Show me just one midi controller with 4 labeled EQ knobs. The only place I've seen 4 knobs is on the high-end Xone 92, and I've heard more than one DJ complain about it. On Fri, 2014-11-14 at 21:23 -0800, Philip Whelan wrote: > I don't think anyone disagrees with 4+ Band EQ's but it's going to be > too much work for the next release. > > On Fri, Nov 14, 2014 at 9:17 PM, Waylon Robertson > wrote: > depending on the track. And why does eq's have to be three > bands? why can't someone skin a four band eq? or make it > replicatable like the decks are? > anyway, the standard mixer has high pass filter button to cut > out everything below 80hz, low, mid, mid's freq sweep to allow > mid to target a particular frequency range, and high. > four band has hpf, low, low mid, low mid sweep freq, high mid, > hi mid freq sweep, high. > > On Sat, Nov 15, 2014 at 5:48 PM, Owen Williams > wrote: > but deck EQs have to be three bands to work with the > skins. > > When do you decide to change the EQs for "more precise > cuts"? On a > track-by-track basis? I can't imagine a DJ actually > doing this during a > set. > > > On Sat, 2014-11-15 at 17:17 +1300, Waylon Robertson > wrote: > > a for instance might be, if you want to make use of > a 4 band eq on one > > deck, for more precise cuts, but a 3 band eq on > another deck will do > > fine. > > four deck: low, low mid, high mid, high > > three: low, mid, high > > of course, what if you want to control the > frequencies of each eq > > band? some mixers have a freq knob linked to low mid > and high mid's, > > or just mid... freq sweep? > > and what of this thing i have heard about, but know > nothing about, Q? > > what is Q? > > > > > > > > On Sat, Nov 15, 2014 at 3:59 PM, Owen Williams > > > wrote: > > What is the use-case of having different EQs > per deck? > > > > > > > > > > On Fri, 2014-11-14 at 23:29 +0100, Daniel > Schürmann wrote: > > > Hi Owen, > > > > Is there any chance of having it be > switchable from the > > old style to the new > > > > style, or does that miss the point > entirely? > > > > > > There is no reason to make it switchable, > because there will > > no big > > > differences for the normal user. > > > They are: > > > * selectable EQ per deck > > > * New EQ types > > > > > > > Why GUI elements does it > > > > need? I thought it would just plug in > to existing skins > > (and crazy eqs > > > > with filters != 3 would be excluded from > being used for > > main EQs to keep > > > > things sane). > > > We need a new preferences GUI to select > the EQ effect per > > deck. The > > > Button effect parameters are required to > support the kill > > buttons since > > > the EQs are living in a effect Rack now. > > > > > > Kind regards, > > > >
Re: [Mixxx-devel] Deciding when to cut for Alpha2/Beta
Filter knobs might have to go in, just because so many controllers have them. My preference would be to have a special effect slot for "per-deck effect", and the filter knob would be the super knob for that effect. So the user could select "filter sweep" or "flange" and the filter knob would alter that effect per-deck. But I already don't have space in LateNight to put another knob, so I don't know if it will go in the mixer section or in the effect section. :( On Sun, 2014-11-16 at 12:37 +1300, Waylon Robertson wrote: > And what of 3 band with mid eq sweep? > > On Sunday, November 16, 2014, Max Linke wrote: > I'm also wouldn't like 4 Band EQ's. 3 Band EQ's for the Decks > are enough. If you > want more bands on a EQ you can use the effects Framework. > > > On Sat, 15 Nov 2014 17:06:31 -0500 > Owen Williams wrote: > > > For the record, I disagree strongly with 4+ band EQs for > decks. > > Emphatically. It's a ton more work for skin designers to > have to deal > > with some hypothetical variable number of eq knobs. Show me > just one > > midi controller with 4 labeled EQ knobs. > > > > The only place I've seen 4 knobs is on the high-end Xone 92, > and I've > > heard more than one DJ complain about it. > > > > > > On Fri, 2014-11-14 at 21:23 -0800, Philip Whelan wrote: > > > I don't think anyone disagrees with 4+ Band EQ's but it's > going to be > > > too much work for the next release. > > > > > > On Fri, Nov 14, 2014 at 9:17 PM, Waylon Robertson > > > wrote: > > > depending on the track. And why does eq's have to > be three > > > bands? why can't someone skin a four band eq? or > make it > > > replicatable like the decks are? > > > anyway, the standard mixer has high pass filter > button to cut > > > out everything below 80hz, low, mid, mid's freq > sweep to allow > > > mid to target a particular frequency range, and > high. > > > four band has hpf, low, low mid, low mid sweep > freq, high mid, > > > hi mid freq sweep, high. > > > > > > On Sat, Nov 15, 2014 at 5:48 PM, Owen Williams > > > wrote: > > > but deck EQs have to be three bands to > work with the > > > skins. > > > > > > When do you decide to change the EQs for > "more precise > > > cuts"? On a > > > track-by-track basis? I can't imagine a > DJ actually > > > doing this during a > > > set. > > > > > > > > > On Sat, 2014-11-15 at 17:17 +1300, Waylon > Robertson > > > wrote: > > > > a for instance might be, if you want to > make use of > > > a 4 band eq on one > > > > deck, for more precise cuts, but a 3 > band eq on > > > another deck will do > > > > fine. > > > > four deck: low, low mid, high mid, high > > > > three: low, mid, high > > > > of course, what if you want to control > the > > > frequencies of each eq > > > > band? some mixers have a freq knob > linked to low mid > > > and high mid's, > > > > or just mid... freq sweep? > > > > and what of this thing i have heard > about, but know > > > nothing about, Q? > > > > what is Q? > > > > > > > > > > > > > > > > On Sat, Nov 15, 2014 at 3:59 PM, Owen
Re: [Mixxx-devel] Deciding when to cut for Alpha2/Beta
(I am much more open to adding a knob for dedicated deck effect than I am to variable number of eq knobs) On Sun, 2014-11-16 at 12:37 +1300, Waylon Robertson wrote: > And what of 3 band with mid eq sweep? > > On Sunday, November 16, 2014, Max Linke wrote: > I'm also wouldn't like 4 Band EQ's. 3 Band EQ's for the Decks > are enough. If you > want more bands on a EQ you can use the effects Framework. > > > On Sat, 15 Nov 2014 17:06:31 -0500 > Owen Williams wrote: > > > For the record, I disagree strongly with 4+ band EQs for > decks. > > Emphatically. It's a ton more work for skin designers to > have to deal > > with some hypothetical variable number of eq knobs. Show me > just one > > midi controller with 4 labeled EQ knobs. > > > > The only place I've seen 4 knobs is on the high-end Xone 92, > and I've > > heard more than one DJ complain about it. > > > > > > On Fri, 2014-11-14 at 21:23 -0800, Philip Whelan wrote: > > > I don't think anyone disagrees with 4+ Band EQ's but it's > going to be > > > too much work for the next release. > > > > > > On Fri, Nov 14, 2014 at 9:17 PM, Waylon Robertson > > > wrote: > > > depending on the track. And why does eq's have to > be three > > > bands? why can't someone skin a four band eq? or > make it > > > replicatable like the decks are? > > > anyway, the standard mixer has high pass filter > button to cut > > > out everything below 80hz, low, mid, mid's freq > sweep to allow > > > mid to target a particular frequency range, and > high. > > > four band has hpf, low, low mid, low mid sweep > freq, high mid, > > > hi mid freq sweep, high. > > > > > > On Sat, Nov 15, 2014 at 5:48 PM, Owen Williams > > > wrote: > > > but deck EQs have to be three bands to > work with the > > > skins. > > > > > > When do you decide to change the EQs for > "more precise > > > cuts"? On a > > > track-by-track basis? I can't imagine a > DJ actually > > > doing this during a > > > set. > > > > > > > > > On Sat, 2014-11-15 at 17:17 +1300, Waylon > Robertson > > > wrote: > > > > a for instance might be, if you want to > make use of > > > a 4 band eq on one > > > > deck, for more precise cuts, but a 3 > band eq on > > > another deck will do > > > > fine. > > > > four deck: low, low mid, high mid, high > > > > three: low, mid, high > > > > of course, what if you want to control > the > > > frequencies of each eq > > > > band? some mixers have a freq knob > linked to low mid > > > and high mid's, > > > > or just mid... freq sweep? > > > > and what of this thing i have heard > about, but know > > > nothing about, Q? > > > > what is Q? > > > > > > > > > > > > > > > > On Sat, Nov 15, 2014 at 3:59 PM, Owen > Williams > > > > > > > wrote: > > > > What is the use-case of having > different EQs > > > per deck? > > > > > > > > > > > &
[Mixxx-devel] LateNight updates
I've done some updating to the LateNight skin to make it work with the new EQ rack and trying to shave off pixels of vertical space where I can. It still looks like crap if you try to turn everything on when the screen is really small, but I don't know how to get around that. Owen -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ 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] skin questions
I am trying to make little pitch-adjuster buttons for LateNight. I have a couple questions: * When I push the pushbutton, the key changes immediately, which sometimes causes the widget to move out from under the mouse while the button is still being held. How do I change this so that the signal isn't fired until I let go? * How do I hide the buttons unless a track is loaded and has a key? I can't just bind visual_key to the visible property -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ 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] Newbie in 1.12 skins
Hey Leo, To support resizeable skins, skin layout is now done with widget containers (vertical and horizontal boxes) and CSS definitions. If you wanted to move everything inside the rate box (slider, display, buttons) you have to figure out where that WidgetGroup is -- in this case, the deck.xml file. Then you can cut and paste the whole block and put it somewhere else. I recommend using an XML editor that tells you which open tags match which close tags, or you will go crazy. On Thu, 2014-11-27 at 20:24 -0300, Leo Combes wrote: > I'm trying to understand how customizations skins are made in version > 1.12 of Mixxx. > In previous versions, if you wanted to change the position of a > widget, looking for the tag and changed the coordinates. > I understand that now the skins XML files are much more modular, but > if I look for the tag in the entire directory of skin LateNight > only find few occurrences and no one use to, for example, to change > the position of the entire widget pitch rate. > How is done in the new version? > > Regards. > > -- > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > ___ > 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 > > -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ 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] Beta Progress Updates
Hey all, time to check in on our progress toward releasing a beta. In the last thread I said I thought skins and the manual needed updating, and I think we've made good progress there, although Deere still has a long way to go. (If someone would just remove the ugly weird background colors that would be a good start!) I also worked on the manual for master sync and the midi window. I've also been focusing on bugs, mostly for master sync, but also cleaning up the eq preference page and refactoring Auto DJ to make it more sane. At this point I still think the following needs to be done: * skins skins skins. LateNite is almost there, although it still fails on small displays (although you're never going to be able to show all the controls on a small screen). * Fix Auto DJ for when there are tracks in decks 3 or 4. * make jog wheels learnable in the wizard What have people been doing toward their own goals for releasing the beta? And why have you not been updating the manual? :) Owen -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk ___ 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] Beta Progress Updates
Yeah it might be nice to have a basic primer on how to use the lancelot / camelot system. I think mostly all that needs to be said is "here is the musical key control, you can make stuff sound good wit dis." And talk about how pushing keylock restores the original key but can still be adjusted after that. I don't think the manual should go in to the music theory although we can provide a helpful link. On Wed, 2014-12-03 at 11:23 +0100, Max Linke wrote: > On Tue, 02 Dec 2014 18:48:40 -0500 > Owen Williams wrote: > > > Hey all, time to check in on our progress toward releasing a beta. > > > > In the last thread I said I thought skins and the manual needed > > updating, and I think we've made good progress there, although Deere > > still has a long way to go. (If someone would just remove the ugly > > weird background colors that would be a good start!) I also worked on > > the manual for master sync and the midi window. > > Thanks for that. I wanted to start writing a something about the new key > detection and wondered if we should also add a section about harmonic mixing > then? > > best Max > > -- > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > ___ > 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 > > -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk ___ 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] Beta Progress Updates
On Wed, 2014-12-03 at 16:46 +0100, Max Linke wrote: > On Wed, 03 Dec 2014 09:33:43 -0500 > Owen Williams wrote: > > > Yeah it might be nice to have a basic primer on how to use the > > lancelot / camelot system. > > Is there some information about this on the web. The names make it kind of > hard > to google for information. http://www.harmonic-mixing.com/HowTo.aspx > > > I think mostly all that needs to be said is > > "here is the musical key control, you can make stuff sound good wit > > dis." > > Sure. > > > And talk about how pushing keylock restores the original key but > > can still be adjusted after that. > > I didn't follow the Key-integration to closely. How does it exactly work here. > Either the keylock fixes the key or it doesn't. Why can I change it the key > with a keylock-on? What would be the use case? Keylock ensures that the musical key remains constant no matter how the speed of the track changes. But that still leaves the question of what that constant key is. I think we will be ending up with a preference so that when keylock is pressed either: * the musical key is reset to the natural key of the track * the musical key is held at the current value. Separately from keylock, there is a pitch knob that allows the user to raise or lower the musical key of the track. Think of this as a musical key offset that's applied to whatever the track would have sounded like whether keylock was on or off. > > > I don't think the manual should go in > > to the music theory although we can provide a helpful link. > > I agree > > > > > On Wed, 2014-12-03 at 11:23 +0100, Max Linke wrote: > > > On Tue, 02 Dec 2014 18:48:40 -0500 > > > Owen Williams wrote: > > > > > > > Hey all, time to check in on our progress toward releasing a beta. > > > > > > > > In the last thread I said I thought skins and the manual needed > > > > updating, and I think we've made good progress there, although Deere > > > > still has a long way to go. (If someone would just remove the ugly > > > > weird background colors that would be a good start!) I also worked on > > > > the manual for master sync and the midi window. > > > > > > Thanks for that. I wanted to start writing a something about the new key > > > detection and wondered if we should also add a section about harmonic > > > mixing > > > then? > > > > > > best Max > > > > > > -- > > > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > > > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > > > with Interactivity, Sharing, Native Excel Exports, App Integration & more > > > Get technology previously reserved for billion-dollar corporations, FREE > > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > > > ___ > > > 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 > > > > > > > > > > > > > -- > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > ___ > 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 > > -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk ___ 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] Beta Progress Updates
that's CircleOfFifths(tm) to you! On Wed, 2014-12-03 at 11:08 -0500, RJ Ryan wrote: > > On Wed, Dec 3, 2014 at 10:58 AM, Owen Williams > wrote: > > http://www.harmonic-mixing.com/HowTo.aspx > > N -- harmonic-mixing.com is a shill site for Mixed in Key -- the > same jerks who claim intellectual property on the circle of fifths. :) > > > Rapid Evolution's wiki is pretty good: > http://www.mixshare.com/wiki/doku.php?id=harmonic_mixing > > http://www.mixshare.com/wiki/doku.php?id=mixing_harmonically > -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk ___ 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] [Fwd: Re: [Question #251368]: xin shen selling mixxx in app store]
How about we get social media on this? 1. Make a blog post to put on the website, alerting people to the existence of bad copies like this, and asking Apple to remove the bad copies. 2. Post on reddit, facebook, twitter. 3. bring the fucking fury. Forwarded Message > From: jus > Reply-to: question251...@answers.launchpad.net > To: owilli...@mixxx.org > Subject: Re: [Question #251368]: xin shen selling mixxx in app store > Date: Thu, 04 Dec 2014 10:26:43 - > > Question #251368 on Mixxx changed: > https://answers.launchpad.net/mixxx/+question/251368 > > Status: Expired => Open > > jus changed the question status: > RJ, complains filed for NON-us stores, yet no reaction from Apple? > > -- > You received this question notification because you are a member of > Mixxx Development Team, which is an answer contact for Mixxx. > > -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk ___ 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] [Fwd: Re: [Question #251368]: xin shen selling mixxx in app store]
disclaimer: "fury" refers only to polite emails sent to a general-delivery mailbox, or calm tweets. On Thu, 2014-12-04 at 09:06 -0500, Owen Williams wrote: > How about we get social media on this? > > 1. Make a blog post to put on the website, alerting people to the > existence of bad copies like this, and asking Apple to remove the bad > copies. > 2. Post on reddit, facebook, twitter. > 3. bring the fucking fury. > > > Forwarded Message > > From: jus > > Reply-to: question251...@answers.launchpad.net > > To: owilli...@mixxx.org > > Subject: Re: [Question #251368]: xin shen selling mixxx in app store > > Date: Thu, 04 Dec 2014 10:26:43 - > > > > Question #251368 on Mixxx changed: > > https://answers.launchpad.net/mixxx/+question/251368 > > > > Status: Expired => Open > > > > jus changed the question status: > > RJ, complains filed for NON-us stores, yet no reaction from Apple? > > > > -- > > You received this question notification because you are a member of > > Mixxx Development Team, which is an answer contact for Mixxx. > > > > > > > > -- > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > ___ > 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 > > -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk ___ 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] Alpha Release Blockers?
There is one remaining issue I'd like to fix before we release, a regression in vinyl control that Daniel is working on (https://bugs.launchpad.net/mixxx/+bug/1406131). Other than that I think we're ready to push out a beta. (I am concerned about Rubberband CPU usage and performance in general, but we can start profiling as part of the release process) On Sun, 2014-12-28 at 23:21 +0100, Max Linke wrote: > Hi > > My current list has 0 items. The key-detection in the manual will be merged in > the next 2-3 days and we have a small text for the new EQ section. There is > still stuff missing in the manual but that should stop us from putting out an > alpha any longer. > > There has also been some progress with the skins. Are they still a blocker for > people? > > I've been a bit busy lately and haven't managed to stay 100% ontop of the > recent changes but it seems to me that we are starting to fix also other stuff > then alpha release blockers again. When we get sidetracked anyway we might as > well just cut an alpha now. > > best Max > > -- > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > ___ > 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 > > -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ 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] Sampler Play buttons
Oh that was a personal hack that must have snuck back upstream. I'm fine to change it back, although the newer behavior makes a lot more sense to me. My girlfriend (a newbie DJ) played a set and made extensive use of samplers, and she had trouble remembering that she had to rewind the sampler every time she played it. She preferred to just push the button and have it play from the beginning. Also, for jokey stutter effects (personally for me, banging the airhorn button), I thought having the play button always start playback made sense. This would make it possible to do drum-machine style performance, too. I'm also thinking about the radio DJ case where they might want to play little sound effects here and there, and they should just be able to push the button without needing to make sure that the playhead is in the right place. I don't really get why we treat samplers like little tiny regular decks when the use-case is really different, so I prefer this style and would prefer to change the other skins to match. On Wed, 2014-12-31 at 12:30 +0100, Max Linke wrote: > Did the sampler play button behavior change lately? The manual says that I can > start/stop a sampler with a left click. > > With the LateNight skin I see that I can only start the track from the > beginning with the play-button and a right click will stop it. > > Is this a desired behavior for some djing-styles? > > best Max > > -- > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > ___ > 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 > > -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ 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] Sampler Play buttons
I like "play_start" better than auto rewind because of the aforementioned drum machine and annoying airhorn reasons. If pressing start always starts from the beginning, you don't need auto rewind. And right-click stop still allows users to interrupt playback if they want. The only flaw is I wish play_start started at the cue point, not the start of the file. On Wed, 2014-12-31 at 09:11 -0500, RJ Ryan wrote: > Auto-rewind or something like that has been a wishlist item for a long > time: > https://bugs.launchpad.net/mixxx/+bug/774808 > > > > It's not intentional that we treat samples like decks -- they just > happen to share 100% of their code right now since nobody has done > that work :). I was going to tackle it for the new release but ran out > of time. > > > > On Wed, Dec 31, 2014 at 9:01 AM, Owen Williams > wrote: > Oh that was a personal hack that must have snuck back > upstream. I'm > fine to change it back, although the newer behavior makes a > lot more > sense to me. > > My girlfriend (a newbie DJ) played a set and made extensive > use of > samplers, and she had trouble remembering that she had to > rewind the > sampler every time she played it. She preferred to just push > the button > and have it play from the beginning. Also, for jokey stutter > effects > (personally for me, banging the airhorn button), I thought > having the > play button always start playback made sense. This would make > it > possible to do drum-machine style performance, too. I'm also > thinking > about the radio DJ case where they might want to play little > sound > effects here and there, and they should just be able to push > the button > without needing to make sure that the playhead is in the right > place. > > I don't really get why we treat samplers like little tiny > regular decks > when the use-case is really different, so I prefer this style > and would > prefer to change the other skins to match. > > > On Wed, 2014-12-31 at 12:30 +0100, Max Linke wrote: > > Did the sampler play button behavior change lately? The > manual says that I can > > start/stop a sampler with a left click. > > > > With the LateNight skin I see that I can only start the > track from the > > beginning with the play-button and a right click will stop > it. > > > > Is this a desired behavior for some djing-styles? > > > > best Max > > > > > > -- > > Dive into the World of Parallel Programming! The Go Parallel > Website, > > sponsored by Intel and developed in partnership with > Slashdot Media, is your > > hub for all things parallel software development, from > weekly thought > > leadership blogs to news, videos, case studies, tutorials > and more. Take a > > look and join the conversation now. > http://goparallel.sourceforge.net > > ___ > > 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 > > > > > > > > > -- > Dive into the World of Parallel Programming! The Go Parallel > Website, > sponsored by Intel and developed in partnership with Slashdot > Media, is your > hub for all things parallel software development, from weekly > thought > leadership blogs to news, videos, case studies, tutorials and > more. Take a > look and join the conversation now. > http://goparallel.sourceforge.net > ___ > 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/li
Re: [Mixxx-devel] Sampler Play buttons
That's close, but you'd have to hold down the buttons and that's not really possible if you're going to do some AraabMuzik style mashing. On Wed, 2014-12-31 at 09:24 -0500, Mel Grubb wrote: > Could the samplers have a "cue" button like decks? That would make > their behavior entirely consistent and allow for "drumming" the > samples. > > __ > From:Owen Williams > Sent:12/31/2014 9:19 AM > To:RJ Ryan > Cc:Too Many DJs > Subject:Re: [Mixxx-devel] Sampler Play buttons > > > I like "play_start" better than auto rewind because of the > aforementioned drum machine and annoying airhorn reasons. If pressing > start always starts from the beginning, you don't need auto rewind. > > And right-click stop still allows users to interrupt playback if they > want. > > The only flaw is I wish play_start started at the cue point, not the > start of the file. > > > On Wed, 2014-12-31 at 09:11 -0500, RJ Ryan wrote: > > Auto-rewind or something like that has been a wishlist item for a > long > > time: > > https://bugs.launchpad.net/mixxx/+bug/774808 > > > > > > > > It's not intentional that we treat samples like decks -- they just > > happen to share 100% of their code right now since nobody has done > > that work :). I was going to tackle it for the new release but ran > out > > of time. > > > > > > > > On Wed, Dec 31, 2014 at 9:01 AM, Owen Williams > > wrote: > > Oh that was a personal hack that must have snuck back > > upstream. I'm > > fine to change it back, although the newer behavior makes a > > lot more > > sense to me. > > > > My girlfriend (a newbie DJ) played a set and made extensive > > use of > > samplers, and she had trouble remembering that she had to > > rewind the > > sampler every time she played it. She preferred to just > push > > the button > > and have it play from the beginning. Also, for jokey > stutter > > effects > > (personally for me, banging the airhorn button), I thought > > having the > > play button always start playback made sense. This would > make > > it > > possible to do drum-machine style performance, too. I'm > also > > thinking > > about the radio DJ case where they might want to play little > > sound > > effects here and there, and they should just be able to push > > the button > > without needing to make sure that the playhead is in the > right > > place. > > > > I don't really get why we treat samplers like little tiny > > regular decks > > when the use-case is really different, so I prefer this > style > > and would > > prefer to change the other skins to match. > > > > > > On Wed, 2014-12-31 at 12:30 +0100, Max Linke wrote: > > > Did the sampler play button behavior change lately? The > > manual says that I can > > > start/stop a sampler with a left click. > > > > > > With the LateNight skin I see that I can only start the > > track from the > > > beginning with the play-button and a right click will stop > > it. > > > > > > Is this a desired behavior for some djing-styles? > > > > > > best Max > > > > > > > > > -- > > > Dive into the World of Parallel Programming! The Go > Parallel > > Website, > > > sponsored by Intel and developed in partnership with > > Slashdot Media, is your > > > hub for all things parallel software development, from > > weekly thought > > > leadership blogs to news, videos, case studies, tutorials > > and more. Take a > > > look and join the conversation now. > > http://goparallel.sourceforge.net > > > ___ > > > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > > > http://mixxx.org > > > > > > > > > Mixxx-d
Re: [Mixxx-devel] Sampler Play buttons
Maybe this is what play_stutter was supposed to do? The way it's written it's broken though. On Wed, 2014-12-31 at 16:36 +0100, Max Linke wrote: > The current behavior is actually nice. With the 32 sampler skin it > will make for a nice drum machine. Have play_start start at the cue > point would indeed be better. > > On December 31, 2014 3:19:32 PM CET, Owen Williams > wrote: > I like "play_start" better than auto rewind because of the > aforementioned drum machine and annoying airhorn reasons. If pressing > start always starts from the beginning, you don't need auto rewind. > > And right-click stop still allows users to interrupt playback if they > want. > > The only flaw is I wish play_start started at the cue point, not the > start of the file. > > > On Wed, 2014-12-31 at 09:11 -0500, RJ Ryan wrote: > Auto-rewind or something like that has been a wishlist item > for a long > time: > https://bugs.launchpad.net/mixxx/+bug/774808 > > > > It's not intentional that we treat samples like decks -- > they just > happen to share 100% of their code right now since nobody > has done > that work :). I was going to tackle it for the new release > but ran out > of time. > > > > On Wed, Dec 31, 2014 at 9:01 AM, Owen Williams > > wrote: > Oh that was a personal hack that must have snuck back > upstream. I'm > fine to change it back, although the newer behavior > makes a > lot more > sense to me. > > My girlfriend (a newbie DJ) played a set and made > extensive > use of > samplers, and she had trouble remembering that she > had to > rewind the > sampler every time she played it. She preferred to > just push > the button > and have it play from the beginning. Also, for > jokey stutter > effects > (personally for me, banging the airhorn button), I > thought > having the > play button always start playback made sense. This > would make > it > possible to do drum-machine style performance, too. > I'm also > thinking > about the radio DJ case where they might want to > play little > sound > effects here and there, and they should just be able > to push > the button > without needing to make sure that the playhead is in > the right > place. > > I don't really get why we treat samplers like little > tiny > regular decks > when the use-case is really different, so I prefer > this style > and would > prefer to change the other skins to match. > > > On Wed, 2014-12-31 at 12:30 +0100, Max Linke wrote: > Did the sampler play button behavior change lately? > The > manual says that I can > start/stop a sampler with a left click. > > With the LateNight skin I see that I can only start > the > track from the > beginning with the play-button and a right click > will stop > it. > > Is this a desired behavior for some djing-styles? > > best Max > > > > __ > > Dive into the World of Parallel Programming! The Go > Parallel > Website, >
Re: [Mixxx-devel] Sampler Play buttons
https://github.com/mixxxdj/mixxx/pull/445 On Wed, 2014-12-31 at 11:21 -0500, Owen Williams wrote: > Maybe this is what play_stutter was supposed to do? The way it's > written it's broken though. > > > On Wed, 2014-12-31 at 16:36 +0100, Max Linke wrote: > > The current behavior is actually nice. With the 32 sampler skin it > > will make for a nice drum machine. Have play_start start at the cue > > point would indeed be better. > > > > On December 31, 2014 3:19:32 PM CET, Owen Williams > > wrote: > > I like "play_start" better than auto rewind because of the > > aforementioned drum machine and annoying airhorn reasons. If > > pressing > > start always starts from the beginning, you don't need auto rewind. > > > > And right-click stop still allows users to interrupt playback if > > they > > want. > > > > The only flaw is I wish play_start started at the cue point, not the > > start of the file. > > > > > > On Wed, 2014-12-31 at 09:11 -0500, RJ Ryan wrote: > > Auto-rewind or something like that has been a wishlist > > item for a long > > time: > > https://bugs.launchpad.net/mixxx/+bug/774808 > > > > > > > > It's not intentional that we treat samples like decks -- > > they just > > happen to share 100% of their code right now since nobody > > has done > > that work :). I was going to tackle it for the new release > > but ran out > > of time. > > > > > > > > On Wed, Dec 31, 2014 at 9:01 AM, Owen Williams > > > > wrote: > > Oh that was a personal hack that must have snuck > > back > > upstream. I'm > > fine to change it back, although the newer > > behavior makes a > > lot more > > sense to me. > > > > My girlfriend (a newbie DJ) played a set and made > > extensive > > use of > > samplers, and she had trouble remembering that she > > had to > > rewind the > > sampler every time she played it. She preferred > > to just push > > the button > > and have it play from the beginning. Also, for > > jokey stutter > > effects > > (personally for me, banging the airhorn button), I > > thought > > having the > > play button always start playback made sense. > > This would make > > it > > possible to do drum-machine style performance, > > too. I'm also > > thinking > > about the radio DJ case where they might want to > > play little > > sound > > effects here and there, and they should just be > > able to push > > the button > > without needing to make sure that the playhead is > > in the right > > place. > > > > I don't really get why we treat samplers like > > little tiny > > regular decks > > when the use-case is really different, so I prefer > > this style > > and would > > prefer to change the other skins to match. > > > > > > On Wed, 2014-12-31 at 12:30 +0100, Max Linke wrote: > > Did the sampler play button behavior change > > lately? The > > manual says that I can > > start/stop a sampler with a left click. > > > > With the LateNight skin I see that I can only > > start the > > track from th
Re: [Mixxx-devel] Features I miss
You can still long-press sync on all the decks you want to be synced together, what is missing from that? We will eventually re-add support for explicit masters (it's actually still in there), but there were some bugs associated with it that I didn't want to include it in 1.12. We recently added a preference so that when you push keylock it stays on the key you selected instead of reverting back to the original key. On Thu, 2015-01-08 at 10:30 +1300, Waylon Robertson wrote: > Okay, the new LateNight skin is great, but its missing the Master bpm > stuff of the old LateNight 4 deck variant. I loved making one deck the > master, and slaving my actions to it, using a 'sync' lock, long press > of Sync button. Okay, when that deck ended, and i forgot to make the > mixer bpm the master, i was in trouble but oh well.. having both decks > finish together would probably be a good thing for anyone else who > doesn't forget to practice good sync hygiene. > > > The other feature im missing, is the ability to keylock at a > particular key, any arbitrary key achieved by > pitchshifting/temposhifting down/up to it, then being able to > temposhift without it affecting my new key. Instead, keylock on master > tip now resets the key, temporarily, to the original key. when the > keylock is removed, it springs back to the current temposhift is. > > > same behaviour with the new < KEY > ui elements. set key with that, > and theres no way to keep it fixed so. > > > Waylon > > -- > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > ___ > 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 -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ 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] Mixxx cpu / mem usage
This is a pretty standard period in development of a new version -- feature-complete, but optimization has not happened yet. We've started that process and will be cutting some low-hanging fruit soon. On Fri, 2015-01-09 at 23:49 +1300, Waylon Robertson wrote: > okay, so i disabled streaming vbo in secondlife client.. and the > problem seems to have been fixed seems... > > the memory requirements of mixxx though has me a little 'what?!' ... > and well... its forcing use of swap due to taking up so much ram. > > Can't believe im going to have to upgrade my computer from 8gb to get > rid of swapping. > > could mixxx be interfering with streaming VBO usage? > > > On Fri, Jan 9, 2015 at 10:50 PM, Waylon Robertson > wrote: > BTW: total used free shared > buffers cached > Mem: 6884 6757126643 1 > 996 > -/+ buffers/cache: 5759 1125 > Swap: 1905953952 > > > > On Fri, Jan 9, 2015 at 10:49 PM, Waylon Robertson > wrote: > Ubuntu 12.04 was fine, with an old mixxx build, pre > libtag2.. forget the exact revision.. but i had to go > to ubuntustudio 14.04 to compile the libtag2 > version... > > my god, does it suck resources now. > > I used to be able to run mixxx on a 1gb ram single > core cpu machine, now with master tip: > PID USER PR NIVIRTRESSHR S %CPU % > MEM TIME+ COMMAND > 6448 waylon20 0 2563800 466268 112060 R 145.2 > 6.6 6:49.68 singularit+ > 3165 waylon20 0 6669832 4.570g 212704 S 12.3 > 68.0 7:31.99 mixxx > > 145% cpu for SL, okay, but still.. singularity client > is quite stuttery at times. and it gets so bad with > mixxx loaded, that it sometimes up and quits without > reason. > > without mixxx running, its fine. > > And look at Mixxx's mem usage. what? i have a 8gb ram > machine, whats going on here? > > it seems that ubuntu 14.04 intel gfx drivers have a > problem sharing gfx between two X11 clients, Mixxx and > Secondlife - singularity. > > > > > > -- > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > ___ > 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 -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ 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] Libtaglib 2
"git help bisect" will give you all the information. You start by saying "git bisect start". Then identify a revision that was fast and say "git bisect good" and then identify a build that is slow and say "git bisect bad". Git will then automatically try checking out different revisions, and then you report to git whether the revision is good or bad. Eventually it can narrow down to a single change that introduced the problem. If the performance issues were introduced slowly, this may not work. (I recently discovered a problem with vinyl control this way, and git bisect worked perfectly and we fixed the bug) On Thu, 2015-01-15 at 14:27 +1300, Waylon Robertson wrote: > don't know how to use. > > > On Thu, Jan 15, 2015 at 2:21 PM, Gavin Swanson > wrote: > If you really want to find the cause. got bisect is your > friend. > > On Jan 14, 2015 5:14 PM, "Waylon Robertson" > wrote: > its a little sluggish, a little bit better but eh > also, the problem increases with time. wonder if > exiting and restarting mixxx will have any effect. > > > On Thu, Jan 15, 2015 at 2:00 PM, Waylon Robertson > wrote: > done, now testing. > > > On Thu, Jan 15, 2015 at 1:58 PM, Waylon > Robertson wrote: > just pulled, and recompiling now. > > > On Thu, Jan 15, 2015 at 1:47 PM, RJ > Ryan wrote: > Oh, I see -- you just want to > go back to then. > > > Uwe's SoundSource refactor was > added just > after > 456c2e06b33608de6d8b86ccc54a80fc5b194f5f so you can git checkout > 456c2e06b33608de6d8b86ccc54a80fc5b194f5f to get back there. > > > Before you do though, would > you mind trying the latest > master if you haven't already? > I added a handful of > performance fixes recently and > am curious if that has > improved the performance > situation. > > > I also have found that > removing VU meters and track > position widgets from the skin > improves Mixxx's interactivity > for me drastically -- so > that's an option if you hack > up your skin. We need to get > to the bottom of those > performance issues before > releasing 1.12.0. but that may > be a workaround for you now. > > > > On Wed, Jan 14, 2015 at 7:14 > PM, Waylon Robertson > > wrote: > And im thinking mixxx > is the culprit.. as > mixxx + secondlife > slows down system > drastically, mixxx by > itself, or second life > by itself is okay. so > yeah.. id like to > recompile the master, > from before taglib 1.9 > was required.. > whenever that was, as > i know
Re: [Mixxx-devel] alternative mixxx nightlies
thanks so much, This is really helpful! We don't have a dedicated packaging person so that tends to fall behind. On Fri, 2015-01-23 at 17:58 +0100, Nico Schlömer wrote: > Hi Mixxx devs, > > For the sake of messing around with the Mixxx debian build files, I > just created a nightly build PPA [1]. It fires off builds for trusty, > utopic, and vivid every night (CET), provided that the sources of the > debian build files changed. > This may be interesting for anyone who wants nightly builds, given the > fact that the actual nightlies [2] aren't updated anymore. > > Cheers, > Nico > > > [1] https://launchpad.net/~nschloe/+archive/ubuntu/mixxx-nightly/ > [2] https://launchpad.net/~mixxx/+archive/ubuntu/nightlies > > -- > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > ___ > 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 > > -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ 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] coverity scan
I've never used coverity, but it sounds like it would be a great addition. Is there anything we have to do on our end? Owen On Sat, 2015-01-24 at 14:59 +0100, Nico Schlömer wrote: > Hey all, > > I noticed that everyone is already quite cautious when it comes to > memory leaks and such in mixxx (e.g., using the AddressSanitizer). One > service I found really helpful in the past is the coverity scan [1]. > Is there already a coverity instance for mixxx? If not, would you mind > if I set one up (with weekly pushed I would think)? > > Cheers, > Nico > > > [1] https://scan.coverity.com/ > > -- > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > ___ > 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 > > -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ 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] Features for Debian
A lot of the compiler features refer to dead, unmaintained code. The defaults are fine, and actually we should think about going through and cleaning out some of the cruft. On Sat, 2015-01-24 at 15:33 +0100, Nico Schlömer wrote: > Hi all, > > from the Ubuntu builds [1], I find > ``` > Features Summary: > > Mixxx Core Features... Enabled > MAD MP3 Decoder... Enabled > CoreAudio MP3/AAC Decoder... Disabled > Media Foundation AAC Decoder Plugin... Disabled > HSS1394 MIDI device support... Disabled > HID controller support... Enabled > USB Bulk controller support... Enabled > Build for Mac App Store... Disabled > Vinyl Control... Enabled >Shoutcast Broadcasting (OGG/MP3)... Enabled > Opus (RFC 6716) support... Disabled > gprof/Saturn profiling support... Disabled > Optimizing for this CPU... Disabled >Debugging message output... Enabled > Verbose compilation output... Enabled > Optimization and Tuning... Enabled -- Basic Optimizations (-03) > FAAD AAC audio file decoder plugin... Disabled > WavPack audio file support plugin... Disabled > Modplug module decoder plugin... Disabled >Mixxx Test Suite... Disabled > Vamp Analysers support... Enabled > Auto-DJ crates (for random tracks)... Enabled > Color Diagnostics... Disabled > Address Sanitizer... Disabled > Locale Aware Compare for SQLite... Enabled >Google PerfTools... Disabled > Agner Fog's ASMLIB... Disabled (due to debug build) >NOT-WORKING iPod Support... Disabled >FFMPEG/LibAV support... Disabled > > ``` > I'm wondering about the disabled features: Clearly, some are not > really necessary (like having more than one MP3 decoder), about the > others I'm not sure. Obviously we would like to ship with as many > features as possible. Which currently disabled features would you > think are worth enabling for the default mixxx build? > > Cheers, > Nico > > > [1] > https://launchpadlibrarian.net/195647808/buildlog_ubuntu-utopic-amd64.mixxx_1.12.0~20150124-utopic1_UPLOADING.txt.gz > > -- > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > ___ > 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 > > -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ 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] Debian patches
I disagree. Since pulseaudio releases the sound devices when they are in use, starting up mixxx with pulseaudio active is usually fine. If pulseaudio does grab the sound devices, it's easy to just wait and then requery sound devices. I think we should stop using pasuspender. On Sun, 2015-01-25 at 11:00 +0100, Daniel Schürmann wrote: > -rw-r--r--0091-desktop_file.patch445logplain > portaudio still not inter-cooperates with pulseaudio so keeping > pasuspender is a good idea. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ 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] Debian patches
releases the devices when they are no long in use, I meant On Sun, 2015-01-25 at 09:14 -0500, Owen Williams wrote: > I disagree. Since pulseaudio releases the sound devices when they are > in use, starting up mixxx with pulseaudio active is usually fine. If > pulseaudio does grab the sound devices, it's easy to just wait and then > requery sound devices. I think we should stop using pasuspender. > > On Sun, 2015-01-25 at 11:00 +0100, Daniel Schürmann wrote: > > > -rw-r--r--0091-desktop_file.patch445logplain > > portaudio still not inter-cooperates with pulseaudio so keeping > > pasuspender is a good idea. > > > > -- > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > ___ > 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 -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ 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] ./lib/ bundling?
RJ's descriptions includes the various reasons we don't depend on the distro's version of each library. Even xwax has slight modifications so it builds under c++. We depend on external packages when we can, but for some libraries it isn't feasible. On Sun, 2015-01-25 at 17:39 +0100, Nico Schlömer wrote: > Some would argue that bundling is evil [1]. Hence the obvious > question: Why don't we simply depend on this software? > > Cheers, > Nico > > > [1] http://wiki.gentoo.org/wiki/Why_not_bundle_dependencies > > On Sun, Jan 25, 2015 at 5:36 PM, RJ Ryan wrote: > > Hi Nico, > > > > Yes, the lib folder is where we stick code that we didn't write but include > > in our binaries. > > > > apple: some Apple-provided headers needed for our CoreAudio decoder (MP3/AAC > > support on OS X) > > > > fidlib : an audio filter construction library > > > > hidapi : a cross platform HID API > > > > replaygain : the standard replaygain example code, adapted slightly for C++ > > > > soundtouch : a sound resampling library -- it frequently has critical > > (segfault) bugs and so we don't use the distro versions because of the > > slowness of distro updates. > > > > gtest/gmock are only for the tests > > > > vamp: a bundling of the vamp plugin SDK so that users don't have to install > > it themselves (quite a pain on some platforms) > > > > xwax: xwax's timecoder, used for vinyl control > > > > Cheers > > RJ > > > > > > > > > > On Sun, Jan 25, 2015 at 8:22 AM, Nico Schlömer > > wrote: > >> > >> Hi all, > >> > >> When skimming through the mixxx sources, I found > >> ``` > >> $ ls lib/ > >> apple fidlib-0.9.10 gmock-1.7.0 gtest-1.7.0 hidapi-0.8.0-pre > >> replaygain soundtouch-1.8.0 vamp-2.3 xwax > >> ``` > >> This looks like we're bundling third-party software. Do we? > >> > >> Cheers, > >> Nico > >> > >> > >> -- > >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > >> GigeNET is offering a free month of service with a new server in Ashburn. > >> Choose from 2 high performing configs, both with 100TB of bandwidth. > >> Higher redundancy.Lower latency.Increased capacity.Completely compliant. > >> http://p.sf.net/sfu/gigenet > >> ___ > >> 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 > > > > > > -- > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > ___ > 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 -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ 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] Integrating Feature Into Mixxx
Hello Jerrid, we use github for code development and launchpad for bugs and feature requests. If you have a patch ready, I would recommend doing a pull request against our master branch (http://github.com/mixxxdj/mixxx), and then we can take a look at your feature. Or you can just file a bug if you don't have code yet (https://bugs.launchpad.net/mixxx/+filebug) It definitely sounds useful, thanks! cheers, Owen Williams On Wed, 2015-01-28 at 00:01 +, Matthews, Jerrid wrote: > To whom this may concern, > > I am a DJ Mixxx user and use it on my 2 in 1 laptop. I have extended > the codebase so that the Mixxx skin changes automatically to a user > selected (via preferences) Skin A when in laptop mode and Skin B when > in tablet mode. I’d like to discuss the code with the maintainers and > figure out how this can be integrated into the Mixxx codebase for the > community. > > > > Sincerely, > > > > Jerrid Matthews, PhD > > Research Scientist > > w: (408) 765-5185 > > Intel Corp, SC > > Engineering Leadership Program > > > > socialmediaF.socialmediaT.socialmediaL > > > > > -- > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk > ___ 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 -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk ___ 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] rubberband CPU usage
Looking at the load meter in deere, rubberband uses way, way, way more CPU (load?) than soundtouch or the linear stretcher. Is there anything we can do to make it lighter-weight? I'm on a core i7 machine, I'm surprised it's struggling so much. owen -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ 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] rubberband CPU usage
it seems to spike when the rate is changing, ie if vinyl is on On Wed, 2015-03-04 at 22:46 -0500, Owen Williams wrote: > Looking at the load meter in deere, rubberband uses way, way, way more > CPU (load?) than soundtouch or the linear stretcher. Is there anything > we can do to make it lighter-weight? I'm on a core i7 machine, I'm > surprised it's struggling so much. > > owen > > > -- > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > ___ > 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 > > -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ 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] VMS4 & LP Mini fix
Glad you're enjoying it! I went ahead and pulled the patch you posted
since it was so simple.
Unfortunately we don't have a generalized solution for adding 4-deck
support to existing control configs. It'll have to be handled through
scripting. For the VCI-400, the controller itself is nice enough to
send different midi signals depending which way the deck select switch
was flipped, so I didn't have to do very much "if (decks12) {}" stuff
On Wed, 2015-03-11 at 20:48 +0200, Peter G. Marczis wrote:
> Hello everyone !
>
> I have been away for a long time, but I got some free time, and
> fetched the newest master, and ww I'm amazed how many cool changes
> happened around. So I got my controllers out and started to play...
> The first thing I realized that my launchpad mini "play" buttons were
> not okay, so I did a fix for that, pull request sent already.
>
> The other thing brothers me is the kind of bad support of 4 decks with
> my VMS4.
>
> I think I will re-write the VMS4 mapping to match better with 4
> decks.
>
> The question would be if you have any "Deck" switch functionality or
> it has to be handled totally on controller script side ?
>
> Thanks a lot in advance !
>
> Br,
>
> Peter.
>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> 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
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
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] beta?
So how about that release? Do we still have crashing problems on windows? is anyone looking in to that? Any other blockers? owen -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ 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] beta?
I can't in good conscience approve of merging a 7000-line delta change to the bedrock of the Mixxx engine, even if it fixes an issue with mp3 seeking. (I also hate how mp3s skip on the first beat, so I can sympathize). I understand there are new tests, and I'm really thankful for those. But it's going to take a long time to go through that patch and then test to find all the issues with bad tags, weird files and formats, etc etc etc. I think RJ has a collection of horrible mp3s that he'll want to test. To me, sitting two years after the last release, I can't justify the delay that this merge will inevitably cause -- I think we're ready for a beta and can tolerate the mp3 issues we have. (by the way, is there a bug for the mp3 issue you're talking about? I can't find it.) owen On Fri, 2015-03-20 at 09:03 +0100, Daniel Schürmann wrote: > The only remaining blocker for me is the seek offset issue for mp3s. > > > Since we have a fully reviewed solution in > https://github.com/mixxxdj/mixxx/pull/411 of really high code quality, > verified by a new set of unittests, > > we should just merge it and release the beta. > > And yes there is a risk of introducing issues and it surely will, but > by now it fixes much more issues than it might introduce. > > > Of cause I would be happy about any pending PR that can be review and > merged before. > > > 2015-03-20 0:35 GMT+01:00 Owen Williams : > So how about that release? Do we still have crashing problems > on > windows? is anyone looking in to that? Any other blockers? > > owen > > > > -- > Dive into the World of Parallel Programming The Go Parallel > Website, sponsored > by Intel and developed in partnership with Slashdot Media, is > your hub for all > things parallel software development, from weekly thought > leadership blogs to > news, videos, case studies, tutorials and more. Take a look > and join the > conversation now. http://goparallel.sourceforge.net/ > ___ > 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 > > -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ 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] beta?
I still need a pointer to what the mp3 bug even is. On Fri, 2015-03-20 at 07:43 -0700, Gavin Swanson wrote: > I exclusively use mp3s with mixxx. I would imagine there is a large > portion of the mixxx user base that does. > I do not agree with pushing a beta with this kind of issue, if the > intent is not to fix it for this release. If the intent is to get the > beta with all its other features out, and then work this issue through > the beta cycle so it is fixed for release, I could get behind that. > At the same time if the fix is a major-rework of the base of mixxx > then it doesn't make sense to do it during a beta cycle and we should > push beta until its ready. If it's a 1000 line fix with 6000 lines of > unit tests (unlikely), that's a different story. > > > my ¢2 > > > -Gavin S > > Gavin S > > On Fri, Mar 20, 2015 at 7:02 AM, Owen Williams > wrote: > I can't in good conscience approve of merging a 7000-line > delta change > to the bedrock of the Mixxx engine, even if it fixes an issue > with mp3 > seeking. (I also hate how mp3s skip on the first beat, so I > can > sympathize). I understand there are new tests, and I'm really > thankful > for those. But it's going to take a long time to go through > that patch > and then test to find all the issues with bad tags, weird > files and > formats, etc etc etc. I think RJ has a collection of horrible > mp3s that > he'll want to test. > > To me, sitting two years after the last release, I can't > justify the > delay that this merge will inevitably cause -- I think we're > ready for a > beta and can tolerate the mp3 issues we have. (by the way, is > there a > bug for the mp3 issue you're talking about? I can't find it.) > > owen > > > > On Fri, 2015-03-20 at 09:03 +0100, Daniel Schürmann wrote: > > The only remaining blocker for me is the seek offset issue > for mp3s. > > > > > > Since we have a fully reviewed solution in > > https://github.com/mixxxdj/mixxx/pull/411 of really high > code quality, > > verified by a new set of unittests, > > > > we should just merge it and release the beta. > > > > And yes there is a risk of introducing issues and it surely > will, but > > by now it fixes much more issues than it might introduce. > > > > > > Of cause I would be happy about any pending PR that can be > review and > > merged before. > > > > > > 2015-03-20 0:35 GMT+01:00 Owen Williams > : > > So how about that release? Do we still have > crashing problems > > on > > windows? is anyone looking in to that? Any other > blockers? > > > > owen > > > > > > > > -- > > Dive into the World of Parallel Programming The Go > Parallel > > Website, sponsored > > by Intel and developed in partnership with Slashdot > Media, is > > your hub for all > > things parallel software development, from weekly > thought > > leadership blogs to > > news, videos, case studies, tutorials and more. Take > a look > > and join the > > conversation now. http://goparallel.sourceforge.net/ > > ___ > > 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 > > > > > > > > > -- > Dive into the World of Parallel Programming The Go Parallel > Website, sponsored > by Intel and developed in partnership with Slashd
Re: [Mixxx-devel] beta?
Good to know, I'll take a look. On Fri, 2015-03-20 at 15:38 +0100, Max Linke wrote: > https://github.com/mixxxdj/mixxx/pull/511 > > this PR is an absolute blocker for me right now. In the current state > the library scanner will leave the database in an inconsistent state if > it is canceled. > > BTW I also thought the new soundsource API would be merged after the > release. > > best Max > > On 03/20/2015 03:02 PM, Owen Williams wrote: > > I can't in good conscience approve of merging a 7000-line delta change > > to the bedrock of the Mixxx engine, even if it fixes an issue with mp3 > > seeking. (I also hate how mp3s skip on the first beat, so I can > > sympathize). I understand there are new tests, and I'm really thankful > > for those. But it's going to take a long time to go through that patch > > and then test to find all the issues with bad tags, weird files and > > formats, etc etc etc. I think RJ has a collection of horrible mp3s that > > he'll want to test. > > > > To me, sitting two years after the last release, I can't justify the > > delay that this merge will inevitably cause -- I think we're ready for a > > beta and can tolerate the mp3 issues we have. (by the way, is there a > > bug for the mp3 issue you're talking about? I can't find it.) > > > > owen > > > > > > > > On Fri, 2015-03-20 at 09:03 +0100, Daniel Schürmann wrote: > >> The only remaining blocker for me is the seek offset issue for mp3s. > >> > >> > >> Since we have a fully reviewed solution in > >> https://github.com/mixxxdj/mixxx/pull/411 of really high code quality, > >> verified by a new set of unittests, > >> > >> we should just merge it and release the beta. > >> > >> And yes there is a risk of introducing issues and it surely will, but > >> by now it fixes much more issues than it might introduce. > >> > >> > >> Of cause I would be happy about any pending PR that can be review and > >> merged before. > >> > >> > >> 2015-03-20 0:35 GMT+01:00 Owen Williams : > >> So how about that release? Do we still have crashing problems > >> on > >> windows? is anyone looking in to that? Any other blockers? > >> > >> owen > >> > >> > >> > >> -- > >> Dive into the World of Parallel Programming The Go Parallel > >> Website, sponsored > >> by Intel and developed in partnership with Slashdot Media, is > >> your hub for all > >> things parallel software development, from weekly thought > >> leadership blogs to > >> news, videos, case studies, tutorials and more. Take a look > >> and join the > >> conversation now. http://goparallel.sourceforge.net/ > >> ___ > >> 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 > >> > >> > > > > > > > > -- > > Dive into the World of Parallel Programming The Go Parallel Website, > > sponsored > > by Intel and developed in partnership with Slashdot Media, is your hub for > > all > > things parallel software development, from weekly thought leadership blogs > > to > > news, videos, case studies, tutorials and more. Take a look and join the > > conversation now. http://goparallel.sourceforge.net/ > > ___ > > 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 > > > > -- > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutoria
Re: [Mixxx-devel] beta?
How hard would it be to backport the mp3 fix to the current architecture? I would much prefer that. On Fri, 2015-03-20 at 17:18 +0100, Daniel Schürmann wrote: > Here are the bug: > https://bugs.launchpad.net/mixxx/+bug/1407394 > https://bugs.launchpad.net/mixxx/+bug/1281654 > > Uwe and I made significant progress with this beast: > https://github.com/mixxxdj/mixxx/pull/411 > It was continuously improved and testes since 30 Nov 2014 > Some important QM tasks are already finished: > * It is reviewed by a second pair of eyes. > * It has Unit-tests for the most difficult parts > > What is missing: > a) Fire ugly files against it > b) test in the wild bay a broad amount of users > > a) can't take long and b) is ideal done in a beat phase, we will never > have such an attention for the next two years. > > For me this advantages have an higher value than a diffuse change of > introducing new bugs. > And yes new code introduces always new bugs (not a big problem in a > beta) > > > > Am 20.03.2015 um 15:49 schrieb Owen Williams: > > I still need a pointer to what the mp3 bug even is. > > > > On Fri, 2015-03-20 at 07:43 -0700, Gavin Swanson wrote: > >> I exclusively use mp3s with mixxx. I would imagine there is a large > >> portion of the mixxx user base that does. > >> I do not agree with pushing a beta with this kind of issue, if the > >> intent is not to fix it for this release. If the intent is to get the > >> beta with all its other features out, and then work this issue through > >> the beta cycle so it is fixed for release, I could get behind that. > >> At the same time if the fix is a major-rework of the base of mixxx > >> then it doesn't make sense to do it during a beta cycle and we should > >> push beta until its ready. If it's a 1000 line fix with 6000 lines of > >> unit tests (unlikely), that's a different story. > >> > >> > >> my ¢2 > >> > >> > >> -Gavin S > >> > >> Gavin S > >> > >> On Fri, Mar 20, 2015 at 7:02 AM, Owen Williams > >> wrote: > >> I can't in good conscience approve of merging a 7000-line > >> delta change > >> to the bedrock of the Mixxx engine, even if it fixes an issue > >> with mp3 > >> seeking. (I also hate how mp3s skip on the first beat, so I > >> can > >> sympathize). I understand there are new tests, and I'm really > >> thankful > >> for those. But it's going to take a long time to go through > >> that patch > >> and then test to find all the issues with bad tags, weird > >> files and > >> formats, etc etc etc. I think RJ has a collection of horrible > >> mp3s that > >> he'll want to test. > >> > >> To me, sitting two years after the last release, I can't > >> justify the > >> delay that this merge will inevitably cause -- I think we're > >> ready for a > >> beta and can tolerate the mp3 issues we have. (by the way, is > >> there a > >> bug for the mp3 issue you're talking about? I can't find it.) > >> > >> owen > >> > >> > >> > >> On Fri, 2015-03-20 at 09:03 +0100, Daniel Schürmann wrote: > >> > The only remaining blocker for me is the seek offset issue > >> for mp3s. > >> > > >> > > >> > Since we have a fully reviewed solution in > >> > https://github.com/mixxxdj/mixxx/pull/411 of really high > >> code quality, > >> > verified by a new set of unittests, > >> > > >> > we should just merge it and release the beta. > >> > > >> > And yes there is a risk of introducing issues and it surely > >> will, but > >> > by now it fixes much more issues than it might introduce. > >> > > >> > > >> > Of cause I would be happy about any pending PR that can be > >> review and > >> > merged before. > >> > > >> > > >> > 2015-03-20 0:35 GMT+01:00 Owen Williams > >> : > >> > So how abo
Re: [Mixxx-devel] beta?
I'm sorry but I can't just take your word for it that this 7000 line patch is safe to merge. I don't even trust myself to review it, it's too big. If it's the day after a big release then we can risk the breakage, but not right now. My experience has been that these reworks always introduce new problems. If there's a way to just fix the mp3 issues, let's do that. Backporting is annoying, but it's a pretty standard procedure on a major project. On Fri, 2015-03-20 at 22:15 +0100, Daniel Schürmann wrote: > Sure it is possible, but it feels stupid to do that. > Taking effort to exclude useful changes from a patch that is already > reviewed and from a high quality. > The result will be un-reviewed code introduced into a sound source > environment from a poor quality, > without additional tests. > > > > Am 20.03.2015 um 18:30 schrieb Owen Williams: > > How hard would it be to backport the mp3 fix to the current > > architecture? I would much prefer that. > > > > On Fri, 2015-03-20 at 17:18 +0100, Daniel Schürmann wrote: > >> Here are the bug: > >> https://bugs.launchpad.net/mixxx/+bug/1407394 > >> https://bugs.launchpad.net/mixxx/+bug/1281654 > >> > >> Uwe and I made significant progress with this beast: > >> https://github.com/mixxxdj/mixxx/pull/411 > >> It was continuously improved and testes since 30 Nov 2014 > >> Some important QM tasks are already finished: > >> * It is reviewed by a second pair of eyes. > >> * It has Unit-tests for the most difficult parts > >> > >> What is missing: > >> a) Fire ugly files against it > >> b) test in the wild bay a broad amount of users > >> > >> a) can't take long and b) is ideal done in a beat phase, we will never > >> have such an attention for the next two years. > >> > >> For me this advantages have an higher value than a diffuse change of > >> introducing new bugs. > >> And yes new code introduces always new bugs (not a big problem in a > >> beta) > >> > >> > >> > >> Am 20.03.2015 um 15:49 schrieb Owen Williams: > >>> I still need a pointer to what the mp3 bug even is. > >>> > >>> On Fri, 2015-03-20 at 07:43 -0700, Gavin Swanson wrote: > >>>> I exclusively use mp3s with mixxx. I would imagine there is a large > >>>> portion of the mixxx user base that does. > >>>> I do not agree with pushing a beta with this kind of issue, if the > >>>> intent is not to fix it for this release. If the intent is to get the > >>>> beta with all its other features out, and then work this issue through > >>>> the beta cycle so it is fixed for release, I could get behind that. > >>>> At the same time if the fix is a major-rework of the base of mixxx > >>>> then it doesn't make sense to do it during a beta cycle and we should > >>>> push beta until its ready. If it's a 1000 line fix with 6000 lines of > >>>> unit tests (unlikely), that's a different story. > >>>> > >>>> > >>>> my ¢2 > >>>> > >>>> > >>>> -Gavin S > >>>> > >>>> Gavin S > >>>> > >>>> On Fri, Mar 20, 2015 at 7:02 AM, Owen Williams > >>>> wrote: > >>>> I can't in good conscience approve of merging a 7000-line > >>>> delta change > >>>> to the bedrock of the Mixxx engine, even if it fixes an issue > >>>> with mp3 > >>>> seeking. (I also hate how mp3s skip on the first beat, so I > >>>> can > >>>> sympathize). I understand there are new tests, and I'm really > >>>> thankful > >>>> for those. But it's going to take a long time to go through > >>>> that patch > >>>> and then test to find all the issues with bad tags, weird > >>>> files and > >>>> formats, etc etc etc. I think RJ has a collection of horrible > >>>> mp3s that > >>>> he'll want to test. > >>>> > >>>> To me, sitting two years after the last release, I can't > >>>> justify the > >>>> delay that this merge will inevitably cause -- I think we're > >>>> ready for a > >>>>
Re: [Mixxx-devel] beta?
I simply disagree that we have to apply the whole PR to get one bug fix. If there are are other similar issues there should be bugs filed for them so we can judge their severity. There is no reason to rush this patch in. I am not saying we will never merge this PR -- the audio subsystem does need help, and I really appreciate the work. The beta will have bugs. The release will have bugs. But I want to *have* a release, and if we merge this giant patch now that will set the release back by *months*. I don't feel any responsibility to find specific bugs with this PR or "prove" where there are hot spots. The risk is too high. owen On Fri, 2015-03-20 at 22:39 +0100, Daniel Schürmann wrote: > I have really reviewed every single line and it took me quite long, (see > the discussion at GitHub) > Yes it is really big, but it has received the same attention as every > small patch got, devided by the number of lines. > > Can you identify a hotspot of risky changes in the PR? Maybe we can > exude just this. > > Th PR Fixes a lot of issues in every sound-source. We have just the bug > reports for mp3, but Uwe and me have identified > a lot of more similar issues in the other sound-sources. > It is a good idea to have them all fixed in the upcomming release. > > > Am 20.03.2015 um 22:24 schrieb Owen Williams: > > I'm sorry but I can't just take your word for it that this 7000 line > > patch is safe to merge. I don't even trust myself to review it, it's > > too big. If it's the day after a big release then we can risk the > > breakage, but not right now. My experience has been that these reworks > > always introduce new problems. > > > > If there's a way to just fix the mp3 issues, let's do that. Backporting > > is annoying, but it's a pretty standard procedure on a major project. > > > > On Fri, 2015-03-20 at 22:15 +0100, Daniel Schürmann wrote: > >> Sure it is possible, but it feels stupid to do that. > >> Taking effort to exclude useful changes from a patch that is already > >> reviewed and from a high quality. > >> The result will be un-reviewed code introduced into a sound source > >> environment from a poor quality, > >> without additional tests. > >> > >> > >> > >> Am 20.03.2015 um 18:30 schrieb Owen Williams: > >>> How hard would it be to backport the mp3 fix to the current > >>> architecture? I would much prefer that. > >>> > >>> On Fri, 2015-03-20 at 17:18 +0100, Daniel Schürmann wrote: > >>>> Here are the bug: > >>>> https://bugs.launchpad.net/mixxx/+bug/1407394 > >>>> https://bugs.launchpad.net/mixxx/+bug/1281654 > >>>> > >>>> Uwe and I made significant progress with this beast: > >>>> https://github.com/mixxxdj/mixxx/pull/411 > >>>> It was continuously improved and testes since 30 Nov 2014 > >>>> Some important QM tasks are already finished: > >>>> * It is reviewed by a second pair of eyes. > >>>> * It has Unit-tests for the most difficult parts > >>>> > >>>> What is missing: > >>>> a) Fire ugly files against it > >>>> b) test in the wild bay a broad amount of users > >>>> > >>>> a) can't take long and b) is ideal done in a beat phase, we will never > >>>> have such an attention for the next two years. > >>>> > >>>> For me this advantages have an higher value than a diffuse change of > >>>> introducing new bugs. > >>>> And yes new code introduces always new bugs (not a big problem in a > >>>> beta) > >>>> > >>>> > >>>> > >>>> Am 20.03.2015 um 15:49 schrieb Owen Williams: > >>>>> I still need a pointer to what the mp3 bug even is. > >>>>> > >>>>> On Fri, 2015-03-20 at 07:43 -0700, Gavin Swanson wrote: > >>>>>> I exclusively use mp3s with mixxx. I would imagine there is a large > >>>>>> portion of the mixxx user base that does. > >>>>>> I do not agree with pushing a beta with this kind of issue, if the > >>>>>> intent is not to fix it for this release. If the intent is to get the > >>>>>> beta with all its other features out, and then work this issue through > >>>>>> the beta cycle so it is fixed for release, I could get behind that. > >>>>>> At the same time if the fix is a major-rework of the base
Re: [Mixxx-devel] beta?
I would be happy to help review a PR that just fixes the mp3 click issue. On Sat, 2015-03-21 at 03:26 +0100, Daniel Schürmann wrote: > Hi, > > For me the mp3 seek an click issue is a very strong, one that makes > the difference between a toy and a tool. > This is much more notable in Mixxx 1.12 alpha compared to Mixxx 1.11 > because of the new syncing code using a lot more seeks. > > I share your concerns that merging the PR will introduce new issues, > but I do not share that we loose reputation by that, because > thats the essence of a beta phase. > This branch is already reviewed and tested and is used by me and Uwe > without issues. > > Would you mind to fire your collections of faulty files again the > branch. This may help to get a better view on this topic. > I wonder if this is more robust against faulty files than the current > master, because Uwe has fixed some other issues > as well. > > (By the way, this branch introduces also the floating point API, a > great benefit for lossy codecs and a highlight of the "whats new" > list. ) > > Kind regards, > > Daniel > > > > Am 21.03.2015 um 02:38 schrieb RJ Ryan: > > > Hey everyone, > > > > > > Uwe and Daniel's work is awesome and much needed. SoundSource is the > > dark corner of Mixxx that is on average where our lowest-quality > > code lives. It hasn't been touched significantly in years and it > > will be great to fix the long standing bugs associated with it. The > > flip side of not having been touched much in years is that we have 5 > > + years worth of evidence that there are no serious decoding (i.e. > > Critical priority) bugs in SoundSource code. > > > > > > I'm with Owen on this one. The benefits of merging this branch pale > > in comparison to the risks. This release will be our biggest in > > years and it will make headlines. This is not the time for an epic > > refactor to fix some -- frankly minor -- decoding glitches. It is > > not possible to get sufficient testing of this code on the diverse > > libraries that exist in the wild in the beta period for this > > release. There will surely be crash bugs as there are with any > > refactor of complicated code (touches 5+ libraries) that deals with > > corrupt and untrusted input (user audio files). Merging this now > > will both delay the release with bugs we find during the beta period > > and hurt Mixxx's reputation (at a critical time for gaining users) > > with the crash bugs that we don't find during the beta period. > > > > > > Finally, I don't believe Uwe has been operating under the impression > > that this refactor would be part of this release. The PR milestone > > is clearly marked 1.13 and IIRC we discussed it explicitly when he > > was working on it. This was why he spit off multiple pieces of it > > into smaller refactors that have merged already. > > > > > > Cheers, > > RJ > > > > > > > > > > > > On Fri, Mar 20, 2015 at 6:48 PM, Owen Williams > > wrote: > > I simply disagree that we have to apply the whole PR to get > > one bug fix. > > If there are are other similar issues there should be bugs > > filed for > > them so we can judge their severity. There is no reason to > > rush this > > patch in. I am not saying we will never merge this PR -- > > the audio > > subsystem does need help, and I really appreciate the work. > > > > The beta will have bugs. The release will have bugs. But I > > want to > > *have* a release, and if we merge this giant patch now that > > will set the > > release back by *months*. > > > > I don't feel any responsibility to find specific bugs with > > this PR or > > "prove" where there are hot spots. The risk is too high. > > > > owen > > > > On Fri, 2015-03-20 at 22:39 +0100, Daniel Schürmann wrote: > > > I have really reviewed every single line and it took me > > quite long, (see > > > the discussion at GitHub) > > > Yes it is really big, but it has received the same > > attention as every > > > small patch got, devided by the number of lines. > > > > > > Can you identify a hotspot of risky changes in the PR? > > Maybe we can > >
Re: [Mixxx-devel] Control external software from Mixxx?
There are a couple of options you could try right now: * use the javascript / midi interface in Mixxx to write a fake midi device that can relay information from mixxx to your other software. We don't support clock information, but you could relay midi CC or key events. I have some boilerplate python code that creates a midi device. * Write a USB HID driver to mimic a controller, and again leverage the javascript interface. This is harder, but more accurate. * Create a click track, load it into a sampler, and loop it. This way you'd have a bpm-locked click track that you could feed into gear that can sync to that. I think some hacking might be necessary to create a dedicated output for the sampler, but it would be fairly minimal. * Write midi clock in/out support into our Master Sync code, which is a major project I'm planning to do this coming year :). * Just sync it by ear, since there's a bpm display. The sync will drift depending on the sound card clock, but that's a well-known physical limitation. Obviously none of these are ideal, and all will take a decent amount of development. Playing back midi tracks is a really hard problem, because what does it sound like when the user scratches the track? For now you'll have to render out the midi to a waveform and then load that. On Fri, 2015-03-27 at 02:31 +, Disco Patrick wrote: > To expand my idea a little… > > > > The world of digital DJ software is sadly lacking in tools that allow > you to synchronise other media to your music performance. > > > > Personally, I would like to be able to do a number of things: > > > > * Play a video track (apparently supported by Serato) > > * Play a MIDI track (which in turn triggers messages to other systems, > e.g. DMX lighting rig, Quartz Composer visuals). > > * Do one of the above for each track deck that happens to be playing, > e.g. Deck A and Deck B are both playing back independent MIDI tracks. > > > > It's almost as if each deck needs to output a timecode signal, or MIDI > timecode, that other software can pick up on, in addition to the music > track it is already outputting. Come to think of it, isn't ReWire > supposed to do this? > > > > Might it one day be possible to sequence and play back a MIDI track > from within Mixxx itself? > > > > Best, > > Patrick > > > > > > > > > > > > > > "Disco Patrick" wrote: > Hi all, > > > > My aim is to control external software based on song position within a > track - to control, for example, MaxMSP, light shows, visual fx, etc. > > > > Is there anything on the Mixxx development roadmap that would allow > this to happen? > > > > > Does anyone have an opinion on how feasible this would be to add to > Mixxx, perhaps as a personal fork project? > > > > Best, > > Patrick > > > > > > -- > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > ___ > 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 -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ 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] Stanton SCS.3m mapping
Thanks for working on this! It sounds like you don't think this mapping is quite ready to replace the existing 1.11 mapping, but that's all right. If you do more testing and get it to a point where it's working nicely, we'd be happy to merge in the changes. I don't know if anyone else on this list even has that particular controller, so we're prepared to take your word for it :). cheers, Owen On Tue, 2015-03-31 at 02:19 +0200, s...@cis.ch wrote: > Hi everybody > > I've started using Mixxx 1.12. The mapping for the Stanton SCS.3d is > not adapted to 1.12 however. I wrote a version that supports four > decks, you can check it out with git clone > https://github.com/sbalmer/mixxx.scs3m.git > > There are a few "issues" with that code > 1. The controls are updated with noticeable lag > 2. The mapping is not complete > 3. It differs from the existing mapping > 4. Weird plumbing code > 5. Getting the device to light all lights is a crapshoot > 6. I haven't tried mixing with it yet :-) > > Because the mapping has the basic features I need, I'll be trying it > out for a bit. At the same time I intend to update the code to allow > smoother mode changes, and get support for blinking controls. > Depending on how easy it will be to solve the above issues, I intend > to update the SCS.3d mapping as well. > > The midi spec for the device is not available form the Stanton website > anymore. I pulled all the midi messaging details from Sean M. > Pappalardo's mapping. Thanks for those mappings by the way! If anybody > knows where I could get the spec, please let me know. > > If the mapping would be useful to you but doesn't have all the > controls you need, please tell me, they should be easy to add. Patches > are welcome too but be aware that the code is pretty fluid at the > moment. > > Stephan > > -- > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > ___ > 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 > > -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ 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] C++11
Currently our Mac build environment does not support c++11, so none of the features are allowed yet. After this release we will be updating the builders so we can start using it. Owen On Tue, 2015-03-31 at 08:42 +, Nico Schlömer wrote: > Hi all, > > > I'm not sure if this has been asked before, and if yes, please just > point me to the relevant discussion. > Otherwise: Does Mixxx have a policy of what C++11 features are > eligible, or are there any plans for admitting C++11 features to the > source code in the future? > > > Cheers, > Nico > -- > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > ___ > 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 -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ 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] can't edit wiki
I'll see if I can figure out what's going on On Mon, 2015-04-06 at 09:27 -0500, Be wrote: > Any idea what's going on with this? Pegasus said he has no trouble > editing the wiki. Did something get messed up with registering new users > when hard drive space was cleared recently? > > On 03/26/2015 06:56 PM, Be wrote: > > I recently registered an account (be) on the wiki. Whenever I try to > > edit a page, I get an unhelpful error: > > Sorry, there was an error processing your request. If this is an error > > contact us at info AT mydomain.com. > > > > -- > > Dive into the World of Parallel Programming The Go Parallel Website, > > sponsored > > by Intel and developed in partnership with Slashdot Media, is your hub for > > all > > things parallel software development, from weekly thought leadership blogs > > to > > news, videos, case studies, tutorials and more. Take a look and join the > > conversation now. http://goparallel.sourceforge.net/ > > ___ > > 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 > > > -- > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > ___ > 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 > > -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ 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] A good introductory bug for someone
Hey all, I know that aspiring Mixxx hackers are often looking for introductory bugs, so here's one I just filed: https://bugs.launchpad.net/mixxx/+bug/1441161 Right now Mixxx has a drop-down list for the percent adjustment the rate slider allows. I wanted to select a range that isn't available, so it would just be a simple preference window change. The actual code in mixxx doesn't care what the range of the slider is so nothing else needs to change. If anyone wants to get in to Mixxx programming, this would be a good bug to start with and I'd be happy to guide someone along the way. (New developers only please!) Owen -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ 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] A good introductory bug for someone
If you have a launchpad account you can assign the bug to yourself. Let me know if you need any help. Owen On Wed, 2015-04-08 at 15:17 -0700, Seemanta Dutta wrote: > I am very interested in doing this :) > Perfect opportunity for me to learn about the code. > > > Thanks, > Seemanta > > On Tuesday, April 7, 2015, Owen Williams wrote: > Hey all, > > I know that aspiring Mixxx hackers are often looking for > introductory > bugs, so here's one I just filed: > > https://bugs.launchpad.net/mixxx/+bug/1441161 > > Right now Mixxx has a drop-down list for the percent > adjustment the rate > slider allows. I wanted to select a range that isn't > available, so it > would just be a simple preference window change. The actual > code in > mixxx doesn't care what the range of the slider is so nothing > else needs > to change. > > If anyone wants to get in to Mixxx programming, this would be > a good bug > to start with and I'd be happy to guide someone along the way. > (New > developers only please!) > > Owen > > > > -- > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 > standard > Learn Process modeling best practices with Bonita BPM through > live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- > event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > ___ > 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 -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ 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] beta deadline suggestion
I am scheduled to give a demo of Mixxx on May 16th, and I'd like to be able to say that the beta is available. I'm pretty sure we're blocked almost entirely on buildserver issues and perhaps some prettifying of Deere. I also recall some issues with windows builds crashing but I don't know what the status is. Sean, if you can get the new linux builder up and running soon, we'll be in really good shape. Then we need to: * make builds * do smoke-tests on all platforms including separate win32/64 * Take a screenshot on OSX for the blog post -- should show 4 decks and effects. (volunteers?) * push to servers * update blog (draft is already complete, pending screenshot) * facebook / tweet / g+ (maybe including translations to german, etc?) -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ 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] beta deadline suggestion
On Thu, 2015-04-16 at 21:40 +0200, Daniel Schürmann wrote: > Hi Owen, > > beta before May 16th should be possible. > > We have a remaining blocker, the mp3 off beat, click and distortion issues. The current mp3 and soundsource code is the same as in the current 1.11 release, so by definition it's not really a blocker since we already have a release with that same code. Yes, it's a bug, but it shouldn't block the beta or release. We've already discussed this issue. > This and the fact that no on is working on a back port is a good hint > that we should merge > Uwes branch before beta. That no one wants to work on a back port for the mp3 fixes is not an argument in favor of a premature merge. I am happy to make the soundsource review a priority after we do the release. > > The other issue that does not itches me but might be very bad for the > Mixxx reputation at all, is > https://bugs.launchpad.net/mixxx/+bug/1441046 > "Mixxx 1.12: library unusable slow spinning HD Win 8.1 notebook" > IMHO this does no block the beta, but the release. > Does anyone else experience this? Since we are unable to reproduce this issue, it definitely shouldn't block the beta. If anything we're more likely to get bug reports that will help us identify the issue. > > It would be also nice if we can merge the pending fading and clicking > issues in engine buffer. > @Owen will you find time for decide over the pending questions? These are low priority bugs and should not block beta. The last blocker bugs we fixed were the issue with canceled library scans breaking the library, and the soundtouch crash. That sort of data-loss bug and party-crasher are what I mean by blockers. The only other one I can think of is the issue with win64 builds crashing on a lot of systems, but we might just have to tell people to expect that problem and help us get feedback to fix it. owen -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ 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] beta deadline suggestion
Uwe, I truly appreciate the work that you have done on the sound source API. It's an important change and it does fix some long-standing issues. The choice has never been between merging the code or throwing it away. Based on the risks and benefits and our experience with long debugging periods after major feature merges, the prudent choice is to keep the current soundsource API for the 1.12 release. Once it's out the door, then we can immediately look at merging the new API. And as far as I'm concerned, as soon as it's stable, we can do another beta right away. I know it's frustrating to have a feature not make it into a release, but it's a self-perpetuating problem. Because releases are rare, we all want everything we do in the next release. Merging everything in slows down the release cycle, and the cycle repeats. If we released more often, it'd be easier to allow a feature to miss a release, and releases would speed up. Therefore, to stop the current cycle of non-releases, we have to agree to hold off on merging this code until after 1.12. I honestly believe that not merging this code now will make it possible to release this code *sooner*! Owen On Fri, 2015-04-17 at 10:55 +0200, Uwe Klotz wrote: > Just some words from my side. I really don't want to give any > recommendations to you, because I'm biased ;) > > The NewSoundSourceAPI branch has gone through many iterations and > Daniel spent a LOT of time reviewing my code very thoroughly. He also > provided the key ideas to fix the MP3 decoding issues! During the last > months the code base has become pretty stable and we have not > discovered any severe defects lately. It is secured by new tests for > many codecs and moreover the critical parts of the code are guarded by > lots of debug assertions that should indicate potential issues or > wrong assumptions early during development in debug builds. > > Of course, I would feel much safer if the new code had been tested by > experienced developers first before rushing it out to the public. On > the other hand, I personally never switched back to master without any > regrets after what I have found there! > > Main features: > * API: Floating-point sample processing > * API: Explicit notion of #channels instead of implicitly assuming > always stereo > * Update, optimization or even re-implementation (MP3, FLAC, > AAC/M4A, ...) of audio decoding > * Many metadata improvements (parsing, character encoding) > > Open issues: > * Windows build with SoundSourceMediaFoundation > * OS X build with SoundSourceCoreAudio > > Uwe > > On 04/17/2015 09:25 AM, Daniel Schürmann wrote: > > > Hi Owen, > > > > We have collected some test results, they are proving that the new > > sound source branch is more reliable then the master solution. > > > > We have no hints for the opposite. > > > > > > So IMHO is worth to consider the 1.12 merge again. > > > > > > > > Yes, master the sound source api has not changed since 1.11, but > > Mixxx 1.12 actually makes a difference since it use a lot of seeks > > when using the new shiny > > > > beat matching algorithms. > > > > They simply fail with effected mp3 tracks. User may blame the > > syncing code in the first place. > > > > > > > > I hope we will get some results from Ryan Kramer before the desired > > beta date. > > > > > > We are still looking for a user that is able to test the Mac > > builds. > > > > It would be nice, if we could provide build server builds for the > > sound source branch. This would allow much more users to run a > > test. > > > > > > Kind regards, > > > > > > Daniel > > > > > > > > > > > > > > > > > > 2015-04-17 1:42 GMT+02:00 Owen Williams : > > On Thu, 2015-04-16 at 21:40 +0200, Daniel Schürmann wrote: > > > Hi Owen, > > > > > > beta before May 16th should be possible. > > > > > > We have a remaining blocker, the mp3 off beat, click and > > distortion issues. > > > > The current mp3 and soundsource code is the same as in the > > current 1.11 > > release, so by definition it's not really a blocker since we > > already > > have a release with that same code. Yes, it's a bug, but it > > shouldn't > > block the beta or release. We've already discussed this > > issue. > > > > > >
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 environments are built from a clean copy of: > https://github.com/mixxxdj/buildserver/tree/windows_environment > > > All the libraries are built with suitable optimizations turned on. I > also found a potential bug in the portaudio MSVC solution for debug > builds which may have been causing the crash-on-start on 64-bit. > > > > On Sun, Apr 19, 2015 at 9:29 PM, RJ Ryan wrote: > > On Sun, Apr 19, 2015 at 8:49 AM, Max Linke > wrote: > > @rryan: When do you think you find the time to fix > the build server? > > This is the real blocker for a 1.12 release for about > a year now. For > some reason everytime we want to cut a beta release > the build-server > shuts down. Unfortunately there is not much sense in > discussing anything > about a release-date until we have a working > build-server back to ship > out beta-builds on all platforms. > > > I'm working on this... release environment for x86/x64 is > building right now (all alpha builds are built with a debug > environment, not release). Hopefully it'll be done in the > morning (Qt takes forever). The main blocker for the Windows > environment is the portaudio segfaults we've seen in alpha > testing. > > > -- > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > ___ 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 -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ 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
