Crashes after audio device setup

i just got traktor pro and i installed the software. i dont have that audio 8 dj thing so i have to select my computers sound card (SigmaTel High Definition Audio CODEC) on my vista pc. well i do that and it says traktor encountered a problem and has to shut down. i can select the audio 8 dj option and it wont crash, i just cant hear my music cause i dont have that . uninstalling and reinstalling did not fix this either.

 

Thats funky, you could try downloading http://www.asio4all.com/ give that a bash and see what happens, welcome to the forum.

 

thanks for the reply but no it didnt fix it. this sucks, i just got two of the new da scratches and 2 stanton tables. i cant do my magic on any of this stuff until i get the program working....

 

i got it to accept my sound card, now does anyone know how to get da scratch to work with traktor pro?

 

I wont unless you are running an approved sound card from N.I like the audio 8 or a mixer.

 

Traktor Scratch drops out every time I use a loop. I thought it was because of High CPU usage but Pro freezes after I try to set Audio Latency. Does anybody else have these problems with TSP and Vista. I am Trying to set up a back up Rig on a ACER 4420 AMD 64BITX2 Dual Processor 1.90 GHZ 2MB RAM with Numark Battle Ready setup. I normally use a Dell Inspiron e1505 1.8ghZ dUo Core intel Centrino Processor with 2.5 Ram. I dont have any issues with this setup running XP except for a few glitches of Tempo automaly speeds up or plays in reverse I believe this is due to needles getting full of lint after I clean them the problem stops. I need to know if TSP just sucks with vista cause vista sucks ass. should I blow out my new laptop and down grade to xp?

 

Sadly, there are way too many combinations of hardware, dodgy driver and OS to give a clear answer.

Am I being blind/stupid, or did you not specify which sound card you're using? I have no idea what a "Numark Battle Ready setup" might be, unless you mean one of the Battle Paks with a pair of decks, mixer, headphones? If so, that's still not covering what the sound card is. The sound card and its drivers are kinda a dealbreaker if they're not good, you see.

It's entirely possible (indeed, it is the opinion of many people, some of whom have experience outside of playing Internet Tough Guy on forums) that Vista just plain "sucks ass". However, it has also worked for some- in some cases better than their old setup, where "upgrading" to Vista got rid of some horribly undermaintained software and drivers. It's just not possible to say if it's better for you. I'd try making sure all the software is a decent, working version (including soundcard drivers), and see how your new machine behaves. If the machine came with a restore DVD, you could always nuke it and try XP, anyway (or back the HD up/use an external one etc).

The trick to finding out if stuff works is to test, test, test. You need to test your workflow and your tunes on your kit, to see how they treat you. If the new machine rocks universes with XP on it, use that. If using some more up to date drivers under vista (hint: stuff that came on a CD with the soundcard is often an old version) is good for you, use that. If your soundcard just bites, consider borrowing a USB/firewire one from a friends and trying it out. There are various possibilities to try here.


Oh yeah, 1.9GHz seems a shade slow for a new laptop- is it new new, or just new to you? Been a while since I saw a non-netbook below 2.xxGHz. Not hugely relevant, just curious.

Despite the fact that Centrinos with the lack of cache are kinda gutless, it should just about be fast enough- and I wouldn't expect a slow CPU to cause too many freezes- though I could see the lack of CPU power causing it to cark while looping, despite the fact that you're above minimum spec to run the software (but again, could easily be soundcard issues).

When you say "locks up when setting latency"- you mean as soon as you touch the latency, or there's a latency setting at or below which it always locks up?


Can't answer your question.. can help you take the first steps towards answering it, or at least supplying better details so people can try and work out what's going on, though. Sorry for the torrent of questions, especially if I missed something hugely obvious already