11 Jan
2013
11 Jan
'13
4:26 a.m.
----- 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?
Thanks,
--ww
17 Jan
17 Jan
12:10 p.m.
New subject: Announcing PHASEX-0.14.96
On Thu, 10 Jan 2013 22:26:15 -0500
"William Weston" <whw(a)linuxmail.org> wrote:
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!
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?
----- 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?
12:36 p.m.
New subject: Announcing PHASEX-0.14.96
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... :-]
6:16 p.m.
New subject: Announcing PHASEX-0.14.96
On Thu, 17 Jan 2013 12:10:20 +0100
Johannes Kroll <jkroll(a)lavabit.com> wrote:
Sorry, I was wrong about that... I played some more with Phasex and I
found another badly encoded directory in the working directory...
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!
4357
days inactive
4363
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
2 participants
participants (2)
-
Johannes Kroll -
William Weston