Good Sunday to all,
2016-01-24 10:32 GMT+01:00 Tim E. Real <[email protected]>:
> >
> > I would not call it "Add audio track"/"Import audio file" because midi
> > and even med files are audio files, too ;-)
>
> Midi and med files are not audio.
>
> I think there was some confusion there, Jens was describing
> the missing wave part event and being very thin too.
>
>
> Anyway, about that naming, maybe we should just unite the two
> midi and wave import functions under one 'import file' item.
>
Indeed a good idea, it's not like we can't distinguish between the two.
>
>
> I want to propose that we add the ability to 'open' a wave file,
> not just import it.
> Notice that our file open dialog filter box says "all known files".
> Thus we should include wave file there.
>
You mean that we take this one step further, if we open a wave file, we
assume it is an import operation?
I was gonna say no, but why not? As I said, we can distinguish between the
file types, we can be fairly certain it should be added/imported.
>
> The reason I say that is that I'm working out the ability to
> 'Open' a pure midi file and auto-load a fluidsynth track
> with a pre-loaded soundfont (the FluidR3).
Yay, very good idea. We'll add the minimized fluidr3 to the muse
installation then?
There will be /no/ usual dialog, warning, or didyouknow
> boxes to pop up, and get in the way, and ruin the experience.
> (Unless there's an error of course.)
>
> Thus MusE attains a sort of 'media player' mode, where you
> just load and play. Like 'Open with MusE' menu associations,
> 'clean' command line opening, etc.
>
> So... If we add wave files to that open dialog, we can load
> the file, and an Audio Output track, and the user is ready to play.
>
> Summary:
> 'Open' a midi file: Auto create a fluidsynth track.
> 'Open' a sound file: Auto create an Audio Output track.
>
> 'Import' a midi file: The usual two options of replace or add.
> 'Import' a wave track: The usual options.
>
> Note: Someone once complained to me that 'importing' a
> midi file did not automatically assign it to a synthesizer track
> if one already existed in the track list. It assigns to hw ports.
> I replied that half the people might want the midi tracks
> to be assigned to the first hardware port(s) found, and the
> other half might want the synthesizer, so it was arbitrary.
> That's stuck in my head all this time.
> But now I think I will try to assign the midi tracks to the first
> available synth track, and if not /then/ the first hw ports.
> Thinking of doing that very soon.
>
>
> All in the name of opening and playing media faster/easier.
> "Easy listening."
>
> T.
/Robert
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
