1.12.0 Alpha Win (XP,Vista,7,8) / Mac / Linux Testers Needed

Hi folks,

As part of our inch-by-inch progression towards Mixxx 1.12.0 – it was high time we upgraded our old-and-busted build system for Windows, Mac and Linux. We need testers for our new environment!

UPDATE: We are moving on to the next phase of our release process. We are now packaging both debug and release builds. When you go to http://downloads.mixxx.org/builds/1.12/ you will have the choice of release or debug. Please start testing release builds and report (make sure to mention which type you are using).

These build should work on:

  • Ubuntu 14.04 (Trusty) and newer
  • Mac OS X 10.5 through 10.10
  • Windows XP through Windows 8

We need test results from EVERY OS version – so if you are running a less common version we could especially use your help.

Removed direct links since we update builds regularly now. New builds will show up at http://downloads.mixxx.org/builds/1.12/. Click through and select the most recent 32-bit (x86) or 64-bit (x64) build to download.

Attention Ubuntu users – we have a PPA for nightly builds: https://launchpad.net/~mixxx/+archive/ubuntu/mixxxbetas.

Note: You can run Mixxx 32-bit on a 64-bit version of Windows. You can’t run a 64-bit version of Mixxx on a 32-bit version of Windows. If you are on 64-bit Windows, it would be helpful if you could test out both the 32-bit and 64-bit versions.

Please answer the following questions:

  • Mixxx build file name you installed: (for example mixxx-1.12.0-alpha-1.12-git4688-debug-x86.exe). (please post the EXACT file name as it tells us specifically what version you are running – every part is significant!).
  • System Info (processor, RAM, graphics card, etc. – provide as much or as little detail as you want)
  • Windows version AND service pack – right-click My Computer and hit Properties. Example: Windows 7 Professional Service Pack 1
  • Windows 32-bit or 64-bit?
  • Mixxx 32-bit or 64-bit build? (i.e. which you downloaded above)
  • Did the installer succeed?
  • Did it crash on start-up? (If so, how, can you repeat it, what error messages, etc.)
  • Did it crash after start-up? (If so, how, can you repeat it, what error messages, etc.)
  • Did MP3 files load and play?
  • Did M4A/AAC files load and play?
  • Did WAV files load and play?
  • Did FLAC files load and play?
  • Did OGG files load and play?
  • Did Filtered (GL) waveforms work?
  • Did GLSL waveforms work?
  • Did Software waveforms work?
  • Any corruption / glitching?

Known issues:

  • 64-bit Mixxx crash on start-up when 64-bit JACK for Windows is installed.

If a crash occurs – you will be super-awesome if you include any (ideally all) of these:

hey there

i installed mixxx 1.12 alpha next to mixxx 1.11 (by choosing another installation location) on my samsung laptop, which succeeded.
however, when i try to run it, it shows me a windows CMD screen followed by the windows error report (that mixxx has stopped working)
i was like: okay… let’s try again.
same thing happened.
now is the problem that i don’t know where the mixxx log file is located by default, so i made a printscreen of the windows CMD output

my setup details:
laptop: 8gb RAM, AMD A8-4500M series APU with a “old-school” hard disk (no SSD).
windows 8.1 x64
mixxx 1.12 alpha x64 edition
and it keeps crashing on startup, so i couln’t test anything else sadly…

just as a side note: mixxx 1.11 still works normal, only mixxx 1.12 refuses to work.

screenshot below

edit: i am pretty sure i don’t have jackaudio installed.

Playing MP3 and FLAC is OK on Windows 7 SP1 32 bit with Logitech active speakers.
Library context menu (right click on song) doesn’t show any options under ‘BPM Options’.
Effects don’t work.
Preferences/Waveforms/Visual gain: High and Low band labels are switched.

Why we, linux users, don’t get builds masters nowadays? I prefer it to compile where I never get good results. Could you post linux deb builds too? :unamused:

Linux builds are coming – we just need a bigger hard drive for the build server.

Cheers,
RJ

Thank you so much. I’m invalid compiling :frowning: so this is a very important and great new to me :smiley: . Waiting for enjoy it.

Using Win7/64/prof, all updates inside. I7, 8 GB RAM.
Installed Mixxx: mixxx-master-git4661-x64, installed over the 1.11 stable.
Skin is Deere 1920x1080 full HD (what’s the new one? Looks 1.11)

VU-Meter Master right: doesn’t work, shows something but doesnt work while play.
After loading 1, or up to 3, songs (mp3) in deck -> mixxx crashes fully, no infos can read in debug window about this but logfile has informations about the problem. Log is attached. The Crash is exactly when i want to load a song in a deck. Double click song or right mouse key “load in deck_x” (both tested).
Use i wrong skin???

I can give you the event for eventviewer:
Name der fehlerhaften Anwendung: mixxx.exe, Version: 1.12.0.4661, Zeitstempel: 0x541d8936
Name des fehlerhaften Moduls: mixxx.exe, Version: 1.12.0.4661, Zeitstempel: 0x541d8936
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000065621a
ID des fehlerhaften Prozesses: 0xab8
Startzeit der fehlerhaften Anwendung: 0x01cfd4dea80c74ca
Pfad der fehlerhaften Anwendung: C:\Program Files\Mixxx\mixxx.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Mixxx\mixxx.exe
Berichtskennung: 9ceb5777-40d2-11e4-a781-b09928d13640
Mixxx.zip (128 KB)

Thanks dg3nec – the logs help a lot but it would tell us exactly where the problem is if you could get a backtrace:
mixxx.org/wiki/doku.php/creating_backtraces
Could you install GDB for Windows and try that out? Thanks a bunch!

Sorry, problem while download GNU debugger. Message: Too many users at same time …
So, if you have the file, can you store it near the master files for the user who wants help to download it? Thanks

Preliminary test of this alpha (1.12 rev4650) in my lappy (dell e6500, core2duo, intel gma4500hd gfx, no controllers attached for now). Everything is 32bits (x86).

On a clean Win7 sp1 installs fine and seems to work with all the defaults.

But under XP sp3, installs fine but crash always when started. The problem is clearly with opengl, because if i modify manually the mixxx.cfg file to edit the waveforms value from 6 to 0, works fine. But if again i try any accelerated GL option (inside mixxx or through .cfg), crash again.
Driver is from intel, 6.14.10.5417 (6/15/2012), WHQL (or so it says… :mrgreen: )

Attached microsoft debug tool report.

If you need the log (or other files), i can upload it, but imho doesn’t seem to be much help in this case… :wink:

PD: Intel support for opengl under windows (at least with >3years HW) left a lot to be desired. I probably would add another shortcut to the desktop for launching mixxx as a “safe mode”, that disables waveforms (or use the SW version), but it’s just a suggestion :stuck_out_tongue:
crashlog.txt (13 KB)

Related to the problem reported by dg3nec about the VU-meters, i have found a way to reproduce easily (at least on my laptop, in both xp and w7).

Load a song on any deck, start playing it, and then just modify any EQ channel (any tiny amount) put the VU-meter of the deck and the global one on the reds for a second -weird because the green bar/sound volume is nowhere near- , and then they are “locked” (are not updated any more, keep the last value). So you can “lock” one vu-meter and the global one, and keep using the other… until you equalize it, that is :slight_smile:.

Gain or FX seems to work fine and don’t trigger the bug.

May i fill a standard bug report on launchpad?

Update: Related to the EQ’s, the kill buttons also triggers this bug, just using a controller directly triggers the bug -because it has to restore the controller position by script at init, don’t know-), and the only part that is “locked” is the green bar, because i’ve seen that the reds continue to work as usual :wink:. As a side note, i have an script for the nanoKontrol2, that use the lights as vumeter, and it fails exactly the same as the screen.

BTW, the EQ part has been touched? It seems that they are messed up… highs are lows, meds are highs and low does nothing… :question:

