Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Intel Core2 Duo and 1394

0 views
Skip to first unread message

jona...@yahoo.com

unread,
Jan 15, 2007, 11:09:12 PM1/15/07
to
Has anybody else had problems with Intel Core 2 Duo systems and using
Presonus 1394 interfaces?

I've got a problem I'm trying to narrow down, and I think it is
specifically related to whatever 1394 drivers/interface is part of the
Intel Core 2 Duo systems. It seems like a timing or throughput
problem.

If anybody else has seen issues, please let me know...

Jonas

jtougas

unread,
Jan 15, 2007, 11:32:14 PM1/15/07
to
On 15 Jan 2007 20:09:12 -0800, jona...@yahoo.com trained 100 monkeys

Two Questions :

What interface are you trying to use with the Firewire?

What controller chip is in your Firewire setup?

There are several Firewire controller chips, some more highly
suggested than others (like the Texas Instruments, for instance).

--
jtougas

"listen- there's a hell of a good universe next door
let's go" - e.e. cummings

Steve

unread,
Jan 17, 2007, 12:49:35 AM1/17/07
to
In article <1168920552.0...@11g2000cwr.googlegroups.com>,
jona...@yahoo.com wrote:


I don't think the problem is specific to Core 2 Duo machines. A friend
of mine bought a Presonus Firewire audio interface and had nothing but
problems. He narrowed it down to the Presonus drivers, and returned it
and bought a cheap USB Digidesign interface with Pro-Tools LE and then
an M-Audio Firewire interface with different audio software (I don't
remember which kind) and didn't have any of those problems.

Lots of phone calls to Presonus technical support and they couldn't get
the system to work flawlessly.

Soundhaspriority

unread,
Jan 17, 2007, 1:15:10 AM1/17/07
to

"Steve" <St...@IHATESPAM.com> wrote in message
news:Steve-AE9883....@comcast.dca.giganews.com...

Yes. But multiprocessor systems do tend to break software that wasn't tested
on them. Practically all software has lightweight processes, ie., threads,
but that doesn't mean it was tested for race conditions on a particular
system.

Bob Morein
Dresher, PA
(215) 646-4894


Tonehenge

unread,
Jan 27, 2007, 11:52:03 AM1/27/07
to
I too had a Presonus device (Inspire) and the drivers were very problematic.
Traded it back in for an M-Audio...now everything is grand.

"Steve" <St...@IHATESPAM.com> wrote in message
news:Steve-AE9883....@comcast.dca.giganews.com...

jona...@yahoo.com

unread,
Jan 29, 2007, 9:22:26 PM1/29/07
to
The interface/chipset is not apparent. It shows up only as OHCI
complient and its built-in. I tried chasing down the vendor ID that
it reports, but was a dead-end.
It is based on the Intel 945PM Express chipset, its a Dell Latitude
D820. I'm assuming that the 1394 part is provided by the Intel
chipset and generic drivers.
Everything works fine even with the Presonus box if I use an add-on
1394 card. Its only a problem with the buil-in 1394 port.

I am using a very precise audio measurement/analasys software package,
and with the built-int 1394 port and the Presonus box, I get pops/
clicks and timing issues.
If I use the add-on 1394 PCCard, everything works fine.

I think that should prove that the problem isn't related to it being a
dual processor setup. I should have the same problem then even with
the add-on card. Personally, I think it is some sort of hardware
optimization made by Intel (or whoever) that Presonus's drivers can't
deal with. I mean, the built-in 1394 port is probably "tuned" for
stuff like external harddrives and video and all that burst-rate
stuff, but maybe sustained digital audio it just can't deal with.
(the combination of the Presonus drivers and the built-in hardware).

What I haven't tried yet and still intend to do is try another 1394
audio product and see how it handles things.

Jonas

Richard Crowley

unread,
Jan 30, 2007, 12:46:11 PM1/30/07
to
<jona...@yahoo.com> wrote ...

Even USB chips are specified as known to operate with certain
operating systems (and versions) and with certain chip-sets, etc.
For example, see the compatibility list on page 34 of the TI PCM2704
spec sheet: http://focus.ti.com/lit/ds/symlink/pcm2704.pdf

But then, Firewire seems even less "universally-operable" than USB.

Although Wikipedia claims that the 1394/Firewire port is implemented
in the 945PM chipset...
http://en.wikipedia.org/wiki/945_chipsets#Intel_Core_Chipsets
I couldn't find any evidence that 1394/Firewire was part of the
chipset from Intel sources. You could likely pin it down with
additonal research.


Roger Norman

unread,
Jan 30, 2007, 2:04:13 PM1/30/07
to
<jona...@yahoo.com> wrote in message
news:1170123745.9...@a34g2000cwb.googlegroups.com...

> Everything works fine even with the Presonus box if I use an add-on
> 1394 card. Its only a problem with the buil-in 1394 port.


If you have a solution, then you have a solution. The question is whether
you want to chase problems or implement solutions. My vote is for the
latter.

--


Roger W. Norman
SirMusic Studio
"Is our children learning yet?" George W. Bush
http://blogs.salon.com/0004478/


> The interface/chipset is not apparent. It shows up only as OHCI
> complient and its built-in. I tried chasing down the vendor ID that
> it reports, but was a dead-end.
> It is based on the Intel 945PM Express chipset, its a Dell Latitude
> D820. I'm assuming that the 1394 part is provided by the Intel
> chipset and generic drivers.
>

Mike Rivers

unread,
Jan 30, 2007, 3:12:39 PM1/30/07
to

jona...@yahoo.com wrote:

> Everything works fine even with the Presonus box if I use an add-on
> 1394 card. Its only a problem with the buil-in 1394 port.

Well, then that's your answer, and your solution, if you want to
concinue using the Presonus interface. A lot of laptop Fireiwire
interface problems have been resolved by using a PCMCIA Firewire
adapter.

Bob Olhsson

unread,
Feb 2, 2007, 9:55:24 AM2/2/07
to
jona...@yahoo.com wrote:
> I've got a problem I'm trying to narrow down, and I think it is
> specifically related to whatever 1394 drivers/interface is part of the
> Intel Core 2 Duo systems. It seems like a timing or throughput
> problem.

The first thing to check are cables!

A huge percentage of brand new shrink-wrapped fire wire cables have been
intermittent in my experience. There is so much error correction going
on in 1394 that this can be really hard to spot. The typical symptoms
are failure when you try to move a lot of data or, even more confusing,
one computer seeing the device while another won't see it.

I rebuilt my C disk a couple times before my wife insisted that I start
swapping the cables around...

--
Bob Olhsson Audio Mastery, Nashville TN
Mastering, Audio for Picture, Mix Evaluation and Quality Control
Over 40 years making people sound better than they ever imagined!
615.385.8051 http://www.hyperback.com

0 new messages