Cross crash and problem

[John Wo_O]

mine were dubstep tracks. I guess I should try again by adjusting the bpm range, I didn't think of that for some reason :S

[Support@MixVibes]

@Blackbrook : yes very strange indeed.
@John Wo_O : reggae, dub, jungle, dnb, always have strange bpm value detected by software.

[hemskoc]

mine were dubstep tracks. I guess I should try again by adjusting the bpm range, I didn't think of that for some reason :S

Dubstep trax tend to read at half time(below the default detection bpm <70 bpm?> (half of 130=65), so thats why u get a 00 bpm analysis

[Blackbrook]

Hello,

so after I updated to Cross 1.3.2 and switched off my virus scanner and nothing ran instead of Cross the terrible sound described above came up again. Luckily I recorded the session and so I can give you a taste of what I have to deal with:

http://steve.boxbox.org/transfer/cross_ ... _sound.mp3

Please note that the whole collection is analysed, my notebook is optimized for audio programmes, everything is turned off (virus scanner, different agents and panels,...) and only Cross was running.

Here are my specs because I think that this seems to be the problem:

Asus F3Sc
Intel Core2Duo T7250 @ 2,0 GHz
2GB Ram
Win XP Pro Version 2002 SP3

I get this terrible sound when I am mixing - always! There has not been a session that I could finish without listening this crazy sound. If there is anybody that has a hint instead of installing a clean and Cross only system I am really looking forward to it.

Thanks a lot for your help mates!

Greetings,

Steve

[Support@MixVibes]

Vinyl or cd ?
It sound like a broken records for me.
In flexible or internal mode do you have this ?

[Blackbrook]

Vinyl - I own six different: the ones that came with DVS, those from the Cross Pack and two brand new records one in yellow and one in red. Mixed with the last two ones when the sound error occured but I also had these sounds when I was mixing with the other records.

I am mixing in absolute mode.

Greetings,

Steve

[hemskoc]

Hey Steve.. i had something similar happening to me in the RC release, and for me it was the soundcard buffering. I had to increase the samples(more latency) to remedy the 'audio glitchyness'. With the 132 version, i have put my soundcard back to 44khz from 48khz sample rate, and increased the buffer rate to compensate. Seems to run great 99% of the time, but maybe once a gig(3 hr), i will get a small audio glitch like yours. When i load a track in the non playing deck, i do get audio spikes tho(i just have to make sure the level/crossfader is not on that loading deck too).
By the way, im using a edirol fa66 firewire, with original drivers.

good luck mate-hope this helps

[Blackbrook]

I guess that it is a driver problem or anything like trouble between my notebook and the audio interface. When I was djing with ableton more than 2 years ago I owned a M-Audio Firewire Audiophile that worked really really good. So I tried to work with my U46 MK II in ableton and there these sounds happen, too. When a track is playing and I drag another track into a channel this strange sound came up. So I guess that it might have been an audio interface - notebook problem and this reminds me to another problem from the past:

I wanted to record the sets from a huge party years ago with ableton live and my former M-Audio interface that worked perfectly as output. But when I tested to record music trough Line In I had buffered sound. After hours and days of testing and troubleshooting with the M-Audio support we concluded that the chipset of my internal firewire port was a cheap via chipset. The support suggested to buy a pcmcia firefire card with a strong texas instruments chipset and guess what happened: It worked!!!

So could this be a problem? I know firewire is different from USB but they all are controlled by chipsets

Greetings,

Steve

@hemskoc: I will try to increase the latency. I am mixing at 44.1kHz already. Thanks for your help!!!

[hemskoc]

The support suggested to buy a pcmcia firefire card with a strong texas instruments chipset and guess what happened: It worked!!!
So could this be a problem? I know firewire is different from USB but they all are

Not sure about the usb chipset thing..but on another note...you may have solved my problem! im using a pcmia card on which i cannot tell if it has a texas chipset in it-(i cant read the manufacturers name on it ) so maybe this could be part of MY problems!! i might have to pry it appart for a closer inspection !
Cheers

[Support@MixVibes]

Yes for firewire, the TI chipset is the only to trust.

I know those may sound basic to you but :
Did you switch off the usb power management on each usb port ?
Are you running fullpower/desktop power scheme ?