HeDa Track Inspector VIP v2.3.13 (2024-03-20)

[Robert Randolph]

Originally Posted by heda

Hi Robert,
go to settings and try to activate the option "Reset EBUR128 using new function". This doesn't generate undo resetting the meter.

This works much better btw, thank you.

I turned it on and just totally forgot about it until now.

[skippertag]

Big Problem here!

I tweaked the AutoGroup file to integrate some plugin names but now when I open the script I get

?:-1: attempt to get length of a nil value

Surprisingly the other two scripts (floating....) are still working ..

How can I get back ?

Thanks
Frank

[heda]

Originally Posted by skippertag

How can I get back ?

Thanks
Frank

Try uninstalling it and installing it again from the manager.
Other instances may work because they don't have auto fx group enabled. In any case I'm going to fix this error you are reporting. Thanks.

You reminded me that I need to update one thing about this FX auto groups file. I should make it easier to edit the auto groups, instead of having to tweak a file, but since I didn't receive feedback about that feature, I wasn't concerned about it.

[heda]

* v1.4pre29 (2017-11-13)
# Only show used FX groups
# small fix in fx names

"Only show used FX groups". The buttons to bypass by groups, now show only the groups that are being used, so now you can use non consecutive numbers.


I was thinking another mode that would let you name the groups, instead of using numbers.
What do you think? It would be less compact but maybe more useful.
Or maybe the name would only show in a tooltip when the mouse is over the number group button.

[skippertag]

Originally Posted by heda

"Only show used FX groups". The buttons to bypass by groups, now show only the groups that are being used, so now you can use non consecutive numbers.


I was thinking another mode that would let you name the groups, instead of using numbers.
What do you think? It would be less compact but maybe more useful.
Or maybe the name would only show in a tooltip when the mouse is over the number group button.

How about letting the user decide?

[skippertag]

Originally Posted by heda

Try uninstalling it and installing it again from the manager.
Other instances may work because they don't have auto fx group enabled. In any case I'm going to fix this error you are reporting. Thanks.

You reminded me that I need to update one thing about this FX auto groups file. I should make it easier to edit the auto groups, instead of having to tweak a file, but since I didn't receive feedback about that feature, I wasn't concerned about it.

I had to uninstall it completely including the settings folder..but now it's working again.

Many thanks for your fast help!

[skippertag]

Heda, as I'm testing..

Did you change the grouping feature already?

I'm using a Track Template that I love so much very often now as it is just incredible helpful (at least to me :-)

https://stash.reaper.fm/v/31454/INTE...RTrackTemplate

The thing is - the folder track has got 64 Channels and to make everything work 42 plugins and when I have Track Inspector open the FXChain is view is flushing away my meters that far that I can't get em back ;-)

edit: I found the button to fix the meters on top..

Is it possible to scroll through the FX Chain's list?

[heda]

Originally Posted by skippertag

Is it possible to scroll through the FX Chain's list?

that stash file... says "The requested file does not exist."

to scroll the panels, drag up and down with the middle mouse button anywhere except over meters panel

[skippertag]

Originally Posted by heda

that stash file... says "The requested file does not exist."

to scroll the panels, drag up and down with the middle mouse button anywhere except over meters panel

AAaaahhh yes...thank you!

Try this one
https://stash.reaper.fm/v/31454/INTE...RTrackTemplate

when you use it, just put the track onto the folder track...and as the chain is working best at -6db Peak use this script on the item firstly
Script: nofish_Normalize selected items active take to X dBFS true peak.lua

And then leave everything doing it's magic and when you want to tweak the 4 bands just use the blue faders...

I love that and I think I don't need to buy Elevate-Bundle ;-)

[heda]

Originally Posted by skippertag

AAaaahhh yes...thank you!

Try this one
https://stash.reaper.fm/v/31454/INTE...RTrackTemplate

that works. I will need more time to understand what is it Thanks!

[heda]

* v1.4pre30 (2017-11-13)
+ Gain reduction meter with GainReduction_dB API (needs REAPER v5.65pre12+)
# TP MAX suffix units changed to dBFS

another update today...
you will need latest pre-release 5.65pre12 from today
to display gain reduction meter from ReaComp
Before it was only supported in General Dynamics. Now it is also on ReaComp. (only from the latest ReaComp instance of the chain if there are more than one)

[heda]

oh it seems I was a bit confused and I thought it was only ReaComp that is supported... but it can work also on other plugins so now I have updated Track Inspector and it should work with all VST plugins that report gain reduction, not just ReaComp. But I don't have any plugin to test it.

[G-Sun]

Originally Posted by heda

* v1.4pre30 (2017-11-13)
+ Gain reduction meter with GainReduction_dB API (needs REAPER v5.65pre12+)

Looking very forward to see devellopment here
(and what plugins that supports this)

A natural way to go is allowing more than one GR read.
It could be stacked (one meter) or multimeter.

[skippertag]

Originally Posted by heda

another update today...
you will need latest pre-release 5.65pre12 from today
to display gain reduction meter from ReaComp
Before it was only supported in General Dynamics. Now it is also on ReaComp. (only from the latest ReaComp instance of the chain if there are more than one)

YIEEHAAA!! Thanks, man!

[vanhaze]

Originally Posted by heda

oh it seems I was a bit confused and I thought it was only ReaComp that is supported... but it can work also on other plugins so now I have updated Track Inspector and it should work with all VST plugins that report gain reduction, not just ReaComp. But I don't have any plugin to test it.

Awesome heda, thanks so much !!

[Sumalc]

Originally Posted by heda

oh it seems I was a bit confused and I thought it was only ReaComp that is supported... but it can work also on other plugins so now I have updated Track Inspector and it should work with all VST plugins that report gain reduction, not just ReaComp. But I don't have any plugin to test it.

Thank you Heda for this add-on, works fine with Reacomp but not with PSP old-timer or TDR Tokelnikov at the moment.

[heda]

I only rely on the new API Cockos added to read that gain reduction value.
I'm not sure which plugins support the gain reduction reporting. But if they don't, maybe in a plugin update they can add it. Like cockos just did in ReaComp. So now it depends on the plugin.

[Ideosound]

Is there a way to turn off the "rendering positive text" notes when rendering files? Would rather just have the inspectors go blank than the text that appears. Not a massive issue just a preference :]

[ericzang]

That is really cool Heda, thanks! Might a work around for plugins without gain reduction reporting be to use the JS: Gain Reduction Scope?

[heda]

Originally Posted by Ideosound

Is there a way to turn off the "rendering positive text" notes when rendering files? Would rather just have the inspectors go blank than the text that appears. Not a massive issue just a preference :]

WHAT!!!??? But that's the best feature in Track Inspector!
you reminded me that I had to make customizable sentences.

yes there is an option in settings page to hide it.

[heda]

Originally Posted by ericzang

That is really cool Heda, thanks! Might a work around for plugins without gain reduction reporting be to use the JS: Gain Reduction Scope?

Yes, it could be possible, but I think a modification in JS Gain Reduction Scope would be needed too to report the value as a parameter (like I did with General Dynamics)

[skippertag]

Hey Heda,
Hey y'all.

The new GR Feature is very welcome :-)

Your .gif looks very good because the item signal is quite low, but when you work on tracks that get around -9db the GR and the Loudness Meter are moving into each others.

How about putting the GR Meter to the side, somehow like PT has managed to show it? Maybe left of the Vol Fader?

What do you think?

[heda]

Originally Posted by skippertag

Hey Heda,
Hey y'all.

The new GR Feature is very welcome :-)

Your .gif looks very good because the item signal is quite low, but when you work on tracks that get around -9db the GR and the Loudness Meter are moving into each others.

How about putting the GR Meter to the side, somehow like PT has managed to show it? Maybe left of the Vol Fader?

What do you think?

I know what you mean.. but I don't see space where to put it... I normally have a lot of headroom in my tracks.. and I don't compress too much.
One thing you can do is to deactivate "Use EBUR128".. then the RMS meters go to the right where the loudness one was.
Or deactivate "Show RMS meters" then use EBUR128 at the right and the GR at the left.

[skippertag]

Originally Posted by heda

I know what you mean.. but I don't see space where to put it... I normally have a lot of headroom in my tracks.. and I don't compress too much.
One thing you can do is to deactivate "Use EBUR128".. then the RMS meters go to the right where the loudness one was.
Or deactivate "Show RMS meters" then use EBUR128 at the right and the GR at the left.

Hello Heda!

Thank you for the tips... good idea

I switched off the Show PEAK HOLDs and the waveform...Now it's much clearer to read.

Thanks!

[heda]

* v1.4pre31 (2017-11-16)
+ Meter Panel: Option to set True Peak MAX level when red indicator happens (TP MAX over level)(default -1.0)
# fix: crash deleting track version when version was created by rendering stem to new version.
# fix: no color of rendered new version if original version had no color.
+ Settings: Do not put FX online when switching track versions.
+ Settings: Do not put FX offline in unactive track versions when switching or creating track versions.

another update. About True Peak MAX gets red above a specific number. Now you can set it to whatever negative number you want. By default is the recommended -1.0 in EBUR128 standard.

[heda]

I forgot in the changelog, there is also a new "Render Track Selected Area to new track version" in the Versions menu. This renders to new track, only the time selected area.

[tyllmusic]

Originally Posted by heda

+ Settings: Do not put FX online when switching track versions.
+ Settings: Do not put FX offline in unactive track versions when switching or creating track versions.

Oh yeah! Thank you very much! Hopefully this will be a good workaround for me. Of course the whole deal of saving the online/offline status in track versions would still be much appreciated, but I very much understand that the low demand for this might not even be worth the effort.

Thanks for implementing these options so quickly!

[Klangfarben]

Originally Posted by heda

I forgot in the changelog, there is also a new "Render Track Selected Area to new track version" in the Versions menu. This renders to new track, only the time selected area.

Love this. Great idea.

[heda]

new update available. changelog:

* v1.4pre32 (2017-11-29)
+ Setting: Added option: Delete hidden Track Inspector Analysis Tracks on Exit
+ FXChain: Added buttons to show FXChain of: Selected Track, Analysis PostFader, Analysis PreFX buttons
+ Meter panel option: Show/Hide pan law and pan mode buttons
+ Export Tags as "Default" will make the list of tags always imported automatically
# fix: refix scroll to first fully visible panel when changing track
# fix: Hide Notepad when showing all track notes
# fix: when importing tags from file, or from default. Do not change tag settings(TCP, MCP, weight etc) if the tag already exists in the project

[ThrashJazzAssassin]

When clicking on 'T' in FX CHAIN

bad argument #1 to 'TrackFX_GetCount' (MediaTrack expected)

[heda]

Originally Posted by ThrashJazzAssassin

When clicking on 'T' in FX CHAIN

thank you... maybe because you have the meter panel hidden?
I'll fix that.

[ThrashJazzAssassin]

Originally Posted by heda

maybe because you have the meter panel hidden?

Correct. No errors when not hidden

[_Stevie_]

Hey Heda,

I became VIP today and installed Track Inspector and I really love it!
I have a couple of questions:

- is it possible to trigger the tags (track visibility) via shortcuts?
I already set up quite a few and I think, I will even add more. It would be
great to have shortcuts for Toggle visibility, AND/OR and Solo visibility.

- soloing via tags really takes long with a lot of tracks, can this behavior be improved? The Reaper internal "solo" function works faster as the Track Inspector version. Not sure what the issue here is.

- Track Archive: can this action be configured, so that the track does not disappear, when clicking "Archive"?

Keep up the great work!

[heda]

Hi Stevie. Thanks!

There are 9 actions that load the presets visibility.
"HeDa_Track Inspector VIP_Load Visibility Preset x.lua"
More can be created copying the lua file to Track Inspector VIP settings renaming the file and editing the number inside.

I've just discovered a bug that the current loaded preset doesn't change when changing with these actions. I think I broke this recently. I'll fix it.

Solo slow? It shouldn't be. I've tried with a tag with many tracks and it is very fast. I can't notice difference. But of course maybe it can be optimized more.

I use the archive button to hide tracks as a reference or something I don't really need anymore but I don't want to delete. So that's why I also hide it.
You can keep using your offline action. You can even add a custom button below in that panel with your action, and hide the Track Inspector "Archive" button.

Thank you for your comments

[_Stevie_]

Hey Heda!

