Traktor 2.5. How was your first weekend of gigs with it?

Home :: NI - Native Instruments S4/S2 Controller talk :: Traktor 2.5. How was your first weekend of gigs with it?Reply
Traktor 2.5. How was your first weekend of gigs with it?
Posted on: 26.05.2012 by Jake Vierow
I'll start:

Weird loop issue. Set an 8 bar loop, but the loop starts 8 bars later?

Grids: seems like the grids are even more screwed up! No where near where the transients are!

I was finding it hard to see the benefits of the upgrade at my gigs this weekend

How'd you guys go?
Cody Mcnall
01.06.2012
Originally Posted by beaubryte
What did 2.5 REALLY give us?? I still have no clue yet. 2.5 needs some work, badly. Now I'm patient enough (holding my breath since 2002) for n.i. to solve it. They will eventually.
Mappings behave different with 2.5, I fixed most issues but somehow I really feel Traktor isn't running smoothly and responsive as in 2.1.2. My S2 mapping feels and acts different, though everything works and it does what it should.
I had some glitches while connecting another USB device, like an audio8dj and an external hdd. Also browsing through my (analyzed) collection gave me some drop outs. Tracks are not syncing tightly as before. Time code switches from absolute to relative or internal mode for no reason..Then I even found out about more bugs at the n.i community , that's when I decided to roll back. So after 3 days of experimenting I decided not to use 2.5 until the next update or I might even wait for till the remix functions are mappable to Maschine. I got many gigs this summer so no experimenting before fall.
I am happy with 2.1.2., love performing with it.
So again, what did 2.5 give S2/S4 performers? anyone?
Agreed....seems like theres more problems to fix right now then there are benefits
Cira Ditz
30.05.2012
Originally Posted by beaubryte
What did 2.5 REALLY give us?? I still have no clue yet. 2.5 needs some work, badly. Now I'm patient enough (holding my breath since 2002) for n.i. to solve it. They will eventually.
Mappings behave different with 2.5, I fixed most issues but somehow I really feel Traktor isn't running smoothly and responsive as in 2.1.2. My S2 mapping feels and acts different, though everything works and it does what it should.
I had some glitches while connecting another USB device, like an audio8dj and an external hdd. Also browsing through my (analyzed) collection gave me some drop outs. Tracks are not syncing tightly as before. Time code switches from absolute to relative or internal mode for no reason..Then I even found out about more bugs at the n.i community , that's when I decided to roll back. So after 3 days of experimenting I decided not to use 2.5 until the next update or I might even wait for till the remix functions are mappable to Maschine. I got many gigs this summer so no experimenting before fall.
I am happy with 2.1.2., love performing with it.
So again, what did 2.5 give S2/S4 performers? anyone?
I guess I've been lucky (reading the very many comments about the update everywhere), and still not had any bad issues with my imac on snow leopard. I've purposely not upgraded my windows laptop as I use that for a 5 hour residency evry fri, and don't want to put the bar's taking at risk from me having any unexpected issues.

But, things I loved about the update are:

1) analysing playlists seems to be quite zippier.

I don't have any tracks with more than one beatmarker, so that wierd bug hasn't affected me

2) LOVE that decks C and D now can be full adv size (before only small and micro).
Tbh I hardly used decks c and d on my S4 just as it was harder to see what I was doing. Now they're all full size and look great on my imac, and I always toggle between decks and browser on my laptop so the extra size of C and D now isn't going to be a prob when I get round to updating my laptop.

3) The sample decks are a lot better in all ways
Just being able to retrigger very quickly and fire off volleys off the same sample really makes them more intiutive.

I can't get an f1 for the forseable as am broke this month :/, so will spend that time checking out further the extra with my s4, and maybe I can get everything I want from that. But the F1 still looks a very promising bit of etra kit - even more so now read today's review on DJTT
Jake Vierow
26.05.2012
I'll start:

Weird loop issue. Set an 8 bar loop, but the loop starts 8 bars later?

Grids: seems like the grids are even more screwed up! No where near where the transients are!

I was finding it hard to see the benefits of the upgrade at my gigs this weekend

How'd you guys go?
Lashay Walchak
12.07.2012
I've left my gigging laptop at 2.1.2 for now.

