This is really simple - I can't bel;ieve so many people have fluffed this up:
IF IT AIN'T BROKE, DON'T FIX IT!!!
Good advice. I think I'll start doing that. :thumbup1:Quote:
Originally Posted by deathy
Printable View
This is really simple - I can't bel;ieve so many people have fluffed this up:
IF IT AIN'T BROKE, DON'T FIX IT!!!
Good advice. I think I'll start doing that. :thumbup1:Quote:
Originally Posted by deathy
True.Quote:
Originally Posted by Jester
I keep a version history manually on the local drive, Dropbox for daily changes and Crashplan for full scale backup.
I have a different opinion. If your update hasn't been fully tested and gone through the QA process, DON'T RELEASE IT.Quote:
Originally Posted by Patch
Some of these issues are so major, I can't see how they missed them during QA, if there even was QA.
At the very least, this update should have been released as a beta; that way there is fair warning that there may be issues.
I wanted the iTunes node updates in this patch very badly...that's why I jumped the gun. I'm sticking with 2.7 for now since there's a workaround for the scaling problem I'm having, but thank goodness you can go back to 2.6 so easily.
It was released as a beta...then as a release candidate...for their team of beta testers.Quote:
Originally Posted by Glitchwerks
Case in point:
The thought that any company could possibly release something without going through the huge, monumental undertaking that is a software release is nothing but asinine. I get that you're angry, but the sky is not falling the way you seem to think it is. Computers are complicated. Shit happens.Quote:
Originally Posted by Karlos Santos
One thing I might have noticed....are the issues people are reporting mostly with Windows? Most of what I've noticed in this thread has seemed to imply that.
Good word. :thumbup1:Quote:
Originally Posted by Mos
And they failed to catch all these issues before release? They need some new beta testers.Quote:
Originally Posted by mostapha
First off, I'm not angry. Let me be clear on that. Since I can easily switch back to 2.6.8, there is absolutely no damage done. It's an inconvenience, although some people are clearly having more issues with it than I am.Quote:
Originally Posted by mostapha
I have not made it out to be like the sky is falling either. I expressed frustration in a previous post, which was made in the heat of the moment. Once things were explained about how to go back to 2.6.8, my frustrations were alleviated.
So do not make my posts to be something they are not and do not take things out of context. Thank you.
Now, it is NOT asinine in the slightest to expect updates to be functional and without huge issues. Minor bugs are tolerable. It happens. However, things like the scaling problem and other issues people are having? Yeah, that's not acceptable. That indicates they really didn't do much testing at all except maybe on a limited amount of platforms. I am not convinced there was much QA at all.
My issues are on Windows, yes.Quote:
Originally Posted by mostapha
Im a fan of NI, but its very clear they rushed this release out because of the S8 leak.Quote:
Originally Posted by mostapha
They broke screen sizing on higher resolutions, and completely broke support for two file formats, ALAC and WMA. These are bugs that should have been found in the first 5 minutes of beta testing, they are not edge cases.
Its a major screwup for their QA process, and I assume there are some stony faces at their support meeting this morning.
But dont forget its super easy to run the old version of Traktor without uninstalling anything. The old executables are all in the Traktor/backup folder.
I don't think I've ever playd ALAC or WMA files, so I never would have caught those. And I think rMBPs are travesties of design, so I won't have to deal with that unless my MBP dies before Apple gets their heads out of their asses.Quote:
Originally Posted by ImNoDJ
So, either I'm not a qualified beta tester or you probably should be.
So....anyway...
My collection got royally screwed up somehow..."missing" an un-analyzed files that were clearly there and had been analyzed. Rather than fixing it, I decided to take the gamble that things mostly worked on OS X and that beat grids and saved cues/loops were stored in metadata.
Just had a little play and the only "issue" on 2.7 and Mountain Lion is the LED off-state brightness thing...which isn't an issue unless you actually have zero lights on, since it's hard to tell whether they're all on or all off. With more than none and less than all of the lights on, it's fine. Also, it helps if you're not playing in a super-bright room.
The iTunes integration is fantastic. I don't know how it'll work long-term, since it seems to require re-starting traktor in some cases. But so far it's leaps and bounds beyond Traktor's actual collection browser, which I've always kind of hated.
And it plays AIFFs. Except for some MP3s from a brain-fart before I just changed the defaults, that's all I play. So, I'm happy.
We'll see if something comes up.
The LED issue is being worked on and is an issue with Controller Editor - fix is imminent.
The ALAC issue is a goes a lot deeper and is not simply a bug introduced by NI. I hope to be able to share more on this asap.
Appreciated Karlos.Quote:
Originally Posted by Karlos Santos
Awesome.Quote:
Originally Posted by Karlos Santos
Like I said, it doesn't actually bother me as long as there's contrast. When it does get fixed, I'll probably end up asking why none of my lights turn on, 'cuz I think I turned their off state all the way down.
Actually if you delete Controller Editor v1.7.1 and reinstall v1.7.0 the issue goes but ... I was told the fix is on the way.
Agreed, i just work here :) but feel free to make a suggestion in This threadQuote:
Originally Posted by niknok
That is WAY too much trouble. And by that I mean....does controller editor work the same way as traktor with the parallel installs?Quote:
Originally Posted by Karlos Santos
I believe that CE v1.7.1 just brings Kontrol S8 functionality into Traktor so v1.7.0 will work fine on T2.7.0
Umm, my Backup is actually in Documents/NI/Traktor 2.6.8/Backup This is the way it was installed. Is this wrong? Should it be moved? In the path that you described in the Traktor 2 folder there is the application itself and the documentation folder. This is all in my rMBP running Mavericks. Thanks.Quote:
Originally Posted by Karlos Santos
And not trying to derail the thread at all but just curious what things turn ya off about the rMBP, mostapha? I enjoy mine thus far, except for some minor screen issues (smallest backlight bleed and maybe a bit discoloration).
Just copy/paste the entire native instruments folder. As a rule, you should back this up after every gig/mix.
P.S delete the contents of the backup collection folder as this can get rather large . e.g over 20mb per session
Nice.Quote:
Originally Posted by Karlos Santos
My question was actually whether I needed to download CE 170 somewhere or if it's somewhere in my NI folder. Unfortunately, my wife is asleep in the room with my MBP, so I can't check for myself right now.
I don't want to get off topic, but I'll answer...PM me if you have a follow-up. I was a computer dork long before I was an Apple user. Soldered RAM and non-commodity SSDs are unacceptable to me....there are better (and significantly cheaper) than OEM options available, and there always have been.Quote:
Originally Posted by Chelan
I'm just bitching because my next Apple laptop is going to cost more than my last one and I'll have to send it into Apple if the RAM dies....which I haven't actually had happen since....idk....1998ish. I'll eventually come around just like everybody else and continue to give Apple money because OS X is worth it. But, I'm going to bitch about it 'till it happens.
To those who experience the problems with screen resolution and scaling on Windows:
NI replied today with a solution/workaround.
This seems to fix the problem for me. Traktor launches in to fullscreen as settings indicate, and everything seems to be in order with scaling now.Quote:
Please try the following:
• right click on the Traktor application icon
• click on properties
• click the compatibility tab
• check "disable display scaling on high DPI settings"
Edit; They also replied on the audio distortion on deck C and D. Disabling Multicore Processor Support fixes the distortion. It doesn't affect performance appearantly.
That works for me too. I hadn't had distortion problems, but I went ahead and disabled multi-core support.Quote:
Originally Posted by AndiPandi
They are your collection and settings backups.Quote:
Originally Posted by Chelan
The application backups should be in the folder I posted. In Applications/Native Instruments/ there should be a Traktor 2 folder with these folders:
Attachment 23942
I have been playing an almost weekly residency with Traktor, timecode vinyl, Macbook Air, and DJM-900 for two years (been using it with an Audio 6 for 5 years) and have never had a single issue. Last night I had two 4 second or so audio dropouts /glitches; only thing changed was being on 2.7. Back to 2.6.whatever for me. Just thought I'd throw that out there.
FWIW, it's still fine for me on ML and a FW410. I should really get around to switching back to the last controller editor.
you have to right click on the traktor logo on the desktop go to properties then compatibility an tick disable display scaling on high DPI settings
Quote:
Originally Posted by gunshy
Wait...wut? Can you explain this?
Fullscreen fix go to the desktop right click on traktor logo go to properties then compatibility an tick disable display scaling on high DPI setting
Well, I don't use desktop shortcuts, but:Quote:
Originally Posted by Chubby Racer
Go to C:/Program Files/Native Instruments/Traktor 2
Right click on Traktor.exe
Select Properties.
Select the Compatibility tab.
At the bottom there will be an option to Disable display scaling on high DPI settings.
Check that, then hit OK.
apparently not...2.7 you are dead to me (just kidding, settle down in the cheap seats)Quote:
Originally Posted by niknok
Oh dear, first time I've ever had a TSP update that has been bad. :(
Installed 2.7 and had a bit on a nightmare with it;
MBP late 2011 build on Mavericks
Z2
1210's
X1 Mk2
F1
Deck A couldn't calibrate, kept telling me to check the vinyl and or stylus. Changed both still had the problem, checked and re-checked ground leads etc.
Sound wasn't right either so closed it down and tried 2.6.6 and everyone worked perfectly. So thats 2.7 binned, going to roll back to 2.6.8
Really surprised, never seen a shoddy update from NI before.
Good news for us Dual-Booters. Will keep 2.6.8 on my SSD for the time being till i do some thrash testing :)
You must be new round here :)Quote:
Originally Posted by anteater32
And 2.7.1 is out, free to download in your nearest Service Center.
Nothing on Yosemite compatibility, unfortunately.Quote:
* Several bugfixes
* Updated Controller Editor to Version (1.7.2)
* S8 manuals are included into the installers
Yeah, I think I'll continue to wait to upgrade until I've heard from other folks who can't resist the upgrade.
2.7 screwed up a number of things for me, so I'm going to go ahead and update.Quote:
Originally Posted by deathy
400+ MB, installation takes a while.
I wish they'd add a progress bar to the service center.
Okay, finally got it up and running.
They fixed the brightness issue with the buttons.
They sort of fixed the full screen issue. Sort of. This may be really difficult for me to explain.
It will go to full screen no problem if you're using your main monitor or a single monitor. I run Traktor on a second, larger display from my laptop. It won't go to full screen on the second monitor. I turned the monitor off and on again, so Traktor will switch to my main monitor, and then when I move the Traktor window to the second monitor and select full screen, it will work.
However, I'm guessing it's at 1080P now, so everything is quite small. I went back and disabled DPI scaling and it looks like it should now. I'm just going to stick with that, I guess. So it's still bugged.
Now before anyone jumps on me for complaining about that, I do realize that running Traktor on a second monitor is probably seldom used by people and not a big priority. I just feel it should work.
I don't use ALAC or any Apple file formats, so I can't report if they got those working yet.
ALAC issue is not fixed in 2.7.1
It is still being worked on.
I've just made an update and the issue seem to still be present on my machine (OS X) and S2kmIIQuote:
Originally Posted by Glitchwerks
What OS do you run?
Windows 8.1 aka Microsoft's biggest mistake ever. :thumbdown:Quote:
Originally Posted by Stewe
I tried 2.7.0 on my windows 8.1 machine and am getting some weird beatmasheresque effect on about half my tracks. All my tracks are wav or mp3. The effect even shows up in the waveforms, like a stutter at the beginning of the track. Anyone else experience this? I'm using my phone as a mobile hotspot and don't have the bandwidth to try and download the 2.7.1 version at the moment to see if this was fixed.
Well the good news is they seem to have corrected the issue with the 2.7.1 update. I tested it today and the attack was spot on. Going to do a full Midi Fighter 3D mapping for it now... :thumbup1:Quote:
Originally Posted by rdej47