[Michael O’reilly]

thanks for your response!

We did a test and if you have logged markers in the clip itself and put them in a sequence, when AutoDuck is used to export the sequence, the markers and the info are carried over the MC project file. (not sure if markers are placed in the sequence itself whether they carry over)

I still need to test this out, but I could conceivably make each bin into a sequence and export them via autoduck. Even if the editor can’t re-link the MXF files I create via resolve transcoding, he will still have that as a reference and can just import the files fresh.

Very clunky, but both are pretty fast! I feel like I just decoded some ancient text – great for me, but pretty much useless to anyone else!

Michael

[Michael O’reilly]

Ha ha – yes, and if I told you who I work for you’d be surprised that we go so long between upgrades.

The transcoding using Resolve route actually works quite well – since they were already organimized and the camera originals no longer exist this is the way I gotta go.

thanks for the response!

Michael

[Michael O’reilly]

thanks for your response.

I get what you mean about the y-split – i think we are saying the same thing.

However, the whole progressive/interlaced thing is where I think it is getting wonky – the monitor is at 1920×1080/60hz – which means the screen is being refreshed more often than a progressive signal – but monitors and frame rates are not the same thing.

Anyway, I think the easier thing would be to get the use to let me install something, like Camtasia.

I appreciate your input.

Michael

[Michael O’reilly]

Hello

I have the same problem where I have two HD monitors – I have the PP app on one and the other I am using as an HD monitor. I can get the 2nd monitor recognized as a full screen HD monitor, but when I come back (as the OP experiences) after a short absence, the 2nd monitor has reverted to an extension of the desktop. I can fix it by going into preferences and choosing it again in the playback. However, I’d like a keyboard command to do this

“1) You can assign a shortcut to toggle Mercury Transmit, which may make your ‘poking’ a little less click-intensive.”

Exactly what I want! However, it does not come up as a choice in the keyboard shortcut search.

Am I missing something?

thanks!

Michael

[Michael O’reilly]

thanks for your response. Getting back to this after a week vacation!

H.264 already transcoded to ProRes. Just two camera angles with a minimum number of cuts.

I shot some stuff with a gopro on this shoot to potentially use in other sequences, but not this one. So I should not have gopro files in the final dataset, but I do! and many other files that are not in this sequence.

maybe they will update this feature soon.

thanks !

Michael

[Michael O’reilly]

Thanks again for your response Alex.

I do understand what is going on under the hood (and I am doing the copy, that is a great suggestion).

I guess I was hoping for more of a concrete indication of what was happening, while I was in the app.

However, this did not work either – in fact the data set that I got from this one was BIGGER by a coupla GB than the other where I did not flatten it.

I’m stumped!

[Michael O’reilly]

thanks for your reply Alex

I see it thanks – it was not coming up in any searches within or outside of the application. I am not sure what it is doing, though as the only indication I am getting that ANYTHINg is happening is that the clips go from light green to light blue.

any other resources you can point me to?

I have version 9.2 or PP CC2015.2 release (which one do people go by ?)

[Michael O’reilly]

Looking for the exact same thing ! (Your description was not vague at all, not sure why the response was indicated as such). The suggestion for re-posting seems to be a good one – I will look there, but did you have any luck getting this question answered ?

Thanks – Mike O

[Michael O’reilly]

Herb, again thanks for your response. I think I got it figgered out this morning. The creation of the source and editing sequences was done with little regard to naming – it would have helped immensely if they had been changed when they were created, but I got them in line.

Did not know there was a keyboard manager – away from the editing computer currently, but will look into that tonight.

Best – Michael O

[Michael O’reilly]

Thanks for your response Herb. I had noticed the difference. I’ll just have to memorize the behavior – it doesn’t make absolute sense to me – double clicking the multicam sequence opens in the timeline, but you have to right click and explicitly tell the multicam source sequence to open in the timeline.

This person I mentioned that created the multicam source sequence and then the multicam sequences – they did not pay any mind to the names, so the original multi camera source sequences have longer names that were truncated on the creation of the multicam sequence. So I am not sure what source sequence refers to which multicam sequence. I guess I’ll just have to go through and try each one, unless there is an easier way.

2 other things I learned: make sure you don’t have the keyboard shortcuts loaded for FCP7 (they must’ve gotten switched somehow) and the numbers at the top of the keyboard are the only numbers that work to choose the current camera – the number pad does not seem to work.

thanks – Michael