MIXVIBES Dj Community old forum

Hi all, need to get to the bottom of this as it's getting annoying.

Basically on starting Cross it hangs (not sure if it's crashed?) on start up. Sometimes for 10 minutes -/+ Shows Non responsive in Finder

I've been using 2.6.0 as I don't really like the Wave form colouring on the later releases. But today I've upgraded to 3.3.10 in the hope it would fix this, but it hasn't.

Also I've experienced hangs (crashes?) when loading tracks into a deck. The deck playing will continue to play music but the screen freezes and i get the Mac Beachball for a minute or two and then it loads as normal.

If a fresh install is the best option, how do i go about doing this without losing my Playlists etc?

System is a 2011 2.2Ghz Macbook Pro on Yosemite OS X with 8 gig Ram

controller is Denon MC3000

Library on external USB prowered drive

Thanks in advance.

The track loading indicates your latency setting for the audio driver is to low (buffer size).

This might be part of the startup issue as well, but not sure of that.

AT Yosemite the 2.6 won't work that good no more as Apple made significant changes without backwards compatibility....

Please let's know if the buffer size had any effect. More suggestions are possible but the latency should just not happen (another second freeze of GUI may be as long as audio isn't interrupted)

Thanks for the reply, I've only recently upgraded to Yosemite too. It had been doing the same thing on Snow Leopard too unfortunately.

I'll try altering the latency to see if it helps. Will report back

Thank you RoJec, that seems to have worked!

Latency was set at 512 samples (10.7 ms) I've increased it to the maximum at 2016 samples (42.0 ms) and it now opens Cross in 12 seconds as opposed to 10 minutes lol!

What's the pro's vs con's of leaving the latency at it's maximum? Should i run it somewhere around halfway? The default must be 512 as i don't think i've ever altered it.

Oddly after messing with the latency slider. I set it at its lowest value of 32ms thinking it would slow start times even more and it's still fast around the 12 second mark. So i've reset it to 512ms as it was originally and it's still opening at 12 seconds.

How odd, maybe it just forgot how to boot up lol

I may leave it like that for the time being as i'd not experienced any audio glitches or drop outs etc.

Much appreciated RoJec

This represents the amount of audio put into the soundcard to transfer bits to audiosignal.

The lower the value the more often the CPU has to fill it with the next part of the music.

To have responsiveness you need the opposite... once the buffer is filled it will come out first.

You should try as low as possible. Any audio dropout indicates the value being to low... unless you have a dropout in the track... It usually takes some time to find out your lowest value.

I would guess it might be close to the 512. This value is supposed to be safe in almost all cases.... My 'fastest' soundcard runs at 1.1ms (49 samples); others all below 256.

You may want to try the internal sc to see if it makes a difference to the denon. Make sure to have the latest drivers/firmware for the denon in use.

The info is still somewhat general, but might help to narrow down where the deviation comes from.

Appreciate the info, i've done a little reading into it and will have a play about.

Cheers bud