Danny Phillips
Forum Replies Created
-
Hey Ken,
No, this will be my first project with native c300. I’ve done a few very simple tests that went without issue (of course) and was looking to ingest with Prelude… Don’t know if maybe that’s a more robust way to build the database or not (actually just looking to learn prelude).
How are you ingesting your media?
Cheers,
danny -
Hi Ken,
Sorry I don’t have any advice directly but I’m very interested in any replies as I have a rather large c300 project starting in a few days (10 x 30 min. episodic). I was hoping to NOT transcode and cut native as it would kill time budget to transcode… Have you found this issue sporadically or more of a constant problem?
Cheers,
danny -
Hi Tim,
Thanks so much for your input…
In the past, a rough cut was handed over to me and I took it to finish so it made sense to have a prores workflow, but I was hoping to stay with the .mxf files at least through the edit – So your advice is exactly what I was hoping for.
Another question… how would you deal with file names i.e. CU, 2shot, MCU etc. would you just use the ‘Comments’ or ‘Description’ field in the NLE and move that field over to the extreme left so that it sits next to the shot in list view – or I suppose with the Thumbnail view this becomes less important. And what about media management in the RAID itself… Makes searching for individual shot from say… episode 4, scene 32, shot 7, take 2 – kinda tricky…
Again, thanks so much for your time.
Cheers,
danny
Melbourne -
Hi David,
Sorry for the late reply… I have found that just turning of Mercury GPU playback in favour of software has helped, mostly clearing up my issues. However, it would be lovely to get back openCL boost from these dual D700 cards in Adobe suite.
I didn’t find that I needed to wipe prefs or trash anything, just turned off Mercury.
So, are you hinting that the 10.9.4 update has some fixes..?
Thanks for your previous responses,
cheers,
danny -
Hi David,
That might be an idea for export but I’m having issues in editorial. I’ve disengaged ‘GPU’ mercury playback in favour of ‘software’ and that seems to have helped quite a bit. I wonder, is it just these D-series GPUs in the new Mac Pro that are causing problems? …i.e. just driver support in 10.9.3?
Cheers,
danny -
Hi Kevin,
I’ve got these issues as well – Very frustrating… Premiere keeps locking up and/or “Serious Error” shutdown along with the digital pink/green visual tearing/distortion. have not exported yet, only in playback so far. Third the way through 10 episode series for broadcast… Hoping help is on the way..!
Specs –
Mac Model: MacPro 6,1
Memory: 16 GB
GPU: D700
Premiere Pro version: CC 7.2.2
Storage – local vs network: Areca 8052TB2
3rd party IO?: BMD Monitor Mini
Dual monitor GPU?: Yes
3rd party plug-ins loaded?: Red Giant
Type of footage?: ProRes 422HQWhere a-bouts would I find the crash log?
Cheers,
danny Phillips
Melbourne, Aus. -
Hi Marc,
Yeah, sometime you find out the hard way… My workflow till recently has been FCP 7 to Color, Color doesn’t really care what’s in the filename… I just got caught out.
Cheers,
danny -
Hi Anna,
For me the problem is the “/” (forward slash) character in my clip filenames. Resolve doesn’t recognize this character and changes it to “:”, which it also cannot recognize, I’m not why it chages it to another unusable character? As Rohit mentioned both of those characters are used in a different capacity and not allowed. I did overcome this by deselecting “Use source filename” in the render window settings and it just makes a self contained movie. Just dropped that into my timeline and good to go.
danny
p.s. Thanks Rohit, got it going.
-
It seems that R9 doesn’t like anything in the file name other than 0-9, letters and underscores. I had “/” and it got changed to”:” in the media pool, by mac os I believe… anyhow… I’m now in a world of PAIN!
danny
-
Hi,
I’m having exactly the same issue. Waiting for DaVinci support to get back to me but if anyone else can chime in that would be great!
Cheers,
danny