Since v6 has been confirmed, what would you like to see added, removed or improved?
I’ll start with my own little list:
1) Add the ability to work with DSD audio (1 bit 2.8mHz).
2) Make sure backward compatibility is 100%
3) A cleaned-up UI (internally & externally). This is one I consider essential. Nt is too erratic even now and I think Flavio is finally aware of the importance of this.
4) Multi-monitor-friendly features.
Thats about it for me.
no cents
The ability to send group and aux signals to various outputs in the same manner as a standard mixing console
- ie 1. track 1 can be assigned to group 1 and 2, etc. and each group can be
sent to soundcard output 5 and 6 and/or main output.
2. aux 1 can be sent to soundcard output 1, aux 2 to output 2, etc.
Paul
- STABILITY
2) More efficient audio engine
3) Sample accurate renders in every case (Freeze, Mixdown etc…)
4) More editing features; Tab to transient, strip silence with adjustable threshold, hysteresis etc…
5) Take management with lanes
6) More flexible routing
7) STABILITY
I’ll think of some more…
D
This might seem like nit picking but…
I would like the “record button” and bar (with the play button and all on it) to stay put.
The other day I lost the thing, I don’t even know how or why but it “disappeared”.
I was moving all kinds of things around trying to find the darn thing, is it under here? how about over in this corner?
Who knows?
I had to restart Ntrack and create a new file and it returned to its rightful place.
and what’s all this talk about stability?
I have found by reading many software reviews and forums that in most cases it was people computers that were causing instability with programs, bad chipsets for audio (especially Dell), soundcard and interface drivers etc etc. (of course that could just the software people saying that to cover their own butts) ! lol 
I just made sure I didn’t by any of those chipsets or audio interfaces that had the driver issues…and N works fine for me!
keep shinin’
jerm 
Hi vanclan:
Thanks for your post regarding the addition to n-Track v6, you talk about.
I’ve been requesting the addition of future builds to be able to render groups…
Sense my lobbying for this addition isn’t getting any attention…
I believe I’m not able to make my request explicit or detailed enough for the idea to make sense… OR… My communication skills are not at a level to get my WANT for the idea across…
Let me put it another way…
If you can render a track-or-tracks
Why can’t you have the ability to render a Group-or-Groups? …
Other n-Track members reply to this request by saying
YES You Can…
YES…
IN A WAY…
YOU CAN DO THAT…
BUT…
without seeing groups in the Render Box…
it’s not the same…
BUT… I don’t see that ability listed in the Render Box where the tracks are listed and/or be hi-lited when you make the command to render tracks…
I want to see The Groups listed in that same box…
I’m not making this request to be Belly-Acheing or Crying the Blues…
IF you can do this audio rendering in the Analogue World, then, you should be able to do this in the Digital World…
Virtual THIS
and Virtual THAT
is ALL O.K.
BUT Lets give Virtual Groups it’s place in the Digital World…
as well…
That’s as simple as I can say it…
If the GROUPS appeared in the Render Box…
I’d be quite happy…
Hi jeremysdemo:
I agree with your post…
100%…
Somehow-or-other…
if you use your computer for more and more things and add utilities and applications along with audio
you you end up sharing more .dll files…
As this happens your machine becomes corrupted and slows down and makes your machine unstable along with it’s ability to process stable audio almost impossible…
That’s what I think…
Bill…
Quote:
and what's all this talk about stability?
I have found by reading many software reviews and forums that in most cases it was people computers that were causing instability with programs, bad chipsets for audio (especially Dell), soundcard and interface drivers etc etc.
OK Jerm... you win. I'm making all this up. n-Track did not work fabulously for me for years and then go to crap mid V4. I dreamed it all. I started looking at other DAW's to get stuff done just so I could hang around here and piss and moan.
Quote:
I agree with your post... 100%.. Somehow-or-other.. if you use your computer for more and more things and add utilities and applications along with audio you you end up sharing more .dll files.. As this happens your machine becomes corrupted and slows down and makes your machine unstable along with it's ability to process stable audio almost impossible..
Guys this is on an audio only PC that is ROCK SOLID with all my other software. Again, n worked great until mid V4. As far as hardware goes, I have not added nor changed anything. You are not helping yourselves or anybody else by suffering through work-arounds and un-installs/re-installs to get things working after some spurious, flaky "episode" where n pukes on you... and it has, many times, because I have read your posts about it over the years. Come on, be realistic. Other softwares work well, n-Track once worked well, let's help Flavio get n-Track back in the game by being honest about n's shortcomings. Is that not what we want? Is that not what Flavio would want? I think so... If you can tell me I am wrong about that, hey I can always shut up and go away... But I would LIKE to hang around to see n-Track returned to the V3.3 glory days.
With all respect,
D
You are right D. I for one have no problem with you posting the Reaper link to anyone who is having problems with N - I would do the same to help out another recording junky.
Quote:
OK Jerm… you win. I’m making all this up. n-Track did not work fabulously for me for years and then go to crap mid V4. I dreamed it all. I started looking at other DAW’s to get stuff done just so I could hang around here and piss and moan.
I like your sarcasm as much as you cynicism…
I’m confident Flavio knows what he’s doin’.
Quote:
I'm confident Flavio knows what he's doin'.
Absolutely he does! For Pete's sake man, Flavio and Justin even implemented EDL import and export so n-Track users and Reaper users could move projects around easily. I don't know that they are on Pal'sy-wal'sy terms but neither man is stupid. Just saying "Oh I can get n-Track to work by re-installing it every time I boot my PC." is NUTS! Flavio needs to no about such weirdness so can fix it. Don't put up with it. For the developers sake as well as the users.
D
You’re preachin’ to the choir here. (Me anyway.)
My problem currently, and I’ll bet with all Vista users, is when I do get a crash and a dmp file starts to being written - Vista shuts down the system before the file can be completed and sent.
Just to not get TOOOooo off topic here.
I would like to see an opacity option for track part overlays. Being very lazy I tend to need to clone parts and cut and paste fixes. It would be nice to see the track behind the patch.
Gads… I wish I could go back and edit spelling errors and typos… I HATE when I look at posts and spot stupid mistakes and can’t correct them.
D
Hi Poppa Willis:
I think I have a workaround for the VISTA Operating System…
I don’t use that system but if I did I’d be looking for a way to send off that .dmp file to Flavio…
My thinking is…
the .dmp file is already written…
But VISTA closes upon sending the file…
If that happens to be the case…
I’d then go looking for this .dmp file after VISTA Re-boots…
It’s likely to be found in the users local file…
OR whereever… it is…
Then I’d send the file off to Flavio Manually in an E-Mail to him…
At least the .dmp file would end up on his Desk or E-Mail or…
to his attention…
and not be waisting space or lost on your C-Drive somewhere…
It’s something to think about…
Bill…
I’ve looked Bill - Evry vista dmp is there - Vista closes during the colorful slick progress window they have.
Nice to have a purty window to look at while your system dumps though. I’ll give 'em that. All my DAW probs to date with Vista have proved to be my US 122 Tascam driver - they are still a work in progress from what I get from support. I have to remember to unplug my unit before I shutdown or Vista will freak on restart.
Hi Again Poppa Willis:
When you say vista dmp’s,
I presumme they are the ones that VISTA creates when VISTA closes…
Are those dmp’s the ones that should or get sent to Microsoft?
Having said that then somewhere in there there should be the series of .dmp files that should get sent off to Flavio…
You may even have some other .dmp files that get created as your Operating System closes or gets created on all those “Close Exceptions”
Look At Me…
Do you think I know…
?
I don’t think that the Tascam Audio Hardware will create any ,dmp files…
BUT…
Tascam should be made aware that the drivers you use for that hardware is creating you “Big Time” issues with your VISTA Operating System…
I’m being Nosey here…
How did you discover that by un-plugging your Audio Hardware that it was the workaround for your saetup?
It would be so nice for you and your setup if Tascam would create a Driver File for their Audio Hardware that would fix this issue you have on your setup from some mail you send them discribing your issue…
You see…
I’m re-building this P-111 machine I have here…
I’ve got 17 days left before I have to register/validate the build I have with Microsoft…
I haven’t looked but I would be safe in saying that I have created a hundred .dmp XP files…
I should allow them to go off to Microsoft instead of “NOT ALLOWING” them to go …
I know…
that by creating these .dmp files as I load this machine that I have to somehow resolve these conflicting issues as I add software to this machine…
Now…
I could take this machine to someone and tell them what this machine should work like…
but I know I could never afford the hours of labour it would take to have that person make it work for me…
I think I would estimate that I may be about 20 - 25% of the way along with this build…
It’s so easy to miss some little issue as the software is installed and configuered…
only to have that issue surface somewhere down the line…
with some other piece of software…
The computers I have is causing me “Big Time” “Mental Abuse”
It so happens that I know several Machine Loaders…
I could never figure out why they acted-and-behaved the way they do…
way back when…
I now believe that I am beginning to act-and-behave exactly the way they do…
AND… it’s not a good atribute to have…
Well…
Bill…
please stay on topic!
lets see your feature requests. save the other stuff for other threads…next…
feature request:
no cents
Per Item FX like Samplitude, Reaper and a few others have. It’s incredibly cool.
D
For version 6, my requests are:
1. Get the volume evolution envelope lines working correctly and solidly. They used to be real touchy and finally got fixed near the end of version 5’s run. I am using build 2287 and they work pretty good, but I recall problems with some of the higher builds that I don’t think got fixed in 2313. I know the tooltips problem was fixed in 2313, but I recall that the nodes were touchy again. I use volume evolution envelopes in Sony Vegas and they are much easier to handle. They would be a good model to look at (probably any Sony audio or video product uses the same evolution envelope system).
2. Fix the problem that was present in 2312 and 2313 where program-generated auto-named filenames for tracks had a space added before the underline.
3. Fix the scrubbing problem where the play button pops out and playback stops during scrubbing if the scrubbing cursor hovers near the vert ical playback indicator. As expected, playback should slow to zero when the scrubbing cursor is over the playback indicator, but as soon as you drag to the right or left of the playback indicator, playback should resume. It doesn’t. You have to click the playback button to get playback going again. Once again, I would look at the Sony products for a good example of scrubbing. In Sony Vegas, you can grab the playback cursor and scrub back and forth just like you were turning the reels of a tape machine. This is a lot better than than the lag that comes from scrubbing by changing playback speed and direction, even if it didn’t stop when you passed by zero speed. So a real scrubbing feature would be nice.
4. Move the playback speed adjuster higher in the toolbar area and add a delay before mousing over it becomes active to reduce the possibility of accidentally changing playback speed while selecting regions on the timeline just below the current position of the playback speed adjuster. This is what caused the problem where we were complaining of tracks being out of time with other tracks. We had accidentally changed playback speed and when you rendered tracks, they were being rendered at a different speed than 1.0. If this mixdown was then A warning during the mixdown selection that playback is other than 1.0 would also catch this problem, such as an error message "Playback is at .98, do you intend to mixdown at this rate, click yes if you do, or reset to 1.0 if you want the mixdown in normal speed."
Other than these annoyances, I would have to say that the later builds of version 5 (at least up to my 2287) were pretty nice. I really liked the ease of cutting and dragging parts of the waveform back and forth in time to correct vocal track timing errors. I could also record some punch-ins and copy and drag the pieces I wanted right over the original vocal track to fix errors. These are features to keep.
Not to nitpick… but 1, 2 and 3 are BUG FIXES. Maybe we should have a separate thread for BUG FIX wishes?
Hopefully Flavio will take care of 'em.
D
I agree that item 2 is a bug fix. But what I am asking for in 1 and 3 are enhancements beyond just fixing the current implementation. Better evolution functionality and audio scrubbing goes beyond what is currently implemented. All of the items on my list, including item 4, are a combination of bug fixes and/or enhancements I had asked for last November and the bug fix portions have not received attention since the final release of version 5, build 2313. With version 6 being somewhat of a redesign (as I understand it) I wanted these features to be better implemented, not just fixed to work the way they currently should.
It is probably just as fine to let this thread be a combination of new features and bug fixes so nothing gets lost by being in two different places, especially those items that are a combination of bug fix and enhancement.
Quote: (Diogenes @ Mar. 21 2008, 9:38 AM)
Quote:
and what's all this talk about stability?
I have found by reading many software reviews and forums that in most cases it was people computers that were causing instability with programs, bad chipsets for audio (especially Dell), soundcard and interface drivers etc etc.
OK Jerm... you win. I'm making all this up. n-Track did not work fabulously for me for years and then go to crap mid V4. I dreamed it all. I started looking at other DAW's to get stuff done just so I could hang around here and piss and moan.
I'm sorry to hear that D,
I did not mean to say implied or otherwise that people whom are having problems are any less than truthful.
As I said (of course that could just the software people saying that to cover their own butts)....about the bad chipsets and drivers in the Dells....
I couldn't help but notice you had problems with "registering" Ntrack after every reboot.
Which begs the question, why reboot?
I had the same problem which occurred a few times with the M-audio Firewire interface.
After reading several articles on how constant rebooting effects the components in the computer and how much energy it took I just decided to leave it run...it's running right now....maybe I'll go up there and work tonight...maybe I won't...but if I do....I know it will be running the same as it was when I left with no boot up errors to read, un-installed or malfunctioning devices, drivers, registrations....etc etc.
My only worry is a power out presently I only have 15 min.- a half hour of backup power...so anything over that would be troublesome.
I don't doubt people have problems with this software and their computers, but I can't report what I don't and haven't had.
I used Ntrack 2.3 for 7 years on a IBM in the late 90's, and 2.3 for the last 5 years on a re-furbished Gateway 1.2G with 98SE.
Then the latest build for the last two months on an Asus 2.2G board with XP pro.
I would like to add I am only using 16 bit.
I don't know how the 24 bit runs on XP or Vista, but do appreciate the many people reporting bugs in the event that one day I may upgrade.
That is how I have always been though, and it has served me well, if it ain't broke don't fix it, I find something that works for me and I keep it in that state.
I am a cautious person, just upgraded to XP this year, and that is only because many of the VST's I like only work in XP and the Interface I bought only works in XP or better when most if not all of my friends are already on Vista and telling me of their woes....
keep shinin'
jerm