And following with the “spam”, another report :mrgreen:

On the same laptop e6500 as the other tests, but this time on a win8.1 (x86) with jack and the controllers (hercules dj control using HID and nanokontrol2 using MIDI), and a previous (used and “working” (*)) installation of mixxx 1.11, it works just fine. I run the setup, installed it on another folder, and just works. It replaces the shortcut on the desktop, pointing to the new one (1.12), but you can still launch the old, and use one or the other.

The only problem i’ve seen is with the EQs/vumeters, as said before.

(*) I try to use it with low latency, and gives the same problems that gives me 1.11 (controllers lost randomly in the middle of a session), as in here [url]https://mixxx.discourse.group/t/threads-latency-and-race-conditions/14409/1], but this is not a new bug and i can “up” the latency, so it doesn’t matter for now :mrgreen:

Here are my gdb crash what ryan said he wants.

About my VU-Meter: i have nothing done on EQ, Gain or so. Only start Mixxx, load songs and play. Then crash. In this case, i cant test more :wink:
mixxx_crash_dg3nec_20140921_1350.txt (15 KB)

Another report :mrgreen:

This time on linux (ubuntu studio x64), mixxx 1.12 alpha revision 4664 (hot from the press :laughing:)… here there are no problems with the vu-meters, and through i see visually how waveforms changes with each EQ knob (low included), and i’m using the laptop speakers :blush: , i still find that they don’t sound right.

Following done because mixxx crashes:

  • de-installed mixxx 12 & 11 (files saved before)
  • Windows full crash blue screen
  • restart
  • Mixxx program folder renamed, new installation with 1.12
  • Mixxx crash
  • AppData Mixxx folder renamed, mixxx starts like “fresh” installation
  • while scanning the new set music folder, extremely many message in debugger: “TagLib: MPEG::Header::parse() – Invalid sample rate.” (wau, the scan takes over 1 hour)
  • now testing my problem that mix crashes when load songs… nothing :slight_smile:

So my problem must be found in the old settings. Found in Local Settings - Application Data - Mixxx.
I will now go forward and test something. Setting up my configuration inside mixxx. Goal is to have the old database! I hope that the database is NOT the reason for my crash!

Auto DJ:
Click on “AutoDJ” start/stop does not start and stop song play.
No song chang at the end with smooth change to other deck.
Manual start stop song doesn’t help.

This is a heroic amount of debug info! Keep it coming! Thanks a bunch.

Mmmm, windows BSOD sounds bad :frowning:

Do you have a c:\windows\minidump folder? If so, do you have some (small, probably) file there from this BSOD timestamp?

More to my crash while loading song:

After the fresh installation it was better. Now test my database (mixxxdb.sqlite), because i want have my infos inside it.

  • Renamed fresh database, copy my old inside folder-> mixxx crashes by loading song (old problem)
  • Now i scan my music again (with the old database that crash me the mixxx), test mixxx crashes
  • Again, start mixxx, rescan databease, test, mixxx crashes

To make it shure, rename the databases back. I have now the new from fresh installation. Test… works. GRMPFTL

Summary: My problem is my database!? Hope the team can help. Databes ZIP made, but 15MB, so i send it to ryan via mail.

(MANY THANKS)

An usability issue: the preferences dialog is so big that in fact it almost fulfill the work area of a (standard windows OS) 1280x800 screen (taskbar included). If windows (the OS) decides to draw the dialog on a vertical negative coordinate (and it does sometimes :mrgreen:) the only way (that i know) to get back to normal is ALT+Space and move it, but i assume it could be a problem for some… I don’t know if you can center the dialog through code on a portable manner, or if could give more problems on multi-displays setups.

Being resizable for both, width and height, perhaps would be easier to just default to a lower size. Usually modern laptops are at least 1366x768, but old netbooks could be as low as 1024x600, and you need a little of “breath space” for resize/open/close (truth be told, i still don’t know why windows (the OS) do that “randomly”).