Found and solved a bug for 64 Studio
 

Hi :)

I had two problems with Rosegarden for Suse 11.0 64-bit and because of
this I found a bug in 64 Studio 64-bit.

Here it is:

spinymouse@64studio:~$ cat /etc/security/limits.conf
[...]
#@audio - memlock 250000
[...]

spinymouse@64studio:~$ rosegarden
[...]
cannot lock down memory for RT thread (Cannot allocate memory)
[...]

I changed limits.conf.

spinymouse@64studio:~$ cat /etc/security/limits.conf
[...]
@audio - unlimited
[...]

After I edited "@audio - unlimited" I didn't get the message "cannot
lock down memory for RT thread (Cannot allocate memory)" Anyway,
Rosegarden is fine for 64 Studio against this message, but it might be
better not to get it.

I had to laugh about Suse, Rosegarden had no DSSI plugins integrated, so
I started it from a terminal and saw that Rosegarden expects the DSSI in
/usr/lib but the package manager says the DSSIs are in /usr/lib64, so
I've done
# cp -r /usr/lib64/dssi /usr/lib and now it seems to be solved. Before I
run Rosegarden in a terminal I searched by Google for the problem and
found some Ubuntu posts with the same problem, but without the answer.

It's good to have a distro like 64 Studio. It looks like the package
builders for Suse and Ubuntu didn't test their packages.

Cheers,
Ralf

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Found and solved a bug for 64 Studio
 

Hi Ralf,

> After I edited "@audio - unlimited" I didn't get the message "cannot
> lock down memory for RT thread (Cannot allocate memory)" Anyway,
> Rosegarden is fine for 64 Studio against this message, but it might be
> better not to get it.

Thanks for the report - setting memlock to unlimited means that your
audio applications get to use all the system's memory, which is probably
OK for a DAW. In practical use, I haven't experienced a system
completely running out of memory this way, but that's perhaps because I
make sure there is enough RAM fitted to avoid swapping to disc.

Cheers!

Daniel

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Found and solved a bug for 64 Studio
 

Gustin Johnson wrote:
> Ralf Mardorf wrote:
> > Hi :)
>
> > I had two problems with Rosegarden for Suse 11.0 64-bit and because of
> > this I found a bug in 64 Studio 64-bit.
>
> > Here it is:
>
> > spinymouse@64studio:~$ cat /etc/security/limits.conf
> > [...]
> > #@audio - memlock 250000
> > [...]
>
> The "#" in the front means that this line is not read.

I know it's the sign to comment things out, resp. for remarks.

> I usually do
> specify a memory limit, so simply commenting this out may have sufficed.

For a default installation it might be better to set memlock to unlimted
or like JAD did, to use a value of ca. 4GB or more.

Cheers,
Ralf


_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Found and solved a bug for 64 Studio
 

Daniel James wrote:
> Hi Ralf,
>
>> After I edited "@audio - unlimited" I didn't get the message "cannot
>> lock down memory for RT thread (Cannot allocate memory)" Anyway,
>> Rosegarden is fine for 64 Studio against this message, but it might be
>> better not to get it.
>
> Thanks for the report - setting memlock to unlimited means that your
> audio applications get to use all the system's memory, which is
> probably OK for a DAW. In practical use, I haven't experienced a
> system completely running out of memory this way, but that's perhaps
> because I make sure there is enough RAM fitted to avoid swapping to disc.
>
> Cheers!
>
> Daniel

Yes, I only have 1920MB of RAM and the swap is unused. With memlock
commented out nothing seems to be different to an active memlock, but it
might be better to set a memlock, maybe PAM or what has to do with
limits.conf will need such settings in the future to work correct. 64
Studio and Suse aren't only DAWs, but I didn't run into troubles with
non-audio applications while memlock is set to unlimited, like it's
recommended on Jack's homepage. I still have troubles with audio Linux
;) ... OT: At the moment I'm making a Song with Suse's Rosegarden,
timing is fine, but Rosegarden sounds static like less good sequencers
do, after some circle playing with an LADSPA FX it crashes etc. ...
anyway, I will see if I can make a groove by using the event editor.
Cubase and even Reaper are much better than Linux sequencers, more
stable and comfortable. Sadly that Reaper with wine has to much jitter
to make music with. However, I'm lucky that making music with Linux is
working at the moment. If 64 Studio 3.0 won't be published in brevity,
I'll reinstall 64 Studio 2.1 again, because I lost some applications
because of dependencies by the upgrade to Lenny for my actual
installation of 64 Studio.

