Mxf op1a match source Media Encoder

I'm trying to use the mxf op1a match source (rewrap) preset in Media Encoder. I've got a variety of source material from Gopros, XF305s and a couple of others. The preset fails consistently with Gorpro footage, and I've had problems with some other sources too. I keep getting the "The source file's video stream is not compatible with this preset. Please choose a different preset." error.
My question is: given that I'm only trying to use the mxf preset as a container, keeping the source material as it is - why am I getting compatibility errors? As I understand it, mxf can be used as a container for a variety of video types, I've not come across anything that states it doesn't work for Gopro files or any others, so what's the problem?
Thanks
Bransby

This won't work for GoPro footage because our MXF exporter doesn't support GoPro CineForm. Unfortunately the preset has to do a little more than just copying the streams to a new wrapper. We have to have an ability to write that stream natively to MXF and currently we can't do that. If you wanted to make a feature request, you should request that we support GoPro CineForm in an MXF wrapper. Once that exists your workflow will work. Feature requests can be made here:https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Similar Messages

MXF XDCAM OP1a Red Frames in Media Encoder

It was advised in the other thread about red frames to start a new one for this kind of the red-frames-problem.
So my usual workflow is:
Export a masterfile from Premiere via Mediaencoder as XDCAM OP1a 1080p5025fps.
From that I generate various versions for my clientst directly in MediaEncoder. Almost only h264 in all different sizes.
Since the update 3 days ago this doesn't work anymore. The h264 files that are made from the mxf have many red frames and mediaencoder reports errors like:
: MXF read error "\\?\V:\xxxxx-1080p-XDCAMHD50PAL.mxf" frame 383.
In a 3 minute clip 8 of those errors at differnet frames are reported. I suppose that is where the red frames are generated.
Yesterdays update (the Audio Buzz fix) did not change the redframe problem.
So I used my 2nd installation that was not updated for weeks. There everything works as expected.
When I generate the MXF there, it's fine and h264 files are made from it without any problems.
So I have a working MXD XDCAM OP1a 1080p 50 PAL25fps.
That same file in the updated media encoder again gives many "MXF read errors". So it's obviously the Mediaencoder that cannot handle that (working) MXF file.
I hope that helps the developers to get rid of that problem as soon as possible.
__Peter__

We are having the same issue at our shop. We have 8 suites, all are experiencing red flashes ever since we upgraded to 7.2.1.
All the systems are Win7, and we've encountered red flashes with XDCam 35, XDCam 422 and Mpeg4 clips. We haven't been to develop a workaround as the flashes occur in very inconsistent patterns.
For example, just a moment ago an editor called me in because he was getting red flashes on his exports. We went to his timeline, and the timeline was showing red flashes as well. We deleted the clip (an XDCam 422 clip) from the bin, and re-imported it. It played in the viewer fine with no flashes. We put it on the timeline and again it played fine. We exported the sequence directly out of Premiere as an XDCam 422 clip (delivery format needed for the client) and the exported file contained red flashes. We went back to the timeline and it had red flashes, and the clip in question had red flashes when viewed directly! WTF?!
So we deleted the clip again, and re-imported it. Played fine with no red flashes. Put it on the timeline - no red flashes. This time we exported the timeline as an AVC-I 100, and the exported file had no flashes. As a test we went back and exported the timeline again as XDCam 422...and red flashes on the exported file, AND the timeline and original clip had red-flashes as well.
Could it be something with XDCam and/or MPEG compressed clips in general? We've only done one more test with AVC-I (which was successful) but I'm not confident enough yet to say that exporting as AVC-I is a consistent workaround.

CS6: Premiere exports MXF Op1a (mpeg based) but Media Encoder does not.

As a company we use several local machines with a full installation of CS6.
Premiere Pro exports in our broadcast format (MXF Op1a - mpeg based - Long GOP - 50Mb - Top Field First - etc...) still Media Encoder does not.
They we both installed in the same procedure, full installation of CS6. MXF presets are present on both directories (Premiere and Media Encoder).
ME simply doesn't recognize "any know exporters" even if I force a preset, when it comes to MXF.
We have to import every single video into Premiere to export as MXF. It's difficult to create an effective workflow this way.
Any thoughts on why is this happening?
NOTE:
- Updated twice all machines - first to 6.0.3, now to 6.0.5 = no result
- Copied presets from a working trial installation = no result
- Microsoft based OS core i7 with 12Gb RAM, 3Tb HD and Nvidia Quadro 4000
Regards, RicardoM

