Quantcast
Channel: Avid Community
Viewing all 30354 articles
Browse latest View live

Media Composer 2018.1 a 2018.12 | Disponibles

$
0
0

1.    Nuevo esquema de control de versiones

Avid se complace en anunciar la introducción de un nuevo esquema de versiones de software basado en fechas. Este esquema de control de versiones comenzará con la versión de Media Composer v2018.1 del 16 de enero de 2018.

 

¿Cuál es el nuevo esquema de control de versiones? : Para 2018, Avid está implementando una nueva convención de numeración de versiones de software:

·         Las versiones de software se numerarán según el año y el mes, por ejemplo, la primera versión de software en enero de 2018 se numerará v2018.1

·         Las versiones posteriores dentro del mismo mes tendrán un sufijo adicional, por ejemplo v2018.1.1

·         Para productos que no se publican mensualmente, será necesario omitir los números a veces; por ejemplo, la versión que sigue a v2018.1.1 puede ser v2018.3

·         Las pantallas de presentación de productos, menúes About, Master Accounts de Avid y Application Manager mostrarán el número de versión completo, por ejemplo v2018.1.1

·         En los casos en que el software instalador no admite cuatro caracteres para el número de versión base, truncaremos los dos primeros caracteres, por ejemplo, un instalador puede tener que referirse a v2018.1.1 como v18.1.1. El archivo exe también puede necesitar mostrar el número de versión truncada.

 

Por qué el cambio?:

· Esta nueva convención en la numeración ofrece varios beneficios para Avid y nuestros clientes: agilizar los productos.

· Nos permite enfatizar el posicionamiento del producto y las últimas noticias en lugar de los números de versión

· Ayuda a recordar a los clientes cuando están desactualizados.

· Alinea los números de versión en todos los productos cuando sale una versión empaquetada o una oferta especial.

· Evita números grandes para productos de larga data

· Promueve la coherencia en las líneas de productos de Avid, lo que permite una mayor coherencia

· Alinea con las expectativas del cliente, ya que otros proveedores ya han adoptado métodos similares (por ejemplo, Adobe, Autodesk)

 

¿Cuándo sucederá?:

· Media Composer fue el primer producto en lanzarlo, con v2018.1 que salió el martes, 16 de enero de 2018 @ 3:00 pm EDT.

· Otros productos seguirán tan pronto como sea posible, con planes de migración claros e información similar para el cliente.

 

¿Qué significa esto para los clientes?:

· Los clientes de Media Composer que están cubiertos por una suscripción activa o un plan de Upgrade y Support recibirán la actualización v2018.1 en su Cuenta Master Account de Avid, Application Manager y en el Download Center. Su licencia actual ejecutará esta versión de software, no necesitan una nueva licencia.

 

· Otros productos operarán de manera similar; el cambio de versión no debería requerir una nueva licencia.

 

 

 

 


Which Codec for final editing and color correction?

$
0
0

I'm wondering which clips would be the best to use for making my final video mixdowns of subsequences to be used in adding transitions and color corrections.

My original footage clips are
Resolution: 4K
Codec: ProRes 422HQ (10 bit)
Data rate: 754 Mbit/s = 94.25MB/s

I've transcoded my clips to DNxHR LB (18.26 MB/s) for doing the bulk of my editing in subsequences, but I'm now ready to swap my DNxHR LB clips with Highest Quality clips for exporting video mixdowns of the various subsequences for use in adding transitions and final color correction.

Should I relink my subsequences to the original ProRes clips for exporting video mixdowns, or should I just transcode the ProRes files into DNxHR 444 (177.67 MB/s) or DNxHR HQ (88.88MB/s) and relink the subsequences to the high quality DNxHR clips?

If relinking to the high quality DNxHR files is the way to go, should I be transcoding to DNxHR 444 since the data rate is 177.67 MB/s which is greater than the 94.25MB/s ProRes original clips?

Thanks!!

 

 

Titler incompatible between Mac and PC?

$
0
0

Could somebody with Mac and PC workstations do me a favor and test this? Make a timeline on a PC. Drop an Avid Titler on some filler. Type something out. Then open that same sequence on a Mac workstation and let me know if it works. 

I have a timeline with a bunch of Avid titler filters on it then went to a Mac workstation to do an output and none of them were working. 

Thanks in advance for your help. 

MC 2018.12.3 on both workstations.  

Linking Error on P2 & XF-AVC Media

$
0
0

Hi,

Running Media Composer 2018.12.3 on HP Z820 with Interplay | Production

When we are linking to P2 cards from within the Source Browser we are consistently getting the following error:

Assertion failed: bAAFProcessorOK

File: s:\coresw\ame\src\ama\ama_manager.cpp, Line: 3082

It is possible to click continue but with a large number of clips it becomes tiresome.

Has anyone seen this error before? I have checked and have the latest version of the P2 plugin from Panasonic installed.

Thanks,

Jonathan

 

Unimaginable long time to open BIN and Sequences

$
0
0

Hello,

 

I have a serious problem with the opening time of BINs and Sequences.

BIN can open up to 20 minutes.

The attempt to open the sequence is up to 15 minutes.

BINs are not so big, they are from a few to several sequences.

Sequences that open long are in very small BINs

(1 sequence)

 

From what I was able to find, I did it:

1. http://avid.force.com/pkb/articles/en_US/troubleshooting/Ways-to-speed-up-Media-Composer-bin-save-load-switching-between-applications-and-startup - nothing it helped

2. http://avid.force.com/pkb/articles/en_US/troubleshooting/en397171 - also without a positive result

3. https://forums.creativecow.net/docs/forums/post.php?forumid=345&postid=373&univpostid=373&pview=t - also without a positive result

4. Fresh installation of WIN 7 PRO on Z440 avid 2012.12.5 - without improvement

 

SPECIFICATIONS:

1. The problem began to occur at Z4 Avid 2012.12.3

2. Project data and media are on AVID ISIS 5500 workspace

3. Connected by the Intel (R) PRO / 1000 PT Dual Port Server Adapter

Dependency issue with mediaprocessor-win-vc14-x64-4.4.25.10050

$
0
0

We ran into an issue with package when installed on a clean system.  It seems that one of the DLLS included with latest VC14 release of media processors is dependant on the VS 2013 c++ lib support.

According to a dependancy walker - FTF.DLL (dated 2016-10-13) is dependant on MSVCR120.DLL and MSVCP120.DLL.

When installing on a clean system, this library fails to load - our installer is not explicity including the 2013 libraries any longer.  Can this be resolved in a future release?

Thanks,

Rich Laws

 

Source Settings - Playback Frame Rates Default

$
0
0

Hello! 

Is anyone aware of a way to force the default Playback Frame Rate in the Playback Rates tab or Source settings to the Project's FPS rather than the Clip's FPS?

To be clear we are AMA linking stock footage at various rates and want to preserve the source framerate on transcode but still have it play back at 23.98 in the timeline.

A console command I'm missing maybe? SetAMAQTForcedFrameRate does not seem to help.

Thanks!

Chris 

p, li { white-space: pre-wrap; }

Source Settings - Playback Frame Rates Default

$
0
0

Hello! 

Is anyone aware of a way to force the default Playback Frame Rate in the Playback Rates tab or Source settings to the Project's FPS rather than the Clip's FPS?

To be clear we are AMA linking stock footage at various rates and want to preserve the source framerate on transcode but still have it play back at 23.98 in the timeline.

A console command I'm missing maybe? SetAMAQTForcedFrameRate does not seem to help.

Thanks!

Chris 

p, li { white-space: pre-wrap; }


Difficulty opening older project

$
0
0

I have the project files archived and the drive ready. I tried copying the old project file, Avid 8, into the 2018.12.3. It's not showing up in Avid but does appear in the harddrive folder where the projects are stored. 

Any thoughts or workarounds?

Thanks!

 

where to send renders?

$
0
0

Hi,

I have a sequence that's ready to Export To File, and I'm choosing a QT Reference file (so as to export proper via Squeeze).  During the process the "Create Video Effect" occurs, and these renders automatically store to my C drive.  I would prefer to have these automatically store on an external drive.  How to instruct?

Thanks,

DC

2018.12.5 on avid link

$
0
0

When will 2018.12.5 be available on Avid Link?

Green Frames - Altered Colors - Major Exporting Issues

$
0
0

I love Avid but I am starting to reach my limit. I am very fed up with how much I struggle to simply export my footage from avid media composer!

I shoot on GH4s and GH5s, 4K and 1080 H.264 .mov’s. Avid’s video column says: AVC Long-GOP High.

I link to the footage and edit with proxies.

The issues arise when I’m exporting the sequences linked to the masters. I usually export animation, DNxHR, but compression type doesn’t seem to have any part in the issue.

If I am linked with the Avid generic plug-in my colours are all wrong and clearly change when switching between quicktime and generic linking. The Quicktime linking is closest to what I see in camera. also with the generic linking I get random skipping of frames at the end of  some shots, it is very oticeable and throws of the edit completely!

But if I am linked with QT it is even worse, the export will have random flashes of comppletely green frames through out the whole export.

So far my only work around has been to transcode the QT linked sequence so the colours are right and when exporting the transcodes the other issues do not occur.

This is not good for me as I export a lot of projects, all the time with 1 hr plus runtimes! Transcoding it all just to export it is not a good workflow, it takes up so much space and time! And is adding rounds of compression or alteration I’d prefer to skip!

This can’t be acceptable from an editing program. I should be able to get my project out of the program with out such a plethera of issues and unsatifactory work arounds!!!!

Media Composer 2018.12.5 AVAILABLE 14 May 2019

$
0
0

Good news! Media Composer 2018.12.5 is now available. This is a patch release, and is only available through the Download Center. You will not see it in your My Avid account or on Avid Link.

The Windows version of Media Composer v2018.12.5 is a patch release. You must have v2018.12.3 already installed. Then use the 2018.12.5 patch to update to this release.

Fixed in Media Composer v2018.12.5

The following has been fixed:

➤ Bug Number: MCCET-2999. You might have received an Exception error when deleting an asset from a bin.

Fixed in Media Composer v2018.12.4

The following have been fixed:

➤ Bug Number: MCDEV-10783. You might have received errors when trying to log into the MediaCentral Cloud UX server.

➤ Bug Number: MCCET-2822. In some instances, the .mxf extension was not appended using Send to Export, therefore “Auto Launch” could not open mxf files.

➤ Bug Number: MCCET-2927. Intermittently, saving bins resulted in Exception errors.

➤ Bug Number: MCCET-2902. In some instances, a video mixdown included the effects from an upper nested layer.

➤ Bug Number: MCCET-2897. After importing, certain WAV files may have had an incorrect start time.

Fixed in Media Composer v2018.12.4

2

➤ Bug Number: MCCET-2748. If a sequence with media from a P2 card was loaded into the Source or Record monitor, relinking to add an extra clip would take too long.

➤ Bug Number: MCCET-2867. In some instances, rendering some effects on linked H264 media resulted in mixed up frames.

➤ Bug Number: MCCET-2862. (Windows 10) The Audio Tool was not updating when scrubbing with CAPS lock enabled.

➤ Bug Number: MCCET-2937. In some instances, if you captured with a single track that was not A1, the capture would abort immediately.

➤ Bug Number: MCDEV-10869. Clicking the yellow bin lock icon maximized bins that were minimized.

➤ Bug Number: MCCET-2967. (Avid Artist DNxIO and DNxIQ) Audio meter levels were not displayed in the Audio tool when recording.

➤ Bug Number: MCCET-2952. The Audio Punch-In Tool did not remember the last bin selected.

➤ Bug Number: MCCET-2914. In some instances, when exporting JPG, if you changed the name of the export, the file may have been unusable.

➤ Bug Number: MCCET-2942. You could not perform an insert edit export of DNxHR HQX media.

➤ Bug Number: MCCET-2946. (Interplay) In some instances, Media Composer would crash during check-in of sequence.

➤ Bug Number: MCCET-2910. Importing a non-shared user profile created a duplicate and prevented the application from closing.

➤ Bug Number: MCCET-2913. The Property Merge window would inadvertently appear when checking in a clip for first time into Interplay.

➤ Bug Number: MCCET-2901. Media Composer would hang when playing back an Avid Titler+ title in the effect editor.

➤ Bug Number: MCCET-2729. You might not have received the correct find results when searching group clips in PhraseFind.

➤ Bug Number: MCCET-2931. After upgrading from Media Composer v2018.12.1 to v2018.12.2 or v2018.12.3, batch re-import of Matte Key clips was not working.

Fixed in Media Composer v2018.12.4

3

➤ Bug Number: MCCET-2878. The UHD video output is converted to HD when consolidating HD media in a UHD project.

➤ Bug Number: MCCET-2859. Switching camera angles in Multicam stopped playback if the group contained mixed frame rates.

➤ Bug Number: MCCET-2857. If you were working on a system using Chinese locale, you might have experienced consolidate and transcode audio issues.

➤ Bug Number: MCCET-2957. Insert Edit Export failed if only video tracks were selected.

➤ Bug Number: MCCET-2966. You might have been unable to import an EDL.

➤ Bug Number: MCCET-2915. The metadata might have been incorrect after importing an ALE.

➤ Bug Number: MCCET-2841. Saved presets did not always retain the last keyframe.

➤ Bug Number: MCCET-2805. The Raster Dimension column in a bin was incorrect for thin raster media.

➤ Bug Number: MCCET-2925. In some cases, after performing a render operation, the green dot remained in the Timeline on PNG clips including a Matte Key effect.

➤ Bug Number: MCCET-2930. You might have seen performance issues when editing a long AVC Long GOP 25 clip.

➤ Bug Number: MCCET-2973. Changes to Audio Reference Level settings changes were not properly reflected when you switched between Normal and Narrow Mixer View.

➤ Bug Number: MCCET-2960. (Mac v10.14.x) When linking to media on a shared network drive, the UNC path in the Drive column might have had the network user name in the path.

➤ Bug Number: MCCET-2732. When consolidating AVC Long GOP subclips created new master clips that were too long. A new check box has been added to the Consolidate/Transcode dialog

boxes. Select the “Re-encode AVC Long GOP media to ensure shortest subclip durations” option when you consolidating AVC Long GOP subclips.

➤ Bug Number: MCCET-2923. (Mac) You might have received “not authorized” errors when trying to use PhraseFind or ScriptSync.

➤ Bug Number: MCCET-2947. You might have received errors when trying to set target the Dynamic Relink settings in an SD 25i PAL project.

Fixed in Media Composer v2018.12.4

4

➤ Bug Number: MCCET-2936. If Dynamic Relink was enabled, imported DaVinci Resolve AAF media was offline.

Avid Every time I insert a clip. Loading media file information and relink

$
0
0

Hello,

Does anyone have this going on? 

Everytime I insert a clip into my sequence avid says its "Loading media file information" with a progress bar that takes about 2 secs and then "relinking to media" progress bar. Does anyone know whats causing this? And how I can get it to not do this?

 

I noticed it only does this with clips that have 4K footage. 

 

I am using transcoded footage (DNxHRx) and the media is on an Internal hard drive. I am using PC and Avid 2018.10. My project settings are 23.976, 3240x1080

Thank you for your time!

Shooting 720p with stage monitors displaying 1080i...What can go wrong? Haha!

$
0
0

But seriously, what will go wrong?  I'm being asked if this will work.  How the F would a tape monkey like me know that?  I'm just an AE.  

So here is what I was asked:  We are shooting a stage show 720p/59.94.  They need a live streem to the stage monitors to be 1080i.  I said, will that look ok on our end in post?  Everyone turned to me and said, go research it.  So here I am.  Haha.  

So, if by chance any of you have shot a stage show 720p with monitors on stage displaying 1080i, can you tell me how that worked out for you on Avid 8.9.4.?  

Don't all rush to share you stories at once.  There's time enough for everyone to tell their stories and help me through this.  Haha!

I guess this was half a question, and half venting.  But the answer if very important to me.  

Thank you all!

jerdog3


Playback stutters

$
0
0

I just installed MC Ultimate on my MacBook Pro running High Sierran 10.13.6.  My problem is in playback.  It stutters.  Does anyone know a solution to this?

marluc

DNxID - MacPro2013 - does it work with Thunderbolt2 Adapter?

$
0
0

Hello

I have 2 Systems - One Main MacPro2013 12Core and now a new MacBooPro2018

I do want to buy the new DNxID with Thunderbolt 3

Does it also work with Apples Thunderbolt2- Thunderbolt 3 Adapter?

Thnax

Sly

Same As Source Export Speed Confusion

$
0
0

Hello,

I noticed that the export speed of my almost daily Same As Source Exports highly increased.

Normally when I export Same As Source, a 90 minute filme needs about 15min.

Everything is DNxHD36, checked via Bin Display (Reference Clips and Sources).

I can't really say from which point on I noticed this.

We had MC8.7.2 in our edit suites, export times are from there. Now we have MC2018.9 and now it starts to get obvious.

Two days ago I had a 105min roughcut, export needed 2h!

Again, all DNxHD36, enough space on the drives, no fancy timeline.

 

Yesterday we did a test, we had a 90min film, one main video track, some snippets on V2, 18 audio tracks, mostly with dissolves.

Exporting Same As Source: 1h20min

We know, that in most cases Audio is the big deal. So we divided the sequence.

Exporting Same As Source Video only: 3:45min

Exporting Same As Source Audio only: 4:30min

Then we made an Audio Mixdwown at first: 4min - and the a Same As Source with video and the audio mixdown: 6min

 

And then again everything together, video and original audio: Export starts with 24min and goes up to over an hour.

Why!?

 

So I am much faster if I either make an audio mixdown before or I export audio and video seperatly and put it together in QT-Player or something else.

Where has Avid a problem?

Ideas on this?

 

Doyle

Exporting Screenshot

$
0
0

Whenever I export a single frame as a screenshot, it includes all the video tracks, even if some of the tracks are not selected.   For example, if I want to export a shot on V1 without overlaying graphics on V2, I have to temporarily delete V2 before exporting a screenshot of V1.  This is different from a video mixdown, where only the selected tracks are included in the mixdown.  Am I missing something or is this the way it is supposed to work?

shortcut to add a SPANNED MARKER won't work

$
0
0

Hi,

I've mapped an 'Add Marker' shortcut to my keybaord and added the little 'Add Option Key' to the shortcut. It doesn't work to make a spanned marker. I'm still required to hold the option key. Any tips?

Thanks,

Aren

 

Viewing all 30354 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>