Re: [ubuntu-studio-users] weird behaviour firewire

2015-08-13 Thread bart deruyter
I already had jackdbus disabled in my search for a solution, was one of the
steps I took. And I filed a bug report, describing behavior with
pulseaudio-module-jack, and without it, in case I'm not alone with this
issue. In Ubuntu 14.10 this wasn't an issue either for me and I kept it in
place too. Luckily, using two sound cards, internal for regular audio, and
audiofire12 for real audio work goes just fine :-).

grtz,

Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2015-08-13 20:18 GMT+02:00 Mike Holstein :

>
>
> On Thu, Aug 13, 2015 at 2:04 PM, bart deruyter 
> wrote:
>
>> Hi all,
>>
>> I think I have found the solution. I still have to test it more in depth,
>> but so far it seems to have worked. The culprit probably was
>> pulseaudio-module-jack.
>> I uninstalled it and now it seems to work just fine.
>>
>> So, if anyone else might have this problem of jackd not wanting to start
>> again after having exited in the same session, and doesn't need it the
>> pulse-jack sink: remove pulseaudio-module-jack.
>>
>>
> i typically leave it in place, in case, for some reason, i would need it,
> in the future, but, i just disable the dbus in the qjackctl settings.. dbus
> tickbox in misc settings, iirc...
>
>
>
>> grtz,
>>
>> Bart
>>
>> http://www.bartart3d.be/
>> On Twitter 
>> On Identi.ca 
>> On Google+ 
>>
>> 2015-08-13 18:23 GMT+02:00 Mike Holstein :
>>
>>>
>>>
>>> On Thu, Aug 13, 2015 at 12:01 PM, bart deruyter >> > wrote:
>>>
 Turning back to the original thread I started:

 @ Mike Holstein:

 my mistake I set the examples in the wrong order, usually I do first
 exit jack, don't hammer on it.* It is not the biggest issue.* Any way
 it happens, exiting jack and trying to start it again, even when I keep the
 device on, I don't get jack working anymore.

 And it's not my first day using ubuntustudio, I'm not a beginner, using
 it sort of hapily for 7 years now, so I do have some experience. Until now
 I never had any problem with exiting jack to start it again later on.
 Secondly I do use the internet to communicate too, not just to browse
 around a little, talking to other people who make music, browsing for
 samples, etc...

 I do not intend to invest in a second machine and I do expect my
 computer to handle audio work and some simple tasks as typing a letter of
 browsing the internet. I simply don't have the funds for it and I don't
 want to scale the philosophy of "for each task a different program" up to
 "for each task a different computer".

 greetz,


>>> at this point, for me, personally, i would go forward. i would test in
>>> 15.10, and see if it works there. file a bug, or join a bug, and move on..
>>> otherwise, im not talking about a requiring a physical machine per task. im
>>> just suggesting, potentially having a different installation on the same
>>> machine, where, one is catering to desktop use, and the other is catering
>>> to audio production. not that this is a key factor. no doubt, it *should*
>>> ideally be working to do what you are wanting to do. but, i find, dealing
>>> with firewire to be especially challenging.
>>>
>>> cheers, and good luck!
>>>
>>>
>>>
>>>
 Bart

 http://www.bartart3d.be/
 On Twitter 
 On Identi.ca 
 On Google+ 

 2015-08-13 17:46 GMT+02:00 bart deruyter :

> Hi all,
>
> as an idea to get jackdbus stopping and then startup again I used as
> Edward Schrober suggested :
>
> sudo kill -9 4327 (the number is the pid of jackdbus)
>
> but to no avail, jack won't start again. Now I'm on xfce, default for
> ubuntustudio. So it is not gnome related, but a more general configuration
> issue I think.
>
> grtz,
>
> Bart
>
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
> 2015-08-13 9:00 GMT+02:00 bart deruyter :
>
>> Hi all,
>>
>> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
>> kxstudio installed through software sources.
>>
>> My soundcard is an Echo Audiofire 12, connected with firewire.
>>
>> Since 15.04 when I start jack it works fine as long as I don't run
>> any other application which requires sound, before starting jack.
>>
>> it is consistently going wrong when I for example start chrome, exit
>> chrome and try to start jack, using claudia, or qjackctl

Re: [ubuntu-studio-users] weird behaviour firewire

2015-08-13 Thread Mike Holstein
On Thu, Aug 13, 2015 at 2:04 PM, bart deruyter 
wrote:

> Hi all,
>
> I think I have found the solution. I still have to test it more in depth,
> but so far it seems to have worked. The culprit probably was
> pulseaudio-module-jack.
> I uninstalled it and now it seems to work just fine.
>
> So, if anyone else might have this problem of jackd not wanting to start
> again after having exited in the same session, and doesn't need it the
> pulse-jack sink: remove pulseaudio-module-jack.
>
>
i typically leave it in place, in case, for some reason, i would need it,
in the future, but, i just disable the dbus in the qjackctl settings.. dbus
tickbox in misc settings, iirc...



> grtz,
>
> Bart
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
> 2015-08-13 18:23 GMT+02:00 Mike Holstein :
>
>>
>>
>> On Thu, Aug 13, 2015 at 12:01 PM, bart deruyter 
>> wrote:
>>
>>> Turning back to the original thread I started:
>>>
>>> @ Mike Holstein:
>>>
>>> my mistake I set the examples in the wrong order, usually I do first
>>> exit jack, don't hammer on it.* It is not the biggest issue.* Any way
>>> it happens, exiting jack and trying to start it again, even when I keep the
>>> device on, I don't get jack working anymore.
>>>
>>> And it's not my first day using ubuntustudio, I'm not a beginner, using
>>> it sort of hapily for 7 years now, so I do have some experience. Until now
>>> I never had any problem with exiting jack to start it again later on.
>>> Secondly I do use the internet to communicate too, not just to browse
>>> around a little, talking to other people who make music, browsing for
>>> samples, etc...
>>>
>>> I do not intend to invest in a second machine and I do expect my
>>> computer to handle audio work and some simple tasks as typing a letter of
>>> browsing the internet. I simply don't have the funds for it and I don't
>>> want to scale the philosophy of "for each task a different program" up to
>>> "for each task a different computer".
>>>
>>> greetz,
>>>
>>>
>> at this point, for me, personally, i would go forward. i would test in
>> 15.10, and see if it works there. file a bug, or join a bug, and move on..
>> otherwise, im not talking about a requiring a physical machine per task. im
>> just suggesting, potentially having a different installation on the same
>> machine, where, one is catering to desktop use, and the other is catering
>> to audio production. not that this is a key factor. no doubt, it *should*
>> ideally be working to do what you are wanting to do. but, i find, dealing
>> with firewire to be especially challenging.
>>
>> cheers, and good luck!
>>
>>
>>
>>
>>> Bart
>>>
>>> http://www.bartart3d.be/
>>> On Twitter 
>>> On Identi.ca 
>>> On Google+ 
>>>
>>> 2015-08-13 17:46 GMT+02:00 bart deruyter :
>>>
 Hi all,

 as an idea to get jackdbus stopping and then startup again I used as
 Edward Schrober suggested :

 sudo kill -9 4327 (the number is the pid of jackdbus)

 but to no avail, jack won't start again. Now I'm on xfce, default for
 ubuntustudio. So it is not gnome related, but a more general configuration
 issue I think.

 grtz,

 Bart


 http://www.bartart3d.be/
 On Twitter 
 On Identi.ca 
 On Google+ 

 2015-08-13 9:00 GMT+02:00 bart deruyter :

> Hi all,
>
> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
> kxstudio installed through software sources.
>
> My soundcard is an Echo Audiofire 12, connected with firewire.
>
> Since 15.04 when I start jack it works fine as long as I don't run any
> other application which requires sound, before starting jack.
>
> it is consistently going wrong when I for example start chrome, exit
> chrome and try to start jack, using claudia, or qjackctl, or commandline.
> the message qjackctl throws is: JackServer::Open failed with -1
>
> When I log out of the system, then log in again (no reboot required)
> it works again, as long as I start jack first.
>
> Also, when I use chrome while running jack things seem to keep
> working, though I have ben thrown out of jack too.
>
> - I checked if I was in audio-group, which I am, otherwise it wouldn't
> work at all.
> - I turned autospawn off for pulseaudio and killed pulseaudio befor
> starting jack
> - tried out various settings in qjackctl.
>
> None seem to have helped.
>
> How can I trace the source of the problem? If it is a known issue,
> anyone idea's on how to fix this?
>
> grtz,
>
> B

