AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libffado (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I confirm this bug with my AudioFirePre8.
I generate this bug in the way below:
1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA).
2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB
3.Prepare reliable MIDI playback and capture software. I utilize "kmidimon" for playback and "amidi" for capture.
Using "kmidimon" and "a2j" togather, software MIDI playback port is connected to jackd's MIDI subsystem.
"amidi" can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem.
4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports.
See "connection.png".
5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB.
I use "control.mid" as playback MIDI data. It includes control change events of 00 control in channel 1.
The captured data is converted to text data, result_XXXX.log.
6.Compare playback and capture MIDI bytes.
When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz.
And at 88.2 and 96kHz, the capture data varies in each playback.
This bug also appear in current upstream, svn revision 2299.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libffado2 2.0.99+
ProcVersionSign
Uname: Linux 3.5.0-28-generic x86_64
NonfreeKernelMo
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Sat Apr 20 23:01:31 2013
InstallationDate: Installed on 2011-12-18 (489 days ago)
InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
MarkForUpload: True
SourcePackage: libffado
UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago)
Changed in libffado (Ubuntu): | |
status: | New → Incomplete |
Unfortunately, FFADO does not have the manpower to monitor bugs in distributor- specific trackers. Furthermore, unless someone tells us about such an entry (as has been the case here) we'll never even find out about them. To ensure that this issue is properly tracked by the project, please create an account on www.ffado.org and then file a ticket on our bugtracker at subversion. ffado.org. Thanks.
We apologise for the inconvenience.