Remastersys and AVLinux Forum
May 24, 2013, 10:28:37 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Remastersys 3.0.4-2 for Ubuntu Lucid and Newer including Quantal Released
 
   Home   Remastersys Home Remastersys downloads Donate Login Register AV LINUX Home Help Search  
Pages: [1]
  Print  
Author Topic: couple of suggestions for the next AV manual  (Read 1017 times)
0 Members and 1 Guest are viewing this topic.
danboid
Full Member
***
Offline Offline

Posts: 46


« on: January 03, 2012, 08:43:37 AM »

Happy new year GMaq and fellow AV'ers!

I have a couple of suggested additions to improve the next version of your fine manual GM:

1 - How to set the default session for slim display manager

I'm not entirely sure this is the 'proper' way to do it but the way that works for me is to edit /etc/slim.conf as root and look for the line like:

login_cmd           exec /bin/bash -login /etc/X11/Xsession startxfce4

and then just change the last parameter to be the command required to start your WM or DE of choice. It'd be good to give a few common examples like startxfce4, icewm, awesome or whatever too.

2 - You do mention how to change the default CPU governor settings but I think an example like this would be a great help:

[battery]
governor=ondemand
[ac]
governor=performance
[governor]
default=performance

Best wishes all for 2012!

Dan
Logged
GMaq
Administrator
Hero Member
*****
Offline Offline

Posts: 2163


A/V 'Nixer


WWW
« Reply #1 on: January 05, 2012, 10:10:18 AM »

Hi danboid,

Will get it into next revision, thanks
Logged

AV Linux, Proudly created with Remastersys: http://www.bandshed.net/AVLinux.html
trulan
Global Moderator
Hero Member
*****
Offline Offline

Posts: 855


« Reply #2 on: January 05, 2012, 10:03:50 PM »

It wouldn't be a bad idea to make those CPU governor settings default. I've been using it that way for quite a while and it seems to be pretty solid.  That way, desktop users won't have to worry about glitches cause by CPU scaling, and laptop users wouldn't be burning their batteries unless they actually want to.
Logged
GMaq
Administrator
Hero Member
*****
Offline Offline

Posts: 2163


A/V 'Nixer


WWW
« Reply #3 on: January 05, 2012, 10:45:47 PM »

Already done!
Logged

AV Linux, Proudly created with Remastersys: http://www.bandshed.net/AVLinux.html
danboid
Full Member
***
Offline Offline

Posts: 46


« Reply #4 on: February 01, 2012, 01:20:43 PM »

Thanks GMaq for incorporating those suggestions into 5.0.3 but I have yet another suggestion for the 'Using JACK' section of the manual and/or the default JACK settings. I really don't want to see the JACK section of the manual get much longer than it already is because there really is only so much the average user actually NEEDS to know about getting JACK to run well but this is one of them.

Within the screenshot of the qjackctl settings of the 5.0.2 manual you have timeout set to 2000 msec although I believe the default in qjackctl and AV Linux is 500 msec. 500 msec is too low a setting for anyone wanting to use multiple MIDI instrument (eg VSTi, LV2, DSSI) plugins within a qtractor or A3 session and with that kind of setting users are likely to find they cannot open sessions that contain more than a few plugins or at least this was my experience and I thought it was a bug in the plugins or the host for a while.

Rui recommends a JACK client timeout value of at least 3000 msec so I set mine to 5000 because its the most liberal default - multi-MIDI plugin sessions have been working great for me since!
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!