• Most new users don't bother reading our rules. Here's the one that is ignored almost immediately upon signup: DO NOT ASK FOR FANEDIT LINKS PUBLICLY. First, read the FAQ. Seriously. What you want is there. You can also send a message to the editor. If that doesn't work THEN post in the Trade & Request forum. Anywhere else and it will be deleted and an infraction will be issued.
  • If this is your first time here please read our FAQ and Rules pages. They have some useful information that will get us all off on the right foot, especially our Own the Source rule. If you do not understand any of these rules send a private message to one of our staff for further details.
  • Please read our Rules & Guidelines

How to set up your files to fanedit: A community resource

DigModiFicaTion

DᴉმWoqᴉԷᴉcɑꓕᴉou
Staff member
Faneditor
Messages
8,607
Reaction score
3,504
Trophy Points
168
I don't know about anyone else, but I often find myself forgetting the particulars of how I set up a project to edit. I thought it might be a good idea for those of us who are forgetful as well as those who share similar NLE's, hardware, etc. to share our project work flows and processes. I know I've recently switched up due to seeing other editors describe what they do. So post away.
 

DigModiFicaTion

DᴉმWoqᴉԷᴉcɑꓕᴉou
Staff member
Faneditor
Messages
8,607
Reaction score
3,504
Trophy Points
168
Programs Used
Vegas Pro ($)
MakeMKV (free: rip blu ray discs, makes 1:1 copies)
tsMuxer (free: create .m2ts files, can separate video and audio files from most video formats)
avidemux (free: transcode or repackage/recontainer a video file)
TunesKit (~$40: Remove DRM protection from iTunes video files)

Task: Converting a Blu Ray disc to a file that's compatible with Vegas Pro/Movie Studio Platinum
  1. Blu Ray Disc
    1. insert into BD
  2. MakeMKV
    1. analyze disc
    2. select video files
    3. Deselect audio tracks & subtitle tracks not wanted
  3. tsMUXER (can skip this step and use MKV is desired)
    1. drop mkv file into program
    2. MUX a .m2ts file with the video and audio file desired
  4. avidemux
    1. Drop .m2ts or MKV file into program
    2. Menu > Audio > Select Track > select track and set the settings to AAC (LAV) and match the bitrate of the file (you can find this using the program mediainfo)
    3. Video settings (found on left side)
      1. (copy)
    4. Audio settings (found on left side)
      1. AAC (lav)
      2. configure (set to desired bit rate and hz)
    5. Output Format
      1. MP4 Muxer
      2. Make sure to
    6. Save file
  5. Drop file into Vegas Pro
Task: Converting an iTunes DRM protected file into a file that's compatible with Vegas Pro (should work for any NLE)
  1. Make sure you are using iTunes version 12.9.0.167 or less
  2. Set iTunes to download full 1080p movies
  3. Download movie in iTunes
  4. Once movie is downloaded, close iTunes
  5. Open TunesKit (this will trigger iTunes to open again)
  6. Select "Library" at the top menu in TunesKit
  7. Select the movie from the list and click "Add"
  8. Select the audio tab and click "No Audio" then click on it again and select the channel you would like to convert (I select the 5.1 surround mix)
  9. Format (found at bottom left corner)
    1. Defaults are M4V Lossless and MP4 Lossless
    2. If you are using Vegas you'll want to make sure to configure the format to the following
      1. MP4 HD
        1. Video:
          1. Codec: Auto
          2. Resolution: Auto
          3. Frame Rate: 23.976
          4. Bitrate: Auto (iTunes videos are encoded in 6mpbs so the lowest setting is the best you're going to get)
        2. Audio
          1. Codec: AAC
          2. Channel: 5.1 surround
          3. Sample Rate: Auto unless you want it at 48000 hz
          4. Bit Rate: 320kbps
  10. Choose the output folder
  11. Click Convert
 
Last edited:

ClarkWayne

Active member
Messages
32
Reaction score
32
Trophy Points
23
I have some file structure and file storage insight/advice for anyone getting started. Any video edit big or small can quickly and easily balloon out of control in both the edit project file and especially on your hard disk. While I don't always follow the best practices myself, I did learn them from a Hollywood VFX specialist.

1. Develop a naming convention that you use for all of the files in your edit. This is absolutely the most important thing to get into a habit with. Regardless of folder structure, you should be able to look at the filename of a particular file and know exactly what it is. If you truly want to develop a professional habit with naming files, DO NOT USE SPACES in your filenames. Spaces in filenames do not always translate the same across operating systems or rending software.

I use something similar-ish to this: mediaType_shortDescription_identifier.ext
mediaType =
Music/Sound/Video/Graphic....etc.
shortDescription = Keep it simple. "ThorDVDrip"
identifier = this can be many things, but you should keep things consistent. The identifier will help you tell that file apart from other versions or copies of the same file. For example "graphic_supermanLogo_red.png" or "projectFile_jumanjiRedux_v03" If you use a number in any part of your filenames, get into the habit of using at least a double digit number. If you start naming with single digits - "version_1" - by the time you get to version 10, you will no longer be able to sort the files in chorological order as "10" will be placed before "1" when sorted in ascending order. So just get in the habit of using "01" or "001" it will make things much easier for you when you find yourself digging for a particular version of a project or file.

2. Use the same project file structure as your folder and file structure on your hard drive. Most editors allow you to import media and organize them into bins or folders. Mirror the folder structure of your storage location. You will find that you are going to be storing and importing more media into your project files than you will actually end up using. If you use the same structure in your project file that you do on your hard disks, it will be very easy to prune your storage location when it's time to archive the project. Or, if you need to migrate the project to a new storage location or to share with someone, you will be able to give them exactly the files necessary vs. the whole mess of things you have downloaded/created/rendered over the course of the project.

3. Data storage tips: If you have more than one hard drive on your computer, you will find that storing all the project media on one hard drive and outputting your renders to another hard drive will usually give you a bit of a speed boost in your render times. Always, always, always backup your stuff. If you really value the work you have been doing, you should be backing up to a different storage location regularly. I don't always do this myself and I almost always regret it. You aren't just combatting file corruption, you may sometimes find that you get your edit sideways by mistake and need to restore from a backup. If you are strapped for space, make sure the project files are backed up first. You can always re-rip a dvd or a soundtrack and then relink the project file. Finally, do not use networked storage for active project files. Most times I find people know this already, but it is worth mentioning. Your renders will suffer hard, even if it's a local network and you are hardwired.
 
Top Bottom