![]() Please feel free to add and edit pages, and list requests in this thread. We prefer public domain or Creative Commons. Want to give away your music or footage: State the copyright.Having a problem: Be specific about your setup, software and footage.If you want to post a job, we expect you to quote some sort of pay - hourly, daily, weekly etc.No posting of your services, or that you're looking for work.This is a subreddit for people who make their living in the field (or are trying to.) If you want to know what software to use.go to /r/VideoEditing.Then be specific about the type of feedback you want. Feedback: do it somewhere other than facebook or YouTube.Imagine someone else is having a bad day. Generally we're not a place for you to advertise your work, and we expect everyone to be civil and generally not act like a jerk. Just last night i had my render machine rendering a final output for one episode of a series, while i was grading the next episode on my workstation.For people that get paid to edit film, video, television, etc. ![]() One other big advantage to the remote render box is that it can run in the background. My remote render "box" is actually a VMware image with a GTX980, and its fantastic - but before that I was running it on a 15" retina macbook, and for straight prores encoding it was still really quick - it just bogged down doing handles on clips with noise reduction. you can't really cache handles so your remote render box will have to process those, so it does help to have a decently powerful mac if you need to render with handles. The mac has no problem reading caches from the windows box - so its really just doing the prores encode, and theres never a need to make a set of intermediate files. Yes you need a shared database and 2 dongles, but once you have everything setup correctly (including mapping mounts on both resolve systems so paths can be interchanged) - it really is completely seamless. please share because lately I generate a lot of Prores files and im trying to streamline this process as much as possible.Ĭlick to expand.This is pretty much exactly how I deliver prores and it works perfectly. If someone has set up some automated workflow for Prores from "PC Resolve". I was thinking of going with another Resolve licence and using Resolve's own remote render functionality for prores (no need for converting and generating double the amount of files) but this works quite well so probalby will be sticking with this workflow for a while. Im sure there are other conversion apps out there that do this better - or worse for that matter. It seems to use multiple cores on the CPU side becasue its doing this simultanousely. (i noticed lately that some clients want to watch prevs through youtube). ![]() So if I renderout an MXF into my watch folder - media encoder will take the file automaticaly and convert it to lets say Prores 422 and then to H264 with high bitrate and resolusion, and lets say h264 720p with lower bitrate for youtube previews. It can also be set up to convert to diferent formats at the same time. Media encoder on the mac side then takes whatever file ends up in the folder and converts it automatically to specified format (in my case Prores422) and then puts the files in respective folders (witch can also be specified). I'm exporting MXFop1 files (DNxHD) out of Resolve into specified folder. All you have to do is set up folders for media encoder to monitor. This is for People who Work on PC but have a "spare" mac in their studio.Īdobe media encoder has a "watch folder" funcionality witch is quite handy. Recently i have set up a Prores conversion workflow that seems to work quite well for me so far - so i want to share a little.
0 Comments
Leave a Reply. |