Mac OSX10.6.7/U-mix44/Cross 1.5.2 glitch

[Hannes]

Just discovered a glitch/bug in the preferences.

I just came back home, so i fired up Cross to have some fun.
But very strangely the TC-latency was immense (ca. 1-2 second) though it was set to 1,3ms/48KHz within Cross´s preferences.
So i quit Cross and rebooted, same problem, but when i changed the samplerate to 44,1KHz and back to 48KHz the latency-issue was gone.

I really have no idea what happened.

[Support@MixVibes]

I think you have fired Cross too fast and device wasn't properly initialized by the OS.

[Hannes]

I don´t think so, because i first unloaded a dvd from the drive which was still in there from watching a movie yesterday evening.

[Support@MixVibes]

I'll try.

[Hannes]

I just encountered something else,
this time channel a (outputs 1-2) were dead.

Only restarting Cross and unplugging the U-Mix helped.

[Support@MixVibes]

I can't reproduce : it is still set to 48Khz 64samples since yesterday each time I launch it.
When this happen can you check if you still have access to the device into the system panel of OSX ?

[Hannes]

I can't reproduce : it is still set to 48Khz 64samples since yesterday each time I launch it.
When this happen can you check if you still have access to the device into the system panel of OSX ?

will do so.

[Hannes]

So it happened again, all ins/outs were muted for Cross, but i could access it via the systemspanel->sound. and i could see the inputlevel from the TCs.
But obviously Cross couldnt access it.

At first everything worked fine, but after analyzing a bunch of new tracks (600) it didn´t work anymore.
Before analyzing i cleared my collection, and added all my itunes-tracks again to see which ones had not been analyzed before.




Now what you cannot see is that in the dropdown-menu i only could select no output.

very strange.


Edit: Right now I´m really thinking of throwing the f****in´ Mac out da window, shitty netbook runs flawlessly on 96 Samples / 108 Samples w/ heavy Cue-jumping. AAHHH!!!!

[Support@MixVibes]

The card have been disconnected, even if Cross show it, it's not here anymore as an audio device this is why you have this message.
It happen on both usb ports ?

[Hannes]

The card have been disconnected, even if Cross show it, it's not here anymore as an audio device this is why you have this message.
It happen on both usb ports ?

Yes happens on both usb-ports.
Do you think it had been disconnected for a short time (usb-problem or whatever) and then Cross didnt recognize it again?

I didnt try de/selecting it in the Cross prefs this time, whih mmight have helped. But it´s just odd that this happens at all.