I've read a lot of suggestions towards similar issues. None worked.
- installed codec packs incluiding different mpeg variations = no result
- copied /common preset files from premiere to AME = no result
- copied and replaced the full directory of AME from another working AME (with MXF exporter) = no result
- re-installed CS6 = no result
- updated CS6 twice = no result
- added MXF Preset zip file available in the official Adobe support (although it refers to mac presets) = no matter... no result
I really don't know what else to do.
It's difficult to accept suggestions like "format c and start over" cause of the impact on the production room, so I really need more options other than the extreme ones...
Any ideia Jim Simon?
Thanks in advance!
BTW: Must add that in all processes above, MXF exporting was allways possible in Premiere, just not in AME.

Media Encoder won't import MXF files from Canon XF100

I'm running Media Encoder CC on two laptops: a macbook pro and a macbook air. Both systems are running the most recent version of Media Encoder CC (including updates) but only one will import MXF files from a Canon XF100? The macbook air imports and encodes the files without issue, however the macbook pro won't import the same MXF files and kicks the following error:
The file /Users/.../.../.../AA0106.MXF could not be imported. Could not read from source. Please check the settings and try again.
I could understand if both computers errored but using the same file, one will import and the other will not. Any help would be greatly appreciated. Thanks.

Just try this and see if it will work for you.
Open iPhoto > Preferences > General and deselect 'Connecting camera opens: iPhoto'.
Change it to 'No Application' and close iPhoto.
Now connect your camera to your computer and turn it on or better still use a card reader.
If iMovie tries to open, close it.
Your camera/card should now appear as an external drive.
Copy/paste your video files into a new folder on your desktop.
Eject and disconnect your camera/card.
Now open iMovie and go File > Import > Movies... and navigate to that folder.
Z.

Issue with Pro Res sources when encoding in Media Encoder.

There seems to be a big issue with Pro Res sources in Media Encoder. I've noticed that when exporting using the 'software only' mode my graphics and titles look horrible, they are pixelated around the edges and the compression looks bad. This issue only happens when it's being made from a Pro Res source, if I make the exact same file Uncompressed this issue is resolved. If I use the 'Cuda' option (which I already know is the better option) this issue is resolved. The thing is, in a work environment not all of our systems are Cuda enabled and I would like to use Media Encoder as a exporting option overall. I love Media Encoder, it's fast and easy to use but this Pro Res issue is huge because the majority of the time we are working in Pro Res. I also did a test out of Avid Media Composer to Media Encoder, I sent a reference file referencing the Avid MXF material and the issue is gone, this seems to my knowledge to be a Pro Res only issue. The settings I am exporting to is 960 x 540 h.264 and also .mp4. This is coming from a 1080p source and yes I do have the 'maximum render quality' checked for best scaling. I understand that Software only vs Cuda and Open CL use different algorithms when scaling but this seems crazy to me that it would look this much worse.
Anyways if somebody can please look into this that would be great, this seems to be an issue where I can't continue at this moment to use Media Encoder. Making my source files Uncompressed every time to do an export is just not a real workflow I want to do.
On a side note I've also recently noticed on a clip that had text over a grey background that there are lines going all down the screen evenly when exporting to even a non scaled 1080p .mp4. Once again, this issue goes away with any format but Pro Res. The weird part is this happens even with Cuda enabled. This is why I am thinking Media Encoder is having some sort of issue with the Pro Res codec.
I am on a current new 27'' fully loaded iMac with the latest Adobe CC updates.
Has anyone else experienced this?
thank you

No, it is why advance users do not use the wizard.
Have a look at OpenOffice.org and its form creation. Once you add your fields in OpenOffice.org, just export to PDF and the form fields will be named just like you named in them in OpenOffice.org and the drop down values carry over.

Adobe Media Encoder timecode doesn't match Premiere sequence

