I apologize for cross posting. I asked this on Alsa-Users a couple of
days ago but haven't received any responses. As it's about shopping I
might do this weekend I figured I'd try here also. Thanks in advance.
I'd like to pick up something to do simple mobile recording gigs with
my laptop. It needs to be USB 2.0 based, have 2 XLR inputs, support
headphone monitoring and preferably do 96KHz.
The M-audio Fast Track Pro seems to come closest although as I
understand it that device won't do 96K on all inputs and outputs at
the same time. Not a huge deal but one tick against for that.
What other devices do folks suggest I take a look at?
Thanks,
Mark
Hi Everyone
Just posted on Sourceforge a new version of these plugins.
I added:
- a CV to Hz convertor and Hz to CV (seems to be working ok, the
VCO is now in tune)
- The VCA module from AMS (called VCA Lin and VCA Exp)
- The ENV module from AMS
With those, it should be possible to create very simple modular synths in Ingen.
>From the few test I have done, things seems to be working fine, but
feel free to provide any comments and feedbacks!
The file can be downloaded from here:
http://sourceforge.net/projects/avwlv2/files/
Aurélien
> On Sat, 2011-10-08 at 16:52 +0100, Aurélien Leblond wrote:
>> That's weird, the error is in the lv2-c++-tools...
>> I might have something missing but I can't figure out what...
>>
>> Anybody that can help?
>
> This package causes a lot of hassles, and a lot of user confusion.
>
> I recommend plugin developers include the relevant headers in their
> projects (or derivates of them, e.g. those at
> http://svn.drobilla.net/lad/trunk/plugins/lolep.lv2/src/) rather than
> depend on these packages, unless you actually need the other things in
> them, which is not the case here (or virtually everywhere else).
What are these "other things"?
I'm using the lv2peg tool and the peg files. (I basically followed the
instructions on "lv2 programming for idiots").
Hello,
I got Beatrix patched and running, but it doesn't seem to receive/honour
noteoffs: so notes don't decay. I haven't had this sort of problem with
any of the other synths I tried. Does anybody have any idea what could
be the problem. It is in no way urgent, but I find it odd.
Cheers,
S.M.
--
After almost two years, I'm happy to announce that a new version of
`synthclone` is available for download!
The new version of `synthclone` is a complete departure from the utility
application I wrote two years ago on a rainy weekend. Here are the most
important changes:
- `synthclone` is now a Qt-based application with a table interface that
allows a user to configure sample times, release times, notes, velocity
values, aftertouch, channel pressure, and MIDI control changes on a
zone-by-zone basis. You can tweak the parameters and audition samples
until you're satisfied with the samples you've acquired.
- The application is now session-based. Sessions can be saved and
restored.
- `synthclone` comes with `libsynthclone`, a plugin API that allows
developers to write plugins that can interact with and extend the
application. Developers can add components to `synthclone`, including
sampler components (for sending MIDI and acquiring audio data), effect
components (for altering audio data), and target components (for
writing patches that work with software that can play back sample-based
instruments). In addition, the API allows plugins to do almost
anything that the application itself can do. All changes to the
session are accessible via the observer pattern (using Qt signals and
slots), allowing plugins to easily sync to session changes.
- `synthclone` is distributed with several plugins:
1.) libsynthclone_hydrogen - Builds Hydrogen drumkits.
2.) libsynthclone_jack - Sampling via the JACK Audio Connection Kit.
Includes JACK Session support.
3.) libsynthclone_sfz - Builds SFZ instruments.
4.) libsynthclone_trimmer - Trims "silence" off of the start and end
of acquired samples.
5.) libsynthclone_zonegenerator - Generates zone data for acquiring
samples.
- The application can write multiple targets (i.e. Hydrogen and SFZ) in
one session. No need to restart `synthclone` and wait while samples
are reacquired.
The new version of `synthclone` is available at:
http://synthclone.googlecode.com/
This is an alpha release. Please report bugs using the issue tracker:
http://code.google.com/p/synthclone/issues/list
If you like `synthclone` and have ideas that can make it better and/or want
to keep up with its progress, join the users group:
http://groups.google.com/group/synthclone-users
If you're a developer and want to write plugins for `synthclone` or
contribute to the application itself, join the development group:
http://groups.google.com/group/synthclone-development
On a closing note, I'd like to thank Peter L. Jones for patiently answering
my questions about the SFZ format. With his help, I was able to understand
far more about the SFZ format than I ever could using the official
documentation. Thanks, Peter!
--
Devin Anderson
devin (at) charityfinders (dot) com
CharityFinders - http://www.charityfinders.com/
synthclone - http://synthclone.googlecode.com/
---------- Forwarded message ----------
From: SuperCollider Symposium London <info(a)sc2012.org.uk>
Date: 2011/10/10
Subject: SuperCollider Symposium, London April 2012: deadline extended
to 30th Oct
Dear all,
The SuperCollider Symposium 2012 is going to be fantastic. To make
sure you have a chance to get involved, we're extending the deadline
by two weeks - to 30TH OCTOBER.
That's almost three weeks from now, so get your ideas for talks,
music, exhibits, workshops polished up! The full call follows:
The SuperCollider Symposium is an international event for musicians,
artists, researchers and coders working with the SuperCollider
software. It features a technical conference, introductory workshops,
and a diverse programme of music and art.
The next SuperCollider Symposium will be April 12th–19th 2012, in London.
http://sc2012.org.uk/
We invite submissions of music, artistic works, talks, and workshops.
Submissions will be peer-reviewed, and should be submitted by:
* Submission date: 16th Oct 2011 -- EXTENDED TO 30TH OCT
* Notification of acceptance: 2nd Dec 2011
The Symposium will be hosted at various venues across East London, by
QMUL Centre for Digital Music, Goldsmiths Digital Studios, City
University Centre for Music Studies, and other partners. All concerts,
performances and exhibitions will be open to the public.
Further details for submissions (plus submission instructions, at the end):
//////////////////
// TALKS
Conference talks are invited on topics of SuperCollider-related
research, technical development, or artistic/musical practice. (Note
that submission is by abstract only, there are no full papers.) Some
examples of subject areas include:
* Audio/music synthesis
* Interactive sound and music
* Machine listening
* Generative sound and music
* Artistic developments
* Teaching and Learning
* Creative Collaborations
* Extending SuperCollider
* Using SuperCollider with other environments
//////////////////
// CLUB MUSIC
The symposium will feature a club night in an East London venue.
Therefore we’re calling for submissions of music for dancing to. Acts
can be any style, but must include some substantial use of
SuperCollider.
//////////////////
// MUSICAL/SOUND WORKS
City University London in partnership with Plus-Minus ensemble
(http://www.plusminusensemble.com) will host an evening concert of
musical/sound works in City University Performance Space.
Works may fall into two categories: 1. purely
electronic/electroacoustic/acousmatic, or 2. instrument/s plus live
electronics. Available instruments are clarinet (doubling bass
clarinet), violin, and piano (doubling accordion). All works must
include some substantial use of SuperCollider.
Technical specs:
8-channel loudspeaker ring with subs, plus on-stage stereo pair.
Alternative loudspeaker configurations may be possible.
//////////////////
// WORKS FOR EXHIBITION
The exhibition programme at the Symposium will be hosted at the Art
Pavilion gallery (Mile End Park, London E3 4QY) and in the adjoining
Arts Park, which features a small lake island. We seek proposals for
works small or large, which may be exhibited in the gallery space
and/or the outside space (lake, island, bridges). Proposals which make
use of the outside area are particularly encouraged. Works must
include some substantial use of SuperCollider.
Exhibition venue information:
* Webpage for the Art Pavilion (inc floor-plans):
<http://www.towerhamlets.gov.uk/lgsl/451-500/461_parks/mile_end_park/mile_en…>
* Map showing the building, the lake and the island:
<http://osm.org/go/euu6whJRk–>
* Photo inside gallery: <http://www.flickr.com/photos/louisejoly/378646724/>
* Photo of the lake+island, with the gallery behind:
<http://www.flickr.com/photos/danstowell/5896781088>
Please ensure that you include information of the space and materials
required for the work.
//////////////////
// WORKSHOP LEADERS
Workshops will be held Sat 14th & Sun 15th April (at Goldsmiths), for
beginner/intermediate-level users. We seek people who would like to
lead a workshop – workshop leaders will be given free admission to the
Symposium. Workshop themes can be general (e.g. Introduction to
SuperCollider) or can cover specific topics, but please target the
beginner/intermediate level. Examples of workshop topics:
* Sound synthesis
* Live coding
* GUI programming
* Interaction with live instruments
* SuperCollider for research
//////////////////
// OTHER
If you would like to propose some other event or feature of the
symposium, please do – giving as much information as possible.
//////////////////
// SUBMISSION INSTRUCTIONS (for all types):
Please email your submission to submit(a)sc2012.org.uk and include the
following information:
* The type of submission (concert / talk / club / installation /
workshop / other)
* Name
* Title (of piece, of talk, etc)
* A description or abstract (no more than 500 words).
* Any specific resources requested (e.g. materials, performers)
* For music/audio, an audio recording can be submitted to soundcloud
dropbox <http://soundcloud.com/supercollider2012>, or you can provide
a link to an online recording. It is not compulsory to send a media
file, but it will help your submission.
/////////////////
Any questions? please contact info(a)sc2012.org.uk or tweet @scsymposium.
Hi,
there is an exciting new mixing desk in the Midas product range, the
"Venice F32" which has Firewire I/Os. Does anyone know if it will work
with Alsa/Ffado?
best, Peter
Greetings,
Hopefully someone here has a similar setup and can help me out.
Yesterday I installed a nice new Seagate 1T drive in my main machine. No
problems with the physical installation, and the BIOS recognizes the
drive. Next I installed Fedora 14 (x86_64) on the new drive. Again, no
problems with the actual installation. On reboot my troubles started.
I already have a system on this machine, an ancient 64 Studio 2.1 that
works beautifully. Alas, it's very old, hence the second drive and new
install. The old system is on /dev/sda1, with a swap at /dev/sda5. The
new disk is /dev/sdb, and the new system is on /dev/sdb1 and /dev/sdb2.
On reboot the machine went directly to the old grub menu for 64 Studio,
which had no entry for Fedora.
Before going further, I should note that I can't even mount the new disk
while in 64 Studio. The older system doesn't recognize ext4 file
systems, so I can't access the second drive.
Okay, back to the boot. I used AV Linux to access the new drive and
copied its grub entry to the old grub. Now when I boot I can see and
select the Fedora entry, but I receive errors whether I attempt the boot
from sdb1(hd1,0) or sdb2 (hd1,1). Sorry, I don't remember the error
numbers, I'll get them and send them if needed. The installation media
was without checksum errors, so the installed system should be ready to
go. I just can't figure out how to boot into it from my existing menu.
So my questions are: How can I get this machine to recognize the new
installation ? Do I need to re-install and manually configure grub ? Is
the 64 Studio boot loader simply too old to handle the new configuration
? The new grub menu.lst include a line "boot=/dev/sdb" but it appears to
mean nothing to the older grub.
I've pasted what I think are the relevant contents of the 64 Studio
menu.lst at the end of this message, in case anyone cares to investigate
and advise. I don't mind re-installing if necessary, but it would be
nice to avoid that expenditure of time. Suggestions for fixing would be
much appreciated. :)
Best,
dp
-------------------- begin 64 Studio grub menu.lst -----------------------
title 64 Studio, kernel 2.6.21-1-multimedia-amd64
root (hd0,0)
kernel /boot/vmlinuz-2.6.21-1-multimedia-amd64 root=/dev/sda1 ro
vga=771 splash=silent
initrd /boot/initrd.img-2.6.21-1-multimedia-amd64
savedefault
title 64 Studio, kernel 2.6.21-1-multimedia-amd64 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.21-1-multimedia-amd64 root=/dev/sda1 ro
vga=771 splash=silent single
initrd /boot/initrd.img-2.6.21-1-multimedia-amd64
savedefault
------------------- the new addition ------------------
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root
# initrd /initrd-[generic-]version.img
# boot=/dev/sdb
# default=0
# timeout=0
# splashimage=(hd0,0)/grub/splash.xpm.gz
# hiddenmenu
title Fedora (2.6.35.6-45.fc14.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.35.6-45.fc14.x86_64 ro
root=/dev/mapper/VolGroup-lv_root rd_LVM_LV=VolGroup/lv_root
rd_LVM_LV=VolGroup/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.35.6-45.fc14.x86_64.img
I just realized I sent this directly to Clemens, instead of to the list.
I guess it's no big deal, but it was supposed to go to the list.
On Sat, Oct 08, 2011 at 01:20:34PM +0200, Clemens Ladisch clemens-at-ladisch.de wrote:
> On 10/07/2011 08:57 PM, Chuck Martin wrote:
> > % ps -eo pid,rtprio,cls,cmd
> > 16531 - TS /usr/bin/jackd -v -P70 -t2000 -dalsa -dhw:Intel -r48000 -p1024 -n2 -Xseq -i2 -o2 -I1 -O1
> >
> > It looks like set_rlimits is working until I look at the realtime priority
> > with ps. What am I doing wrong?
>
> Realtime priorities are shown by ps only for threads that actually are
> using a realtime scheduling policy, and jackd's first thread doesn't.
> Use H to show threads.
Thanks, Clemens. That explains why I thought I had it working, and
then not working later. The first time, I used the ps command from
http://subversion.ffado.org/wiki/IrqPriorities (even though I'm not
using ffado), which included the -L option (which also shows threads
like H), but the next time I was doing it from memory, and I neglected
to include the -L option, so it looked like it wasn't working when it
really was. Well, one advantage to making that mistake is that I've now
learned something more about ps. I was wondering why there were so few
lines in the output from what I remembered from the first time, and now
I know.
Chuck