Loudness Meter; assignable source

All feature requests and suggestions for upcoming releases of Nuendo 7 can be posted here.
Post Reply
User avatar
MattiasNYC
Grand Senior Member
Posts: 3255
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Loudness Meter; assignable source

Post by MattiasNYC » Tue Mar 15, 2016 4:20 pm

I would like the Loudness Meter/Track analysis to get audio from a source that is assignable.

The way it currently works it takes signal from the "main mix" output only. However, there are certainly occasions where it seems more convenient to be able to tap a signal from a different point in the signal path instead.


This is a request that goes back two years (old request is here.

For example:

In some of my templates I have as the "main mix" LCR/LFE. The reason is that I like to listen to center-only when doing dialog editing. It also allows me to use my smaller 5-inch speakers crossed over to a subwoofer when I feel like it. The routing uses groups for each 'food group'; dialog, narration, sfx, music etc. They all get routed according to delivery specs on a per-network basis, and I use the outputs for that purpose (they don't all get connected to a physical output). So, I might have:

- Main STEREO mix
- Mix Minus STEREO
- DME STEREO
- Main MONO mix

I would like to assign the loudness measuring "function" to any of those sources. In addition to those outputs I'd like to be able to pick up the output of a track, that way I can do a faster than realtime analysis of any of my already 'printed' mixes whenever I want. There are occasions where this is desirable, for example if a client comes back and claims the network said the mix didn't conform to spec. A quick analysis would yield the info needed.

This also ends up directly relating to two different topics, and addressing either of these would provide an arguably reasonable alternative (especially #2):

1. "Leave off-line plugin window open AND continue DAW control". I added an explanation there.

2. "Loudness measurement: offline & batch"(here)
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

philusion
New Member
Posts: 7
Joined: Mon Aug 18, 2014 11:59 am
Contact:

Re: Loudness Meter; assignable source

Post by philusion » Mon Apr 11, 2016 12:20 pm

You can always download the free SLM128 plugin by Steinberg and put that on individual tracks (I'm actually so used to it that I tend to use it instead of the new built in one!)

User avatar
Xeneize99
New Member
Posts: 19
Joined: Mon Aug 05, 2013 3:59 am
Contact:

Re: Loudness Meter; assignable source

Post by Xeneize99 » Wed Oct 26, 2016 2:30 am

+1 :D

ErikG
Member
Posts: 439
Joined: Fri Dec 17, 2010 8:43 am
Contact:

Re: Loudness Meter; assignable source

Post by ErikG » Sat Nov 05, 2016 9:04 am

Yep, and while they are re-working it, perhaps make the loudness track truly usable so it can store multiple ranges of data (example multiple episodes or versions in on timeline where loudness data is kept for each) and also to be a less to recalculate loudness data based on loudness track readings rather than re-measuring full content over and over and over....
I am aware the readings my not get perfect but should get close enough if they store all the data properly. Data and audio measurements are not quite the same thing but it would still be useful.
Measuring one our shows multiple times can get really boring really quickly.
Filmlance
11xNuendo, 5xPT
Dubstage with 2k Christie projection
8xMedia Composer, VFX, online, grading and more

User avatar
MattiasNYC
Grand Senior Member
Posts: 3255
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Re: Loudness Meter; assignable source

Post by MattiasNYC » Mon Nov 07, 2016 8:53 pm

ErikG wrote:to recalculate loudness data based on loudness track readings rather than re-measuring full content over and over and over....
Excellent suggestion Erik.

I could see situations where I've recorded onto tracks and need to punch in / consolidate (bounce) files to fix something. It'd maybe be a solution for it to automatically then just take the data up until maybe 10-20 seconds on either side of where you just recorded, and then just re-measure with those "handles" and then regenerate the final data.

Very cool suggestion of yours..... It's almost as if you do this stuff for a living! :D
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

User avatar
lemix
Member
Posts: 338
Joined: Fri Dec 28, 2012 2:01 pm
Contact:

Re: Loudness Meter; assignable source

Post by lemix » Tue Nov 08, 2016 6:07 am

Absolutely !
The loudness data stays with the project and updates itself as you describe it.
That would be great :!:
cheers,
Andrew

W7 pro 64_i7 3930K_16GB_ Nuendo 6.5.4-7.1.30 & PT 12.4------Mac Mini OSX Lion_PT 10.xx-----WXP, Wavelab, Plextor Premium, Hofa DDP
Allen&Heath GS R-24M_ full rack of vintage analog boxes _UAD2_Nugen_iZotope_Melda_Waves_Plugin Alliance_McDSP
1.0_2.0 and 5.1 monitoring

Post Reply

Return to “Feature Requests and Suggestions”

Who is online

Users browsing this forum: No registered users and 1 guest