Ed Elliott
Forum Replies Created
-
This is an old thread but there was no complete solution given. But Dave LaRonde’s suggestion is the only way I could figure to do it.
The steps are to use Colorista II’s Keyer to define the matte; select Invert in the Keyer; suck all of the color out using the all three of the Secondary 3-Way luminance shift controls, all three of the saturation shift controls (highlighted but not visible in the image above because the indicator is white and the scale is white), and reduce Secondary Saturation to -100; then apply a blend mode of Stencil Luma to the layer.
Colorista II v1.0.7; After Effects CS6
-
I created a CS6 version:
4850_premieremarkerscs6.ahk.zipBefore running this version, you must create a keyboard shortcut for Edit Marker = Ctrl+Alt+Shift+F12. (I couldn’t identify an unused shortcut which tied in nicely with the M key (like the other marker-related shortcuts) — hence the obscure F12 combination.)
If you encounter difficulties, you can email me your .prproj file (no media needed) if you wish and I will debug. eelliott AT tritel.net
-
Arran,
As you have discovered the present script will not work with CS6. Adobe changed the keyboard shortcuts for Create Sequence Marker, Next Sequence Marker, and Previous Sequence Marker. Additionally, whereas the old NumPad * shortcut would either create a new sequence marker when none existed at the CTI or edit the existing marker at the CTI, the new shortcut (M) will create a new marker regardless of whether a marker already exists at CTI. So, at a minimum, to work with CS6 the script must be modified for the change in these keyboard shortcuts. And the modified version will probably require that the user manually create a keyboard shortcut for Edit Marker because there is no default shortcut. There may be other changes required.
In case you are not aware: if you just need to view or edit (as opposed to exporting) a summary list of the sequence markers, CS6 now has a Markers panel (Window > Markers).
Opening the CS6 project in an earlier version probably will not work. Thread https://forums.adobe.com/message/4470584?tstart=0 offers workarounds for opening CS6 projects in CS5 (opens directly with no special actions required) or CS5.5 (manually edit project file). I don’t have CS5. My CS4 test hung while opening the CS6 project and had to be manually terminated. And manually changing the Version in the .prproj file then opening in CS5.5 resulted in the modified .prproj file opening successfully BUT THE MARKERS WERE MISSING FROM THE SEQUENCES (Adobe probably changed the way markers are encoded between CS5.5 and CS6 — which probably means that opening is CS5 will not work either).
If none of the suggested alternatives work for you, let me know and I’ll try to get the script working with CS6.
Ed
-
This version supports Premiere’s various time formats more gracefully. For example, if a sequence’s time format was set to feet+frames, the prior version would extract the time as “arker @ 2+19” rather than “2+19”.
If you have Audition, be aware that there is an alternative to using this script if you just want to view, rather than export, the sequence markers: select a Premiere sequence > Edit > Edit in Adobe Audition > Sequence …> OK, then within Audition > Window > Markers. This may be the only alternative available to Apple users.
-
This version fixes a problem where all numbered markers were ignored, i.e., the previous versions only worked for unnumbered markers.
To recap in case this thread has gotten a little confusing, this version:
o Exports Premiere marker data (time, name, comment) to the clipboard for both numbered and unnumbered sequence markers.
o It does not export the marker number for numbered markers.
o Works as-is with the English-language version of Premiere CS5.5/CS5/CS4/CS3 (earlier versions have not been tested). For the French-language version of Premiere, one line will have to be uncommented (i.e., use Notepad to remove the semi-colon).
o It can be modified for other language versions of Premiere by using Notepad to change the value for stringMarker.
o The instructions are at the beginning of the file. Use Notepad to view or edit the file.
-
To all of those expressing their appreciation for the script, I’m pleased that so many of you find it useful.
Sam, I do not have a web site or a link for donations. I view efforts like this as giving back in a small way to those many people around the world who have given their time freely to post problem solutions, tutorials, information (e.g., Wikipedia), and software (e.g., AHK) or to develop and maintain web sites, etc. For those desiring to donate, there are many worthy charities and projects which can make better use of donations than I could. Some needs are pretty obvious, but local animal shelters are often behind the scenes and forgotten. The local animal shelter here, for example, is a non-profit which receives only small governmental compensation — one-week of financial assistance for each stray. It survives with a no euthanasia policy only because of the community’s generosity with money, supplies, and time.
-
The following thread discusses a similar problem, but somewhat different scenario, but may give you a clue:
https://forums.creativecow.net/thread/3/918905
I have no expertise on formats and “long gop”. I was searching Creative Cow for Premiere <-> Resolve workflow issues and happened to notice your thread and the potential answer.
-
The link I posted couple hours ago should work fine for English and French users. The version posted below will also work fine for English and French users. Anyone converting the script for another language version should definitely use the version below.
This version revises the way a Marker’s CTI (time) value is extracted from the Marker’s title. The prior version counted characters from left-to-right, which worked fine for the English and French versions because “Marker @ ” and “Marque a ” have the same number of characters. Other languages could use longer or shorter titles. The revised version counts characters from right-to-left (i.e., from the end of the title) so the logic is now language independent and extracts the right-most 11 characters as the CTI.
-
Kevin and I got the script working in the French version of Premiere. Testing indicates that the only language-dependent item is the “Marker” text which appears in the top-left of the Marker dialog box. There is now an additional line (presently commented out) in the code for “Marque”.
Also, I reversed a previous change which was intended to make the left-most sequence in the Timeline the first sequence output to the clipboard. While working on Kevin’s problem I discovered that the earlier change was NOT working as intended because Premiere is sorting the sequences in alphabetical order before displaying them in the Window > Timeline menu. Another downside of this previous change was that the keystrokes used to bring up the Window > Timeline menu vary by language; so reversing the change made it simpler to port the script to other languages. And this latest script works as is with CS3 (the previous version required commenting out one line).
The above change means that the script is back to its original logic, i.e., if you have multiple sequences in the Timeline and you want the left-most sequence to be the first sequence output to the clipboard, you should make the right-most sequence active (click on it) before executing the script.
The revised script works as-is with the English-language version of Premiere CS5.5/CS5/CS4/CS3 (earlier versions have not been tested). For the French-language version of Premiere, one line will have to be uncommented (i.e., use Notepad to remove the semi-colon):
3014_premieremarkers.ahk.zipThe PDF which I uploaded for Kevin a couple days ago is now only relevant regarding the text at the top-left of the Marker dialog box. The stuff at the bottom-left of the PDF about the Premiere main menu (Alt+w, t, t, {Enter}, {Enter}) is NO LONGER RELEVANT. As discussed above that code has been replaced with a simpler, language-independent Shift+3 to activate the Timeline.
-
Kevin,
(I thought that I had sent this reply 12 hours ago but it did not show up in the thread so I am retyping it. I think that I associated the original submission with the uploading of the attached PDF and my reply has gotten lost in the cloud somewhere. Anyway…)
The most likely cause of the problem is that you are running a non-English version of Premiere. The attached PDF discusses the two areas of the script code which probably require modification for other languages.
I do not have the French version of Premiere installed and the French version of the Premiere Help PDF does not include the screen snapshots which would have allowed me to modify the code myself.
The attached PDF contains two Premiere screen snapshots. If you are not comfortable with modifying the code yourself, you can send me the similar snapshots from your French version and I can modify the code. This, of course, is not the best way to do software development and it may take more than one iteration to get it right.
Besides the two likely culprits discussed in PDF, there are two other less likely causes: (a) common keyboard shortcuts are different in the French Version and (b) low-level naming of software elements is different in the French version. I suspect that (b) is is unlikely. Here I’m referring to such things as the “class” (“Premiere Pro”) and Windows controls such as “Edit3” and “Edit4” in the Marker dialog. If, for example, there was a problem with “class” you would have seen a popup that the script could not find a Premiere session. I mention (a) and (b) now only to set the expectation that the two likely causes discussed in the PDF might not totally resolve the issues with the French version of Premiere. But with some persistence we should be able to get it working. If the PDF does not get the script working, for example, I suggest looking at each Send command in the script and testing it from the keyboard, e.g., does Home move to the beginning of the Timeline; does Ctrl+RightArrow move to the next marker; does Ctrl+LeftArrow move to the previous marker; does Numpad * create new Marker and open existing Marker; etc.
Sorry that I do not speak French. Hopefully the above is relatively easy to understand.
Ed
3007_premieremarkerslanguagesensitivity.pdf.zip
