lmuse-user

[Lmuse-user] Getting MusE2 beta2 running on Arch

[Pieter B. <pi...@re...>]

Hi All,

Just downloaded the second beta version of MusE2 from Sourceforge, read 
the README and tried to get it running. I was curious so instead of 
creating the build directory myself, I ran "compile_muse.sh". I can 
start muse2, but when I do:

[pieter@s061123 ~]$ muse2
QGtkStyle was unable to detect the current GTK+ theme.
Denormal protection enabled.
no locale <muse_en_US>/</usr/local/share/muse-2.0beta/locale>
Trying RTC timer...
RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
   precise timer not available
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 66
starting with default template
WARNING: Cannot lock memory:: Cannot allocate memory
JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
JACK: buffersize changed 128
WARNING: Cannot lock memory:: Cannot allocate memory
AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer 
(max is 300)
   freq stays at 300 Hz
WARNING: Cannot lock memory:: Cannot allocate memory

Ok, first things first. I don't care that my theme isn't recognized, 
probably an inconsistency between GTK2 and GTK3 or something?
About the RTC timer, I read that I should be able to access it. However, 
my /dev/rtc seems to point to /dev/rtc0:

[pieter@s061123 ~]$ ls -l /dev/rt*
lrwxrwxrwx 1 root root       4 May 22 20:23 /dev/rtc -> rtc0
crw-rw---- 1 root audio 254, 0 May 22 20:23 /dev/rtc0

I am a member of the audio group:
[pieter@s061123 ~]$ groups
lp wheel games video audio optical storage scanner power users

The README says something about "/proc/sys/dev/rtc/max-user-freq", but I 
don't even have the rtc directory in /proc/sys/dev.

Next the memory thing, what should I do about this?

I hope you guys can help me as good as almost a year back, Tim and 
Robert helped me a lot when I just started using MusE on Ubuntu!

Cheers,
Pieter

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Florian J. <flo...@we...>]

this probably won't help you much, but i'm getting the same error 
messages and muse works fine as a MIDI sequencer for me; i didn't try 
any wave-stuff, however

greetings
flo


Am 23.05.2011 00:10, schrieb Pieter Barendrecht:
> Hi All,
>
> Just downloaded the second beta version of MusE2 from Sourceforge, read
> the README and tried to get it running. I was curious so instead of
> creating the build directory myself, I ran "compile_muse.sh". I can
> start muse2, but when I do:
>
> [pieter@s061123 ~]$ muse2
> QGtkStyle was unable to detect the current GTK+ theme.
> Denormal protection enabled.
> no locale<muse_en_US>/</usr/local/share/muse-2.0beta/locale>
> Trying RTC timer...
> RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
>     precise timer not available
> Trying ALSA timer...
> AlsaTimer::initTimer(): best available ALSA timer: system timer
> got timer = 66
> starting with default template
> WARNING: Cannot lock memory:: Cannot allocate memory
> JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
> JACK: buffersize changed 128
> WARNING: Cannot lock memory:: Cannot allocate memory
> AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer
> (max is 300)
>     freq stays at 300 Hz
> WARNING: Cannot lock memory:: Cannot allocate memory
>
> Ok, first things first. I don't care that my theme isn't recognized,
> probably an inconsistency between GTK2 and GTK3 or something?
> About the RTC timer, I read that I should be able to access it. However,
> my /dev/rtc seems to point to /dev/rtc0:
>
> [pieter@s061123 ~]$ ls -l /dev/rt*
> lrwxrwxrwx 1 root root       4 May 22 20:23 /dev/rtc ->  rtc0
> crw-rw---- 1 root audio 254, 0 May 22 20:23 /dev/rtc0
>
> I am a member of the audio group:
> [pieter@s061123 ~]$ groups
> lp wheel games video audio optical storage scanner power users
>
> The README says something about "/proc/sys/dev/rtc/max-user-freq", but I
> don't even have the rtc directory in /proc/sys/dev.
>
> Next the memory thing, what should I do about this?
>
> I hope you guys can help me as good as almost a year back, Tim and
> Robert helped me a lot when I just started using MusE on Ubuntu!
>
> Cheers,
> Pieter
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Lmuse-user mailing list
> Lmu...@li...
> https://lists.sourceforge.net/lists/listinfo/lmuse-user
>
>    

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Pieter B. <pi...@re...>]

Thanks for your reply Florian. Yeah, I wouldn't mind those messages if 
MusE worked fine, however it doesn't. I can add MIDI tracks, but when I 
want to add a SoundFont (Add Synth -> MESS -> FluidSynth Soundfont 
Loader By ...), that window freezes.

Output in my terminal:

[pieter@s061123 ~]$ muse2
QGtkStyle was unable to detect the current GTK+ theme.
Denormal protection enabled.
no locale <muse_en_US>/</usr/local/share/muse-2.0beta/locale>
Trying RTC timer...
RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
   precise timer not available
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 66
starting with default template
WARNING: Cannot lock memory:: Cannot allocate memory
JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
JACK: buffersize changed 128
WARNING: Cannot lock memory:: Cannot allocate memory
AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer 
(max is 300)
   freq stays at 300 Hz
WARNING: Cannot lock memory:: Cannot allocate memory
Application asked to unregister timer 0x55000010 which is not registered 
in this thread. Fix application.
Application asked to unregister timer 0x2f000004 which is not registered 
in this thread. Fix application.
fluidsynth sampleRate 48000
JACK ERROR: zombified - calling shutdown handler
Audio::shutdown()
sequencer still running, something is very wrong.

Furthermore, I wondered how up-to-date the main README file is? It says 
something about "realtime-lsm", I don't have that module installed and 
I'm not sure where I can find it. I assume I need to load it using 
modprobe, right?

Thanks,

Pieter


On 05/23/2011 11:38 AM, Florian Jung wrote:
> this probably won't help you much, but i'm getting the same error
> messages and muse works fine as a MIDI sequencer for me; i didn't try
> any wave-stuff, however
>
> greetings
> flo
>
>
> Am 23.05.2011 00:10, schrieb Pieter Barendrecht:
>> Hi All,
>>
>> Just downloaded the second beta version of MusE2 from Sourceforge, read
>> the README and tried to get it running. I was curious so instead of
>> creating the build directory myself, I ran "compile_muse.sh". I can
>> start muse2, but when I do:
>>
>> [pieter@s061123 ~]$ muse2
>> QGtkStyle was unable to detect the current GTK+ theme.
>> Denormal protection enabled.
>> no locale<muse_en_US>/</usr/local/share/muse-2.0beta/locale>
>> Trying RTC timer...
>> RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
>>      precise timer not available
>> Trying ALSA timer...
>> AlsaTimer::initTimer(): best available ALSA timer: system timer
>> got timer = 66
>> starting with default template
>> WARNING: Cannot lock memory:: Cannot allocate memory
>> JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
>> JACK: buffersize changed 128
>> WARNING: Cannot lock memory:: Cannot allocate memory
>> AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer
>> (max is 300)
>>      freq stays at 300 Hz
>> WARNING: Cannot lock memory:: Cannot allocate memory
>>
>> Ok, first things first. I don't care that my theme isn't recognized,
>> probably an inconsistency between GTK2 and GTK3 or something?
>> About the RTC timer, I read that I should be able to access it. However,
>> my /dev/rtc seems to point to /dev/rtc0:
>>
>> [pieter@s061123 ~]$ ls -l /dev/rt*
>> lrwxrwxrwx 1 root root       4 May 22 20:23 /dev/rtc ->   rtc0
>> crw-rw---- 1 root audio 254, 0 May 22 20:23 /dev/rtc0
>>
>> I am a member of the audio group:
>> [pieter@s061123 ~]$ groups
>> lp wheel games video audio optical storage scanner power users
>>
>> The README says something about "/proc/sys/dev/rtc/max-user-freq", but I
>> don't even have the rtc directory in /proc/sys/dev.
>>
>> Next the memory thing, what should I do about this?
>>
>> I hope you guys can help me as good as almost a year back, Tim and
>> Robert helped me a lot when I just started using MusE on Ubuntu!
>>
>> Cheers,
>> Pieter
>>
>>
>> ------------------------------------------------------------------------------
>> What Every C/C++ and Fortran developer Should Know!
>> Read this article and learn how Intel has extended the reach of its
>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>> developers boost performance applications - including clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> Lmuse-user mailing list
>> Lmu...@li...
>> https://lists.sourceforge.net/lists/listinfo/lmuse-user
>>
>>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Lmuse-user mailing list
> Lmu...@li...
> https://lists.sourceforge.net/lists/listinfo/lmuse-user
>

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Florian J. <flo...@we...>]

Hi

did you compile muse2 from scratch? or did you have some old build 
directory, and just did svn update and make again?
because, in this case, it sometimes happens that cmake links an old 
(incompatible!) object file into your binary. this leads to all kinds of 
memory corruption and errors.

if you did this, erase the build/ directory, and recreate it. make clean 
is not enough.

flo

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Pieter B. <pi...@re...>]

Hi Flo & Robert,

I just downloaded the source and compiled from scratch, on my freshly
installed Arch Linux.

Some time ago I used Ubuntu and got MusE1 running, after some help from
you guys.

When I start QJackCTL, the message output says:

12:55:49.854 Patchbay deactivated.
12:55:49.869 Statistics reset.
12:55:49.874 ALSA connection change.
12:55:49.893 JACK connection change.
12:55:49.896 Client activated.
12:55:49.903 Buffer size change (128).
cannot lock down memory for RT thread (Cannot allocate memory)

Even though my /etc/security/limits.conf has these values:

@audio          -       rtprio          95
@audio          -       nice           -10
@audio          -       memlock         unlimited

Unlimited, just to be sure for now. I am member of the audio group:

[pieter@s061123 ~]$ groups
lp wheel games video audio optical storage scanner power users

Screenshot of Jack settings:
http://www.redpanda.nl/JackSettings.png

So, I started muse2 with flag -D:

======================================================================================================

