maybe look at Trainspotter and see how the do what they do.
maybe look at Trainspotter and see how the do what they do.
from what i could see, they just manipulate the collection.nml....
i already knew that program. But it can't help me much.
The problem with memory editing is that traktor doesn't seem to use the same memory addresses all the time. For example:
I searched for the string "Loneliness" in the memory. The result was a set of several memory addresses but one, in particular, catched my attention. So i noted the address and then restarted the traktor. In the second run, the save value that i found in the previous search was located at a different address....So, i can't make a "traktor trainer" :/
So you want to prod around in Traktor's memory when it's running? I really don't think this is a sensible idea, I think you would be better off trying to reverse engineer the TRAKTOR4 tag.
that's what i though before.
the problem is that, if i just reverse engineer it (http://dope.cz/code/), i would still have the problem that once the track is in the collection, the tags will never be accessed, unless you erase it from the collection and insert it again....
that would be a pain in the ass.
|
Bookmarks