INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Logic for Name Field on Import  (Read 121 times)

hoyt

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 867
Logic for Name Field on Import
« on: November 21, 2024, 04:26:46 pm »

What is the logic behind the Name field when a file gets imported? I recently changed my naming convention for some of my recordings, by adding brackets. Now the name defaults to the content in the brackets. It's not a huge deal, because I typically go in and tag stuff anyway, but why wouldn't it just default to the entire name of the file?
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72444
  • Where did I put my teeth?
Re: Logic for Name Field on Import
« Reply #1 on: November 21, 2024, 04:40:30 pm »

Video files?  Maybe Carnac:  https://wiki.jriver.com/index.php/Carnac
Logged

hoyt

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 867
Re: Logic for Name Field on Import
« Reply #2 on: November 21, 2024, 04:55:58 pm »

Yes, video files of tv recordings that I'm doing outside of MC and managing with some python scripts, and then importing into MC using MCWS Library/Import. They are just raw mkv files with no tags in them and they will be named "Series - SxxExx [resolution].mkv"

I didn't previously add the resolution and the file would come into MC with the Name showing Series SxxExx. Now it's literally [resolution], with the brackets. I can change my logic to be something else (parenthesis, braces, another hyphen, etc), but I thought that was fairly standard. I could tag the files in my script, but would prefer to just leave those blank and initiate the lookup in MC.
Logged
Pages: [1]   Go Up