Re: [ubuntu-studio-users] weird behaviour firewire

2015-08-13 Thread bart deruyter
Hi all,

I think I have found the solution. I still have to test it more in depth,
but so far it seems to have worked. The culprit probably was
pulseaudio-module-jack.
I uninstalled it and now it seems to work just fine.

So, if anyone else might have this problem of jackd not wanting to start
again after having exited in the same session, and doesn't need it the
pulse-jack sink: remove pulseaudio-module-jack.

grtz,

Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2015-08-13 18:23 GMT+02:00 Mike Holstein :

>
>
> On Thu, Aug 13, 2015 at 12:01 PM, bart deruyter 
> wrote:
>
>> Turning back to the original thread I started:
>>
>> @ Mike Holstein:
>>
>> my mistake I set the examples in the wrong order, usually I do first exit
>> jack, don't hammer on it.* It is not the biggest issue.* Any way it
>> happens, exiting jack and trying to start it again, even when I keep the
>> device on, I don't get jack working anymore.
>>
>> And it's not my first day using ubuntustudio, I'm not a beginner, using
>> it sort of hapily for 7 years now, so I do have some experience. Until now
>> I never had any problem with exiting jack to start it again later on.
>> Secondly I do use the internet to communicate too, not just to browse
>> around a little, talking to other people who make music, browsing for
>> samples, etc...
>>
>> I do not intend to invest in a second machine and I do expect my computer
>> to handle audio work and some simple tasks as typing a letter of browsing
>> the internet. I simply don't have the funds for it and I don't want to
>> scale the philosophy of "for each task a different program" up to "for each
>> task a different computer".
>>
>> greetz,
>>
>>
> at this point, for me, personally, i would go forward. i would test in
> 15.10, and see if it works there. file a bug, or join a bug, and move on..
> otherwise, im not talking about a requiring a physical machine per task. im
> just suggesting, potentially having a different installation on the same
> machine, where, one is catering to desktop use, and the other is catering
> to audio production. not that this is a key factor. no doubt, it *should*
> ideally be working to do what you are wanting to do. but, i find, dealing
> with firewire to be especially challenging.
>
> cheers, and good luck!
>
>
>
>
>> Bart
>>
>> http://www.bartart3d.be/
>> On Twitter 
>> On Identi.ca 
>> On Google+ 
>>
>> 2015-08-13 17:46 GMT+02:00 bart deruyter :
>>
>>> Hi all,
>>>
>>> as an idea to get jackdbus stopping and then startup again I used as
>>> Edward Schrober suggested :
>>>
>>> sudo kill -9 4327 (the number is the pid of jackdbus)
>>>
>>> but to no avail, jack won't start again. Now I'm on xfce, default for
>>> ubuntustudio. So it is not gnome related, but a more general configuration
>>> issue I think.
>>>
>>> grtz,
>>>
>>> Bart
>>>
>>>
>>> http://www.bartart3d.be/
>>> On Twitter 
>>> On Identi.ca 
>>> On Google+ 
>>>
>>> 2015-08-13 9:00 GMT+02:00 bart deruyter :
>>>
 Hi all,

 I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
 kxstudio installed through software sources.

 My soundcard is an Echo Audiofire 12, connected with firewire.

 Since 15.04 when I start jack it works fine as long as I don't run any
 other application which requires sound, before starting jack.

 it is consistently going wrong when I for example start chrome, exit
 chrome and try to start jack, using claudia, or qjackctl, or commandline.
 the message qjackctl throws is: JackServer::Open failed with -1

 When I log out of the system, then log in again (no reboot required) it
 works again, as long as I start jack first.

 Also, when I use chrome while running jack things seem to keep working,
 though I have ben thrown out of jack too.

 - I checked if I was in audio-group, which I am, otherwise it wouldn't
 work at all.
 - I turned autospawn off for pulseaudio and killed pulseaudio befor
 starting jack
 - tried out various settings in qjackctl.

 None seem to have helped.

 How can I trace the source of the problem? If it is a known issue,
 anyone idea's on how to fix this?

 grtz,

 Bart

 http://www.bartart3d.be/
 On Twitter 
 On Identi.ca 
 On Google+ 

