All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D. Sen" <dsen@homemail.com>
To: Florian Faber <faber@faberman.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: RME madiface
Date: Fri, 11 Jul 2008 17:58:32 +1000	[thread overview]
Message-ID: <487712A8.6020403@homemail.com> (raw)
In-Reply-To: <200807110954.31479.faber@faberman.de>

Sure ...going over to private email.

Florian Faber wrote:
> Dee,
> 
>>>> Any ideas?
>>> There is no difference on the MADI bus wether you use Windows, OS X
>>> or Linux. This seems to be a specific problem with the Euphonix.
>> I have no reason to believe the MADI bus is different. However, I
>> suspect the stream are different.
> 
> The MADI cards work autonomous, they are only controlled by a few 
> parameters. If the parameters are the same, the behaviour is the same. 
> Thus the settings must differ, and we have to find out where.
> 
>> I have two Euphonix boxes and they both behave perfectly under
>> windows - but not under linux. The main problem under linux is that
>> they lose sync - at the slightest electromagnetic interference (such
>> as turning off/on the speakers - on the analogue side - even from a
>> distance of 3 metres). 
> 
> I don't believe electromagnetic interference to be a reasonable cause 
> for this. What exactly is your setup - 1x 703 and 1x 713? And both lose 
> sync?
> 
> I just had a glance over the Euphonix' user manual and had to learn that 
> they cannot loop through MADI and you have to use the wordclock. So, 
> please, be a bit more specific about the setup - and maybe via private 
> mail, because that's of no relevance to alsa development..
> 
> 
> Flo

  reply	other threads:[~2008-07-11  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 23:31 RME madiface D. Sen
2008-07-11  4:26 ` Florian Faber
2008-07-11  6:50   ` D. Sen
2008-07-11  7:54     ` Florian Faber
2008-07-11  7:58       ` D. Sen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-13  7:35 Florian Faber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=487712A8.6020403@homemail.com \
    --to=dsen@homemail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=faber@faberman.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.