Jamie Worsfold
Forum Replies Created
-
D’oh! Yes – 24 bit, of course!
OK – I’ll have a search on Blackmagic forums. THanks!
-
Hi Michael
Thanks for the reply!
At present, the audio is being monitored just via the Mac audio. I don’t think that is the issue, though as all other audio is playing out fine. The MXf files sometimes seem to play back fine if they have already been played, but if I then play another part of the timeline then they are silent again when I go back to them – which seems like a cache issue, maybe?
It’s 10-bit 48khz Linear PCM, and recording the full 8 tracks as per usual with Sony.
Tried muting the other six audio tracks that are mute and that hasn’t fixd it.
Another of our editors is also experiencing the same issue – he’s running Resolve on an iMac. Once again, audio from any other files is not a problem, it’s just the MXF files. -
Thanks!
I was actually just about to come back on here and reply to myself that I’d figured out Color Trace. -
Nope. The CC app is still flakey and will come and go randomly.
-
As I thought. Yeah – bit of a pain.
Usually I’d find out what the edit is being done on but a bit of a funny one this; hopefully we’ll be doing the post (in which case everything is organised) but it *may* go elsewhere. So was just trying to make it as easy as poss for someone cutting on Avid. But it looks like anyone else may have to do all their own organising if so (using – of course – my own very well organised log notes!).
Thanks.
-
Yeah, I’ve managed to pull all the files into Avid using AMA. No problem there. Just keeping that bin structure would have been nice to keep it tidy…!
-
Yep. Getting problems a lot.
Had CC disappear this week from the edit suite at work and spent the whole day trying to fix it. Tech support couldn’t help.Now had the exact same thing happen this morning on my home edit suite. Can’t open Photoshop or Illustrator. The CC desktop app doesn’t work. Can’t re-install it as the installer doesn’t initialize.
These are working from two different Adobe IDs The one at work and my personal one at home.
I was getting similar problems over a year ago with AAM when running Creative Cloud with CS6. It’s turning into one big not-very-funny joke.
Adobe: pull your fingers out and get these issues sorted. If you’re going to charge people a subscription then you can’t expect them to turn on their computer every day and be wondering if the software is going to work or not.
-
Strangely, some of the scaling does come through but not all.
For example, I have a few shots in the timeline which I have a slow zoom in on. These work fine. And I think these are set as ‘Scale to Frame’.
It seems to be on r3d 4K footage which has been left at 100% in Premiere where the sizing is not working. It defaults to being scaled to 1080.
I think as a quick workaround for those particular shots I’ll just resize in Resolve.
I’m also now thinking that this isn’t a Resolve issue. I imported the XML that Premiere created into FCP and got a similar issue. So it must be a Premiere thing.
-
But it isn’t distorting. It is just not recognising the sizing information from the XML.
Surely if I have done an edit in Premiere in a 1920×1080 timeline and send the XML of that to DaVinci then a 1920×1080 timeline in DaVinci should look the same?
I have two seperate edits: One for the left screen and one for the right screen. Both of these are 1920×1080 and are independent of one another.
-
Nope. It’s a 1920×1080 sequence in Premiere.