Re: digi 003 compatible with ubuntu studio ?

2010-06-01 Thread Kenneth Koym 
Laurent, look at this and the link cited...

See Komputor @
http://ubuntuforums.org/showthread.php?p=9397472&posted=1#post9397472

*Jack Control** *
--

Success at last!! I think the problem was in my code (always trust the
code). Instead of setting my "memlock" to a specified number, I just changed
it to unlimited. Instead of having "nice" set to -19, I set it to -10.
I am not sure what I did with having it the other way before, but now Jack
message output is as follows:
p, li { white-space: pre-wrap; } 21:39:41.291 Patchbay deactivated.
21:39:41.315 Statistics reset.
21:39:41.467 ALSA connection graph change.
21:39:41.620 ALSA connection change.
21:40:33.661 Startup script...
21:40:33.662 artsshell -q terminate
sh: artsshell: not found
21:40:34.064 Startup script terminated with exit status=32512.
21:40:34.065 JACK is starting...
21:40:34.065 /usr/bin/jackd -dalsa -dhw:0,0 -r44100 -p1024 -n2
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and
others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Memory locking is unlimited - this is dangerous. You should probably alter
the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 1052490
21:40:34.096 JACK was started with PID=4640.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
21:40:36.191 Server configuration saved to "/home/komputor/.jackdrc".
21:40:36.193 Statistics reset.
21:40:36.705 Client activated.
21:40:36.707 JACK connection change.
21:40:36.713 JACK connection graph change.
#end of msg

And now Jack is showing RT up and running!




On Tue, Jun 1, 2010 at 5:02 PM, Andrew Euell wrote:

> Most Digidesign stuff is not supported by UbuntuStudio or the audio
> driver backends it uses.
> The audio back ends available in Linux are:
> FFADO -- for all firewire devices
> ALSA -- Advanced Linux Sound Architecture
> OSS -- Open Sound System (not installed by default)
>
> Digidesign is very very proprietary.
> The terms and agreement for their SDKs and documentation are very
> restrictive. You can check them out at this URL:
> http://www.avid.com/us/partners/audio-plugin-dev-program
>
> For a good list of compatible hardware check out these websites
> http://www.alsa-project.org/main/index.php/Matrix:Main
> http://www.ffado.org/?q=devicesupport/list
>
> Good Luck!
>
> On Tue, Jun 1, 2010 at 4:31 AM, laurent.bellegarde
>  wrote:
> >
> > Yes,
> >
> > i'm talking about this kind of sound card.
> >
> > Laurent
> >
> > Le 01/06/2010 05:02, Andrew a écrit :
> >>
> >> Digi soundcard? Are you talking about a digidesign soundcard? Like the
> >> kind that would be used with pthd?
> >> --Original Message--
> >> From: laurent.bellegarde
> >> Sender: ubuntu-studio-users-boun...@lists.ubuntu.com
> >> To: Ubuntu Studio Users Help and Discussion
> >> ReplyTo: Ubuntu Studio Users Help and Discussion
> >> Subject: digi 003 compatible with ubuntu studio ?
> >> Sent: May 31, 2010 5:19 PM
> >>
> >> Hi all,
> >>
> >> does anyone have news about compatibilty of digi 003 sound card with
> >> ubuntu studio ?
> >>
> >> it seems not to work.
> >>
> >> Thanks for answers,
> >>
> >> Laurent,
> >> lprod.org
> >>
> >>
> >
> >
>
>
>
> --
> Andrew Euell
> andyzweb [at] gmail [dot] com
>
> --
> Ubuntu-Studio-users mailing list
> Ubuntu-Studio-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
>


JackControlUbuStudio.doc
Description: MS-Word document
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: digi 003 compatible with ubuntu studio ?

2010-06-01 Thread Andrew Euell 
Most Digidesign stuff is not supported by UbuntuStudio or the audio
driver backends it uses.
The audio back ends available in Linux are:
FFADO -- for all firewire devices
ALSA -- Advanced Linux Sound Architecture
OSS -- Open Sound System (not installed by default)

Digidesign is very very proprietary.
The terms and agreement for their SDKs and documentation are very
restrictive. You can check them out at this URL:
http://www.avid.com/us/partners/audio-plugin-dev-program

For a good list of compatible hardware check out these websites
http://www.alsa-project.org/main/index.php/Matrix:Main
http://www.ffado.org/?q=devicesupport/list

Good Luck!

On Tue, Jun 1, 2010 at 4:31 AM, laurent.bellegarde
 wrote:
>
> Yes,
>
> i'm talking about this kind of sound card.
>
> Laurent
>
> Le 01/06/2010 05:02, Andrew a écrit :
>>
>> Digi soundcard? Are you talking about a digidesign soundcard? Like the
>> kind that would be used with pthd?
>> --Original Message--
>> From: laurent.bellegarde
>> Sender: ubuntu-studio-users-boun...@lists.ubuntu.com
>> To: Ubuntu Studio Users Help and Discussion
>> ReplyTo: Ubuntu Studio Users Help and Discussion
>> Subject: digi 003 compatible with ubuntu studio ?
>> Sent: May 31, 2010 5:19 PM
>>
>> Hi all,
>>
>> does anyone have news about compatibilty of digi 003 sound card with
>> ubuntu studio ?
>>
>> it seems not to work.
>>
>> Thanks for answers,
>>
>> Laurent,
>> lprod.org
>>
>>
>
>



-- 
Andrew Euell
andyzweb [at] gmail [dot] com

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: What's wrong with jack ?

2010-06-01 Thread Ricardo Lameiro 
Hello List,

Well, I have been reading the messages and there is a couple things that
people don't discuss or maybe don't know.

As of Ubuntu/UbuntuStudio 10.04, Jack is on the main repositories, this is a
huge improvement from the past. what does this mean?

If you do a fresh install, at install time, either alternate install or
ubiquity will prompt the user if they want to install and setup jack.
This means that the audio group and the settings are made on install time.
Another thing is that the settings now are at

/etc/security/limits.d/audio.conf

more info at https://help.ubuntu.com/community/UbuntuStudioPreparation

There is also
underway, some efforts to use Jack2, that is Dbus enabled. this will
enable"in theory" a good and seemingly interaction with PulseAudio. thing
aren't perfect, true, but sometimes we need to help each other to find the
better solutions, and also, try to give that solutions to the devs.
 The devs have families to, lives, they dont work for canonical,
ubuntustudio is a community project, and i think sometimes people forget
that, they just want it working without giving nothing back.
 I love this discussion, because at least some people want it to become
better and do exchange info. So i hope with all of our efforts as users, we
could help as much as we can the dev team. this is a win for all of us.

Ricardo Lameiro


2010/6/1 Hartmut Noack 

> Am 01.06.2010 14:08, schrieb Pablo Fernandez:
>
> > I find it neater the way it is now. As a user, I think the case
> > is similar to /etc/apt/sources.list and
> > /etc/apt/sources.list.d/someother.list
> > Particular configurations for particular goals are in a separate file.
> > Someone in the LAU list mentioned other examples and gave better reasons.
> > Anyway,  the user does not have to bother anymore with editing a system
> > file.
> >
> > More authoritative reasons are here:
> >   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507248
>
> Very interesting read - thanks for the link!
>
> This discussion shows quite clearly, where the overall problem with
> pro-audio on Linux lies: Those, who do the good work in building Distros
> like Debian do not know about pro-audio. If you tell them, that it is so
> demanding, they see a risk for their overall working system/security
> etc. And they are apalled to hear, that there are some crazy people out
> there, that want to have a 970MB-File locked into memory to be
> accessible with less then 10ms latency.
>
> This I understand but I do absolutely not understand, that these
> tech-people do not react like this:
>
> "Well quite interesting stuff, you crazies do there - let us do whatever
> possible and sane to make our system support such incredible features!"
>
> They act more like:
>
> "Comeon, do not bother us with such strange single-user
> niche-applications. Do this if you like but stay away from our great
> system settings that work so well for dozens of years now."
>
> > I like when Steve writes "common doesn't mean correct".
>
> I am not sure if he really knows, what he is talking about.
>
> The whole thing is, that jack, though it is a user-process, needs to be
> priviledged even more than the avarage root-process in order to work
> properly for the user. And this is not a bug or a flaw in the design of
> jack but simply a neccissity. This process needs to access data as fast
> as technically possible. Can the kernel-memory management guarranty
> that? Apparantly not. So you have 2 decisons:
>
> 1.) have a system set up conservatively for everyone, that runs normal
> Desktop-Apps and thats it. No RT-apps on Linux at least not for users
> with higher skills in tweaking system settings.
>
> 2.) find a sane way to let the user decide, what he/she likes to do with
> the system-setup.
>
> >
> > We will have to learn again  :)
>
> Everybody needs to learn every day.
>
> >
> >>
> >> Plus, as you mention yourself later on, the script must set up group
> >> audio as well, this is a no-brainer and I really do not know, why the
> >> packagers do not implement that.
> >>
> >
> > I didn't say exactly so. I think a package script must not deal with
> users
> > and groups.
> > But the distro should do it, imho.
>
> You mean: group audio should be set up in the initial install and the
> first user should be in that group?
> Why?
>
> >
> >>
> >>> For the rest, qjackctl launches pasuspender so pulseaudio is (almost)
> out
> >> of
> >>> the way.
> >>
> >> I recommend that. It works very much OK for me.
> >>
> >>> Afaik, a cleaner approach than pasuspender or the rm you suggest in
> >> getting
> >>> rid of pulseaudio is the following:
> >>>
> >>> qjackctl -->   Options tab, execute script on startup:
> >>> pulseaudio -k
> >>>
> >>> (this kills pulseaudio) (artsshell sounds like jurasic)
> >>>
> >>> However, pulseaudio will respawn automatically if you don't do the
> >>> following:
> >>>
> >>> $ sudo edit /etc/pulse/client.conf
> >>>
> >>> Ch