Hi, I'm having an issue when exporting through Adobe Media Encoder. My source sequence is 23.976 fps; I've set the Display Format in AME to 24 fps (options are 24, 25 and 30) and the export setting to 23.976 but the time codes don't match; AME seems to be adding frames. Over the course of a 90 minute export AME is adding about 6 seconds; the Premiere sequence is 01:33:52:13 while the AME export settings show 01:33:58:04.
I'm exporting this in chunks so I'm concerned that when I string them all together with the audio there will be a sync problem.
Version: AME CS6 6.0.2.81 64bit
Using with Premiere CS6; have entire suite installed
Most recent update installed
Mac OS X 10.7.3
Creative Cloud: No.
Working with a mix of RED 5k, 4.5k and 4k footage; all shot 23.976
No error messages
Is the problem only occurring with a specific output format or encoding preset? If so, which one? - same on all outputs; exporting to prores 422 1920x1080 23.976
Running Premiere at same time
Mac Pro, 2 x 2.4 GHz 6-core intel xeon, 64 gb ram, solid state boot drive, red rocket, black magic, decklink hd extreme 3d+
Are you using Mercury Playback Engine GPU Acceleration in Premiere Pro? - yes by default? no cuda / opencl
An unrelated problem I've also been having is when I try to export the full sequence, or even half, the export will freeze around 40%. No error message, just stops.

How are you checking the exports?

Can't export AVCHD transcoded to MXF through CS4 Media encoder

So, I need some help. I shot AVCHD clips PH 1080P 24P transcoded with the Panasonic transcoder into MXF files to my desktop. Imported that folder with 15 clips into Premiere and and began editing about a three minute sequence in a P2 1080 24p preset. i even interpolated all my files to 23.976 I built a timeline. Everything looked great and played nicely.
Then I went to export it. I Went to file export - media. It launched the media encoder and showed up in the box. It said "waiting." I clicked on start que. When I clicked on that it said loading "my project file" below. After about ten minutes a yellow yield sign came up and said couldn't locate source material.
Any ideas?? I'd really appreciate it.

Hi MarkCole,
did you have Pr CS3 on the same system which you had un-installed after installing Pr CS4? If yes, then you may need to re-install Pr CS4 again.
If not, then you can try launching AME, going to File>Add Premiere Pro sequence, navigate to the location where the Pr project is saved and select it. Once the Pr project loads in UI, select the appropriate sequence and click OK and then click Start Queue.
Also, you might want to update to Pr CS4.0.1 and AME CS 4.0.1 and see if the problem goes away.
Thanks
Aurobinda

Adobe Media Encoder for CS4 error Could not read from the source

Hello,
I get an error when I try to export from Premiere CS4. It doesn't matter how I export. Seems like an easy fix, but I can't figure it out. Any help is appreciated:
- Source File: C:\DOCUME~1\ARTWHI~1\LOCALS~1\Temp\extra and b roll.prproj
- Output File: E:\Living Accused Movie Transfers\video\Cindy at table.avi
- Preset Used: NTSC DV
- Video:
- Audio:
- Bitrate:
- Encoding Time: 16:10:34
1/21/2009 9:50:25 PM : Encoding Failed
Could not read from the source. Please check if it has moved or been
deleted.
Thank you
Art

When you attempt to encode media with Adobe Media Encoder CS4 on Windows, the following error message appears in the text file (AMEEncodingErrorLog.txt) that opens when you click the error icon: "Encoding Failed. Could not read from the source. Please check if it has moved or been deleted."
If it's that correct, you removed an earlier version of Adobe Premiere Pro or Adobe Creative Suite on the same computer.
Do one or both of the following solutions:
Solution 1: Create a shortcut to the Premiere Pro executable file, rename the shortcut to Premiere, and move the shortcut to C:\Program Files\Common Files\Adobe\dynamiclink.
Close all Adobe applications.
In Windows Explorer, navigate to C:\Program Files\Adobe\Adobe Premiere Pro CS4. (If you installed Premiere Pro CS4 in a location other than the default of C:\Program Files\Adobe, then navigate to your custom installation location.)
Right-click on Adobe Premiere Pro.exe (which might appear without the .exe extension) and choose Create Shortcut.
Rename the newly created shortcut to just Premiere.
Important: The name of the shortcut must be exactly Premiere with no other characters.
Open a second Windows Explorer window, and navigate to C:\Program Files\Common Files\Adobe\dynamiclink.
Move the Premiere shortcut that you created into the dynamiclink folder.
Solution 2: Remove and reinstall all Premiere Pro CS4 components or all Adobe Creative Suite 4 components.
Do one of the following:
Windows XP: Choose Start > Control Panel > Add or Remove Programs.
Windows Vista: Choose Start > Control Panel > Programs and Features.
In the list of installed programs, select Adobe Premiere Pro CS4, Adobe Creative Suite 4 Production Premium, or Adobe Creative Suite 4 Master Collection.
Click Change/Remove (Windows XP) or Uninstall (Windows Vista).
Follow the on-screen instructions to remove all components of Premiere Pro CS4 (including Adobe Encore CS4 and Adobe OnLocation CS4) or to remove all components of your edition of Adobe Creative Suite 4.
Re-install your Adobe software.

