:48.0 +0100
+++ jack-audio-connection-kit-0.126.0/debian/changelog 2024-03-21
02:03:21.0 +0100
@@ -1,3 +1,9 @@
+jack-audio-connection-kit (1:0.126.0-2+m68k) unreleased; urgency=medium
+
+ * Only B-D: libffado-dev if jackd1-firewire is built
+
+ -- Thorsten Glaser Thu, 21 Mar 2024 02
Package: ffmpeg
Version: 7:4.3.4-0+deb11u1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’ve seen people use ffmpeg to add metadata to .wav files
and wanted to try it.
ffmpeg -i /usr/share/sounds/alsa/Noise.wav -metadata comment='miau mäh mio'
foo.wav
It added an ICMT (good) and an ISFT
Dixi quod…
>I noticed that multimedia-musiciantools Recommends: musescore
>
>It should instead
> Recommends: musescore3
> Suggests: musescore
>for bullseye.
multimedia-guitar=0.10 (built from the same source package)
Suggests musescore; it probably should Suggests musescore3
instead thus.
bye,
Package: multimedia-musiciantools
Version: 0.10
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I noticed that multimedia-musiciantools Recommends: musescore
It should instead
Recommends: musescore3
Suggests: musescore
for bullseye.
Rationale: musescore3 is the recent version of MuseScore and
On Thu, 28 Jan 2021, Felipe Sateler wrote:
> No, I'm not. As a matter of fact, I've been grossly neglecting stk
> since a few years. Maybe you could be interested in taking over? It is
> not much maintenance, but the annoyance is the unstable-abi that
> requires transitions on each update.
Hi maintainers,
are you planning to backport stk? This would be a prerequisite for
a backport of polyphone; I could have a look at it myself if simply
rebuilding would work, or if there’s not too much CFrustFrust involved.
(I actually have the same question about bionic-backports, but I’ve
got
Package: jackd2
Version: 1.9.16~dfsg-1
Severity: minor
X-Debbugs-Cc: t...@mirbsd.de
From the following information in the MuseScore fora…
> beatboxchad • Oct 17, 2020 - 20:52
>
>| In reply to Sorry - I thought the linked… by willy3
>
>> JACK does MIDI routing, but it doesn't implement a lot of
Package: libasound2
Version: 1.2.4-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, debian-multimedia@lists.debian.org
Control: notfound -1 1.2.3.2-1+b1
The latest libasound2 introduced a severe regression:
Starting musescore3 and loading a score, e.g. like this…
$ musescore3
Sebastian Ramacher dixit:
>That looks like the expected difference between the amd64 and arm64
>packages. So what issues are you seeing?
Oh, interesting. I was using p.d.o to search for RtMidi.h
and found this divergence in the file lists on p.d.o…
>>
Package: librtmidi-dev
Version: 3.0.0~ds1-2+b1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
The amd64 package…
https://packages.debian.org/sid/amd64/librtmidi-dev/filelist
/usr/include/rtmidi/RtMidi.h
/usr/include/rtmidi/rtmidi_c.h
/usr/lib/x86_64-linux-gnu/librtmidi.so
tags 964576 + patch
thanks
On Wed, 8 Jul 2020, Thorsten Glaser wrote:
> dav1d misdetects x32 as amd64, leading to failures such as:
>
> /usr/bin/ld: i386:x86-64 architecture of input file
> `src/25a6634@@dav1d@sha/loopfilter.obj' is incompatible with i386:x64-32
> output
d
Source: dav1d
Version: 0.7.1-2
Severity: important
Tags: ftbfs
Justification: fails to build from source, debian-ports architecture
dav1d misdetects x32 as amd64, leading to failures such as:
/usr/bin/ld: i386:x86-64 architecture of input file
`src/25a6634@@dav1d@sha/loopfilter.obj' is
Fabian Greffrath dixit:
> https://sourceforge.net/p/mscore/code/3412/
>
> Where did you find the corresponding commit on Github?
https://github.com/musescore/musescore-old/commit/90c33ef9d87b3f5ff92efd3b07d89eb455fb1fef
But SVN is probably the primary source, I just couldn’t
be bothered with
Fabian Greffrath dixit:
> Just realized this conversation is nearly one year old now...
Yeah, I found it buried under more TODOs…
> Well, I fail to see in which mysterious way you formatted musescore's
Human-readable format, standard Debian, but with Debian specifics
on top, then “Licence:”,
Fabian Greffrath dixit:
>Am Freitag, den 02.08.2019, 21:46 + schrieb Thorsten Glaser:
>> >Do you wish to adapt that? I can commit how I imagine that to
>> >work, if you want.
>
>I am not exactly sure I understand what you mean here? You want to
>embed licensin
Hi Thomas,
>as a special favour to Thorsten, I added the 'u' key now for the
>upcoming mpg123 1.26.0 to (un)mute in the audio backend, at the end of
>the optional buffer, so that it works immediately like pause.
thanks!
>This was not as easy as it sounds, as I wrote the output library
[…]
Dennis Braun dixit:
>first of all this is a feature request for the upstream project and not
>for debian.
Yes, I know, hence I tagged it with “upstream”, and…
>here you can go to make a feature request for mpg123:
>https://sourceforge.net/p/mpg123/bugs/
… while maybe I could, I would have
Thomas Orgis dixit:
>any special reason why this suggestion is not posted to the mpg123 bug tracker,
>or just even just mailed to upstream, but reported to the Debian project
>instead?
Because reportbug is easier and the package maintainer should
forward them as part of their regular duties and
Package: mpg123
Version: 1.25.13-1
Severity: wishlist
Tags: upstream
I often control the volume of playback inside mpg123, not
with alsamixer as the latter is less ephemeral. However,
occasionally, I wish to listen to something else for a
minute and come back.
With playing files, it’s easy to
Package: libfluidsynth1
Version: 1.1.11-4
Severity: normal
Hi Fabian,
since you moved the dependency on timgm6mb-soundfont|sf3-soundfont-gm
to Depends and versioned timgm6mb-soundfont, the Breaks are now more
hindering than helpful; please remove them.
Thanks!
-- System Information:
Debian
Dixi quod…
>so where does the GPLv2-only snippet come from? Not even
From https://musescore.org/en/node/1463#comment-9168
apparently. (I’m a bit wary about blanket PD statements,
but…)
bye,
//mirabilos
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God
Dixi quod…
>Fabian Greffrath dixit:
>
>>Agreed, then I'll prepare timgm6mb-soundfont for upload now.
>
>I just noticed that the soundfont itself is GPLv2… (only?)
>in mine I use a script that edits the .sf2 to update metadata
>like author or licence, perhaps you want to embed the licence
>grant
severity 906144 serious
reassign 906144 libmypaint-common
found 906144 1.3.0-2.1
thanks
As documented in #894757, gimp and mypaint not being coïnstallable is
clearly RC.
I’ve just poked around: it’s *only* the libmypaint.mo files that
are affected, that is, the translation files of the
Package: ffmpeg
Version: 7:4.1-1
Severity: wishlist
Tags: upstream
size= 155373kB time=03:15:59.53 bitrate= 108.2kbits/s speed=2.76e+03x
During:
for x in *.@(mp4|m4a); do ffmpeg -i "$x" -vn -sn -c:a copy
./"${x%.@(mp4|m4a)}.wma"; done
This is… probably correct, but “2760x” would be
Hi Tiago,
>I've been a bit off from Musescore development, and I even didn't know
>they had released a 3.0 (yay!).
It’s both yay and work. Users will need 2.x available (as well) for
quite some time, since 2.x scores need massive relayout in 3.x, plus
the code tends to crash occasionally and
Hi Tiago,
>So, waiting from upstream answer.
thanks for looking into this… I talked to upstream about this a
while ago and it ended with that they don’t have much interest
in the /etc/papersize thing, which is pretty distro-specific,
but would merge a patch if someone would write it.
I looked
Hi Fabian,
>>* Upload to experimental, again with the revert restriking patch
>
>just out of interest, what's the matter with this patch and what is
>upstream's stance about it?
It basically fixes audio. Upstream wants to have it only
when we have an end-user-friendly UI for assigning MIDI
Hi everyone,
I’ve looked at the development of MuseScore 3 and have made some sort
of plans for it and buster:
I’ll keep MuseScore 2 in unstable/testing in order to have it
available and in good shape in buster and stretch-backports,
and, for *buntu 12.04, 14.04, 16.04, 18.04 and 18.10, the PPA.
Andreas Beckmann dixit:
>Thanks for the explanation.
You’re welcome. Is there a place in the source or binary package
where such an explanation would make sense / be found? Something
like anbe-overrides to go with lintian-overrides ;-)
>You could ship empty directories and let dpkg take care of
tags 910145 + wontfix
close 910145
thanks
Andreas Beckmann dixit:
>during a test with piuparts I noticed your package ships (or creates)
>a broken symlink.
> /usr/share/mscore-2.3/sound/sfz -> ../../sounds/sfz (musescore-common)
> /usr/share/mscore-2.3/sound/sf2 -> ../../sounds/sf2
tags 898757 - moreinfo
tags 898757 + confirmed
severity 898757 important
thanks
Giovanni Mascellani dixit:
>Here you have a backtrace of the startup crash, which I guess is the
>same of the original poster.
It’s on amd64, but thanks anyway, this helps.
>Removing configuration and cache files
severity 898757 normal
tags 898757 + moreinfo
thanks
Hi Rob,
>After displaying the splash screen, Musescore stops
while I understand your frustration this works for others,
so I’m downgrading the severity. I’m even using it on an
i386 system the same as you are.
Please do the following:
32 matches
Mail list logo
