For those supporting OpenOctave...

[etienne]

OpenOctave has a great feature set! Shouldn't we be supporting such a great project? Everyone makes mistakes, however small, so let's move on and support OpenOctave!

[ccherrett]

Open Octave newest features:

A new routing mechanism to support our new multi channel audio support. This new routing connections manager can not only route external sources but facilitates the routing of all our internal oomidi instruments.

Open Octave Instruments are grouped by their routes so the user always knows what ports belobg to what instrument.



A multi channel buss used for sidechaining.



We will be pushing these changes to git very soon.

Enjoy!

[wolftune]

Amen, etienne.

Chris: looking good. Is this like basically a JACK patchbay that lives within OOM? Because as much as I like consolidated stuff, I'm really getting to be gung-ho about the flexibility that JACK and LADISH offers for mixing whatever tools one wants… It's great to be able to control that within OOM or any other program as long as it doesn't make connections invisible to the broader JACK system.

[ccherrett]

Amen, etienne.

Chris: looking good. Is this like basically a JACK patchbay that lives within OOM? Because as much as I like consolidated stuff, I'm really getting to be gung-ho about the flexibility that JACK and LADISH offers for mixing whatever tools one wants… It's great to be able to control that within OOM or any other program as long as it doesn't make connections invisible to the broader JACK system.

It runs the same as patchage or catia,

http://kxstudio.sourceforge.net/KXStudi ... ions:Catia

The original code was ported into oomidi by faltx and then integrated by Andrew.

So you have full controll over all external and internal ports. Just we have tweeked how we represent internal ports in oomidi so you see a group of port for an instrument.

[ccherrett]

Amen, etienne.

Chris: looking good. Is this like basically a JACK patchbay that lives within OOM? Because as much as I like consolidated stuff, I'm really getting to be gung-ho about the flexibility that JACK and LADISH offers for mixing whatever tools one wants… It's great to be able to control that within OOM or any other program as long as it doesn't make connections invisible to the broader JACK system.

I felt that way for a long time about modularity, but we ended up depending on too many different development teams to call our pipeline stable. So at least this way we control all the code and can make sure it get's the attention it needs to become feature rich and stable.

[ccherrett]

Please use 2012.1 and not 2011 Open Octave Studio to see our newest code base.

For anyone wanting to try Open Octave studio please use the 2012.1 version. I see someone reviewing 2011 code and that is very very dated from where we are now. All the issues he mentioned have been addressed I believe:

https://github.com/ccherrett/oom/wiki/Installing-OOM

You will need a current svn copy of linuxsampler or if you are on Ubuntu you can use the ppas:

http://tinyurl.com/oom2011

We update the ppas as we become more stable

Thanks everyone!

[awilliams]

Hey guys, I know there has not been much action in our git over the last couple weeks.

Well I've been working very hard to rework our audio processing and audio and MIDI routing in OOM.

Here are the some of the results of that work.



Enjoy.

[wolftune]

It runs the same as patchage or catia,

Great. And the whole system will integrate with LADISH too, right?
I totally respect getting everything consolidated and inside OOM, just as long as it still integrates with other tools.

[ccherrett]

It runs the same as patchage or catia,

Great. And the whole system will integrate with LADISH too, right?
I totally respect getting everything consolidated and inside OOM, just as long as it still integrates with other tools.

We most likely will look to Jack Session support. Not sure about Ladish.

[GraysonPeddie]

Does this mean that we can have 5.1 surround sound mixing?

By the way, this is what open source, collaboration, and contribution is all about. Developers and users can all win if we can all make a difference and help improve the quality of code.

[ccherrett]

Does this mean that we can have 5.1 surround sound mixing?

By the way, this is what open source, collaboration, and contribution is all about. Developers and users can all win if we can all make a difference and help improve the quality of code.

It means we have all the channels to route whatever we need and all the control to do so. We will still have to encode the surround. That is yet to be accomplished. But we are a good way there!

[ccherrett]

We most likely will look to Jack Session support. Not sure about Ladish.

lol, it already has ladish support since the beginning... remember a patch from nedko?

Awesome haha

[studio32]

Aha, talking about software again!

Btw I would vote for Non Session Management (NSM) support

http://non.tuxfamily.org/nsm/
http://non.tuxfamily.org/nsm/API.html

[Pablo]

Btw I would vote for Non Session Management (NSM) support

Another session manager! I long for a doc similar to "jack1 vs jack2" in jackaudio.org or "pulseaudio vs jack" in Lennarts blog that clearly explains the differences between Ladish, Jack session and, now, Non Session. Is there something on this?

Ah, and you can always have the scripts!

[studio32]

Btw I would vote for Non Session Management (NSM) support

Another session manager! I long for a doc similar to "jack1 vs jack2" in jackaudio.org or "pulseaudio vs jack" in Lennarts blog that clearly explains the differences between Ladish, Jack session and, now, Non Session. Is there something on this?

Ah, and you can always have the scripts!

Short summary :
JackSession to minimal, not an ideal user experience
Ladish the opposite of minimal (requires jackdbus),
NSM user friendly, all the functionality you need, but still light and minimal.