AdminBruce Bullis (Adobe)
(Admin, Adobe DVA)
My feedback
-
1 vote
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment 1 Playback, after reverse, seems to work fine here. Can you provide any details that might help us reproduce the problem?
2 Is that the only step required to generate the "not responding" behavior?
-
1 vote
An error occurred while saving the comment What were you trying to accomplish, by changing the original media's frame rate, _after_ making the proxy?
-
8 votes
An error occurred while saving the comment From the team that built Productions:
You can make a label color change in the source project and whatever the label color is in the source project will be the same when you drag it into the timeline. But the connection is broken from that point onward, so if you change the label in the source project, it won’t update the timeline project; you can only update the label color in the timeline project (right click the clip in the timeline and change label).
If you right click on a clip in the timeline and select rename, it will open the source project and highlight the text field of the clip in the project panel. You can rename it from there, as long as you have read-write access, and it should update the projects you have opened that are in read/write mode.
-
1 vote
An error occurred while saving the comment Confirming: You're using the PPro beta, and not the official PPro 14.3.2x42 release, yes?
-
5 votes
An error occurred while saving the comment Not every user wants to 'just merge everything', but it'd make a nice preference...
-
3 votes
An error occurred while saving the comment Your description gives us no idea what to fix.
What changed about your system configuration, 3 weeks ago?
You say memory is overflowing; what, specifically, were you doing in PPro, when memory was leaked?
-
1 vote
An error occurred while saving the comment We've considered this in the past, and test user input has steered us way from doing so; file movement performed by others could then alter your project, without the creator's intent/knowledge.
Still, some third party CEP panel integration does exactly that, for the storage it provides...
-
1 vote
An error occurred while saving the comment Works here, on mac and windows. Did you change the default?
-
2 votes
An error occurred while saving the comment "Make a Copy" was added for just that purpose.
-
5 votes
An error occurred while saving the comment We're tracking this issue as DVAPR-4224119: "When project is sorted by 'User Sort', using File --> Import to bring in files adds them in random order; if dragged in, new imports are alphabetized"
-
2 votes
An error occurred while saving the comment That behavior makes it sound like a drive/volume is becoming unavailable, and/or "going to sleep"...
Are you using an external hard drive?
-
2 votes
An error occurred while saving the comment Do all the .jpg files have the same image dimensions?
We're having trouble understanding 'shows all the images as if they were the same image than the first JPG'; do you mean all frames of the image sequence show the first jpg?
-
5 votes
An error occurred while saving the comment XAVC MXF uses GPU hardware.
Specifically, what codec(s) are you hoping we'd accelerate further?
-
1 vote
An error occurred while saving the comment Given that AME exists, it's unlikely that we'd add another render queue within PPro.
AME and PPro rely on the same rendering code; perhaps you could provide specifics about the inconsistencies you've found? Can you reliably reproduce the 'messes up the image' behavior? Happy to help further, provided actionable specifics...
-
10 votes
An error occurred while saving the comment Dynamic Link is used daily in demanding professional workflows. Let's see whether we can get it to work, for you.
Do you have the current versions of both PPro and AE installed? Specifically, which folder are you deleting? Do you get any different (hopefully, better) behavior, when using the auto-saved versions of the projects, open during the crash?
Restarting your OS after a crash = great idea.
-
2 votes
An error occurred while saving the comment PPro works with 10.15.4; did something else change on your system, between now and the last time you successfully ran PPro? From what OS X version, did you upgrade to 10.15.4? The snippet above isn't much to go on, but perhaps there's a permissions issue; that's what makes me wonder whether the OS upgrade didn't necessitate (re-)giving PPro appropriate 'security clearance'...
-
93 votes
An error occurred while saving the comment Adobe is aware of the issue, have identified some anomalies in the timecode info provided for the media, and are working with Autokroma to better understand the issue.
-
2 votes
An error occurred while saving the comment If PPro _didn't_ honor the mute state on export, users would need to actually delete unwanted tracks, before export. Honoring the Mute button seems preferable.
-
1 vote
An error occurred while saving the comment setValue() works fine in PPro 14.x ("2020"), if New World isn't on; it fails, even in PPro 13.x ("2019"), if New World is on.
We're tracking this issue as DVAPR-4220968; I'll update the SDK Forum, and this thread, with our progress.
.mov is a file format wrapper, which can contain a broad(!) variety of different essence formats.
What codec was used, to encode the media within those .mov files?