4 different boxes trying to export ProRes (Windows) through Media Composer.  

If I try to export a 45 min 1080 program to Prores, I have success if I do a stereo output.

If I try to do Direct output for a 10 channel output, I get either a Memory error, or a consistancy check error on 3 of the 4 boxes.

Box 1- Home made i9 with 64 gigs ram and Radeo VII graphics card. -Errors out.

Box 2- 1 year old HP Z4 Workstation Intel Xeon 3.7 ghz with 32 gigs ram  Quadro P2000 graphics card- Errors out

Box 3- same as box 2, but with a P4000 graphics card - Errors out.

Box 4- has a Xeon gold 5118 2.3 ghz (dual processors) 128 gigs of ram, and 2080Ti graphics card.  This is the only box that completes the output.

All boxes are exporting to 10 shared storage. Boxes 2,3,4 are at one facility. Box 1 at a different facility.

Exports seem to go about 3/4 of the way through before erroring out.

Is this simply a ram issue? Do I need 128 gigs to get this to work, or is this a video card issue?

What resource is Avid more dependant on for this type of export?   

I have had this happen over several shows, different lengths of programs.  The only consistancy really is the direct output seems to put a huge stress on something somewhere. 

I get this error message all the time. It's not limited to one or more specific activities and pops up even when I'm not doing anything. There are a bewildering number of posts on this error message.

Has Avid spoken to this error message with a specific explanation or specific troubleshooting steps? If so, would someone please provide a link or something?

So I've had MC first for awhile but decided to try the ultimate trial. However it will only download the first version. I've tried uninstalling and reinstalling everything and I've also tried creating awhole new avid account but it will still only give me MC First. Can anyone help?

I may have found a bug.

Every time I go to the audio workspace and try to adjust the levels I crash.

Anyone else experiencing this?

I am on 2021.2 Win10 pro HP ZBOOK quadro k1100

Hi all, has anyone here managed to install Media Comp on an M1 mac / Big Sur set-up? I know it's all rather premature but I've been trying to force it with Rosetta 2... with zero success. I have an "unavailable BoB" apparently. Can anyone help me with this please before lose my mind entirely. Perhaps I should just give up and wait, which isn't the end of the world. Thanks in advance. Duncan

I want to:

In a Marker screen with red and white markers/locators, I want to export only the white markers and then re-import them back into a bin.

Convert locators in the Marker menu into subclips in a bin, preferably polulated with the Marker comments.

Hi, and once again my apologies for a basic question--I wasn't able to filter to a relevant post about this.

(Please feel free to forward any links or white papers)

I have a 2010 Mac Pro upgraded to 12 core. 

1 Slot has a 3GB Radeon R9 280x,  1 Slot a USB 3.0 card, 1 Slot a PCI NVME Hard Drive, Last slot Fibre Channel card.

That maxes out my slots so I can't have the Nitris DX card anymore, even though I run Mojave and Media Composer 2021.

Could a 8GB Radeon RX 580 or 480 type card, run 2 Monitors and then also output out of its HDMI with AVID sending the signal there for full screen output to an HDTV for client monitoring? Or is that going to produce some lag vs how the Nitris DX (or even a decklink card) sends it through HDMI?

Just curious, right now I have no way to send to a client monitor, no more space for cards. But I need all the cards I have right now and anyways when I go to Catalina on the 2010 Mac Pro it won't run the Nitris DX anyways. Right now I run Mojave though so I'm fine.

Anyone know where, if possible, to buy this book without taking a class?

When creating stringouts I:  

Display bin in Script Mode > Select All clips > Remove Marks > Mark In > Option drag into the the Timeline window.

This is basically allowing me to mark the first frame of every clip in a bin with no outpoints before creating the stringout. 

But is there a way mark (for intance) frame #20 of each clip simultaneously?  I seem to remember this from years ago.

i previously installed mc first now i want to install the full version on my surface tablet. i have downloaded the files and every time it finishes it's running mc first. i have removed all of mc first numerous times. i have my sys id & activation code but during the install it never asks for it. what am i doing wrong?

Hugh

ford_q1@msn.com

