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

color correct camera inside multicam group causes crashing

New Here ,
Nov 11, 2022 Nov 11, 2022

Copy link to clipboard

Copied

mac big sur Pre Pro 22.2.0 hackintosh 64g ram radeon rx 6800xt 16g

 

clips are 1080  - h264 or h265

proxies created are h265 & were previously h264

a multicam group clips can be 2 hrs length

might have 5, 7 or 8 camera video tracks

multi cam will also include seperate camera audio tracks 

 which are muted except for the top audio channel which is a final mix wave file

 

for a half year easily, I've had the problem of crashing when inside multicam 

like a country song or such - I've been up down all around different app versions & mac versions

 

I open multicam (mc) in timeline & go to different cameras to adjust color
during this work, inconsistantly but eventually, this causes the app to crash

usually generating 1 of 3 reports; 

I do send the reports to adobe & I copy & save reports... generally reports are:

 

1.

Crashed Thread:        38

Exception Type:        EXC_BAD_ACCESS (SIGBUS)

Exception Codes:       KERN_PROTECTION_FAILURE at 0x0000000112474c60

Exception Note:        EXC_CORPSE_NOTIFY

 

Termination Signal:    Bus error: 10

Termination Reason:    Namespace SIGNAL, Code 0xa

Terminating Process:   exc handler [1129]

 

2.

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

 

Termination Signal:    Segmentation fault: 11

Termination Reason:    Namespace SIGNAL, Code 0xb

Terminating Process:   exc handler [6190]

 

VM Regions Near 0:

--> 

    __TEXT                      100000000-100008000    [   32K] r-x/r-x SM=COW  /Applications/Adobe Premiere Pro 2022/Adobe Premiere Pro 2022.app/Contents/MacOS/Adobe Premiere Pro 2022

 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

 

 

3rd.

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       EXC_I386_GPFLT

Exception Note:        EXC_CORPSE_NOTIFY

 

Termination Signal:    Segmentation fault: 11

Termination Reason:    Namespace SIGNAL, Code 0xb

Terminating Process:   exc handler [13177]

 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   com.adobe.HandlerProject.framework 0x0000000120b082ac HandlerProject::ProjectHandler::~ProjectHandler() + 732

 

 

also note:

There are usually 2 types of crashing out of app
A. when a window appears - 'a serious eeror has occured...'

this type of crash I can 'apple S' 

when I do that I see the File column flash

that tells me the project saved

when I press the error ok button app quits out

 

B. another crash out is just a hard flush - this app disappears suddenly closed
it might have been a long time since auto-save was backing up... in this crash I believe I might not get a crash-window, app is closed 

 

Attached are a few crash reports that are common

 

In my searching for clues for cause of problem I do not find much regarding color work inside a

multicam - 'open in timeline'


When doing this multi cam cc work one or two new projects a week 

with tech support as mentioned I have gone to different app version

gone into documents adobe folder with tech support creating fresh folders, tossing caches...

created - recreated keyboard layouts  - but can't shake the problem in this task I find essential because a clip in the multicam might have 7 or 8 color adjustment on each  camera video track in the multicam

 

I appreciate any assistance / guidance 

Mostly - I think the crash reports will show consistant issues -  permissions conflict & or other stuff

I don't know how to fully understand the reports 

 

TY

Gramps

TOPICS
Crash , Editing , Error or problem

Views

389

Likes

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
Adobe Employee ,
Nov 14, 2022 Nov 14, 2022

Copy link to clipboard

Copied

Hey Gramps,

Sorry for the frustrating crashes with your Multicam projects. I am not an engineer, but you can trace these kinds of crash reports back to faulty installations of the OS. Since you have a Hackintosh, that can be the root of many problems along these lines; sorry. Is it possible to check your workflow on a Mac?

 

My feeling is that your installation of macOS may not have all the components necessary for Adobe Creative Cloud apps to run smoothly. I would recommend updating macOS or reinstalling a more current version of the existing OS. 

 

Try using ProRes LT or similar proxies when cutting multiple video streams in a Multicam edit. Avoid H.264 proxies while troubleshooting. 

 

Thanks,
Kevin

Likes

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
New Here ,
Nov 15, 2022 Nov 15, 2022

Copy link to clipboard

Copied

Much appreciate Kevin,
I will try to get back on my m1 imac to see if color group issue occurs;
i need to do that at the right time when it's convient for my significant other...

That Imac had crashes - at moment I can't remember if it was during the multi cam cc work?

it is possible, and the reports look similar to many of the current reports

- though i can't say I actually understand most of what the report is showing

I've attached some of the saved IMAC reports

 

i guess this might be an mpeg issue??
It is strange to me that I can make it happen in this synerio - cc in multicam,
but not in other tasks - I notice reports are sometimes a permissions conflict

 

I have 2 weekly gigs at about 300gigs to download of h264/h265 every 7 days
I know QT pro res is general best for quality & stable workflow 
the multicam projects (about 2oo gig)  has some budget challenges

regarding storage space & I worry about the time they'd need for uploading the shot prores footage/

& I haven't even imagined the extra time it would take to upres the shot ftg to qt prores, though thinking now what if started with making proxy as QT PR low Res... it wouldn't take as much storage space, I need to make proxies anyway... just that on this remote job, per request, I've been keeping their footage since a year ago;

h265 I've kinda grown fond of...
ok on next week's multicam project I will make low res pro res - perhaps link to them as masterclips then relink back to mpeg once edit is done ...

Alrighty, thank you for guidence in my effort to trouble shoot this issue I am having!

- Gr (aka - Paul)

Likes

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
Adobe Employee ,
Nov 17, 2022 Nov 17, 2022

Copy link to clipboard

Copied

Still having trouble, Gramps? Let me know.

 

Thanks,
Kevin

Likes

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
New Here ,
Nov 21, 2022 Nov 21, 2022

Copy link to clipboard

Copied

LATEST
Hello,
Over the weekend the problem continued regarding multicam cc (color
correct) work

With this weeks new project I guess my plan is to make proxies in low res
prores to see if there is improvement regarding crashes


>From a previous call to customer support, before posting here, I got a
follow up from them last week to check two articles that although the issue
was with different apps - the reports re: problem of crashing out of app
showed similar messages... messages I was getting when app closed always
seemed to be -

*Exception Type: EXC_BAD_ACCESS (SIGBUS)*

*Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000112474c60*


*Termination Signal: Bus error: 10*

also got code

*Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000*

*Termination Signal: Segmentation fault: 11*

VM Regions Near 0:

__TEXT 100000000-100008000 [ 32K] r-x/r-x
SM=COW /Applications/Adobe
Premiere

*as well as*

*Exception Type: EXC_BAD_ACCESS (SIGSEGV)*

*Exception Codes: EXC_I386_GPFLT*

*Exception Note: EXC_CORPSE_NOTIFY*

*Termination Signal: Segmentation fault: 11*


I believe the advice recommended was to go into system preferences,
security/privacy, accessibility &then give permission / control access to
Premiere Pro app
here are the references they sent regarding this issue:
https://community.adobe
.com/t5/photoshop-ecosystem-discussions/photoshop-crashed-exception-type-exc-bad-access-sigsegv/m-p/10234097
https://community.adobe
.com/t5/photoshop-ecosystem-discussions/photoshop-won-t-open-exc-bad-access-sigsegv/td-p/10223856

I did this correctly, I believe, yet the issue of app crash continued
1. sometimes the 'crash' is premiere pro suddenly quitting and No
problem/crash report - though at times there is the feel that the system is
becoming sluggish (sometimes there are little indicatiors like this but not
always)
2. crash happens where app freezes a little message appears that a problem
has happened I believe the alert says something like restart app... When
this occurs I can usually press
'Apple S' with these crashes I will then see at top of screen the file
column flash black in response to 'apple s' press I will, i believe it goes
that, after 'apple S'
I click the 'ok' button on the alert window that says i need to relaunch
app. the frozen app closes a kind of crash report, like the 3 types listed
above will appear after the app closes...
3. crash type is a full system crash & need to do a force restart of
computer there could be a crash/panic report when system relaunches but it
looks more in response to the forced close & restart

I think there are a variety of crash types & i am probably not mentioning
some of the variations.
I also want to mention again that I was having crash issues with my m1 imac
at moment the reports look the same as what i am currently dealing with,
also I open from the auto-save generated when i was on the imac - I have a
few crashes I save reports for - anyway I open the auto save and see the
crash occured on projects with similar set work the auto saves were from 7
minutes apart - I go into the before crash & after crash which was created
after the crash event & generate report - so back then there was a
relaunching of the app & continued working - I think the crash
occured around multicam color work when I launch the 2 autosaved projects
in both projects there are two timeline tabs
one tab is the multicam opened on timeline & the other tab is the sequence
where I am building 'the cut'
'the cut' sequence is the one showing of the two tabs in timeline
when I click over to the multicam in both autosaved projects the blue
vertical indication line where currently on the timeline is in different
spots - meaning between the 7 minute autosaves the blue cursor on the
opened multicam is in a different spot meaning I was probably working on
the multicam color correction work when i was having the crash problem
while working on the m1 imac
before the imac for a month or so I worked on one of those new mac minis
(ibelieve is was an m1 chip ) after the problem was occuring on both those
systems I went back to an upgraded hackintosh on big sur, new Radeon RX
6800 XT graphics card & 64 gig ram yet the problem continued
I've moved media to solid state drives & still that work caused crashes on
the multicam projects that followed

I get hackintosh can be contributing to the crashes & until i have time to
again migrate to a strong regular mac to see if the problem with my routine
occurs there too - well
for now the next step i can do is create proxies as lo res pro res
quicktimes with the aim to uses those clips as the masterclips for the
duration of edit by this point I'm expecting this could be happening cus of
h264 &265 master clips
I hope to give an update about that effort later this week
sorry for this lengthy update, neverless, I hope to send an update asap
(pardon my typos & such)
back to work I must
Thank you
Gramps

multicam is open on the timeline as well as the sequence I was cutting is
the tab showing when the projects open
--
Paul Heiman
310.480.1106
888pgh@gmail.com

Likes

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