Latest build   2455

Normalize Works Fine.

I downloaded b 2455 this morning…



The normalize issue works fine again…
At leat the way I use the feature…
That is…
setting the left-or-right-or both level adjust…
However, the level adjust field/window doesn’t delete/clear the window of the previous level that was entered…
OR to the default/clear
e.g.
If the normalize level entered into the field was a -2.0db change…
the next time that the normalize feature is called up

that -2.0db figure is still in the “Field” window…

That’s O.K…

The feature now works…


Thank you…
Flavio…



I forgot to check the Loop Icon on the toolbar…
I’ll look into that later…




Bill…

Hi Bill, I think the normalize level window has always been that way with the existing project open, I believe it only resets to 0db after closing and re-opening the program.

I’ll grab 2455 and see what’s up.

Hi Yaz:

Thanks for your reply and a check on another setup…
to see how it behaves…
It’s about the only reason I use the normalization…
Just to reset levels on a track…
or…
whatever…
Sometimes the full track…
sometimes just a section of a track…
as opposed to setting levels with drawing volume envolopes… or whatever…



You know…
it’s not what or how you use all this editing stuff…
It’s what you get used to the stuff you use…



I can tell you one thing…
I gotta get a stable Operating System running… that I feel comfortable with…




n-Track is looking So
Nice…
AND…
it operates flawlessly…
at least how I intend to use n-Track…
It’s the damn Operating System…
I just don’t feel like it’s running for me to depend on it…
Why is that ????


I have so much wireing and setup ahead of me in the studio…
I have maintenance work to do on the Consel/Desk…
AND…
the weather is not helping all this …
either…




Bill…

I like that wall of guitars you have…

Hi Bill I kind of like that. Especially if working on a rough or botched area. If you rescan and cancel what appears then?

Working with 2455 was pretty nice after the last few builds. :agree: So far all’s good for me.

I got lucky…
The build I downloaded and installed before 2455 was 2451…
I know when Flavio is working away he’ll update a FIX build if anyone reports a glitch…
However, my XP build will not restore…
(I don’t know why)…

SO…
I’m stuck…
BUT…
I could un-install n-Track and then re-install…
BUT
there are issues to doing that…


I’m just gonna sit in the corner and pout…
sigh…
and watch all you guys play with n-Track…






Bill…

Every one seems to like xp, but to me after a yr with vista, xp seems lazy and out of touch. But I have xp on my DAW.

Why not just remove n, via your computers control panel.
Then clean your machine a little.
Run a reg’mechanic and reinstall n55 to the default settings?
When I did a normalization with 51 it went like this…scan slection, normalize to -19.00 to remove some guitar bumping noise, and press ok to see nTrack take that section to about +200… 55 over 51 anyday goodman.

Bill, I’m glad the normalize button is working for you, but last night I wanted to give a harmonica track a little more punch, and after opening the normalize window, setting the level I wanted, and telling it to go - the wav file disappeared from the track view, and double-clicking in the empty space brought up a ‘file may be corrupted’ warning window. Happily, 'undo normalize` brought it back, and I was able to use my external editor to get the sound I wanted, but I should have been able to do it in n, as I have for years…

Anyway, I will report it to Flavio, and hopefully it will be corrected in the next build…

'til later;
Tony W

Hi wynot:

I never encountered an issue like that before…
However, the undo command works…
and that’s good…



I’d like to see Flavio expand/address some more detail into the Normalize feature…


As I write this reply…
my Grey Matter has gone into a BiG pAiN… :) :D :whistle:



For example…
Open the normalize feature…
Scan for the highest peak…

That’s what happens now…
That’s good…
If the track has the headroom you can BUMP it up till the headroom is used up…
If you choose to reduce the level…
you enter the Level Change in the box and render/normalize the track…
That’s GREAT…
If you choose to UP-the-Level
OR

Down-the-evel
So-Be-It…



What I’d like to see added to the normalize feature is…



Scan the track for the peak(s)…
reduce thew peak(s) without touching the Average Level Content of the Track…



I KnOw…

Someone is gonna say…
use a Compressor/Limitor…



NO…
NO…
I don’t want to alter the dynamics of the track…
I Just Want To Reduce The Peak Level Content of the TRack…
I’ve already set/adjusted the dynamics of that Track or Group…




The Normalize Scan will-and-should identify all the positions of the peaks above a presaet level and reduce just those peaks to a preset level… up-to and including any number of peaks…
Lets say there might be 100+ peaks in the track…
above a preset level…




Who Knows…
Maybe, there’s a lot of Coding to produce a normalize update like that…
However, I could certenly use a Normalize feature like that…
A good discussion along those lines might produce a workable Normalize UPDATE…



I’d support that…
BIG TIME…



I can remember in the past as builds were being FIXED-and-Update as a version was being built issues would sometimes create a .dmp file OR even if they didn’t I would try several times to identify and observe if an issue would repeate itself… If it did, I would send Flavio a .jpeg link of what would appear in a printscreen… and try to describe as best I could how to repeate the issue…
If I discovered a workaround for it I would send him what I thought might be the FIX…
Many times a new build would get posted and all got FIXED…



As I use v6.0.3
the only issue I see now in the graphics is the LOOPING Icon… It would be nice now to get the LOOPING Icon on the Toolbar FIXED…
It could be he has bigger fish to fry…


Who knows… ????






Bill…

Quote: (wynot @ Feb. 17 2009, 9:03 AM)

the wav file disappeared from the track view, and double-clicking in the empty space brought up a 'file may be corrupted' warning window.

I'm finding wav files being removed when removing parts, happening in all recent builds.
And not related to normalization.
I've not had enough work in b55 or 56 to know if that prob has been corrected.
It doesn't happen all the time.
It's possible that my old way of writing with n isn't advantageous now with lanes.

I didn't have a corruption notice with those errors.

I’m downloading b2457 as I reply here.

I have less time to play with things I’d rather do, these days…
However, I’m bringing in a little more spending money…
I hope I get to use on things I’d like to blow money, on…
instead of dumping it in the heating fuel tank…
It (the weather) can only better over here…


I only tried the normalize once with build 2455…
It seemed to work perfectly, here…
for the way I use it…



I’ll spend more time with the thing this time around…






Bill…

Bill, according to the ‘what’s new’ for the latest build, the disappearing wav file problem was with 24 bit and 32 bit float files. If you were recording at 16 bits, you would not have seen a problem…

'til later;
wynot

You’re correct wynot…
They were 41.1kbs. 16 bit files that I had on the timeline…

bill…