[PlanetCCRMA] PlanetCCRMA Digest, Vol 84, Issue 1

[elecronicq]

On Mon, 02 Mar 2015 12:00:04 -0800
planetccrma-request at ccrma.Stanford.EDU wrote:

> Send PlanetCCRMA mailing list submissions to
> 	planetccrma at ccrma.stanford.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> or, via email, send a message with subject or body 'help' to
> 	planetccrma-request at ccrma.stanford.edu
> 
> You can reach the person managing the list at
> 	planetccrma-owner at ccrma.stanford.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of PlanetCCRMA digest..."
> 
> 
> Today's Topics:
> 
>    1. external soundcard future (Oded Ben-Tal)
>    2. fedora 20 (elecronicq qcinorcele)
>    3. Re: fedora 20 (Samuel Sieb)
>    4. Re: fedora 20 (Donald Steven)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 2 Mar 2015 00:47:48 -0800
> From: "Oded Ben-Tal" <oded at ccrma.Stanford.EDU>
> Subject: [PlanetCCRMA] external soundcard future
> To: planetccrma at ccrma.Stanford.EDU
> Message-ID: <20150302084011.M32674 at ccrma.stanford.edu>
> Content-Type: text/plain;	charset=iso-8859-1
> 
> Dear all,
> I am wondering if anyone knows what the future of good soundcards looks like. At 
> the moment I rely on expresscard connectors (RME + an old focusrite using 
> firewire). I started realising that most new laptops don't have expresscard 
> slots any longer so this option seems to be closing. Does anyone have any 
> experience getting sound working through a USB<-expresscard adapter? Or should I 
> hurry up and buy a new laptop (my current one is 7 YO) before I ran out of 
> options? Would new soundcards being developed use USB3? Or? 
>  thanks
> Oded
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 2 Mar 2015 20:41:15 +0200
> From: elecronicq qcinorcele <elecronicq at gmail.com>
> Subject: [PlanetCCRMA] fedora 20
> To: planetccrma at ccrma.Stanford.EDU
> Message-ID:
> 	<CACsynHUoHLZF1osTJgk+P421ZbiqwiCQkBqJHqn3Wuw+X1Gtxg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> hello,
> 
> i just installed fedora 20 lxde on my laptop, following an install of the
> planetccrma repository but now i arrived at a point where i don't
> understand what is going on with my audio setup entrails---is it pulse
> audio, alsa or jack server that are controlling the thing?
> thank you in advance
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://ccrma-mail.stanford.edu/pipermail/planetccrma/attachments/20150302/2aa31954/attachment-0001.html 
> 
> ------------------------------
> 
> Message: 3
> Date: Mon, 02 Mar 2015 11:01:39 -0800
> From: Samuel Sieb <samuel at sieb.net>
> Subject: Re: [PlanetCCRMA] fedora 20
> To: planetccrma at ccrma.Stanford.EDU
> Message-ID: <54F4B393.3040706 at sieb.net>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 03/02/2015 10:41 AM, elecronicq qcinorcele wrote:
> > i just installed fedora 20 lxde on my laptop, following an install of
> > the planetccrma repository but now i arrived at a point where i don't
> > understand what is going on with my audio setup entrails---is it pulse
> > audio, alsa or jack server that are controlling the thing?
> > thank you in advance
> >
> ALSA is the kernel layer (and a wrapper library).  By default, you will 
> be running PulseAudio as the audio system, but if you install Jack, you 
> can use that.  It should be able to take over control from PulseAudio 
> when it starts up.
> 
> As an aside, why F20?  F21 has been out for a while, F22 is already 
> approaching Alpha.
> 
> 

i went to f20 because of the ccrma repo's. i noticed that the last (work in progress) was the version 20 so i went for that...
also noticed that the pd-extended is buggy... doesnt load pdp or gem libs and doesnt respond to the quit program command.

regards
joão

> 
> ------------------------------
> 
> Message: 4
> Date: Mon, 02 Mar 2015 14:43:30 -0500
> From: Donald Steven <t6sn7gt at aim.com>
> Subject: Re: [PlanetCCRMA] fedora 20
> To: Samuel Sieb <samuel at sieb.net>, planetccrma at ccrma.Stanford.EDU
> Message-ID: <54F4BD62.2050607 at aim.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
> Some cards (my RME HDSP 9632, for example) don't 'like' pulseaudio. I've 
> had success doing the following:
> 
> ==========
> 
> 1. Remove:
> 
> alsa-plugins-pulseaudio
> xine-lib-pulseaudio
> xmms-pulse
> 
> 2. If you can, prevent pulseaudio from starting using open 
> gnome-session-properties.
> 
> 3. Create a file called client.conf containing the lines:
> 
>    autospawn = no
>    daemon-binary = /bin/true
> 
> and place this file in ~/.pulse
> 
> 4.  Reboot and, hopefully,  no more pulseaudio.
> 
> ==========
> 
> Don
> 
> On 03/02/2015 02:01 PM, Samuel Sieb wrote:
> > On 03/02/2015 10:41 AM, elecronicq qcinorcele wrote:
> >> i just installed fedora 20 lxde on my laptop, following an install of
> >> the planetccrma repository but now i arrived at a point where i don't
> >> understand what is going on with my audio setup entrails---is it pulse
> >> audio, alsa or jack server that are controlling the thing?
> >> thank you in advance
> >>
> > ALSA is the kernel layer (and a wrapper library).  By default, you will
> > be running PulseAudio as the audio system, but if you install Jack, you
> > can use that.  It should be able to take over control from PulseAudio
> > when it starts up.
> >
> > As an aside, why F20?  F21 has been out for a while, F22 is already
> > approaching Alpha.
> >
> > _______________________________________________
> > PlanetCCRMA mailing list
> > PlanetCCRMA at ccrma.stanford.edu
> > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> >
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> 
> 
> End of PlanetCCRMA Digest, Vol 84, Issue 1
> ******************************************
> 


-- 
elecronicq <elecronicq at gmail.com>