Here's a quick find from googling
MXF/ARRIRAW compatibility with post tools
ALEXA Mini's software SUP 4.0 has enabled in-camera ARRIRAW recording as a *.mxf-wrapped file. That's a new style of ARRIRAW - but still uncompressed and unencrypted. The big difference is the wrapper: MXF/ARRIRAW is single ARRIRAW frames within a MXF container.
By 4/2016 there are only three tools out now supporting MXF/ARRIRAW:
I hope to expand that list soon!
Jan
By 4/2016 there are only three tools out now supporting MXF/ARRIRAW:
- ARRIRAW Converter - ARRI's free reference tool for ARRIRAW processing
I hope to expand that list soon!
Jan
Jan Heugel
Application Engineer
Application Engineer
- Jan Heugel
- Posts: 267
- Joined: Wed Aug 13, 2014 3:15 pm
- Location: Munich, Germany
Re: MXF/ARRIRAW compatibility with post tools
Maybe time to post a link to the worfklow section of the ALEXA Mini web site:
https://www.arri.com/camera/alexa_mini/ ... _workflow/
This site will be constantly updated!
https://www.arri.com/camera/alexa_mini/ ... _workflow/
This site will be constantly updated!
- Michael Jonas
- Posts: 20
- Joined: Thu Mar 26, 2015 3:28 pm
---In Avid-L2@yahoogroups.com, <bigfish@...> wrote :
Thanks for the suggestion. Fortunately Resolve 15 beta 2 did the job. I have a mid 2012 MacPro 12 Core 2.66GHz with a GTX-680 in the tower and 2 TitanX GPUs in a Cyclone Microsysystems Expansion Chassis.
At the recent BlackMagic Editor's Lounge event it came up that if you check the box in Resolve to allow the GUI GPU to aid in computations when there are multiple GPUs it might slow down a faster expansion GPU to the pace of the slower GPU. The example sighted was a system with and expansion chassis on a MacPro Cheese Grater with with 2 GTX-680 cards. When the 2nd GTX-680 was replaced with a 1080, or whatever that model is not a TitanX but something 1080 there was no noticeable increase in render speed. The BlackMagic Presenter suggested that because the GUI GPU was slower than the new GPU that perhaps it dragged the newer GPU performance down to match it's slow level. The suggestion was to not have the GUI 680 be involved in the computations. I wonder if anyone really knows if this is true.
The reason I mention all this is when I brought these 3K Arri Raw files into Resolve 15 b2 on my home system I turned off the GTX-680 for computation just in case. I was getting about 16 to 18 frames per second processed going from Arri Raw 2880x1620 source to MXF Op Atom DNxHR HQX 10 bit. I can playback at 23.976 from a Mercury Elite Pro USB 3 drive which gets approx 140 Mbps according to blackmagic disk speed test. The playback does stall along the way. As a test I'm going to copy the Camera Neg Arri Raw to my internal 3 strip raid where the BM Speed test for the first partition is 450 Mbps and the the third Partition clocks at 350 Mbps. I believe my 4 partitions on the 3 strip raid start on outside to inside given the 2st is the fastest and they slow down with each of the other 3 partitions. I built the raid taking Hitachi Deskstar 4TB drives and partitioning each with 4 partitions then combining each of the corresponding partitions 1st through 4th in a 3 way stripe. I'll be curious to see how the camera raw plays of the fastest internal.
I'm use to looking at Activity Monitor to see core usage during various processes. Is there a way to monitor the usage of the GPUs? Just want to see if there is a way to quantify how Resolve is utilizing the TitanX GPUs in the expansion chassis.
As far as the Arri Raw Converter I did end up using it on one problem clip that would not show up in Resolve. The file could be seen in the finder but wouldn't be listed in Resolve. After contacting the DIT he said he had the same problem and was able to use Silverstack to process it for making ProRes LT files. The camera had run out of power during the problem clip and didn't get wrapped properly. The Arri Raw Converter however played it and I transcoded to ProRes 4444 and then that worked in Resolve. I guess the Arri Raw Converter is more forgiving with whatever the error was caused by the camera losing power mid take.
I assume that the Arri Mini will only create Arri Raw to a .mxf file format but I don't know this for sure. Oh boy more googling.
---In Avid-L2@yahoogroups.com, <bogdan_grigorescu@...> wrote :
From: "John Moore bigfish@... [Avid-L2]" <Avid-L2@yahoogroups.com>
To: Yahoogroups <avid-l2@yahoogroups.com>; Yahoogroups <editing-list@yahoogroups.com>
Sent: Friday, May 11, 2018 7:21 PM
Subject: [Avid-L2] Arri Raw into Avid What is going on?
At the recent BlackMagic Editor's Lounge event it came up that if you check the box in Resolve to allow the GUI GPU to aid in computations when there are multiple GPUs it might slow down a faster expansion GPU to the pace of the slower GPU. The example sighted was a system with and expansion chassis on a MacPro Cheese Grater with with 2 GTX-680 cards. When the 2nd GTX-680 was replaced with a 1080, or whatever that model is not a TitanX but something 1080 there was no noticeable increase in render speed. The BlackMagic Presenter suggested that because the GUI GPU was slower than the new GPU that perhaps it dragged the newer GPU performance down to match it's slow level. The suggestion was to not have the GUI 680 be involved in the computations. I wonder if anyone really knows if this is true.
The reason I mention all this is when I brought these 3K Arri Raw files into Resolve 15 b2 on my home system I turned off the GTX-680 for computation just in case. I was getting about 16 to 18 frames per second processed going from Arri Raw 2880x1620 source to MXF Op Atom DNxHR HQX 10 bit. I can playback at 23.976 from a Mercury Elite Pro USB 3 drive which gets approx 140 Mbps according to blackmagic disk speed test. The playback does stall along the way. As a test I'm going to copy the Camera Neg Arri Raw to my internal 3 strip raid where the BM Speed test for the first partition is 450 Mbps and the the third Partition clocks at 350 Mbps. I believe my 4 partitions on the 3 strip raid start on outside to inside given the 2st is the fastest and they slow down with each of the other 3 partitions. I built the raid taking Hitachi Deskstar 4TB drives and partitioning each with 4 partitions then combining each of the corresponding partitions 1st through 4th in a 3 way stripe. I'll be curious to see how the camera raw plays of the fastest internal.
I'm use to looking at Activity Monitor to see core usage during various processes. Is there a way to monitor the usage of the GPUs? Just want to see if there is a way to quantify how Resolve is utilizing the TitanX GPUs in the expansion chassis.
As far as the Arri Raw Converter I did end up using it on one problem clip that would not show up in Resolve. The file could be seen in the finder but wouldn't be listed in Resolve. After contacting the DIT he said he had the same problem and was able to use Silverstack to process it for making ProRes LT files. The camera had run out of power during the problem clip and didn't get wrapped properly. The Arri Raw Converter however played it and I transcoded to ProRes 4444 and then that worked in Resolve. I guess the Arri Raw Converter is more forgiving with whatever the error was caused by the camera losing power mid take.
I assume that the Arri Mini will only create Arri Raw to a .mxf file format but I don't know this for sure. Oh boy more googling.
---In Avid-L2@yahoogroups.com, <bogdan_grigorescu@...> wrote :
|
be aware that this is computational intensive, don't think you'll get more than 3-6FPS transcoding speeds
BG
www.finale.tv
From: "John Moore bigfish@... [Avid-L2]" <Avid-L2@yahoogroups.com>
To: Yahoogroups <avid-l2@yahoogroups.com>; Yahoogroups <editing-list@yahoogroups.com>
Sent: Friday, May 11, 2018 7:21 PM
Subject: [Avid-L2] Arri Raw into Avid What is going on?
Here is the metadata from a clip report:
Size 1.25 TB
Duration 2:03:57 h
Files 107
Input ARRI
FPS 23.98
Resolution 2880x1620
Type Mxf
Codec ARRIRAW
I can not ama link to these .mxf files in Avid 8_9_4. I tried installing the old Arri DNxHD mxf plugin but it is not longer compatible and now that I see what the media is it wouldn't work anyways. It seems I need Glue tools or to use Resolve to do the transcode. I tried to bring a clip into Resolve 11.3.1 but it wouldn't even show me the clips. I could see the folder but clicking on it shows nothing. I can't upgrade the Resolve due to Mac OS limits. I'm going to take the media home to my Resolve 15 beta system and see if it works there.
Some googling by my AE suggested Glue Tools ama plugin which seems to be 500 bucks or to use Resolve. His search suggested Resolve 12 or higher. I'm surprised I don't even see the mxf clips show up in Resolve 11.3.1 but given what my AE found perhaps that is par for the course.
Of course the shoot the day before was to prores and worked fine so today they shoot in a completely different format. WTF?
Any suggestions welcomed. Time to go borrow Bob Zelin's tool for fixing these situations!!! A nice pump action tweaker is in order here.
John Moore Barking Trout Productions Studio City, CA bigfish@...
__._,_.___
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
this is the Avid-L2
.
__,_._,___
No comments:
Post a Comment