Parental Lock for Imported Videos

[wirecreative]

Hey, so is this a part of Version 6?

I only had 6 installed for a few hours last weekend, but had some problems so I had to roll-back, but I'm going to try it again this weekend.

How does this parental control work? I'd love for it to be folder-based.

Would a protected folder also then not show thumbnails?

[dvd_maniac]

As a temporary fix I put all the videos that i do not want the kids to watch onto an external Hard Drive and keep it off until Me or my wife want to watch something on it. The videos still show up on the menu but gives an error when trying to play them.

Would definitely be nice to see something added to address this internally though.

[bcjenkins]

You can do this in SageMC, which is largely why I use it. I would prefer an add-on for the default stv though.

B

[nielm]

V6.1 allows 'real' parental controls on imported videos if you use the poperties file metadata feature added in 6.1.4 to specify the rating. (see the v6.1.4 release thread for a list of valid property names)

This is independant of the STV used (provided your STV supports parental controls)

For each video you want protected, you create a <videofilename>.properties file containing the line:

Rated=<rating>

where rating is one of the parental protected ratings (eg TV14, R, PG, etc)
Then reimport the file (remove/re-add library, or change file name or parent folder name and rescan).

eg:

my_naughty_vid.avi
my_naughty_vid.avi.properties (containing 'Rated=R')

When the file is reimported you can see using detailed info in my webserver that it has a parental rating, and when played, you will prompted for the parental code.

Caveats:

• Advisories don't seem to be supported in the properties file....
• The video file names will still be seen and be found in search results but not playable (just like late-night movies on TV).

Plus points:

• The parental controls will still work if the user browses media files to the file in question and attempts to play it
• so long as the properties file stays with the media file, the parental controls will be updated when/if you move the file.

[dvd_maniac]

Thanx Nielm,
This works flawlessly...

[ChePazzo]

Is there a way to put all of the info into a single file? or a way to batch create the files? I'm just thinking for 100's of movies, creating 100's of files would be cumbersome. I also guess there's no way to use the Sage GUI to create any of the .properties files?

Even so, it's still a useful feature and I can't wait to play with it.

Originally Posted by nielm

V6.1 allows 'real' parental controls on imported videos if you use the poperties file metadata feature added in 6.1.4 to specify the rating. (see the v6.1.4 release thread for a list of valid property names)

This is independant of the STV used (provided your STV supports parental controls)

For each video you want protected, you create a <videofilename>.properties file containing the line:

Rated=<rating>

where rating is one of the parental protected ratings (eg TV14, R, PG, etc)
Then reimport the file (remove/re-add library, or change file name or parent folder name and rescan).

eg:

my_naughty_vid.avi
my_naughty_vid.avi.properties (containing 'Rated=R')

When the file is reimported you can see using detailed info in my webserver that it has a parental rating, and when played, you will prompted for the parental code.

Caveats:

• Advisories don't seem to be supported in the properties file....
• The video file names will still be seen and be found in search results but not playable (just like late-night movies on TV).

Plus points:

• The parental controls will still work if the user browses media files to the file in question and attempts to play it
• so long as the properties file stays with the media file, the parental controls will be updated when/if you move the file.

[nielm]

Originally Posted by ChePazzo

Is there a way to put all of the info into a single file?

no - it has to be per-file

or a way to batch create the files?

no, but it would be trivial for someone to create a Dos batch or WScript file to iterate thro a directory structure and create a simple .properties file containing just the rating.

[bcjenkins]

This does not seem to be working for ripped DVDs. Bummer

FTR

videoframe/pc_restrict=Rape,Graphic Language,TVM,Graphic Violence,NC-17,R,PG-13,Nudity,Strong Sexual Content,NR,Brief Nudity,AO,

[JREkiwi]

Originally Posted by ChePazzo

I also guess there's no way to use the Sage GUI to create any of the .properties files?

<shameless plug> There is an import for the creation of .my and .properties files. Thread over here.

The test version 2.1.0 provides creation of properties files, import of info (including MPAA rating) from IMDB and editing of existing wiz.bin info.</shameless plug>

John

[nielm]

Originally Posted by bcjenkins

This does not seem to be working for ripped DVDs. Bummer

Narflex mentioned to me that this will be fixed in a future release...

[bcjenkins]

Originally Posted by nielm

Narflex mentioned to me that this will be fixed in a future release...

Yeah, I got that back from George at support. I did find a work around though. If I use your IMDB plugin along with John's .my file creator, I can import the info into the wiz.bin and the controls take affect.

B

[eobiont]

uoy could have jere's dirmon monitor the video linrary abd call a batch file to create the properties files, still it would be best if you coukd protect whole folder in the same way/

Let's say you have a folder called "fluffy bunnies" and then you drop a bunch of risque files in there. You sould be able to make a properties file at the same level and name as the folder and that would prevent access to the entire folder. The sage user would only see the folder name, and would be required to enter the password to browse the folder and sub folders. Seems like a pretty simple implementation, that lots of people would take advantage of.

I don't like at all how any placeshifter user can browse my whole hard drive.

[bcjenkins]

For me it is not "Fluffy Bunnies" more "Blood and Guts" Presumably you can prevent a PS user from browsing the directory by removing the SageTV user's rights to list directory contents with NTFS permissions.

B

[jchong]

Originally Posted by eobiont

...You sould be able to make a properties file at the same level and name as the folder and that would prevent access to the entire folder. The sage user would only see the folder name, and would be required to enter the password to browse the folder and sub folders. Seems like a pretty simple implementation, that lots of people would take advantage of...

Does this actually work? I wasn't able to get it to work

[edbmdave]

Originally Posted by flachbar

Yep, that's exactly what will be addressed in the next version


Dirk

Did this ever get implemented? If so how does it work.

[Stuntman]

I'm looking for this too.. need to be able to password protect just 'some' of the DVD's I've ripped..