1 Dec
2018
1 Dec
'18
4:26 p.m.
Greetings,
A little moody ambience from a work in progress exploring automatic
melodic generation with VCV Rack modules.
https://www.youtube.com/watch?v=DXFz7xNGYjc
Still working on it. :)
Best,
dp
1 Dec
1 Dec
6:46 p.m.
On Sat, Dec 1, 2018 at 9:27 AM Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Greetings,
A little moody ambience from a work in progress exploring automatic
melodic generation with VCV Rack modules.
if you could:
(a) do the hour long version
(b) come over and run my VCV Rack install for me
that would just fine. Lovely work, as usual! Such nice tone taste.
3 Dec
3 Dec
1:25 p.m.
Hi Paul,
re: 1625 :
if you could:
(a) do the hour long version
(b) come over and run my VCV Rack install for me
that would just fine. Lovely work, as usual! Such nice tone taste.
Thank you ! I'd be happy to do both, but alas, my time is limited, we're
moving into new digs this week. Sorry about that. :)
I had you and Will Godfrey in mind after working on this one, I hoped
you'd enjoy it. I do have a second section prepared - it adds about
another four minutes to the piece - I just have to figure a way to merge
the essential aspects of the continuation into the original patch. Rack
is not yet optimized nor does it support multicores so I have to be
careful about patch size, there's a tipping point that sends its
performance into xrun hell.
Regarding the sounds: I use fairly simple modules for sound creation in
Rack, doing so makes me think about ways to subvert their simplicity. I
also use only a few straightforward effects (reverb, chorus, tremolo), I
find it helps to keep the textures clear.
I had hoped to present a "composing with VCV Rack" paper at LAC 2019 but
our move puts that notion to rest. Dang.
Best always,
dp
1:49 p.m.
Enjoyable work.
I am also one of those people who wonders how you managed to make VCV Rack
work. On my machine all it does is generate XRUNs.
Louigi Verona
https://louigiverona.com/
On Mon, Dec 3, 2018 at 12:36 PM Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Hi Paul,
re: 1625 :
if you could:
(a) do the hour long version
(b) come over and run my VCV Rack install for me
that would just fine. Lovely work, as usual! Such nice tone taste.
Thank you ! I'd be happy to do both, but alas, my time is limited, we're
moving into new digs this week. Sorry about that. :)
I had you and Will Godfrey in mind after working on this one, I hoped
you'd enjoy it. I do have a second section prepared - it adds about another
four minutes to the piece - I just have to figure a way to merge the
essential aspects of the continuation into the original patch. Rack is not
yet optimized nor does it support multicores so I have to be careful about
patch size, there's a tipping point that sends its performance into xrun
hell.
Regarding the sounds: I use fairly simple modules for sound creation in
Rack, doing so makes me think about ways to subvert their simplicity. I
also use only a few straightforward effects (reverb, chorus, tremolo), I
find it helps to keep the textures clear.
I had hoped to present a "composing with VCV Rack" paper at LAC 2019 but
our move puts that notion to rest. Dang.
Best always,
dp
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
2:41 p.m.
Hi Louigi !
On 12/03/2018 06:49 AM, you wrote:
Enjoyable work.
Thank you, I caught your comment on YT too. :)
I am also one of those people who wonders how you
managed to make VCV
Rack work. On my machine all it does is generate XRUNs.
I urge anyone interested in VCV Rack to join the Facebook official group
page. Yes, it's Facebook, and yes, it's chaotic, but it's also packed
with information for and from users on all platforms, including Linux.
If you can use FB's Search function you can usually find what you're
looking for. Otherwise it's a pretty good read, lots of news on a daily
basis. There's also a large and growing larger library of patches
available at patchstorage.com, a very helpful resource.
So, a few questions for anyone having problems getting Rack up and running:
Are you using the precompiled Rack or did you build it yourself ?
What's the last version you tried ? It's currently at 0.6.2c coming up
quickly on a 1.0 release.
I assume you're using a low-latency and/or realtime system with JACK ?
Do you have a multicore CPU running in performance mode ?
And a few suggestions, again to anyone interested:
Start with extremely simple patches, i.e. patch together a Fundamental
VCO-1 and VCA-1 (level set to 0) by running a cable from the oscillator
sine output into the amplifier and onwards to the Core set's Audio module.
Make sure that the project sample rate matches your system audio sr
(it's listed under one of the top menu icons).
There's a minimum level requirement for OpenGL support. I figure, if you
got as far as the default display you're probably okay for the required
version.
Rack currently runs in single-core mode, so if your CPU has good support
for single-core you're better off than me. IIUC Intel CPUs outperform
AMDs in that regard. I would be happy to learn otherwise, my machine
runs an AMD FX 6300.
Good luck, let me know if I can be of more assistance. :)
Best,
dp
3:37 p.m.
On Mon, Dec 3, 2018 at 7:42 AM Dave Phillips <dlphillips(a)woh.rr.com> wrote:
[ ... ]
Following on from Louigi's question, I want to say on this mailing list a
couple of things about VCV Rack that i've said often on IRC but not
elsewhere. Really just two.
1) I want to give HUGE thanks and congratulations for Andrew Belt and what
he has done with VCV Rack. Not so much the program itself, but the
ecosystem he either deliberately or accidentally created around it. Some of
you (*cough* Dave *cough*) might remember that before I wrote Ardour and
JACK, my first foray into Linux audio was something called Quasimodo.
Powered by a reimplementation of CSound, the GUI was a lot like VCV Rack
(and other similar software). Quasimodo never succeeded, for a variety of
reasons, and it is so good to see a GPL'ed modular synth now finally really
finding and creating a community and success. The visual appeal, ease of
use, and relatively simple module API of VCV Rack have all been critical in
its success, and Andrew deserves many kudos for this. It really is amazing
to see the set of available modules (and their quality) and the dual
business model (no-cost vs. paid) for modules. I'm actually jealous.
2) All that being said, as a programmer, the internals of VCV Rack's engine
are deeply disturbing. It is really amazing that VCV Rack works as well as
it does. It isn't properly coupled to the audio hardware at all (it uses a
timer to drive the graph), and it can't be trivially modified. Thankfully,
someone has done the modification for the VST version of VCVRack (because
in a plugin, you have no choice), and so perhaps the redesign might make it
back into the mainline code. Given the lovely to use GUI and the fantastic
ecosystem, it's a little sad to see the internal code suggest almost no
understanding of how to write a realtime audio application. Maybe Andrew
had his reasons for the internal design - I don't know. But it certainly
makes it much more likely to have audio glitches and to be incapable of
operating at the lowest latencies. It works well enough for me, however
(and is a huge risk because I could spend hours playing with it).
4 Dec
4 Dec
10:43 p.m.
Thanks for sharing those observations about VCV Rack and the internal
software design in particular.
On Mon, 3 Dec 2018, 13:56 Paul Davis, <paul(a)linuxaudiosystems.com> wrote:
On Mon, Dec 3, 2018 at 7:42 AM Dave Phillips <dlphillips(a)woh.rr.com>
wrote:
[ ... ]
Following on from Louigi's question, I want to say on this mailing list a
couple of things about VCV Rack that i've said often on IRC but not
elsewhere. Really just two.
1) I want to give HUGE thanks and congratulations for Andrew Belt and what
he has done with VCV Rack. Not so much the program itself, but the
ecosystem he either deliberately or accidentally created around it. Some of
you (*cough* Dave *cough*) might remember that before I wrote Ardour and
JACK, my first foray into Linux audio was something called Quasimodo.
Powered by a reimplementation of CSound, the GUI was a lot like VCV Rack
(and other similar software). Quasimodo never succeeded, for a variety of
reasons, and it is so good to see a GPL'ed modular synth now finally really
finding and creating a community and success. The visual appeal, ease of
use, and relatively simple module API of VCV Rack have all been critical in
its success, and Andrew deserves many kudos for this. It really is amazing
to see the set of available modules (and their quality) and the dual
business model (no-cost vs. paid) for modules. I'm actually jealous.
2) All that being said, as a programmer, the internals of VCV Rack's
engine are deeply disturbing. It is really amazing that VCV Rack works as
well as it does. It isn't properly coupled to the audio hardware at all (it
uses a timer to drive the graph), and it can't be trivially modified.
Thankfully, someone has done the modification for the VST version of
VCVRack (because in a plugin, you have no choice), and so perhaps the
redesign might make it back into the mainline code. Given the lovely to use
GUI and the fantastic ecosystem, it's a little sad to see the internal code
suggest almost no understanding of how to write a realtime audio
application. Maybe Andrew had his reasons for the internal design - I
don't know. But it certainly makes it much more likely to have audio
glitches and to be incapable of operating at the lowest latencies. It works
well enough for me, however (and is a huge risk because I could spend hours
playing with it).
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
16 Jan
16 Jan
4:26 p.m.
Greetings,
On 12/01/2018 11:46 AM, Paul Davis wrote:
On Sat, Dec 1, 2018 at 9:27 AM Dave Phillips <dlphillips(a)woh.rr.com
<mailto:dlphillips@woh.rr.com>> wrote:
Greetings,
A little moody ambience from a work in progress exploring automatic
melodic generation with VCV Rack modules.
if you could:
(a) do the hour long version
No hour long recording, but here's the final version:
https://youtu.be/7f2RLTbbs9Y
For your enjoyment. Comments welcome, as always.
Edited and mixed with Ardour6. :)
Best,
dp
17 Jan
17 Jan
5:56 p.m.
On Wed, January 16, 2019 8:23 am, Dave Phillips wrote:
No hour long recording, but here's the final
version:
https://youtu.be/7f2RLTbbs9Y
Very nice. Do I understand correctly that this is essentially an
algorithmic style composition, in that once you setup the patching, the
modules are generating the control "voltages" that determine notes and
frequency, so it starts up and just runs without intervention?
Edited and mixed with Ardour6. :)
Nice to know that Paul hasn't broken basic functions with all his
re-arranging of the guts. :)
What type of editing do you actually do (assuming my understanding above
is correct)? Do you listen through and pull out interesting segments and
stitch
together? Or is it lighter weight than that?
--
Chris Caudle
10:19 p.m.
Hi Chris,
On 01/17/2019 10:56 AM, Chris Caudle wrote:
To be clear, that's Ardour6 very-beta, built from git sources.
On Wed, January 16, 2019 8:23 am, Dave Phillips
wrote:
Yes, that's pretty much the picture. The challenge is in setting up the
modules, i.e. their programming. While the music itself is the result of
more-or-less random procedures the sounds themselves are typically
closely designed (read: I spend a lot of time tuning the modules to an
expected behavior).
No hour long recording, but here's the final
version:
https://youtu.be/7f2RLTbbs9Y
Very nice. Do I understand correctly that this is
essentially an
algorithmic style composition, in that once you setup the patching, the
modules are generating the control "voltages" that determine notes and
frequency, so it starts up and just runs without intervention?
Edited and
mixed with Ardour6. :)
Nice to know that Paul hasn't broken basic functions
with all his
re-arranging of the guts. :) What type of editing do you actually do (assuming my
understanding above
is correct)? Do you listen through and pull out interesting segments and
stitch
together? Or is it lighter weight than that?
In 1625 the editing was straightforward, just selecting and merging
sections of two tracks. The synchronization was easy in this case, and
the only other process involved was a normalization pass. Incidentally,
things were done this way because Rack gets cranky when my patches hit a
certain load limit. I designed the patch for a single performance pass,
but it's too big a hit on my CPU (a 3.5 GHz 6-core AMD). Hence the
multiple takes. In sum, for this recording I added a little more than a
minute to the original by interpolating the "bridge" section.
Thanks for listening, Chris, and thank you for your inquiry as to how it
all got made.
Best regards,
dp
2140
days inactive
2187
days old
linux-audio-user@lists.linuxaudio.org
9 comments
5 participants
participants (5)
-
Chris Caudle -
Dan Ballance -
Dave Phillips -
Louigi Verona -
Paul Davis