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

[hopi]

EDIT... yes works good now thought it did not but had to restart reaper to get new ver. of TI active
thank you sir

EDIT :

so reporting ... using goto next or previous as a button in the TI works as expected and scrolls both the TI and the MCP as it should
However, that buglet I mentioned about having to clk twice on the TCP panels to get the MCP to scroll when TI is active is still there
I hope you can believe me but I could make a LICECap if needed
Now in fact it is a really strange bug... say we have 3 tracks... I should simply single clk om any to also see that trk in the MCP
BUT NOT... each single clk on a track shows the first, top most track in the MCP, the second clk does make it scroll to the correct track
... the bug is only there when TI is active

[heda]

Yes I believe you. For me it works well. Maybe you can send me an email with your reaper.ini and track inspector settings file and I can see if I can detect what is different that breaks it.

[hopi]

sure I will get those to you asap

email sent let me know if you don't get it plz

[heda]

I got it but I am very busy lately. I tested and I can see the issue. it is something in your track inspector settings that is different that causes it. But I still don't know what.

[hopi]

thanks.... no hurry... take your time

[heda]

this is one of those bugs that run and hide...
for now I have seen that if you minimize the meters panel, it won't happen. It sometimes creates undo entry for reset EBUR128 when changing track, which causes the issue (I think)

[hopi]

sorry for finding that kind of bug... ugh

I don't know what 'minimize the meter panels' setting is...
.. surely not the Show Meters check box????

plz tell what to change for now...

thanks much HeDa

EDIT: did you mean the little down triangle for the meters panel? that does not fix it for me...

again... what is extra strange is ... I have to custom buttons to go to next or prev track on the TI... and when using those the TCP and MCP work as they should...
It is only when clking on the TCP panels that it shows the bug

[Zirrex]

Please add new special tag - Video.
This is good for video production (video track, dialog track, reff music track).

[hopi]

Also... hey HeDa... on the receives... there is a S button but not a Mute button... yes I know there is a M on the sends...

could there be an M on the receives??? It could be handy

[heda]

fixing...

* v1.4rc25 (2019-06-25)
# fix: scroll mixer view for selected track
# fix: issue with meters for a track not showing after switching to master track and back.

[heda]

Originally Posted by Zirrex

Please add new special tag - Video.
This is good for video production (video track, dialog track, reff music track).

thanks. I'll look into it

[heda]

Originally Posted by hopi

Also... hey HeDa... on the receives... there is a S button but not a Mute button... yes I know there is a M on the sends...

could there be an M on the receives??? It could be handy

Thank you, now I don't remember why I didn't make mute buttons on receives. I will see if it is not difficult to add.

try latest update for the scrolling issue in the mixer... it should work now. But let me know.

[_Stevie_]

Hey HeDa, I just wanted to thank you once again for all the recent additions.
Truly remarkable and you really surpassed yourself!

[hopi]

Originally Posted by heda

try latest update for the scrolling issue in the mixer... it should work now. But let me know.

YES... a very big YES works as it should, you nailed it whatever it was

[Skorobagatko]

Get this when deleting track:

[heda]

Originally Posted by Skorobagatko

Get this when deleting track:

thanks.. I don't get this error.. but this fix should prevent it.

* v1.4rc26 (2019-06-28)
# fix crash when deleting track in some cases

[AtmanActive]

Absolutely brilliant.

A masterpiece.

Cockos should buy this out and include it by default in every version of Reaper. That's how good it is!

[heda]

Originally Posted by AtmanActive

Absolutely brilliant.

A masterpiece.

Cockos should buy this out and include it by default in every version of Reaper. That's how good it is!

Thank you. You are exaggerating a bit. Just a bit. Hehee

[heda]

scroll mixer MCP is causing problems for me.. scrolling it all the time when I don't want... so I made it as an option.. and disabled by default.
Still I see that it is needed to click twice to make it scroll, which I have no idea why. It seems a refresh issue somewhere, but I don't see anywhere where the script could cause this. But forcing scrolling it all the time is a bad workaround. Should investigate more about it.
Also, fixing a crash and some other things too.

* v1.4rc27 (2019-06-30)
# fix crash tags presets sometimes
# selected track scroll MCP into view as an option (disabled by default)

[AtmanActive]

Hi heda,

I would like to express my frustration with using time offset feature of Track Inspector (TI). Since forever I've been using time offset on each and every track in each and every DAW, so for me, it is an absolutely crucial DAW feature.

In current TI implementation I have two problems with it:

Problem #1:
In my Reaper JSFX folder I have "Time Adjustment Delay" by Cockos, while TI is adding "time_adjustment" to insert chain. Since all of my tracks already have the Reaper's built-in one, as soon as I want to control the offset, TI adds it's own "time_adjustment" and I end up with two of them on the track. In other words, TI doesn't recognize that "Time Adjustment Delay" is already on the track and adds it's own instance. Even though it does correctly read it's value before I touch the slider on TI.

This problem can be fixed in two ways, IMHO:
a) make TI recognize "Time Adjustment Delay" and skip adding it's own "time_adjustment" when track already has it.
or
b) install "time_adjustment" together with TI so I can switch to that one and have that one on each track and avoid ending up with duplicate FX.

I did read the source code and indeed "Time Adjustment Delay" and "time_adjustment" are identical, but how does that help me when I can't find "time_adjustment" in my FX list and I can't add it myself. So TI is actually forcing me to add all time-offset FX for each track through it's UI and it's UI only. More like a nuisance than a feature.

Problem #2:

Time offset scale is too coarse. In last 25 years of my DAW experience, I never ever used time offset of more than +- 40ms. If I encounter a situation where I need more than that, then I move the items in the arrangement and reset the offset to 0. In 90% of usage cases offsets are from -20ms to +20ms for me. Current TI implementation is going +-400ms which makes the slider too coarse and fiddly and almost impossible to set to, for example, -5, or +3 which are more or less most important values ever. Also, the slider head is 1px wide which makes it extremely hard to navigate with mouse. IMHO, it should be as thick as pan slider is, which is, by the way, working perfectly.
So, if I may suggest, make the time offset slider handle fat, same like pan has now, and scale the whole slider to go -40ms to +40ms and it should work perfectly then.

Thanks.

Cheers!

[Klangfarben]

Originally Posted by AtmanActive

Problem #2:

Time offset scale is too coarse. In last 25 years of my DAW experience, I never ever used time offset of more than +- 40ms. If I encounter a situation where I need more than that, then I move the items in the arrangement and reset the offset to 0. In 90% of usage cases offsets are from -20ms to +20ms for me. Current TI implementation is going +-400ms which makes the slider too coarse and fiddly and almost impossible to set to, for example, -5, or +3 which are more or less most important values ever. Also, the slider head is 1px wide which makes it extremely hard to navigate with mouse. IMHO, it should be as thick as pan slider is, which is, by the way, working perfectly.
So, if I may suggest, make the time offset slider handle fat, same like pan has now, and scale the whole slider to go -40ms to +40ms and it should work perfectly then.

I regularly use track offsets with a -100ms negative delay or sometimes even slightly higher. It really depends on the sample library you are using. So -40 to +40 would be WAY too small of a range for me.

[_Stevie_]

Same here, Hollywood Strings and CSS are between 100 and 200 ms.

[AtmanActive]

Yeah, I understand. For slower music and slower attack-time instruments wider range is useful.

Still, having it from -200ms to +200ms would already double the precision, comparing to what it is now.

Actually, for precision's sake it should move exactly one ms per pixel. So, depending on how wide it is on the screen that's how wide the range should be.

Ultimately, it should be user configurable in preferences of TI so users that need -1000ms to +1000ms and do not care about a single ms difference can have their way, while others can have it more precise if they need to. I would be quite happy to be able to set it to -20ms to +20ms for myself.

[heda]

the name of the file is time_adjustment
but the description is Time Adjustment Delay
so it should have to be able to detect that.. I'll fix it.

regarding precision and range...
there is a global setting to configure the range of the display, but I see it is not working... I'll have a look at it when I can.

Try CTRL dragging for fine adjust.. also you can click on the number and type the exact ms number.
CTRL clicking on it, would store it as a preset.. you can name the preset according to your instruments for example.
The to access presets, right click on the number and it will display a menu with your presets.



Thanks

[AtmanActive]

Thanks heda.

CTRL+click helps, a lot. A bit fiddly, but OK.
One pixel wide slider handle is a pain in the butt.

Correction: it doesn't even have a slider handle, we are supposed to click on the indicator line ?!?

[heda]

the bar is 5 pixels height... Dragging from a bit below until the panel ends also works. but I can make it customizable to make a 15 pixels height bar for example. Maybe in high resolution monitors is too thin.

[AtmanActive]

No way to make it the same as pan?

[heda]

I was checking the "Time Adjustment Delay" issue...
and it should already detect that name as the plugin for the delay.

but if you insert a new one from TI, then it will add it as "time_adjustment" instead of "Time Adjustment Delay", even if it is the same plugin. I don't know why, but if I try to insert it as "Time Adjustment Delay", it won't insert it. I could insert it and then rename it to "Time Adjustment Delay" but I dont' find API function to rename FX ... ¿?

