Issue with Track Index Numbers Not Showing Up

[Retro]

I am modding jedstar2000's Hybridv1-1 Theme for forum member martmix and have run into an issue I cannot resolve. The theme uses a background image with the trackidx and I cannot get the index number to show on the new MCP layout I created. Any assistance would be greatly appreciated.

I uploaded the modded theme to the stash for inspection here:

https://stash.reaper.fm/v/39791/Hybr...ReaperThemeZip


For additional information see the The thread covering the mod found here:

https://forum.cockos.com/showthread.php?t=238821

[Retro]

A related issue I need assistance with. martmix requested external scale marking on the meters. I modified the mcp_idxbg.png with the scale, but now it does not seem to be loading in the MCP correctly and the scale is not showing up. I am pulling out my hair (and believe me, at my age I don't have a lot of that stiff to spare!)

Below is a mugshot of the villainous subject and attached is the file for further inspection.

[White Tie]

There's some pretty nutty WALTER going on in that theme for reasons I can't fathom. The base layout has this:

set mcp.trackidx [0 -102 73 2 0 1 0 1]
set mcp.trackidx.margin  	[25 927 15 0 0 0]

so that's drawing it at ...er... -102, and then pushing it into view with a massive 927px margin. And there doesn't seem to be a reason why. The whole theme is almost entirely static WALTER, so there doesn't seem to be a need for unexpected cleverness. You have removed the nutty margin, but you're still drawing in a strange place, so it seems to me you're heading in the right direction by writing your own WALTER instead of tweaking.

If an element is giving you trouble, I'd suggest replacing its image with something ugly, like a block of semi transparent full red, and then doing a new layout that just goes:

Layout "testing"
clear mcp.*
set mcp.size [blah]
set my element [values you're wondering about]
EndLayout

FWIW the theme also contains reverse_margin references in the TCP, READ THIS for my thoughts on that

[Retro]

Originally Posted by White Tie

There's some pretty nutty WALTER going on in that theme for reasons I can't fathom. The base layout has this:

set mcp.trackidx [0 -102 73 2 0 1 0 1]
set mcp.trackidx.margin  	[25 927 15 0 0 0]

so that's drawing it at ...er... -102, and then pushing it into view with a massive 927px margin. And there doesn't seem to be a reason why. The whole theme is almost entirely static WALTER, so there doesn't seem to be a need for unexpected cleverness. You have removed the nutty margin, but you're still drawing in a strange place, so it seems to me you're heading in the right direction by writing your own WALTER instead of tweaking.

If an element is giving you trouble, I'd suggest replacing its image with something ugly, like a block of semi transparent full red, and then doing a new layout that just goes:

Layout "testing"
clear mcp.*
set mcp.size [blah]
set my element [values you're wondering about]
EndLayout

FWIW the theme also contains reverse_margin references in the TCP, READ THIS for my thoughts on that

Thanks White Tie,

Yeah, the Walter has got my head spinning at times (doesn't take much to get this newbie head spinning) wondering why did you do it like this. Such a negative take on things (a real glass half empty approach )

Edit: Question - was this mysterious coder in your post named "Nick?"

[Retro]

Originally Posted by White Tie

There's some pretty nutty WALTER going on in that theme for reasons I can't fathom. The base layout has this:

set mcp.trackidx [0 -102 73 2 0 1 0 1]
set mcp.trackidx.margin  	[25 927 15 0 0 0]

so that's drawing it at ...er... -102, and then pushing it into view with a massive 927px margin. And there doesn't seem to be a reason why. The whole theme is almost entirely static WALTER, so there doesn't seem to be a need for unexpected cleverness. You have removed the nutty margin, but you're still drawing in a strange place, so it seems to me you're heading in the right direction by writing your own WALTER instead of tweaking.

What if I resized the MCP and increased the height and got rid of the negative number. I am still trying to wrap my head around what is going on with these negative numbers and the positioning of the trackidx bg and the idx number and how the two relate.

[White Tie]

I'd suggest you don't bother trying to get your head around the existing code. Decide where you want your element, draw it, go about your day.

[Retro]

It is something about the new background. I can load the background I made for the version without external meter scale and works fine. I can load original background with scale and it works fine. But when I use the version I added the scale which I drew on separate layer with pixel tool it doesn't recognize background. Strange, because it is the same one I made that works with only an added layer with the meter scale thrown on top (pink and yellow line layer topmost).

[White Tie]

Ah yes, your pink and yellow lines' colours are corrupted. I suspect a program has done some unwanted colourspace management.

[Retro]

Yeah, I am checking the png and Affinity Designer keeps wanting to render my pink lines at 240 255 0. This is becoming irritating. I am fiddling with setting trying to figure out whats off. It shouldn't be this difficult to get pure color!


Edit: Still doesn't solve the idx number issue. I am working on the mcp background and looking at ditching the idx background image. It causes more problems than its worth I think.

[Retro]

I tried loading the image into PS and adding the pink lines -- still corrupted. Finally, fired up my DAW and used it to render - perfect pink! It is as I have suspect for some time, the issue is my computer -- which explains why it has followed me from Inkscape to Photoshop to Affinity Designer.

[White Tie]

What's your operating system?

[Retro]

Windows