M4 Test

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Bonteburg wrote:MU.LAB keeps forgetting the MIDI-setup and you have to reset it on each startup. As with M3 it's not really a showstopper which is why I kept procrastinating on it but for the sake of thorough testing, here it is.
Yes got a note about that on the todo list. Will check & fix asap.

Post

MIDI: My Kurzweil SP4-7 shows twice when I'm choosing it as a MIDI output in the modular area. Phasing occurs when playing it (presumably because both instances are played at the same time). The sound gets streamed normally when playing back the sequence.

Adding my Oxygen MIDI controller to the setup adds one instance of the Oxygen and a third instance of my Kurzweil.

Post

And there is only 1 kurz as MIDI out in the MIDI Setup? :o

Post

Yes!


And weird MIDI stuff is happening since I upgraded to OSX 10.6.8 this afternoon:

-MU.LAB takes considerably longer to load
-Trying to use my Oxygen after setting up the MIDI connections on start up results in hanging notes.

10.6.8 is considered a 'recommended' update by Apple.

Post

Works now after two reboots - knock on wood!

Still creepy to think it ever happened...

Post

The problems mentioned above don't seem to happen in M3 so long as you stay away from M4, but when I open M4 (and the problems occur), close M4 and open M3, it's kind of 'infected' so I have to reboot.

Post

OK in M3 the problem happens every other time I open MU.LAB. I then have to press the panic button to get rid of the hanging note and the next time I open it the MIDI problem (including the long startup time) doesn't occur. Then however, the next time... etc etc.

In M4, pressing "reset music processing" doesn't have the desired result.

Post

That sounds like it's not closing down properly and releasing resources. When you exit, check your process list to see.

Post

Hm, I shall try it!

That said - if it's connected to my 'recommended' upgrade I had best do a clean sweep, put on the old one and give Jo a break.

Post

I checked M3 <-> M4 wrt MIDI on OSX and nothing has changed so it's strange that there are all these sudden new issues.

However i do confirm that MIDI on OSX is not always immediately working and going to MIDI setup fixes this. So i'll recheck MIDI on OSX in detail asap.

Maybe things are related..? We'll see.

Post

I can check my MIDI setup too!

I'm prepared to switch back to 10.6.3 though.


For the record: I did a system upgrade to 10.6.8. It was only then that the problems started to occur.

Post

Happens with EXT, REaper and MU.LAB, not with Garageband. Happens with Oxygen, not with Kurzweil as far as I can tell. :shrug:

Post

Hey all of the more tecchy folks on here...

I have a feeling my MIDI problems are connected to my system upgrade and the make of the keyboard (Oxygen).

I had to upgrade the system for a certain piece of software to run so I'd rather not go back to 10.6.3 right now but here's an idea - I could get an external disc, put OSX 10.6.3 on it and boot from there to use MU.LAB. Would such a setup be feasible? I guess I'm mostly talking about bandwidth though I hardly run complex projects with a lot of audio tracks.

Cheers,

Marco :)

Post

Hey, besides what we discussed via email, this thought: Maybe the problem is a driver incompatibility problem. Did you check the M-Audio site for that? Maybe update the Oxygen driver?

Post

There isn't a driver - apparently it's deemed 'class compliant', ie (I think) not in need of a driver.

I'd use my USB/MIDI adapter which helped solve a very similar LUNA problem with my old keyboard back in 2007) but this particular make of keyboard doesnt' have true MIDI jacks.

I think I will look for a MIDI interface that allows for a USB cable to go from the keyboard through the interface to the computer, if such a thing exists, or try the external HD method - I was going to get more storage.

Post Reply

Return to “MuTools”