Re: What's wrong with jack ?

2010-06-01 Thread Hartmut Noack 
Am 01.06.2010 14:08, schrieb Pablo Fernandez:

> I find it neater the way it is now. As a user, I think the case
> is similar to /etc/apt/sources.list and
> /etc/apt/sources.list.d/someother.list
> Particular configurations for particular goals are in a separate file.
> Someone in the LAU list mentioned other examples and gave better reasons.
> Anyway,  the user does not have to bother anymore with editing a system
> file.
>
> More authoritative reasons are here:
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507248

Very interesting read - thanks for the link!

This discussion shows quite clearly, where the overall problem with 
pro-audio on Linux lies: Those, who do the good work in building Distros 
like Debian do not know about pro-audio. If you tell them, that it is so 
demanding, they see a risk for their overall working system/security 
etc. And they are apalled to hear, that there are some crazy people out 
there, that want to have a 970MB-File locked into memory to be 
accessible with less then 10ms latency.

This I understand but I do absolutely not understand, that these 
tech-people do not react like this:

"Well quite interesting stuff, you crazies do there - let us do whatever 
possible and sane to make our system support such incredible features!"

They act more like:

"Comeon, do not bother us with such strange single-user 
niche-applications. Do this if you like but stay away from our great 
system settings that work so well for dozens of years now."

> I like when Steve writes "common doesn't mean correct".

I am not sure if he really knows, what he is talking about.

The whole thing is, that jack, though it is a user-process, needs to be 
priviledged even more than the avarage root-process in order to work 
properly for the user. And this is not a bug or a flaw in the design of 
jack but simply a neccissity. This process needs to access data as fast 
as technically possible. Can the kernel-memory management guarranty 
that? Apparantly not. So you have 2 decisons:

1.) have a system set up conservatively for everyone, that runs normal 
Desktop-Apps and thats it. No RT-apps on Linux at least not for users 
with higher skills in tweaking system settings.

2.) find a sane way to let the user decide, what he/she likes to do with 
the system-setup.

>
> We will have to learn again  :)

Everybody needs to learn every day.

>
>>
>> Plus, as you mention yourself later on, the script must set up group
>> audio as well, this is a no-brainer and I really do not know, why the
>> packagers do not implement that.
>>
>
> I didn't say exactly so. I think a package script must not deal with users
> and groups.
> But the distro should do it, imho.

You mean: group audio should be set up in the initial install and the 
first user should be in that group?
Why?

>
>>
>>> For the rest, qjackctl launches pasuspender so pulseaudio is (almost) out
>> of
>>> the way.
>>
>> I recommend that. It works very much OK for me.
>>
>>> Afaik, a cleaner approach than pasuspender or the rm you suggest in
>> getting
>>> rid of pulseaudio is the following:
>>>
>>> qjackctl -->   Options tab, execute script on startup:
>>> pulseaudio -k
>>>
>>> (this kills pulseaudio) (artsshell sounds like jurasic)
>>>
>>> However, pulseaudio will respawn automatically if you don't do the
>>> following:
>>>
>>> $ sudo edit /etc/pulse/client.conf
>>>
>>> Change the line:
>>> ; autospawn = yes
>>> to:
>>> autospawn = no
>>>
>>> If you wish to start pulseaudio, once the jack session is finished:
>>>
>>> $ pulseaudio --start
>>
>> This methods I tried in Open Suse 11.2 and it broke my system so
>> globally and totally that I abandoned the OpenSuse-Installation. So I
>> really recommend to check out, if pasuspender does the trick
>
>
> In my case, pasuspender does the trick but I don't want a pulseaudio daemon
> running at all.
> https://help.ubuntu.com/community/UbuntuStudioPreparation#Pulse%20Audio
> recommends creating a *~/.pulse/client.conf*  with "autospawn = no" (instead
> of editing the system wide /etc/pulse/client.conf as I suggested) and then
> put "pulseaudio -k" as a "Startup Application".


