Print

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

[wer]

Currently we have a way to export/import and share view definitions for Standard View, but nothing like that exists for Theater View/JRemote/DNLA views.

With all the customization and advances that have been made recently in the tooltip thread, view definitions (especially for Theater View) have become a lot more complicated than previously.  People would really like to be able to copy their carefully crafted view definitions to another machine, or to share them with others.

Could we please have an export/import functionality for Theater View/JRemote/DNLA views?

The export need not be super elaborate.  Even if it exported the entire structure for all views, as long as it saved it to a readable text file, the user could strip out the views he didn't want to share or copy.  The import function could then just add to the existing structure whatever is defined in the file.

The point is, even something very simple would be infinitely better than what we have now, which is a totally manual process where all levels must be manually created, and you have to individually copy/paste on many many many different entry boxes to move even one view over.

I think this could help a lot of people, and spur further cool developments.

[Moe]

This would be really great.

[lepa]

+1
I'm especially in need to duplicate my DLNA servers.

My scenario for example is that I'm creating three DLNA servers which all have some special use case:
- One DLNA server is meant to use inside LAN so nothing is re-encoded because I have the bandwith.
- Second server I have set MC to re-encode "everything" so it is practical when playing outside the LAN.
- Third is DLNA for headphones which uses DSP crossfeed.

It is really really time consuming and frustrating to create every view three times and then do the same also for JRemote views.

So big +1 from me

[greynolds]

Agreed, this would be a very useful addition.

[RoderickGI]

Agreed. This would be good. I'd mostly use it to import other people's View ideas, or share mine with them. But I might also use it to back up View definitions before I rework them, without the need to Backup/Restore the whole MC Library.

Particularly useful when building new Views based on new fields, so that I can Backup/Restore Views without having to Restore a Library and lose any new fields created.

[greynolds]

As sort of a stretch goal, it would be nice too if it could be extended a bit to be able to copy / paste views in the view editor.  I know I've created several different views that share a lot in common, but differ by grouping the results by import date, name, or series.  It sure would have been nice to be able to create one of the views and then copy/paste and tweak for each of the variations.

[wer]

The copy/paste is a good idea.  In fact, if actual file i/o is too much to ask, we could just copy and save the clipboard to a text file ourselves. 

[arcspin]

I agree with all of the above.
The ability to share Theater views in this community would be a game changer.

It even got me thinking of setting up a second DLNA server to encode as per lepa's post.

[Mans]

+1, agreed, this would be very useful.
Looking forward !

[greynolds]

The copy/paste is a good idea.  In fact, if actual file i/o is too much to ask, we could just copy and save the clipboard to a text file ourselves.

For the copy/paste feature to be useful for exporting the entire tree, a top level "All" item would need to be added to the tree in the Theater View editor.  When copy is selected, it would copy the currently selected node (and all sub-items).  Similarly, when paste is selected, it would paste the selected content under the currently selected node.  At least for me, this would have been a HUGE time saver when creating my views.

Being able to save the copied content to a file would similarly be a game changer for sharing views.  There would still be the issue of differences in custom library fields, but that's something people could presumably handle dealing with.

[wer]

For the copy/paste feature to be useful for exporting the entire tree, a top level "All" item would need to be added to the tree in the Theater View editor.

A new level in the tree isn't needed.  This could be done with just "Copy all" and "Copy node (and sub-nodes)" items on a right-click menu.

[greynolds]

A new level in the tree isn't needed.  This could be done with just "Copy all" and "Copy node (and sub-nodes)" items on a right-click menu.

Sure, that would work fine as well.

[timwtheov]

+1 for me here as well.

[wer]

Could someone from JRiver consider this and give us some feedback?

[JimH]

It isn't a bad idea.

[greynolds]

It isn't a bad idea.

So does that mean it's a good idea that will be given serious consideration?

[wer]

Well we already knew that in fact it's a really good idea.

But will you implement it? 

[JimH]

Possibly.  No promises.