Hello, two quick questions:
* Is there someone here using Ubuntu (16.04 LTS) with a hard RT
PREEMPT kernel?
* Can he tell me how to obtain it? Probably not pre-built from a
repository/ppa, I've done my homework and found two that seem
nothing but dead :
o https://launchpad.net/~abogani/+ppa-packages
o https://launchpad.net/~linux-libre/+archive/ubuntu/rt-ppa
Otherwise, I guess I'll have to build it. Never done it. I've compiled
all sort of stuff, but never a kernel. Now what would be the easiest
way? By easy, in fact, I only mean scriptable. Ideally something like
* Get the latest kernel sources package with apt
* Fetch the corresponding patch (this is the hard part for me, I'm a
bit lost in versions)
* Apply the patch, build the kernel and install it
The idea being to be able to repeat the procedure when a new kernel is
out in the lifespan of my Ubuntu version, to stay up to date.
Any pointers? Thanks for your patience. Note that if I manage to get a
fairly repeatable procedure, I'll write a tutorial about it. Cordialement,
yPhil
--
Yassin Philip
http://yassinphilip.bitbucket.org
> Not sure what package I'm missing ... but I get:
>
> bob$ ./moloop
> "sni-qt/14917" WARN 16:11:18.077 void
StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
> Traceback (most recent call last):
> File "./moloop", line 7, in <module>
> mol.main()
> File "/home/bob/Downloads/mol/mol-master/mol/__init__.py", line 1379,
in main
> Looper(app)
> File "/home/bob/Downloads/mol/mol-master/mol/__init__.py", line 926, in
__init__
> self.show_settings()
> File "/home/bob/Downloads/mol/mol-master/mol/__init__.py", line 1264,
in show_settings
> dialog = SettingsDialog(self)
> File "/home/bob/Downloads/mol/mol-master/mol/__init__.py", line 423, in
__init__
> self.auto_connect_group.setId(radio, i)
> AttributeError: 'SettingsDialog' object has no attribute
'auto_connect_group'
>
> Probably a pyqt4 module.
I've seen a similar error in a previous software I released. Unfortunately
I'm away for a couple of days, so I can't check it, and it could still be
an error of mine.
I'll try to debug it as soon as I come back!
Maurizio
jack-matchmaker
---------------
jack-matchmaker is a small command line utility that listens to JACK
port registrations by clients and connects them when they match one of
the port pattern pairs given on the command line at startup.
jack-matchmaker never disconnects any ports.
The port name patterns are specified as pairs of positional arguments or
read from a file (see below) and are interpreted as Python regular
expressions, where the first pattern of a pair is matched against output
(readable) ports and the second pattern of a pair is matched against
input (writable) ports. Matching is done against the normal port names
as well as any aliases they have.
Example:
jack-matchmaker '.*:out_l' system:playback_1 \
'.*:out_r' system:playback_2
Port patterns can also be read from a file given with the
-p/--pattern-file option. The file is re-read when the HUP signal is
received.
Where to find it:
GitHub: https://github.com/SpotlightKid/jack-matchmaker
PyPI: https://pypi.python.org/pypi/jack-matchmaker
Requirements:
* A version of Python 3 with a ctypes module (i.e. PyPy 3 works too).
* JACK version 1 or 2.
* Linux, OS X (untested) or Windows (untested, no signal handling
Acknowledgements:
jack-matchmaker is written in Python and incorporates the jacklib module
taken from falkTX's Cadence application.
It was inspired by jack-autoconnect, which also auto-connects JACK
ports, but doesn't support port aliases. jack-autoconnect is also
written in C++, and therefore probably faster and less memory hungry.
The idea to read ports (patterns) from a file and re-read them on the
HUP signal was "inspired" by aj-snapshot.
Share & Enjoy,
Chris Arndt
jack-matchmaker
---------------
Version 0.4.0 is out hard on the heels of 0.3.0!
This now has the full feature set I wanted the program to have when I
started coding it, so I'll probably release a stable version 1.0 soon-ish.
If you have any suggestions for improvement or other comments, please
let me know!
Changes:
* Added -c command line option to list existing JACK port connections.
Where to find it:
GitHub: https://github.com/SpotlightKid/jack-matchmaker
PyPI: https://pypi.python.org/pypi/jack-matchmaker
Share & Enjoy,
Chris Arndt
Hi,
8 years later (last release is 2008) - does freewheeling today works
with the current Linux VST plugins ?
http://freewheeling.sourceforge.net/
Cheers.
Hello,
I just pushed another update on my latest little project.
It is a MIDI looper, but a bit different from other looping systems.
Usually you have a time basis (a MIDI clock) or you manually set when your
loop starts and stops. MOL works in a different way: it just "listens" to
what you play, and if you play it for 3 times, it will repeat it.
There is a configurable time threshold (default is 100 milliseconds), so
you have to be precise, but not too much. I'm thinking about adding a
velocity threshold too.
Apart from that, you don't need to do anything else: MOL will automatically
play and loop the pattern you repeated to the ports the original MIDI
devices is connected to, until you stop it.
That's it, the concept is almost that.
Since simple things are usually not so simple, I've added an extensive set
of configurable features and options.
By default, MOL will automatically connect to every ALSA MIDI hardware
ports (system sound card, USB MIDI devices) and will play the loop pattern
to every device to which that device is already connected to, but you can
also set it to connect to software ports only, every available (and new)
MIDI port, or a customizable port list (port names and client_id:port_id
are available, also using regular expressions), even with port blacklisting.
Other features:
- loops can be triggered according to event type (by default it uses NOTEON
events only)
- specific event types can be ignored at all, and will not be played
- a feedback port is provided (also with auto-connect features), which will
send custom events on status change
- MOL status (enable/disable/stop) can be controlled via MIDI (again, with
auto-connect)
- when a loop stops, it will try to stop *only* the notes in the loop that
are still playing
- further custom MIDI events can be sent on loop stop to the ports the
original source is connected to
I started this project just a week ago (after a long time of thinking about
it), so it probably has some bugs here and there.
Though, I think it's an interesting concept, and I'd like you to give it a
try.
MOL is written in Python 2.7, and requires PyQt4 and pyalsa.
You can find it here:
https://github.com/MaurizioB/mol
There's not a setup script yet, but, if you meet all the requirements
mentioned above you just need to run the main script as explained in the
repository description.
I'll be glad to have any kind of feedback, I hope some of you will like
this little program.
Cheers,
MaurizioB
> Date: Tue, 1 Nov 2016 13:59:59 +0100 (CET)
> From: "J. C." <julien(a)mail.upb.de>
> To: Linux-audio-users' mailinglist
> <linux-audio-user(a)lists.linuxaudio.org>
> Subject: [LAU] [OT] Looking for symphony with good counterpoint or
> independent voices
> Message-ID: <alpine.LNX.2.20.1611011351110.22573(a)britney.spears.net>
> Content-Type: text/plain; format=flowed; charset=US-ASCII
>
> Hey hey,
> sorry to ask this here, but I'm not very familiar with 19th century music,
> which is what I'm interested in. I know that this list harbours some
> connaisseurs of classical music. :)
>
> I'm looking for symphonies with good examples of independent voices or
> counterpunctual techniques. [...]
>
> So, if someone could suggest more works, or composers, which are famed for
> their strong, parallel voices, I'd be very grateful.
A master of counterpoint during the last years of 19th century was surely J.
Brahms.
I suggest listen to his 4 symphonies [1] and its beautiful vocal and chorals
works [2] (among them [3] [4] [5] which are simply wonderful imho).
Good listening!
A.
[1]
https://en.wikipedia.org/wiki/List_of_symphonies_by_Johannes_Brahms
[2]
https://en.wikipedia.org/wiki/List_of_compositions_by_Johannes_Brahms_by_ge…
[3]
https://en.wikipedia.org/wiki/A_German_Requiem_%28Brahms%29
[4]
https://en.wikipedia.org/wiki/Schicksalslied
[5]
https://en.wikipedia.org/wiki/N%C3%A4nie
--
al3xu5 / dotcommon
Say NO to copyright, patents, trademarks and any industrial design restrictions.
Guys, I'm really excited, I want to share this with you : I managed to
solve the biggest ergonomics gripe that I had with Qtractor
<http://www.rncbc.org/drupal/comment/7175#comment-7175>, and given the
fact that I live in it, you can imagine my trepidation :p
You see the mixer is a /floating/ window. And while that's fine for a
lot of people in a lot of use cases, for me, most of the time, it's not.
I don't like floating windows, for many reasons, and to avoid the
questioning of my very membership of the troubadour's guild, let's skip
to the first : Just because ; Please don't waste our time, go play with
your own windows and float them to your heart's content :/
I basically need to see my mixer at all times. Well no, not at all
times, in fact most of the time I'm in the timeline, full screen ; But
when I want to see it, I definitely want to see my timeline /as well/,
all of it. Very rarely/never do I need to see /just the mixer, full screen/.
Note that I had this issue with basically /every/ horizontal
timeline-based DAW that I used (Ableton live - up until 7, after that I
don't know - comes to mind) the only viable alternative being the Ardour
way, where the selected track/bus can be embedded on the side. I love that.
Add to that the fact that a lot of WMs don't always honor the position
directives of said floating windows, like typically, in both Unity and
i3 "default", when one toggles the mixer's display with either the mixer
button or the F9 shortcut, it springs back in the dead center of the
screen, no matter where you painstakingly positioned it before. I don't
know about you, but grabbing my mouse to constantly resize a window /the
same way every time/ simply ruins my joie de vivre. Oh, I'm sure in Kwin
it's pixel perfect ;) back to our overlapping problem : I want to see my
mixer, but I also want to see ALL my tracks by scrolling
vertically/zooming in the timeline. I also, when I open a plugin GUI, or
more than one for that matter, dont want it/them to get in the way.
And finally, according to recent studies floating windows are bad for
the ozone layer. If you ask me for an interview, that's what I'll say :)
Enter i3 <https://i3wm.org/>. This "tiling" WM is quite popular, it's
light, configurable, and very well documented. I cannot emphasize
"light" enough : Try it on this old laptop that struggles more at each
Debian iteration. The idea is that no window overlap/float, except for,
well, floating windows. Obvious ones, file copy dialogs, that sort of
things. And Qtractor's Mixer is, by default, in this category, so I
struggled a bit to get to what I want, but I finally did it (and missed
a heartbeat) look:
https://youtu.be/TeYHkjlHtTghttps://youtu.be/sTKr_G2AnKQ
It's a directive in i3 config file, that targets this specific window
based on its class and name, discovered using the xprop command. That
means that under this regime, it will *never* float again.
for_window [class="Qtractor" instance="Mixer - Qtractor"] floating disable
One can go further and specify precise sizes, positions and layouts, and
put them in the config file, and switch to them on-the-fly. Oh, and of
course everything can be resized/re-positioned with the keyboard. i3, by
default, uses the super (win logo) key in a very elegant, mnemonically
and unobtrusive way. Fantastic, told ya.
Now let me tell you, the real fun begins. No window overlap, no more
"always on top" hacks, or putting down the guitar pick to fiddle with
the (*$-@+°#¤!) mouse ; Everything respond at the touch of a key, this
is per-fick :) cheers everybody. Programmers, musicians, carpenters and
motocyclists, lovers, friends, acquaintances, etc. and /of course/ (duh)
every combination of it :)
yPhil
--
Yassin "xaccrocheur" Philip
http://yassinphilip.bitbucket.org