INTERACT FORUM

Please login or register.

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

Author Topic: MC plugin Automation not working on the client side  (Read 2080 times)

raldo

  • Citizen of the Universe
  • *****
  • Posts: 1102
MC plugin Automation not working on the client side
« on: October 29, 2010, 11:19:40 am »

The PvdImport plugin doesn't seem to find any files when MC is run as a client.

Is there a way around this? I intend to use a client on a laptop for tagging...
Logged

raldo

  • Citizen of the Universe
  • *****
  • Posts: 1102
Re: MC plugin Automation not working on the client side
« Reply #1 on: October 31, 2010, 08:07:40 am »

Bump...................
Logged

raldo

  • Citizen of the Universe
  • *****
  • Posts: 1102
Re: MC plugin Automation not working on the client side
« Reply #2 on: November 02, 2010, 05:01:56 am »

Bump...................
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42442
  • Shoes gone again!
Re: MC plugin Automation not working on the client side
« Reply #3 on: November 02, 2010, 09:19:54 am »

I'm not sure the answer.

A client won't be able to "find" files on the file system when you're a client since they're not local files.

With the SDK, you can check the field 'Library Server URL' or 'Library Server Key' to see if a file comes from a server.

Logged
Matt Ashland, JRiver Media Center

raldo

  • Citizen of the Universe
  • *****
  • Posts: 1102
Re: MC plugin Automation not working on the client side
« Reply #4 on: November 02, 2010, 03:54:07 pm »

I'm not sure the answer.

A client won't be able to "find" files on the file system when you're a client since they're not local files.

Some details: I'm first doing an expression search which returns a collection of files. Then I perform a MJFileAutomation.Get("Filename",...) . I expected this to return the "local" filename but it returns an url of some sort "m01p://.." which I assume is the MCWS lookup.

In the ActionWindow\tag section, the filename I'm after is correct. There surely must be a way to obtain the "true" filename through the SDK?



Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42442
  • Shoes gone again!
Re: MC plugin Automation not working on the client side
« Reply #5 on: November 03, 2010, 09:17:56 am »

Some details: I'm first doing an expression search which returns a collection of files. Then I perform a MJFileAutomation.Get("Filename",...) . I expected this to return the "local" filename but it returns an url of some sort "m01p://.." which I assume is the MCWS lookup.

In the ActionWindow\tag section, the filename I'm after is correct. There surely must be a way to obtain the "true" filename through the SDK?

MJFileAutomation.GetFilename(...) will return a URL that points to the server.

MJFileAutomation.Get("Filename", FALSE) should return the local filename, not a URL.
Logged
Matt Ashland, JRiver Media Center
Pages: [1]   Go Up