Media Encoder crash in CS6. Could not read from the source. Check if it has moved or been deleted.

I'm having a problem getting Media Encoder to get past the dynamic link portion of encoding a time line sequence.
I can send it over to Media Encoder, but it crashes consistently after the yellow bar saying something about dynamic link.
I have CS6 installed in my computer here at work, it previously had CS5.5 installed on it.
I read some answers about CS4 having this problem and tried to create a shortcut and put it in the dynamic link folder, but that didnt work.
I would hate to have to reinstall the software here at work as the IT department is a pain- but I can't encode video on one of the computers we use here.
Any ideas on what may be happening and how I can solve the problem?
Thanks!
Its a Dell Workstation with Windows 7 Ultimate installed dualE5620 processors at 2.4GHz. .
only 6 GB RAM, and a RAID 5 hard drive setup with 3- one gb drives giving the C drive space of 1.8Gigs
Its got an NVIDIA Quadro NVS 420 video card.
I'm upgrading this computer to better work with editing video, so this is a good time to get this all cleaned up.
Im adding RAM (24GBs)- replacing the video card to a GTX 780 3GB running 3 monitors.
I'd also like to either split up the RAID (ugh)..or just add 2 internal SAS HDDs. to split up the video and the cache and the OS/programs as is usually done with editing video.
Thanks for your help in advance...
Mike

...more information...problem still not solved....
After searching more in the forums, I tried a couple more things:
I tried to restart AME and clearing the preferences. This didnt help.
I also deleted the ...appData/Roaming/Adobe/AdobeMediaEncoder/6.0 folder and all subfolders No help here either.
I also tried to import the sequence via AME rather than export via PP. This worked. The sequence loaded immediately and processed perfectly.
When I export via PP, I hit the queue button, it hangs for about 3 mins, then the yellow bar appears saying "Connecting to Dynamic Link server"
it then hangs for approx 3 mins again and then I get the Failed alert.
the error log reports:
Encoding failed
Could not read from source. Please check if it has moved or been deleted.
any help available here????

Media Encoder CS4 hangs when opening large XDCAM HD MXF files

I am having a problem with Media Encoder CS4 hanging consistently when importing large (18GB) XDCAM HD (25mbps, MPE-2 HD) MXF files. Smaller files are not a problem. This is on a soupped up system, HP XW8600 Workstation / Windows Vista Pro. The same files work fine in After Effect CS4.
Any idea what could cause this?
Thanks.
T.

Yes, I did. Thanks for the tip though.
Thierry Humeau, DoP
Télécam Films, LLC
4400 MacArthur Blvd. NW
suite 201
Washington DC, 20007
o: +1 202.298.0030
c: +1 202-255-8696
www.telecamfilms.com

Export 24 Bit Source WAV as 32 Bit Float Before Converting In Adobe Media Encoder?

Hi,
I'm exporting movies from After Effects as .avi and wondering what I need to do to preserve my audio as close to the source as possible. My source audio file is 24bit / 48K. I am using Adobe Media Encoder to encode the video/audio as YouTube Widescreen HD, but since After Effects doesn't offer 24bit export, should I export as 32bit float? And is this going to alter my audio in any way before it goes to Adobe Media Encoder?
I've read about this on some different forums, but am still not clear about it..
Thanks,
Henry

Hi Dave,
Thanks for your response. The issue that I'm running into with Adobe Premiere is that I've created "odd" frame rates in After Effects to sync my animations in "time" with my music. For this particular animation, the BPM of my music is 72.5, so I've used half of that, 36.25 FPS to perfectly line up my animation in After Effects. It locks right in with the BPM. I've tested this out on YouTube, where my videos are headed, and it works perfect. The problem is that Premiere is not using the source (After Effects) frame rate and and I have to choose from a set list of frame rates. Is Premiere limited to these frame rates? If that's the case, then I guess the only other option for me is to export from After Effects as 32bit float and test to see if their is even a difference from the source WAV. Most people are not going to be monitoring with high end D/A converters anyways, so it's probably not even going to make a difference. However, I have put a lot of work into this project and I want to deliver the best possible master.

