William Light:
> it's interesting to me that free (source and/or beer) music software
> on
> OSX and windows has come further than it has on Linux. off the top of
> my head:
>
> http://psycle.pastnotecut.org/portal.php
> http://www.buzzmachines.com/
I'm very interested in knowing what you're missing from Psycle and
Buzzmachines
that Radium doesn't have...
Oops, mistakenly replied direct instead of to list. Forwarding.
---------- Forwarded message ----------
From: drew Roberts <zotzbro(a)gmail.com>
Date: Sun, Feb 10, 2013 at 8:55 AM
Subject: Re: [LAU] So what do you think sucks about Linux audio ?
To: Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
On Sun, Feb 10, 2013 at 8:37 AM, Ralf Mardorf
<ralf.mardorf(a)alice-dsl.net> wrote:
> On Sun, 2013-02-10 at 12:17 +0100, Jörn Nettingsmeier wrote:
>> On 02/10/2013 01:59 AM, gerald.mwangi(a)gmx.de wrote:
>>
snip
>
> Using Linux, keeping the workflow can become a PITA, just by updating
> the DE ;), there are no updates for a 8 track analog recorder.
So just buy an already setup, tested, and warranted computer from
someone who knows what they are doing. Then, ***do not update it
yourself*** - use it as is just like a dedicated piece of equipment.
Down the road, get that same person who knows what they are doing to
update it for you or build you a new one.
I am not saying that these problems do not exist, and things can get
better for those who don't mind knowing a bit. I am saying thought
that for the person who does not want to know anything, they can avoid
the knowing somewhat if they will take an approach along the lines
mentioned.
>
> IMO the issue is "stand alone" vs "computer".
>
> Regards,
> Ralf
all the best,
drew
--
http://freemusicpush.blogspot.com/
Hey all!
I have a simple enough question, but I don't know the best practice for
solving it, so figured I'd ask.
There's an LV2 synth running in a LV2 host. The synth exposes its operation
trough control ports.
Option 1:
The plugin can bind incoming MIDI events to these control ports values,
allowing "standard" MIDI maps to be made for the synth.
Use cases include using the synth on another machine with the same
hardware: easy operation, layout identical to before.
Downside: these MIDI binding values are hard coded in the plugin, and can't
be changed. Also the host may update the control port (which has been
effected by the MIDI stream) and causes a parameter jump.
Option 2:
The host has to implement its own form of binding the MIDI events to the
control ports.
Downsides: the plugin has no control over what causes what effect, so no
standardized maps can be made.
Application specific MIDI mapping... which is nasty.
I think the "safe option" is number 2, each application sorts this thing
out itself, and the user has to map the same synth per host.
The MIDI mapping situation on Windows and MacOS is terrible (IMO), with
various different "software re-map" features like Novation Automap, and
Bores midi translator just getting in the way even more.
Can anybody see a solution to using the same MIDI map for the same
instrument in different software, without hard-coding it in the plugin?
Or another solution? -Harry
Hi James,
On 02/09/2013 01:11 PM, James Stone wrote:
> Hi Flo, I am also running Ubuntu 12.10 and using jackdbus. It is
> really nice for things like playing along to youtube videos.. On my
> computer, I noticed that jack does have a tendency to lockup after a
> while when jackdbus is running. I had the feeling that it might be
> something to do with latency, as I found it is impossible to start
> jack at very low latencies with jackdbus running. I was using 128
> samples which seemed to be OK, but at that latency, the lockups
> occurred after some time. I tried increasing latency to 256
> samples/44.1k. Following this, it seems to operate fine (at least I
> have had no more dropouts), but it is all a bit fiddly to get it to
> work properly, and I would probably disable pulse if I wanted to do
> serious recording etc without the mixing capabilities that jackdbus
> adds.. James
I use very large period sizes, 1024 or even 2048. The problem of jackd
starting to eat 100% cpu occurs usually when I'm done with my current
work (recording something or fiddling around) and just leave it running
idly. Then when I return to my computer after a few hours jackd sits
there happily eating cpu. It has the side effect of heating my room, but
heating with electricity is expensive and thus I'd rather avoid it ;D
Have fun,
Flo
--
Florian Paul Schmidt
http://fps.io
Hi,
I was a long term jackd1 user and my first action on a new linux
installation (mostly using Ubuntu) was normally to remove pulseaudio as
it was badly configured and/or buggy. Things have changed and I really
started to like PA for everyday stuff. And then jackdbus came along
which together with the device reservation API and the jackd sinks
promised to make using these two things together more easy. This mostly
works fine, except for the device reservation bug in PA which is easy to
work around though:
- Make sure no audio process is actively using the soundcard you want
jackd to use
- Run pulseaudio -k
- Run jack_control start
I have noticed some issues with jackdbus though:
a] jack_control start sometimes doesn't work at all after the first time
it failed to aquire the device. A killall -9 jackdbus is in order to
restore it
b] after some hours of operation jackdbus starts to eat 100% cpu on two
of my four cores.
Are these known issues? I use Ubuntu 12.10 and jackd:
fps@mango 12:08:21 .../Games/Xonotic/ $ jackd -v
jackdmp 1.9.9
[...]
How to diagnose the 100% cpu thing more closely? The
~.log/jack/jackdbus.log shows nothing suspicious.
Thanks and regards,
Flo
--
Florian Paul Schmidt
http://fps.io
Currently, it's just for display and editing. There's no playback yet. And
it's still pre-alpha, so you can expect it to crash without expending too much
effort.
Just a few bug fixes. I've included the changelog to 0.1.3 as well, since the
announce didn't make the list. If all goes well, the next release should be
sometime in March.
Website:
http://sourceforge.net/projects/sqorlatti
Download (bzipped source tarball):
http://downloads.sourceforge.net/sqorlatti/Sqorlatti-0.1.3-b.tar.bz2
Changes in Sqorlatti 0.1.3-b:
* Fixed bug when trying to edit data in Score Dialog.
* Set initial background color of Staff Editor to white.
Changes in Sqorlatti 0.1.3:
* Converted configure/build system to cmake. See the INSTALL file for more
information.
* Added default tab tunings for std guitar and bass to Score.
* Added combo to select tab tuning to track dialog.
* Cleaned up some C-style casts and fixed some sloppy code involving const.
* Added edit modes (select, insert, and delete) to StaffEditor.
* ToolBar in StaffEditor with common note durations. For use in insert mode.
* Allow add/remove notes to chords and tuplets.
* Cleaned up Staff Editor drag & drop a little. There's still not much
consistency checking, though.
* Added some user preferences, in particular, Staff Editor font size and
background color. These preferences get stored in $HOME/.config/Sqorlatti (the
usual place for Qt to put QSettings data). On the initial run, you probably
want to change the Staff Editor background color. You can do this through the
main window menu Tools->Preferences->Staff Editor.
Known problems:
* cmake cleanup not very good when doing in-source builds.
* Undo for inserting events and containers through MasterView not combined
into a macro, so separate commands are issued for insert and edit. It's not
really wrong, just inconvenient and confusing.
* Editing tab tunings not yet implemented.
--
7:8
On Tuesday 05 February 2013 18:26:24 David Baron wrote:
> My main complaint is not really about Linux, per se, but the whole DAW,
> etc., scene: Lack of interoperability!
>
> I have a lot of Cakewalk files from the Windows days. Cannot do anything
> with them besides play two tracks in Cakewalk-Express using WINE.
That is because you have been ignoring that KMidimon reads and plays Cakewalk
WRK files. And my library drumstick-file is available under a free license,
offering this functionality to any interested developer.
For me, this says everything about the worse problem in the Linux audio
development community.
Regards