[Desktop-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

2018-05-16 Thread Takashi Sakamoto 
Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755326

Title:
  Periodic glitch in sound with Firewire and snd-dice

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  Not sure if this information can be added afterwards: but I installed
  the  3.19.8 low latency kernel, and the problem disappeared. On 17.1 I
  can't use the current low latency kernel because the system becomes
  very unresponsive to the point of being hard to even log in. So I'm
  not sure if this is just a matter of difference between the low
  latency and regular kernels.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', 
'/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', 
'/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=2446385e-9b65-4ff6-

[Desktop-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

2018-05-16 Thread Takashi Sakamoto 
Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1755326

Title:
  Periodic glitch in sound with Firewire and snd-dice

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  Not sure if this information can be added afterwards: but I installed
  the  3.19.8 low latency kernel, and the problem disappeared. On 17.1 I
  can't use the current low latency kernel because the system becomes
  very unresponsive to the point of being hard to even log in. So I'm
  not sure if this is just a matter of difference between the low
  latency and regular kernels.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', 
'/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', 
'/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=2446385e-9b65-4ff6-

[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller

2016-05-14 Thread Takashi Sakamoto 
This is partly fixed at upstream of PulseAudio. And a new package has
already released for Ubuntu 16.04.

In detail, please refer to this commit.
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/udev-util.c?id=3ac73598c67cb59a318c8baaf33fe97eed1e0b3e

Thanks.

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Takashi Sakamoto (mocchi)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1381475

Title:
  Firewire sound card registered by the name of the fw controller

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use "help" for usage information.
  >>> 4 sink(s) available.
  [...]
  index: 2
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "PHASE 88 Rack FW PCM"
alsa.id = "BeBoB"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "PHASE 88 Rack FW"
alsa.long_card_name = "TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a"
alsa.driver_name = "snd_bebob"
device.bus_path = "pci-:01:09.0"
sysfs.path = 
"/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0"
udev.id = "firewire-0x000aac0300592827"
device.bus = "firewire"
device.vendor.name = "Texas Instruments"
device.product.name = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
device.string = "hw:0"
device.buffering.buffer_size = "163840"
device.buffering.fragment_size = "81920"
device.access_mode = "mmap+timer"
device.profile.name = "10-channels"
device.profile.description = "10 Channels"
device.description = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels"
alsa.mixer_name = "PHASE 88 Rack FW"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-firewire"

  
  PulseAudio 1:4.0-0ubuntu11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] Re: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2015-06-17 Thread Takashi Sakamoto 
** Changed in: libffado (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in libffado package in Ubuntu:
  Incomplete

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-20 Thread Takashi Sakamoto 
Hi David,

> The ID_MODEL_FROM_DATABASE is probably set (for the firewire controller) by 
> udev/systemd,
> see the "hwdb" directory of systemd sources.

Exactly. I've already realized it and it require discussion between
ALSA, PulseAudio and systemd about which part of userspace has these
information for FireWire sound devices. This requires a batch of time so
I made it pending. Currently I would like to concentrate on my work for
ALSA kernel-land.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1381475

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use "help" for usage information.
  >>> 4 sink(s) available.
  [...]
  index: 2
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "PHASE 88 Rack FW PCM"
alsa.id = "BeBoB"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "PHASE 88 Rack FW"
alsa.long_card_name = "TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a"
alsa.driver_name = "snd_bebob"
device.bus_path = "pci-:01:09.0"
sysfs.path = 
"/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0"
udev.id = "firewire-0x000aac0300592827"
device.bus = "firewire"
device.vendor.name = "Texas Instruments"
device.product.name = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
device.string = "hw:0"
device.buffering.buffer_size = "163840"
device.buffering.fragment_size = "81920"
device.access_mode = "mmap+timer"
device.profile.name = "10-channels"
device.profile.description = "10 Channels"
device.description = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels"
alsa.mixer_name = "PHASE 88 Rack FW"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-firewire"

  
  PulseAudio 1:4.0-0ubuntu11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-19 Thread Takashi Sakamoto 
FYI, a part of my work is already included in Linux 3.16 or later. In
this bug, the reporter uses my breeding-edge in github.com, thus you may
have an idea that this is due to out-of-tree kernel modules. But you can
actually see the same issue on Ubuntu utopic.

http://packages.ubuntu.com/utopic/amd64/linux-image-extra-3.16.0-23-generic/filelist
(You can see 
/lib/modules/3.16.0-23-generic/kernel/sound/firewire/bebob/snd-bebob.ko in this 
list.)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1381475

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use "help" for usage information.
  >>> 4 sink(s) available.
  [...]
  index: 2
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "PHASE 88 Rack FW PCM"
alsa.id = "BeBoB"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "PHASE 88 Rack FW"
alsa.long_card_name = "TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a"
alsa.driver_name = "snd_bebob"
device.bus_path = "pci-:01:09.0"
sysfs.path = 
"/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0"
udev.id = "firewire-0x000aac0300592827"
device.bus = "firewire"
device.vendor.name = "Texas Instruments"
device.product.name = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
device.string = "hw:0"
device.buffering.buffer_size = "163840"
device.buffering.fragment_size = "81920"
device.access_mode = "mmap+timer"
device.profile.name = "10-channels"
device.profile.description = "10 Channels"
device.description = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels"
alsa.mixer_name = "PHASE 88 Rack FW"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-firewire"

  
  PulseAudio 1:4.0-0ubuntu11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-19 Thread Takashi Sakamoto 
Hi,

I'm an authour of this kernel module (snd-bebob), I think you already
know.

I'll explain about the naming rule for ALSA FireWire drivers.

struct snd_ctl_card_info.driver[16]
=> BeBoB/Fireworks/OXFW/Dice/Digi00x etc...
struct snd_ctl_card_info.name[32]
=> 'model name' from config ROM, see below
struct snd_ctl_card_info.longname[80]
=> a joined string of 'vendor name', 'model name', bus speed etc... 
Sometimes truncated.
struct snd_ctl_card_info.mixername[80]
=> not important because these modules basically has no control elements
struct snd_ctl_card_info.components[128]
=> not filled

The 'config ROM' is defined in IEEE 1212 and IEEE 1394. Generally, each
device on IEEE 1394 bus have its information in the same register
defined in these specifications. In the information, vendor and model
name is included and the kernel modules refers to them.

You can see actual examples of the information in config ROM in ffado page:
http://subversion.ffado.org/wiki/AvcModels

For example,
http://subversion.ffado.org/wiki/AvcModels/TerratecPhase88

{{{
Config ROM
Current Node Id:0
GUID:   0x000aac0300d99287
Vendor Name:TerraTec Electronic GmbH
Model Name: PHASE 88 Rack FW
...
}}}

Well, I reccomend you to use struct snd_ctl_card_info.name[32] for shown
name. It can be retrieved by snd_ctl_card_info_get_name().

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1381475

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use "help" for usage information.
  >>> 4 sink(s) available.
  [...]
  index: 2
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "PHASE 88 Rack FW PCM"
alsa.id = "BeBoB"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "PHASE 88 Rack FW"
alsa.long_card_name = "TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a"
alsa.driver_name = "snd_bebob"
device.bus_path = "pci-:01:09.0"
sysfs.path = 
"/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0"
udev.id = "firewire-0x000aac0300592827"
device.bus = "firewire"
device.vendor.name = "Texas Instruments"
device.product.name = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
device.string = "hw:0"
device.buffering.buffer_size = "163840"
device.buffering.fragment_size = "81920"
device.access_mode = "mmap+timer"
device.profile.name = "10-channels"
device.profile.description = "10 Channels"
device.description = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels"
alsa.mixer_name = "PHASE 88 Rack FW"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-firewire"

[Desktop-packages] [Bug 1097308] Re: Echo Audiofire 12 not working on Ubuntu 12.10

2013-12-13 Thread Takashi Sakamoto 
Hi,

I'm an upstream developer. I applied solutions for this issue at
r2451/2452.

http://subversion.ffado.org/changeset/2451
http://subversion.ffado.org/changeset/2452

Would you test current upstream?

Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1097308

Title:
  Echo Audiofire 12 not working on Ubuntu 12.10

Status in “libffado” package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 12.10, but my Echo Audiofire 12 interface (a fully 
supported device) doesn't work in my system.
  I've installed FFADO-mixer, but it won't start because:

  15:56:31 logginghandler: Could not communicate with the FFADO DBus
  service...

  Running ffado-dbus-server results in:

  adriano@adriano-Ubuntu:~$ ffado-dbus-server
  Cannot create thread 1 Operation not permitted
  ---
  FFADO Control DBUS service
  Part of the FFADO project -- www.ffado.org
  Version: 2.999.0-
  (C) 2008, Pieter Palmers
  This program comes with ABSOLUTELY NO WARRANTY.
  ---

  ERROR: messagebuffer not initialized: Discovering devices...
  ERROR: messagebuffer not initialized: 18287510873: Warning 
(ieee1394service.cpp)[ 375] initialize: Could not set SPLIT_TIMEOUT to min 
requested (100)
  ERROR: messagebuffer not initialized: 18287510953: Warning 
(ieee1394service.cpp)[ 379] initialize: Set SPLIT_TIMEOUT to min requested 
(100) did not succeed
  ERROR: messagebuffer not initialized: 18287839982: Warning (efc_avc_cmd.cpp)[ 
90] deserialize: Deserialization failed
  ERROR: messagebuffer not initialized: 18287840153: Error 
(fireworks_device.cpp)[ 217] doEfcOverAVC: EfcOverAVCCmd command failed
  ERROR: messagebuffer not initialized: 18287840175: Error 
(fireworks_device.cpp)[ 738] readFlash: Flash read failed for block 0x8000 
(64 quadlets)
  ERROR: messagebuffer not initialized: 18287840193: Error 
(fireworks_session_block.cpp)[ 129] loadFromDevice: Flash read failed
  ERROR: messagebuffer not initialized: 18287840208: Error 
(fireworks_device.cpp)[ 427] loadSession: Could not load session block
  ERROR: messagebuffer not initialized: 18287840220: Warning 
(fireworks_device.cpp)[ 367] buildMixer: Could not load session
  ERROR: messagebuffer not initialized: 18287840475: Warning (efc_avc_cmd.cpp)[ 
90] deserialize: Deserialization failed
  ERROR: messagebuffer not initialized: 18287840555: Error 
(fireworks_device.cpp)[ 217] doEfcOverAVC: EfcOverAVCCmd command failed
  ERROR: messagebuffer not initialized: 18287840567: Error 
(fireworks_device.cpp)[ 624] getClock: Could not get clock info
  Errore di segmentazione (core dump creato)

  ffado-test ListDevices results in:

  adriano@adriano-Ubuntu:~$ ffado-test ListDevices
  Cannot create thread 1 Operation not permitted
  ---
  FFADO test and diagnostic utility
  Part of the FFADO project -- www.ffado.org
  Version: 2.999.0-
  (C) 2008, Daniel Wagner, Pieter Palmers
  This program comes with ABSOLUTELY NO WARRANTY.
  ---

  === 1394 PORT 0 ===
Node id GUID VendorId ModelId Vendor - Model
 0 0x0014865e75918c0e 0x1486 0xAF12 Echo Digital Audio - AudioFire12
  ERROR: messagebuffer not initialized: 18452596596: Error (configrom.cpp)[ 
150] initialize: Could not parse config rom of node 1 on port 0

  Here is the output of ffado-test Discover:

  adriano@adriano-Ubuntu:~$ ffado-test Discover
  Cannot create thread 1 Operation not permitted
  ---
  FFADO test and diagnostic utility
  Part of the FFADO project -- www.ffado.org
  Version: 2.999.0-
  (C) 2008, Daniel Wagner, Pieter Palmers
  This program comes with ABSOLUTELY NO WARRANTY.
  ---

  ERROR: messagebuffer not initialized: 18545396667: Warning 
(ieee1394service.cpp)[ 375] initialize: Could not set SPLIT_TIMEOUT to min 
requested (100)
  ERROR: messagebuffer not initialized: 18545396728: Warning 
(ieee1394service.cpp)[ 379] initialize: Set SPLIT_TIMEOUT to min requested 
(100) did not succeed
  ERROR: messagebuffer not initialized: 18545719198: Warning (efc_avc_cmd.cpp)[ 
90] deserialize: Deserialization failed
  ERROR: messagebuffer not initialized: 18545719337: Error 
(fireworks_device.cpp)[ 217] doEfcOverAVC: EfcOverAVCCmd command failed
  ERROR: messagebuffer not initialized: 18545719358: Error 
(fireworks_device.cpp)[ 738] readFlash: Flash read failed for block 0x8000 
(64 quadlets)
  ERROR: messagebuffer not initialized: 18545719376: Error 
(fireworks_session_block.cpp)[ 129] loadFromDevice: Flash read failed
  ERROR: messagebuffer not initialized: 18545719391: Error 
(fireworks_device.cpp)[ 427] loadSession: Could not load session block
  ERROR: messagebuffer not initialized: 18545719403: Warning

[Desktop-packages] [Bug 619752] Re: Ubuntu couldn output sound through the Presonus Firebox

2013-12-13 Thread Takashi Sakamoto 
Hi,

I'm an upstream developer. I applied a solution for this issue at r2451 and 
r2452.
http://subversion.ffado.org/changeset/2451
http://subversion.ffado.org/changeset/2452

Would you please test the latest sources?

Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/619752

Title:
  Ubuntu couldn output sound through the Presonus Firebox

Status in “libffado” package in Ubuntu:
  New

Bug description:
  Ubuntu 10.10 Alpha 3
  Sound: Presonus Firebox 
http://www.presonus.com/products/Detail.aspx?ProductId=4
  Workaround with jack2 are very glitch, and a lot of application works only 
with pulse audio.
  FFADO prodect make driver only for jack2: http://www.ffado.org/

  Please, fix that pulseaudio could work with Presonus Firebox audio
  card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/619752/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
** Attachment added: "result_96000_1.log"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649077/+files/result_96000_1.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
** Attachment added: "result_96000_2.log"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649078/+files/result_96000_2.log

** Description changed:

  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.
+   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".
+   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_.log.
+   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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

** Summary changed:

- MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 
96.0 kHz
+ AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback 
runs at 88.2 and 96.0 kHz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
** Attachment added: "result_88200.log"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649076/+files/result_88200.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
** Attachment added: "connection.png"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649072/+files/connection.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
** Attachment added: "result_48000.log"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649075/+files/result_48000.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
** Attachment added: "result_44100.log"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649074/+files/result_44100.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
** Attachment added: "control.mid"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649073/+files/control.mid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1170949] [NEW] AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz

2013-04-20 Thread Takashi Sakamoto 
Public bug reported:

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_.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+svn2019-1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
Uname: Linux 3.5.0-28-generic x86_64
NonfreeKernelModules: nvidia
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)

** Affects: libffado (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jackd libffado quantal

** Attachment added: "connection.png"
   
https://bugs.launchpad.net/bugs/1170949/+attachment/3649069/+files/connection.png

** Attachment removed: "connection.png"
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649069/+files/connection.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libffado in Ubuntu.
https://bugs.launchpad.net/bugs/1170949

Title:
  AudioFirePre8, MIDI data from hardware port is invalid when MIDI
  playback runs at 88.2 and 96.0 kHz

Status in “libffado” package in Ubuntu:
  New

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_.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+svn2019-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp