On Sun, Dec 20, 2015 at 09:28:32PM +0900, Takashi Sakamoto wrote: > I note that just powering on, the device is muted. Only with respect to the audio streams from the PC. All other hardware-based routing is set up as per the saved device configuration. > You can de-mute it by write > transaction. For example, by using 'firewire-request' command in > linux-firewire-utils(https://github.com/cladisch/linux-firewire-utils): > > $ ./firewire-request /dev/fw1 write 0x0000801c0000 0x000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000010000000100000001000000 > > Currently, libffado gives no way to do it via its mixer interface. Instead, done > in methods to start streaming. I think it better to move de-mute codes to mixer > initialization. The mutes controlled here apply only to the software audio streams. I suspect they are utilised to eliminate noise during streaming setup and when the device is idle with respect to the computer. When other systems mute individual playback channels under user control they do not use these mutes and instead do it in other ways. The above mutes are only ever turned off and on as part of streaming setup and teardown. As a result, I think Linux should do the same thing because this is the mode of operation used on other systems and is therefore the "supported" approach. In other words, I think we should do what all other systems do with these devices and treat this mute register as a part of the streaming setup procedure. Note in passing that the above firewire-request will only enable output for the first four audio streams. Others (such as ADAT) will remain muted. The correct initialisation of the 28 quadlets at 0x0000801c0000 is to set every quadlet to 1. > There's an issue of periodical hissing noise. I observed this with Fireface 400. > Interval of the noise differs depending on the situation (10-20 minutes) and > continues around 20 seconds. The cause is not clear but I've experienced similar > issue with TASCAM FireOne. A common point between these two models is > non-blocking transmission. I guess that the cause may be on data block > calculation in AMDTP packet streaming layer (calculate_data_blocks() function > in sound/firewire/amdtp-stream.c). Further investigation is required. I've just got back from an week's off-line break and will look at the code once I've caught up on things. I suspect the audio packets are not being timed correctly so over time things get a little out of sync. The timing mentioned above certainly suggests a slow beating. I haven't looked at calculate_data_blocks() yet so I don't know how it works. I suspect that the method of timing data blocks doesn't quite match up with what the Fireface interfaces really expect. There are two "proper" ways to determine whether an audio packet should be sent: 1) Monitor the buffer status bits returned within the incoming audio data stream and send at an appropriate time. 2) Keep track of the time between incoming audio packets and simply mirror that in the output stream. Option 1 is rather difficult in reality and in practice isn't really required. Option 2 is sufficient and is guaranteed to keep everything in sync. As a side comment, FFADO does neither because of the way the RME driver must interface with the rest of the FFADO infrastructure. > In my previous RFC, I described that zero bits have no effect in write > transactions to 0x00008010051c. But this is wrong. The transaction has > side effect to set the other options. That would be correct. 0x00008010051c is the start of the FF400's configuration block. Fields within this set all manner of things including phantom power status, input pads, optical port mode and so on. Blindly writing zeros will force the device into the physical state represented by that zero byte pattern. > In this patchset, the state of clock is changed on the way to initialize > transaction. This is a bit rude but unavoidable. Fortunately, it's > software's responsibility to read from flash memory and set initial > configuration, Not quite. The device powers up with the configuration that is stored in the internal flash memory and does not require any interaction with a computer in order to be functional. Software needs to synchronise itself with this configuration so as to maintain it. Forcing a particular configuration is fine for an initial version of a driver, but in time there is a need to be more sophisticated about how this is handled. The setup of these interfaces can be highly complex and many users rely on the flash memory configuration to avoid time consuming setup at every power on. Forcing a configuration reset like this can certainly be worked around during initial development, but in the long term the driver needs to preserve device status. I have several ideas about how this might look but need to wait to see what framework we have to work within before any of that can be solidified. The primary difficulty is that the configuration register needs to be known by all software components which interact with the device: not just the streaming system. A way to make the configuration available to usespace will be needed. In FFADO this was handled with a shared memory segment so it didn't matter which component (streaming, mixer) was started first. I imagine in FFADO the configuration will be made available via hwdep, /proc/ or something similar, ideally in a manner which is transparent to the type of Fireface device in use. In summary: zeroing out the configuration block is fine for now, but in time this will need to be revisited. Regards jonathan _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