I've done the option to increase height of the delay bar. update later.

[heda]

small update to change the delay bar height(in pixels) 10 by default. in settings: Delay bar height.

* v1.4rc28 (2019-07-02)
# customizable delay panel bar height

[_Stevie_]

Amazing HeDa! I really like the new track delay fader.

[AtmanActive]

Thanks heda, these updates help a lot. Brings TI's time offset function one step closer to be fully usable. Your development efforts are highly appreciated.

However, there is still some weird slider behavior when I try to push "Delay panel bar scalling" below zero. I have it set to 0.1 right now (since I want to try to calibrate it for -20ms to +20ms for my usage scenario) and at that scale it behaves really, really weird. It jumps all over the place, but instead of changing mouse sensitivity, it just changes the graph display scaling. So, I can't reach mouse precision even though it looks like I should be able to. In other words, what I believe is happening is that the bar itself is getting scaled alright, but it's reaction to mouse input is not.

As far as the JSFX issue go: is there a way for me to rename the JSFX to match "time_adjustment"? I wouldn't mind renaming/hacking the built-in JSFX just to have it work properly with TI.

Thanks.

Cheers!

AtmanActive

[Klangfarben]

Hey Atman, I think you might have better luck just editing the JSFX itself to have the range you want. Shouldn't be that hard to do. You can then save your edited JSFX with whatever name you want.

[AtmanActive]

Thanks Klangfarben, good idea, I'll try that. I'm not sure TI will recognize it though, but it's worth a try.

[Klangfarben]

Well, you can rename the original plugin with a different name and your edited version with the "proper" name.

And as far as the delay range, TI will use whatever is set in the JSFX, so if you just open up the JSFX and hit edit, you can find the range and tweak. Just go to Slider 1 and change the range from -1000 to 1000 to whatever you want.

"slider1:0<-1000,1000,1>Delay Amount (ms)"

For example: slider1:0<-200,200,1>Delay Amount (ms)

Should sort you out.

[AtmanActive]

That works!

I copied the JSFX plugin, renamed the copy to "time_adjustment_cockos", then edited "time_adjustment", commented out two first lines (desc) and changed

"slider1:0<-1000,1000,1>Delay Amount (ms)"

to:

"slider1:0<-100,100,1>Delay Amount (ms)"

And yes, now TI recognizes it when it is already on the track, it doesn't create unnecessary duplicates, and range is what I wanted. I changed TI's setting "Delay panel bar scalling" to 1 and the mouse-to-screen resolution is just right.

All problems solved. I'm a happy camper.

[hopi]

hmmm ok on that delay and the scaling setting...

I find the red\blue line for the delay to be a little bitchy to grab and drag.. like the 'hit point' for the mouse cursor is a bit vague... maybe it would be better if the height of the line itself was more? like either a user setting or double what it is now???

PS: also it seems I can't adjust the delay slider when play is stopped... it only adjusts when the project is playing... is that what we'd expect???

[heda]

Hopi, that is what the latest update was about. To make the height user configurable. It is in settings page.
I don't remember having any problem changing it while stopped. It should work but I will check later when I can.

[hopi]

ok let me dbl check my updates

OK... I have the latest update...

I must be blind cuz for Delay I find only Delay panel bar scaling
and what that seems to control is how the red\blue bar scales in length to match the range of the +1000 to -1000 ms setting in the JS FX itself
I don't see anything to make the red\blue bar more px's high or thick or however we'd say that

The update DOES let me move that red\blue bar OK now when not playing so that is good and it is easier to grab so maybe it's OK for now

ummm no I take that back... to me moving that red\blue bar is still 'bitchy'... hard to grab it and then to drag it out takes great distance of mouse movement
like halfway across a 30" monitor... so something could be better IMHO... I would expect it work as nicely as the pan slider wouldn't you?

[AtmanActive]

hopi, I had the same experience until I changed TI setting "Delay panel bar scalling" to 1. From that moment on, it started behaving much better.
But I agree with you and I still think that having a proper slider handle, like the one on pan or sends would work much better.

[heda]

Hopi you are right that grabbing from the bottom part of the bar if it has small height, doesn't work. I don't know why... I'll tweak that. Thanks

the difference with this and a normal slide bar is that the movement is relative, you don't need to grab from the handle, there is no handle.. you can grab it anywhere on the bar and slide, because you may want to slide more than the range display allows. But I guess it could be changed to a fixed defined displayed range if it is easier to handle.

another option would be to create presets in the button (CTRL click) for -5 -7.5 -10 12.5 15 17.5 20 etc... the most used ones and forget about dragging the bar

about the height... The setting should be there.