Great news……. Today December 21^st, 2020 @12:00 pm EDT Avid launched the last release of Media Composer 2020.x for the year 2020.

 Location at Launch:  The new Avid Link 2020.12 is available in the your MyAvid Master Accounts, through the Avid Link application itself, and from the Download Center.  

Status of Support Plan:  The ability to launch this Media Composer 2020.12 software is dependent on the status of a your Upgrade and Support Plan on the date this software version is released. Media Composer 2020.12 will be released on December 21^st, 2020. 

Media Composer Notes: 
   

MCDEV-11537. If you intend to use full-frame stereoscopic with an Avid Artist DNxIQ, you may want to remain with Media Composer v2018.12.x until the issues with Stereoscopic support are resolved in a future version.

• Media Composer now includes a dnxmov2mxf executable in the \Program Files\Avid\Avid Media Composer\SupportingFiles\Utilities folder. This executable allows you to manually convert MOV files with DNX essence with separately stored alpha to an MXF OP1a file with DNX essence and embedded alpha. The tool is available for Windows, osX, and Linux. To run on Windows, Visual C++ Redistributable for Visual Studio 2015 or Visual C++ Redistributable for Visual Studio 2017 is required. Run the command from a command prompt on Windows or from terminal on macOS.DNXMOV2MXF usage is:dnxmov2mxf path_to_mov [path_to_mxf]

Changed in Media Composer v2020.12

For details on new features, see the attached document and the final update will be uploaded to the knowledge base What’s New v2020.12 document. page at launch.

The following are new for Media Composer v2020.12

• Transcode of Alpha Mattes
• H.265 Support
• Export Media Difference Between Sequences
• Avid Titler+ Updates
• Dragging Bin Content to an Open Bin in Bin Container Sidebar
• Mapping Bin Fast Menu Commands to Buttons
• Floating Panel Windows
• Updated Interface Settings
• Bin Brightness Updates
  
• Finding a User Profile
• Additional Languages for PhraseFind and ScriptSync
• Custom Color Space for Exported MOV, MP4, and OpenEXR
• AAC Audio Format for Exported MOV and MP4
• Audio Mixer Update
• Additional ACES Support
  

What’s Fixed in 2020.12:  The following has been fixed.

• Bug Number: MCCET-3834. After upgrading to Media Composer v2019.12.2, you might have received a “Fatal error” message when opening a sequence containing image (without alpha) clips.
• Bug Number: MCCET-3860. In some instances, when in a Production Management environment, the application unexpectedly deleted the original files of linked clips.
• Bug Number: MCCET-3869. You could not link or import DNxHD MXF OP-1A from an AJA Ki-Pro Ultra.
• Bug Number: MCCET-3892. Media Composer Floating License consumed 2 seats during activation.
• Bug Number: MCCET-3870. Line trail marks might have appeared in AniMatte effects when Windows Display Setting Scaling was set to 200%.
• Bug Number: MCCET-3906. Clip gain was being ignored when rendering Audiosuite effects.
• Bug Number: MCCET-3561. (Windows 10) Microsoft YaHei and JjengHei fonts did not appear in Subcap.
• Bug Number: MCCET-3863. You might have received an “Assertion failed” error when opening a project or bin.
• Bug Number: MCCET-3829. The Production Management Folder Setting did not follow the Site Settings.
• Bug Number: MCCET-3724. Site settings for General, and Media Creation were not always working for New projects.
• Bug Number: MCCET-2885. Imported TIFF with alpha had softer edges compared to .mov with alpha.
• Bug Number: MCCET-3748. The title bar did not change in contrast when you switched to a light interface setting.
• Bug Number: MCCET-3818. In some instances, a User folder was being placed in a project when accessing a bin from a different project.
• Bug Number: MCCET-3888. You might have received an “Unable to proceed” error when exporting as MP4 or MOV.
• Bug Number: MCCET-3184. Media from the Arri Alexa Mini were displayed upside down and flipped in Media Composer.
• Bug Number: MCCET-3665. You could save the bin even when it had a yellow bin lock.
• Bug Number: MCCET-3716. A keyboard shortcut for audio punch-in and record did not always start recording.
• Bug Number: MCCET-3822. In some instances, even when Dynamic Relink was set to Highest Quality, video clips were relinked to the proxy resolution.
• Bug Number: MCCET-3605. (macOS) Event logs might have mislabeled a “DSM path not found” error as a critical error.
• Bug Number: MCCET-3825. Deleting a custom-saved Title Style from the settings resulted in a crash to a Breakpad window.
• Bug Number: MCCET-3742. Markers did not display in an EDL if placed on a group clip.
• Bug Number: MCCET-3551. Performing an XDCAM proxy import or batch reimport might have resulted in a crash to a Breakpad window.
• Bug Number: MCCET-3762. You continued to receive the warning, even after selecting the “Don’t warn again” message, when loading IMX50 SD clips with restrictions.
• Bug Number: MCCET-3792. If the primary Transfer Engine was down, the Send to Playback list would not appear.
• Bug Number: MCCET-3670.  You could not successfully Dynamic Relink to XDCAM HD 50 and MPEG 50 SD (IMX50) at the same time. The Dynamic Relink options would not allow you to relink XDCAM HD 50 and MPEG SD 50 at the same time, with the proxy offline.To fix this, an additional option has been added to the Dynamic Relink dialog.
• Bug Number: MCCET-3871. You could not successfully send a mixed resolution sequence to Send to Playback if Dynamic Relink was set to a specific resolution.
• Bug Number: MCCET-3831. The MultiRez button in the Timeline did not display colors properly as in previous releases, making it difficult to distinguish the status.
• Bug Number: MCCET-3750. (Japanese locale) In some instances, you could not open your Project by double-clicking the .avp file
• Bug Number: MCCET-3868. In some instances, you might have received an “Exception” error when accessing the Dynamic Relink settings dialog. This happened if the Dynamic Relink Override Target Video menu did not populate correctly.
• Bug Number: MCCET-3830. Using the MultiRez Button in the Timeline did not change the Timeline segment colors for working/target mismatches.
• Bug Number: MCDEV-8972. (HiRes Dual Monitor) Bins did not reopen in the same location after closing and reopening 
  

• Photoshop PSD files are not supported for AMA linking if QuickTime is not installed.
• Some fonts, by their design, are available only in Bold. On the Mac system, it can happen that    selecting a font does not produce any visual changes. Try selecting “Bold.”
• If you launch a project and receive an “Enable 3rd Party Emulation” warning, even if you select Enable in the warning dialog, you should also perform the following: Select File > Settings and click the Project tab. Click General Settings and select “Enable Bin Sharing on 3rd party storage emulating Avid NEXIS/ISIS.

• Bug Number: MCCET-3788. You might receive a “clip name is a clip in a multi-essence file that cannot be exported using the specified Embedded in AAF setting” when exporting embedded AAFs with OP1a audio clips.Workaround: Consolidate the OP1a clips to Avid OP-Atom prior to performing the export.

