MIXVIBES Dj Community old forum

hey guys, been using Cross for a few weeks now loving the improved engine over DVS...

appear to be getting glitches/pops coming out on my mixes though, im running on windows 7, maudio delta 44 for mixing and a delta audiophile 2496 for recording, im pretty 99% sure its not coming out when i mix but only on the recording.

seems to only be when loading in new tracks and sometimes on timecode movement (ie deck 1 is playing a track, cueuing deck 2 in headphones, a click could still occur on the ist deck) its not constant glitching but is quite annoying when it comes through.

any help would be much appreciated, have tried lowering the memory buffer in Cross, tried running in various modes as admin etc, tried going right up to 768 latencyt on the soundcard buffer. another strange thing is since getting Cross ive never been able to run it on anything other then 48000 even changing the rate out of Cross then loading Cross it always switches to 48?

2gb ram
quad core 2 Q6600 2.4ghz
windows 7

sorry if ive left anything out, cheers

sorry thats a
m-audio delta 44 - mixing
m-audio audiophile 2496 - recording

same PC

Cross can't always drive the samplerate so usually it takes what the asio rivers is saying.

If you mix with the Delta44 alone everything is fine but as soon as you record with the 2496 (same computer you've got issue).

All my questions will be about the 2496 :
- do you use asio ? (raising latency or use wdm if possible)
- what software do you record with ? (try with another)

Try dpc latency checker (http://www.thesycon.de/deu/latency_check.shtml) to see what acts differently in simple mix & mix+record mode.

i stream to an internet radio station using simplecast (mp3 192kbps) as it lets me rip to a local mp3 aswell as stream

within the m-audio control panel i always keep the settings the same for both sound cards 48khz 512 samples

i'll give shoutcast a try (just annoying i cant save my mixes on the fly)

ive tried that latency checker before, i usually get something that looks like this both when recording and not recording...



Uploaded with ImageShack.us

since messing about with that latency checker ive found that simply running Cross and doing nothing at all it stays in the yellow 90% of the time

mixvibes DVS im getting around the 300-400 mark

i think weve found the problem nice one, not sure what to try now though

Did you optimated your computer for audio software?

http://www.audioforums.com/resources/wi ... ation.html

A lot of that works for Vista & Win7 too. Give it a try

Cheers,

Steve

Ultra weird...

When you launch Cross it reachs the 1ms mark ?
with a quad core 2 Q6600 2.4ghz...

Here is mine with the same OS/cpu combo setup :


As your are using PCI cards, you might have a look at this tool :
PCI latency tool
http://downloads.guru3d.com/download.php?det=951

It helps you to give priorities between your pci devices

Hi!

Did you check your graphics card is correctly configured, with a good working driver ?

In some cases, it might be the point.

thanks for all the help guys

right ive tried a few things, optimizing some settings, no page file etc, disabled the on-board hd sound card, that pci latency app completely freezes my PC :\ cant seem to get it to run at all

fully working graphics card with drivers etc, ati radeon hd3850

on running simply the dpc latency checker and Cross from bootup, im solid on yellow bars, one thing to note back when i used to use mixvibes DVS (on xp and win7) i had trouble running @96khz and running vsts etc, finally found the cure on here to disable two of the bios settings that are still disabled... names of the 2 settings evades me but it cured the strange garbled frequencies when mixing (best way i can explain it lol)

hmm, somehow when messing about with the preferences in Cross i managed to change my sample rate to 96khz on the fly, seems to allow me to change it all the time now... strange lol

not sure what else to try, might see how Cross behaves in xp

Don't think it is W7 related and concerning the PCI tools never seen this sorry.
Look into the bios for pci related things.