I would like to see easier midi creating and editing. Especially for drum tracking.
Yaz 
Quote: (bax3 @ Apr. 18 2008, 3:17 PM)
I'd suggest emailing Flavio with your idea.
I sent an email to Flavio with the suggested envelope editing improvements and he replied:
"Thanks for the detailed suggestions. I'll add some if not all of them in version 6.0."
That is great news. I look forward to it.
Here is another feature request. Clipped peak restoration. More and more DAWs are including this feature which I recall was available in the shareware Cool Edit when it was affordable (pre-Adobe)and still is included in Audition. Sometimes an otherwise excellent take is marred by some clipped peaks. This is particularly possible for those that record using the Audigy 2 soundcards at 16/44 where peaks get clipped at 95% and never flash the peak meter. Also, from time-to-time a ripped CD file is found to contain clipped peaks. I have read that the newer clipped peak restorers do a credible job of restoring the peak using algorithms to interpolate the missing part.
Another feature that Flavio has said would be added to Ntrack 6 would be the ability to access upto 6 additional program besides the assigned External Editor - sort of a “Send to” menu. This is great news for those of us who have programs that contain features that we want to access without leaving Ntrack. If we have more than one editor, or special purpose software with features only available in that other software, we don’t have to open and close Ntrack to use them. Personally, I think this will answer many of the requests we are making for additions to Ntrack without Flavio having to “reinvent the wheel” -writing quality plug-ins I feel sure must present it’s own set of problems The ability of Ntrack to use both DirectX and VST has already been a strong feature. The abality to move easily between our favorite audio programs opens up many options.
N track has a lot going for it as I am using two different sound cards together. I got them to work ,eventually, by using wdm drivers.
Reaper doesn’t do it.
Tracktion seems to after a fashion, has problems with asio at times and doen’t support wdm.
The others, I don’t know and couldn’t afford them.
I would like to see in the next release.
1: Better refresh rate on the controls, they smear.
2: Better ability to see less stuff on screen (see Tracktion)
3: Some of the controls are hard to see.
I will try and think of more later 
- When using the EQ settings, those 3 little buttons, I notice I can view the EQ frequency view. The problem is, setting the 3 dots to follow the green bar over the red bouncing indicators is somewhat frustrating as the lines always move. So when I stop the track the lines disappear as the EQ frequency view is in real time. What would be nice is to have feature that takes a snap shot of the EQ frequency view for viewing later or even better a function to allow the average over time and time being set by the user (like a section group select). This would help me set the EQ to average IE: line up the green line over the red peaks.
2)Also I like to see a new option: A setting to turn on or off a function to allow each new track to be given a different color instead of having to change the color manually. Auto rainbow. (Gee I like the sound of that)
3)High detail 3D buttons like the sliders, more brushed chrome and black accents and EQ buttons a little bigger. What would be cool is a zoom feature. For example when the mouse enters the the area of the 3 EQ buttons the buttons automatically zoom just a little and then while the mouse is over the EQ you can then make fine adjustments (because the buttons are now a little bigger and easy to use). When the mouse moves away from the EQ “Zone” it zooms back to small. Isn’t that a great idea? This could be applied to other functions who’s buttons appear small and difficult to adjust such as balance, Aux slider and it’s balance ect ect… I’m not talking about a large zoom just a little to make adjustments finer and more precise. The zoom feature when used should show nice detailed 3D buttons or sliders.
I don’t ask much do I?
PACO
My section 3 request for zoom, I just wanted to add that the 3 EQ buttons should zoom together all at once and not individually. May make things easier. I was going to just edit my post but it says I can’t even though I’m logged in. Not a biggie anyways. Thanks for listening.
PACO
in n-Track press ctrl P - appearance - check ‘use different color for each track.’
(You probably knew that…)
It would be nice to have a ‘auto rainbow’ for imported projects though.
No I didn’t LOL!!, so thanks for telling me.
PACO
To get different colors for each track, I set the Preferrence>Options to “Different colors for each track,” Works for me anyway.
Got another feature request;
QUICKER START TIME! Please?
Holy cow… I have been noodling around a bit with n to see if I want to try out the Song Contest or not… it takes for blinkin’ ever for this beast to start up. What is it doing? Brand X starts in a few seconds and is rip rearin’ and ready to go…
I haven’t timed it but I’d guess a fresh start of n-Track takes close to minute before I see the GUI fired up and ready to run. WAAAAAYYY too long mi amigo’s…
D
PS All my other DAW/audio softies start up much, much faster than n-Track. What’s going on Flavio? I don’t think it is system specific as it does the same on my laptop and my sons machine as well.
PPS One (or many) might argue “What’s the big deal? So n-Track takes a bit longer to fire up?” Well, if it did not crackle, pop, fart and crash, it would be worth the wait… Please… no flames. I’m frustrated enough as it is… sorry.
Quote: (Diogenes @ Apr. 28 2008, 10:52 PM)
I haven't timed it but I'd guess a fresh start of n-Track takes close to minute before I see the GUI fired up and ready to run. WAAAAAYYY too long mi amigo's...
On my P4 Dual Core 2.8GHz, a fresh start of n-Track takes 10 seconds. If it had been previously opened, it takes 3 seconds.
Quote: (vivona @ Apr. 28 2008, 10:52 PM)
Quote: (Diogenes @ Apr. 28 2008, 10:52 PM)
I haven't timed it but I'd guess a fresh start of n-Track takes close to minute before I see the GUI fired up and ready to run. WAAAAAYYY too long mi amigo's...
On my P4 Dual Core 2.8GHz, a fresh start of n-Track takes 10 seconds. If it had been previously opened, it takes 3 seconds.
Yeah... if part of it has been cached it starts up quicker. I'm just curious as to why the fresh start takes soooo LONG. A minute may be an exaggeration but still... Sam 9SE and Reap are started up and ready to run almost as soon as my finger comes off the mouse button.
With n, there have been a few times where I thought I hadn't double-clicked properly and ended up with two instances running!
Certainly not the end of the world but annoying none the less.
D
Quote: (Diogenes @ Apr. 29 2008, 1:17 PM)
Quote: (vivona @ Apr. 28 2008, 10:52 PM)
Quote: (Diogenes @ Apr. 28 2008, 10:52 PM)
I haven't timed it but I'd guess a fresh start of n-Track takes close to minute before I see the GUI fired up and ready to run. WAAAAAYYY too long mi amigo's...
On my P4 Dual Core 2.8GHz, a fresh start of n-Track takes 10 seconds. If it had been previously opened, it takes 3 seconds.
Yeah... if part of it has been cached it starts up quicker. I'm just curious as to why the fresh start takes soooo LONG. A minute may be an exaggeration but still... Sam 9SE and Reap are started up and ready to run almost as soon as my finger comes off the mouse button.
With n, there have been a few times where I thought I hadn't double-clicked properly and ended up with two instances running!
Certainly not the end of the world but annoying none the less.
D
Yep, it can be a bit slow (although I don't think I've every come anywhere near to a minute, or even 30 seconds).
I don't know for sure but I'm wondering if the length of time to startup depends on the number and type of plugins that you have.
Also, and again I'm guessing, I wonder if the .NET framework takes a while to get started up on first run. On subsequent runs it's already up and running so things seem better.
Quote:
Also, and again I'm guessing, I wonder if the .NET framework takes a while to get started up on first run. On subsequent runs it's already up and running so things seem better.
I think you have it Mark. See my somewhat "dubious" theory I posted in "n-Tracks Future" thread.
D
Another request:
Fix PDC so it works in all possible scenarios. I know this is a pain but it IS doable. The only time it should fail is when a plugin fails to report it’s latency. Even then, it would be cool to have a per plugin, per track option to manually enter a value for PDC.
D
I know PMS stands for “pre murder syndrome” but what does PDC stand for??
Plugin Delay Compensation
A DAW needs to automatically compensate for plugin processing delays to keep everything in synch upon Playback/Recording.
D
Another request please… Track Templates and Project Templates. Very handy and very cool.
Maybe give that a go for V6?
D
From another thread discussing pitch and/or time shifting…
Can V6 include a better algorithm for pitch/time shifting? Elastique Pro V2 does an amazing job of this.
Elastique Pro LINK
Thanks,
D
Yeah, Elastique is indeed the bomb diggity.