Danni Coy wrote:
> hitting TAB once should take you to keyboard mode (testing with 0.6
> from xubuntu here)... however one of the first few times I tried it -
> it did lock up and not allow keyboard input at all
> if escape does not close the application then this may be the case
escape doesn't close the app. Nothing doesn't close the app, even ctr-c
in terminal not. I have to close the terminal to shut it down... So
there is a problem maybe...
\r
>
> On Thu, Aug 6, 2009 at 10:04 PM, Grammostola Rosea
> <rosea.grammostola(a)gmail.com <mailto:rosea.grammostola@gmail.com>> wrote:
>
> Norval Watson wrote:
> > ----- Original Message ----
> >
> >
> >> From: Grammostola Rosea <rosea.grammostola(a)gmail.com
> <mailto:rosea.grammostola@gmail.com>>
> >> Norval Watson wrote:k
> >>>
> >>>
> >>>
> >>>> From: Grammostola Rosea
> >>>>
> >>>> Danni Coy wrote:
> >>>>
> >>>>
> >>>>> You need to hook up the inputs of Freewheeling before it
> does anything
> >>>>> useful...
> >>>>> Patchage is probably the easiest tool for this. Connect the
> inputs to
> >>>>> what you want to record and the outputs to the outputs on your
> >>>>> soundcard. From here the qwerty keyboard is used to
> record,trigger and
> >>>>> stop playing loops.
> >>>>> Each key is a loop.
> >>>>> 1st press starts recording
> >>>>> 2nd press stops recording and starts playback
> >>>>> 3rd+ toggles playback.
> >>>>>
> >>>>> space + key clears loop
> >>>>> alt + space clears all loops
> >>>>>
> >>>>> hope that helps you get started
> >>>>>
> >>>>>
> >>>> Thanks. I have the connections, but pressing a key doesn't do
> anything.
> >>>> I think the settings for the pc keyboard etc are not right yet...
> >>>>
> >>>> \r
> >>>>
> >>>>
> >>> If you press TAB does the Freewheeling window cycle through
> representations of
> >>>
> >> the QWERTY keyboard, an octave on a piano keyboard, a dance mat
> etc?
> >>
> >>> (NB: the Freewheeling window has to be the active window)
> >>> Norv
> >>>
> >>>
> >>>
> >> no... it doesn't do that.
> >>
> >> \r
> >>
> > OK that means the QWERT is not talking to Fweelin at all.
> > What version of Freewheeling are you using?
> > (I'm not on my Fweelin system right now but I can check it out
> tomorrow.)
> > N
> >
> >
> Right. I'm using 0.6 on Debian testing. Like I said, fweelin has a new
> configuration system, which I don't understand and can't find good
> info
> to handle it right myself.
> Thanks for your help.
>
> \r
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> <mailto:Linux-audio-user@lists.linuxaudio.org>
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
>
<blockquote>Message: 19
Date: Tue, 04 Aug 2009 21:36:02 -1000
From: david <gnome(a)hawaii.rr.com>
Subject: Re: [LAU] resubmitting questions from last week
To: linuxaudio <linux-audio-user(a)lists.linuxaudio.org>
Message-ID: <4A793662.2030501(a)hawaii.rr.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Perhaps you're so far out on the leading edge of audio kernel
configuration that you're pursuing things nobody else is doing yet?
Document well what you do, you may be blazing the trail!
Paul</blockquote>
Appreciate the compliment, but assure you that am not intending anything even close to that at all. Rather, am simply and humbly asking where to plug in the values mentioned last week or so by several people about the migration, posixcputmr and the other things.
Continued thanks in advance and process of this
On 08/06/2009 03:16 AM, David Robillard wrote:
> On Wed, 2009-08-05 at 21:53 +0200, Jens M Andreasen wrote:
>
>> > From TFA:
>>
>> --8<----------------------------------
>> Go to System->Preferences->Sound, click on the Devices tab, and check
>> out the pulldown menu next to ‘Sound Events’ at the top of the panel.
>> You will see various acronyms, possibly including cryptic-looking
>> technologies like OSS, ESD, ALSA, JACK, and Pulse Audio. These acronyms
>> represent a byzantine tangle of conflicting technologies that over time,
>> and due to political reasons or backwards compatibility, have ended up
>> cohabiting with one another. ‘Frankenstein’ might be an accurate
>> metaphor here.
>>
>>
>> Thankfully, there is a simpler way, which is the combination of ALSA [a
>> high-performance, kernel-level audio and MIDI system] and JACK [a system
>> for creating low-latency audio, MIDI, and sync connections between
>> applications and computers]. The battle-scarred among us have learned to
>> ignore all the other audio cruft bolted on to Ubuntu and just use ALSA
>> and JACK. One can think of the ALSA/JACK stack, the heart of most pro
>> Linux studios, as the Core Audio of Linux and in my opinion Jack should
>> be the first thing installed on any musicians laptop. I’d go so far as
>> to suggest placing it in the Startup Applications so it’s always
>> running.
>> -------------------8<--------------------------------------------------
>>
>
> IMO without a ton of effort Jack could, and should, be turned into a
> viable default installation audio system (or the bottom layer of such a
> system, at least). The desktop guys certainly aren't ever going to get
> it right.
>
> The above problem is a very real one as far as people's perception of
> GNU/Linux as an audio system. What a mess. We can do better.
>
>
AFAICT it's like 95% there already as far as the average user is
concerned. So the desktop guys you are referring to have got it and are
way ahead of anyone else in this respect.
Pulse is ubiquitous now. Jack was never intended to be the default audio
system for desktop use.
Let's just fix the interaction between pulse and jack and be done with it.
It's harmful to suggest that it things are less than they are as it just
makes people who have already invested a lot of effort get annoyed and
turned off.
Patrick Shirkey
Boost Hardware Ltd
> -dr
>
>
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
>
Hello everyone!
A quick one: What is the best and fastest way to make an exact copy of an
audio-cd only using the console and the IDE driver for CD. Special importance
here of course: the gaps or non-gaps.
Please I need some quick help here! Anything is appreciated!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
Sorry, this didn't get to the list... Didn't see that.
Hi Nick!
Thanks for that one. But I always tought that dd only works for data-disks
(iso9660)? Anyone else, any opinion?
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
Danni Coy wrote:
> That does appear to be the problem
> does it do this everytime you start the app?
>
> Also what kernel are you running (is it rt)?
Yeah everytime, RT kernel, no problems with other pro audio apps.
No errors or something...
\r
>
> On Thu, Aug 6, 2009 at 10:25 PM, Grammostola Rosea
> <rosea.grammostola(a)gmail.com <mailto:rosea.grammostola@gmail.com>> wrote:
>
> Danni Coy wrote:
> > hitting TAB once should take you to keyboard mode (testing with 0.6
> > from xubuntu here)... however one of the first few times I tried
> it -
> > it did lock up and not allow keyboard input at all
> > if escape does not close the application then this may be the case
>
> escape doesn't close the app. Nothing doesn't close the app, even
> ctr-c
> in terminal not. I have to close the terminal to shut it down... So
> there is a problem maybe...
> \r
>
>
> >
> > On Thu, Aug 6, 2009 at 10:04 PM, Grammostola Rosea
> > <rosea.grammostola(a)gmail.com
> <mailto:rosea.grammostola@gmail.com>
> <mailto:rosea.grammostola@gmail.com
> <mailto:rosea.grammostola@gmail.com>>> wrote:
> >
> > Norval Watson wrote:
> > > ----- Original Message ----
> > >
> > >
> > >> From: Grammostola Rosea <rosea.grammostola(a)gmail.com
> <mailto:rosea.grammostola@gmail.com>
> > <mailto:rosea.grammostola@gmail.com
> <mailto:rosea.grammostola@gmail.com>>>
> > >> Norval Watson wrote:k
> > >>>
> > >>>
> > >>>
> > >>>> From: Grammostola Rosea
> > >>>>
> > >>>> Danni Coy wrote:
> > >>>>
> > >>>>
> > >>>>> You need to hook up the inputs of Freewheeling before it
> > does anything
> > >>>>> useful...
> > >>>>> Patchage is probably the easiest tool for this.
> Connect the
> > inputs to
> > >>>>> what you want to record and the outputs to the outputs
> on your
> > >>>>> soundcard. From here the qwerty keyboard is used to
> > record,trigger and
> > >>>>> stop playing loops.
> > >>>>> Each key is a loop.
> > >>>>> 1st press starts recording
> > >>>>> 2nd press stops recording and starts playback
> > >>>>> 3rd+ toggles playback.
> > >>>>>
> > >>>>> space + key clears loop
> > >>>>> alt + space clears all loops
> > >>>>>
> > >>>>> hope that helps you get started
> > >>>>>
> > >>>>>
> > >>>> Thanks. I have the connections, but pressing a key
> doesn't do
> > anything.
> > >>>> I think the settings for the pc keyboard etc are not
> right yet...
> > >>>>
> > >>>> \r
> > >>>>
> > >>>>
> > >>> If you press TAB does the Freewheeling window cycle through
> > representations of
> > >>>
> > >> the QWERTY keyboard, an octave on a piano keyboard, a
> dance mat
> > etc?
> > >>
> > >>> (NB: the Freewheeling window has to be the active window)
> > >>> Norv
> > >>>
> > >>>
> > >>>
> > >> no... it doesn't do that.
> > >>
> > >> \r
> > >>
> > > OK that means the QWERT is not talking to Fweelin at all.
> > > What version of Freewheeling are you using?
> > > (I'm not on my Fweelin system right now but I can check it out
> > tomorrow.)
> > > N
> > >
> > >
> > Right. I'm using 0.6 on Debian testing. Like I said, fweelin
> has a new
> > configuration system, which I don't understand and can't
> find good
> > info
> > to handle it right myself.
> > Thanks for your help.
> >
> > \r
> >
> > _______________________________________________
> > Linux-audio-user mailing list
> > Linux-audio-user(a)lists.linuxaudio.org
> <mailto:Linux-audio-user@lists.linuxaudio.org>
> > <mailto:Linux-audio-user@lists.linuxaudio.org
> <mailto:Linux-audio-user@lists.linuxaudio.org>>
> > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
> >
> >
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> <mailto:Linux-audio-user@lists.linuxaudio.org>
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
>
Hi,
I want to play a bit with Freewheeling (0.6). But how to use it with an
qwerty keyboard? There is a note somewhere that I should switch laptop
mode off or something, but it is not clear at all how and where actually.
Help needed here...
thanks in advance,
\r
Danni Coy wrote:
> You need to hook up the inputs of Freewheeling before it does anything
> useful...
> Patchage is probably the easiest tool for this. Connect the inputs to
> what you want to record and the outputs to the outputs on your
> soundcard. From here the qwerty keyboard is used to record,trigger and
> stop playing loops.
> Each key is a loop.
> 1st press starts recording
> 2nd press stops recording and starts playback
> 3rd+ toggles playback.
>
> space + key clears loop
> alt + space clears all loops
>
> hope that helps you get started
Thanks. I have the connections, but pressing a key doesn't do anything.
I think the settings for the pc keyboard etc are not right yet...
\r
