HeDa Track Templates v1.6.3 (2024-03-27)

[UknownSource]

I get this error msg when I drag and drop a template into the TCP panel only when there are no tracks in the TCP panel
__DEV__Track Templates VIP.lua:6178: bad argument #1 to 'SetOnlyTrackSelected' (MediaTrack expected)

[heda]

Thanks... fixed.

* v1.4.4 (2021-11-17)
# fix crash when dragging to empty project (Thanks @UknownSource)


I forgot to post about previous fixes too:

* v1.4.3 (2021-11-16)
# fix: Do not solo tracks that are muted, when rendering audio previews. (Thanks @Reflected)
# fix: remove invalid characters in track names when saving template files (Thanks @Reflected)

[UknownSource]

Originally Posted by heda

Thanks... fixed.

* v1.4.4 (2021-11-17)
# fix crash when dragging to empty project (Thanks @UknownSource)


I forgot to post about previous fixes too:

* v1.4.3 (2021-11-16)
# fix: Do not solo tracks that are muted, when rendering audio previews. (Thanks @Reflected)
# fix: remove invalid characters in track names when saving template files (Thanks @Reflected)

Ty!!

FR:
it's really nice that it automatically saves name of the first track for quick saving (especially when saving single tracks)

it could be also nice if there was an option to "save as" (so we can choose different name), this will be useful especially when saving an idea rather than a single track

[Skorobagatko]

Originally Posted by UknownSource

Ty!!

FR:
it's really nice that it automatically saves name of the first track for quick saving (especially when saving single tracks)

it could be also nice if there was an option to "save as" (so we can choose different name), this will be useful especially when saving an idea rather than a single track

I support this!

[UknownSource]

Originally Posted by UknownSource

Ty!!

FR:
it's really nice that it automatically saves name of the first track for quick saving (especially when saving single tracks)

it could be also nice if there was an option to "save as" (so we can choose different name), this will be useful especially when saving an idea rather than a single track

Originally Posted by Skorobagatko

I support this!

Thank for supporting

this is the best script ever!

[Reflected]

render audio previews for fxchains doesn't work :X

[heda]

Added Save As... and render audio for FX Chains, but what I'm thinking also is to add a way to dynamically preview FX Chains on selected tracks by clicking them as we play in the project. I'll see if it works.

* v1.4.5 (2021-12-08)
+ Save As (prompt for file name when saving track template) (FR @UknownSource)
# fix: small double click issue
# fix: Render FX Chain audio preview (thanks @Reflected)

[pcp]

Fantastic updates, thanks Heda for this awesome script!

[Reflected]

Originally Posted by heda

Added Save As... and render audio for FX Chains, but what I'm thinking also is to add a way to dynamically preview FX Chains on selected tracks by clicking them as we play in the project. I'll see if it works.

* v1.4.5 (2021-12-08)
+ Save As (prompt for file name when saving track template) (FR @UknownSource)
# fix: small double click issue
# fix: Render FX Chain audio preview (thanks @Reflected)

Thank u so much for these updates!
looking forward ur great idea!

[Reflected]

Hey Heda
I've noticed that for some reason the template windows losing their focus in their dockers while changing screensets

1. dock the template window in a docker
2. dock project bay window in the same docker
3. save a screenset with the project bay window on focus
4. save a screenset with the templates window on focus
5. load the screen set with the project bay on focus - works!
6. load the screenset with the templates window on focus - the project bay window steal the focus.. (no change)

[Reflected]

another bug:

the templates is saved without grid positions..

i mean when loading something that saved in 175bpm into a project with 125bpm, the items ignore the grid positions (getting off the grids)

[UknownSource]

Thank you heda for the updates!

Originally Posted by Reflected

Hey Heda
I've noticed that for some reason the template windows losing their focus in their dockers while changing screensets

1. dock the template window in a docker
2. dock project bay window in the same docker
3. save a screenset with the project bay window on focus
4. save a screenset with the templates window on focus
5. load the screen set with the project bay on focus - works!
6. load the screenset with the templates window on focus - the project bay window steal the focus.. (no change)

Originally Posted by Reflected

another bug:

the templates is saved without grid positions..

i mean when loading something that saved in 175bpm into a project with 125bpm, the items ignore the grid positions (getting off the grids)

confirmed both.

Also if I save the template from reaper's save template option, there is no such problem. so it's not a reaper thing I guess.

[heda]

this is strange.... I am testing to export it normally, and then with the script and it seems the chunk data is not exactly the same. I don't know why

I see some differences like this:

normal export:

<ITEM {7C6BD353-E7E5-C0B3-0391-7C1D3DB8B49A}
POSITION 1 2
SNAPOFFS 0 0
LENGTH 2.5 5


script export:
<ITEM
POSITION 1
SNAPOFFS 0
LENGTH 2.5

[Reflected]

Originally Posted by heda

this is strange.... I am testing to export it normally, and then with the script and it seems the chunk data is not exactly the same. I don't know why

I see some differences like this:

normal export:

<ITEM {7C6BD353-E7E5-C0B3-0391-7C1D3DB8B49A}
POSITION 1 2
SNAPOFFS 0 0
LENGTH 2.5 5


script export:
<ITEM
POSITION 1
SNAPOFFS 0
LENGTH 2.5

it wasn't like this in the paste, i just don't know which version changed that.

do you have any a clue how to fix this?

[Reflected]

is it worth to ask justin/shcwa for help ?

I can't use my templates properly in different bpms projects.

[UknownSource]

Originally Posted by heda

it seems the chunk data is not exactly the same. I don't know why

ohhh no

[Reflected]

can it be a issue in the settings?

[heda]

Originally Posted by gvanbrunt

I'm just setting up TT and have a strange issue. For some reason the directory doesn't show up unless the pane is nearly half the screen.

in the menu, check the "Minimum window width pixels to fit horizontally..."
changing that value affect how wide the window can get before switching to the normal display mode.
if you set it to 1, it will always display the panels normally.

[heda]

Originally Posted by Reflected

can it be a issue in the settings?

no.. I need to sit down and figure out what is happening.
I think the native track template saving may do something else and not only copy the chunk to a file. If that is the case, maybe we cannot do anything.. and wait for a API function to export templates from Cockos.

[Reflected]

Originally Posted by heda

no.. I need to sit down and figure out what is happening.
I think the native track template saving may do something else and not only copy the chunk to a file. If that is the case, maybe we cannot do anything.. and wait for a API function to export templates from Cockos.

oh no.. please don't say it.... wait for cockos?! it might take a decade mate.

Did you send a request for this API?

[heda]

no.. because maybe it is just that I am doing something wrong? I don't know.
maybe mpl is the one to ask.. he is the expert in API and chunks

[Reflected]

sent him a pm
cross your fingers

[mpl]

Originally Posted by heda

no.. because maybe it is just that I am doing something wrong? I don't know.
maybe mpl is the one to ask.. he is the expert in API and chunks

Totally not an expert here, but from first look, that looks like difference is only GUID after ITEM. And POSITION, SNAPOFFS and LENGTH duplicated with a same value, but measured with a beats (I guess it is for internal import handling, most likely item time-related values validation for specific timebase modes during import track template).

[heda]

Originally Posted by mpl

Totally not an expert here, but from first look, that looks like difference is only GUID after ITEM. And POSITION, SNAPOFFS and LENGTH duplicated with a same value, but measured with a beats (I guess it is for internal import handling, most likely item time-related values validation for specific timebase modes during import track template).

hey mpl. thanks.
yes I see that the difference may not be much... but I wonder if there could be more differences that we don't know and if it would be easier to ask Cockos for the API function to export a template to a specified file. Because the action to export a template is always prompting for a filename so it cannot be used on a script.

[Mavriq]

