Sunday, June 12, 2016

[Avid-L2] Re: _bg.1 folder

 

In my experience it remains.  I'm pretty sure that avid will not rebuild the media database with the folder named _bg.1.  That is if you go in a delete the media database it will not rebuild IIRC.  However if you do another background render it will add to that existing _bg.1 and not create a _bg.2 etc...  At that point Avid must rebuild/modify the existing media database somehow.  So while it can be updated it doesn't then act like a normal subfolder and if you want to manually rebuild the database you have to rename it to a more standard number then it rebuilds.  I've not had a problem just leaving them as _bg1.  In some ways it helps me know where my transcoded media is.  Background rendering also goes into that folder but beware if you are using LUTs there is a bug with background rendering and it will render posterized garbage.  This has been confirmed with Avid support.  Not sure if it is LUT or number of LUTs dependent but in my case with a Panny VLog LUT followed by a Full Range to Legal LUT it background renderered crap.  A normal render worked fine so beware of that.



---In avid-l2@yahoogroups.com, <danlist@...> wrote :

Working in 8.5.2 I believe background transcoding or rendering creates
the _bg.1 folder.

Does it normally disappear after a job and media files move into
numbered folders? If it remains, should I clean it up by moving the
files into a numbered folder? Anything special in that folder or is it
just the default location for background created media?

Thanks

__._,_.___

Posted by: bigfish@pacbell.net
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (2)

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