Matt O. ...tivo what? ...dish dvr--uh... huh? ...cable dvr fees--you're kidding, right?
My System Specs
WHS 2011 (4TB running Drive Bender & MyMovies) ● Windows 7 Media Center (64bit, 4GB PC28400, 2x750GB SATA-II RAID 0, Ceton InfiniTV4 - Comcast Digital Cable, Portland) ● 3x Xbox 360 (1 slim, all wireless connections)
Ummm, .. this seems to be a DVR-MS file metadata editor written over 4 years ago before .WTV files. Does it work with the newer .wtv files, or did (or do) you have to convert them back to .dvr-ms first?
Update: well, I answered my own question by trying the editor on some .wtv files. To my surprise, it seems to work just fine on them with no noticeable side-effects. However, unless you need to get to some really obscure metadata fields, many of them can be edited directly in the windows file browser (usually the bottom preview/details pane area, and sometimes the properties dialog box).
heres a powershell script that pulls metadata from wtv files and renames them using it, so when you use mce buddy to convert to avi or mp4, you can have meaningfull filenames.
/code
## metaname.ps1 ##[void][System.Reflection.Assembly]::LoadFile("C:\Toub.MediaCenter.Dvrms.dll")$source="e:\recorded tv"$target="e:\recorded tv"foreach ($file in gci "$source\*.wtv") { $wtv = New-Object Toub.Mediacenter.Dvrms.Metadata.DvrmsMetadataEditor($file) $attrlist = $wtv.GetAttributes() $t = $attrlist["Title"].value -replace(":","-") $s = $attrlist["WM/SubTitle"].value -replace(":","-") $d = $attrlist["WM/SubTitleDescription"].value -replace(":","-") write-host "$file" write-host "$t-$s-$d.wtv" move "$file" "$target\$t-$s-$d.wtv" move "$file" "$target\$t-$s.wtv" }
if you want to copy instead of move/rename, change the move to a copy.its there twice in case the description makes the filename too long and the first move fails. if the first move succeeds, the second fails, so dont worry about it.
just edit the source and target vars. and then make a task with "powershell c:\metaname.ps1" (assuming you put it in c:\
the dll you get from the dvrms toolbox site.
## metaname.ps1 ### get the Toub.MediaCenter.Dvrms.dll from the dvrms toolkit site and save in in c:\ # if you save it somewhere else, change the path below[void][System.Reflection.Assembly]::LoadFile("C:\Toub.MediaCenter.Dvrms.dll")# set the vars below to fit your situation$source="e:\recorded tv"$target="e:\recorded tv"# this loop gets the Title, Subtitle, and Description from each wtv file and renames itforeach ($file in gci "$source\*.wtv") { $wtv = New-Object Toub.Mediacenter.Dvrms.Metadata.DvrmsMetadataEditor($file) $attrlist = $wtv.GetAttributes()# you can add or remove other metadata as you see fit $t = $attrlist["Title"].value -replace(":","-") $s = $attrlist["WM/SubTitle"].value -replace(":","-") $d = $attrlist["WM/SubTitleDescription"].value -replace(":","-")# the multiple moves below handle cases of duplicates and long descriptions, only one will actually work. move "$file" "$target\$t-$s-$d.wtv" move "$file" "$target\$t-$s-$d-2.wtv" move "$file" "$target\$t-$s-$d-3.wtv" move "$file" "$target\$t-$s.wtv" move "$file" "$target\$t-$s-2.wtv" move "$file" "$target\$t-$s-3.wtv"}
this is a little clearer
make powershell run in remotesigned mode by typing "powershell Set-ExecutionPolicy RemoteSigned" at the start bar
you may have to run powershell as administrator to the above command to workSet-ExecutionPolicy RemoteSigned
TheOsburnFamilMost video containers (avi for instance) don't hold any usable metadata.
That is not true. AVI certainly can hold at least two types of metadata: "native" INFO LIST and XMP. abcavi Tag Editor supports the first and Metadata Touch supports both.
Dugso TheOsburnFamilMost video containers (avi for instance) don't hold any usable metadata. That is not true. AVI certainly can hold at least two types of metadata: "native" INFO LIST and XMP. abcavi Tag Editor supports the first and Metadata Touch supports both.
Dugso, I was referring to usable metadata for sorting purpose as it related to the OP. Virtually anything can hold metadata--it's just using it that it becomes problematic. Sorry for the confusion.