Traktor 4.3.0 - Beatgrid setting "issue" still there

Following on from my previous post after the 4.2.0 update:

https://community.native-instruments.com/discussion/45935/traktor-4-2-0-manually-setting-beatgrid-issue

The same "issue" is in the 4.3.0 update.

I have now logged a ticket as a bug.

This workflow has not changed in years … I mean many many YEARS … I'm tempted to pull out one of my old MacBooks (circa 2007) and fire up the version of Traktor on there …

As previously stated, this is probably not an issue for everyone but when you've been doing something the same way for nearly 20 years, and it works well … I'm not sure what "bug" this change fixed.

Find more posts tagged with

Comments

Victor_Ruderalis

My track prep routine is pretty much the same as yours. I remember being totally confused at first and it took me a while to get the hang of it.

Eventually, I found a workaround — when I’m prepping tracks, I just use my MacBook keyboard and mapped one of the keys to toggle Snap on and off. Super handy once you get used to it.

Owner

https://community.native-instruments.com/discussion/comment/243925#Comment_243925

That's also how I do it. Mapping the keyboard to grid tracks has made a lot of things easier for me. I'm now almost as fast at gridding an old disco track as I would be if I were warping it in Ableton, for example.

I still don't fully understand user @frankle problem and can't reconstruct it. Ultimately, it's probably just cumbersome to change something when you've done it the same way for years. But I never want to miss out on the new possibilities we now have with grids. I wouldn't want to go back.

Let's see what his ticket comes out with. Perhaps it will be further developed at some point, and then a solution will emerge that works for everyone.

frankle

https://community.native-instruments.com/discussion/comment/243984#Comment_243984

If you take a look at my original thread I have screenshots of the issue.

Essentially I have had SNAP on for the last 10+ years and when I set my manual INITIAL BEATGRID it sets the grid point to where the play head is …

Now, with 4.2 and 4.3 it does not do this, it snaps to some imaginary beatgrid point that Traktor has decided is the downbeat, even when I explicitly DO NOT get it to analyse the beatgrid.

I actually fired up my old black plastic MacBook (Late 2007 … for those with that on their bingo card) that turned on after I finally found my Magsafe 1 charger … the battery is completely shot …

OS X 10.7.5 "Lion" with Traktor Scratch Pro 2.6.8 from around 2014.

EXACTLY the same workflow as 4.1.1 where you can have SNAP enabled and when you set the beatgrid, it goes where the playhead is positioned.

It makes me want to rip out the PowerBook G4 12-inch that I still have that used to run Traktor DJ Studio 3 to see how it worked then.

As I've said, they "fixed a bug" that did not exist.

If only they worked on some of the other "actual bugs" that have been in the software for over a decade …

Quick links

Unanswered questions