[pieter@s061123 ~]$ muse2 -D
QGtkStyle was unable to detect the current GTK+ theme.
Denormal protection enabled.
Muse: using unoptimized non-SSE dsp routines
Start euid: 1000 ruid: 1000, Now euid 1000
initJackAudio()
initJackAudio(): client MusE opened.
initJackAudio(): registering client...
JACK: sample rate changed: 48000
JackAudioDevice::scanMidiPorts:
global lib:       </usr/local/lib/muse-2.0beta>
global share:     </usr/local/share/muse-2.0beta>
muse home:        </home/pieter>
project dir:      <./>
user instruments: </home/pieter/.config/MusE/instruments>
no locale <muse_en_US>/</usr/local/share/muse-2.0beta/locale>
scan ladspa plugin dir </usr/local/lib/muse-2.0beta/plugins>
loadPluginLib: adding ladspa
plugin:/usr/local/lib/muse-2.0beta/plugins/doublechorus.so
name:DoubleChorus label:doublechorus1 loadPluginLib: adding ladspa
plugin:/usr/local/lib/muse-2.0beta/plugins/freeverb.so name:Freeverb
label:freeverb1 loadPluginLib: adding ladspa
plugin:/usr/local/lib/muse-2.0beta/plugins/pandelay.so name:PanDelay
label:pandelay scan ladspa plugin dir </usr/local/lib64/dssi> scan
ladspa plugin dir </usr/lib64/dssi> scan ladspa plugin dir
</usr/local/lib/dssi> scan ladspa plugin dir </usr/lib/dssi>
loadPluginDir: ladspa
path:/usr/local/lib64/ladspa:/usr/lib64/ladspa:/usr/local/lib/ladspa:/usr/lib/ladspa
loadPluginDir: loading ladspa dir:/usr/local/lib64/ladspa scan ladspa
plugin dir </usr/local/lib64/ladspa> loadPluginDir: loading ladspa
dir:/usr/lib64/ladspa scan ladspa plugin dir </usr/lib64/ladspa>
loadPluginDir: loading ladspa dir:/usr/local/lib/ladspa scan ladspa
plugin dir </usr/local/lib/ladspa> loadPluginDir: loading ladspa
dir:/usr/lib/ladspa scan ladspa plugin dir </usr/lib/ladspa>
loadPluginLib: adding ladspa plugin:/usr/lib/ladspa/amp.so name:Mono
Amplifier label:amp_mono loadPluginLib: adding ladspa
plugin:/usr/lib/ladspa/amp.so name:Stereo Amplifier label:amp_stereo
loadPluginLib: adding ladspa plugin:/usr/lib/ladspa/delay.so
name:Simple Delay Line label:delay_5s loadPluginLib: adding ladspa
plugin:/usr/lib/ladspa/filter.so name:Simple Low Pass Filter label:lpf
loadPluginLib: adding ladspa plugin:/usr/lib/ladspa/filter.so
name:Simple High Pass Filter label:hpf loadPluginLib: adding ladspa
plugin:/usr/lib/ladspa/noise.so name:White Noise Source
label:noise_white loadPluginLib: adding ladspa
plugin:/usr/lib/ladspa/sine.so name:Sine Oscillator (Freq:audio,
Amp:audio) label:sine_faaa loadPluginLib: adding ladspa
plugin:/usr/lib/ladspa/sine.so name:Sine Oscillator (Freq:audio,
Amp:control) label:sine_faac loadPluginLib: adding ladspa
plugin:/usr/lib/ladspa/sine.so name:Sine Oscillator (Freq:control,
Amp:audio) label:sine_fcaa loadPluginLib: adding ladspa
plugin:/usr/lib/ladspa/sine.so name:Sine Oscillator (Freq:control,
Amp:control) label:sine_fcac scanDSSIDir: scan DSSI plugin dir
</usr/local/lib64/dssi> scanDSSIDir: scan DSSI plugin dir
</usr/lib64/dssi> scanDSSIDir: scan DSSI plugin dir
</usr/local/lib/dssi> scanDSSIDir: scan DSSI plugin dir </usr/lib/dssi>
scanDSSIDir: found /usr/lib/dssi/less_trivial_synth.so scanDSSILib:
name:LTS listname:LTS lib:less_trivial_synth listlib:less_trivial_synth
audio ins:0 outs:1 control ins:6 outs:0 scanDSSIDir:
found /usr/lib/dssi/karplong.so scanDSSILib: name:karplong
listname:karplong lib:karplong listlib:karplong audio ins:0 outs:1
control ins:1 outs:0 scanDSSIDir:
found /usr/lib/dssi/trivial_sampler.so scanDSSILib: name:stereo_sampler
listname:stereo_sampler lib:trivial_sampler listlib:trivial_sampler
audio ins:0 outs:2 control ins:5 outs:0 scanDSSILib: name:mono_sampler
listname:mono_sampler lib:trivial_sampler listlib:trivial_sampler audio
ins:0 outs:1 control ins:4 outs:0 scanDSSIDir:
found /usr/lib/dssi/trivial_synth.so scanDSSILib: name:TS listname:TS
lib:trivial_synth listlib:trivial_synth audio ins:0 outs:1 control
ins:2 outs:0 QtLibraryPath: </usr/lib/qt/plugins> </usr/local/bin>
Song::clear load user instrument definitions from
</home/pieter/.config/MusE/instruments> load instrument definitions
from </usr/local/share/muse-2.0beta/instruments> READ
IDF /usr/local/share/muse-2.0beta/instruments/Access_Virus.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Akai-SG01v.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Alesis-QS-78R.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/AlesisQS6.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Emu-4mbgsgmmt-sf.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/emuproteus2000.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/gm.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/gs.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Hammond_XB-1.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Korg-MS2000R.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Korg-X50.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Korg-X5DR-PresetA.idf
READ
IDF /usr/local/share/muse-2.0beta/instruments/Korg-X5DR-PresetB.idf
READ IDF /usr/local/share/muse-2.0beta/instruments/Kurzweil-SP2X.idf
READ IDF /usr/local/share/muse-2.0beta/instruments/MC303.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/MC505.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/ns5r.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Roland-E28.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Roland-JV90.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Roland-SCD70.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Roland-XP30.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Roland_FantomXR.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Roland_SRX-02.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Roland_SRX-09.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Waldorf-microQ-Factory2000.idf
READ
IDF /usr/local/share/muse-2.0beta/instruments/Waldorf-microQ-Factory2001.idf
READ
IDF /usr/local/share/muse-2.0beta/instruments/Waldorf-microQ-Phoenix.idf
READ IDF /usr/local/share/muse-2.0beta/instruments/Waldorf-microQ.idf
READ IDF /usr/local/share/muse-2.0beta/instruments/Waldorf-Q.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Waldorf_Microwave-I.idf
READ IDF /usr/local/share/muse-2.0beta/instruments/xg.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-01v.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-Motif-Rack.idf
READ IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-Motif.idf
READ IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-P100.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-P50m.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-PSR275.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-PSR530.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/Yamaha-S90.idf READ
IDF /usr/local/share/muse-2.0beta/instruments/ZynAdd-1_4.idf
initMidiAlsa ALSA port add: <Midi Through Port-0>, 14:0 flags 3 0x63
ALSA port add: <qjackctl>, 128:0 flags 1 0xc2 Trying RTC timer...
RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission
denied precise timer not available Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer got
timer = 66 searching for software synthesizer in
</usr/local/lib/muse-2.0beta/synthi> 11 soft synth found starting with
default template Song::clear setRecord recordflag =0 f(record state)=0
autoRecEnable=1 WARNING: Cannot lock memory:: Cannot allocate memory
JACK ERROR: cannot lock down memory for RT thread (Cannot allocate
memory) JACK: graph changed JACK: buffersize changed 128 JACK:
registration changed JACK: registration changed
JACK: port connections changed: A:4 B:2 isConnect:1
JACK: graph changed
JACK: port connections changed: A:5 B:3 isConnect:1
JACK: graph changed
MusE::seqStart: getting audio driver realTimePriority:5
WARNING: Cannot lock memory:: Cannot allocate memory
Thread <Prefetch, id 0xb2615b70> has SCHED_FIFO priority 6
AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer
(max is 300) freq stays at 300 Hz
WARNING: Cannot lock memory:: Cannot allocate memory
Thread <Midi, id 0xb1e14b70> has SCHED_FIFO priority 7
looping waiting for sequencer thread to start
Audio::seek already there
JackAudioDevice::scanMidiPorts:
JackAudioDevice::scanMidiPorts:
Audio::seek already there
fluidsynth sampleRate 48000
JACK ERROR: zombified - calling shutdown handler
Audio::shutdown()
sequencer still running, something is very wrong.
Killed

