# 64studio 3.0 observations

• alex stone
Posted: Fri, 03/13/2009 - 03:38
Up and running with a fresh beta 3 (12/3, and the 2.6.29 RT kernel), and i add the following observations so far: During boot up i get a failure "kernel.maps_protect". No idea what this is, but everything kept going.... Once boot is finished, and the os is running, all seems fine so far. (And a good, quick, install with no problems.) I have two midi keyboards, that i don't turn on until the system is running, and qjackctl is open. When i then turn the keyboard on, and they appear in the Qjackctl window, i then get a nasty squawk, and the system locks hard, requiring a hardware reboot. Note: This happened on my regular Hardy UBstudio install at first. I upgraded Alsa from 1.0.16, to a source install 1.0.19, and the problem went away. I could then start and stop eitther or both keyboards, without a problem, or any type of crash. Maybe there's a clue here for the devs. (And it's the only crash or problem i've had.) I used Envy to install the opensource NV driver for graphics, and it all just works. (26" monitor.) And interestingly, i've just installed jack-1.9.1 (jack2) and no problem there either, with the current 1.0.17. So maybe between Alsa and Jack and the kernel, there's a version conflict of some sort. (I can't up update Alsa to 1.0.19 at the moment, because of some sort of missing kernel header or source, but you probably already know that.) I'm doing all this on an AMD64 X2 5600+, with 4 gig of ram, and no fear. I've also upgraded from source, libsndfile, to version 1.0.19. I appreciate this is probably quite brave/foolish/pickone, but there are a couple of apps that require at least 1.0.18, so maybe the devs might like to consider this as well, at least to version 1.0.18. Generally, so far so good, and i'm impressed with how quickly it boots up, and fast in general the OS performs. I've done the usual tweaks for Jack, etc, and with the 1.9.1 Jack2 version, it's running sweetly, and without xruns, at 128/44100/3. That's it so far. I'll install the latest CVS for linuxsampler, etc, and see what happens next. With the above observations taken into account, the sound works, the graphics work, almost directly "out of the box", so nice work fellas. Alex.

## First Segfault

• alex stone
• 11/30/07
• Sat, 03/21/2009 - 07:02
I'm going through some of the other apps i use from time to time, and hit a snag with JackEQ. I get a persistent segfault when trying to open it, with some sort of GTK error. Before i get further into this, can someone do a quick test, and see if they have the same problem. If not, i'll delve further, and try to figure out what's happening. This was consistent with both the repo version, and the source version. (which i D/L and tried for comparison.) Alex.

## realtime parchment studios build?

• skullnotions
• 09/29/07
• Fri, 03/20/2009 - 11:54
Hi Alex, Sure is trial and error on my part, I've mainly used what Free provides with distros. I've been following his work since aGNUla DeMuDi. Great journey. I'm just really venturing into the compile\install world. I want to learn more so I can contribute to Debian Multimedia and help with package maintaining. realtime parchment studios build? Cheers! Dave.

## trial and error

• alex stone
• 11/30/07
• Fri, 03/20/2009 - 10:41
Dave, there's nothing scientific about my 'process' of build, lol. However, i do seem to have a stable result more often than not with the following, based on experience and 4 million user errors. (Still counting) Install kernel/distro (In this case it was a straight install.) Get any graphic issues sorted out. (Please note here, my 64studio 'graphics' install was free of pain, woohoo.) Update Alsa. I've got a bit smarter with this, after several attempts over more than one distro. (Source build) ***NOTE*** I respectfully suggest the 64studio team consider alsa 1.0.19 for a standard install, for the 2.6.29 multimedia kernel. It just plain works, doesn't glitch, or do any of the little sulks that seemed to accompany earlier versions. Even my little G4 /linux ppc Xubuntu build now uses 1.0.19, and the difference in performance and stability is tangible. At least test it for yourself, and see if i'm drawing the right conclusions, or just got very lucky. We get winning combinations sometimes, that just 'click' into place. This one did for me. /end empassioned plea on behalf of new users that may not be as brave/foolish as i am .......... Only once the above is done, do i move on. (Good foundation builds a sturdy palace) Jack. Install Jack, and do all the tweaking and refining. If it doesn't work, i do it again, until it does. Rinse and repeat. Install up to date libs. Libsndfile, libsamplerate, etc.. in other words, all the audio related libs required. QT. I'm looking forward to the day we have up to date builds of this by default, because QT can be a pain in the rear. But it's essential for some apps, and being up to date now, means less pain upgrading later. (RG likes this approach) Only once the above is done, do i move on. (But if i were to update KDE, if i chose to use it, it's this point i'd do that too. I did this with Suse when i tried it, and it paid dividends. Foundation, palace, blah, blah, blah...) Source build of Linuxsampler. This is the meat and potatoes of my setup, so i install this with the right flags, etc. (I include Fantasia in this.) Normally i would source build RG, Ardour, and Jconv here. I've done Jconv for this 64bit 64studio beta 3 build, but RG and Ardour are good to go in the standard install. (I'd dearly like to see Ardour 2.8.1 in the final release, so i hope the 64studio devs will consider this, when Paul finally releases it.) Another lib update, for any extras, like raptor for drobilla-lad, etc.. Install the rest, drobilla-lad, denemo, mscore (sigh), from source, or from straight install, if the version is recent enough. There's been many many errors, and testing done to yield this completely subjective approach, but it works, and testing and checking each stage, as the build profile grows has been worth it. I will say here, that 64studio beta 3 built 'out of the box' for me. (more or less) It only required a couple of tweaks, to have it running nicely. It was after this, that i began adding my requirements, based on my own workflow profile. More to come. :) Alex. p.s. I'm one step ahead of you. Last night i built 64studio with my extra bits, into a realtime parchment studios build. So we're live, and in pursuit of global domination for real!

## linuxsampler cvs

• skullnotions
• 09/29/07
• Fri, 03/20/2009 - 09:47
Hi Alex, Compiling\installing linuxsampler cvs as I type this, then there's only alsa left to do. I probably should have built alsa first? but I have a good idea of the whole process now so I'll make a better job when I start over. Great news about RTC kernel issue. Thanks again for all your guidance ;-) Cheers! Dave.