Adobe Media Encoder Export like source size

Hey,
i´m trying to set up a custom export setting based upon HD BlueRay Mpeg setting.
My source is a custom size (1400 x 1050 px), but i am not able to change to "size as source".
Any Ideas how to change that?
THX
MArco

Marco,
You can use AME to encode a 1400x1050 M2V file.
You need to use the generic MPEG2 format (not Blu-ray or DVD) and change the Level to High. (High 1440 will also work, but it is designed for specific applications.) You will also need to set the Profile to Main or High.
The most important factor is what type of MPEG2 streams your playback device will support. That will be important for setting the Profile and Level values, which constrain the bitrate and therefore the frame size/frame rate of the MPEG2 stream. (This is what Mylenium was referring to.)
Read this for more technical detail about different Profiles and Levels:
http://en.wikipedia.org/wiki/H.262/MPEG-2_Part_2#Video_profiles_and_levels
You cannot transfer encoding presets between After Effects and AME. However, remember than you can encode an After Effects comp directly from AME without rendering an intermediate comp first. Either drag and drop the comp from AE's Project panel into the AME queue, or simply import the AE project into AME, and choose the comp you wish to render. In the next version of After Effects, this process will be much easier with the introduction of a new Add To Adobe Media Encoder command from within After Effects.
http://blogs.adobe.com/aftereffects/2013/04/whats-new-changed-after-effects-next.html
If you want to contact in-person support for AME, visit the following page and choose After Effects as the product (there is no AME option because AME is not sold separately).
http://helpx.adobe.com/contact.html

Premiere Pro CS4 Export fails with Media Encoder CS4 "Encoding Failed"," Could Not Read From Source.

There has never been a history of Adobe CS3 installation on the brand new MAC Pro I am using prior to installing Master Collection CS4, despite other posts claiming that chief cause of this issue is a previous CS3, Beta or trial installations of previous versions. I simply had a straightforward installation of CS4 and have had trouble since day 1.
I have uninstalled and reinstalled Master CS4 three times, two times with the action script cleaner for CS4. I tried changing Adobe Cache folder locations to alternative drives. I ran shift start many times to correct any inconsistencies and corrected for permissions using disk utilities repeatedly. All updates have been installed and I am still getting the same error when exporting my timeline to Media Encoder CS4, be it a large High Definition project or a small one consisting of few stills.
No matter what presets I chose, the job appears as one of the items in the render qeuee of Media Encoder CS4 and sits there with the status WAITING until i hit Start Queue. When I do, it still says WAITING under Status and at the bottom corner of the window it reads : Loading "project name.prproj" and after an average of about 6 minutes, a yellow caution sign appears. No render whatsoever takes place. When I click on the yellow caution sign, it reads a log of all errors in connection with each job, including the ones that have gone before it. Here is one:
Start of the Error Paste
- Source File:/users/myname/Library/Caches/TemporaryItems/test.prproj
- Output File:/ users/my name/Documetns/Adobe/Premiere Pro/4.0/Sequence 01.mov
- Preset used :NTSC DV
- Video:
- Audio:
- Bitrate:
0 Encoding Time: 00:33:01
Sat Mar 21 17:12:25 2009 : Encoding failed
Could not read from the source. Please check if it has moved or been deleted.
END OF ERROR Paste
Please any gurus out there know how to troubleshoot this damn thing on Mac, I really appreciate it. I have not yet encountered any posts of Mac owners with no previous CS3 installation having this issue. I am in the middle of 3 projects with tight deadlines and need your urgent help. THANK YOU!

