Hi all,
Here comes a new release of NASPRO, 0.5.0 this time. No new features,
just bugfixes and "regular" updates.
The components being updated are:
* NASPRO core: untested fix for semaphores on Mac OS X, build system fixes;
* NASPRO bridge it: build system fixes;
* NASPRO bridges: dynamic manifest URIs changed, updated
LRDF-equivalent data matching newest CAPS releases, build system
fixes;
* LV2proc: fixed bogus warning w.r.t. lv2:sampleRate ports, updated
manpage, build system fixes.
ino, gino and FreeADSP have been undergoing experimentation in the
last months and their future is uncertain at this point.
Enjoy!
Stefano
Info and download is here:
http://lvtoolkit.org/releases/lvtk-v1-0-4
* Fixed Synth bug where handle_midi wasn’t being called if overridden
* Compatibility with older and newer boost versions
* Added support for LV2UI_Resize
Hello,
I'm trying to poll mixer events in Alsa using C. I've used the following
functions within an infinite while loop:
if (snd_hctl_wait(hctl,-1))
{
...
}
###### and
snd_hctl_poll_descriptors(hctl, poll_fds, 1);
err = poll (poll_fds, 1, -1);
if (poll_fds[0].revents & POLLIN)
{
...
}
While I can get the first mixer event fine, in all subsequent rounds,
both snd_hctl_wait and poll always return immediately.
With the snd_mixer functions one has to call snd_mixer_handle_events to
clear events. However, calling snd_hctl_handle_events here never returns
and I can't quite figure out why. Nonetheless, I'm not even sure that's
the key to my solution.
Can anyone give me some advice on how to get this working?
Kind regards, Maarten
Hi Tim,
Great update. Superb sound, and very tweakable!
Thanks for making this!
I have a similar problem as the one reported earlier:
In AmpVST, all amp-models sound the same to me except the BassMan.
Also: they all have a lot more gain/distortion then the BassMan.
This is with v 0.9.7.
If you want I can provide a small Ardour session to demonstrate the
problem.
All the best,
Bart.
I'm proud to announce the release of guitarix2-0.25.2
Guitarix is a mono tube amplifier simulation for jack, with additional
mono/stereo effect racks which can be filled with some in-build effects
as well as with external LADSPA plugins.
Download from http://sourceforge.net/projects/guitarix/
new in this release:
* add ts9 tube screamer simulation to lv2.plugs
* add dunlop wah / autowah simulation to lv2.plugs
* add booster /treble/low to lv2.plugs
* add factory settings file contributed by kokoko3k
* add patch by Brendan Jones to set (libgxw)library install path
* fix lv2 build on non ix86 arch (only use sse2 when supported by
build host)
* switch to use fixed block-size in zita-convolver for all lv2 amps
(hopefully fixed bug 5252 reported by prokoudine on tracker.ardour)
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
> ----- Original Message -----
> From: Johannes Kroll
>
> On Thu, 17 Jan 2013 12:10:20 +0100
> Johannes Kroll <jkroll(a)lavabit.com> wrote:
>
> > But I'm pretty sure that syncing Phasex to an external MIDI clock
> > worked before, now it doesn't. I'm sending MIDI Clock from Renoise to
> > Phasex. I checked that the ports are connected and the clock is sent
> > with qjackctl & aseqdump. Is it possible that some change between 0.96
> > and 0.97 created a problem with the MIDI Clock?
>
> By "problem" I mean that I remember the BPM value being updated by the
> MIDI Clock, now it isn't.
> I don't know if it's related, but the "Lock parameter (manual
> adjustment only)" checkbox in the "Map MIDI Controller" window of the
> BPM Pot is always checked after phasex startup. I tried turning it off,
> then saving a session. After reloading the session, the "Lock
> parameter" field has always the same value as before, it's apparently
> not affected by session loading. But it is affected by "Load MIDI map".
>
> Turning "Lock parameter" off however doesn't cause the BPM to be
> changed by the MIDI clock, so now I think I might have imagined it was
> doing that in 0.14.96... :-]
(I should have read this before responding to the first email...)
I just found a new issue with the BPM locking with v0.14.97, so I'm not
surprised at all if updating BPM from tempo sync got broken as well.
Getting this fixed will be a priority for v0.14.98.
Cheers,
--ww
> ----- Original Message -----
> From: Johannes Kroll
> On Thu, 10 Jan 2013 22:26:15 -0500
> "William Weston" <whw(a)linuxmail.org> wrote:
>
> > > ----- Original Message -----
> > > From: Johannes Kroll
> > >
> > > I played around with it, it's fun! GUI looks very cool, too.
> > >
> > > After using it a few times, I noticed that some folders with strange
> > > names had been created with files like patchbank, phasex.cfg,
> > > phasex.map, sessionbank in them. The folder names contain weird
> > > characters, Thunar file manager displays them as 'invalid encoding'.
> > > One such folder showed up in my downloads folder, the other one in a
> > > src directory I was working in, possibly the PWDs when I started
> > > phasex... Has anybody else seen this behaviour?
> > >
> > > I'm running Ubuntu 12.04 on x86-64.
> >
> > These files and directories are created when a session is saved via
> > LASH, JACK Session, or native session management. Â I've seen this
> > behavior once before, when first working on LASH support, and it
> > turned out to be a character encoding problem with LASH supplied
> > directory names. Â The only thing I can think of here is to use the
> > "C" locale instead of obtaining locale from the user's environment,
> > so I've made this change in v0.14.97-dev. Â Could you try the latest
> > in git, and let me know how it goes?
>
> I'm not using LASH, but I did save sessions in Phasex "natively". I
> tried the latest git and I don't see the strange directories in the
> working directory where I started Phasex. I don't know if they popped
> up somewhere else, but I think they were in the WD, so I guess that
> fixed it!
Great!
> But I'm pretty sure that syncing Phasex to an external MIDI clock
> worked before, now it doesn't. I'm sending MIDI Clock from Renoise to
> Phasex. I checked that the ports are connected and the clock is sent
> with qjackctl & aseqdump. Is it possible that some change between 0.96
> and 0.97 created a problem with the MIDI Clock?
Are there any specific sync/timing issues that you're trying to solve
by sending MIDI Clock messages?
MIDI Clock messages are currently ignored. Â The original MIDI enabled
version of phasex had this, but it ended up adding too much jitter to
the LFO frequencies and caused more problems than it solved. Â The
internal MIDI clock in phasex is used for timestamping incoming events
and assigning frame position. Â (Future plans include a more robust
tempo clock that can be used with MIDI Clock, MTC, MIDI triggers, tap
tempo, JACK Transport, etc.)
For now, the best options for keeping in sync with tempo changes are
JACK Transport Tempo sync or automating the BPM parameter. Â Not ideal,
I know... but this is better than nothing and should hold up until I
can get the tempo clock designed.
Cheers,
--ww
