Am 03.04.2015 um 19:59 schrieb Fons Adriaensen:
On Fri, Apr 03, 2015 at 03:05:56AM +, Joël Krähemann wrote:
I don't want to do JACK, since it is believed to be somehow the Qt thing.
Where do you get that sort of nonsense ?
Fons, like ever, polite and friendly in his posts. :-)
Maybe
On Fri, Apr 03, 2015 at 03:05:56AM +, Joël Krähemann wrote:
I don't want to do JACK, since it is believed to be somehow the Qt thing.
Where do you get that sort of nonsense ?
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on
On Fri, 3 Apr 2015, Hermann Meyer wrote:
Am 03.04.2015 um 19:59 schrieb Fons Adriaensen:
On Fri, Apr 03, 2015 at 03:05:56AM +, Joël Krähemann wrote:
I don't want to do JACK, since it is believed to be somehow the Qt thing.
Where do you get that sort of nonsense ?
Fons, like ever,
On Fri, Apr 03, 2015 at 08:13:15PM +0200, Hermann Meyer wrote:
Am 03.04.2015 um 19:59 schrieb Fons Adriaensen:
On Fri, Apr 03, 2015 at 03:05:56AM +, Joël Krähemann wrote:
I don't want to do JACK, since it is believed to be somehow the Qt thing.
Where do you get that sort of nonsense ?
On Fri, 3 Apr 2015 20:16:37 +0100
Gordonjcp gordon...@gjcp.net wrote:
On Fri, Apr 03, 2015 at 11:46:17AM -0700, Len Ovens wrote:
The only downside is longer sysex events. I think there is work
underway to deal with this as well, but of course a long sysex no
longer would have sample
On Fri, 3 Apr 2015 15:37:27 -0400
Paul Davis p...@linuxaudiosystems.com wrote:
On Fri, Apr 3, 2015 at 3:35 PM, Will Godfrey willgodf...@musically.me.uk
wrote:
From the hardware viewpoint SysEx events can be effectively infinite. The
header contains the number of bytes in the block, so
On Fri, Apr 3, 2015 at 9:16 PM, Gordonjcp gordon...@gjcp.net wrote:
I can't help but think that if you're doing something that requires
sample-accurate sysex messages, you're doing something a bit strange and
wrong :-D
There are some cases where this actually makes sense, such as MTS tuning
On Fri, Apr 03, 2015 at 11:46:17AM -0700, Len Ovens wrote:
The only downside is longer sysex events. I think there is work
underway to deal with this as well, but of course a long sysex no
longer would have sample acurate timing (maybe the first part will
be time stamped) or at least would
On Fri, Apr 3, 2015 at 3:35 PM, Will Godfrey willgodf...@musically.me.uk
wrote:
From the hardware viewpoint SysEx events can be effectively infinite. The
header contains the number of bytes in the block, so the number
representation
limits the block size,
not true. sysex messages do not
On Fri, 3 Apr 2015, Gordonjcp wrote:
I can't help but think that if you're doing something that requires
sample-accurate sysex messages, you're doing something a bit strange and
wrong :-D
Even RPN/NRPNs start to wander from sample accurate Both are
effectively single events that are
Hi all, me just migrated gsequencer to GitHub.
http://www.gsequencer.org
Further me did renamed binary from `ags` to `gsequencer`. About the
state of the sequencer: Version 0.4.2-44 is believed to be stable.
Since me don't have the time to test it well, me need people to test
it. Please, let me
11 matches
Mail list logo