Hello There,
I resolved the issue through a simple process of elimination. So simple in fact I wonder how I missed it. Since there has been no history of prior CS3 installation on this machine and every conceivable trick was applied to resolve the problem (refer to my original post earlier in the thread) ending in frustration, the problem had to reside in a factor or series of factors that were only present in this machine. Of the two remaining causes different in compare to other machines, I had to look into the possibility of any hardware and/or software conflicts. After all, this very same installation works perfectly fine on my colleague's Apple Macbook Pro and several Windows machines.
It turns out that I had installed Pro Tools on this machine that comes with all kinds of optional plug-ins in the so called ignition pack. One of these optional plug-ins is called IZOTOPE (three varieties include Spectron, Trash and another one that escapes my mind). They were all lite version licenses that would automatically pop up on their own when you would start a program where they had been residing. One such program where an association existed was indeed the Premiere. An annoying dialogue box directing you to buy the full version when you would start the premiere would refuse to go away. Sometimes it would even start on its own culminating in a a permanent dialogue box.
The cause of the problem was right before my eyes and I had overlooked it. Once uninstalled using IZOTOPE clean uninstaller on step 4, the problem was resolved. Projects are now loading very fast into the AME and encoding begins in earnest. I have never had any issues ever since.
Long story short, if you have any plug-ins specially the ones that are loading upon the start of any program or the ones that reside inside the premiere or the ones that start on their own independently, they could be one of the highly probable causes of this error. I have seen other similar posts complaining of plug in folders inside premiere that needed to be moved to resolve the issue for instance the ones that needed to be moved to AE folders. If you are a plug-in admirer, I would suggest to look into them seriously.
On the side note, many combination and causes may lead to the same error. I am not claiming that this is the solution for everyone.
It must also be noted that I applied the trick of creating a shortcut of Premiere (and naming it exactly as such) and dropped it into the Adobe Dynamic LInk folder (even though this was suggested for windows)and have changed the adobe Cache locations to an alternative folder on a separate drive. I haven't been able to establish conclusively if the latter steps are also essential in fixing the error on MAC but I can confirm that since the latter steps were taken before the uninstalling of Izotope plug-ins and i still had issues, probably uninstalling those plug ins or finding a way to move them to a place where they don't interfere (if you absolutely need to keep them) is the one essential step that solved the problem.
Hope this helps.

Replace source file in Media Encoder

Is it not possible to replace the source file being used in Media Encoder to encode files?
Every time I try to do this it gives me red render frames. Even if the clip is the exact same length. Sometimes ill render a master out, and then create a setup with inpoints and filenames and then relize there is an error in the master but I cannot just re-render the master with the fixes and re-use all the settings I have.
In Sorenson Squeeze I can just reset the status of the encode and it will just use the new version of the source file with no issues at all.

This is an unsupported workflow and as such your results may vary. It is very possible that in some cases this would work, but my recommendation would be to simply import the new master and apply the same preset that you used the first time. That being said, please feel free to submit a feature request if this feature is important to you: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Should Media Encoder Source Name

Hello all,
I've asked this question in another way, but I didn't get a soluton -- so I'll simplify my question....
Adobe Premiere CS4 4.21 and Media Encoder CS4 4.2.0 006 Windows
When in The Media Encoder The Source Name of the file.
Should the actual directory of the video and video file name be shown or does it show in this format: C:\Document\user\LOCALSETTINGS\temp\Sequence 01
In my case it is showing in per above -- and I think I must have mysetting wrong somewhere????????????
See screen capture. Is this "normal"?
Thanks,
...Rowby

Hi,
I think your image showed this information about where media encoder is " seeing " your "source name"....
c:\docume~1\rowby\locals~1\temp\commercial-15_3.prproj/Sequence 01
It seems to me that this part..... \commercial-15_3.prproj/ ..... is an adobe premiere pro "project name".
My impression is that you have saved your project there. After the project name is the following:
\commercial-15_3.prproj/Sequence 01
That looks to me like your Sequence saved within that project.... what you are calling the "source name ?"
I think what Adobe Premiere Pro does is it makes links to the real video and audio files you have on your hard drive and saves the information about your manipulation of the real files as code in the location you choose for your project. The project doesn't have to be in the same directory as the files you are using for video or audio, etc.
When I begin a new project it is often the default directory "c:\documents and settings\rod\my documents\adobe\premiere pro\3.0 " that is listed for me to save the project. That is the default directory (folder) that my project would be saved in if I don't choose one of my own .....
Maybe your default directory is the one you have showing above... ??? I think that is the likely reason you have that project saved in that directory.
However, it makes no difference really....where the project is saved in relation to the video and audio files you use within the project, because the project is only saving references to the source material and doesn't need to be in the same directory as that source material.
When you start a new project, look at where the project is to be saved, and you can "browse" your hard drive and save it in a folder of your choice. I usually create a folder before I start a new project , just for that project, and then choose the folder I've created to start the project there....
Hope this helps...
Rod

Mxf op1a match source Media Encoder

Similar Messages

Maybe you are looking for