New Bug in Traktor 1.2?

[BentoSan]

I'm just trying to gather information to help me decide wether or not to make the switch from traktor3 to traktorpro... the evidence suggests it's in my best interests to stay put with t3.

1.1.2 was a MEGA stable release that never crashed on me once or bugged out on me in any way shape or form.

1.2 hasn't failed me yet either to be honest, but people have reported some issues - so if your paranoid best to stick with 1.1.2 until everyone here is as confident about the next release as they were with 1.1.2

[wrong chris]

^ alright, yeah it seems to differ from person to person. I'm gonna grab a "demo" version and see how it works for the time being, just so im comfortable with it once a more stable version comes out I can purchase.

I mean, for those of you guys still using traktor 3, i'd definitely go pro, just see if you can get a copy of 1.1, thats plenty stable, i've never had a problem with it.

the features in 1.1 don't cut the mustard for me, otherwise i'd be all over it.

I like having 4 seperate fx channels like in T3... also the pitchbend sensitivity in T3 is easier to work with for when I feel like doing manual beatmatching.

so you can see why Im stoked about 1.2 as they addressed those particular issues in the update, but the reported bugs are a little disconcerting.

[CodeMorse]

Used to love 3.4.1 apart from the pitch bend via controller issue it had, got a free upgrade to pro and tested out 1.02 it wuz ok but i didnt touch pro again till 1.1.2 which is i think the most stable yet, i have only come across crashes on shutdown with 1.2.1 other than that playback seems ok, but on the ni forums things seem to be a little heated conscerning 1.2.1, so ni will probably have 1.2.2 out very soon, theyre already beta tesitng it.

[Karlos Santos]

Im not sure that things are 'heated' on the NI forums.

There seems to be some people who are hell bent on telling people to roll back to 1.1 and that 1.2 isnt as stable but i havent had a single issue with 1.2
1.1 is not anymore or less stable than 1.2.

People seem to use stability as a by-word for bug that affect them especially the driver bug that people are having due to using Unibody Macs and/or Snow Leopard.

"when are NI gonna fix the distortion issue" this is caused by Unibody Mac driver handling NOT traktor yet everyone blames NI and actually NI are fixing it by changing the driver because obviously Apple dont care.

All this yadda yadda about stability is baffling.

The Hot Fix for issues that got through the Beta AND Public Beta test is due very soon.

[Be-Ne-Dek]

^ alright, yeah it seems to differ from person to person. I'm gonna grab a "demo" version and see how it works for the time being, just so im comfortable with it once a more stable version comes out I can purchase.





the features in 1.1 don't cut the mustard for me, otherwise i'd be all over it.

I like having 4 seperate fx channels like in T3... also the pitchbend sensitivity in T3 is easier to work with for when I feel like doing manual beatmatching.

so you can see why Im stoked about 1.2 as they addressed those particular issues in the update, but the reported bugs are a little disconcerting.

see i feel the same way, i love the 4 separate FX channels, and i love the feel of the program over, that's why i don't want to go back to 1.1.2 just yet, but because of the issues i've had, i'm scared of doing any major gigs with it...

[pepehouse]

Im not sure that things are 'heated' on the NI forums.

There seems to be some people who are hell bent on telling people to roll back to 1.1 and that 1.2 isnt as stable but i havent had a single issue with 1.2
1.1 is not anymore or less stable than 1.2.

People seem to use stability as a by-word for bug that affect them especially the driver bug that people are having due to using Unibody Macs and/or Snow Leopard.

"when are NI gonna fix the distortion issue" this is caused by Unibody Mac driver handling NOT traktor yet everyone blames NI and actually NI are fixing it by changing the driver because obviously Apple dont care.

All this yadda yadda about stability is baffling.

The Hot Fix for issues that got through the Beta AND Public Beta test is due very soon.

Your position as a moderator at NI makes you defend the indefensible, we complain about stability because the program just stops playing after a few tracks, the decks freeze and there's no sound anymore and all you can do to
fix it is to restart Traktor. That is mayor stability bug and makes the software unusable in a live situation, that's why we are complaining and returning to 1.1. and recomending the other users also downgrade. There are lots of posts about it at the NI forum and here as well among other important bugs, I´m tired of paying to be a beta tester instead of a DJ while others say everything is ok.

[Karlos Santos]

Im not an NI mod on here im a user and the DJTTs Mod know that i take my NI hat off when im here.
I dont defend the "indefensible" because i wouldnt insult your intelligence.

Its ME that has been nagging NI about this 31 track freeze so im also like anybody else, a thorn in NIs side.
There maybe new bugs in 1.2 but it isnt less stable than 1.1

Ive heard this all before and i understand why people say it but i do not defend the product when its clearly undefensible. Choose to believe at your will.

[lsmith]

Overall I have not been very impressed with NI's QA controls. I am also not very impressed with how they choose what features to add. Then again, with a large userbase its comes harder to please "everyone" .. I was quite thrilled about the MIDI mapping changes until I realized that they stop half way .. lets hope they actually think things through for 1.3. So I agree right now 1.1.2 seems to be the most stable release, but I am still going to switch to 1.2 since I can "fix" most of NI's omissions in the MIDI mapping department with bome's for now.

[CodeMorse]

Im not sure that things are 'heated' on the NI forums.

There seems to be some people who are hell bent on telling people to roll back to 1.1 and that 1.2 isnt as stable but i havent had a single issue with 1.2
1.1 is not anymore or less stable than 1.2.

"when are NI gonna fix the distortion issue" this is caused by (ect ect)
driver handling NOT traktor yet everyone blames NI and actually NI are fixing it by changing the driver because obviously (etc etc) dont care.


The Hot Fix for issues that got through the Beta AND Public Beta test is due very soon.

Hey Karlos, i say heated i mean it but it may be taken a little out of context, the debate seems to be whether to downgrade to 1.1.2 or not, like you said. I agree with you on what i quoted of your post, and i have to say i take my hat off to NI for TPro, I had T3 before that and i have to say they have improved their software no end, that sai i do have a few issues with TPro but at least at the moment i cant verify its on TPro due to my new controller (Vestax VCI 300) and newish OS got a prerelease of Win7 64bit to try out if it works on my programs.

I would like to ask a couple of questions since i found you, can you confirm if traktor pro has hi def support for jog wheels, the vci300 has hi def jogs and its ptoving to be a devil to map them...

[R3clu23]

After Djing for about an hour tonight (not a gig thank god), i noticed that deck a would just stop sending music to the audio card?! you could still do everything you could do with it normally, just no music from that deck. i checked my mixer, no problem there. loaded the same track onto deck b, no problem there. looked at my audio routing settings, nothing. finally, i rebooted traktor, and it worked again! the same thing happened about 30 min later!

I wouldve crapped myself if i had been giggin out tonight, i'm starting to question just how stable this new version of traktor really is in its current state, i've been hearing about lots of bugs lately, and i may have just discovered a new one.

Anybody else have anything similar???

I actually had this happen to me during a live gig. It ran fine for about 45 minutes into my set and then dead air.

I had to have the guest dj step in while I reverted back to TP 1.1.2, which I had the installer on my laptop just for the instance.

Hopefully NI looks into this.