zarb-ml/mageia-dev/20101218/001777.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] mageia sound tasks
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C1292652283.31038.1.camel%40athene%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001776.html">
   <LINK REL="Next"  HREF="001778.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] mageia sound tasks</H1>
    <B>herman</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C1292652283.31038.1.camel%40athene%3E"
       TITLE="[Mageia-dev] mageia sound tasks">herman at aeronetworks.ca
       </A><BR>
    <I>Sat Dec 18 07:04:43 CET 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="001776.html">[Mageia-dev] Choosing packagers representatives
</A></li>
        <LI>Next message: <A HREF="001778.html">[Mageia-dev] mageia sound tasks
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1777">[ date ]</a>
              <a href="thread.html#1777">[ thread ]</a>
              <a href="subject.html#1777">[ subject ]</a>
              <a href="author.html#1777">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>
On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:
&gt;<i> I'm here for sure. Doing subtasks was one of the ideas coming in from several linuxmao.org members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.
</I>&gt;<i> But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.
</I>&gt;<i> 
</I>&gt;<i> I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...
</I>IMHO the most important thing is to make a basic package that works.
The user can then add other things they like.  As things are, it is very
difficult for an ordinary mortal to make a working sound system by
installing individual packages.

</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001776.html">[Mageia-dev] Choosing packagers representatives
</A></li>
	<LI>Next message: <A HREF="001778.html">[Mageia-dev] mageia sound tasks
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1777">[ date ]</a>
              <a href="thread.html#1777">[ thread ]</a>
              <a href="subject.html#1777">[ subject ]</a>
              <a href="author.html#1777">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>