alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Pap Peti <roachkiller44@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	Jonathan Woithe <jwoithe@just42.net>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	ffado-devel@lists.sf.net
Subject: Re: M-audio Audiophile Firewire
Date: Thu, 27 Oct 2016 16:10:06 +0200	[thread overview]
Message-ID: <80a6876e-6ced-7daa-7268-1277850c8270@gmail.com> (raw)
In-Reply-To: <6f6374d3-f616-0d9d-31ac-2d463573f889@sakamocchi.jp>

My controller:


*-firewire
                    description: FireWire (IEEE 1394)
                    product: XIO2200A IEEE-1394a-2000 Controller (PHY/Link)
                    vendor: Texas Instruments
                    physical id: 0
                    bus info: pci@0000:06:00.0
                    version: 01
                    width: 32 bits
                    clock: 66MHz
                    capabilities: ohci bus_master cap_list
                    configuration: driver=firewire_ohci latency=32 
maxlatency=4 mingnt=2
                    resources: irq:19 memory:f1c04000-f1c047ff 
memory:f1c00000-f1c03fff


...summerize:

- If the system work with ALSA driver, the latency minimum 5ms. (and 
where/how can I check the current/real value?)

Anyway I cant use the Sakamoto's utils, I downloaded and installed from 
a package, but not any manual with that. I dont know how can I start 
that stuff and configure in terminal. So only the Jack controller 
remember my settings (and save)?


Regards



On 2016-10-27 01:47, Takashi Sakamoto wrote:
> On Oct 27 2016 04:25, Pap Peti wrote:
>> I think my things still belongs to the 'alsa-devel' topic, because I use
>> the 'ffado-mixer' only to 'turn on' my audio input(s)/output(s)
>>
>> I added my username to the "audio" anyway, and already I wont noticed
>> noise (but sometimes the audio 'stream(?)' stuck a ~half second when I
>> listen music and e.g.: meanwhile run a long file copy, or come some
>> sound from the browser. I think its a 'multi-threaded' problem, and/or
>> different audio sampling rate in same time.
>>
>> So I use to make live records, and do some electric tracks too, but I
>> dont feel I need Jack, because ALSA also can work with low latency (at
>> least in the Tracktion). And - strange - but I feel on this platform the
>> sound quality better than on Windows (with Win10 and the latest Win7
>> 64bit drivers).
> If you need "sham" latency value, using libffado stuff is suitable to
> your aim.
>
> In a point of packet streaming protocol for IEC 61883-1/6 and interrupt
> interval of OHCI 1394 context, ALSA bebob driver has minimum value for
> PCM frames in one buffer period. Currently tt's 5msec. In detail, see
> comment of corresponding code:
> http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/firewire/amdtp-stream.c#n140
>
> Jackd with firewire backend just displays value convenient to users,
> although it's not reasonable in a technical point.
>
>
> Well, about the noise you heard, I can't re-generate the issue. So we
> could judge it depending on environment. Do you explain more details?
> Which application you use? What OHCI 1394 controller you use? And so on.
>
>> My main problem already only;
>>
>> After when I turn off the soundcard and/or the laptop, I need to start
>> again the ffado-mixer to turning on the channels (default: every channel
>> muted, or inactive). I'd appreciate some stuff that resolves the basic
>> settings, I only need the 1/2 sreaming out and 1/2 analog input. Thats all.
>>
>> (sometimes when I restart the system and the soundcard still on power
>> (external ps) the settings are retained)
> This is not supported in ALSA bebob driver because it can be implemented
> in user land. Please use ffado-dbus-server/ffado-mixer or
> libhinawa/hinawa-utils.
>
>
> Regards
>
> Takashi Sakamoto

  reply	other threads:[~2016-10-27 14:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPzTivG=yDAbFZo+u5qauE_LdpqhUM5fT9MT9+hrmi3gTsTGqw@mail.gmail.com>
2016-10-21 23:09 ` M-audio Audiophile Firewire Takashi Sakamoto
2016-10-21 23:51   ` Takashi Sakamoto
     [not found]     ` <CAPzTivEubUhef5LR_p3y0_4TZtbwoLimvzU-tx=xmUhBnT+T0g@mail.gmail.com>
     [not found]       ` <CAPzTivHypNMZvBVBks=wpx1XakELyeWsBVD9mpq-risb_DtH=Q@mail.gmail.com>
2016-10-23  4:54         ` Takashi Sakamoto
2016-10-23  9:03           ` Peti Pap
2016-10-23  9:23             ` Takashi Sakamoto
2016-10-23 10:48               ` Peti Pap
2016-10-23 18:22                 ` Peti Pap
2016-10-23 22:43                   ` [FFADO-devel] " Jonathan Woithe
2016-10-26 19:03                     ` Pap Peti
2016-10-26 19:25                     ` Pap Peti
2016-10-26 23:47                       ` Takashi Sakamoto
2016-10-27 14:10                         ` Pap Peti [this message]
2016-10-28  1:30                           ` Takashi Sakamoto
2016-11-01 13:54                             ` Pap Peti
2016-11-01 15:38                               ` Pap Peti

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=80a6876e-6ced-7daa-7268-1277850c8270@gmail.com \
    --to=roachkiller44@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ffado-devel@lists.sf.net \
    --cc=jwoithe@just42.net \
    --cc=o-takashi@sakamocchi.jp \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).