On Wed, Oct 10, 2012 at 6:09 AM, Dan MacDonald <allcoms(a)gmail.com> wrote:
> Hi LV!
>
> Nice and interesting write up of your experiences and opinions there. I
> agree with most all of it except:
>
> "Saving projects is still a huge problem. In addition to LADISH we do now
> have NSM, the Non-Session Manager, which seems like a workable solution, so
> we'll see how this works out in the long run.
> LMMS seems to be the only game in town for those who want to save full
> projects by just clicking "Save" and not having to install and configure a
> "session manager". I must admit, by the way, that I have not followed LMMS
> recently."
>
> Saving projects is only tricky if you use the modular approach versus
> instrument plugins hence this isn't really a problem for A3 and qtractor.
> Aside from LMMS, MusE and sunvox have a few integrated instruments so they
> don't have this problem either (if you stick to the built-in synths for
> Muse only - sunvox doesn't handle plugins) and pretty soon MusE should gain
> native VST support to further improve this situation.
>
> Your article has reminded me of my one and only JACK complaint/ feature
> (yep - just one!!!) request which I filed a couple of years ago now but is
> still to be addressed:
>
> http://trac.jackaudio.org/ticket/202
>
> I'm surprised others haven't been asking for more descriptive 'device
> busy' error messages from JACK as for many years this has been my only
> issue with JACK - it doesn't start and you don't know what process is
> preventing it doing so. Quite often I'll not bother doing the detective
> work and just reboot but that is hardly ideal so I think this small
> addition would make JACK (and qjackctl) and as a result Linux audio much
> more user friendly.
>
> Your thoughts Mr Davis?
>
current jack1 (released months or years ago):
if (snd_pcm_open (&driver->playback_handle,
playback_alsa_device,
SND_PCM_STREAM_PLAYBACK,
SND_PCM_NONBLOCK) < 0) {
switch (errno) {
case EBUSY:
current_apps = discover_alsa_using_apps ();
if (current_apps) {
jack_error ("\n\nATTENTION: The
playback device \"%s\" is "
"already in use. The
following applications "
" are using your
soundcard(s) so you should "
" check them and stop
them as necessary before "
" trying to start JACK
again:\n\n%s",
playback_alsa_device,
current_apps);
free (current_apps);
Hey Dan!
"Saving projects is only tricky if you use the modular approach versus
instrument plugins hence this isn't really a problem for A3 and qtractor."
True, but since there are very few plugins, most power of Linux Audio today
is not in its plugin collection ;)
On Wed, Oct 10, 2012 at 2:09 PM, Dan MacDonald <allcoms(a)gmail.com> wrote:
> Hi LV!
>
> Nice and interesting write up of your experiences and opinions there. I
> agree with most all of it except:
>
> "Saving projects is still a huge problem. In addition to LADISH we do now
> have NSM, the Non-Session Manager, which seems like a workable solution, so
> we'll see how this works out in the long run.
> LMMS seems to be the only game in town for those who want to save full
> projects by just clicking "Save" and not having to install and configure a
> "session manager". I must admit, by the way, that I have not followed LMMS
> recently."
>
> Saving projects is only tricky if you use the modular approach versus
> instrument plugins hence this isn't really a problem for A3 and qtractor.
> Aside from LMMS, MusE and sunvox have a few integrated instruments so they
> don't have this problem either (if you stick to the built-in synths for
> Muse only - sunvox doesn't handle plugins) and pretty soon MusE should gain
> native VST support to further improve this situation.
>
> Your article has reminded me of my one and only JACK complaint/ feature
> (yep - just one!!!) request which I filed a couple of years ago now but is
> still to be addressed:
>
> http://trac.jackaudio.org/ticket/202
>
> I'm surprised others haven't been asking for more descriptive 'device
> busy' error messages from JACK as for many years this has been my only
> issue with JACK - it doesn't start and you don't know what process is
> preventing it doing so. Quite often I'll not bother doing the detective
> work and just reboot but that is hardly ideal so I think this small
> addition would make JACK (and qjackctl) and as a result Linux audio much
> more user friendly.
>
> Your thoughts Mr Davis?
>
> On Wed, Oct 10, 2012 at 9:24 AM, Louigi Verona <louigi.verona(a)gmail.com>wrote:
>
>> Hey fellas!
>>
>> Would like to present an article I've written. Mostly wrote it to start a
>> conversation and hear what others have to say on the subject.
>>
>>
>> http://www.louigiverona.ru/?page=projects&s=writings&t=linux&a=linux_progre…
>>
>> You can comment here or on my textboard (which does not require
>> registration).
>>
>>
>> --
>> Louigi Verona
>> http://www.louigiverona.ru/
>>
>> _______________________________________________
>> Linux-audio-user mailing list
>> Linux-audio-user(a)lists.linuxaudio.org
>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>>
>>
>
--
Louigi Verona
http://www.louigiverona.ru/
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
First, what I would like to do is pick which channel I send audio to
on the RME 9632 card.
My RME card is device 0.
When I call this function:
snd_pcm_open(&handle,device,SND_PCM_STREAM_PLAYBACK,0)
And set device = plughw:0,0 I get playback across all the RME
outputs.
(Just using hw:0,0 without the "plug" prefix does not work for some
reason which may or may not matter.)
So, how do I access the subdevices/channels?
When I run aplay -l I only see 1/1 subdevices.
Shouldn't I be able to set my device to hw:0,0,1 or plughw:0,0,1 to
access channel 2, for example?
There's no .asoundrc. Do I need it for this?
Finally, when attempting multichannel alsa, I assume I need to
simply make an array of pointers to the same datatype as "handle" and
run through
initializing each handle separately.
In the first time thought the loop, I can get handle[0] and all its
parameters to initialize without errors.
When I try to initialize handle[1] on a new device such as
plughw:0,0,1 I get an error that the device or resource is busy.
I feel like I've hit a brick wall here. Perhaps I am out of my
league. But, it feels tantilizingly close to working.
Thanks guys/gals!!
Grekim
Hi there,
Maybe some of you agree with me, that this has been the longest since
last dot release and the new one with the least brand new features count
being introduced. Aha no big deal I say, the uber-procrastinator is just
roaring its ugly head once more, specially after a beloved summer
vacation season. Whatever.
Qtractor 0.5.6 (golf tango) is now released!
One of the interesting dots, if not the most, is that LV2 State Files
interface implementation, once in a gruesome SNAFU support status, is
now officially over. For the laymen it means that any files, referenced
by those LV2 plug-ins which implement the LV2 State Files interface,
will get righteously bundled to an archive/zip session file (suffix or
extension .qtz), all other cases remain untouched. That should add up
some notches on the session portability and archival ranks and purposes.
Besides, LV2 1.0.0 compliance status is now closed business. I hope.
Moving on, slowly forward...
Release highlights:
* LV2 State Files support (NEW)
* Unused files clean-up removal (NEW)
* Edit/Insert empty range (NEW)
* MIME Document types and icons (NEW)
* Improved plug-in state resilience (FIX)
* French and Japanese translations (NEW)
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
- source tarball:
http://downloads.sourceforge.net/qtractor/qtractor-0.5.6.tar.gz
- source package (openSUSE 12.2):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.6-2.rncbc.suse122.sr…
- binary packages (openSUSE 12.2):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.6-2.rncbc.suse122.i5…http://downloads.sourceforge.net/qtractor/qtractor-0.5.6-2.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:
- The dedicated audio outputs setting for instrument plugins was not in
effect as default global option for new MIDI tracks, now fixed,
hopefully (thanks to danboid aka. Daniel MacDonald persistence).
- An immediate Files widget cleanup option is now made available, as to
select and remove all unused file entries.
- MIDI track (un)solo/mute reset clip event sequence fixing; definite
regression to MIDI track's occasional muting bug while clip editing and
playback is rolling.
- Apologies due on this one: shift/ctrl keyboard modifiers are back in
business to change MIDI events currently selected in one single step
while on MIDI clip editor (aka. piano-roll). Sorry.
- Japanese (ja) translation added (by Takashi Sakamoto).
- General time-scale bar, beat and tempo rounding fixing.
- Keyboard shortcuts configuration (Help/Shortcuts...) now checks and
warns for already assigned key sequences.
- The View/Snap menu is now listed as fully accessible actions, making
each snap-per-beat setting assignable to a keyboard shortcut (after a
feature request by danboid aka. Daniel MacDonald, thanks).
- Fixed MIDI resize tool, now applying symmetric proportional changes to
pitch-bend event values [-8191, +8191].
- Fixed re-loading of LV2 Presets that are newly created/saved during
current session; actually delete and remove a LV2 Preset if found in the
file-system (as suggested by Jiri Prochaszka aka. Anchakor, thanks again).
- Preset drop-down list is now sorted, on plugin properties dialog.
- After a long absence, edit(blue) cursor vertical lines are back on the
MIDI clip editor views (aka. piano-roll).
- LV2 1.0.0 compliance phase II: LV2 State Files support completed.
- Updated to newer LV2 External UI extension support (now maintained by
Filipe Coelho aka. falktx).
- Brand new editing tool: empty range insertion, split/moving clips or
events forward the specified edit-head/tail interval, defaults to next
measure or bar (cf. menu Edit/Insert/Range, Track Range).
- Don't show the waiting cursor anymore when loading any plugins which
might have a nice native editor (GUI) and options are set to show it.
- MIDI clip editor now hopefully rid of random but persistent muting, a
slight regression to editing while playback is rolling.
- A MIDI file player's bug, evident while transport rolling in looped
mode, has been fixed with yet another oneliner patch (kind by Jiri
Prochaszka aka. Anchakor, thanks again).
- LV2 plugins with a Qt4 GUI (guess what or whom?) are now guaranteed to
some reasonable window type like Qt::Widget but not Qt::Dialog nor
Qt::Popup, preventing those from standing always on top while on some
window managers or desktop environments (a simple addition by Jiri
Prochaszka aka. Anchakor, thanks).
- MIME type icons support for session (*.qtr *.qtr), template (*.qtt)
and zip/archive (*.qtz) are now being introduced.
- LV2 State Files feature support is shamelessly getting real trial, now
letting files referenced in LV2 plugin states to be seamlessly included
when saving to a zip/archive file bundle (.qtz suffix). Added some
virtual destructor stubs to shut up gcc 4.7 warnings.
- Improved plugin state resilience, now finally with parameter name
matching, specifically targeted on loading old sessions or plugin preset
files (.qtx), preserving old saved plugin states as much as possible in
face of rogue or discrete parameter index renumbering, due naturally on
any plugin's life cycle ie. upgrades etc.;)
- Added some more snap-to-beat divisors (Beat/14, /21 and /28) due on
feature request ticket, while dropping highest, probably useless one
(Beat/128).
- New French (fr) translation added (by Yann Collette, thanks).
- Slight late optimization on vertical zebra/grid lines drawing.
Enjoy!
--
rncbc aka Rui Nuno Capela
Hi All,
Praxis LIVE is an open-source, graphical environment for rapid
development of intermedia performance tools, projections and
interactive spaces.
A new build of Praxis LIVE is now available for download. While this
is mainly a bug fix release, it does see the Praxis command line
player added to the main installation, and work which paves the way
for distributing Praxis projects as standalone applications (coming
separately in the next couple of weeks).
Website - http://code.google.com/p/praxis
Release notes - http://code.google.com/p/praxis/wiki/ReleaseNotes
Videos - http://praxisintermedia.wordpress.com/2012/07/30/video-rough-cuts-1/
If any of you who've been playing with Praxis LIVE would be interested
in submitting example projects for the next release, please get in
touch with me off-list.
Thanks and best wishes,
Neil
--
Neil C Smith
Artist : Technologist : Adviser
http://neilcsmith.net
