There have been a few guys that have had Hardware and or Driver issues over the recent months that have moved on from the n-Track community.. Maybe, they were ready to move on anyway.. There was an Alabama guy (Yaz and Him used to trade Threads) and a guy from one of the Baltic Countries.. mwaha ? was that his ID.. ?
mawah, was unable to get n-Track and the Hardware he used to record in MONO Tracks.. I think that was the issue, with him.. It's too bad.. these guys have so much to offer to the n-Track community with there audio experience-and-knowledge.. Anyway, and maybe these guys will re-appear and contribute to the Board... again.. Who knows..
I have no reason to say this.. BUT.. I think these guys were and are part of the AMD Camp of the computer class.. If you're not in the Apple/Mac camp and you're in the audio business I believe you should be in the Intel Camp..
I say this without trying to light any fires and support any partiality to what kind of computers to throw one's hard-earned money at..
I sure have plenty of issues with these old P-111 and P4 Intel Boxes I have around here..
Just when I think I am ready to track and put creativity to-task, a fly gets in the ointment and I end up with Big-Time Issues to un-fathom.. Mainly, I think it's trying to stay "Current" with these Service Packs and Windows/Microsoft Security Updates, and all.. and then my setups balking at the stress-of-it-all..
Well.. that's what I think..
Bill..
Well, that may be what backfired on me ..for my latest DAW I bought a real IBM with an Intel P4 and a real intel chipset...XP pro, service pack 3..and then the problems began in earnest. My old machine was an AMD athlon on an ECS Motherboard and Win2K pro...I ran N 3.3 and my Delta 66 for 3+ years without a single crash or issue... I bought some high falutin' plugs and got caught in the plugin/latency/automation bug..got the new machine, upgraded to V6 and the dance began..I haven't cut a single keeper track (with N) since July..sigh...
This Looping Issue has me wondering if I am sure that it has nothing TO-DO with n-Track or any other Multi-Track Editor… for that matter…
I had a nice reply going and my computer shut down and rebooted… for no reason… I think I have a faulty stick of RAM… It needs addressing… Anyway, after the run I’ll return to the thread and see if I can repeat what I was almost ready to post…
This delay/latency in what is shown when “Looping” is seen as in-consistent on as many computers as there is out there… Let’s say every machine is given the same/identical tracks to display and repro on a timeline… The play button is pressed and timeline scans/streams the files from the hard drives… The graphics cards are all different… The hard drives are of different manufacture… different Main boards,.etc The latency reported are gonna be close but not exactly the same… NOW… AN Area of the timeline is set to “LOOP”… This is where I am unsure as to the “LOOPED” area of the timeline is not “Streamed” It is reproduced from the RAM… I stand corrected on this… BUT… if the ram repro’s the timeline then… as many sticks of RAM that is used there are then as many different latencies are introduced to the Graphics cards and monitor latencies… as well…
Maybe, some of you might be able to elaborate on this theory I have… Could this be what we are seeing when we “LOOP” an area of the timeline ?
If it is… What could be introduced as a corrective measure (in the preferences) with-in n-Track or any other multi-track Editor that could compensate for all the different hardware that these computer set-ups could possibly have ? OR… What in your opinion would be necessary to FIX this LOOPING Issue. ?
Bill…
p.s. EDIT…
This is not how I wrote the reply to this thread at 4:45 am this morning… BUT… it’s close…
[EDIT 2] This is not the thread I wanted to post this response to… However, all this thought has TO-DO with how we perceive n-Track to preform/behave on all our setups… Sorry Gents… BUT. You all know the direction that this reply is taking us…
? 
..for my latest DAW I bought a real IBM with an Intel P4 and a real intel chipset...XP pro, service pack 3..and then the problems began in earnest. My old machine was an AMD athlon on an ECS Motherboard and Win2K pro...I ran N 3.3 and my Delta 66 for 3+ years without a single crash or issue... I bought some high falutin' plugs and got caught in the plugin/latency/automation bug..got the new machine, upgraded to V6 and the dance began..I haven't cut a single keeper track (with N) since July..sigh...