parallel waveforms problem

I can't see the full waveform in a nice way .
waveforms looks blurred after 70 or 80 beats

Happens in an old macbook pro (2012) but also in the last 15" model .

 

hallo man-tk, unfortunately this is a limitation of the current waveform implementation.
Can't promise something but will see if we can extend this for the next release.
In the end its a trade-off between used resources and available waveform lookahead.

 

thanks for the answer , it looks like we have better feedback now .
BTW , i'm using last update in the club without any problem .

 

nice to hear that

 

I have this problem too, and it affects BOTH the parallel waveforms and the regular waveforms, as reported here. IMO calling this a limitation is an understatement. Technicalities aside, if the track has already been analysed, I can't see how this would require more resources than, say, 3D modelling software which runs smoothly on my laptop and is able to rotate complex 3D models without a glitch. If a track has already been analysed, all Traktor needs to is load an image, and then scroll it past the screen. This works fine in other DJ programs.

Also, the waveforms are super laggy when dragged with the mouse. This was an issue in TP2. In the following screen capture, the track is stopped, and yet the waveform keeps moving after the mouse has stopped, while the mouse button is still being held down::

 

Fabian, thanks for the reply.

I fully understand that NI has to be mindful of their global users when implementing new features which may be processor/memory dependant or as you say 'a trade off between resources' but there are other programmes out the who have provided this feature for a long time and 'competitors' who are taking on the 'industry' standard and challenging the norm, and it just works from the get go.

Ni should not bend to pressure from end users to implement a feature, in this case, parallel wave forms which i'm currently using and i think is fab, but doesn't work as it should - compared to your competition without ensuring that it works almost flawlessly, and i respect that NI apologised for keeping the latest Beta closed [correct me if i'm wrong] but your beta testers [bigger the better] are and always have been necessary for ensuring that bugs and issues are quashed as soon as possible.

I'm a new user to NI products having left the DJ scene a long time ago so this is more of a hobby for me, but i am enjoying the hardware that i have recently purchased and it is clear to see from the user base that there are a lot of people who just want to see things happen, but as customers happen sooner rather than later.

As an aside i'm running Traktor on a high end Windows laptop with absolutely no resource tradeoff, i have a SSD connected directly to my S4 Mk3 and it performs fantastic. I also have a 6 year old Core I5 windows laptop which also has no issues with the latest version running parallel wavef orms, so to perhaps justify resource as a trade off i think was shortsighted.

Just my 2 cents.

 

hey Revan,

please consider that we had to subsequently add this feature to a 19 (!) years grown software what is technically challenging.
Thats why competitors who have that since a long time are doing better at Parallel Waveforms.
(But they miss many other features Traktor Pro has )
On longterm we are building up a new codebase to fix those impediments but that takes time.

For Traktor Pro there was the option to do this long requested feature with trade-offs or not doing it at all.
It was discussed for several years in the company until two people in the team volunteered.
So they did what was possible within the time constraints for TPro 3.1.0

Personally i believe we make some users that requested it (more) happy.
The other users will continue to use the classic layout which will always stay the default for Traktor Pro.

In the end again i can't promise something - but will see if we can improve this for the next update.

 

NO Fabian : you are wrong here , competitors don't have better parallel waveforms , at min. zoom they show same amount of beats after play position , BUT they don't have PlayMarker Position who is a big thing for Traktor users .
SAME happens also to RB , showing even less beats and without the Play Marker Position Option

If Dev team can correct this issue Traktor will have better waveforms than the rest with no DOUBT

 

i find this only happens when i have the playhead offset. at 50 where it’s in the middle, no blurring. only a blur for the offset portion.


Sent from my iPhone using Tapatalk

 

Hey Fabian, I really appreciate this perspective. I know what it's like working on a big team with many competing priorities and limited resources to serve them all. I'm sure I speak for most of the NI user community and say that we're grateful it made it in there at all!

A few users and I have been discussing alternative layouts for the parallel waveform function over on this thread: https://www.native-instruments.com/forum/threads/parallel-waveform-layout-request.348695/

I'd be grateful if you could forward it to the attention of those two unsung heroes responsible for the current implementation! I'd be curious to hear their thoughts if possible.

Thanks again and best,
Noah (Jumeirah Sound System)