How do you change the color of the background and border that surrounds the image of a directory? Currently it is a olive color and its rather jarring with my current theme. I couldn't find it anywhere in the template file unless I'm missing something.

[UknownSource]

Originally Posted by gvanbrunt

How do you change the color of the background and border that surrounds the image of a directory? Currently it is a olive color and its rather jarring with my current theme. I couldn't find it anywhere in the template file unless I'm missing something.

it's right in this file:
\REAPER\Scripts\HeDaScripts\Track Templates VIP settings ---> Default_6.0.TT_theme

make a copy and play with the numbers.

[UknownSource]

Originally Posted by heda

hey mpl. thanks.
yes I see that the difference may not be much... but I wonder if there could be more differences that we don't know and if it would be easier to ask Cockos for the API function to export a template to a specified file. Because the action to export a template is always prompting for a filename so it cannot be used on a script.

this way or another
I hope that you will find a soution.

this script is amazing but this bug is a pain in the azz.

[Mavriq]

I did look in the theme file. I don't see a setting for this anywhere. I'm I missing something?

[heda]

Originally Posted by gvanbrunt

I did look in the theme file. I don't see a setting for this anywhere. I'm I missing something?

change the text_color2 values... for example this would have a cyan tone... I know... text_color2 is not very descriptive of what it does.


["text_color2_red"]=128,
["text_color2_green"]=255,
["text_color2_blue"]=255,


make sure you change it in a copy of the theme file in the settings folder. Otherwise it would be lost when replaced when updating the script.

[Mavriq]

Perfect! That did the trick.

I know that at some point you are planning to overhaul the theming part of the Script, but it would be helpful if there were comment lines in the Theme. Especially about what some of the obscurely named settings do.

Thanks again for a great add on that has been a game changer for me.

[Mavriq]

Is there a script similar to "HeDa_Track Templates VIP_Save Track Template" for FX Chains? I'm looking to add a shortcut so I can do that from the keyboard.

[Reflected]

any signs of solution?

[heda]

Originally Posted by Reflected

any signs of solution?

unfortunately not
Do you know any other script that saves track templates? Maybe someone has already figured it out? If not... I'll try to make an API request

[Reflected]

Originally Posted by heda

unfortunately not
Do you know any other script that saves track templates? Maybe someone has already figured it out?

couldn't find anything in the last 12 years. :X

[UknownSource]

Because the action to export a template is always prompting for a filename so it cannot be used on a script

Hey heda

i was thinking Maybe...
Is it possible that once we save a template using the "save as" feature in your script, it will save the template like Reaper's default template saving feature?

this might be a good temporary solution until Justin will answer your API request
what do you say?

[heda]

you could always use REAPER's native export template to overwrite the one generated with the script. The thing was that the script automatically generates the file in the folder you currently are displaying in the script.

[UknownSource]

what do the developers have to say about it?

[heda]

Originally Posted by UknownSource

what do the developers have to say about it?

This is probably not a priority for devs right now, but I have just requested API function here just in case
https://forum.cockos.com/showthread....47#post2515647

[Reflected]

Originally Posted by Reflected

Hey Heda
I've noticed that for some reason the template windows losing their focus in their dockers while changing screensets

1. dock the template window in a docker
2. dock project bay window in the same docker
3. save a screenset with the project bay window on focus
4. save a screenset with the templates window on focus
5. load the screen set with the project bay on focus - works!
6. load the screenset with the templates window on focus - the project bay window steal the focus.. (no change)

dear heda can you fix this please?


btw - when if I close reaper and reopen it, the TrackTemplates doesn't stay open even if it was open before I closed reaper. (maybe this is related)

**edit: not solved it completely but if I set it as startup action it works better, but if I load a screenset that shouldn't include TT it will open it when restarting. not perfect but if it's too tricky to solve, I can live with that now.

[Reflected]

hey heda

is it possible to make an option that will open extra panel for folders that are inside the selected folder?

this will really speed up my workflow
something like this: