• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

app.project.path Prefix with \\?\

New Here ,
Jul 19, 2017 Jul 19, 2017

Copy link to clipboard

Copied

Hello,

I want to get current project path of adobe premiere pro.

I am using below code to get that path

getProjectPath : function() { 

                    

     projectPath = app.project.path 

     return projectPath 

}

but the value contains with prefix '\\?\' in windows

the value is like below

\\?\D:\test\import\test.prproj

Is this premiere pro issue?

Do we have any specific fix?

Is there any prefix for MAC os?

I have tested in Premiere Pro version 2015 & 2017

TOPICS
SDK

Views

746

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Engaged , Jul 19, 2017 Jul 19, 2017

Quoting Bruce Bullis​ in the similar thread here :

No; that prefix is the Window OS's idea.

Naming Files, Paths, and Namespaces (Windows)

Whereas in Mac OS paths are always like "/Volumes/[VolumeName]/path/to/file" .

Votes

Translate

Translate
Engaged ,
Jul 19, 2017 Jul 19, 2017

Copy link to clipboard

Copied

Quoting Bruce Bullis​ in the similar thread here :

No; that prefix is the Window OS's idea.

Naming Files, Paths, and Namespaces (Windows)

Whereas in Mac OS paths are always like "/Volumes/[VolumeName]/path/to/file" .

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jul 19, 2017 Jul 19, 2017

Copy link to clipboard

Copied

As a followup question, is this actually an issue? Does it cause problems with certain other Premiere Pro APIs that actually use the path?

Or was it simply unexpected (as it really does look like a bug when you first see it...)?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jul 19, 2017 Jul 19, 2017

Copy link to clipboard

Copied

Hi,

I think the APIs is not entirely consequential in its design; I haven't done a reverse test (feeding a "\\?\D:\path\to\file.ext" to a method which expects a "D:\path\to\file.ext" string), but I guess under the hood there are some error catching methods which add Win32-required prefixes or directives to the input. In other cases, read methods seem to return the Win32 result. Or maybe it's added there as well, I don't know... anyway, the results vary.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jul 19, 2017 Jul 19, 2017

Copy link to clipboard

Copied

LATEST

Right, I guess the question was whether the OP was experiencing problems when passing such a path to another panel API or not. If so, then it would be worthwhile to report it to Adobe.

On the other hand, they may simply need to special-case their logic if, for example, they're doing something with regular expressions or showing the path to users...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines