hi dominic!
first of all, thanks for sharing your tools - klick has saved the day by
adding a much-needed jack-transport aware metronome to a sooperlooper setup.
now i'm a lazy bastard and want to use gtklick, but even though it
compiles and installs fine, it barfs when i start is, like so:
nettings@kleineronkel:/usr/lib/python2.7/site-packages/gtklick> gtklick
Traceback (most recent call last):
File "/usr/bin/gtklick", line 14, in <module>
from gtklick.gtklick import GTKlick
File "/usr/lib/python2.7/site-packages/gtklick/gtklick.py", line 30,
in <module>
import klick_backend
File "/usr/lib/python2.7/site-packages/gtklick/klick_backend.py",
line 12, in <module>
import liblo
ImportError: /usr/lib64/python2.7/site-packages/liblo.so: undefined
symbol: lo_address_new_with_proto
i have tried both liblo-0.26 and current liblo svn, no luck.
now the python paths in this openSUSE tumbleweed install are a horrible
mess, with three different python versions and libs in /usr/lib,
/usr/lib64, and /usr/local/lib64. but they all seem to be found, and i
made sure that the liblo.so mentioned in the error message is actually
the one from your pyliblo package (by copying it manually). i removed
the build directory of pyliblo for each try, and also recreated liblo.c
via cython.
how do i proceed to fix this?
best,
jörn
--
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487
Meister für Veranstaltungstechnik (Bühne/Studio)
Tonmeister (VDT)
http://stackingdwarves.net
Is there any way to completely switch off the vertical measure/beat
lines in Ardour3's edit window ? Changing the colors to hide them
won't do because they are on more than one background.
If not, I'd suggest to not draw them when the corresponding
bars on top are disabled.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
Dear Developers,
I've written a convenience interface to implement Non Session Management as fast and easy as possible in Python 3 applications. It is no magic programming at all, but it makes things just that tiny bit easier that is required to actually implement something, and not only plan it.
The real work is to follow the rules of a managed system (see http://non.tuxfamily.org/nsm/API.html ). So implementing the technical side should be a no-brainer to let you focus on the actual task.
pynsmclient is open source under the GPL3 or later and can be found on my github page so you can start using it right away.
https://github.com/nilsgey/pynsmclient
I also have written a short article in my blog about that topic http://nilsgey.de/?id=24
Greetings,
Nils
Hi,
after a somewhat productive weekend I'm happy to announce some alpha
quality software (i.e. bug ridden, not feature complete) for your
consideration and feedback :)
But: release early, release often XD
I went a little overboard with modularization and separation of
concerns, so in the end it became four packages (with possibly one more
in the future - a LV2 plugin to load the synths/instruments).
Documentation is also very much lacking, but each package contains at
lease a single example file to illustrate the usage.
* ladspa.m - https://github.com/fps/ladspa.m
ladspa.m is a header only c++ library to build and run general synthesis
graphs made up out of LADSPA plugins. The interface is kept deliberately
kept simple and unsafe, as it is expected that one uses higher level
tools to build these synthesis graphs (e.g. using a library on top op
ladspa.m.swig or ladspa.m.proto).
* ladspa.m.swig - https://github.com/fps/ladspa.m.swig
ladspa.m.swig are SWIG generated python bindings for ladspa.m. This
allows building and running general synthesis graphs made up of LADSPA
plugins from within python. This requires ladspa.m. NOTE: I just saw
that the swig interface definition lacks the ability to connect outside
buffers onto plugin ports. This will be fixed in the next few days..
* ladspa.m.proto - https://github.com/fps/ladspa.m.proto
ladspa.m.proto contains google protobuf definitions for general
synthesis graphs made up of LADSPA plugins. It also contains a
definition for an instrument file format. This library does not depend
on either of the two above. It becomes useful with the last package
(ladspa.m.jack) and possibly in the future with an LV2 plugin to load
and run these (to be announced when done). The python bindings generated
for ladspa.m.proto can be used to generate synth and instrument files
that can be loaded by ladspa.m.jack. The instrument file definition
allows for polyphony while at the same time putting no constraints on
the inner structure of the instrument (each voice is made up out of
plugins, they can be identical or not between all voices)..
An example is included which defines a simple sawtooth instrument with
exponential envelopes and with 5 identical voices except for a different
delay setting on each voice.
https://github.com/fps/ladspa.m.proto/blob/master/example_instrument.py
Pipe its output into a file called e.g. instrument.pb. This you can then
load into ladspa.m.jack.instrument.
Here's a little example of the generated instrument file loaded into
ladspa.m.jack.instrument and playing a little 120bpm loop (from ardour3)
with it:
https://soundcloud.com/fps-2/t-m
This also highlights the need for a higher level interface on top of it
to ease the process..
* ladspa.m.jack - https://github.com/fps/ladspa.m.jack
ladspa.m.jack is a library which allows loading ladspa.m.proto synth and
instrument definition files into jack hosts that are provided as example
clients.
ladspa.m.jack.synth allows loading a synth definition file and run it in
the jack graph.
ladspa.m.jack.instrument allows loading an instrument definition file
and provides a midi in port which allows playing the synth.
But like I said this is all ALPHA software and I just announce it
because someone else might have fun with it. Please report all issues
that you find either per email to me, on LAD or LAU or on the issue
trackers of the github projects..
Have fun,
Flo
--
Florian Paul Schmidt
http://fps.io
Last time i tried to make a roll with G-Town Church Bassdrum, but it
appears ugly. Did not try to humanize timing, but expecting it much
better with interpolation. May be, it is some hidden feature, which is
not used in most freeware gig and sfz banks?
I've been working with large lscp files, over a hundred .idfs for muse 2,
etc, for sometime now, and i'm pretty well knackered from manually creating
large monolithic instrument config files of some sort or another, for the
same sample library set, across apps.
I propose the following, and i'm wiling to put some money in someone's
pocket for this:
A simple app (CLI is ok but GUI based preferred) that:
1) automatically converts lscp files containing single or multiple midi
instrument maps into individual midnam files.
2) automatically converts muse2 .idf files into midnam files.
3) converts midnam files into muse2 .idf files
Obviously needs to work properly, and create correct ( auto app checked)
midnam and .idf files.
App needs to be opensource (obviously), and public, for those other poor
souls who have to struggle with large instrument files, particularly those
using large sample libs with copious articulations per instrument, and for
whom automation of these excruciating data processing tasks would save
massive amounts of time and effort.
Thanks, and if you're interested, contact me privately,
Alex Stone.
Hi all,
Time for another update for general consumption, minor changes done but
quite a few of them!
Nearly arbitrary list of changes from the changelog:
- Allow reading old drummaps for new style drumtracks
- Added metronome icon in main window
- Fixed moving events with keyboard in Drum editor
- Added theme support, Light, Dark and Ardour so far
- Added missing line draw shortcut (F) to drum editor.
- Added new french translation from Yann Collette
- Added: Pan and Zoom tools to editors. P + Z shortcuts. Added a Settings
item for alternate behaviour.
- Fixed: Pianoroll and Drum Editor 'Snap' boxes not remembering 1st or 3rd
columns.
- Fixed: Arranger 'Snap' was not stored or remembered.
- Fixed: Accelerator buttons shift/ctrl/alt for moving/copying/cloning /
restricting movement.
- Fixed: Shift key restricting movement: Ignore snap setting now.
- Fixed: Resize shift key ignore snap setting now.
- Fixed: Draw new item shift key ignore snap setting now.
- Fixed: Shift key was not snapping to vertical.
- Fixed: ALL 'Speaker' related playing of notes. Works with new notes,
moving notes, piano press etc.
- Fixed: ALL 'Speaker' related notes now send true note-offs instead of
zero-velocity note-ons.
- Fixed: Drum 'Cursor' mode was playing double notes.
- Fixed: New Drums 'Cursor' mode and instrument up/down movement was
broken, jumping all over the place.
- Added prebuilt PDF of manual (work in progress)
- Improved: Shortcut listings: Added Wave/Score categories. Re-categorized
several keys. Updated README.shortcuts
- Improved: Right-click menus expanded. Now also shows 'Tools' menu when
clicked on parts.
- Added choice of new metronome with different sounds and adjustable volume.
- Fixed gain adjustment with 'Other' choice in wave editor, it was reversed
For more information and additional changes see the full changelog:
http://lmuse.svn.sourceforge.net/viewvc/lmuse/trunk/muse2/ChangeLog?revisio…
Find the download at:
https://sourceforge.net/projects/lmuse/files/
MusE on!
The MusE Team