Roles and Subroles do not show up in X2PRO

Hey Daniel - yes that is the same FCPXML file. However, I did resolve this issue a long time ago simply by using 'current version' from FCPX as well as "Audio" (not Extended) when exporting a new file. This seemed to work. The other extended export did not read roles correctly.

Side note: I wish the naming structure was the same as FCPX when converting. Capitalization, spaces, etc. When bringing into Logic-X, for example, a lot of the track names had some extra information in them and missing 1 or 2 words from the original Role Name. I don't know if this is a known issue or not - just speaking from an organizational stand point in working with teams in post production. Having put in the effort of properly naming everything in FCPX, I was hoping that would transfer properly into Logic-X using X2Pro.

Cheers!

Hi Stephen,

We are slightly confused because when we look at your XML in the current release (4.0.29) and the future release (4.0.32) we can clearly see 9 roles compared to the 6 that you are able to see. Please see the attached image, can you confirm that we are using the same FCPXML.

Thanks,

Daniel

Dear Stephen

I have sent you a private mail, we have raised this as ticket 7523, we should support roles and subroles.

Yours sincerely

James

Quick update: I've tried exporting from FCPX as with "latest version" as well as Audio export with XML drop down options, and it seemed to be able to read most of the roles with this. Not all, and some were labelled really differently than what I had assigned within FCPX but it's better than nothing!

I'm experiencing this same issue with missing roles, trying to go from FCPX to Logic-X using X2Pro. All latest versions. Attached XML and screenshot from FCPX and X2Pro for reference & comparison. Moving into post-audio this week so we need to have roles resolved as possible to hit our deadline. Thanks!

Dear Dan, Ase and Maarten,

We have just released 4.0.17, can you please retry as this should resolve the issue.

Yours sincerely

James

The next version will probably contain the fix but if not, the version after that will. It has gone though development already, but not gone through QA/Test yet. After that it also will need to be approved by Apple before it can be put in the app store.

Thanks, Graeme! That helps. Do you know when this bug will get fixed?

Maarten,

There is a bug in X2Pro where clips that are on a secondary storyline inherit the audio configuration from the clip that the secondary storyline is connected to.

All the clips with "Voois Over" assigned as their role are on two secondary storylines that are both attached to the first clip in your sequence. That first clip has had audio channels 1, 2, 5 & 6 disabled and the bug in X2Pro means that the clips on the secondary storylines have also inherited this. Since they only have 1 channel, the whole clip has been disabled.

You can work around this bey changing what clip the secondary storylines that contain the vo clips are attached to. For example CMD+OPT+Click on the secondary storylines at 2:12 to attach them to the second clip in the primary storyline.

Attached the fcp xml file. Missing role is 'voois over' (voice over).

Thanks!

Please attach your fcpxml and tell us what clips and roles are missing.

Hi,

I've got this issue as well. I've made a role 'voice over' and subroles for each language. This role and its subroles won't show up in X2pro. Renaming / reassigning / new roles - nothing helps.

I'm using FCP X 10.3.2 / MacOS 10.12.3 / X2Pro 4.0.12.

Please advise,

Kind regards

The last we heard from you, you explained that you had a workaround but ot a solution to the missing roles problem.
We haven't seen a response to Graeme's post below and I wanted to follow up with you.
Do you have problems with both 1.5 and 1.6 XMLs still?

Please let us know.

If you get all the roles, but an error when using the v1.6 fcpxml, perhaps we should look into that. Can you try removing the clip called "018_0005" from your project and try converting a 1.6 fcpxml again?

I'm afraid we're still trying to get to the bottom of this. We are still investigating