## alsa

• alex stone
• 11/30/07
• Thu, 03/19/2009 - 18:45
Dave, I installed alsa 1.0.19 from source, taken from the Alsa website. I didn't do anything to it, just a standard install. Alex.

## 2.6.29 - ALSA 1.0.19 - Mscore and Muse

• skullnotions
• 09/29/07
• Thu, 03/19/2009 - 18:09
Hi Alex, The amount of information available regarding these configurations is rare to say the least, you are one of a very few who are looking at this problem. Even finding kernel & alsa 1.0.19 permutations is rare, without adding Mscore, Muse into the equation. I do find references to 2.6.28 and this version of alsa, even then Mscore is missing. You are on new ground here. Going back over the thread is this the only issue remaining: I wonder if Mscore, and Muse use absolute paths, and this is why any variant of rtc (rtc0, rtc1, rtc2) is not sufficient? In the morning I'd like to upgrade alsa to see the results here. Do you have any advice for this? What method did you use? Great work, Checking out this now: Cheers! Dave.

## only issue

• alex stone
• 11/30/07
• Thu, 03/19/2009 - 18:46
Dave, Correct. Only the RTC kernel issue, which Werner has already indicated he's planning to change. (Woohoo) The rest is good. RG, Ardour, Jconv, Linuxsampler, etc, all perform correctly, and without problems. Summary for my 64studio 64bit boot: Kernel= Free's 64studio 64bit 2.6.29-multimedia Alsa = 1.0.19 (and for extra flavour, i'm using a basic asoundrc that points all things alsa through Jack. I have jack as an autostart up app. So it's on from bootup.) HPET max-user-freq timer setting in /etc/sysctl.conf set to 3072. Jack2 (a.k.a. Jackmp) 1.9.1. Tweaks include the usual stuff with RT priority set to 89. I'm using a Delta44 soundcard. Runs at 128/44100/2 now without problems. Stable, and the only xrun i seem to get is when i open and close an app, and even then, only occasionally. QT4 = 4.4.3. No problems here either, but i'm not quite brave enough to try 4.5, just yet. Ardour. Standard version available in 64studio beta 3. No problems. RG. Same, and it runs really well. Jconv = 0.8.0. Fon's latest version, and no problems at all. (Zita-convolver needs updating too, to V1.0.0) Linuxsampler cvs install, latest version. No problems. (0.5.1.11cvs) The rest is reliable, stable, and runs without stalling, glitching, or hesitating. My Beta 3 report so far. I'm not sure i'll even upgrade. This one's a good'un.it So the Os is fine, no problems, no outstanding issues, and bootup shows no errors. I'm hammering it now with a big LS template, Jconv with a large IR, RG, and Ardour with 60tracks, and 40 busses, trying to break something. All good so far. Alex.

## and still more

• alex stone
• 11/30/07
• Thu, 03/19/2009 - 14:57
After taking out the rtc-max-user-freq line from /etc/sysctl.conf, i have a clean boot with no errors, except for 2.6.29-multimedia- source not being installed. (Any news on this?) 64studio starts up ok, with no errors, or kernel failure messages. (Which i've never had with this 2.6.29 kernel during runtime. Nice work, Free. :) ) A quick tip for those who may have a challenge getting devices automounted on startup in 64studio 64bit. Install a little app called mountpy. go to sessions/startup programs, and create a new entry with the following command: sudo mountpy Now, when you boot up, devices are mounted automagically. I used to have this challenge in more than one ubuntu/debian build, and mountpy fixed it. This also works on my debian 5 32bit RT build. More to come.... Alex.

## hpet.

• alex stone
• 11/30/07
• Thu, 03/19/2009 - 14:22
The answer is: Yes. the hpet timer can be set for max-user-freq, the same as rtc. Line in /etc/sysctl.conf as follows: dev.hpet.max-user-freq=3072 (My usual setting, and it seems to work ok.) NOTE** dev.rtc.max-user-freq=3072 does NOT work, and records as a failure in bootup, with alsa 1.0.19 version installed. This makes sense to me, as in /proc, rtc is not listed, but hpet is. So i reckon hpet is emulating rtc successfully, but apps like mscore, built to use one timing source only (rtc) can't use hpet, and don't work without a manual symlink in this instance, for the obvious reason rtc in /dev is actually rtc0. I wonder if Mscore, and Muse use absolute paths, and this is why any variant of rtc (rtc0, rtc1, rtc2) is not sufficient. I've just done the hpet freq (3072), and will report back with any challenges, from hammering the system. (The usual method of screwing the latency right down, then gradually backing off, until i hit the 'sweet spot'). I confess i'm enjoying the challenge. :) Alex. p.s. I'm not a geek, honest.

## Re:2.6.29 & ALSA 1.0.19

• skullnotions
• 09/29/07
• Thu, 03/19/2009 - 13:19
Hi Alex, That's the best response I could have hoped for because you are stating facts where I'm having to go off feelings and google searches (which aren't conclusive). When you say running like a dream then I believe it's running like a dream. If we only have 2 problems Mscore, and Muse, then the hill is not so steep, and if you have a solid foundation with 2.6.29 then that's a great test\result for future development. We just need to research and find fixes if they exist for Mscore, and Muse. It will be a pleasure to travel with you on the journey. Edit: You are testing the base & kernel to fine limits, and it sounds good to me ;-) Cheers! Dave.

## aaah, damn

• alex stone
• 11/30/07
• Thu, 03/19/2009 - 13:09
You're a mischievous rascal, Dave. I don't get enough sleep as it is, and now you introduce me to PDK!! I'll just have a 'quick' look. :) Personally, i don't think there's a problem with Alsa 1.0.19, and the 2.6.29 64studio kernel. The only apps that seem challenged by this are Mscore, and Muse, and as we've remarked, they're strict in their RTC requirements, to the point of digital petulance. Apart from those two, everything else runs like a dream here, and the foundation of kernel, sound device, and jack server is really stable, at low latency. (I'm running 128/44100/3 without a problem.) So i have confidence in the foundation, and have tended to look further 'up' if there's a challenge of some sort. So far, that perspective has been entirely fruitful. We have different results when setting all this up, but my experience is an extremely good one, so far, and certainly better than other builds i've done. Alex.

## 2.6.29 & ALSA 1.0.19

• skullnotions
• 09/29/07
• Thu, 03/19/2009 - 12:00
Hi Alex, Alex wrote: But i would be interested to know if the rtc0 i see in /dev is actually rtc, or a default hpet emulation. - - - - - Yes I'm thinking along these lines also, but you are light years ahead of my knowledge in these respects. Also not having ALSA 1.0.19 installed limits my testing capabilities, but I'm thinking the 2.6.29 kernel and ALSA 1.0.19 are not playing nicely together and are contributing to the hpet\rtc issues. I am also very impressed with the beta3 and this is why I bumped this thread: PDK. I'm only on the first steps with PDK but I'm able to pull 64studio as it is created. Also the builds I have done include a minimal install cd with Emacs Supercollider. However starting with a minimal install blank canvas sees endless options with someone like yourself who could compile\build to your hearts content. The learning curve is not easy, Daniel & Free released an article in the linuxformat 113 magazine, it was titled "Build your own Distro_PDK the hard way". As it says, not easy but well worth the effort. The options could be e.g. Minimal install, 2.6.29 kernel & blank canvas. Brilliant. ;) I'll research Werner's apps and also the work the Denemo team are doing. Keep in touch I love reading your posts. Cheers! Dave

## HPET timer, as opposed to RTC

• skullnotions
• 09/29/07
• Thu, 03/19/2009 - 07:39

## apologies

• alex stone
• 11/30/07
• Tue, 03/17/2009 - 16:45
Sorry Dave, A lack of clarification on my part reference QT. The svn build of musescore is asking for QT4.5, which i understand came out a couple of weeks ago. It doesn't neglect 4.4.3, which i have installed without a problem, but the user has to manually adjust flags in the CMakelist.txt file. (Commenting out a couple and changing 2 others from True to False.) Mscore 0.7. works well enough here, but naturally lacks many of the recent features. That's a choice on my part, not a criticism, or a challenge with the version supplied with 64Studio. (Hence the apology. The version supplied with the OS does work.) The more important issue coming up will be RTC timing, strictly required by mscore, and muse as the only timing option, and the advent in up to date Alsa of Hpet timing. Again, a conversation some time ago with Paul, and Fons, had us all asking the same question. Why does Mscore insist on exclusivity with RTC timing? Rg handles this well in contrast, with more timing options than a swiss clock factory.. So, yes, Mscore 0.7. installs, and is usuable. 0.9.4 will install, with the added dependencies, and me manually adding symlinks, to try and get the rtc stuff sorted out. (I have no RTC on my system. It's RTC0, and i have to create an rtc file, then symlink to the rtc0 file, naming the link "rtc", before it all starts to work.) The svn mscore build "0.9.5" fails with the lack of QT4.5, or builds with warnings, when i comment out the QT4.5 build requirement, then runs in a fragile state, like using a glass hammer to belt a nail. And again, that wretched rtc message............. Sorry for the vague description. Regards, Alex.

## libsndfile jconv Fantasia... Re: A simple setup

• skullnotions
• 09/29/07
• Tue, 03/17/2009 - 11:49
Hi Alex, Great posts, thanks. :-) I've got as far as libsndfile and jconv installed but got a bit distracted finishing my kernel tests, so sorry about the delay in posting. I need to reinstall and go through this first part all over again so as to get comfortable with the process. Libsndfile was the part that I found the most confusing, libsndfile 1.0.19. was the version I went for and it seems to be working ok. I need a step by step compile\install up to jconv to get used to installing the dependencies, it would be great to have installable packages built to make installing easier, and I'm only going to achieve this by taking one step at a time. Gnome allowing the user to define which desktop an app opens into by default is an interesting concept and would certainly be a great aid in workflow. I didn't know kde could do this but I'm going to look into it. Thanks again for all your help. Edit: Before reinstalling I have continued with the howto and compiled and installed down to the java based Fantasia. All seems well but drobilla-lad needed quite a few dependencies installed from debian testing? then the build was clean without any errors, but I'm not sure about pulling from debian testing and mixing sources this way. I also compiled and installed JSampler as a test. Now I just need to learn how to get it all up and running ;-) Cheers! Dave

## the journey continues....

• alex stone
• 11/30/07
• Tue, 03/17/2009 - 14:38

## Traverso

• alex stone
• 11/30/07
• Sun, 03/15/2009 - 12:07
I've had a long term challenge with Traverso, that with later builds of Jack, tends to segfault, and crash. I've also asked Ramon if he could take a look at it, testing with the latest jack version. Can anyone else confirm or deny this? Traverso is quite handy for building 'human' string runs, and unique phrases, etc.. and i'd like to keep using it if possible. Currently, i can only get it running, after a fashion, in my debian 32bit build, but still no success with 64Studio Beta 3. This may well be some sort of user error on my part, so experiences and input from others would be welcome. Alex.

## A simple setup

• alex stone
• 11/30/07
• Sun, 03/15/2009 - 11:42

## qjackctl% & Audio Performance.

• skullnotions
• 09/29/07
• Sun, 03/15/2009 - 09:12
Throughout the process of creating 64studio 3.0 alpha\beta I have used a benchmark project in Ardour to compare Audio performance between 64studio 2.1\lenny dist-upgrade and 3.0 hardy alpha\beta. The 3.0 alpha\beta was always showing the worst performance with the Ardour benchmark project playing looped, it was only a small discrepancy 1% - 2% worse than 2.1\lenny but no amount of tweaks and configuration changes could get the performance to balance until I removed Timidity. Today with Timidity removed I now have 3.0 alpha\beta performance on an equal par and performing the best to date. - - - - - - - - - - - - - - - Daniel wrote: Unfortunately the Ubuntu packages (Timidity, solfege, stopmotion, fam) are where the bugs are, so the better option would be to provide a fixed backport in the repository. Quentin wrote: - - - - - - - - - - - - - - - I'm really enjoying reading your journey so far Alex and it would be great if you would write some howto's and methods\links. I have a fresh install here and would like to try some of the source installs you are using. Cheers! Dave

## Timid

• Quentin Harley
• 05/24/07
• Fri, 03/13/2009 - 19:09
I also removed my Timidity after I tried to decrease the latency and ended up always burning 15% of one of my processors running Timidity in the background - with no advantages I could see.

## shm versus tmp

• alex stone
• 11/30/07
• Fri, 03/13/2009 - 18:58
A quick follow up. /dev/shm kept coming up as a failure at boot verbose, so i switch to the other option of tmp. All is now well with Jack, and the only notification i get is kernel source not installed, which i gather you chaps know about. Dave, thanks for the feedback about Timidity. It confirms there's something going on there that isn't so healthy, or needs a further degree of configuration. Either way, it's gone here, and things are good. The 64Studio OS itself is faster than anything i've used so far. Just simple things like opening and closing windows, running terminal apps, etc, feel......snappier. Hard to quantify, but definitely more sprightly, imho. I reported before about CPU use. I now have linuxsampler (medium orchestra template) jconv with orchestral IR, Ardour 2.7.1 (which is the fastest i've seen it operate), and rosegarden running, all smoothly, and quite a degree more efficiently than i'd previously experienced. No big crashes or stalls at all, so far, so nothing that i could say that needs fixing, or is broken, at this stage.. The testing journey continues......... Alex.

## uninstall Timidity

• skullnotions
• 09/29/07
• Fri, 03/13/2009 - 17:03
Hi Alex, I need to spend more time reading your last post, but I can confirm your Timidity test. After removal here my qjackctl & sound performance is much better. Thanks for the info, I'm looking forward to reading more of your journey into beta3. Cheers! Dave.

## continuing the journey....

• alex stone
• 11/30/07
• Fri, 03/13/2009 - 16:01