Hello, lists.
Not long ago I tried KX Studio 10.04.1 (updated LiveDVD) and installed it from stratch.
I am very glad to see linuxsampler, included to this distro. Of course, there is more notable things, but it is most for me.
2) Missing dependies: jack-netsource-gui from zenity.
3) Also, disk content's size is less then 2 Gb, so some packages would be nice included to disk: MuseScore, Aeolus, Ingen.
4) Needs packaging Cinecutie; cinelerra doesn't support unicode (very critical for russian and like users), not speaking about GUI. I don't see any reason to use cinelerra instead cinecutie. Both cinecutie and cinelerra have own PPA, maintained by Akirad.
Now a question: what is difference between kernels: linux-preempt from general ubuntu 10.04 repo and lowlatency/realtime kernels from kxstudio? There are two things, that caused me to be interested with kernel from standard ubuntu repository:
1) problems with Nouveau drivers at realtime kernel (nouveau module not found, though I have installed headers) and
2) When I select lowlatency driver, it goes into mode, specified with video= parameter, only after some time, when splash already appeared with theme, not specified through default.plymouth alternative.
On 7 July 2010 10:43, Philipp Überbacher <hollunder(a)lavabit.com> wrote:
> Excerpts from James Morris's message of 2010-07-07 11:33:57 +0200:
>> On 7 July 2010 10:12, Philipp Überbacher <hollunder(a)lavabit.com> wrote:
>> > Excerpts from James Morris's message of 2010-07-07 10:42:31 +0200:
>> >> Hi,
>> >>
>> >> Yoshimi 0.58 crashes when loading a padsynth instrument from instrument menu.
>> >>
>> >> The attached instrument fails, as does a simple test instrument with
>> >> default params.
>> >>
>> >> Cheers,
>> >> James.
>> >
>> > Tried with that instrument. I wouldn't call it 'falling asleep', it's
>> > chewing all CPU it can get and needs a SIGKILL to stop.
>>
>> On AMD64. Htop shows an S beside it which I take means it's asleep,
>> and it isn't using very much CPU at all. It needs kill -9 to kill it.
>> Switching to a padsynth instrument from the bank list does work
>> however.
>
> I'm on an Intel celeron single core 64bit and 64bit Linux, so there's
> one thing in common. I only tried 'yoshimi -L filename'.
Uh interesting, it loads plinkyplank1.xiz successfully from the
command line here, thanks.
James.
Hi Jeremy
Thanks for your help. I have installed rtirq-init right now and was able to
set it up right( I wasnt last time) When I run htop i can see my pccard ,
firewire and jack in top.
I did the changes in setup you mentioned.
But the problem is unfortunatly not solved. Jack still stops when
framesperiod is low or create xruns when high.
Best Thomas
2010/6/25 Jeremy Jongepier <jeremy(a)autostatic.com>
> On 06/25/2010 03:55 PM, Thomas Hedegaard wrote:
> > firewire ERR: wait status < 0! (= -1)
> >
> > DRIVER NT: could not run driver cycle
> >
>
> Hello Thomas,
>
> This could indicate something is blocking the data stream, in your case
> maybe the Radeon card. Are you using rtirq-init? If not it may be wise
> to give it a try: http://ubuntuforums.org/showthread.php?t=1328175 and
> http://subversion.ffado.org/wiki/IrqPriorities
> I would also set JACK's prio lower, maybe 70 would be better. And
> Firewire cards, in my personal experience, work better with a periods
> setting of 2 instead of 3.
>
> Best,
>
> Jeremy
>
>
Drumstick is a C++ wrapper around the ALSA library sequencer interface using
Qt4 objects, idioms and style. ALSA sequencer provides software support for
MIDI technology on Linux. Complementary classes for SMF and WRK file
processing are also included. This library is used in KMetronome, KMidimon
and KMid2, and was formerly known as "aseqmm".
Changes:
* New visibility attribute for all public classes allowing client programs to
be compiled with hidden visibility if desired.
* Better error reporting for all the utilities.
* Subdirectory "tests" renamed as "utils".
* Utility "smfplayer" renamed as "guiplayer" and enhanced with a new interface
design and support for Cakewalk WRK files.
Copyright (C) 2009-2010, Pedro Lopez-Cabanillas
License: GPL v2 or later
Project web site
http://sourceforge.net/projects/drumstick
Online documentation
http://drumstick.sourceforge.net/docs/
Downloads
http://sourceforge.net/projects/drumstick/files/0.4.0/
a program i'm making (yes that one) will benefit from knowing about
musical scales. i looked in the source code for non-sequencer (i'll
look at arpage next), and adapted an array there into the following
form:
{ "Major", { 1, 0, 1, 0, 1, 1, 0, 1, 0, 1, 0, 1 }},
{ "Natural Minor", { 1, 0, 1, 1, 0, 1, 0, 1, 1, 0, 1, 0 }},
{ "Harmonic Minor", { 1, 0, 1, 1, 0, 1, 0, 1, 1, 0, 0, 1 }},
{ "Melodic Minor", { 1, 0, 1, 1, 0, 1, 0, 1, 0, 1, 0, 1 }},
{ "Major Pentatonic", { 1, 0, 1, 0, 1, 0, 0, 1, 0, 1, 0, 0 }},
{ "Minor Pentatonic", { 0, 0, 0, 1, 0, 1, 0, 1, 0, 0, 1, 0 }},
{ "Chromatic", { 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1 }}
(1 means a note is part of that scale, 0 means it is not).
so for C Major:
{ "Major", { 1, 0, 1, 0, 1, 1, 0, 1, 0, 1, 0, 1 }},
c c# d d# e f f# g g# a a# b
(Unless I'm mistaken) all the above scales can be transposed to work
with any key.
Now I'm not very musical, and found my way to wikipedia, specifically this page:
http://en.wikipedia.org/wiki/Whole_tone_scale
Which says "In music, a whole tone scale is a scale in which each note
is separated from its neighbours by the interval of a whole step.
There are only two complementary whole tone scales, both six-note or
hexatonic scales:
* {C, D, E, F♯, G♯, A♯, C}
* {B, D♭, E♭, F, G, A, B}.
"
Which is confusing for me because it seems I can represent it in the array as:
{ "Whole Tone", { 1, 0, 1, 0, 1 ,0, 1, 0, 1, 0, 1, 0 }},
But goes on to say I it is impossible for any key other than "c" or
"b" but the array representation seems to show it could work for any
key.
Can anyone explain?
Cheers,
James.
Hi, all!
I have completed new(actually old) song recently --
http://kompoz.com/t/91208
hydrogen, ardour, japa, jkmeter and jamin was used -- many thanks to its
authors.
I will be happy to read your opinions, especially about my "mastering".
--
Truly yours, Oleg Ivanenko aka Ash
[if it wasn't so sad, it would be funny]
On 07/06/2010 07:04 PM, Louigi Verona wrote:
> "it is simply not possible to stop people from copying without taking
> away a very big infrastructure that the people using to do the copying
> on are going to defend to the death"
>
> and it can be argued that it is simply impossible in question.
> torrents are "underground", but they are so common that I would say
> that in fact legal shops are more underground than the pirate bay.
> and so if, say, they make it illegal to use a computer that was not
> authorized by Microsoft or Apple, with DRM built into their systems,
> most of the population will simply be using illegal hardware (and, of
> course, illegal software). Also, it will create a very tense
> situation. It is very hard to pass a law that does not allow a company
> to create hardware they want. It will ruin a lot of businesses and in
> turn they will have enough power to ruin the entertainment "industry".
>
> So I am confident that battle will be lost.
>
> L.V.
But with industry heavily invested in the mission to control how the
information is distributed and external forces pushing for the industry
to handle it in draconian ways it will no doubt be a long battle to the
bitter end. Quite probably a war of attrition has already been started.
--
Patrick Shirkey
Boost Hardware Ltd
Hi people of linuxland once again I seem to have found the volume knob
on my guitar so I took the liberty of turning it all the way to 11,
which is how this first piece of this project best should be entering
your ear drums.
10 timmar (10 hours)
It's in swedish. Basically it's about stage fright :).
http://spamatica.se/thecharlesdarwinevolutionexperience/
/Robert
On 5 July 2010 08:18, Philipp Überbacher <hollunder(a)lavabit.com> wrote:
> Excerpts from James Morris's message of 2010-07-02 15:37:33 +0200:
>> On 2 July 2010 11:46, Philipp Überbacher <hollunder(a)lavabit.com> wrote:
>> > Excerpts from Gabriel M. Beddingfield's message of 2010-07-02 01:57:17 +0200:
>> >>
>> >> On Thu, 1 Jul 2010, James Morris wrote:
>> >>
>> >> > It's like a sequencer in that the user will be able to create rhythmic
>> >> > patterns which lack pitch and velocity data, and almost like an
>> >> > arpeggiator in that it will automatically generate the pitch and
>> >> > velocity data from an algorithm - and unlike either a sequencer or
>> >> > arpegiattor, it uses a 2d window-placement like algorithm to generate
>> >> > pitch/velocity (mapping these to x/y).
>> >>
>> >> The more I think about this... the more fun it sounds.
>> >>
>> >> Have you considered doing an MDI interface? This way you
>> >> can go back to spamming windows... but it stays contained in
>> >> your applications MainWindow.
>> >
>> > Since most window managers support a 'workspace' concept I guess it's
>> > not a big deal. But who uses xterm? :) And fixed size? What about tiling
>> > window managers?
>>
>> The window placement algorithm is done, and I spent quite some time
>> getting it working satisfactorily performance-wise, within real time
>> constraints. The idea is based upon window-manager window-placement,
>> but in the distant future - when the app is up and running with a nice
>> shiny GUI - the user might not ever care nor need to care, that the
>> boxes that appear simultaneously as notes are played is based upon
>> window-manager window-placement. I don't think it will be necessary to
>> place much emphasis on it's origins. It's only that way right now
>> because I've not evolved my thinking about how to describe it further
>> than "it's like a window-manager's window-placement" :-)
>>
>>
>> And what are you referring to as fixed size?
>>
>>
>> Cheers,
>> james.
>
> Quote:
> "It's currently in the "i demand an xterm at least 128 x 128 in size
> but i still can't do anything you might want me to do" stage."
>
> As I don't really understand the concept I have no idea whether the
> terminal window size matters or not, it just seems like it would be
> large for windows that are placed for placements sake. As said before,
> I've no idea what I'm talking about since I don't know how window
> placement translates to anything musical.
I've tried to be as clear as possible here:
http://wiki.github.com/jwm-art-net/BoxySeq/at-a-glance
xterm is used only because writing to a terminal is the simplest
method for a program to provide a user with information about what is
happening. size of the xterm matters only if you want to make any
sense of what boxyseq is displaying - it won't affect the behaviour of
boxyseq in any way.
forget any ideas in your mind about boxyseq placing windows on your
desktop - this won't happen. all i've done is written some code which
emulates the window-placement strategy of the fluxbox window
manager... and used it for other purposes. with boxyseq, the "window
placement" is just a scanning of bits followed by a manipulation of
bits which happens within a data array.
the basis of the idea is best represented by the following single line of text:
"window-manager window-placement".
the simplest way to represent the data that results from this idea is
by creating a textual representation of that binary data and
displaying it in a terminal. (then i can watch in real time what is
happening :-) and see if it's working properly :-)
i don't want to implement a complex way (GUI) of representing the data
until i have a solid foundation to build upon.
really it is far too early for users to take any interest in this
program. but sometimes I just need some feedback about some of the
ideas i have before I can proceed further in its development.
Cheers,
James.
> --
> Regards,
> Philipp
>
> --
> "Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
>
>