There are 9 actions that load the presets visibility.
"HeDa_Track Inspector VIP_Load Visibility Preset x.lua"
More can be created copying the lua file to Track Inspector VIP settings renaming the file and editing the number inside.

What a great approach, easy to extent, that's awesome, thanks!

Ah okay, I thought we could maybe also toggle the tags via actions.
That's something I would love to put on my Lemur app on the iPad.
Another thing: when clicking on the instrument tags, the view is not focusing the first track. Could this be added? Let me show you what I mean:



I think I found the "problem". It's not the solo action that takes long, it's the re-selecting of the tracks.

I use the archive button to hide tracks as a reference or something I don't really need anymore but I don't want to delete. So that's why I also hide it. You can keep using your offline action. You can even add a custom button below in that panel with your action, and hide the Track Inspector "Archive" button.

That's a great idea adding my own disable/enable track action!

[heda]

Hi Stevie...
Thanks for explaining with the screen captures. It helps to understand the problem... The problem is you have TOO MANY TRACKS !!!!! Use less tracks and it will work. haha just kidding. I always wanted to compose orchestral epic soundtrack music.. I never managed to buy all the necessary libraries and I'm just jealous

What a great approach, easy to extent, that's awesome, thanks!

Ah okay, I thought we could maybe also toggle the tags via actions.
That's something I would love to put on my Lemur app on the iPad.

Yes. Copying to the "Track Inspector VIP settings" folder is necessary because the files inside "Track Inspector VIP" are deleted when updating the script, but not the "Track Inspector VIP settings" ones. If you need more than 9 presets buttons, there is an option for that in the settings page.
I could do actions for individual tags. But there sohuld be one action to select tag, one for toggle TCP view, one for MCP view, one for MUTE, one for SOLO.. for each tag. That's a lot of actions. I have an idea... mmmmm You will see

Another thing: when clicking on the instrument tags, the view is not focusing the first track. Could this be added? Let me show you what I mean:

I didn't test Track Inspector with so many tracks per tag. You are right it would be better to scroll to the first track in the tag. Thanks for the feedback!

I think I found the "problem". It's not the solo action that takes long, it's the re-selecting of the tracks.

I think I can fix that. There is probably a bug there. But it is not slow here. I thought you were using the solo button on the tag. Not the solo button for the selected tracks on the top panel.

That's a great idea adding my own disable/enable track action!

I told you to do it, but I didn't explain how to. I hope it was easy. You can also add custom buttons to each panel. In each panel name there is a button with a menu with options, or right click the panel name one, and at the bottom of the menu you add the custom button actions for that panel.

Thanks for your feedback! I'll try to simulate a huge template like yours and see if I can optimize more things.
A suggestion.. I see you have all the tags with weight 0. You can use the weight buttons on the tags, to reorder the tags by that number. So you can have the tags in the same order as your track folders. Once you have that, save the tags to a file "Default" to have all the tags loaded for each project.

[ThrashJazzAssassin]

I really like the tagging idea. Is there a way to auto-tag tracks when they are created? Thanks

[heda]

Originally Posted by ThrashJazzAssassin

I really like the tagging idea. Is there a way to auto-tag tracks when they are created? Thanks

How do you determine which tag to set automatically? For example if track name has the tag in the name?

Another thing I want to do is auto VCA slave assign for tags.

[ThrashJazzAssassin]

Originally Posted by heda

How do you determine which tag to set automatically? For example if track name has the tag in the name?

That would work. I recently started experimenting with prefixing my track names:

@ for Aux FX tracks e.g. @reverb
> for Audio Input tracks e.g. >In1/2
# for VSTi tracks e.g. #Kontakt
:: for MIDI tracks e.g. ::Yamaha MIDI In

Then each has it's own custom script to find and show only them in the MCP.

Your tagging system is more powerful and versatile, but it requires more preparation for each project.

Could they be auto-tagged by track colour?

[heda]

I could think a universal system using the #tag in the track name.. like hastags in social networks... for example a track name "Low Strings #Kontakt #orchestra" could automatically assign the Kontakt and orchestra tags to the track. So if you have the #tags in the track template that would work ok without having to manually type the tags on the track which would be more time consuming that CTRL clicking on a Track Inspector tag.
Track colours.. Each user uses different colours for different purposes. That would be more difficult.