>>>
>>>
>>> http://www.bartart3d.be/
>>> On Twitter 
>>> On Identi.ca 
>>> On Google+ 

Re: [ubuntu-studio-users] weird behaviour firewire

2015-08-13 Thread Mike Holstein
On Thu, Aug 13, 2015 at 12:01 PM, bart deruyter 
wrote:

> Turning back to the original thread I started:
>
> @ Mike Holstein:
>
> my mistake I set the examples in the wrong order, usually I do first exit
> jack, don't hammer on it.* It is not the biggest issue.* Any way it
> happens, exiting jack and trying to start it again, even when I keep the
> device on, I don't get jack working anymore.
>
> And it's not my first day using ubuntustudio, I'm not a beginner, using it
> sort of hapily for 7 years now, so I do have some experience. Until now I
> never had any problem with exiting jack to start it again later on.
> Secondly I do use the internet to communicate too, not just to browse
> around a little, talking to other people who make music, browsing for
> samples, etc...
>
> I do not intend to invest in a second machine and I do expect my computer
> to handle audio work and some simple tasks as typing a letter of browsing
> the internet. I simply don't have the funds for it and I don't want to
> scale the philosophy of "for each task a different program" up to "for each
> task a different computer".
>
> greetz,
>
>
at this point, for me, personally, i would go forward. i would test in
15.10, and see if it works there. file a bug, or join a bug, and move on..
otherwise, im not talking about a requiring a physical machine per task. im
just suggesting, potentially having a different installation on the same
machine, where, one is catering to desktop use, and the other is catering
to audio production. not that this is a key factor. no doubt, it *should*
ideally be working to do what you are wanting to do. but, i find, dealing
with firewire to be especially challenging.

cheers, and good luck!




> Bart
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
> 2015-08-13 17:46 GMT+02:00 bart deruyter :
>
>> Hi all,
>>
>> as an idea to get jackdbus stopping and then startup again I used as
>> Edward Schrober suggested :
>>
>> sudo kill -9 4327 (the number is the pid of jackdbus)
>>
>> but to no avail, jack won't start again. Now I'm on xfce, default for
>> ubuntustudio. So it is not gnome related, but a more general configuration
>> issue I think.
>>
>> grtz,
>>
>> Bart
>>
>>
>> http://www.bartart3d.be/
>> On Twitter 
>> On Identi.ca 
>> On Google+ 
>>
>> 2015-08-13 9:00 GMT+02:00 bart deruyter :
>>
>>> Hi all,
>>>
>>> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
>>> kxstudio installed through software sources.
>>>
>>> My soundcard is an Echo Audiofire 12, connected with firewire.
>>>
>>> Since 15.04 when I start jack it works fine as long as I don't run any
>>> other application which requires sound, before starting jack.
>>>
>>> it is consistently going wrong when I for example start chrome, exit
>>> chrome and try to start jack, using claudia, or qjackctl, or commandline.
>>> the message qjackctl throws is: JackServer::Open failed with -1
>>>
>>> When I log out of the system, then log in again (no reboot required) it
>>> works again, as long as I start jack first.
>>>
>>> Also, when I use chrome while running jack things seem to keep working,
>>> though I have ben thrown out of jack too.
>>>
>>> - I checked if I was in audio-group, which I am, otherwise it wouldn't
>>> work at all.
>>> - I turned autospawn off for pulseaudio and killed pulseaudio befor
>>> starting jack
>>> - tried out various settings in qjackctl.
>>>
>>> None seem to have helped.
>>>
>>> How can I trace the source of the problem? If it is a known issue,
>>> anyone idea's on how to fix this?
>>>
>>> grtz,
>>>
>>> Bart
>>>
>>> http://www.bartart3d.be/
>>> On Twitter 
>>> On Identi.ca 
>>> On Google+ 
>>>
>>
>>
>> http://www.bartart3d.be/
>> On Twitter 
>> On Identi.ca 
>> On Google+ 
>>
>> 2015-08-13 9:00 GMT+02:00 bart deruyter :
>>
>>> Hi all,
>>>
>>> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
>>> kxstudio installed through software sources.
>>>
>>> My soundcard is an Echo Audiofire 12, connected with firewire.
>>>
>>> Since 15.04 when I start jack it works fine as long as I don't run any
>>> other application which requires sound, before starting jack.
>>>
>>> it is consistently going wrong when I for example start chrome, exit
>>> chrome and try to start jack, using claudia, or qjackctl, or commandline.
>>> the message qjackctl throws is: JackServer::Open failed with -1
>>>
>>> When I log out of the system, then log in again (no reboot required) it
>>> works again, as long as I start jack first.
>>>
>

