Fwd: [NEW Spins websites] Functional spins
by Brendan Jones
Apologies for top posting. If anyone has any suggestions on the featured
applications list for the spin website, please reply. Robert is also
asking for icons, so if there are any goods ones you know of please let
me know.
Obvious ones:
Ardour
Qtractor
Frescobaldi
Hydrogen
?
?
-------- Forwarded Message --------
Subject: Re: [NEW Spins websites] Functional spins
Date: Wed, 6 May 2015 22:14:58 +0200
From: Robert Mayr <robyduck(a)fedoraproject.org>
To: amitksaha(a)fedoraproject.org, Bruno Wolff III <bruno(a)wolff.to>,
timn(a)fedoraproject.org, rmattes(a)fedoraproject.org, Joerg Simon
<jsimon(a)fedoraproject.org>, fab(a)fedoraproject.org, Brendan Jones
<brendan.jones.it(a)gmail.com>, Jørn Lomax <northlomax(a)gmail.com>, Máirín
Duffy <duffy(a)redhat.com>
Hi all,
we are now very close to F22 and we still have no features for your
spins, except design and scientific who replied immediately (thank you!).
I think the websites should in some way interest you, in my eyes they
are the connection between end users and Spin SIGs.
I'm not worried about the description or the content we already have on
the old spins.fpo website. I'd like to know from you which features are
characteristic for your spin, you should also provide the SVG icon and a
small text description. If this is not possible, please give us urgently
a list of the features, as shown in:
http://labs.stg.fedoraproject.org/it/design-suite/
http://labs.stg.fedoraproject.org/it/scientific/
You can reply to this email and I can look for the rest if you are not
interested in providing icons or text.
Sorry for speaking so frankly, but I really don't understand why only
few SIGs are responsive here. We need to code the pages within this week
to give l10n teams the chance to translate the websites in time.
I hope to hear soon from you.
Thank you.
Robert
2015-04-25 15:33 GMT+02:00 Robert Mayr <robyduck(a)fedoraproject.org
<mailto:robyduck@fedoraproject.org>>:
Dear Spin owners,
probably you heard it already but after getfedora.org
<http://getfedora.org> for F21, the websites team is redesigning
spins.fedoraproject.org <http://spins.fedoraproject.org> and we
decided to split the content there in desktop spins and functional
spins.
The Spins you own actually will go under a complete new website,
labs.fedoraproject.org.[1] We are already working on it and I made
an example for the Design Suite to show you how it will look like. [2]
All Spins will have their own space and therefore I'm asking you to
help us with the content. I should be able to write all the rest,
but as you can see we want to promote the most important features of
every single Spin, in order to give end-users an overview of what
they get when installing your spin.
It would be very helpful if you could reply with a list of features
and some short description of them, maybe also with an SVG of the
icon if it's spin related. Otherwise I can try to find one somewhere
else.
We don't have much time left until F22 final release and labs.fpo
will not be the only new website. Be so kind and try to get back to
me ASAP, we need to code the pages and give translators some time to
work on it.
For any question o doubt feel free to contact me.
Thank you.
[1]
https://github.com/fedoradesign/fedora-spins/blob/master/functional/labs-...
[2]
https://github.com/fedoradesign/fedora-spins/blob/master/functional/spins...
(these are design mockups, but both pages are already web-coded).
See also a blogpost from Mairin:
[3]
http://blog.linuxgrrl.com/2015/04/23/redesign-of-spins-fedoraproject-org-...
--
Robert Mayr
(robyduck)
7 years, 11 months
Re: [Fedora-music-list] No output from Focusrite Scarlett with kernel 4.x
by Jeff Sandys
> Can you run lsmod with both the working and non working kernel and paste
in the output?
Short version:
lsmod for kernel 4.0.5-200.fc21.x86_64 inculdes:
snd_seq_midi_event
snd_seq_midi
x86_pkg_temp_thermal
that are not listed in lsmod for 3.18.9-201.rt5.1.fc21.ccrma.x86_64+rt
snd_seq have used by snd_seq_midi_event snd_seq_midi
snd_rawmidi, snd_seq_device, and snd_seq_midi_event have used by
snd_seq_midi
Other snd modules listed in both are:
snd snd_hda_codec
snd_hda_codec_generic
snd_hda_codec_hdmi
snd_hda_codec_via
snd_hda_controller
snd_hda_intel
snd_hwdep
snd_pcm
snd_rawmidi
snd_seq
snd_seq_device
snd_timer
snd_usb_audio
snd_usbmidi_lib
soundcore
-- Jeff
7 years, 11 months
Re: [Fedora-music-list] No output from Focusrite Scarlett with kernel 4.x
by Jeff Sandys
> Have you checked that the outputs are not muted or at 0 volume in alsamixer?
I forgot to check alsamixer. But the settings in --does not work--
4.0.4-201.fc21.x86_64, are the same as in --does work--
3.18.9-201.rt5.fc21.ccrma.x86_64+rt (only 3. kernel I have available).
It looks like I can set all the parameters on the Scarlett (except
sample rate?) with alsamixer, so I don't need to use Windows to set
up the device, sweet.
-- Jeff
On 06/27/2015 01:39 PM, Jeff Sandys wrote:
>* I do not get any audio output with my Focusrite Scarlett 18i8 with any
*>* of the 4. kernels from Fedora or CCRMA. The audio input works and all
*>* the audio I/O ports are visible in jack and pulseaudio. Audio output
*>* still works with kernel 3.18.9-201.rt5.1.fc21.ccrma.x86_64, the only 3.
*>* kernel left on my computer.
*>>* Where should I submit this bug?
*>>* Thanks,
*>* Jeff
*>
7 years, 11 months
No output from Focusrite Scarlett with kernel 4.x
by Jeff Sandys
I do not get any audio output with my Focusrite Scarlett 18i8 with any of
the 4. kernels from Fedora or CCRMA. The audio input works and all the
audio I/O ports are visible in jack and pulseaudio. Audio output still
works with kernel 3.18.9-201.rt5.1.fc21.ccrma.x86_64, the only 3. kernel
left on my computer.
Where should I submit this bug?
Thanks,
Jeff
7 years, 11 months
Fedora 22 problems with Pianoteq
by Martin Tarenskeen
Hi,
Pianoteq is one of the few commmercial music software packages that are
available also for the Linux platform. And I find it worth paying for and
have been enjoying my Licence since Pianoteq version 3.
But since my update to Fedora 22 I have some mysterious problems running
Pianoteq 5 from the commandline. (No such problems I think on Fedora 21).
I am using 64 bits Fedora 22. The problems only occur if I run the 64 bits
Pianoteq binary. I have also some 32 bits libraries installed on my
system. If I run the 32 bits version of Pianoteq on my system, the
problems don't seem to occur. There is a demo version available on
www.pianoteq.com if you want to try Pianoteq. I am especially interested
if other Fedora 22 users are able to reproduce my issues. Or if people
still using Fedora 21 or older don't see these problems happening.
If there really is a problem with Fedora 22 I would like to find what
exactly goes wrong, so that I can send a bug report to the right place.
Until now this is a big mystery for me.
examples:
$ amd64/Pianoteq\ 5 --version
Pianoteq version 5.2.1/20150428 -- http://www.pianoteq.com
Copyright (c) #PROBLEM: HERE IT EXITS
$ i386/Pianoteq\ 5 --version
Pianoteq version 5.2.1/20150428 -- http://www.pianoteq.com
Copyright (c) 2015 Modartt. #THIS IS CORRECT
$ amd64/Pianoteq\ 5 --help
Pianoteq version 5.2.1/20150428 -- http://www.pianoteq.com
Copyright (c) #PROBLEM: HERE IT EXITS
$ i386/Pianoteq\ 5 --help #THIS WORKS AS EXPECTED
Pianoteq version 5.2.1/20150428 -- http://www.pianoteq.com
Copyright (c) 2015 Modartt.
Options from command-line:
--help : show this help, and quit
--version : show current version number and date, and quit
--no-prefs : start Pianoteq without using any saved preference
--no-audio-prefs : start Pianoteq with a clean audio/midi configuration
--prefs FILENAME : stores the preferences in the specified file
--fxp FILENAME : load an FXP file on startup
--preset NAME : load a preset on startup
--list-presets : display the list of all presets
--midimapping NAME: load a midimapping preset on startup
--midi FILENAME : load a midi file
--wav FILENAME : export midi file as wav, and quit
--rate FREQ : change the sample rate for the exported wav
--bit-depth D : change the bit-depth for the exported wav (16,24 or
32)
--dither ON/OFF : turn dithering when exporting on or off
--mono : export the wav file as mono
--headless : do not show the graphical interface
--fullscreen : start in fullscreen mode
--play : immediately start playing the midi file
--play-and-quit : start playing the midi file, and quit when it ends
Example of use: Pianoteq --preset "U4 Small" --midi foo.mid --wav foo.wav
$ amd64/Pianoteq\ 5 --midi "example.mid" --wav "example.wav"
amd64/Pianoteq\ 5 --midi example.mid --wav example.wav
Current preset: D4 Daily Practice, instrument: Grand D4
Multi-core: got real-time scheduling with priority 16
Writing to example.wav, quality: #PROBLEM: HERE IT EXITS
$ i386/Pianoteq\ 5 --midi "example.mid" --wav "example.wav"
Current preset: D4 Daily Practice, instrument: Grand D4
Writing to example.wav, quality: 0
Multi-core: got real-time scheduling with priority 16
...................... #HERE THE FILE example.wav IS CORRECTLY WRITTEN
--
MT
7 years, 11 months
Motu audio-MIDI interfaces on FEdora 21
by andremartins
Hi there, I have an audioExpress hybrid firewire/usb from MOTU, and I am
running Fedora 21 on X220. Is there any chance that it can work on Pd,
Supercollider or Ardour?
Thanks.
7 years, 12 months
Naming of Ardour packages
by Nils Philippsen
Hi all,
with the advent of Ardour version 4, the question came up why the oldest
available version 2 is packaged as "ardour" rather than the latest one:
https://bugzilla.redhat.com/show_bug.cgi?id=1216055#c15
The reason for keeping version 2 around is that while later versions can
migrate old sessions, some information is lost in the process. Ardour
version 3 became ardour3 so people could install both versions 2 and 3
side-by-side, and that the new package got reviewed instead of the old
one (which would have been the case had I submitted an ardour2 package
for review). In that vein I packaged version 4 as ardour4, also because
ardour3-4.0.0 would have looked plain silly (despite that the session
files are compatible between versions 3 and 4) and introducing a new
major version replacing the old one with a substantially changed
look-and-feel in an existing Fedora release is a big no-no.
The question posed in the ardour4 review ticket is valid though, so I'd
like to come up with a scheme for the future that achieves these
objectives:
- Installing "ardour" will always get you the latest available version
(on a Fedora release -- e.g. F-20 won't get version 4 because the JACK
package is too old).
- Every major version gets its own package so side-by-side installs are
possible, especially for occasions where the session format changes
(like v2 -> v3).
- Versions which are session-compatible with newer versions get retired
from Fedora releases that aren't stable yet (e.g. v3 because the session
format is the same as with v4).
I'd do it like this (in Fedora >= 22):
- Move version 2 to its own ardour2 package. This would get it
re-reviewed but I guess that's a mere formality.
- Reuse the ardour package as a meta-package which simply requires the
latest versioned package.
- Retire ardour3.
What do you think?
Nils
--
Nils Philippsen "Those who would give up Essential Liberty to purchase
Red Hat a little Temporary Safety, deserve neither Liberty
nils(a)redhat.com nor Safety." -- Benjamin Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
7 years, 12 months
