Saturday, June 1, 2019

Re: [Avid-L2] Re: MC with New UI...?

 

Its not only Avid users.  Premiere only handles BRAW via a third party plugin. Not sure about their future plans.

On Sat, Jun 1, 2019 at 8:09 AM 'Job ter Burg (L2B)' Job_L2@terburg.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
 



On 31 May 2019, at 07:53, Pat Horridge pat@horridge.org.uk [Avid-L2] <Avid-L2@yahoogroups.com> wrote:

 I guess most folks are using Resolve to convert as BM intended. 

Well, BM does offer a free SDK for any third party to implement. Only Avid users will have to use Resolve or any of the other third-party applications to deal with the codec. Avid develops the RED AMA plug-in using the RED SDK. Avid developed the DPX AMA plug-in (seeing as it's an open format and not owned by anyone). 
 
Remember the XAVC-S codec where Avid users had to scramble to find other solutions? Avid finally added support as well as a third party charging $99. The same will most likely happen for BRAW, Avid users will end up paying to use it because a third party will develop it from the freely available SDK. 

No reason for BM to develop it. 

And why should Avid give more reason for anyone considering using Avid or already using Avid to use Resolve?

J

__._,_.___
Posted by: John Pale <pale.edit@gmail.com>
Reply via web post • Reply to sender • Reply to group • Start a New Topic • Messages in this topic (5)
this is the Avid-L2

SPONSORED LINKS
.

__,_._,___
Posted by Video Geek Squad at 8:16 AM 0 comments

Re: [Avid-L2] Re: MC with New UI...?

 



On 31 May 2019, at 07:53, Pat Horridge pat@horridge.org.uk [Avid-L2] <Avid-L2@yahoogroups.com> wrote:

 I guess most folks are using Resolve to convert as BM intended. 

Well, BM does offer a free SDK for any third party to implement. Only Avid users will have to use Resolve or any of the other third-party applications to deal with the codec. Avid develops the RED AMA plug-in using the RED SDK. Avid developed the DPX AMA plug-in (seeing as it's an open format and not owned by anyone). 
 
Remember the XAVC-S codec where Avid users had to scramble to find other solutions? Avid finally added support as well as a third party charging $99. The same will most likely happen for BRAW, Avid users will end up paying to use it because a third party will develop it from the freely available SDK. 

No reason for BM to develop it. 

And why should Avid give more reason for anyone considering using Avid or already using Avid to use Resolve?

J

__._,_.___
Posted by: "Job ter Burg (L2B)" <Job_L2@terburg.com>
Reply via web post • Reply to sender • Reply to group • Start a New Topic • Messages in this topic (4)
this is the Avid-L2

SPONSORED LINKS
.

__,_._,___
Posted by Video Geek Squad at 5:08 AM 0 comments

Thursday, May 30, 2019

[Avid-L2] Re: MC with New UI...?

 

The new UI release was postponed to ensure it was ready for end users.

As mentioned its down to camera supplies to use the Avid AMA plugin  sdk to produce plugins for new formats. I've heard no news on Avid working on that or any demand for it anywhere but this topic. I guess most folks are using Resolve to convert as BM intended.

Pat Horridge

__._,_.___
Posted by: Pat Horridge <pat@horridge.org.uk>
Reply via web post • Reply to sender • Reply to group • Start a New Topic • Messages in this topic (3)
this is the Avid-L2

SPONSORED LINKS
.

__,_._,___
Posted by Video Geek Squad at 10:53 PM 0 comments

[Avid-L2] Avid MC 2018.12.5 gives Project Format Error in 4K with NitrisDX?

 

At work I have an old NitrisDX circa 2009 it works fine with MC 2018.12.3 with a 4K DCI 4096_2160 Rec 709 Project but when I update to MC 2018.12.5 i get the following error launching the 4K project:
"Current hardware is not compatible with this project's settings and is being switched to to inactive."
I went back to 2018.12.3 and it was fine with the project and I then went back to 2018.12.5 assuring I checked NitrisDX to be installed but got the same error.  I'm not sure what the issue is I have a newer generation PCIe HIB that works fine with the DNxIO when I bring it in.
I get that Nitris DX doesn't support 4K but why isn't it acting like 2018.12.3 and just doing a down convert with no fuss?  I will try the same on my home system which has a newer NitrisDX circa 2012 and see if it gives the same error.
NitrisDX is not EOL yet and I didn't see it flash firmware like it use to but I haven't seen that for a while.  Is there a manual firmware flash in addition to the NitrisDX driver?  Oh they joy.

John Moore Barking Trout Productions Studio City, CA bigfish@pacbell.net

[Non-text portions of this message have been removed]

__._,_.___
Posted by: John Moore <bigfish@pacbell.net>
Reply via web post • Reply to sender • Reply to group • Start a New Topic • Messages in this topic (1)
this is the Avid-L2

SPONSORED LINKS
.

__,_._,___
Posted by Video Geek Squad at 5:55 PM 0 comments

[Avid-L2] Re: Timeline quality related to video mixdowns. 16 Bit

 

The timeline quality setting did matter 2-3 years ago, when I ran into this issue.


Video mixdowns done in green-10bit mode preserved my 10-bit footage, and mixdowns done in regular green mode were only 8-bit.  The truncation of the last 2-bits was observed on a scope in the second case.  

The timeline quality settings affected mixdowns only, not renders.

I don't know whether this is still the case a couple years later, and with 16-bit media. Worth testing.

Cheers,
--Michael Brockington

__._,_.___
Posted by: mbrockns2@yahoo.ca
Reply via web post • Reply to sender • Reply to group • Start a New Topic • Messages in this topic (3)
this is the Avid-L2

SPONSORED LINKS
.

__,_._,___
Posted by Video Geek Squad at 11:56 AM 0 comments

[Avid-L2] Re: Timeline quality related to video mixdowns. 16 Bit

 

There was a long thread approx. 9 months ago related to interaction of TimeLine settings and I think Terry C found it did effect mixdowns.  I never felt like we totally sussed it out in that thread IIRC Avid got involved.  My limited understanding is the upcoming Avid has a 16 bit pipeline to satisfy Netflix requirements.  I don't think that has been implemented in 2018.12.5.

Curious what computer you are running as I'm having some performance issues on my mid 2012 MacPro 12 Core and 2018.12.5.  It might be with all the 2018.12.X versions but his is the first time I've hammered on my home system since going to 2018.12.X.  I think my 2.66GHz is starting to become a limiting factor for 4K DCI and ProResHQ renders.  DNxHRHQX renders play much better.

Of course my computer is no longer qualified but I have to dance with the date I brought to the party for now.


---In Avid-L2@yahoogroups.com, <benfolts@...> wrote :

Hello All,  

I am running MC 2018.12.5 with an Avid Artist I/O.  We're starting to do some testing for a new show that is going to be an 4k HDR Dolbyvision delivery.

Client states the work pipeline must remain 4K and 16bit throughout finishing.

My quesiton is this:  Does the timeline quality setting matter if I am making mixdowns from the clips in the timeline that are 16 bit DNXUncompressed or any other 16 bit media?  I don't see an option under the timeline quality settings to do anything greater than 12 bit.  I have never been clear on if creating a mixdown even has anything to do with the TL quality setting, so I typically leave it at the highest setting when rendering or mixing down video.

I'd like to avoid creating lower quality mixdowns that has been downsampled from 16bit media. (assuming this even has anything to do with the mixdown media).  A little confused on this one so any explaination would be greatly appreciated.

 

Thanks,

 

Ben

__._,_.___
Posted by: bigfish@pacbell.net
Reply via web post • Reply to sender • Reply to group • Start a New Topic • Messages in this topic (2)
this is the Avid-L2

SPONSORED LINKS
.

__,_._,___
Posted by Video Geek Squad at 11:37 AM 0 comments
Subscribe to: Posts (Atom)