Re: [ubuntu-studio-users] weird behaviour firewire

2015-08-13 Thread bart deruyter
Turning back to the original thread I started:

@ Mike Holstein:

my mistake I set the examples in the wrong order, usually I do first exit
jack, don't hammer on it.* It is not the biggest issue.* Any way it
happens, exiting jack and trying to start it again, even when I keep the
device on, I don't get jack working anymore.

And it's not my first day using ubuntustudio, I'm not a beginner, using it
sort of hapily for 7 years now, so I do have some experience. Until now I
never had any problem with exiting jack to start it again later on.
Secondly I do use the internet to communicate too, not just to browse
around a little, talking to other people who make music, browsing for
samples, etc...

I do not intend to invest in a second machine and I do expect my computer
to handle audio work and some simple tasks as typing a letter of browsing
the internet. I simply don't have the funds for it and I don't want to
scale the philosophy of "for each task a different program" up to "for each
task a different computer".

greetz,

Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2015-08-13 17:46 GMT+02:00 bart deruyter :

> Hi all,
>
> as an idea to get jackdbus stopping and then startup again I used as
> Edward Schrober suggested :
>
> sudo kill -9 4327 (the number is the pid of jackdbus)
>
> but to no avail, jack won't start again. Now I'm on xfce, default for
> ubuntustudio. So it is not gnome related, but a more general configuration
> issue I think.
>
> grtz,
>
> Bart
>
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
> 2015-08-13 9:00 GMT+02:00 bart deruyter :
>
>> Hi all,
>>
>> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
>> kxstudio installed through software sources.
>>
>> My soundcard is an Echo Audiofire 12, connected with firewire.
>>
>> Since 15.04 when I start jack it works fine as long as I don't run any
>> other application which requires sound, before starting jack.
>>
>> it is consistently going wrong when I for example start chrome, exit
>> chrome and try to start jack, using claudia, or qjackctl, or commandline.
>> the message qjackctl throws is: JackServer::Open failed with -1
>>
>> When I log out of the system, then log in again (no reboot required) it
>> works again, as long as I start jack first.
>>
>> Also, when I use chrome while running jack things seem to keep working,
>> though I have ben thrown out of jack too.
>>
>> - I checked if I was in audio-group, which I am, otherwise it wouldn't
>> work at all.
>> - I turned autospawn off for pulseaudio and killed pulseaudio befor
>> starting jack
>> - tried out various settings in qjackctl.
>>
>> None seem to have helped.
>>
>> How can I trace the source of the problem? If it is a known issue, anyone
>> idea's on how to fix this?
>>
>> grtz,
>>
>> Bart
>>
>> http://www.bartart3d.be/
>> On Twitter 
>> On Identi.ca 
>> On Google+ 
>>
>
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
> 2015-08-13 9:00 GMT+02:00 bart deruyter :
>
>> Hi all,
>>
>> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
>> kxstudio installed through software sources.
>>
>> My soundcard is an Echo Audiofire 12, connected with firewire.
>>
>> Since 15.04 when I start jack it works fine as long as I don't run any
>> other application which requires sound, before starting jack.
>>
>> it is consistently going wrong when I for example start chrome, exit
>> chrome and try to start jack, using claudia, or qjackctl, or commandline.
>> the message qjackctl throws is: JackServer::Open failed with -1
>>
>> When I log out of the system, then log in again (no reboot required) it
>> works again, as long as I start jack first.
>>
>> Also, when I use chrome while running jack things seem to keep working,
>> though I have ben thrown out of jack too.
>>
>> - I checked if I was in audio-group, which I am, otherwise it wouldn't
>> work at all.
>> - I turned autospawn off for pulseaudio and killed pulseaudio befor
>> starting jack
>> - tried out various settings in qjackctl.
>>
>> None seem to have helped.
>>
>> How can I trace the source of the problem? If it is a known issue, anyone
>> idea's on how to fix this?
>>
>> grtz,
>>
>> Bart
>>
>> http://www.bartart3d.be/
>> On Twitter 
>> On Identi.ca 
>> On Google+ 
>>
>
>
-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modif

