> ----- Original Message -----
> From: Jörn Nettingsmeier
>
> On 12/30/2012 05:42 AM, William Weston wrote:
> > Happy New Year!
> >
> > Yes, your eyes are working correctly. This is v0.14.96. Some things
> > are worth the wait. I know it's been a while, but I haven't forgotton
> > about PHASEX...
>
> whoohooo!
>
>
> just a quick feedback: distros that are moving to a unified /usr/bin
> will need this patch:
>
> diff --git a/configure.ac b/configure.ac
> index 5fb0368..3b2496c 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -334,7 +334,8 @@ AC_DEFINE_UNQUOTED(PHASEX_GCC_MINOR, [$gccminor],
> [Built with gcc minor version]
> Â CPU_POWER_LEVEL=2
> Â ARCH_OPT_CFLAGS=""
> Â ARCH_MATH_CFLAGS=""
> -ARCH_BITS=`( file /bin/true | grep 'ELF 64-bit' > /dev/null && echo 64
> ) || echo 32`
> +ARCH_TRUE=`which true`
> +ARCH_BITS=`( file $ARCH_TRUE | grep 'ELF 64-bit' > /dev/null && echo 64
> ) || echo 32`
>
> because `file /bin/true` will return "/bin/true: symbolic link to
> `/usr/bin/true'", which in turn will force the bitness to 32, which then
> fails unless a full 32-bit environment is installed.
Thank you. Â This is now in the dev tree.
> now i'm hunting a couple errors wrt jack headers - my guess is that
> PHASEX is being tested with JACK2 exclusively - it seems to rely on a
> couple of types and methods which don't seem to be present in my jack1
> environment (more or less fresh from svn).
You're absolutely right. Â I actually haven't tested with jack1 since
adding JACK Session support. Â I'll have to check and see what else is
jack2 only. Â Restoring jack1 support will be top priority for v0.14.97.
Thanks again,
--ww
> ----- Original Message -----
> From: Robin Gareus
>
> It compiles cleanly and works just fine on debian.
>
> There's single compiler warning, nothing major, really:
>
> midi_event.c: In function ‘queue_midi_event’:
> midi_event.c:140:47: warning: pointer targets in passing argument 1 of
> ‘g_atomic_int_compare_and_exchange’ differ in signedness [-Wpointer-sign]
> /usr/include/glib-2.0/glib/gatomic.h:45:10: note: expected ‘volatile
> gint *’ but argument is of type ‘volatile unsigned int *’
Good to hear. Â Congratulations on the first debian build of 0.14.x!
A single warning is as good as one can hope for on the first build on
another distro. Â This particular warning is a nothing to worry about.
In this case, an identical binary is produced after applying the fix
(which is now in the dev tree).
> [..]
>
> > So what do we do, now that the world didn't end?
> > Let's make some music!
>
> I suggest to announce this on linux-audio-announce, too.
>
> keep up the good work,
> robin
I just wanted to make sure that it doesn't blow up on distros outside
the RedHat/Fedora/CentOS world first. Â Moving from Fedora 17 to Fedora 18
actually posed a bigger challenge than expected: Â A 16 hour debugging
session to find that a segfault a few function calls deep inside
jack_client_open() was being caused by the global variable 'int shutdown'
overshadowing the system call shutdown() in the linker's symbol table.
I'm glad to see that everything builds properly on debian.
Cheers,
--ww
Hey guys!
I am trying out Highlife LV2, got it from here:
http://distrho.sourceforge.net/ports.php
In my case it does not display in Carla (external GUI looks like a small
box). Displays fine as a standalone and as LV2 in Qtractor, but when I
click Import File - nothing happens.
Problem is that I am still on Ubuntu 10.04 and desperately don't want to
upgrade since most things I need work and I enjoy this version very much.
Is there anything I can do to make Highlife work?
--
Louigi Verona
http://www.louigiverona.ru/
We are proud to announce the release of guitarix2-0.25.0
Guitarix is a mono tube amplifier simulation for jack, with additional
mono/stereo effect racks witch can be filled with some in-build effects
as well as with external LADSPA plugins.
Download from http://sourceforge.net/projects/guitarix/
This release introduce the first LV2 plugs created from the guitarix
amps. Well, they will perfectly fit into hotel sierra
* GxAmplifier tube 12ax7 tonestack sovtek cabinet 4x12
* GxAmplifier-II tube 12AT7 tonestack soldano cabinet AC30
* GxAmplifier-III tube 6C16 tonestack bassman cabinet 1x15
* GxAmplifier-IV tube 6V6 tonestack soldano cabinet mesa
* GxAmplifier-V tube 6DJ8 tonestack ampeg cabinet HighGain
there are mono and stereo versions of those amps included in the bundle.
Thanks goes to Richard Dalton from http://www.Ampskindesigns.com
for given me permission to use (and distribute) his work within a GNU
GPL project,
many thanks Richard.
thanks goes as well to David Robillard for his great work on the LV2
specs and to Rui Nuno Capela for implement them so excellent in qtractor.
Please check it out and give feedback if you
find a problem.
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
download site:
http://sourceforge.net/projects/guitarix/
have fun
guitarix development team
On Monday 24 December 2012 05:52:41 Pedro Lopez-Cabanillas wrote:
> I think that you are not getting more help here because a terminology
> confusion. This is only a guess, but I think that by "jack connections" you
> mean the lines that can be created in the "ALSA" tab of qjackctl. In that
> case, you are using the wrong name because those lines have nothing to do
> with jack. They are ALSA sequencer connections that can be made using
> other programs as well, like "aconnect". There is an ALSA API to create
> connections; look for "subscription" here:
> http://www.alsa-project.org/alsa-doc/alsa-lib/seq.html
>
> If you want to use jack midi instead, please clarify (and don't expect
> answers or interest from me.)
Well, that explains why there's a separate ALSA tab in QJackCtl. And, yes, I'm
using the ALSA tab to make my connections. So, at this point, it seems I don't
really need jack.
Just a side question: if I had an application that uses audio and midi (like
Sonar), who keeps them in sync? Is this ALSA or Jack?
> > The first thing I don't understand is in scheduleEvents() why passing
> > absolute times to the queue doesn't work.
>
> Probably because when you execute snd_seq_start_queue(), the queue's clock
> starts rolling, and the queue won't play events having timestamps in the
> past, only in the future. If your MIDI events have very low timestamps,
> you can try adding the current queue's time at scheduleEvents(). But in
> this case, using relative times is much easier.
>
> > And once I have absolute times,
> > how do I do the play/pause in the transport loop in main().
>
> You already know the queue control functions: snd_seq_start_queue(),
> snd_seq_stop_queue() and snd_seq_continue_queue().
So the queue has its own clock? Can I create the queue, push events to it,
then start it? And if I then stop the queue and later continue, will it
process the rest of the events from where it left off when it was stopped?
> Assuming that you want to use the ALSA Sequencer, and not jack midi, I can
> provide some working examples.
>
> As per your request, a simple metronome program in C
> http://lalists.stanford.edu/lau/2009/08/att-0005/ametro.c
>
> You can check as well the examples in my drumstick library (Qt4, C++)
> http://drumstick.sourceforge.net/docs/metronome.cpp-example.html
Perfect. And you pre-answered my next question. Is there a C++ wrapper for
ALSA? And uses Qt too! Nice. Thanks.
--
7:8
Hello all,
I'm seeing a strange problem with the WFS system at the Casa del
Suono.
It consists of a number of Jack apps managed by a python program
which in turn takes its input from 'player' like remote control
apps running on two EEEs used by the musem staff.
Some of the port connections are fixed, some are made or unmade
by the python program according to the item chosen on the player
interface.
Twice now, after a few weeks of 'uptime', some of the fixed
connections have disappeared. Everything else remains normal,
the whole system still functions (apart from some missing audio
signals) and restoring the connections manually is all that
is required. No errors or whatever in any of the log files.
The connections that are lost are always between the same two
apps, both of which only have fixed connections. In other words
there is nothing in the python control program that ever touches
any ports of those two apps.
So I'm wondering what's happening here. Anyone else running
jack1 uninterrupted for months noticed anything strange ?
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)
Greetings,
Yeah. Not much to tell about the times I'm afraid. But let me wish you
all a merry and great new year, following the one which end is nigh.
Just in case you wanna party, feel welcome, by all means:
Qtractor 0.5.7 (hotel sierra) is open, come on in!
Release highlights:
* LV2 Options and Buf-size support (NEW)
* Location markers/bar (NEW)
* MIDI editor line-drawing (NEW)
* Punch & loop recording compatibility (FIX)
* Untangled LV2 UI parameter communication (FIX)
* Dropped libSLV2 support, honoring libLILV for good (FIX)
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
- source tarball:
http://downloads.sourceforge.net/qtractor/qtractor-0.5.7.tar.gz
- source package (openSUSE 12.2):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.7-4.rncbc.suse122.sr…
- binary packages (openSUSE 12.2):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.7-4.rncbc.suse122.i5…http://downloads.sourceforge.net/qtractor/qtractor-0.5.7-4.rncbc.suse122.x8…
- quick start guide & user manual:
http://downloads.sourceforge.net/qtractor/qtractor-0.5.x-user-manual.pdf
Weblog (upstream support):
http://www.rncbc.org
License:
Qtractor is free, open-source software, distributed under the terms
of the GNU General Public License (GPL) version 2 or later.
Change-log:
- Loop and punch in/out ranges may now get set simultaneously, may even
overlap each other. However, punch in/out range recording will always
prevail over any loop recording takes.
- LV2 Worker/Schedule now supporting multi-instance vs. single-UI scenarios.
- LV2 Options and Buf-size extension support added.
- Fixed an off-by-one-tick bug on MIDI file input which was leaving
spurious zero-length runt notes at the end of a MIDI clip, if a note-on
coincides with the ending/split point (on ticket issued by Jonathan H.
Pickard, thanks).
- Good old SLV2 library support for LV2 plug-ins (libslv2) is now
irrevocably deprecated, or better said, completely wiped-out from the
LV2 host code, now considered extinct.
- LV2 UI parameter updates are now asynchronously detached from the
source GUI widget thread, in attempt to improve cross-GUI-toolkit
responsiveness, specially focused on LV2 plugins with a GTK based UI
(eg. amsynth, triceratops, etc.).
- Make sure LV2 UI parameters (input control ports) get updated when
loading a genuine LV2 state preset.
- Improved the (custom) tempo spin-box widget signal(ing) processing and
dispatching.
- Show proper pointing cursor and location tool-tip while dragging any
of the time ruler markers (including latest location markers/bar).
- On saving as an archive/zip session file (suffix .qtz) include only
those files that are actually referenced by live clips arrangement.
- Ongoing integration of location markers infrastructure (time-scale and
MIDI-file support).
- Free-hand/linear retouching of event values, while on the MIDI clip
editor's view pane below the main piano-roll (eg. note velocities), is
now possible provided the target events are selected, otherwise the
usual painting edit sub-mode applies (cf. menu Edit/Select Mode/Edit Draw).
- The MIDI clip editor now senses which target view pane has focus for
general selection commands (cf. Edit/Select/None, All, Invert, Range)
whether the main piano-roll or the event value (velocities) view.
- Mouse middle-button clicking is back in business on main track-view
and on MIDI clip editor views (piano-roll) as an immediate play-head
(re)positioning command or merge/reset the edit-head/tail cursors if
Shift/Ctrl keyboard modifiers are pressed.
- Formerly protected, class qtractorClip::FadeFunctor is now public in
an shot-in-the-dark attempt to fix clang builds (as reported by Jekyll
Wu, thanks).
- Override all sub-classed widgets mouse-pointer event handlers to be
isolated from base widget style and/or window management.
Enjoy!--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
I'm using Qt and C++ under Linux with ALSA. Ideally, what I'd like is a simple
example like alsa's midiseq.c or a MIDI metronome hooked up to jack so that it
outputs to fluidsynth. Then I could see the whole system in action. Is there
such an example available? I'm having some trouble understanding how all the
pieces fit together.
I have a few other questions that aren't directly related:
The first has to do with manipulating midi ctlr events to simulate various
musical techniques like legato and palm muting. What I've tried so far doesn't
sound very good. I need legato in polyphonic mode, so just overlapping notes
doesn't work. Sending a legato ctlr message doesn't seem to do anything. I'm
not looking for anything real fancy, just something to make trills & slurs
sound reasonable. I think all I want to do is to skip the attack portion of
the sample. For palm muting, I've shortened the note duration, but I'd like to
darken or thicken the timbre. Is there any simple way to do this?
Second, I've lifted a lot of glyphs from the Lilypond font and placed them in
my own font and I was wondering how and where to credit creators of these
glyphs. I've added glyphs of my own (bends, vibrato, etc.) and doctored some
others, but many are just cut, pasted, & resized from Lilypond. Before I
release any code, I'd like to get the credits properly documented.
Thanks, all.
--
7:8
Am 23.12.2012 03:29, schrieb David Robillard:
> Suil 0.6.6 is out. Suil is a lightweight C library for loading and
> wrapping LV2 plugin UIs. Suil transparently presents UIs written in
> any toolkit as the desired widget type of host programs, so hosts do
> not have to depend on foreign toolkits.
>
> This minor release fixes a couple of potential crashes.
>
> Suil home: http://drobilla.net/software/suil/
> Download: http://download.drobilla.net/suil-0.6.6.tar.bz2
>
> Changes:
> * Fix crash in x11_in_gtk2 when event_filter fires before widget
> is realized
> * Use libgtk-x11-2.0.so.0 (with .0 suffix) by default which is
> available on systems without the dev package
> * Update to waf 1.7.8 and autowaf r90 (install docs to versioned
> directory)
>
> Also, a note about the previous release: the Gtk in Qt fixes are thanks
> to Devin Anderson; apologies for this attribution oversight in the hasty
> release and corresponding announcement.
>
> Enjoy,
>
> -dr
>
Thanks for your work on this, suil makes the live for a
plug-in-developer a bit more easy, and gives the chance to keep the
knowing toolkit for create a plug-in UI.
I just wonder a bit, you announce Suil 0.6.8, gives the download link
for Suil 0.6.6, and when I have a look at your project page I found Suil
0.6.10 :-)
regards
hermann
Hello LAD,
LVTK v1.0.3 is out. For those who aren't already aware, LVTK is the
successor to lv2-c++-tools.
Info and source download:
http://lvtoolkit.org/releases/lvtk-v1-0-3
Important Fixes:
- Fixed UI compiler errors with -Wl,nodelete.
- Accurate MIDI triggering in the Synth base class
- Fixed GtkUI mixin bug that was causing crashes when a plugin is
unloaded while UI is still open.
A complete list of changes is in the Git history.