gmidimonitor 3.6+dfsg0-4build3 source package in Ubuntu
Changelog
gmidimonitor (3.6+dfsg0-4build3) noble; urgency=medium * No-change rebuild against libasound2t64 -- Steve Langasek <email address hidden> Sun, 07 Apr 2024 07:14:42 +0000
Upload details
- Uploaded by:
- Steve Langasek
- Uploaded to:
- Noble
- Original maintainer:
- Ubuntu Developers
- Architectures:
- any
- Section:
- sound
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Oracular | release | universe | sound | |
Noble | release | universe | sound |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
gmidimonitor_3.6+dfsg0.orig.tar.bz2 | 114.8 KiB | 424f3db7941fd653e7c331e80bc633a0a449e6af75e59e6d6088c708e1b280c9 |
gmidimonitor_3.6+dfsg0-4build3.debian.tar.xz | 131.0 KiB | d2c3f3d779fce18754f3456d60c91ab5352d202e968566bf31583da7a8c7553e |
gmidimonitor_3.6+dfsg0-4build3.dsc | 2.2 KiB | 0fe746fdaea5186b5141934ed20a923a39bc8aba575ab20ba21c3a4633befad0 |
Available diffs
- diff from 3.6+dfsg0-4build2 to 3.6+dfsg0-4build3 (330 bytes)
Binary packages built by this source
- gmidimonitor: GTK+ application that shows MIDI events
GMIDImonitor is GTK+ application that shows MIDI events.
.
You need to connect desired source of MIDI events to gmidimonitor
input using some kind of patchbay like qjackctl, patchage. For
restoring connections (not connecting every time) you can use LASH.
- gmidimonitor-dbgsym: debug symbols for gmidimonitor