More > JRiver Media Center 29 for Windows

JRVR Profiles Discussion

<< < (2/3) > >>

jgreen:
A big "No Thanks" to Zones also.  If there is a zone-specific benefit to custom settings, then at least enable media track-specific settings that would override this.

Currently, if I want to crop black bars in the video, or zoom the video, or correct aspect ratio, I can do this simply and powerfully on a track-specifc basis, and no one is ever hurt by this.  The settings travel seamlessly with the media track, and they are easy to undo or disable. 

A field-based system for JRVR profiles would serve much the same role, as does "Playback Range" currently, and plenty of others.

mattkhan:
You need to be able to distinguish between configuration for the display device and configuration for the source content. The former could (for me at least) happily be set on a per zone basis in a particular client, the latter should travel with the library item though I would think you may still need to override on a per zone basis. For example, say you had some content that would benefit from expensive processing to clean it up but one client has the horsepower to do that while another doesn't.

It would also be great if the same approach could be applied to audio configuration and DSP as it seems the same problem to me

jmone:
Matt makes a very good point.  I've use multiple MC Clients than range from NUCs to 1660ti to 3090 (well that one is the server as well), all reading the same library.  With the:
- 3090 I want all the goodies with HDR passthrough
- on one 1660ti I want all the goodies with HDR passthrough for but may need to drop down to FSRCNNX 8 for UHD 50/60fps
- on one 1660ti I want all the goodies with HDR tonemapping and again may need to drop down to FSRCNNX 8 for UHD 50/60fps
- on the NUCs I want HDR passthrough and just the minimum

These could all be done by profiles on each install......  I'm trying to think of when I'd need something that is track specific (like we have with other playback options that travels with the library) in regards to processing that would not fit in with a Profile.  I'm not sure I do.

Hendrik:
Settings are generally system specific, which profiles would fall into. They wouldn't sync to a library client, unless we specifically invent something new that would - but I'm not sure we need to.
Most profiles will likely be performance-oriented. Swap out settings based on content - resolution, or frame rate, or such.

Even if you make profiles based on the type of content (eg. Sports vs Cinema), it would be easier to setup rules that look at generic library fields (Subtype, Genre, etc), or even a custom field, instead of manually applying profile preset names for individual files to use, because a link from files to profiles would be awkward to maintain in the long term.

To make setting up multiple systems easier, we could consider profile import/export, which would also allow sharing here. Not syncing with the library gives you freedom on every client, at the expense of a bit more setup, but unless you have very closely matched clients, that might be an advantage.

A separate but related topic would be the ability to override certain file properties to fix bad files, like forcing deinterlacing, or overriding the color properties. This is obviously something that needs to be done per file, but it should be separate from any profile concerns, as it should target individual file details, and not generic settings.

jmone:
I think that would work for me.

Navigation

[0] Message Index

[#] Next page

[*] Previous page