64 Studio is the best audio Linux by default. My actual Suse isn't a
JAD, because JAD isn't up to date, I had to set everything myself and
reading about Ubuntu Studio, users seems to have too much troubles with
it. There are some very strange Linux out there, like Dynebolic, with an
absolute idiotic idea, called nesting.

Thank you for 64 Studio. The only drawback is the KDE < 3.5.9 :(. If
making music with Linux won't keep ready some evil surprises, I won't
install a Windows. I hope Rosegarden will become a more state of the art
sequencer or that Ardour's sequencer will have the features sequencers
have since the end of the 80ies.

I have to say that Reaper running on wine was much more stable and
effective than Rosegarden is ... if there wouldn't be the jitter.

All in all I will live with some week points, because Linux and
applications are FOSS and if more people will become fine with audio
Linux, there will be more people to advance the quality of audio Linux.
One advantage of audio Linux at the moment might be, that e.g. Windows
can't access 4 or more GB RAM, as far as I know.

I will make music now, to compose the first two beats I needed more than
24 hours ;D, I guess now I'm able to work more efficient.

Cheers,
Ralf

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Found and solved a bug for 64 Studio
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> For a default installation it might be better to set memlock to unlimted
> or like JAD did, to use a value of ca. 4GB or more.

Except that if I don't have 4GB of RAM, then bad things could happen if
a program misbehaves. Commented out is the better default IMO.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIqaGkwRXgH3rKGfMRAv4qAJ4z0eFyhPkSrvX7OBg8VM TO1xTzQQCdHciT
4af7GETFL3Ho5FayY59T5rc=
=qJga
-----END PGP SIGNATURE-----

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Found and solved a bug for 64 Studio
 

Gustin Johnson wrote:
>
> > For a default installation it might be better to set memlock to unlimted
> > or like JAD did, to use a value of ca. 4GB or more.
>
> Except that if I don't have 4GB of RAM, then bad things could happen if
> a program misbehaves. Commented out is the better default IMO.
But than there will be an error or warning when e.g. running Rosegarden
from a terminal. "Memlock unlimted" might be the better solution. But I
don't know.

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Found and solved a bug for 64 Studio
 

Ralf Mardorf wrote:
> Gustin Johnson wrote:
>
>>> For a default installation it might be better to set memlock to unlimted
>>> or like JAD did, to use a value of ca. 4GB or more.
>>>
>> Except that if I don't have 4GB of RAM, then bad things could happen if
>> a program misbehaves. Commented out is the better default IMO.
>>
> But than there will be an error or warning when e.g. running Rosegarden
> from a terminal. "Memlock unlimted" might be the better solution. But I
> don't know.
>

Hardly anyone runs Rosegarden from terminal, and I they do, they expect
some messages. Setting something that can cause a hard lockup of your
system is not a wise decision, especially not is it is only to remove a
warning message.

my 2c

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Found and solved a bug for 64 Studio
 

Quentin Harley wrote:
> Ralf Mardorf wrote:
>> Gustin Johnson wrote:
>>
>>>> For a default installation it might be better to set memlock to
>>>> unlimted
>>>> or like JAD did, to use a value of ca. 4GB or more.
>>>>
>>> Except that if I don't have 4GB of RAM, then bad things could happen if
>>> a program misbehaves. Commented out is the better default IMO.
>>>
>> But than there will be an error or warning when e.g. running Rosegarden
>> from a terminal. "Memlock unlimted" might be the better solution. But I
>> don't know.
>>
>
> Hardly anyone runs Rosegarden from terminal, and I they do, they
> expect some messages. Setting something that can cause a hard lockup
> of your system is not a wise decision, especially not is it is only to
> remove a warning message.
>
> my 2c

What might be a good value for memlock? The Computer has got 1920MB
memory for Linux (and 128MB for the integrated ATI).

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users