======================================================================================================

Cheers,
Pieter


On Tue, 24 May 2011 11:05:38 +0200
Florian Jung <flo...@we...> wrote:

> Hi
> 
> did you compile muse2 from scratch? or did you have some old build 
> directory, and just did svn update and make again?
> because, in this case, it sometimes happens that cmake links an old 
> (incompatible!) object file into your binary. this leads to all kinds
> of memory corruption and errors.
> 
> if you did this, erase the build/ directory, and recreate it. make
> clean is not enough.
> 
> flo
> 
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery, 
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Lmuse-user mailing list
> Lmu...@li...
> https://lists.sourceforge.net/lists/listinfo/lmuse-user

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Robert J. <spa...@gm...>]

Hi Pieter,

2011/6/5 Pieter Barendrecht <pi...@re...>:
>
> Screenshot of Jack settings:
> http://www.redpanda.nl/JackSettings.png

The memory error printed in the qjackctl is that from muse or does
jack print it by itself?

It looks like something causes your system to fail memory locking.
>
> So, I started muse2 with flag -D:

Does muse2 start after this? It seems to me the memory error should be
fixed but muse2 hopefully starts anyway.

Regards,
Robert

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Pieter B. <pi...@re...>]

Hi,

The memory error is from jack itself. MusE displays the same error when
I start it after Jack is running. The GUI appears, I can import a MIDI
file, but when I want to load a SoundFont with a loader, it crashes.

Regards,
Pieter

PS: I use mpd for my music, but I stopped the daemon before starting
Jack. Moreover, a recent issue (with udev if I remember correctly)
makes me start the snd_seq module manually.


On Sun, 5 Jun 2011 17:15:03 +0200
Robert Jonsson <spa...@gm...> wrote:

> Hi Pieter,
> 
> 2011/6/5 Pieter Barendrecht <pi...@re...>:
> >
> > Screenshot of Jack settings:
> > http://www.redpanda.nl/JackSettings.png
> 
> The memory error printed in the qjackctl is that from muse or does
> jack print it by itself?
> 
> It looks like something causes your system to fail memory locking.
> >
> > So, I started muse2 with flag -D:
> 
> Does muse2 start after this? It seems to me the memory error should be
> fixed but muse2 hopefully starts anyway.
> 
> Regards,
> Robert

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Geoff B. <ge...@la...>]

On 06/06/2011 06:11 PM, Pieter Barendrecht wrote:
> Still confused about the Memory Errors, I'm going to check out the Arch
> forums once more to see whether others have this same issue with Jack.
are you using a RT kernel Pieter?

g.

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Robert J. <spa...@gm...>]

Hi Pieter,

2011/5/23 Pieter Barendrecht <pi...@re...>:
> Thanks for your reply Florian. Yeah, I wouldn't mind those messages if
> MusE worked fine, however it doesn't. I can add MIDI tracks, but when I
> want to add a SoundFont (Add Synth -> MESS -> FluidSynth Soundfont
> Loader By ...), that window freezes.
>
> Output in my terminal:
>
> [pieter@s061123 ~]$ muse2
> QGtkStyle was unable to detect the current GTK+ theme.
> Denormal protection enabled.
> no locale <muse_en_US>/</usr/local/share/muse-2.0beta/locale>
> Trying RTC timer...
> RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
>   precise timer not available

RTC is the best timer

> Trying ALSA timer...
> AlsaTimer::initTimer(): best available ALSA timer: system timer

ALSA is good enough if it does not complain about too low rate

> got timer = 66
> starting with default template
> WARNING: Cannot lock memory:: Cannot allocate memory
> JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
> JACK: buffersize changed 128
> WARNING: Cannot lock memory:: Cannot allocate memory
> AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer
> (max is 300)
>   freq stays at 300 Hz


This is the complaint.
A rule of thumb is that frequencies below 1000 may be audible if you
are very sensitive to such things.
So 300 Hz means you may experience audible jitter.

> WARNING: Cannot lock memory:: Cannot allocate memory

These lock errors may point to a problem. Please see link below.

> Application asked to unregister timer 0x55000010 which is not registered
> in this thread. Fix application.
> Application asked to unregister timer 0x2f000004 which is not registered
> in this thread. Fix application.

These errors are bad, we need to find why this happens.

> fluidsynth sampleRate 48000
> JACK ERROR: zombified - calling shutdown handler
> Audio::shutdown()
> sequencer still running, something is very wrong.

----