Do have my "studio" machine running 2.5 and have been mapping my newly acquired Mikro to work alongside my S2. My mapping had Sample Slot "Slicer" function which allowed me to fire off the sample at the start, 1/4, 1/2, and 3/4. Not achievable on 2.5. Other than that though everything seemed to be there and working. If memory serves correct 2.5 did change some of my modifiers for Sample Deck control that did cause problems, but I simply sorted my functions by modifier's 1 & 2 and fixed the problems.

LOVE the new automated and learn functions for mapping Outputs.

I've slimmed down my S2 map as I've gained controls on the Mikro. Got rid of Loop Recorder (except Dry/Wet) controls on the S2. Got rid of Snap and Quantize on S2. Did away with Record controls as well. Also got rid of FX unit on/off controls on the S2 and have been dabbling with creating a "Slip Mode" feature that uses the FX unit on buttons to change deck flavors, copy from deck, and other controls to turn down the volume on A/B and up on C/D to do your scratch or loop, then you return to deck A/B as the track continued to play. All of that was achievable on 2.1.2 as well, however I didn't have a secondary controller to get rid of buttons I've used to make these new features work. I haven't touched my MIDI map which allows control over any deck or FX unit from either side of the S2. Not sure what may or may not be buggy on that yet.

I will be changing the Laptop very soon once I finish up mapping the Mikro. I have two pages left if anyone has some recommendations. Already have 8 hot-cues for all decks, Ean's "Synth" (Fln-F, F92, T3 Delay with parameter controls and key adj), Shiftee's "Plooper" for A/B (really just loop controls), modified Instant Grat, and LFO "Wobbles".
Maryland Garciasanchez
12.07.2012
i updated to 2.5 and i will be using traktor 2.5 for the first time this weekend, fingers crossed everything goes ok. i have tested it out at home and it seems fine, but supose you never know untill you actually put it through it's paces at a full gig
Cody Mcnall
01.06.2012
Originally Posted by beaubryte
What did 2.5 REALLY give us?? I still have no clue yet. 2.5 needs some work, badly. Now I'm patient enough (holding my breath since 2002) for n.i. to solve it. They will eventually.
Mappings behave different with 2.5, I fixed most issues but somehow I really feel Traktor isn't running smoothly and responsive as in 2.1.2. My S2 mapping feels and acts different, though everything works and it does what it should.
I had some glitches while connecting another USB device, like an audio8dj and an external hdd. Also browsing through my (analyzed) collection gave me some drop outs. Tracks are not syncing tightly as before. Time code switches from absolute to relative or internal mode for no reason..Then I even found out about more bugs at the n.i community , that's when I decided to roll back. So after 3 days of experimenting I decided not to use 2.5 until the next update or I might even wait for till the remix functions are mappable to Maschine. I got many gigs this summer so no experimenting before fall.
I am happy with 2.1.2., love performing with it.
So again, what did 2.5 give S2/S4 performers? anyone?
Agreed....seems like theres more problems to fix right now then there are benefits
Cira Ditz
30.05.2012
Originally Posted by beaubryte
What did 2.5 REALLY give us?? I still have no clue yet. 2.5 needs some work, badly. Now I'm patient enough (holding my breath since 2002) for n.i. to solve it. They will eventually.
Mappings behave different with 2.5, I fixed most issues but somehow I really feel Traktor isn't running smoothly and responsive as in 2.1.2. My S2 mapping feels and acts different, though everything works and it does what it should.
I had some glitches while connecting another USB device, like an audio8dj and an external hdd. Also browsing through my (analyzed) collection gave me some drop outs. Tracks are not syncing tightly as before. Time code switches from absolute to relative or internal mode for no reason..Then I even found out about more bugs at the n.i community , that's when I decided to roll back. So after 3 days of experimenting I decided not to use 2.5 until the next update or I might even wait for till the remix functions are mappable to Maschine. I got many gigs this summer so no experimenting before fall.
I am happy with 2.1.2., love performing with it.
So again, what did 2.5 give S2/S4 performers? anyone?
I guess I've been lucky (reading the very many comments about the update everywhere), and still not had any bad issues with my imac on snow leopard. I've purposely not upgraded my windows laptop as I use that for a 5 hour residency evry fri, and don't want to put the bar's taking at risk from me having any unexpected issues.

