Muse2

[alextone]

A quick heads up for you.

I'm running Muse2 (or trying to) with a large Linuxsampler session and Jc_Gui already running. (muse2 is from the AV repo)

There's a persistent jack fail error message comes up in a popup window in Muse2, and I get a jack graph error in the terminal where i'm running LS and JC (a zombify error).
When i run oomidi with the same setup i get no error.

Looking at the muse forum, for the work being done towards a muse2 release, i see Tim's done a bit with the jack driver setup in M2. It maybe the case that he's spotted something that doesn't sit well with jack1. (I had the same setup with Jack2, Muse2, LS, and JC running in Arch64 not so long ago, and had no errors of this sort.)

I suspect there's something in LS and Muse that doesn't sit well with jack1, but is...."tolerated" in jack2, to the point it will continue to run.

Can i respectfully suggest that you look at the latest svn (branches/release2.0) from the Muse2 team, when building up AV 6.0, and if possible revisit the possibility of including a non-dbus version of jack2 in the AV repo?

I've had glitches with jack1 in the past where "something somewhere" makes it mischievous, but the cause is often a moving target, as it seems certain combinations go well, and others don't. At times muse2 has behaved like a drunken elephant with some jack1 version, and gone sweetly with others. I've had better luck with jack2 overall.

Nothing empirical about any of the testing above, just trying to find a sweet spot, as a saying goes.


Alex.

[GMaq]

Hi,

I'll be honest I'm not terribly familiar with Muse2 but I can likely put a package up soon, as far as JACK is there a reason you'd want jack2 without dbus specifically? Just curious since Dbus seems to be the most attractive feature of jack2. Historically we've favored jack1 because it seems to behave better with FireWire audio devices and we have a fair number of users doing FireWire.

I'll consider putting up an optional JACK2 package OR in the meantime you can always do an overlay install of jack2 from source over the existing jack1 libs provided that you build jack2 with --prefix=/usr

[alextone]

Hi,

I'll be honest I'm not terribly familiar with Muse2 but I can likely put a package up soon, as far as JACK is there a reason you'd want jack2 without dbus specifically? Just curious since Dbus seems to be the most attractive feature of jack2. Historically we've favored jack1 because it seems to behave better with FireWire audio devices and we have a fair number of users doing FireWire.

I'll consider putting up an optional JACK2 package OR in the meantime you can always do an overlay install of jack2 from source over the existing jack1 libs provided that you build jack2 with --prefix=/usr

Gmaq,

The muse chaps have been posting for a little while now that they're close to a release of muse2, so it may be mature enough to be worthy for inclusion.

I don't usually build jack2 with dbus, but it runs without zombifying LS, muse2, or anything else here. That's the reason i use it. I get as low a latency, and the apps tend to behave more nicely with jack2. As i wrote, this isn't empirical, just my daily experience, running big linuxsampler sessions, and using daws with lots of tracks.

If it's unlikely to mess up my AVlinux install, i'll install jack2 from source, and give you some feedback, and possibly a better comparison. Having jack2 as an alternative to jack1 would be useful for those of us who have problems with jack1, imho.

Alex.

[GMaq]

Oh I just remembered something!

Did you see this, may be worth looking at: http://www.remastersys.com/forums/index.php?topic=2022.0 AFAIK this may have affected 5.0.2 and 5.0.3.

[alextone]

Oh I just remembered something!

Did you see this, may be worth looking at: http://www.remastersys.com/forums/index.php?topic=2022.0 AFAIK this may have affected 5.0.2 and 5.0.3.

Yes i did see that, and i've removed the -dev files as a result. Still no change here though. and the zombify error continues to appear when muse2 is opened, and a template is selected to be loaded.

I'll install jack2 today, and see what happens.

Thanks for the feedback,

Alex.

[alextone]

No go with jack2.

the latest svn builds, with a tweak, but won't run.

When jack is started, this error appears:

jackdmp 1.9.9
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
creating alsa driver ... hw:M44|hw:M44|512|3|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 512 frames (10.7 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 3 periods for playback
08:42:54.882 ALSA connection graph change.
port created: Midi-Through:midi/playback_1
port created: Midi-Through:midi/capture_1
port created: MK-249-USB-MIDI-keyboard:midi/playback_1
port created: MK-249-USB-MIDI-keyboard:midi/capture_1
08:42:54.909 JACK was stopped successfully.
08:42:54.910 JACK has crashed.
08:42:56.575 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Could not open component .so '/usr/lib/jack/jack_oss.so': /usr/lib/jack/jack_oss.so: undefined symbol: jack_driver_init
Could not open component .so '/usr/lib/jack/jack_oss.so': /usr/lib/jack/jack_oss.so: undefined symbol: jack_driver_init
jack_get_descriptor : dll jack_oss.so is not a driver
jack_get_descriptor returns null for 'jack_oss.so'
Could not open component .so '/usr/lib/jack/jack_oss.so': /usr/lib/jack/jack_oss.so: undefined symbol: jack_driver_init
unknown option character l


After installing the "stable" source release, Version 1.9.8, i get the same error.

Clues anyone?

Alex.

[GMaq]

Hmmm,

I'll have to experiment with this, unfortunately I'm on a 'working weekend' and probably can't get to this until an evening sometime later this week. What happens if you install jack2 from the default Debian Squeeze repos (yes it's an old 1.9.6 but we're just using it for a placeholder) and then do an overlay install of the 'stable' 1.9.8 ? The only potential wrinkle being the older Debian package will bring in Dbus and I'm not certain if the overlay will properly purge that or not.

Also in the meantime FYI all the build dependencies for Muse2 should be present in AV Linux 5.0.2 if you want to see if a new SVN build behaves any better. This is good info thanks, I regret you are seeing these issues but I am personally not a large user of either MIDI or Linuxsampler so as much as it chagrins me it's good for me to find out. I wonder if more wisdom could be found at the JACK IRC channel?

[alextone]

Hmmm,

I'll have to experiment with this, unfortunately I'm on a 'working weekend' and probably can't get to this until an evening sometime later this week. What happens if you install jack2 from the default Debian Squeeze repos (yes it's an old 1.9.6 but we're just using it for a placeholder) and then do an overlay install of the 'stable' 1.9.8 ? The only potential wrinkle being the older Debian package will bring in Dbus and I'm not certain if the overlay will properly purge that or not.

Also in the meantime FYI all the build dependencies for Muse2 should be present in AV Linux 5.0.2 if you want to see if a new SVN build behaves any better. This is good info thanks, I regret you are seeing these issues but I am personally not a large user of either MIDI or Linuxsampler so as much as it chagrins me it's good for me to find out. I wonder if more wisdom could be found at the JACK IRC channel?

Nice call, that did the trick. Installing Debian jack2 meant losing a few packages with jack1 leaving (naturally), but i've got most of it back, and jack1.9.8 is now installed and working with no dbus in sight. I'll give it a workout today and tomorrow, and get back to you with any odd results or errors.

Thanks,

Alex.

[alextone]

hehe, works a treat. So far so good. Full LS session, and a 108 track Muse2 template, and no problems. I have JC_Gui going as well with a long concert hall IR running as well.

So, the stable release of jack 1.9.8, sans dbus (classic mode used when compiling), works, after using the Debian 1.9.6 version to "plant" all the dependencies. More testing to do, but we might have a potential candidate here as a jack2 version for AVlinux?


Thanks again for the help,

Alex.

[GMaq]

Hi,

Well with some experimenting and breaking an existing install I've determined that building interchangeable custom JACK 1 and JACK 2 packages that cleanly keep Debian happy and safely replace each other is beyond my hackaging skills especially with no source for Debian Squeeze which forces me to use pure upstream source, Certainly I can build and package updates to JACK 1 OR JACK 2 on an existing system but the interchangeability unfortunately evades me. Couple that with the fact that I am confident in JACK1 and it has been my default for a couple of years now with very rare almost non-existent requests for JACK2 so I have taken another direction in solving this problem...

AV Linux 6.0 will have the dependencies fixed so that Debian's official JACK packages will interchange without collateral damage to existing installed packages. If someone wants to use JACK2 they can either grab the existing JACK2 Squeeze packages and do an overlay OR grab the newer JACK2 packages from Debian Wheezy (which works currently with no guarantee for future compatibility). I have also built a Muse2 SVN package as well which can be found here: http://bandshed.net/custom/muse2_b2+SVN1505avlinux-1_i386.deb

[alextone]

Hi,

Well with some experimenting and breaking an existing install I've determined that building interchangeable custom JACK 1 and JACK 2 packages that cleanly keep Debian happy and safely replace each other is beyond my hackaging skills especially with no source for Debian Squeeze which forces me to use pure upstream source, Certainly I can build and package updates to JACK 1 OR JACK 2 on an existing system but the interchangeability unfortunately evades me. Couple that with the fact that I am confident in JACK1 and it has been my default for a couple of years now with very rare almost non-existent requests for JACK2 so I have taken another direction in solving this problem...

AV Linux 6.0 will have the dependencies fixed so that Debian's official JACK packages will interchange without collateral damage to existing installed packages. If someone wants to use JACK2 they can either grab the existing JACK2 Squeeze packages and do an overlay OR grab the newer JACK2 packages from Debian Wheezy (which works currently with no guarantee for future compatibility). I have also built a Muse2 SVN package as well which can be found here: http://bandshed.net/custom/muse2_b2+SVN1505avlinux-1_i386.deb

Thanks for offering an alternative solution, and keeping us posted. The muse package is welcome, and i'll try the jack2 wheezy package soon.

Alex.