Please try starting with 'muse2 -D' to and post the printout, it may
give some more clues to why it fails totally.
What version of jack do you have and what arguments do you use to start it?

Did I understand correctly that you had 1.x working on the same system?

> Furthermore, I wondered how up-to-date the main README file is? It says
> something about "realtime-lsm", I don't have that module installed and
> I'm not sure where I can find it. I assume I need to load it using
> modprobe, right?

Oh. that is old. The realtime-lsm has not been used for a long time.
We need to update the READMEs.
For a start I updated this page in the muse support docs
http://muse-sequencer.org/index.php/Realtime
with a pointer to jacks instructions and recommendations.

Regards,
Robert

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Geoff B. <ge...@la...>]

On 05/23/2011 08:10 AM, Pieter Barendrecht wrote:
> Hi All,
>
> Just downloaded the second beta version of MusE2 from Sourceforge, read
> the README and tried to get it running. I was curious so instead of
> creating the build directory myself, I ran "compile_muse.sh". I can
> start muse2, but when I do:
>
> [pieter@s061123 ~]$ muse2
> QGtkStyle was unable to detect the current GTK+ theme.
> Denormal protection enabled.
> no locale<muse_en_US>/</usr/local/share/muse-2.0beta/locale>
> Trying RTC timer...
> RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
>     precise timer not available
> Trying ALSA timer...
> AlsaTimer::initTimer(): best available ALSA timer: system timer
> got timer = 66
> starting with default template
> WARNING: Cannot lock memory:: Cannot allocate memory
> JACK ERROR: cannot lock down memory for RT thread (Cannot allocate memory)
> JACK: buffersize changed 128
> WARNING: Cannot lock memory:: Cannot allocate memory
> AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer
> (max is 300)
>     freq stays at 300 Hz
> WARNING: Cannot lock memory:: Cannot allocate memory
>
> Ok, first things first. I don't care that my theme isn't recognized,
> probably an inconsistency between GTK2 and GTK3 or something?
> About the RTC timer, I read that I should be able to access it. However,
> my /dev/rtc seems to point to /dev/rtc0:
>
> [pieter@s061123 ~]$ ls -l /dev/rt*
> lrwxrwxrwx 1 root root       4 May 22 20:23 /dev/rtc ->  rtc0
> crw-rw---- 1 root audio 254, 0 May 22 20:23 /dev/rtc0
>
> I am a member of the audio group:
> [pieter@s061123 ~]$ groups
> lp wheel games video audio optical storage scanner power users
>
> The README says something about "/proc/sys/dev/rtc/max-user-freq", but I
> don't even have the rtc directory in /proc/sys/dev.
>
> Next the memory thing, what should I do about this?
>
> I hope you guys can help me as good as almost a year back, Tim and
> Robert helped me a lot when I just started using MusE on Ubuntu!

do you still require assistance Pieter?

g

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Pieter B. <pi...@re...>]

Hmm, when I start MusE without Jack running (just for testing purposes),
I _can_ load a SoundFont.

Still confused about the Memory Errors, I'm going to check out the Arch
forums once more to see whether others have this same issue with Jack.

Pieter

On Sun, 5 Jun 2011 17:36:34 +0200
Pieter Barendrecht <pi...@re...> wrote:

> Hi,
> 
> The memory error is from jack itself. MusE displays the same error
> when I start it after Jack is running. The GUI appears, I can import
> a MIDI file, but when I want to load a SoundFont with a loader, it
> crashes.
> 
> Regards,
> Pieter
> 
> PS: I use mpd for my music, but I stopped the daemon before starting
> Jack. Moreover, a recent issue (with udev if I remember correctly)
> makes me start the snd_seq module manually.
> 
> 
> On Sun, 5 Jun 2011 17:15:03 +0200
> Robert Jonsson <spa...@gm...> wrote:
> 
> > Hi Pieter,
> > 
> > 2011/6/5 Pieter Barendrecht <pi...@re...>:
> > >
> > > Screenshot of Jack settings:
> > > http://www.redpanda.nl/JackSettings.png
> > 
> > The memory error printed in the qjackctl is that from muse or does
> > jack print it by itself?
> > 
> > It looks like something causes your system to fail memory locking.
> > >
> > > So, I started muse2 with flag -D:
> > 
> > Does muse2 start after this? It seems to me the memory error should
> > be fixed but muse2 hopefully starts anyway.
> > 
> > Regards,
> > Robert
> 
> 
> ------------------------------------------------------------------------------
> Simplify data backup and recovery for your virtual environment with
> vRanger. Installation's a snap, and flexible recovery options mean
> your data is safe, secure and there when you need it. Discover what
> all the cheering's about. Get your free trial download today. 
> http://p.sf.net/sfu/quest-dev2dev2 
> _______________________________________________
> Lmuse-user mailing list
> Lmu...@li...
> https://lists.sourceforge.net/lists/listinfo/lmuse-user

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Pieter B. <pi...@re...>]

On Tue, 07 Jun 2011 08:24:36 +1000
Geoff Beasley <ge...@la...> wrote:

> On 06/06/2011 06:11 PM, Pieter Barendrecht wrote:
> > Still confused about the Memory Errors, I'm going to check out the
> > Arch forums once more to see whether others have this same issue
> > with Jack.
> are you using a RT kernel Pieter?
> 
> g.

At the moment I don't, I wanted to see the results without one first.
By the way, the Memory Errors are gone now - I decided not to kill mpd,
but just stop the music. Might have an other reason, but they are gone.

However, still no RTC  permissions, and MusE keeps crashing when I want
to load a SoundFont using a loader.

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Tim E. R. <ter...@ro...>]

On June 6, 2011 06:34:14 pm Pieter Barendrecht wrote:
> On Tue, 07 Jun 2011 08:24:36 +1000
>
> Geoff Beasley <ge...@la...> wrote:
> > On 06/06/2011 06:11 PM, Pieter Barendrecht wrote:
> > > Still confused about the Memory Errors, I'm going to check out the
> > > Arch forums once more to see whether others have this same issue
> > > with Jack.
> >
> > are you using a RT kernel Pieter?
> >
> > g.
>
> At the moment I don't, I wanted to see the results without one first.
> By the way, the Memory Errors are gone now - I decided not to kill mpd,
> but just stop the music. Might have an other reason, but they are gone.
>
> However, still no RTC  permissions, and MusE keeps crashing when I want
> to load a SoundFont using a loader.
I'm fixing problems in there.
If it crashes only when you move the cursor to position zero, that's one
 of the bugs I'm fixing now. Wait 'till I've got this done and then try again.

If it crashes as soon as you try to load a soundfont in the Fluidsynth dialog,
 then that's another problem I'll have to look at. 

I should be done within next few days.

Don't worry too much about the RTC, only one thing can use it at a time,
 and likely Jack midi is using it. So MusE should fall back to using an 
 ALSA timer. 

Tim.

Re: [Lmuse-user] Getting MusE2 beta2 running on Arch

[Geoff K. <gs...@gm...>]

Hi Pieter,
I know you don't use Fedora, but this link might help setting up permissions
to use the rtc and other things.  I do most of this stuff on my Fedora 14
setup.

http://forums.fedoraforum.org/showpost.php?p=1406122&postcount=6


You might also try these (or something like them) first to see if you can
get it working before setting up the login files.   this might enable the
rtc for you and set it to a better frequency for audio work. As root...

chmod 660 /dev/rtc0
chgrp audio /dev/rtc0
echo 2048 >/sys/class/rtc/rtc0/max_user_freq
echo 2048 >/proc/sys/dev/hpet/max-user-freq
cat /sys/class/rtc/rtc0/max_user_freq
cat /proc/sys/dev/hpet/max-user-freq

Hope this helps.  Geoff K