The latter looks promising. If I find the time, Ill try it just for 
curiosity ;-)

best regs

HZN

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: What's wrong with jack ?

2010-06-01 Thread Pablo Fernandez 
 So the user should have the

> option to disable it completely - the same as he/she has the option not
> to use nautilus or apache.
> And this should be possible *without* deinstalling it.
>

I agree


>
> Again: is there ANY sane reason, that this script does not edit
> /etc/security/limits.conf?
>
> The script works but it breaks standards, that used to work like a charm
> for years now in the Linux audio realm. Asking G "how to setup linux for
> jack" turns out dozens of tutorials how to set up limits.conf. All of
> those work perfectly well on any Linux.
>

I find it neater the way it is now. As a user, I think the case
is similar to /etc/apt/sources.list and
/etc/apt/sources.list.d/someother.list
Particular configurations for particular goals are in a separate file.
Someone in the LAU list mentioned other examples and gave better reasons.
Anyway,  the user does not have to bother anymore with editing a system
file.

More authoritative reasons are here:
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507248
I like when Steve writes "common doesn't mean correct".

We will have to learn again  :)


>
> Plus, as you mention yourself later on, the script must set up group
> audio as well, this is a no-brainer and I really do not know, why the
> packagers do not implement that.
>

I didn't say exactly so. I think a package script must not deal with users
and groups.
But the distro should do it, imho.


>
> > For the rest, qjackctl launches pasuspender so pulseaudio is (almost) out
> of
> > the way.
>
> I recommend that. It works very much OK for me.
>
> > Afaik, a cleaner approach than pasuspender or the rm you suggest in
> getting
> > rid of pulseaudio is the following:
> >
> > qjackctl -->  Options tab, execute script on startup:
> > pulseaudio -k
> >
> > (this kills pulseaudio) (artsshell sounds like jurasic)
> >
> > However, pulseaudio will respawn automatically if you don't do the
> > following:
> >
> > $ sudo edit /etc/pulse/client.conf
> >
> > Change the line:
> > ; autospawn = yes
> > to:
> > autospawn = no
> >
> > If you wish to start pulseaudio, once the jack session is finished:
> >
> > $ pulseaudio --start
>
> This methods I tried in Open Suse 11.2 and it broke my system so
> globally and totally that I abandoned the OpenSuse-Installation. So I
> really recommend to check out, if pasuspender does the trick


In my case, pasuspender does the trick but I don't want a pulseaudio daemon
running at all.
https://help.ubuntu.com/community/UbuntuStudioPreparation#Pulse%20Audio
recommends creating a *~/.pulse/client.conf*  with "autospawn = no" (instead
of editing the system wide /etc/pulse/client.conf as I suggested) and then
put "pulseaudio -k" as a "Startup Application".

Cheers! Pablo
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Someone know this bug with ardour2?

2010-06-01 Thread Thomas Orgis 
Hi,

I reported that one recently, perhaps someone here remembers something like 
that, too? It would be so nice if recording on Linux would be stable:-/

http://tracker.ardour.org/view.php?id=3213

Quote:

I am typing this out of my memory, as the affected box is in the studio, not 
here. But better a bad bug report than no one:-/

This is an install of ubuntu studio 10.04, with ardour 2.8.6, and jackd 
0.118+svn, I presume (I used jack2 before on another install, but I don't 
remember hacking around in the ubuntu one to get jack2). Ardour quite often is 
disconnected from jack (for whatever reason, usually _not_ during recording) 
and the real bummer is that it fails to reconnect the channels/tracks to jack 
ports.

It can connect to jack, but the client name changes from ardour to ardour-01 
... ardour then tries to connect ports for the non-existent client "ardour". 
That doesn't work, of course. I have to exit ardour and start again to get the 
connections working. This is very reproducable once you got ardour disconnected 
by some other mischief (I'd need to try if this happens on user requested 
disconnect/reconnect, but I doubt it).

This is is also quite frightening since ardour promises only proper saving of 
projects when the jack connection is right ... and I had to reconnect things 
after recovering from the ardour-01 confusion. This gives us (ardour2/Linux and 
me) really bad press when we (the band) are in a recording session and my band 
waits where I have to fiddle around with that strange Linux thing:-/

Question is now: Who is to blame for the client name mismatch? Ist it ardour, 
is it jack? Should ardour verify which name it gets assigned and not try to 
connect ports for someone else (named "ardour" where ardour is named 
"ardour-01")? In any case, I hope this one is resolvable...


Alrighty then,

Thomas.


signature.asc
Description: PGP signature
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: What's wrong with jack ?

2010-06-01 Thread Hartmut Noack 
Am 31.05.2010 14:40, schrieb Pablo Fernandez:
> I agree that jack should work out of the box in ubuntustudio but I don't
> agree that pulseaudio should not be the default audio system.
>
> In many cases, jack does not suit users well but pulseaudio is fine.

PA has the potential to solve a lot of old problems in Linux Desktop 
audio for good but it is not there yet. So the user should have the 
option to disable it completely - the same as he/she has the option not 
to use nautilus or apache.
And this should be possible *without* deinstalling it.

> As I see it, Jack is a must  for audio production, but not for audio in
> general. For example, if you have a surround system like in a home cinema,
> pulseaudio is the audio system that just works. Not jack.
>
>
>
>> Am I supposed to *"rm /usr/bin/pulseaudio"* to make jack work ?

This may or may not work I suppose it will not for it canwill break many 
other things on the desktop, crashing apps etc.

>> just that Ubuntu Studio is not ready to be used for music production in a
>> real sense ? = it is just for testing and experimenting
>>
>
> US is almost there. Imho, US should add the first user to the audio group
> automatically so that jackd starts out of the box from qjackctl. jackd post
> inst script (in lucid) gives the users in the audio group the privileges
> that jackd needs.

Again: is there ANY sane reason, that this script does not edit 
/etc/security/limits.conf?

The script works but it breaks standards, that used to work like a charm 
for years now in the Linux audio realm. Asking G "how to setup linux for 
jack" turns out dozens of tutorials how to set up limits.conf. All of 
those work perfectly well on any Linux.

Plus, as you mention yourself later on, the script must set up group 
audio as well, this is a no-brainer and I really do not know, why the 
packagers do not implement that.

> For the rest, qjackctl launches pasuspender so pulseaudio is (almost) out of
> the way.

I recommend that. It works very much OK for me.

> Afaik, a cleaner approach than pasuspender or the rm you suggest in getting
> rid of pulseaudio is the following:
>
> qjackctl -->  Options tab, execute script on startup:
> pulseaudio -k
>
> (this kills pulseaudio) (artsshell sounds like jurasic)
>
> However, pulseaudio will respawn automatically if you don't do the
> following:
>
> $ sudo edit /etc/pulse/client.conf
>
> Change the line:
> ; autospawn = yes
> to:
> autospawn = no
>
> If you wish to start pulseaudio, once the jack session is finished:
>
> $ pulseaudio --start

This methods I tried in Open Suse 11.2 and it broke my system so 
globally and totally that I abandoned the OpenSuse-Installation. So I 
really recommend to check out, if pasuspender does the trick or try a 
system, that is 100% geared towards audio-power use such as pure:dyne or 
AVLinux. Both outperform anything else in audio today but they are not 
as nice a desktop as Ubuntu and they do not have such a big community 
and most of all: they lack the near-perfectly integrated big 
repositories Ubuntu has.


Best regards,
HZN/Berlin



-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

Re: digi 003 compatible with ubuntu studio ?

2010-06-01 Thread laurent.bellegarde 

Yes,

i'm talking about this kind of sound card.

Laurent

Le 01/06/2010 05:02, Andrew a écrit :
> Digi soundcard? Are you talking about a digidesign soundcard? Like the kind 
> that would be used with pthd?
> --Original Message--
> From: laurent.bellegarde
> Sender: ubuntu-studio-users-boun...@lists.ubuntu.com
> To: Ubuntu Studio Users Help and Discussion
> ReplyTo: Ubuntu Studio Users Help and Discussion
> Subject: digi 003 compatible with ubuntu studio ?
> Sent: May 31, 2010 5:19 PM
>
> Hi all,
>
> does anyone have news about compatibilty of digi 003 sound card with
> ubuntu studio ?
>
> it seems not to work.
>
> Thanks for answers,
>
> Laurent,
> lprod.org
>
>


-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users