30 Nov
2010
30 Nov
'10
4:27 p.m.
1- can anyone recommend a LADSPA or Windows VST plug (want to use in
Ardour) that approaches the quality and flexibility of the GRM Equalize
plug?
http://www.grmtools.org/qt/files/Equalize_ST.html
2- my Dell laptop has a 4-pin firewire output and was wondering if there
are any issues with using a 4 pin cable for a 6 pin I/O other than not
supplying power?
I know I have to supply power to the box since a 4-pin 1394 connector
doesn't carry DC power.
30 Nov
30 Nov
4:56 p.m.
On Tue, Nov 30, 2010 at 8:20 AM, Kim Cascone <kim(a)anechoicmedia.com> wrote:
<SNIP>
2- my Dell laptop has a 4-pin firewire output and was wondering if there are
any issues with using a 4 pin cable for a 6 pin I/O other than not supplying
power?
I know I have to supply power to the box since a 4-pin 1394 connector
doesn't carry DC power.
There should be no issues. The 6-pin connector is literally the 4-pin
connector signals (2 out, 2 in) with 2 power wires. There is no
difference in the IEEE-1394A specs for either connector and, in my
experience, the 4-pin has always worked for me.
The biggest issue with 1394 on Linux is the 1394 controller in the PC.
You might look around for evidence that your specific hardware (the
chip inside - not the laptop) is well supported. (I.e - TI is, others
vary) Stefan Richter in the 1394 user list is a great resource. lspci
is your friend.
Hope this helps,
Mark
5:38 p.m.
Mark Knecht wrote:
On Tue, Nov 30, 2010 at 8:20 AM, Kim Cascone
<kim(a)anechoicmedia.com> wrote:
<SNIP>
OK thanks for the info! :)
2- my Dell laptop has a 4-pin firewire output and
was wondering if there are
any issues with using a 4 pin cable for a 6 pin I/O other than not supplying
power?
I know I have to supply power to the box since a 4-pin 1394 connector
doesn't carry DC power.
There should be no issues. The 6-pin connector is literally the 4-pin
connector signals (2 out, 2 in) with 2 power wires. There is no
difference in the IEEE-1394A specs for either connector and, in my
experience, the 4-pin has always worked for me.
The biggest issue with 1394 on Linux is the 1394
controller in the PC.
You might look around for evidence that your specific hardware (the
chip inside - not the laptop) is well supported. (I.e - TI is, others
vary) Stefan Richter in the 1394 user list is a great resource. lspci
is your friend.
yeah I did a lspci and found:
09:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
(rev 05)
-- also --
sudo lshw | grep 1394
description: FireWire (IEEE 1394)
product: R5C832 IEEE 1394 Controller
configuration: driver=ohci1394 latency=32 maxlatency=4
mingnt=2 module=ohci1394
Hope this helps,
Mark
6:13 p.m.
On Tue, Nov 30, 2010 at 9:38 AM, Kim Cascone <kim(a)anechoicmedia.com> wrote:
<SNIP>
OK, as it's Ricoh which is a brand known to have a few problems over
the years I would consider doing a little Googling or better yet
subscribe to the Linux 1394-user group and ask on there about any
specific things you should need to know.
Note that there are now two 1394 stacks in the kernel. (Have been for
a while...) Depending on which one you choose you use different
drivers and get slightly different results. I only mention this
because in distro kernels they choose different ones and this may be
an issue for you. I strongly suggest building your own kernels if
you're going to use 1394 as then you'll be able to take full advantage
of info you get from other users about setup.
Of course, maybe it will just work and there won't be any issues at all! ;-)
Cheers,
Mark
The biggest
issue with 1394 on Linux is the 1394 controller in the PC.
You might look around for evidence that your specific hardware (the
chip inside - not the laptop) is well supported. (I.e - TI is, others
vary) Stefan Richter in the 1394 user list is a great resource. lspci
is your friend.
yeah I did a lspci and found:
09:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev
05)
-- also --
sudo lshw | grep 1394
description: FireWire (IEEE 1394)
product: R5C832 IEEE 1394 Controller
configuration: driver=ohci1394 latency=32 maxlatency=4
mingnt=2 module=ohci1394 
1 Dec
1 Dec
1:44 a.m.
On Tue, Nov 30, 2010 at 09:38:09AM -0800, Kim Cascone wrote:
Mark Knecht wrote:
Ricoh chipets are, IIRC, the ones with extreme nonworkingness. Though it may depend on
which rev, I dunno.
I had one, and nothing worked. I had to get an ExpressCard with a TI chipset, and that one
worked.
-ken
On Tue, Nov 30, 2010 at 8:20 AM, Kim Cascone
<kim(a)anechoicmedia.com> wrote:
<SNIP>
OK thanks for the info! :)
2- my Dell laptop has a 4-pin firewire output and
was wondering if there are
any issues with using a 4 pin cable for a 6 pin I/O other than not supplying
power?
I know I have to supply power to the box since a 4-pin 1394 connector
doesn't carry DC power.
There should be no issues. The 6-pin connector is literally the 4-pin
connector signals (2 out, 2 in) with 2 power wires. There is no
difference in the IEEE-1394A specs for either connector and, in my
experience, the 4-pin has always worked for me.
The biggest issue with 1394 on Linux is the 1394
controller in the PC.
You might look around for evidence that your specific hardware (the
chip inside - not the laptop) is well supported. (I.e - TI is, others
vary) Stefan Richter in the 1394 user list is a great resource. lspci
is your friend.
yeah I did a lspci and found:
09:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
(rev 05)
-- also --
sudo lshw | grep 1394
description: FireWire (IEEE 1394)
product: R5C832 IEEE 1394 Controller
configuration: driver=ohci1394 latency=32 maxlatency=4
mingnt=2 module=ohci1394
3:42 a.m.
I don't remember which one I bought. It was like 3 or 4 years ago. Just something
cheap off of pricegrabber.com. I think it was $60.
-ken
-------------
On Tue, Nov 30, 2010 at 06:15:46PM -0800, Kim Cascone wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ken Restivo wrote:
<blockquote cite="mid:20101201014408.GB3591@aieee.restivo.org"
type="cite">
<pre wrap="">On Tue, Nov 30, 2010 at 09:38:09AM -0800, Kim Cascone
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Mark Knecht wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, Nov 30, 2010 at 8:20 AM, Kim Cascone <a
class="moz-txt-link-rfc2396E"
href="mailto:kim@anechoicmedia.com"><kim@anechoicmedia.com></a>
wrote:
<SNIP>
</pre>
<blockquote type="cite">
<pre wrap="">2- my Dell laptop has a 4-pin firewire output and
was wondering if there are
any issues with using a 4 pin cable for a 6 pin I/O other than not supplying
power?
I know I have to supply power to the box since a 4-pin 1394 connector
doesn't carry DC power.
</pre>
</blockquote>
<pre wrap="">There should be no issues. The 6-pin connector is
literally the 4-pin
connector signals (2 out, 2 in) with 2 power wires. There is no
difference in the IEEE-1394A specs for either connector and, in my
experience, the 4-pin has always worked for me.
</pre>
</blockquote>
<pre wrap="">OK thanks for the info! :)
</pre>
<blockquote type="cite">
<pre wrap="">The biggest issue with 1394 on Linux is the 1394
controller in the PC.
You might look around for evidence that your specific hardware (the
chip inside - not the laptop) is well supported. (I.e - TI is, others
vary) Stefan Richter in the 1394 user list is a great resource. lspci
is your friend.
</pre>
</blockquote>
<pre wrap="">yeah I did a lspci and found:
09:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
(rev 05)
-- also --
sudo lshw | grep 1394
description: FireWire (IEEE 1394)
product: R5C832 IEEE 1394 Controller
configuration: driver=ohci1394 latency=32 maxlatency=4
mingnt=2 module=ohci1394
</pre>
</blockquote>
<pre wrap=""><!---->
Ricoh chipets are, IIRC, the ones with extreme nonworkingness. Though it may depend on
which rev, I dunno.
I had one, and nothing worked. I had to get an ExpressCard with a TI chipset, and that
one worked.
</pre>
</blockquote>
which ExpressCard I/O did you buy?<br>
<br>
</body>
</html>
2:19 p.m.
On Tue, Nov 30, 2010 at 6:15 PM, Kim Cascone <kim(a)anechoicmedia.com> wrote:
<SNIP>
Ricoh chipets are, IIRC, the ones with extreme nonworkingness. Though it may
depend on which rev, I dunno.
It does. Some work OK.
Again, the info comes for free. Google, 1394 users list, build a
kernel and try it, etc., will gain some specific knowledge before
spending money.
I had one, and nothing worked. I had to get an
ExpressCard with a TI
chipset, and that one worked.
which ExpressCard I/O did you buy?
Does your laptop offer some solution for adding external peripherals
other than using USB or 1394?
2 Dec
2 Dec
1 p.m.
On 11/30/2010 05:20 PM, Kim Cascone wrote:
1- can anyone recommend a LADSPA or Windows VST plug
(want to use in
Ardour) that approaches the quality and flexibility of the GRM Equalize
plug?
http://www.grmtools.org/qt/files/Equalize_ST.html
for studio work, i'd advise against using graphic eqs. if you look at
the actual results (rather than the nice "graph" of your sliders),
you'll break a sweat :)
i find fons' FIL plugin (with the nice graphical lv2 ui written by
nedko, google for lv2fil, or your distro might already have it) solves
most issues. the only other things i use in addition to that are steep
low and highpass filters, sometimes.
2- my Dell laptop has a 4-pin firewire output and was
wondering if there
are any issues with using a 4 pin cable for a 6 pin I/O other than not
supplying power?
I know I have to supply power to the box since a 4-pin 1394 connector
doesn't carry DC power.
no other issues. i found that a 4pin connector is usually a tighter fit
and seems more trustworthy to me than its big brother...
4899
days inactive
4901
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Jörn Nettingsmeier -
Ken Restivo -
Kim Cascone -
Mark Knecht