Had a good chat with Adrian Likins, Steven Salevan and Luke Macken today
about what a "music collaboration server" might look like. Here's a whole
firehose full of notes. To Adrian/Steven/Luke, this'll probably mean more
-- but any questions, feel free to ask. :)
We're getting together again here in Red Hat HQ to brainstorm more about
possible clients on Thursday. For those of you on the list who aren't
from around here, apologies, and we'll start filling in gaps soon.
--g
=======================================================================
The Four Steps
--------------
1. EXPORT TOOLS AND RULES. Figure out how to get output from every major
music production tool into a simple, common format. If it's tools that
plug in to GarageBand/Steinberg/Logic, great. If it's a 20-step HOWTO for
each of those tools, great. The end result: wav/midi files, per track,
that can be easily shared.
2. DEFINE COMMON METADATA FORMAT. Rough database schema follows.
3. REPOSITORY FOR METADATA. Ditto.
4. UPLOAD TOOLS. We need some simple way of getting "sharable" data into
the system initially.
The WAG at Schema
-----------------
user
email varchar
password varchar
asset
(a superclass, subclassed per asset type)
id varchar (md5sum)
creator_id fk (user.email)
license_id fk (license table)
uri varchar
creation_date date
music_asset
(a subclass of asset, we thus leave the possibility of video/clipart/etc.)
asset_id fk (asset.id)
lyric_id fk (lyric.id) (nullable)
type? (midi/wav/loop/etc?)
key? varchar?
tempo? varchar?
bpm? int?
others?
lyric
id varchar (md5sum)
author fk (user.email)
authored_date date
song
id varchar (md5sum)
producer_id fk (user.email)
uri varchar
production_date date
song_tracks
song_id fk (song.id)
track_id fk (music_asset.asset_id)
track_parent
track_id fk (music_asset.asset_id)
parent_id fk (music_asset.asset_id)
Other stuff:
tagging schema for songs and tracks
--g
-------------------------------------------------------------
Greg DeKoenigsberg || Fedora Project || fedoraproject.org
Be an Ambassador || http://fedoraproject.org/wiki/Ambassadors
-------------------------------------------------------------
1. Fresh install of Fedora Core 5 x86_64 on a fancy new AMD X2 3800+.
2. su - (and enter the password to obtain the mythical root superpowers)
3. rpm --import
http://ccrma.stanford.edu/planetccrma/RPM-GPG-KEY.planetccrma.txt
4. rpm -Uvh
http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/5/i38…
No errors so far. Everybody's happy. But this serenity will not last for
long...
5. yum check-update
Yum bails with a 404, followed by [errno 256 - no more mirrors to try]
or something similar. The GUI package manager (pirut?) fails to load now
as well.
Grr.
-David
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=191239
Final comment says:
> Looks good. I can't give final approval, but this is approve-able in
> my opinion. Someone please sponsor Fernando, we need him. :)
So.... where do I go from here? I have other packages I'd like to submit
as well (and qsynth[*] is waiting and has had no comments so far - I
doubt it is a perfect package! :-)
Qjackctl is really needed if you want to actually use the recently
released jack package in Extras.
-- Fernando
[*] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=191538