INTERACT FORUM

Yes, right click while a film is playing, however the only thing I dont like is its universal and doesnt save for just the film thats playing. I believe it should only apply to the film and save to that film, not all!

I thought that I could use a global variable in the Add Rules section, however it seems that global variables only work in the Modify Results section (see attachment). Could you please add Global Variable usage in the Add Rules section?

Hi, I have 5.1.4 system and I want to to add my to subs to my stereo playback.
How do I add it properly and without eliminating the possibility to playback also 5.1 or 5.1.4 when I want to?

It looks fine, but as predicted, the entire CloudPlay page is one solid color - no contrast for the CloudPlay Header area like it is now (or I guess before after this update). Maybe no one will care, but skins that don't use dark gray backgrounds might not look as good as this skin with one solid color.  Regardless, you can just go with it as-is and see if you get complaints that header is not a different color from the main content area any longer.

Any possibility of getting rid of the ugly purple New and yellow Popular text link colors?  Using those colors is such a bizarre choice and they clash with basically every skin.  Maybe the yellow text works for the Aruba skin, but that skin is seriously out-of-date looking and should be deprecated (along with a slew of others IMO).  The purple does not work with any skin.

Here it is with Purity using the list background.

I don't know why the code was using the tree background color but list text colors.  It seems like if it just used all the same it would work fine.

I am pretty sure I made that exact point about the streaming page in a thread a year or so ago. Every view should use the list background color for the main content area so it is consistent across every MC view.

A potential issue however is the CloudPlay Header already uses the list background color (or at least that's what appears to be when I check multiple skins). That means this change would create a solid color throughout the CloudPlay view/page. Not the end of the world, but stylistically, different colors for the header and main content areas is probably preferable, if for no other reason than to help visually segregate them, and to be consistent with header/content colors elsewhere in a skin.

That is why I suggested using the hex color specified for Background or BackgroundHeader in the <VIEWHEADER> section. This would provide guaranteed proper text/background contrast as it would already be accounted for in the rest of the skin' s design.

Coupling the new CloudPlay background color with the header color change I am proposing here will result in the header/content colors matching throughout every MC skin, which seems to me to be a desirable outcome.  The attached pictures show how the Playlist and CloudPlay page appearance do not match currently - these changes would fix that.

And while you're at it, maybe get rid of the oddball colors that are used for the New and Popular text links? Those colors conflict with every skins other text colors, so I'm not sure why that was done.  And really, why not turn those links into buttons instead, like you have for the genre options across the top?

How about we try this:
Changed: Cloudplay uses the list background color instead of the tree background color (since it uses list colors for text).

I don't know why the code was using the tree background color but list text colors.  It seems like if it just used all the same it would work fine.

Hi HPBEME.  Should we pull that mod into the main Purity skin?  It looks like you changed two files: Playerbar_Display and Tree_Background.  Thanks.

Not really sure - obviously I don't work at J River, but I do appreciate your asking for my opinion. I was just trying to help a specific user out with that skin - it took me about ten times as long to write the explanatory post than it did to make the skin change! That said, the issue the OP was having would apply to anybody using the Purity skin with CloudPlay, so it probably does make sense to permanently incorporate those modifications.

You probably saw what I did with the PlayerBar display image, but I will describe the changes I made specifically, just to be sure: The images upper corners were nicely rounded, but the lower corners were almost sharp. I mirrored the upper half of the image to the lower half to make all the rounded corners symmetric, which to my eyes looks better.

I also increased the image height. Purity's default is to capture the data only within its PlayerBar display "window", with the track slider and 3 lower right buttons (Repeat, Shuffle, DSP) outside of it. As you know, in the main.XML file the user can change the Data Style from 0 to 1 in the <PlayerBar> section, which enlarges the display window to include the track slider and three buttons within its borders.  But the original image's short height resulted in no discernible difference when you toggled the Style setting. With the increased image height, you can now show the PlayerBar window two different ways as intended.  I did not bother to explain all this in the original post… because… well… it would take so long to explain, hahahahaha.

We don't even know yet if the OP has tried out this modified skin and likes the change! 

All that said, I really do think (as I noted in my 1st reply at the bottom) CloudPlay's content area should use the skin's XML specified list background color, and the CloudPlay header should use either the skin's specified tab Background or PlayList Header background color. That way you never have to worry about any color conflicts or poor contrast.  Every skin uses text/background colors that are contrasting (some with better/higher contrast than others) - if they didn't, every skin's display would be problematic across all MC view types, not just CloudPlay.

I know that CloudPlay, Spotlight, and Streaming pages/views behave differently than all the other views, which I presume has something to do with those pages interfacing directly with the Internet (maybe?). So perhaps it's just not possible to point directly to a skins specified hex color, which is why CloudPlay's content background color is "sampled" from the tree background… is that correct?  If however, that is not the case, then using approach I noted above would be much more robust and foolproof.

I don't believe Windows can control subsampling ... it's up to GPU drivers ... NVidia allows to control subsampling, but that's at output stage (so Windows handles everything in RGB ... then Nvidia subsamples that for final output)

Just for kicks ... set your GPU to 4:2:2 10 bit ... then look at small colored text on white background ... you should see color "bleed" to white background... that's subsampling - not so great ... for video - basically, JRiver tries to minimize this - if you subsample, that effort is for nothing

We don't specifiy bitdepth or color subsampling at all. All you tell it is the resolution and refresh rate you want. I don't believe Windows has a setting at all to control the subsampling used. Any further settings are usually hidden in graphics card specific settings somewhere. Maybe you can setup those to specifically handle only those modes you desire.