EKS OTUS RAW HID mapping

[hschabel]

Hi everybody,

wanted to share my latest success feelings as newborn trial and error scriptwriter. It's not yet 100% ready, but maybe someone is interested. I think the concept behind the mapping is quite cool.

Besides jogwheel and hotcues I have my mapping working. But I have the problem, that mixxx freezes regularily after less than an hour, and I don't know why. I guess that the reason is, that mixxx usage memory is running up. If I switch off the OTUS RAW controller, I have found no problems.

Looking forward to get some feedback.

hschabel

[Pegasus]

The freezing could be due to an issue I found in the library we use for HID support. It's been worked around in trunk but not yet in the alpha. Which are you running?

[hschabel]

Hi Pegasus,

Thank you for your help. I have installed mixxx_1.11.0-alpha2-0ubuntu1~trunk~bzr3185_amd64.deb . I had running htop on top of mixxx and found that the memory goes up contineously until I reload the controller configuration im mixxx. The memory usage remains constant for some minutes and then start going up contineously again without any further debug notice. This can be repeated as long until mixxx freezes because the total memory usage of all programs is close to 100%. One time I saw mixxx crashing it was using 87% of 4GB.

I must add that I have no swap partition, because I have 4 GB RAM on my laptop. I didn't have this issue without the OTUS controller connected.

If the reason is not my script this is good to know. If it's an issues of the mixxx program, I hope this issue can be fixed until the official release of mixxx 1.11. I will install the latest version of the trunk as soon as a new is there and see what's happening.

[hschabel]

Hi everybody,

if somebody is interested, I put my latest mixxx mapping online. It works fine for the basic function besides scratching. I don't know why, but scratching is somehow not realtime at all but rather delayed.

I have modified the skin a little bit to resemble to the OTUS LED colors (skin.xml is from LateNightBlues1366x768-WXGA).

Also I have some issues with the hotcue buttons, as sometimes the play button is staying turned on after just hitting the hotcue pad once.

As well memery usage is going higher all the time. Therefore I'm still waiting for a new ubuntu AMD64 built in the trunk.

If somebody can use it, feedback would be appreciated.

[Pegasus]

Can you try running Mixxx under valgrind to find out where the memory is leaking? It may be in the HID library we use instead of Mixxx's code. :S

[hschabel]

Hi,

thanks for the answer. Basically, I think valgrind did what it should, I copied the options from wiki.ubuntuusers.de and have attached the log-file:

sudo G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log mixxx -f

But as far as I have seen it tells me nothing at all. Maybe you are able to see problem?

[rryan]

Thanks for the log! It looks like your distro is stripping debug info from the Mixxx binary so we can't actually see what a lot of the backtraces valgrind provided referred to. I'm not sure how you could get debug symbols other than building it yourself. Could you try that and repeat it?

Best regards,
RJ Ryan

[hschabel]

Hi,

attached my latest mapping. All sending to the DJ-controller is deleted in this mapping.

[hschabel]

Hi rryan,

thanks for the answer. I tried to compile mixxx, but some packages are missing in my installation or named a little bit different. libhss1394 is not availabe as well as protobuf-light. Somehow it worked, but I am not sure for any errors built in.

I restartet valgrind and I copied the options from wiki.ubuntuusers.de as last time:

sudo G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log mixxx -f

But as I saiad it tells me nothing at all. I have seen, that with the compiled version I have some 37 MB of logfile now instead of 841 kB with the downloaded deb package installed. IU have added the mixxx logfile as well. Maybe as mixxx developer you are able to see problem?

Regards
hschabel

[hschabel]

Hi cotton,

I had built mixxx on my laptop. I have no idea about software development, but if I know what to do, I can try. If it's a mixxx problem, i think this should be fixed before the next release.

It would be nice to hear, if other linux systems have the same problem.