Greetings,
I'm writing an article about using Jaunty for a desktop recording
platform, so of course I had to create a demo. Out of sheer laziness I
decided to record a song written by someone else, thus we now have:
http://linux-sound.org/audio/idontworryaboutathing.ogg
And for the OGG-deficient:
http://linux-sound.org/audio/idontworryaboutathing.mp3
The song is a great Mose Allison tune. The recording was quick & dirty,
done entirely (and literally) from the desktop. All parts performed by
DP except the drums, which are once again from the Beta Monkey Jazz
Essentials collection.
Vast thanks to the Ardour devs. What an amazing program.
Enjoy, and comments are welcome. Go easy on me, folks, this one was a
real rush job.
Best,
dp
Announcing the new public beta release of phasex! All phasex users
are encouraged to upgrade. Since the days of 0.11.1, all known bugs
and many annoying quirks have been worked out, making
PHASEX-0.12.0-beta3 is the most stable, best sounding, and most
studio friendly release yet:
* Fixed all currently known crash issues and build issues. Code has
been updated for newer versions of gcc, gtk, and glibc. Realtime
threading issues have been fine-tined, using realtime locks where
appropriate. The build system has been fixed up for newer
distributions and includes default optimizations for the entire x86
family (run './configure --enable-arch=foo', where foo is an
architecture supported by your version of gcc).
* Sound quality has been greatly refined by reshaping envelope
curves (eliminating pops and clicks), adding hermite interpolation
to the chorus (removing fuzziness from chorus), adding fine tuning
to oscillator frequencies and FM amounts, adding sampled oscillators
(currently with Juno-106 and vocal samples), fixing portamento
and key triggering logic, and more.
* The JACK code has been reworked to allow multiple instances with
persistent instance numbers and resilience to JACK crashes and
restarts.
* The GUI has been refined slightly, with a new color scheme, patch
folders in the file dialog shortcuts list, and a couple slight
optimizations to the knob code.
* There's more. See http://sysex.net/phasex/beta for details if
you're that curious.
Since 0.12.0-beta2, fixes have been implented for GTK >= 2.16
(fixing Fedora 11 builds), the max polyphony has been turned into a
runtime configurable setting, and the build system and default
architecture specific optimizations have been fixed up some more.
Source tarball and arch specific Fedora 11 RPMS are now available
for download:
http://sysex.net/phasex/beta/phasex-0.12.0beta3.tar.gzhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.src.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.i386.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.i586.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.i686.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.athlon.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.amd64.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.x86_64.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.ia32e.rpm
Build reports and bug reports, and package build files for all
distributions are highly welcome. This is the final beta for
0.12.0. Any build and crash issues reported in the next two weeks
will be fixed for the 0.12.0 stable release. Please direct any
feedback to weston(a)sysex.net.
The latest version of phasex can always be found at:
http://sysex.net/phasex
For those of you who use git:
git clone http://sysex.net/git/phasex.git
Thank you all for your support, feedback, and contributions over the
years, helping to make PHASEX what it is today.
Happy music making!
--ww
It feels like my several year old PC will crap out soon for one reason
or another, so I need a replacement, better sooner than later.
This time it should be a laptop and I heard that formerly IBM and now
Lenovo thinkpads are of good build quality, even if they only come
with intel CPUs and cost an arm and a leg.
So, do you have any experience with those for audio work?
I'd be most interested in the T and R series and more recent models.
Also helpful would be some data that's impossible to find on websites:
- What chipsets are built in?
- do the usb buses and the like share interrupts with something nasty
like graphics?
Helpful commands to gather that data:
cat /proc/interrupts
lspci
lsusb
Thanks in advance for any help.
Regards,
Philipp
Hi everyone,
Atte's recent thread about sync got me to thinking about MIDI clock.
Is there a simple app out there that will generate MIDI clock at a
tempo can can be defined? If not, would one of you
scripting/programming wizards be willing (or able, if what I'm asking
is possible) to drum something up?
Thank you,
Josh
--
Josh Lawrence
http://www.hardbop200.com
>> Agreed.
>>
>> If you want a Debian-based system, Ubuntu is much more focused on
>> requirements for a general-purpose desktop. Not specifically for
>> musicians of course, but easier to adapt for that purpose.
>
>maybe it is more of a trade-off -
This is the big If?.. Why specifically a Debian based distro?
Are you looking for the best performing music workstation, a politically correct
distro, a server or a general purpose desktop?
If the answer is music workstation, why does the choice need to be limited to
Debian?
Many would argue (including myself).. that a ground up type of distro, like
Gentoo, Paludis or Arch are the best way to start. Although Debian if carefully
installed will fit into this category.
I have also found this personally in experience too. I've tried the pre-built
distros for music Studio64, Apodio and UbuntuStudio and GP desktops Mandriva and
Ubuntu and found they were
a) bloated
b) did not contain everything I needed or had old versions of what I needed
c) trying to add things not in the repos was more than trivial
d) did not perform as fast as as a ground up distro...
e) a nightmare come upgrade if any customisations have been made..
Comparatively, I have a number of purpose built Gentoo systems (1 server, 2 media
pc's and one studio computer) and while they take an initial amount of work to
built, once built they are very reliable, and perform amazingly quickly... Should
an app not be available through portage or an overlay .. it is trivial to install
from source.. My audio machine is now back on a standard (gentoo-sources) kernel,
I have done very little in PAM and get fantastic latency results.
Reports from friends using Arch reflect a similar situation.
However, for those looking for an easier option.. AV Linux looks like an amazing
option.. although it is more of an image that needs modification rather than a
distribution per-se. And yes it is debian based...
But to re-iterate my question.. why necessarily a debian based solution, why not
simply look for something that will give you a reliable, fast performing music
machine? Debian may be able to provide this, but why limit the initial question
to something debian based?
cheers
Allan
Hello,
I have just bought a second hand keyboard, (edirol PCR-500) which has
loads of knobs and sliders on it. The trouble is that all the knobs are
pots, not rotary encoders; encoders would be much more useful I think
because it would mean that if you press a button to switch to a new
synth or effects patch, the correct defaults for it could be
automatically loaded to each of the knobs when you switch. Without that,
it seems like whenever you switch to a new instrument you would have to
spend a while tweaking all the knobs to get the right basic sound.
What I would like is a device with a couple of rotary encoders on it
(you only have two hands), maybe 16 buttons, and a character LCD screen.
The way it would work is (something-like):
- one of the buttons would be for loading new instruments. To switch to
a new instrument, you would press the button and then turn either
encoder. The LCD would show which instrument you were choosing from a
list, and you would press the button again to make the switch.
- most of the buttons would be for accessing different midi controls.
You could assign a midi control to an encoder by pressing the button for
that control first, then pressing a button underneath the encoder you
were assigning.
- having done this, that encoder would be bound to that midi control -
turning it would send out midi messages for that control, and also
update a display on the LCD saying what the level of that control is
currently set at.
- loading a new instrument would automatically set the right default
levels for each controller that that instrument used.
Does anyone know of anything like this that's already being made? If so
I might get hold of one and see if I can hack it to work with linux; if
not I'm thinking of having a go at making my own some time.
cheers,
andy baxter.
Guys, I was wondering:
Here, http://dis-dot-dat.net/mailman/listinfo/lam_dis-dot-dat.net
I read this:
*About LAM* English (USA)
LAM is a mailing list for posting you Linux-made music, getting feedback and
finding collaborators.
Software trouble should be discussed in LAU and the coding side of things
should be sent to LAD.
But there it seems that only one person (Julian) posts his music in the last
two years.
I see that music is been posted on all LA- lists occasionally, but I was
never sure whether it was the right place for posting (the various LA-
lists)
It would be nice to have a place where Linux music is posted and people
(audiophiles/musicians/linux geeks) make comments about it and generally,
hang out, say like http://www.zoxsy.com/
Any ideas, suggestions about it?
Viktor
I found a pdf of a MIDI implementation chart for the KORG padKONTROL
*not the nanoKontrol*
but it might be similar enough to get people started on patching
something up in pd
http://kpkproject.twoday.net/files/Padkontrol-Sysex-Imp/