Fwd: Re: Muse - Was: OT: Bitwig beta for Linux reviewed - Linux-audio-dev

10 Mar 2013

On March 8, 2013 11:47:52 PM Ralf Mardorf wrote:
...
  On Fri, 2013-03-08 at 16:37 -0500, Tim E. Real wrote:
  On March 8, 2013 09:31:50 PM Ralf Mardorf wrote:
  IIRC Muse can mute individual clips, but Muse
never was
 able to run on my machine. I tested it for different distros, in
 different years.  
 Howdy, Ralf.
 Can you give us an idea of why this might be?
 Any clues at all, like choice of kernels, tweaks, RTIRQs etc.
 Can you briefly describe the hardware involved?
 I imagine you must run a pretty tight setup there.

 Your experience with MusE is important to us.
 We'd like to try to correct whatever the problem is, with your help.  
 I'm short in time this month, I can spend some time at the end of the
 month and install Muse again.

 The PC is an ASUS M2A-VM HDMI with an on-board ATI Radeon X 1250-based
 graphics, in the past I sometimes replaced it by a PCIe NVIDIA GeForce
 7200 GS.

 In the past the PC first had one, later two TerraTec EWX 24/96 ICE1712
 PCI cards, for more then a year I'm using it with those two cards for
 MIDI and a RME HDSPe AIO for MIDI and audio.

 The CPU always was and still is an AMD Athlon 64-bit dual-core BE-2350
 2.1 GHz. I started with 2 GiB RAM, but early extended to 4 GiB.

 FWIW the PCIe RME card not only is bad supported, on my machine I still
 get xruns with very high latency, when using the RME card, but Muse
 already had issues on my machine, when I used the TerraTec cards only,
 that can be used without xruns at a passable latency.

 I'm usually using self-build kernel-rt in the past 2.6.x and today 3.x.

 Nothing does share the IRQ with a sound card.

 I also tried to tune the machine by:

         ### Bluetooth
         service bluetooth stop

         ### TerraTec EWX 24/96
         modprobe -r snd_ice1712

         ### Others
         modprobe -r firewire-ohci
         modprobe -r firewire_core
         service cups stop
         modprobe -r ppdev # parallel port
         modprobe -r lp    # printer

         ### Unbinding devices
         echo -n "0000:00:13.2" > /sys/bus/pci/drivers/ohci_hcd/unbind
         echo -n "0000:00:13.4" > /sys/bus/pci/drivers/ohci_hcd/unbind

 This doesn't improve the situation. However, xruns were not the issues,
 IIRC Muse usually freeze and is completely unusable here. Architecture
 of the Linux usually is 64-bit, I don't know if I ever tried Muse on a
 32-bit install. I'm using Jack2 only, first regarding to the alsarawmidi
 switch, to get rid of MIDI hardware jitter and because Jack1 never
 worked on this Computer and also not on my first PC, an ASRock K7VT2
 with an 800 MHz single core, 32-bit Athlon. All versions of Jack1 I
 tested, not only the version that was known to do this, disconnected
 clients.

 Onboard audio always is disabled, Northbridge AMD 690G, Southbridge ATI
 SB600, 1 * PCI Express x16, 1 * PCI Express x1, 2 * PCI.

 At the moment I'm booted to Arch Linux, the only installed audio
 software at the moment are Jack2 and Simple Sysexxer and I've got no
 time to test Muse right now. >= 22. March I might have some time to test
 Muse. If I should forget to test Muse, at the end of this month or
 during next month please ask me again.

 Regards,
 Ralf

OK. Great! Thanks for the info. I'll wait a while.

I also run MusE on an AMD 64, an Athlon. It is single-core, a bit old now.
With a Delta1010 ice1712 card.
I blacklisted my on-board audio because even when I disable it in BIOS, the 
 OS still somehow finds it and pollutes the daily ordering of device listings.

There is a MusE command-line debug switch -D which gives us information. 
Sometimes it can be a plugin or soft synth misbehaving with us. 
There are switches to turn off loading of the plugins and soft synths.
Hopefully these will help narrow it down.
I fixed a freeze or two recently, kind of obscure though.

Current release is 2.1.1, next is due out soon, plenty of great new fixes
 and features, and new online docs. Would be cool if you could run a 
 recent version but it might require building source but it's not too hard. 
We have removed the Doxygen requirement for example :)

As a midi editor she's fairly advanced, per-drum or note midi controllers 
 like poly-aftertouch for example.

But, gulp, we're about to face some seeerious competition on two fronts.
Oh, apologies for breaking in on this Bitwig thread, carry on.
And congratulations to the Ardour team expecting the new baby! 
'Gonna hand out some cigars?

Tim.