MarshalSerna
Explorer
MarshalSerna
Explorer
Activity
Sep 13, 2024
01:51 PM
1 Upvote
I agree. For me it is an indispensable tool. That said, if Dr. Brown's Services ever stop working it will be a real problem.
... View more
Feb 06, 2024
02:38 PM
1 Upvote
@Kevin Stohlmeyer I'm still on this project, and continuing to use 25.3.1. I just wanted to report that neither "Deactivate Native Canvas" nor unchecking "Use Mulithtreaded Compositing" resolves the mask display issues for me in this version.
... View more
Feb 04, 2024
05:01 PM
Thanks for the suggestions. I've downgraded to 25.3.1 for while a so that I can wrap a project. It's been working as before. Assuming the settings remained intact from 25.3.1 to 25.4 and back, it appears I already had "Deactivate Native Canvas" selected in Technology Preview settings. I've now unchecked "Use Mulithtreaded Compositing" in Performance to see if that resolves the mask display issues in 25.3.1.
... View more
Feb 02, 2024
12:47 PM
Just going to add: 25.3.1 does have some really annoying display glitches, and I was sincerely hoping this update would address them. The biggest issue is that the display of layer masks break at different zoom levels. Huge, random blocks of stuff that should be masked out will nonetheless be displayed. The masks themselves are intact, but the display is incorrect. Often zooming several steps in our out will show the effect of the mask as it should be displayed, but it doesn't repair the view at the zoom level you wish to work at. I've made several adjustments based on other reports here, but its still a consistent issue.
... View more
Feb 02, 2024
11:41 AM
Downgraded to 25.3.1 and everything seems to work as before.
... View more
Feb 02, 2024
11:38 AM
1 Upvote
I just updated to PS 25.4. When I open a file, I get a new tab or window for the document, scroll bars, layers visible in the pallete, etc... but the document is invisible. There are no canvas boundaries visible. Obviously, this renders the application entirely unusable. I'm going to try and downgrade for now.
... View more
Nov 14, 2023
04:43 PM
5 Upvotes
I'm using PS2022 and PS2024 for testing on MacOS Ventura 13.6. For some reason, Extendscript is not treating /Users/USERNAME/Desktop/FOLDER as an absolute path. This code (with a valid path) returns false when checking folder.exists: var folder = new Folder('/Users/USERNAME/Desktop/FOLDER');
var files = folder.getFiles();
// Check if the folder exists
if (folder.exists) {
alert("Folder exists.");
} else {
alert("Folder does not exist.");
} If the path is changed to this, then folder.exists returns true: var folder = new Folder('/Volumes/Macintosh HD/Users/USERNAME/FOLDER'); When I use the function 'Folder.selectDialog' I get a string like the path in the first example - without Volumes/Drive - which should be a valid absolute path. In my previous testing it worked fine, but that was on a different machine. If I need the Drive info in the path, how can I grab that? Thanks in advance!
... View more
Jun 23, 2023
03:24 PM
@Mark.Dahm in the workaround you describe, Apples own OS-specific app has an option to keep a specific note (analogous to a docucument, no?) always on top. It seems that providing us with an option to keep a document window floating on top would in fact adhere to Mac OS interactions. I understand the design premise, but the notion that we should use a Apple-provided, Mac OS specific app as a workaround to achieve this indicates that Ps is not really adhering to Apples convention. Using a note to do this becomes problematic if any changes need to be made to the floating document, in which case the process of copying and pasting must be done over and over. I imagine that color management could be an issue as well. Tiling the floating windows works as long as you never forget to hold option while zooming, which even seasoned Mac users often forget. Just give us the option. It would be most Apple-like.
... View more
Jun 23, 2023
03:02 PM
1 Upvote
@gary_sc good to know. I've downgraded for BR2022 for some time.... at least until Adobe either restores the "New Window" functionality, or makes Content Windows as functional as opening a new Bridge instance. (You know... independent filters, metadata, and previews concurrently viewable, etc.)
... View more
Jun 22, 2023
09:20 PM
Hear's an idea, Adobe: Why not remove the never-going-to-work-always-greyed-out CUT option and the also-never-going-to-work keyboard command-X shortcut hint from the Edit menu altogether?? Maybe you can replace it with a note in the drop down menu that says something like "YOU CANNOT CUT ON MAC OS. NOT EVER. USE COMMAND-C TO COPY, THEN COMMAND-OPTION-V TO MOVE." It doesn't have to be that wordy, or all caps. At least people would know what's going on, instead of that for 4 or 5 years you've had the same, invalid menu item and keyboard shortcut in your menu.
... View more
Jun 20, 2023
06:40 PM
Update: this bug only seems to happen when using the application frame.
... View more
Jun 20, 2023
05:46 PM
Photoshop 23.5.5 (I've downgraded from PS2023 until Bridge "New Window" functionality is restored.) MacOS 13.4 The Adobe Color Picker will not let me sample anything outside of the Active Document. I've got two images open, one has a Solid Color layer (the Active Document), the other is an image in another PS window that I need to sample colors from. Clicking on the color I need in the non-active document does nothing. Sample size is set to 5x5 (none of the sample size options work), sample is set to all layers, and the document I'm trying to sample from is flat, no layers, no masks, not in quickmask mode. I was able to make it work once by changing the sample size, but that only worked the one time. This is basic functiuonality... what's up?
... View more
Jun 19, 2023
08:41 PM
3 Upvotes
I begrudgingly switched from Mac to Windows in 2020, while waiting for Apple to update their pro machines to Apple Silicon. Ps works on Windows of course, but little things like how the Wacom tablets respond, inconsistent color management, and the OS in general were constant annoyances. You deal with it. I'm getting back to work now on a new Mac Studio M2. And as much as I like it... there are annoyances. Here's one: With PS on Windows, you don't really have a choice but to have the Application frame on. You don't get windows floating over the desktop. I prefer this. It's clean, and it keeps me focused. If you do float a window IT ALWAYS APPEARS ON TOP OF THE APPLICATION FRAME. This feature has become indispensable for me. I do a lot of color matching. Having a small independently floating window or two showing a section of an image that I can move around a larger, tabbed image that I am working on has become my standard workflow. I can open 20 files in a tab group, float my reference color images over the top of them and get to work, one image at a time. Honestly, I've forgotten how I did this before. Whatever it was was far less efficient. On Mac, with the application framed any floating windows are sent BEHIND THE FRAMED APPLICATION when any of the framed tabs are made active. Why? Why can't I keep a reference image or two floating above the image I'm working on? If one attempts the workflow I describe above... it's impossible. Windows must be constantly resized. You cannot place a reference anywhere over the image you are working on and make adjustments while looking at the reference, as the reference get's sent to the back. As much as I hate to say it, the way this works on Windows makes so much more sense, and allows for a much more streamlined workflow. I see this has been a request since at least 2014. That’s almost a decade. https://community.adobe.com/t5/photoshop-ecosystem-discussions/how-do-i-keep-a-floating-window-on-top-of-a-tabbed-document-so-that-it-can-be-used-as-a-reference/td-p/6141600
... View more
Jun 14, 2023
06:25 PM
1 Upvote
I appreciate that you agree your solution is horrible. I won't belabor that. The primary reason I refer to Bridge 2023 as "broken" (not completely broken, but nonethless not ready for production use) is the ill-advised and much lamented elimination of New Window / new instance capablity it has had for DECADES, and its replacement with utterly insufficient Content Windows. This was a breaking change that NO ONE ASKED FOR. Sure, plenty of people have asked for something like Content Windows to be added to Bridge. But if you polled any number of folks working with hundreds or thousands of images in a day (or who serve multiple clients, or a work in a variety of quite common scenarios) if they would trade New Window fuctionality for the current Content Windows, the answer would be a resounding NO. I won't go into the list of things you can do with multiple Bridge windows/instances that are impossible in Bridge 2023, as I have done so elsewhere on these forums. Suffice to say that BR2023 breaks workflows that have been employed by professionals around the world for a long, long time, and instead of employing cubersome (non-solutions, TBH) like the one you offered for Image Processor, many of us are continuing to use BR2022 (and PS2022 on Mac*). I'm setting up a workstation right now - brand new M2 Mac Studio, 96GB, 2TB SSD Mac OS 13.4. Frustratingly, I can get Dr. Brown's Image Processor Pro (long since developed or supported) to work with BR2022, processing images in PS2023. Drop down the Tools Menu to Dr. Brown's, select IPP, and (if PS 2023 is running) just like that PS2023 is brought forward with the IPP dialog. But if I want Adobe's own Image Processor to work (on Mac*) I must install PS2022. That's just... Lame. *Mac. We have a Workstation running Windows 10 in the studio (AMD 3900X 12-core, 64GB ram.) Running Bridge 2022 on that machine, Image Processor will work with whichever version of Photoshop happens to be open. If Photoshop is not already running, invoking IP from Bridge will open the latest version of PS installed. On that machine, it will open the latest Photoshop Beta we are evaluating.
... View more
Jun 14, 2023
01:53 PM
I feel this. I'm doing my best to avoid Bridge 2023 still, as I know many in production are. Having a hell of a time making basic integrations like Image Processor work with Bridge 2022 to PS 2023 on a new install now, so it's just a matter of time until I quit my job completely. haha.
... View more
Jun 14, 2023
01:42 PM
3 Upvotes
Gary, you cannot do the exact same thing from the file menu in Photoshop. How would you use the PS file menu to, say... filter the files in a folder by aspect ratio (for example) then run image processor on only those images? This is key functionality using a working version of bridge (i.e. versions prior to the still-broken Bridge 2023): make a selection of images in bridge using filters or whatever, and then do something with those images using Image Processor or any of the actions in Tools > Photoshop. I would also note that FOR YEARS many users (myself included) have mixed and matched versions of Bridge with different versions of Photoshop. The idea that both of these applications must maintained at exactly the same version is something new, and would have been demonstrably fiction just a year ago.
... View more
Jun 13, 2023
06:28 PM
The ability to have separate Bridge instances remains crucial not only to my workflow, but the workflow every imaging production professional. Content Windows do not cut it. Why? Unlike opening a New Window (or instance of Bridge) like we could in version after version previous to 2023, Content Windows as currently implimented lack the ablity to: Apply different filters to multiple sets of images and have those controls independently and simultaneously available. Like you can when running multiple instances of Bridge. Have those differently filterable sets available with full controls in separate spaces / windows sets. Like you can when running multiple instances of Bridge. Quilckly switch between sets of images with shortcut keys. Like you can when running multiple instances of Bridge. We need these features back, working natively on Apple Silicon running Ventura. Instead, here I am installing an Intel app on a second generation Apple Silicon machine. Lame.
... View more
Feb 09, 2023
04:08 PM
How do you give each new Content Panel their own Filter settings, and File tree, and Preview Panel? Can you move the different Content Panels to different Windows Desktop window sets / Mac OS Spaces? If I have multiple monitors, can I set up a Content Window with its own Preview Window on each monitor?
... View more
Feb 07, 2023
05:39 PM
Apologies for the delayed response. I've been super busy, and I guess I'm not getting notifications about replies. I'm mixing things up a bit here I think... you cannot FSV Bridge on Mac, but what you can do with previous versions is run separate instances in multiple "desktops". I have both Mac and Windows workstations in my studio, and on each we use multiple desktop enviroments. Usually one per client. In early 2020 I started using a Windows machine as my primary workstation, waiting for Apple Silicon to mature. I have a like/hate realtionship with it. (Would never say I love it, haha!) I honestly wish more apps allowed multiple instances like Bridge used to do. At first I disliked how Outlook on Windows would open a new instance in seprate desktop environments, but now I find it to be crucial. In one desktop environment/windowset I can have Outlook open to emails from one specific client, with with independent Bridge window(s). There can be only one instance of Photoshop open, which is fine as I'm always only actually working on one client's images at a time. If only Acrobat and Slack would allow multiple instances... Anyway, yes - alt+tab on windows to cycle to different instances in the current desktop environment on Windows (though it does cycle through ALL open apps within the current desktop environment) and command+tilde to cycle between instances on MacOS (though one instance must be in focus to start.)
... View more
Feb 02, 2023
11:17 PM
1 Upvote
The ability to have separate Bridge instances is crucial not only to my workflow, but the workflow every imaging production professional. I know, this has been brought up before. The issue is not resolved until we reclaim the ablilty to: Apply different filters to multiple sets of images and have those controls independently and simultaneously available. Like you can when running multiple instances of Bridge. Have those differently filterable sets available with full controls in separate spaces / windows sets. Like you can when running multiple instances of Bridge. I have multiple clients, and I like to keep each one's notes and assets in their own space. IMO, it's one of the reasons why spaces / window sets exist. Quilckly switch between sets of images with shortcut keys. Like you can when running multiple instances of Bridge. Do this natively on Apple Silicon running Ventura. I understand that multiple content panels was a popular request. Perhaps those of us who rely on Adobe tools to make e-commerce happen aren't very popular. Nonetheless, the giant misstep of removing "New Window" functionality has been decried practically since the day Bridge 13.0 was released. Please tell me that sometime in the very near future we will have this functionality back. Rosetta will not be around forever.
... View more
May 05, 2020
01:50 PM
Having a strange issue with a new-ish machine: With a few images open in tabs in PS, the active image I'm working on will freeze. The cursor changes to to a white arrow (like the Direct Selection tool). The program is still running... I can save, access menus, change tools (though while on the image that has frozen, the cursor remains stuck on the white arrow). I can change focus to another open image, or open a new image and work on it as normal - but when I switch back the image that has frozen will not display (the newly opened image remains) and again the cursor is stuck. I can go for a while, maybe 30 minutes or so sometimes before this happens. When it does happen I'm able to save and reopen. Still, it's incredibly inconvenient and just weird. System Info: Intuos Pro PTH-651 / Driver 6.3.38-2 Adobe Photoshop Version: 21.1.2 20200410.r.136 2020/04/10 Operating System: Windows 10 64-bit Version: 10 or greater 10.0.18362.778 System architecture: AMD CPU Family:15, Model:1, Stepping:0 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, HyperThreading Physical processor count: 12 Logical processor count: 24 Processor speed: 3793 MHz Built-in memory: 65484 MB Free memory: 47998 MB Memory available to Photoshop: 59997 MB Memory used by Photoshop: 80 % ACP.local Status: - SDK Version: 1.26.5 - Core Sync Status: Reachable and compatible - Core Sync Running: 4.3.36.1 - Min Core Sync Required: 4.3.4.2 ACPL Cache Config: - Time to Live: 5184000 seconds - Max Size: 20480 MB - Purge Percentage: 50% - Threshold Percentage: 85% - Purge Interval: 300 seconds Manta Canvas: Disabled. Alias Layers: Disabled. Modifier Palette: Enabled. Highbeam: Enabled. Image tile size: 1028K Image cache levels: 4 Font Preview: Medium OpenGL Drawing: Enabled. OpenGL Allow Old GPUs: Not Detected. OpenGL Drawing Mode: Normal OpenGL Allow Normal Mode: True. OpenGL Allow Advanced Mode: True. AIFCoreInitialized=1 AIFOGLInitialized=1 OGLContextCreated=1 NumGLGPUs=1 NumCLGPUs=1 NumNativeGPUs=0 glgpu[0].GLVersion="2.1" glgpu[0].IsIntegratedGLGPU=0 glgpu[0].GLMemoryMB=6144 glgpu[0].GLName="NVIDIA GeForce GTX 1660 Ti" glgpu[0].GLVendor="NVIDIA Corporation" glgpu[0].GLVendorID=4318 glgpu[0].GLDriverVersion="26.21.14.4292" glgpu[0].GLRectTextureSize=32768 glgpu[0].GLRenderer="GeForce GTX 1660 Ti/PCIe/SSE2" glgpu[0].GLRendererID=8578 glgpu[0].HasGLNPOTSupport=1
... View more
Jul 26, 2019
04:38 PM
I'm pretty new to scripting, and taking sort of a deep dive here. (For me at least!) I've got a script that creates uniquely-named displacement map file, then applies the map with a Displace Smart Filter. So far so good. What I'd really like to take advantage of though is CC2019's new "Embed File Data in Smart Object" feature. This feature prevents the 'Could not update smart object files because the file was not found' error common when moving files with displace filters applied to smart objects between different computers. This error forces the user to redo the Displace filter, and browse to the correct map file. I want to avoid making my client have to do that! I've used r-bin's Script Event Listener to try and sus this out. It appears that the generated code stores displace data in "DspD". You'll see it in the second to last line of the code I've pasted below. (It's truncated from 30110090 to 10000.) I assume this data is some representation of the map file. I'm wondering if there's a clever way to get that data, store it, and use it in my script. I'll be batch processing many, many files and they'll each have a unique map to grab. var d = new ActionDescriptor(); d.putInteger(stringIDToTypeID("horizontalScale"), 10); d.putInteger(stringIDToTypeID("verticalScale"), 10); d.putEnumerated(stringIDToTypeID("displacementMap"), stringIDToTypeID("displacementMap"), stringIDToTypeID("stretchToFit")); d.putEnumerated(stringIDToTypeID("undefinedArea"), stringIDToTypeID("undefinedArea"), stringIDToTypeID("repeatEdgePixels")); d.putPath(stringIDToTypeID("displaceFile"), new File("~/Desktop//DisplaceMap_1668.psd")); d.putBoolean(charIDToTypeID("EmbF"), true); d.putData(charIDToTypeID("DspD"), /* real data length = 30110090, truncated to 10000*/ String.fromCharCode(0x40,0x1A,0x00,0x00,0x80,.... executeAction(stringIDToTypeID("displace"), d, DialogModes.NO);
... View more
Jan 24, 2017
06:40 PM
1 Upvote
Hi Kevin, Unfortunately I do not have a backup of the file from earlier in the day. However, I was able to recreate the problem: I have just sent you two files: One that opens - “Rustic_Home_Gate_03", and one that does not - "Rustic_Home_Gate_03_deleted-captions”. The “deleted captions” file that errors out is exactly the same as the one that opens, EXCEPT I have deleted *all* of the individual captions from the captions ‘clip’ at the top of the timeline. (I did also offline all of the assets, as I don’t have then local on this Mac.) My intended workflow was to keep as many elements as I could from this sequence. (That’s why I left the framework for the captions in place.) Once that change has been made, it appears to be impossible to re-open the file. (As this was one of the very first steps I did, it is unlikely that any previous backup would work anyway.) Note that the file will re-open if I leave a single caption field in that caption ’clip’. The problem occurs when there are not caption fields left in the clip. Thanks, Marshal
... View more
Jan 24, 2017
06:09 PM
Kevin: Let me see what I can do. I should have a time machine backup from earlier that day. Note however, the issue I'm having is that the project will not open. Hence this forum post. If I was able to open the file, obviously I would not be reporting this new issue. (I am aware of the captions issue where the captioning panel will not work unless the workspace is set to the default. This is why I mentioned it in a previous comment.) When opening this file, I get no indication that it is corrupt (I have seen that warning on past projects.) Instead, I get the message that a serious error has occurred. If I have an earlier backup, I'll send it to you. If per chance that earlier backup opens without error, I'm not sure what you'll be able to help me with. The whole problem is the Serious Error on opening. Sent from my iPhone
... View more
Jan 24, 2017
04:30 PM
PP2017 CAN'T find the previews. It SHOULD NOT be this way.
... View more
Jan 24, 2017
04:29 PM
I've had to do this so many times I've forgotten it's an issue: Every time I "Render In to Out" PP2017 can seem to find the render files it just created. If I close the program and re-open the project, it loads the previews and played perfectly. Quitting the program has become part of my workflow. Should be this way. Windows 10, quad i7, 32gb, ssd system, ssd media drive.
... View more
Jan 24, 2017
10:45 AM
Yes, I do have a backup copy. How can I send it to you?
... View more
Jan 23, 2017
03:11 PM
2 Upvotes
Could it be that once you have created captions (which presently only work if your restore default workspaces) you must ALWAYS use the default workspaces? I notice that the thread that crashed is about captions...
... View more
Jan 23, 2017
02:52 PM
This project (which started in PP2015.3, and was unfortunately updated to PP2017 a few months ago), has run into every new bug imaginable. I have been saving a new version for each product video that I add. Friday I saved the project with a new filename, then did 8 hours of organizing and editing, auto-saving and manually saving often. Today, I cannot open the project. I get a progress bar/ file opening dialog, then the obsolete audio filter warning, then I see my project windows... and immediately the "Sorry, a serious error has occurred that requires shutdown" message. The primary machine I've been using for this project is running Windows 10. It is an i7 with 32gb of ram, and two gtx 550 ti cards (don't laugh.) The project lives in the Creative Cloud folder on an internal SSD system drive, footage is on another internal SSD. I just tried opening the same project file (sans footage) on my MacBook Pro 2015 with PP2017.0.2 and I get the SAME error. The report is pasted below. Any suggestions as to how I might get that day's worth of work back? Thanks. Process: Adobe Premiere Pro CC 2017 [1073] Path: /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/MacOS/Adobe Premiere Pro CC 2017 Identifier: com.adobe.PremierePro.CC11 Version: 11.0.2 (11.0.2) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Adobe Premiere Pro CC 2017 [1073] User ID: 501 Date/Time: 2017-01-23 14:47:27.078 -0800 OS Version: Mac OS X 10.12.2 (16C67) Report Version: 12 Anonymous UUID: DE8679F5-9E9B-3F88-B4AF-45A04061F7D8 Time Awake Since Boot: 3800 seconds System Integrity Protection: enabled Crashed Thread: 26 Dispatch queue: com.apple.root.utility-qos Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000040 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [0] Thread 26 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 com.adobe.dvacore.framework 0x000000010010ff59 std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >::basic_string(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 9 1 com.adobe.dvacaptioning.framework 0x0000000102270d5c dvacaptioning::CaptioningMetaData::CaptioningMetaData(dvacaptioning::CaptioningMetaData const&) + 28 2 com.adobe.dvacaptioning.framework 0x0000000102270712 dvacaptioning::CaptionList::GetMetaData() const + 18 3 com.adobe.Backend.framework 0x00000001027412b6 BE::SequenceCaptioningStream::HarvestCaptionsInner(std::reverse_iterator<__gnu_cxx::__normal_iterator<ASL::InterfaceRef<BE::IClipTrack, BE::IClipTrack> const*, std::vector<ASL::InterfaceRef<BE::IClipTrack, BE::IClipTrack>, std::allocator<ASL::InterfaceRef<BE::IClipTrack, BE::IClipTrack> > > > > const&, std::reverse_iterator<__gnu_cxx::__normal_iterator<ASL::InterfaceRef<BE::IClipTrack, BE::IClipTrack> const*, std::vector<ASL::InterfaceRef<BE::IClipTrack, BE::IClipTrack>, std::allocator<ASL::InterfaceRef<BE::IClipTrack, BE::IClipTrack> > > > > const&, dvamediatypes::FrameRate const&, dvamediatypes::TickTime const&, dvamediatypes::TickTime const&) + 1350 4 com.adobe.Backend.framework 0x0000000102740b14 BE::SequenceCaptioningStream::HarvestCaptions(dvamediatypes::TickTime const&, dvamediatypes::TickTime const&) + 580 5 com.adobe.Backend.framework 0x000000010273e915 BE::SequenceCaptioningStream::Init(ASL::InterfaceRef<BE::ITrackGroup, BE::ITrackGroup> const&, dvacaptioning::StreamFormat) + 629 6 com.adobe.Backend.framework 0x000000010273e60d BE::SequenceCaptioningStream::CreateSequenceCaptioningStream(ASL::InterfaceRef<BE::ITrackGroup, BE::ITrackGroup> const&, dvacaptioning::StreamFormat) + 173 7 com.adobe.Backend.framework 0x000000010273cb97 BE::CaptioningStreamCompositor::SeedCaptionMap(dvamediatypes::TickTime const&, dvamediatypes::TickTime const&) + 679 8 com.adobe.Backend.framework 0x000000010273986e BE::CaptioningStreamCompositor::Init(ASL::InterfaceRef<BE::ITrackGroup, BE::ITrackGroup> const&) + 622 9 com.adobe.Backend.framework 0x0000000102739547 BE::CaptioningStreamCompositor::CreateForSequence(ASL::InterfaceRef<BE::ISequence, BE::ISequence> const&) + 199 10 com.adobe.Backend.framework 0x0000000102da535e BE::Sequence::GetCaptioningStreamCompositor() + 62 11 com.adobe.Backend.framework 0x000000010271b51e BE::CaptioningStreamsFromClip(ASL::InterfaceRef<BE::IClip, BE::IClip> const&, dvacore::utility::SmallBlockAllocator::vector<ASL::InterfaceRef<BE::ICaptioningStream, BE::ICaptioningStream> >&) + 542 12 com.adobe.Backend.framework 0x000000010271c561 BE::QueryAvailableCaptioningStreamFormats(ASL::InterfaceRef<BE::IMasterClip, BE::IMasterClip> const&, dvacore::utility::SmallBlockAllocator::set<dvacaptioning::StreamFormat, std::less<dvacaptioning::StreamFormat> >&) + 193 13 com.adobe.Backend.framework 0x000000010271d2d0 BE::QueryAvailableCaptioningStreamFormats(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, dvacore::utility::SmallBlockAllocator::set<dvacaptioning::StreamFormat, std::less<dvacaptioning::StreamFormat> >&) + 160 14 com.adobe.Mezzanine.framework 0x000000010879bb3a MZ::(anonymous namespace)::GetCaptionStreamLabels(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 106 15 com.adobe.Mezzanine.framework 0x00000001087a4b1f MZ::(anonymous namespace)::ProjectSource MZ::(anonymous namespace)::MakeSimpleProjectSource<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > >(MZ::(anonymous namespace)::SourceFnType<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > >::SimpleReadFn, MZ::(anonymous namespace)::SourceFnType<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > >::SimpleWriteFn)::SimpleProjectSourceImpl::Read(boost::function<bool (ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&)> const&, ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, dvacore::utility::ImmutableString const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 31 16 com.adobe.Mezzanine.framework 0x00000001087a464f MZ::(anonymous namespace)::ProjectSourceImpl<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > >::Read(boost::function<bool (ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, dvacore::utility::ImmutableString const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&)> const&, ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, __XMPMeta__*, dvametadata::Path const&) + 95 17 com.adobe.Mezzanine.framework 0x00000001087a47b4 MZ::(anonymous namespace)::ReadMetadataFromProject(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, __XMPMeta__*, dvametadata::Path const&) + 68 18 com.adobe.Mezzanine.framework 0x00000001087aaaad boost::_bi::bind_t<boost::_bi::unspecified, boost::_bi::bind_t<void, void (*)(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, __XMPMeta__*, dvametadata::Path const&), boost::_bi::list3<boost::_bi::value<ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> >, boost::_bi::value<__XMPMeta__*>, boost::arg<1> > >, boost::_bi::list1<boost::arg<1> > > std::for_each<adobe::poly<adobe::bidirectional_iter<dvametadata::Path, dvametadata::Path, long> >, boost::_bi::bind_t<boost::_bi::unspecified, boost::_bi::bind_t<void, void (*)(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, __XMPMeta__*, dvametadata::Path const&), boost::_bi::list3<boost::_bi::value<ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> >, boost::_bi::value<__XMPMeta__*>, boost::arg<1> > >, boost::_bi::list1<boost::arg<1> > > >(adobe::poly<adobe::bidirectional_iter<dvametadata::Path, dvametadata::Path, long> >, adobe::poly<adobe::bidirectional_iter<dvametadata::Path, dvametadata::Path, long> >, boost::_bi::bind_t<boost::_bi::unspecified, boost::_bi::bind_t<void, void (*)(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, __XMPMeta__*, dvametadata::Path const&), boost::_bi::list3<boost::_bi::value<ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> >, boost::_bi::value<__XMPMeta__*>, boost::arg<1> > >, boost::_bi::list1<boost::arg<1> > >) + 205 19 com.adobe.Mezzanine.framework 0x000000010879cfa1 MZ::(anonymous namespace)::CreateXMPForProjectItem(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, __XMPMeta__*) + 385 20 com.adobe.Mezzanine.framework 0x000000010879c924 MZ::ProjectMetaDataProvider::OnProjectItemsChanged(dvacore::utility::SmallBlockAllocator::vector<ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> > const&) + 116 21 com.adobe.Mezzanine.framework 0x000000010879c634 MZ::ProjectMetaDataProvider::ResetProjectItem(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, bool) + 420 22 com.adobe.Mezzanine.framework 0x00000001087a02ee MZ::MetaDataProvider::ResetProjectItem(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, bool) + 1134 23 com.adobe.Mezzanine.framework 0x000000010879fa46 MZ::MetaDataProvider::MetaDataProvider(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, bool) + 454 24 com.adobe.Mezzanine.framework 0x00000001087a117c MZ::CreateProvider(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, bool, MZ::ProviderType) + 92 25 com.adobe.Mezzanine.framework 0x0000000108789792 MZ::GetColumnValues(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> const&, std::vector<dvametadata::Path, std::allocator<dvametadata::Path> > const&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 98 26 com.adobe.Mezzanine.framework 0x0000000108787e8d boost::detail::function::void_function_obj_invoker2<boost::_bi::bind_t<void, boost::_mfi::mf2<void, MZ::MetadataCache, ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem>, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&>, boost::_bi::list3<boost::_bi::value<MZ::MetadataCache*>, boost::arg<1>, boost::arg<2> > >, void, ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem>, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&>::invoke(boost::detail::function::function_buffer&, ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem>, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 93 27 com.adobe.Mezzanine.framework 0x000000010878f6b5 boost::function2<void, ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem>, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&>::operator()(ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem>, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) const + 69 28 com.adobe.Mezzanine.framework 0x000000010878e4b5 MZ::MetadataCacheUpdateRequest::Process() + 341 29 com.adobe.dvacore.framework 0x000000010020eb32 dvacore::threads::(anonymous namespace)::SubExecutorImpl<dvacore::threads::ThreadSafeQueue<dvacore::threads::(anonymous namespace)::AllocatedFunctionWithSerialNumber> >::CallFunctionWithExceptionHandler(boost::function<void ()> const&) + 34 30 com.adobe.dvacore.framework 0x000000010020faa3 dvacore::threads::(anonymous namespace)::SubExecutorImpl<dvacore::threads::ThreadSafeQueue<dvacore::threads::(anonymous namespace)::AllocatedFunctionWithSerialNumber> >::OnThreadExecute(boost::shared_ptr<dvacore::threads::(anonymous namespace)::SubExecutorImpl<dvacore::threads::ThreadSafeQueue<dvacore::threads::(anonymous namespace)::AllocatedFunctionWithSerialNumber> > > const&) + 179 31 com.adobe.dvacore.framework 0x000000010022e8c4 dvacore::threads::WrapExecuteTopLevelFunction(void*) + 36 32 libdispatch.dylib 0x00007fffa53990b8 _dispatch_client_callout + 8 33 libdispatch.dylib 0x00007fffa539b029 _dispatch_root_queue_drain + 917 34 libdispatch.dylib 0x00007fffa539ac47 _dispatch_worker_thread3 + 99 35 libsystem_pthread.dylib 0x00007fffa55e6712 _pthread_wqthread + 1299 36 libsystem_pthread.dylib 0x00007fffa55e61ed start_wqthread + 13 Model: MacBookPro11,5, BootROM MBP114.0172.B10, 4 processors, Intel Core i7, 2.5 GHz, 16 GB, SMC 2.30f2 Graphics: AMD Radeon R9 M370X, AMD Radeon R9 M370X, PCIe, 2048 MB Graphics: Intel Iris Pro, Intel Iris Pro, Built-In Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), Broadcom BCM43xx 1.0 (7.21.171.68.1a4) Bluetooth: Version 5.0.2f4, 3 services, 27 devices, 1 incoming serial ports Network Service: Thunderbolt Ethernet Slot 2, Ethernet, en6 Network Service: Wi-Fi, AirPort, en0 Serial ATA Device: APPLE SSD SM0512G, 500.28 GB USB Device: USB 3.0 Bus USB Device: Apple Internal Keyboard / Trackpad USB Device: Bluetooth USB Host Controller Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1
... View more
AdChoices