My laptop has a 13", 1280x800 screen. My main screen at home is a Dell Ultrasharp 2209WA, 22" and 1680x1050. I don't much like to work with dual screens as I always end up clicking outside the screen I'm supposed to be in, windows keep opening in the wrong screen etc. so I just shut of the laptop screen.
Anyway, after the "reform" where xorg.conf was deemed to be user-unfriendly, it is actually harder to manually add a screen resolution. In Gnome's "Display preferences" window, 1680x1050 was not on the list of possible resolutions. After some googling I found this helpful post about how to add a screen resolution manually with xrandr. After step 3, however, I just used the "Display preferences" dialog to choose the newly added resolution, which makes the rest of the steps unnecessary.
The "Display preferences" is apparently a GUI for xrandr. I hope that in the future, it will be able to add modes as well.
By the way, for those who celebrate: merry christmas!
lördag 26 december 2009
onsdag 23 december 2009
Using a MIDI controller - the Nobels MF-2
I have recently purchased an old MIDI foot controller, a Nobels MF-2 (pictured here). Part 3 of Dave Phillips' "Brief survey" of Linux MIDI applications (from 2004!) directed me towards kmidimon (for monitoring MIDI events) and QMidiRoute (for routing MIDI commands). I still haven't figured out how to hook things up, but the signals from the pedal show up in kmidimon, which is a good sign.
I have yet to read the MF-2 owner's manual (thankfully downloadable from Nobels) and figure out how the pedal itself works. Then I will make an effort to understand this MIDI routing business.
My intention is to control start/stop/overdub in SooperLooper and start/stop active loops in seq24. Any helpful hints are appreciated.
I have yet to read the MF-2 owner's manual (thankfully downloadable from Nobels) and figure out how the pedal itself works. Then I will make an effort to understand this MIDI routing business.
My intention is to control start/stop/overdub in SooperLooper and start/stop active loops in seq24. Any helpful hints are appreciated.
Success with new Jack settings
No wonder there are problems when you are stupid! I was using the obsolete "freebob" driver instead of the newer FFADO "firewire" driver in Jack. Once this was corrected, even Bristol seemed relatively stable. (I'm on Ubuntu Studio (Karmic) using an Edirol FA-66, FYI)
Now I can achieve lower latency, too. With a sample rate of 44.1 kHz and a buffer size of 64 frames/period (latency according to Qjackctl: 4.35 msec) things seem to work well. With a buffer size of 32 (latency: 2.18 msec) Adour disconnects from Jack, and with an even lower setting, my whole system gets very slow. But I've worked with higher latencies than 4.35 msec without being dissatisfied, so this is a win.
At maximum sample rate (192 kHz) I can get down to 4 msec (with 256 frames/period). I can go even lower but then my system gradually gets a bit slow. Somehow Hydrogen doesn't recognize the higher sample rate, or maybe all the samples in the drum kits are recorded with a lower sample rate, because everything gets more high-pitched when Jack is set to a higher rate.
I guess I could tweak the settings more to achieve optimal performance. I don't know what "No memory lock" or "Unlock memory is", and I know even less what the difference between these two is, so I will need to read up on it. Maybe "Periods/buffer" is something to get acquanted with as well. Checking the memory lock boxes has had no apparent effect, though.
Ardour still throws a segmentation fault once in a while, particularly when normalizing a region or when trying to reconnect to Jack once connection was lost (Ardour always dies when I try that at 192 kHz). This is quite annoying, and I hope I can fix it. Hydrogen has also died once for no apparent reason.
In short: I'm back on track. My goal is to have a stable environment for composing, recording and mixing. There are still some things to work out but I'm getting closer!
Now I can achieve lower latency, too. With a sample rate of 44.1 kHz and a buffer size of 64 frames/period (latency according to Qjackctl: 4.35 msec) things seem to work well. With a buffer size of 32 (latency: 2.18 msec) Adour disconnects from Jack, and with an even lower setting, my whole system gets very slow. But I've worked with higher latencies than 4.35 msec without being dissatisfied, so this is a win.
At maximum sample rate (192 kHz) I can get down to 4 msec (with 256 frames/period). I can go even lower but then my system gradually gets a bit slow. Somehow Hydrogen doesn't recognize the higher sample rate, or maybe all the samples in the drum kits are recorded with a lower sample rate, because everything gets more high-pitched when Jack is set to a higher rate.
I guess I could tweak the settings more to achieve optimal performance. I don't know what "No memory lock" or "Unlock memory is", and I know even less what the difference between these two is, so I will need to read up on it. Maybe "Periods/buffer" is something to get acquanted with as well. Checking the memory lock boxes has had no apparent effect, though.
Ardour still throws a segmentation fault once in a while, particularly when normalizing a region or when trying to reconnect to Jack once connection was lost (Ardour always dies when I try that at 192 kHz). This is quite annoying, and I hope I can fix it. Hydrogen has also died once for no apparent reason.
In short: I'm back on track. My goal is to have a stable environment for composing, recording and mixing. There are still some things to work out but I'm getting closer!
måndag 21 december 2009
A bunch of problems
Since last time I wrote, I haven't had access to my equipment and I haven't had time for music making. I'm back now and ready to go. Sadly, I've had a fair share of trouble this far:
1. "Ubuntu Studio controls" don't seem to work for me. I need to set the permissions for /dev/raw1394 manually every time I restart.
2. Ardour crashes during normal usage without further explanation.
3. The Bristol version included in Ubuntu Studio isn't compiled with the Jack driver, which is a big mystery to me. After compiling it from source, I can run hook up a midi keyboard to it through Jack. Sadly, it crashes randomly, emitting the most horrendous sound.
4. ZynAddSubFx crashes too.
On top of this, ALSA sound playback fails every half an hour or so - Rhythmbox gives me a weird Gstreamer error ("pad problem") and Spotify (Wine) just stops playing without further notice.
I'm not so enthusiastic about this as I first was... I think I need to find someone who can help me set up a stable audio production environment, this trial-and-error thing is starting to wear me out.
EDIT: After correcting a mistake, everything works better! The enthusiasm is back. See the next post
1. "Ubuntu Studio controls" don't seem to work for me. I need to set the permissions for /dev/raw1394 manually every time I restart.
2. Ardour crashes during normal usage without further explanation.
3. The Bristol version included in Ubuntu Studio isn't compiled with the Jack driver, which is a big mystery to me. After compiling it from source, I can run hook up a midi keyboard to it through Jack. Sadly, it crashes randomly, emitting the most horrendous sound.
4. ZynAddSubFx crashes too.
On top of this, ALSA sound playback fails every half an hour or so - Rhythmbox gives me a weird Gstreamer error ("pad problem") and Spotify (Wine) just stops playing without further notice.
I'm not so enthusiastic about this as I first was... I think I need to find someone who can help me set up a stable audio production environment, this trial-and-error thing is starting to wear me out.
EDIT: After correcting a mistake, everything works better! The enthusiasm is back. See the next post
Prenumerera på:
Inlägg (Atom)