Re: CIP Discontinuity with snd-firewire-digi00x

[Takashi Sakamoto <o-takashi@sakamocchi.jp>]

Hi,

On Jun 5 2016 08:09, lin-alsa@noblejury.com wrote:
> The relavent dmesg lines (dmesg | grep fire) are here: http://ix.io/OQ2.
> I don't know if the first bit about the config rom has anything to do with
> this, but I hope it helps, and the hex pairs are in that log.

It's really my help, great ;)

> Re: the clock issue, I'm not actually using optical in, if that's what
> you mean. Please explain what you mean to me, I'm a bit confused as to
> your question.

Oops. I was dull just after waking up. (it's an exchange for the quick
reply...)

On Jun 5 2016 07:30, lin-alsa@noblejury.com wrote:
> `Optical mode: adat
> Sampling Rate: 88200
> Clock Source: internal`

Indeed, your unit is set to use internal clock signal as sampling clock.
So no worry about the external signals, sorry.


Well, as long as seeing your log, ALSA digi00x driver detects
discontinuity of data block counter on incoming packets from the unit.
(On IEEE 1394 bus, data is transferred as a form of packet.)
Unfortunately, I cannot reproduce this situation with my unit.

So I think there's two possibility:
1.We work with different drivers; i.e. based on different source code.
2.We work with different state of the unit; i.e. different firmware.

At first, let's confirm the item 1. Could you explain where
snd-firewire-digi00x comes from? Is it from any Linux distribution? Or
you did handy install from somewhere such as my repository in github.com?


Regards

Takashi Sakamoto