Re: [Lmuse-developer] jack session support ??

[geoff <ge...@la...>]

Thanks for the heads up Tim. ..I get it's complicated ;)

Best

g


Sent from my smartphone. 

"Tim E. Real" <ter...@ro...> wrote:On April 7, 2013 01:19:38 PM Geoff Beasley wrote:
> Would it be difficult to add this ??  Would be really good now that
> fsthost has full session support ( IT's MIGHTY !!)
> 
> thoughts ?
> 
> best
> 
> g
> 

Never looked at JS yet so I don't know what's involved in adding it. 

But I suspect it might not be so easy.

I will assume here that Jack server must be running to use Jack Session.
But MusE can be run without Jack running.
So we might require a session manager that doesn't rely on Jack.
We use LASH (now LADISH emulated), which I tested recently 
and still seems to work pretty good.
Yeah it could be argued who's gonna need sessions while running the
dummy audio driver.
But some folks might be using only the ALSA midi features, with other 
ALSA apps. (Flo wanted to add a native OSS midi driver too.)
Or more philosophically, if dummy driver is running, we would still want 
to be able to open our Jack 'sessions' with minimal consequences 
(no audio, at least).

I know, it's a valid question to ask why not just make MusE *require*
Jack to be running, or else - we no run, end of story... 
But you can see there might be risks, like say putting all our eggs 
in one basket. What if say (don't laugh) Pulse Audio one day
overtakes Jack performance? Does PA do midi?
(Been reading about making a PA audio driver - for OOB MusE experience.)
I like more and more the idea Florian has of disabling ALSA (optional)
and relying only on Jack. I really want to help out there.
If we ever port to Apple and Windows and BSD and so on, what is the lowest 
common denominator, if any? Jack? PA? ALSA? OSS? Likely BSD is common-ish,
and Flo has shown that we have some problem areas that aren't BSD compatible 
when they /could/ be (certain system calls, headers etc).
But our native ALSA midi driver (and maybe later OSS, PA etc.) is 
important, even if just to use as a base, and should be kept around,
if you recall discussions about why before - latency, resolution, timers etc.

When I mentioned that part about Jack not running, on one of those 
epic SM threads before, one of the heavyweights, forget who, piped up 
and said that was why "he would never use Jack session".
Dunno, gotta think some more. Opinions? 
Common denominator of above stated desired OS's = Jack + Jack Session?
Tablets, phones? Pipe dream? Inevitable custom MusE native drivers for each?
Whatever gives us the best performance available I suppose.

Consensus seems to be the NON Sequencer Session Manager 
is well regarded, not to mention some of the techniques used
in the NON Sequencer. Seem to recall NON-SM can work with or 
without Jack, correct me if I'm wrong.

Anyway what really worries me is having two session managers 
(ex. Jack session, and LASH for when Jack isn't running).
Seems like asking for trouble flip-flopping between them, can it be done?
Need to pick one and stick with it?

G'Day.
Tim.

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Lmuse-developer mailing list
Lmu...@li...
https://lists.sourceforge.net/lists/listinfo/lmuse-developer