Vassilis,
First of all, mind that Jack is a professional sound server, such as
Asio for Windows and CoreAudio for MacosX. It is not a default
configuration. You can see it because when you run it for the first
time, there is no .jackdrc file in your home folder. If you run jack in
a terminal with
I'm sorry but I cannot see why I'm being misunderstood. In the summary I
state that if it is started with -n 3 IT WORKS. Right now, jackd WORKS
for me. The default configuration does NOT work.
Please explain to me how a bad default configuration for software that
is able to work on my machine is n
Please get on a forum or mailing list about this issue. This is a
personal configuration issue.
** Changed in: jack-audio-connection-kit (Ubuntu)
Status: New => Invalid
--
wrong arguments for jackd
https://bugs.launchpad.net/bugs/214256
You received this bug notification because you are a
Hi again. I know that this is a configuration issue and that this
depends on my sound card. This is why I changed it to -n 3 . I reported
this because things are supposed to work out of the box, without having
an average user spend hours digging documentation to find out what alsa,
jackd and nperio
Please close the bug
** Changed in: jack-audio-connection-kit (Ubuntu)
Status: New => Invalid
--
wrong arguments for jackd
https://bugs.launchpad.net/bugs/214256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Vassilis,
Depending on the mother board chipset, and the sound card chipset, the
period (n) should be 2 or 3, most of the time. For exemple, RME hdsp and
Echo Audio need 2, Presonus need 3, and for Intel integrated sound
chipset, it depends and it is sometine 2, sometime 3.
So I can close the bu
It appears that you are right - ardour is not just running jackd on its
own. The offending line is found in ~/.jackdrc :
/usr/bin/jackd -p 128 -T -d alsa -n 2 -r 48000 -p 1024 -d hw:0,0
Running this gives :
[EMAIL PROTECTED]:~/backup/pandis/music$ /usr/bin/jackd -p 128 -T -d alsa -n 2
-r 48000
Ardour can not be the problem, it is a jack audio connection kit
configuration problem.
Think that your integrated intel sound chipset is not ready for low
latency configuration. So first of all, try with something getting a
latency around 60ms, and try again to launch ardour. You can try real
tim
I will include the output of jack when I get back to my computer. jackd
is in the jack-audio-connection-kit source package.
--
wrong arguments for jackd
https://bugs.launchpad.net/bugs/214256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Please include any error message.
It seems that the jackd package is not listed in Launchpad, so it is not
possible to report the bug for it.
Toine
--
wrong arguments for jackd
https://bugs.launchpad.net/bugs/214256
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller (rev 02) is the mother board integrated sound chipset,
it is in the lspci txt file.
Vassilis, can you try to configure your sound card with qjackctl instead
of terminal, and tell what it does ?
Toine
--
wrong
What soundcard are you using? This is most likely a HW and or ALSA
issue.
--
wrong arguments for jackd
https://bugs.launchpad.net/bugs/214256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Attachment added: "lspci -vv"
http://launchpadlibrarian.net/13265323/lspci
--
wrong arguments for jackd
https://bugs.launchpad.net/bugs/214256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
13 matches
Mail list logo