But, things I loved about the update are:

1) analysing playlists seems to be quite zippier.

I don't have any tracks with more than one beatmarker, so that wierd bug hasn't affected me

2) LOVE that decks C and D now can be full adv size (before only small and micro).
Tbh I hardly used decks c and d on my S4 just as it was harder to see what I was doing. Now they're all full size and look great on my imac, and I always toggle between decks and browser on my laptop so the extra size of C and D now isn't going to be a prob when I get round to updating my laptop.

3) The sample decks are a lot better in all ways
Just being able to retrigger very quickly and fire off volleys off the same sample really makes them more intiutive.

I can't get an f1 for the forseable as am broke this month :/, so will spend that time checking out further the extra with my s4, and maybe I can get everything I want from that. But the F1 still looks a very promising bit of etra kit - even more so now read today's review on DJTT
Johnetta Olewine
29.05.2012
LOL @ the involuntary NI beta testers.
Claire Auyeung
29.05.2012
@KILLMeDJ: +1
Jake Vierow
29.05.2012
Do NI actually have DJ's on their development team?
I know they have endorsees pimping their stuff after the fact.
But the kind of issues we're finding seem like something a working DJ would find in the early BETA stages.
It;s a shame these releases are a bit of a fizzer =(
Claire Auyeung
29.05.2012
What did 2.5 REALLY give us?? I still have no clue yet. 2.5 needs some work, badly. Now I'm patient enough (holding my breath since 2002) for n.i. to solve it. They will eventually.
Mappings behave different with 2.5, I fixed most issues but somehow I really feel Traktor isn't running smoothly and responsive as in 2.1.2. My S2 mapping feels and acts different, though everything works and it does what it should.
I had some glitches while connecting another USB device, like an audio8dj and an external hdd. Also browsing through my (analyzed) collection gave me some drop outs. Tracks are not syncing tightly as before. Time code switches from absolute to relative or internal mode for no reason..Then I even found out about more bugs at the n.i community , that's when I decided to roll back. So after 3 days of experimenting I decided not to use 2.5 until the next update or I might even wait for till the remix functions are mappable to Maschine. I got many gigs this summer so no experimenting before fall.
I am happy with 2.1.2., love performing with it.
So again, what did 2.5 give S2/S4 performers? anyone?
Roy Houn
28.05.2012
I had a play at home yesterday, and i noticed using my turntables thu my S4 that when i was adjusting the tempo the tempo slide on the macbook and the bpm wasnt adjusting accordingly altho the track was actually increasing/decreasing..anyone else had that? tried to recalibrte but didnt do anything
Fidelia Messing
28.05.2012
only really heard problems this far.
Jake Vierow
28.05.2012
It's weird, but unless I try something on a gig I never really find out what the real issues are.
like the pressure.
Plus I have an array of back up options so I'm never really without a safety net.
Cira Ditz
27.05.2012
Mine was fine. Some of the tracks were out of sync with beatgrids when I was checking them after install, but just re analysed them and all seemed to reset themselves thankfully. Did three sets of industrial/electro/hardstyle/gabba (and gaga) and thankfully no probs.

Was all looking forwards to dropping in some samples but the evening was so full on kinda forgot I had them haha. Thankfully all went good. Was on my imac, and had my laptop with the last version just in case
Luke Loughin
27.05.2012
Are there any improvements for timecode users in TSP2.5? Wont be using the remix decks personally.
Johnetta Olewine
27.05.2012
People really gig with first release NI updates? Jesus.
Nedra Fresneda
27.05.2012
It's not worth the risk updating before a gig, learn early or learn the hard way.
Classie Alvizo
27.05.2012
haha

far too close to the weekend for me to upgrade, for exactly this reason. Don't want to turn it on and find any unusual surprises I have some work to do Tuesday/Wednesday and then will go for it Wednesday evening , give me a few days to sort any issues should their be any before the weekend.

k

<< Back to NI - Native Instruments S4/S2 Controller talkReply

Copyright 2012-2023
DJRANKINGS.ORG n.g.o.
Chuo-ku, Osaka, Japan

Created by Ajaxel CMS

Terms & Privacy