Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mattkhan]

NB: this is aimed at TV use as current setup works ok for library content

JRVR profiles are expression based which mean you need to play tagged content otherwise it will stick in the default profile

I can't see a way to make this work automatically when used with a capture card & a filter that automatically changes format as the source changes, i.e. the source device can change content as it goes and MC will never see any tags to react to

I suspect that, right now, the only solution is manual profile changes

A nicer solution would be to give JRVR the ability to handle this case, i.e. tell it to switch between certain output profiles as the provided dshow mediatype changes based on the content of that mediatype.

I think such functionality would made MC/JRVR super slick for capture card use (as opposed to just very slick as it is today )

[Hendrik]

https://yabb.jriver.com/interact/index.php/topic,133480.0.html

The "JRVR" special variables are taken live during playback (not from the database) and any changes to them should also affect the profile selection immediately.

[mattkhan]

ah great, thanks, I had forgotten (or never noticed) that capability

[mattkhan]

see attached

profile.png = capture card
works.png = uhd bd (i.e. in library)

one works but the other doesn't, am I missing something or it's a bug?

[mattkhan]

I notice the capture card shows HDR10 0 nits whereas the source is sending as per the pic so I guess it means the metadata is not passed through to JRVR? and the JRVR HDR flag is based on the presence of metadata?

[Hendrik]

The [JRVR Video HDR] flag uses the transfer function to flag it, which according to the OSD is present.

Having looked over the code, it seems to set the flag to reload profiles when it changes just fine as well.

Output profiles are monitor dependent, you didn't have it on another screen when testing by any chance?

[Hendrik]

Something else just occured to me, there needs to be a database file for the profile selection to work, even if you don't use any properties from the file.
I don't know how you integrated your capture exactly, but if for some reason it does not have a database file, even if generic and with no data, that would explain why it doesn't work. The entire functionality to resolve these search expressions is based on files, so resolving that might need some extra thinking.

[mattkhan]

This card is registered as a device with 1 channel, it appears as a file of type tvlb when you play and I use that file type as the basis for a zoneswitch rule

certainly it looks like it is a regular database entry but idk how that works internally

[Hendrik]

You could check your MC log and see if it outputs anything about CVideoPlaybackJRVROptions::SelectProfiles, if it has no file, it would not log that at all. Otherwise it'll list some info about the profiles it selected, if any.

[mattkhan]

I can't find that in the log