• Bug Number: APPSVCS-723.  The Collab App in MediaCentral CloudUX window does not currently work with Media Composer.
• Bug Number: MCDEV-13604.  You might have issues playing clips containing Media Composer effects in the Baselight User Interface if the Fast Image Access option is enabled in the Baselight plug-in
• Bug Number: MCDEV-12926. (macOS) If you have upgraded to macOS 10.15.4, there is a known issue with local attached RAID storage. The system will hang when running Media Composer or copying large files. This does not happen with earlier versions of the OS. You can read details about this issue in this blog. This limitation no longer exists with macOS 10.15.5.
• Bug Number: MCDEV-12964. For a faster performance of export audio/video sequences to .mov in 2020.4, please render the sequence prior to export, or disable the GPU fx (in the Render Settings - Current menu)
• Bug Number: MCDEV-12735. Maestro graphics do not appear correctly in the Timeline if your system uses the Radeon video card.
• Bug Number: DEFI-1808. (Media Composer | Distributed Processing) Two clips or sequences will always be created when performing a consolidate or transcode with Media Composer | Distributed Processing.
• Bug Number: MCDEV-11481. Promoting a title from the Title Tool application to Avid Titler+ cannot be performed if it includes a motion adapter.
• Bug Number: MCCET-11796. Larger than 10 bit DPX files might fail to link correctly.Workaround: Go to File > Settings and click the User tab. In the Link Settings, click the Link Options tab and make sure Alpha Channel is set to Ignore.
• Bug Number: MCDEV-11430. Media Tool ignores the “Current project” filtering option and lists media files that are not associated with the current project.
• Bug Number: MCDEV-11197. In some instances, the Interleave option might not appear in the Export As dialog box. If you are performing an Export using the Avid Media Processor, the Interleave option should appear when you choose Stereo, 5:1, or 7.1 Audio.Workaround: If it does not appear, briefly toggle back to the Mono setting, then toggle to Stereo Mix once again. Doing so should reveal the Interleave option.
• Bug Number: MCDEV-8641. (AMD Graphics). Systems with AMD graphics cards might display tearing when performing Full Screen playback.
• Bug Number: MCDEV-9269. (Media Composer | Cloud) After performing a remote download operation on a sequence containing AVC-I 100 remote media, the downloaded media appears as XAVC-I 100.Workaround: Download the entire master clips.
• Bug Number: (macOS).  You may occasionally see the menu bar flash followed by a brief beach ball. To fix this, deactivate “Displays have separate spaces” under System Preferences > Mission Control settings.
• Bug Number: MCDEV-9011. Intermittently, when working with the XDCAM Nablet Plug-in, you might see “Failed to get the sample position from the AMA Plug-in” errors if you have waveforms enabled in the Timeline.
• Bug Number: COGS-2560. While working in the Script Window, text operations (cut/copy/paste/delete/editing) can only be done in edit mode. See “Editing a Script” in the Help.
• Bug Number: MCDEV-5650.  When working with Panasonic LongG media, you might receive an “SFPlayConsumer Timeout” error if audio waveforms are enabled.Workaround: Turn off audio waveforms.
• Bug Number: MCDEV-5385. MultiCam editing with Panasonic LongG media is not supported with this release.   

ReadMe: The new ReadMe has been uploaded to the Knowledge Base Media Composer 2020 Documentation page at launch.

I just installed MC First, and I'm looking for the best way to have my media handled. I've got the computer's hard drive but I also have a 2TB External Drive I'd like to use for the AvidMediaFiles. Does anyone know how to set it up so that I'm not clogging up the internal drive with Avid files?

Hi

I can not access Media Composer via the avid link.

Write to me that the servers are unavailable. And so the avid link does not receive my user ..

I deleted and installed the avid link

Would appreciate help.

Thanks.

Today February 9^th, 2021 @12:00 pm EDT Avid launched Media Composer 2021.2.

 Location at Launch:  The new Media Composer 2021.2 is available in your My Avid Master Account, through the Avid Link application itself, and from the Download Center.  

Status of Support Plan:  The ability to launch this Media Composer 2021.2 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released. Media Composer 2021.2 will be released on Tuesday, February 9th, 2021. 

Media Composer Notes: 

MCDEV-11537. If you intend to use full-frame stereoscopic with an Avid Artist DNxIQ, you may want to remain with Media Composer v2018.12.x until the issues with Stereoscopic support are resolved in a future version.

• Media Composer now includes a dnxmov2mxf executable in the \Program Files\Avid\Avid Media Composer\SupportingFiles\Utilities folder. This executable allows you to manually convert MOV files with DNX essence with separately stored alpha to an MXF OP1a file with DNX essence and embedded alpha. The tool is available for Windows, osX, and Linux. To run on Windows, Visual C++ Redistributable for Visual Studio 2015 or Visual C++ Redistributable for Visual Studio 2017 is required. Run the command from a command prompt on Windows or from terminal on macOS.DNXMOV2MXF usage is:dnxmov2mxf path_to_mov [path_to_mxf]

ReadMe: The new ReadMe will be uploaded to the Knowledge Base Media Composer 2021 Documentation page at launch.

I just loooked at the list of qualified Mac systems along with the new 2021.2 update, and no longer see my trusty 15" mid-2015 Retina MacBook Pro on the list. Is this machine really no longer supported?

Hello to everyone,

When I close avid with the nitris connected, a blue screen appears that forces me to restart the PC. My AMC version is 2018.12.7.

Thank you

Best Regards

Hello everyone,

I am experimenting with exporting markers with comments from my sequences's markers list as a TabD file and then importing the same tabD file back into Avid with the hope of pasting the markers onto another sequence, but I can't seem to get it to work. When I open up a new sequence and go to markers list and then right click to 'import markers' and choose the tabD file at windows level - nothing happens! Does anyone know how to copy markers with comments from one sequence to another? I've tried simply copy and pasting but that also doesn't work. I'm on Avid MC 8.8.1

Thanks!

Michael

Hi

Everytime I launch Licence manager I get a Startup Error and I can't open it.  It's called "Startup Error" and then says "An error has occurred during startup:" then a whole load of stuff that seems to refer to Java.  Any ideas appreciated.  (It had been working previously and I don't know what I've done different since)

Thanks, Paul

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'databaseServicesEventHandler': Unsatisfied dependency expressed through field 'loginServiceImpl': Error creating bean with name 'loginServiceImpl': Unsatisfied dependency expressed through field 'entitlementService': Error creating bean with name 'entitlementServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entitlementServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'loginServiceImpl': Unsatisfied dependency expressed through field 'entitlementService': Error creating bean with name 'entitlementServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entitlementServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException

at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:569)

at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88)

at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:349)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1214)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:543)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:776)

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:861)

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:541)

at org.springframework.context.annotation.AnnotationConfigApplicationContext.<init>(AnnotationConfigApplicationContext.java:84)

at com.avid.fncservice.websocket.WebSocketServer.runServer(WebSocketServer.java:220)

at com.avid.fncservice.websocket.WebSocketServer.main(WebSocketServer.java:71)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.exe4j.runtime.WinLauncher.main(Unknown Source)

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'loginServiceImpl': Unsatisfied dependency expressed through field 'entitlementService': Error creating bean with name 'entitlementServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entitlementServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException

at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:569)

at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88)

at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:349)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1214)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:543)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)

at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:207)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1214)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1054)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1019)

at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:566)

... 21 more

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entitlementServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException

Hi all,

I am having constant crashes during audio scrubbing in 2019.12 with a Blackmagic Decklink Studio 2. The system is an HP Z840 running Windows 10.

It's happening with Desktop Video 11.7 and the latest Desktop Video 12.0. If I disable the hardware, the problem goes away.

All I need to do is move up and down an audio clip in the source window a few times, with digital scrub enabled, and the system will hang and need to be crashed via task manager. 

I've just worked out that if I turn off Fast Scrub the system will recover after ten seconds or so, but then I seem to lose scrubbing the timeline! As you can imagine, this is beyond frustrating. 

If anyone has any ideas that would be great. There is an error message when fast scrub is off, as below.

Cheers, 

Ollie

scrub error

Need some pro advice please. FINALLY at the point where it's time to upgrade from my current HPz440 (still a pretty darn good workstation). But I fear that most of it's components are going to become more obsolete as time progresses. 

Looking for feedback as to the best Windows based workstation to choose. I've got Avid's qualified PC list but I want actual editor opinions as to what they use, what works for you, etc.  Couple things:

NOT interested in going Mac. Nothing personal..I'm just an "old geezer" of an editor who prefers PC

AND..I'm not interested in building my own. I've had a couple specially built computers in the past and had issues each time

so I'm looking for the best pre-built workstation. As you can see from my specs..I'm way past due for an upgrade!

My current specs are listed below. I know I can trust this group of great editors and pros to guide me in the right direction. "Googling" it has done nothing.

THANKS!!!

Current Specs: HP Z440, Media Composer 2018.8, 32GB Ram, WIN 7 pro, 64-bit OS, Nvidia Quadro K2200 4GB, Intel Xeon CPU-E5 1650 v3 3.5ghz 6 cores, 12 threads, 15mb cache