Re: [ubuntu-studio-users] weird behaviour firewire

2015-08-13 Thread bart deruyter
Hi all,

as an idea to get jackdbus stopping and then startup again I used as
Edward Schrober suggested :

sudo kill -9 4327 (the number is the pid of jackdbus)

but to no avail, jack won't start again. Now I'm on xfce, default for
ubuntustudio. So it is not gnome related, but a more general configuration
issue I think.

grtz,

Bart


http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2015-08-13 9:00 GMT+02:00 bart deruyter :

> Hi all,
>
> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
> kxstudio installed through software sources.
>
> My soundcard is an Echo Audiofire 12, connected with firewire.
>
> Since 15.04 when I start jack it works fine as long as I don't run any
> other application which requires sound, before starting jack.
>
> it is consistently going wrong when I for example start chrome, exit
> chrome and try to start jack, using claudia, or qjackctl, or commandline.
> the message qjackctl throws is: JackServer::Open failed with -1
>
> When I log out of the system, then log in again (no reboot required) it
> works again, as long as I start jack first.
>
> Also, when I use chrome while running jack things seem to keep working,
> though I have ben thrown out of jack too.
>
> - I checked if I was in audio-group, which I am, otherwise it wouldn't
> work at all.
> - I turned autospawn off for pulseaudio and killed pulseaudio befor
> starting jack
> - tried out various settings in qjackctl.
>
> None seem to have helped.
>
> How can I trace the source of the problem? If it is a known issue, anyone
> idea's on how to fix this?
>
> grtz,
>
> Bart
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>


http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2015-08-13 9:00 GMT+02:00 bart deruyter :

> Hi all,
>
> I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and
> kxstudio installed through software sources.
>
> My soundcard is an Echo Audiofire 12, connected with firewire.
>
> Since 15.04 when I start jack it works fine as long as I don't run any
> other application which requires sound, before starting jack.
>
> it is consistently going wrong when I for example start chrome, exit
> chrome and try to start jack, using claudia, or qjackctl, or commandline.
> the message qjackctl throws is: JackServer::Open failed with -1
>
> When I log out of the system, then log in again (no reboot required) it
> works again, as long as I start jack first.
>
> Also, when I use chrome while running jack things seem to keep working,
> though I have ben thrown out of jack too.
>
> - I checked if I was in audio-group, which I am, otherwise it wouldn't
> work at all.
> - I turned autospawn off for pulseaudio and killed pulseaudio befor
> starting jack
> - tried out various settings in qjackctl.
>
> None seem to have helped.
>
> How can I trace the source of the problem? If it is a known issue, anyone
> idea's on how to fix this?
>
> grtz,
>
> Bart
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
-- 
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


[ubuntu-studio-users] weird behaviour firewire

2015-08-13 Thread bart deruyter
Hi all,

I'm running ubuntu 15.04 now, gnome variant, with ubuntustudio and kxstudio
installed through software sources.

My soundcard is an Echo Audiofire 12, connected with firewire.

Since 15.04 when I start jack it works fine as long as I don't run any
other application which requires sound, before starting jack.

it is consistently going wrong when I for example start chrome, exit chrome
and try to start jack, using claudia, or qjackctl, or commandline.
the message qjackctl throws is: JackServer::Open failed with -1

When I log out of the system, then log in again (no reboot required) it
works again, as long as I start jack first.

Also, when I use chrome while running jack things seem to keep working,
though I have ben thrown out of jack too.

- I checked if I was in audio-group, which I am, otherwise it wouldn't work
at all.
- I turned autospawn off for pulseaudio and killed pulseaudio befor
starting jack
- tried out various settings in qjackctl.

None seem to have helped.

How can I trace the source of the problem? If it is a known issue, anyone
idea's on how to fix this?

grtz,

Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 
-- 
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