Hi Florian

2012/10/4 Florian Jung <florian.a.jung@web.de>
Am 03.10.2012 22:29, schrieb Robert Jonsson:
> Hi,
>
> I've always thought it unnecessary that AudioInputs and Wave tracks are
> created in stereo and that AudioInputs are muted.
> Some weeks ago Dan MacDonald also questioned these practices (not the least
> the muting), this pushed me over the edge and I've now
> changed these to be instantiated unmuted and in mono. Other tracks are left
> as is which seems reasonable to me.
> If anyone has issue with this we can discuss it.


Hi

as newbie, it's hard to understand the need/purpose for AudioInput,
AudioOutput and possibly even AudioAux tracks.

Yes, we have talked about this before, I think the flexibility outweigh the extra complexity.
To be frank I don't think it's complicated at all :) but I'm used to it... 

We talked earlier about adding a dialog for setting up lots of tracks/synths/inputs/outputs in one go. This is also an option.
Worth to mention is the "Duplicate tracks" Tim added in the edit menu, I use it all the time to create lots of tracks.
 

Why do i need an additional AudioOutput, i just want to route my
WaveTrack directly into my speaker!

Just to be clear, you only need one output in the generic case. That output is already created in the default template and automatically routed correctly.
 
Why a AudioInput, i directly want to capture from my Microphone!

This does need some additional steps, but this is also where we can benefit the most from the design.

Consider if you are using a software synth that communicates only through jack.
For mixing purposes you really need it to appear in the same mixer as all the rest. Then just connect the synth to an audio input and route it to the correct output so it appears in the mixer.

The documentation for this needs to be written though...

We could possibly make this easier by:
- adding one "Default" audio out for every song (this is actually done
already)
- adding one "Default" audio in, similar to the audio out.

Yes maybe we should do that, I always thought it unclear what it should be connected to but it might not be so hard.
 
- create some setting: have a setting like "auto-route from/to these
tracks: [list]", so that every newly created WaveTrack has [list1]
tracks routed to its input, and has its output routed to [list2]

or do we have that already?

wavetracks are routed to the first output automatically.
Inputs do however not have any automatic handling as it is uncertain what to do. 
I'll think a bit, maybe it's not so hard to add the choice and make a relevant connection.
 
btw, in case we don't have enough new features, but instead only
bugfixes, minor enhancements etc: how about increasing the micro version
number, that is, MusE 2.0.1?

2.0.2 in that case as we already have 2.0.1 :)
But I think before the end of the month we will have enough to make a 2.1 release.

Regards,
Robert
 

greetings
flo




>
> Regards,
> Robert
>
>
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
>
>
>
> _______________________________________________
> Lmuse-developer mailing list
> Lmuse-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lmuse-developer



------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Lmuse-developer mailing list
Lmuse-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmuse-developer