MuTools

muzycian · Post by **muzycian** » Sat Dec 22, 2007 1:12 pm

toxicoh wrote:Hi Jo,
This new version knocks off about 5% cpu here.

Alright, it's something

Good luck with the G4s.

Are they known to be hard to be optimized or what?

Toxicoh, another thing:

As a thanks for your valuable support and beta testing of MU.LAB, i want to give you a MU.LAB Unlimited User License for free.

This will also give you the Unlimited tracks you want

Please email me your name and country and i'll send you a MU.LAB Unlimited User License.

Thanks again for all your supportive feedback!

jpumphandle · Post by **jpumphandle** » Sat Dec 22, 2007 6:43 pm

muzycian wrote: I've changed some compilation settings, and have uploaded an alternative MU.LAB Free 1.0 for OSX here:

http://www.mutools.com/mulab/mulab-free ... 22-osx.zip

Please put this app into your existing mulab folder thereby overwriting the current application file (first back up your mulab.app as you have an 'Unlimited' and the above test is a 'Free'), and see how this one runs.

Looking forward to your feedback.

Big improvement! This compilation runs the Demo at about 37% (did show a peak of 41.5%). When not running the Demo shows 9% on the teeny, tiny meter.

Also I can report that the CPU usage numbers don't display after a few uses. (I saw this was reported in the '1.0' thread)

Thanks for improving the performance on my lowly PPC iMAC.

toxicoh · Post by **toxicoh** » Sat Dec 22, 2007 10:53 pm

muzycian wrote:
toxicoh wrote:Hi Jo,
This new version knocks off about 5% cpu here.
Alright, it's something

Good luck with the G4s.
Are they known to be hard to be optimized or what?

Oh, no. It was just a general comment that most G4 processors are getting a bit old now....

My G5 iMac is 2.5 years.

jpumphandle · Post by **jpumphandle** » Sat Dec 22, 2007 11:08 pm

jpumphandle wrote:
Big improvement! This compilation runs the Demo at about 37% (did show a peak of 41.5%). When not running the Demo shows 9% on the teeny, tiny meter.

Also I can report that the CPU usage numbers don't display after a few uses. (I saw this was reported in the '1.0' thread)

Thanks for improving the performance on my lowly PPC iMAC.

However, I had to go back to the MU.LAB Free of 12/7.

I encountered a bug in the 12/22 Test version. When I try to import a WAV file, the WAV file somehow is doubled in Frequency and comes up as high pitched and short in length. I tried erasing the OVW file and even writing over the WAV file but the result is always the same - a doubly compressed WAV file. The WAV file was double checked in iTunes, Audacity and Quicktime and is fine.

So now, I am back to where I started - Can't run the Demo file.

I did turn out a piece of music on the iMAC (using the old MU.LAB Free). An old Wayne Shorter riff which I converted from AIFF to MP3 using Audacity. here's the link:

http://johnnypumphandle.com/johnny/jazz ... handle.mp3

jpumphandle · Post by **jpumphandle** » Sun Dec 23, 2007 1:21 am

More on the Chipmunk style loading of WAV files ...
iMAC PPC 1,6GHZ, 256RAM, OSX 10.3.9

It turns out that both the old and the new versions have developed the habit of loading WAV files with chipmunk style sounds.

I started the JACK server and started using this audio interface. NO MORE WAV PROBLEMS!

There must be a problem in the relationship of MU.LAB's interface with Core Audio?

Bottom Line: I am back using the 12/22 version of MU.LAB Free but with JACK Audio.

As an aside: The JACK Pilot program reports CPU usage also (in readable size).
The CPU usage is approximately 10% higher than MU.LAB numbers. Different measures?

muzycian · Post by **muzycian** » Sun Dec 23, 2007 12:33 pm

Regarding the pitch issue of audio files: mu.lab does not (yet) automatically compensate for samplerate differences between the audio file and sound device.

So if you have a auido file at 44.1 khz and it's played using 96 khz, it will be pitched. Solution is to resample the audio file in an external audio editor.

jpumphandle · Post by **jpumphandle** » Sun Dec 23, 2007 4:36 pm

muzycian wrote:Regarding the pitch issue of audio files: mu.lab does not (yet) automatically compensate for samplerate differences between the audio file and sound device.

So if you have a auido file at 44.1 khz and it's played using 96 khz, it will be pitched. Solution is to resample the audio file in an external audio editor.

I don't see why I should resample the file to 96Khz.

I double-checked the Audio setup and it looks like both the JACK Router and the Built-in Audio are set to 44,100 hz and 16 bit rate for Input and Output. (The port is named Master Stream)

The Built-in Audio can be set up to 96K, but I am sure that it currently is not, unless some other music app can set this. Do you think that this is possible? I guess if it happens again, I will check to see if anything has changed.

So you are saying that each WAV file tells you what sample rate it was recorded at but MU.LAB ignores this?

As I mentioned before - iTunes, Quicktime, Audacity all play the file correctly, so I would classify this as a bug.

muzycian · Post by **muzycian** » Mon Dec 24, 2007 11:59 am

No, it's not a "bug".

It's just that audio files are played back at a 1:1 ratio.

So a 44.1 KHz file played on a 96 KHz system will sound at a bit more than double pitch.

Cubase used to work like this for a loooong time, with the only difference it just started a resampling process automatically (non realtime). Maybe it still does.

MU.LAB will soon be improved on this aspect. This will come together with the sampler, which will need an interpolation engine (that's what we need) anyway.

So for now: resample any audio files with a different samplerate than the working samplerate so samplerates match the audio setup's samplerate.

And look forward to the future version of MU.LAB with the built-in realtime samplerate converter

MuTools

KVR Audio

MU.LAB PreRelease