V4 build 2099 to run…
Hi n-Trackers:
Today, I’m working on re-organizing the VST Folder/Folders on my C-Drive and to get v4 build 2099 to work, on this P-111 Asus/Intel computer…
After the installation of v5, I could no longer get v4 build 2099 to operate on my setups… After launching build 2099 and pressing the play button n-Track would just “Close” shut down leaving the Operating System desk… XP, on the monitor screen…
To begin the process, I created a System Restore Point… then I created a VST Folder in the Program Directory and cut-and-pasted all the .dll files/information that was in the v4 VST folder to the new VST folder in the program file directory. Then, I opened V4 build 2099, opened the prefs. and changed the place where the VST Folder is found… Then… I did a VST re-scan… However, after some time the VST Scan did not complete the task, and “Closed”… (the VST Scan could not complete and n-Track needs to "Close)…
Then, I opened a .wav file on the timeline and pressed the play button… Now, v4 build just locks up… but, it doesn’t close… and the time-line cursor doesn’t move, on the timeline… But, it is better then it was… no “Close Exception”… I just did an “Exit” from n-Track v4
Next, I opened n-Track v5 build 2193 and waited till a VST Scan completes… It takes forever … and doesn’t complete… However, n-Track does open to a desk and plays… and the cursor scans the timeline… I opened the prefs. and changed the place where n-Track looks for the VST .dll files… (the same place where v4 build 2099 looks for them)… I closed v5 and re-opened n-Track… Now n-track does a VST Scan that doesn’t complete… The VST scan window says the VST scan cannot complete the scan and needs to close… But, n-Track will run when I push the “Play” button…
Something is not right with n-Track on this P-111 computer… I believe that I can do a system restore and return to the “Restore” point I created earlier this morning…
However, I’d like to pursue this issue to see if I can improve this quandary and get v4 build 2099 and v5 build 2193 to behave as they should…
Can you suggest what are some things that I can look at (and try) and correct to make all this right?
Bill…
switch OFF system restore -
remove both versions of N (v4 & v5) from your PC - run registry checker (reg mechanic or something like that) -
install V4 FIRST and get it to run - (you will have to re-register it so have a copy of your codes handy)
make new folder for V5 (ntrack5) will do - do not install v5 in v4 folder keep them seperate -
install v5 into new folder - open v5 and set VST folder path to VST plugin folder where you installed V5 (VST path in v5 is set to OLD v4 VST folder by default) -
it should now run correctly, try it for 2 days or more if OK switch system restore back on and DELETE all prior restore points, set new restore point from that day - DO NOT set new restore point before you are happy with it (DO NOT try to use old restore points as registry will be altered) -
Dr J
Bill,
It sounds as if you may have a plugin that ntrack doesn’t like or has become corrupted. (I found one or two when moving up to V5. Pity I can’t remember what they are).
I suggest that you move all the files out of your plugin folder and then move a few back at a time, re-starting n-track each time. When you find a batch that causes n-track to crash, move 'em back out of the VST folder and move them in one at a time until you find the culprit.
There is a VST scan log file somewhere that may also tell you which one is giving the problems.
PITA, but it doesn’t hurt to clean up the plugin folder occasionally.
X
.
.
Correct, plugins can mash N up when changing versions - the problem i had was i uninstalled V4, then realisied that i may want it again so reinstalled it, then had all the problems that Bill is having - had to do the above to get both to work again –
Dr J
Hi Guys:
I see that this isn’t gonna be an easy task… I’m not a guy that can work on computer issues with any amount of confidence. But I’ll tackle the job, if I have to… Not having build 2099 is not the end of the earth…
After reading your replies, I may give it a day-or-two to contemplate how I’ll approach this… At first glance I have this in mind…
What if I do a system restore now… to get build 2099 and build 2193 back to normal, or as they were? Then approach build 2099 in some manner that will not stress build 2193?
Can build 2099 be removed without affecting build 2193? That is, if I can direct the VST scan to look where the new VST folder is located? My thinking is, if I can get v5 to exist without v4… Then find a way to re-install v4 but… on is own/ without any connection to v5… If I can’t get that I’d just drop v4… Or maybe, install v4 on another drive, altogether…
I just had a look at the control panel in the “Add-and-Remove” programs… where, I see both n-Tracks (v4) and (v5) as separate identities…
I’m gonna look at the registry and see how v4 and v5 exist there… Maybe, I can … wait… I’ll look…
I use RegCleaner 4.3… I see only two references to n-Track… One… Just n-Track and another saying n-Track v5… If there’s any other references I must have missed them…
Now might be a good time to back-up this registry… Well, that’s if I can get build 2193 to scan the VST file… ??
Bill…
start from scratch Bill - dump them both then reg clean, install V4 FIRST get it OK, then install V5 - IT WORKS, TRUST ME - BEEN THERE, DONE IT, BOUGHT THE TEE SHIRT etc (and you dont lose anything in the process) - FORGET SYSTEM RESTORE you are just adding complications to what is a very easy task - PLUGINS, best to put them ALL in the V4 VST folder as this is the default folder used by both versions -
Dr J
Hi Doc:
I have some mail (on-it’s-way) over to you…
Gents:
I hope this isn’t an up-hill battle… v5 is working O.K. as much as I know… I wouldn’t want v5 to come back and bite me in the Back-Side… 
Bill…