12 Sep
2016
12 Sep
'16
8:35 p.m.
System: Ubuntu Mate 14.04.
Hi, there. With some problems that I could resolve, I compiled with success:
- zita-resampler-1.3.0
- zita-njbridge-0.1.1
I did this in two computers. Now, in one computer, I run zita-j2n with
success. In Patchage, I can see the Jack server, it is there. I connect
PureData to it.
Now, in the other computer, I try to run zita-n2j and it says:
/mario@circo3d:~$ zita-j2n --jname zita --chan 2 192.168.1.41 8800//
//Cannot read socket fd = 6 err = Success//
//CheckRes error//
//JackSocketClientChannel read fail//
//Fatal error condition, terminating.//
//Server is not running//
//Server is not running//
/
... but Jack is running. I use QjackCtl, but I tried with jackd from
command line and it tells me the same error.
In this computer, zita-n2j runs well.
What's happening with zita-j2n?
Is Kokkini Zita in this list?
Thanks in advance.
12 Sep
12 Sep
9:04 p.m.
I could make it work...
*This didn't work:*
/zita-n2j --jserv zita --chan 2 192.168.1.35 8800/
I wanted to have a jack server called "zita", but it didn't work. I
wanted to in this way because, in the other computer, I runned:
/zita-j2n --jname zita --chan 2 192.168.1.35 8800/
This created a 2 channel port called "zita" in Jack.
*This worked:*
/zita-n2j --chan 1,2 192.168.1.35 8800/
It creates automatically a port called "zita-n2j" in patchbay.
Is this a bug?
I mean, shouldn't --jserv <name> be the port name? If not, what should I
put in that option?
Anyway... It works but after some seconds, there are a lot of
pops/clicks: UNACCEPTABLE.
I'm trying with netjack.trip right now...
El 12/09/16 a las 15:35, Mario Sottile escribió:
System: Ubuntu Mate 14.04.
Hi, there. With some problems that I could resolve, I compiled with
success:
- zita-resampler-1.3.0
- zita-njbridge-0.1.1
I did this in two computers. Now, in one computer, I run zita-j2n with
success. In Patchage, I can see the Jack server, it is there. I
connect PureData to it.
Now, in the other computer, I try to run zita-n2j and it says:
/mario@circo3d:~$ zita-j2n --jname zita --chan 2 192.168.1.41 8800//
//Cannot read socket fd = 6 err = Success//
//CheckRes error//
//JackSocketClientChannel read fail//
//Fatal error condition, terminating.//
//Server is not running//
//Server is not running//
/
... but Jack is running. I use QjackCtl, but I tried with jackd from
command line and it tells me the same error.
In this computer, zita-n2j runs well.
What's happening with zita-j2n?
Is Kokkini Zita in this list?
Thanks in advance.
9:21 p.m.
Do not attempt to use JACK server names.
This feature should never have been exposed to users (my mistake).
On Mon, Sep 12, 2016 at 3:04 PM, Mario Sottile <mariomey(a)gmail.com> wrote:
I could make it work...
*This didn't work:* *zita-n2j --jserv zita --chan 2 192.168.1.35 8800*
I wanted to have a jack server called "zita", but it didn't work. I wanted
to in this way because, in the other computer, I runned:
*zita-j2n --jname zita --chan 2 192.168.1.35 8800*
This created a 2 channel port called "zita" in Jack.
*This worked:* *zita-n2j --chan 1,2 192.168.1.35 8800*
It creates automatically a port called "zita-n2j" in patchbay.
Is this a bug?
I mean, shouldn't --jserv <name> be the port name? If not, what should I
put in that option?
Anyway... It works but after some seconds, there are a lot of pops/clicks:
UNACCEPTABLE.
I'm trying with netjack.trip right now...
El 12/09/16 a las 15:35, Mario Sottile escribió:
System: Ubuntu Mate 14.04.
Hi, there. With some problems that I could resolve, I compiled with
success:
- zita-resampler-1.3.0
- zita-njbridge-0.1.1
I did this in two computers. Now, in one computer, I run zita-j2n with
success. In Patchage, I can see the Jack server, it is there. I connect
PureData to it.
Now, in the other computer, I try to run zita-n2j and it says:
*mario@circo3d:~$ zita-j2n --jname zita --chan 2 192.168.1.41 8800*
*Cannot read socket fd = 6 err = Success*
*CheckRes error*
*JackSocketClientChannel read fail*
*Fatal error condition, terminating.*
*Server is not running*
*Server is not running*
... but Jack is running. I use QjackCtl, but I tried with jackd from
command line and it tells me the same error.
In this computer, zita-n2j runs well.
What's happening with zita-j2n?
Is Kokkini Zita in this list?
Thanks in advance.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
13 Sep
13 Sep
1:44 p.m.
On Mon, Sep 12, 2016 at 04:04:21PM -0300, Mario Sottile wrote:
*This didn't work:*
/zita-n2j --jserv zita --chan 2 192.168.1.35 8800/
I wanted to have a jack server called "zita", but it didn't work. I
wanted to in this way because, in the other computer, I runned:
/zita-j2n --jname zita --chan 2 192.168.1.35 8800/
This created a 2 channel port called "zita" in Jack.
*This worked:*
/zita-n2j --chan 1,2 192.168.1.35 8800/
It creates automatically a port called "zita-n2j" in patchbay.
Is this a bug?
I mean, shouldn't --jserv <name> be the port name? If not, what
should I put in that option?
Certainly not. Read the help text and/or the man page.
You need --jserv only if you have more than one Jack
server running on the same machine, or if the only one
doesn't have the default name.
P.S. Contrary to 'official wisdom', having more than one
server (and hence having to select wich one to connect
to) is perfectly normal thing in some use cases.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
3085
days inactive
3086
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Fons Adriaensen -
Mario Sottile -
Paul Davis