See the following article for more information:

http://www.osnews.com/story/23322/BREAKING_Google_Opens_VP8_Codec_Enables_it_on_YouTube

http://howto.blbosti.com/2010/03/ubuntu-9-10-compiling-ffmpeg-with-x264/

However, getting it installed on Ubuntu can be a bit frustrating (it is primarily designed to run on Fedora). The following guide includes the patches you need to get DSS up and running on Ubuntu 8.04 (and possibly later versions as well, haven’t tested that yet).

http://cwshep.blogspot.com/2008/08/darwin-streaming-server-603-on-linux.html

MediaInfo confirmed that the files were encoded with XviD, so I went ahead and re-installed the codec, making sure to get an Intel Mac compatible binary.

This did not fix the problem. Upon rebooting (probably not necessary anyway) I continued to receive the same error, and the same link to the XviD page.

Long story short, a quick install of Perian cleared up all my problems. I’m still not entirely sure what was at fault; maybe the DivX codec which I believe is a pre-requisite for XviD on Mac.

Anyway, I’ll wrap with a plug for Perian. It’s a great package of Quicktime components, and is super-easy to install. I use it on every Mac that I use regularly (somehow this one got overlooked, probably due to a recent reformatting).

Why would you choose this over the multitude of free GUI transcoding programs out there?

• Mencoder is super-fast
• Allows the process to be scripted
• Wide range of codecs
• Cross-platform compatible

Once you get the feel for it, you can append videos much quicker with Mencoder than a more “user friendly” GUI program. And, it works on Linux, Macintosh, and Windows machines, so you don’t have to learn 3 different programs if you work on multiple operating systems.

Here’s the basic format of a Mencoder append command:

mencoder -oac copy -ovc copy -o 'combined_clip.avi'
'clip1.avi' 'clip2.avi'

Simple as that. The breakdown is as follows:

• -oac
  Tell Mencoder what audio codec to use. For a complete list of options, check out the Mencoder documentation. In this case we have simply used “copy”, which will keep the current audio codec the same without transcoding (this option should only be used if the audio codecs are the same for all the clips).
• -ovc
  Tell Mencoder what video codec to use. Otherwise, same as above.
• -o
  Define the paths to input and output files. First list the output filename, then all the clips in the order which they will be appended.

Knowing this, it is easy enough to script the process. Say I have a whole directory of video files that I want to combine (ex: VID001.AVI, VID002.AVI, VID003.AVI, etc.). I could use the following ruby script to string them all together in their numbered order:

vlist = String.new()
vpath = "/path/to/my/video/directory/"
vdir = Dir.new(vpath)
vdir.each do |v|
  if v.include?(".AVI") == true
    vlist << "\'#{vpath}#{v}\' "
  end
end

cmd = "mencoder -oac copy -ovc copy -o \'combined_clip.avi\'
#{vlist}"
system cmd

Save the script as VAppend.rb and run it like so:

ruby VAppend.rb

(you must be in the same directory as the script in order to run it with the above command)

Final Notes
The command in the first code box is all one line, and the line in the second code box starting with "cmd =" is also all one line that continues onto a second for formatting purposes (in other words, #{vlist}" belongs at the end of the previous line).

Avidemux will only accept segments from up to 100 clips.

If you are appending each clip manually, there may or may not be an error message (this is not how I encountered the limit, so I’m not sure). However, if you, like me, are using scripting to append a large number of files, there will be no error message; just a crash file. This crash file will show one app.load() entry and 99 app.append() entries, and the comments will state something like // 100 Videos, regardless of how many more your script attempted to append.

My workaround was an obvious one: if I have 300 videos to splice together, I create three or more smaller videos first and then splice those together.

For example…

• Vid_A.avi = clips 1 – 100
• Vid_B.avi = clips 101 – 200
• Vid_C.avi = clips 201 – 300

…and then…

• Vid_Final.avi = Vid_A.avi + Vid_B.avi + Vid_C.avi

Of course, this takes a little longer, but when automated from the command line with another script, it’s not so bad.

If anyone else has a different tactic for dealing with this limit, please leave it in the comments.

Now, assuming that you haven’t recently dropped the player, or rubbed sandpaper across the bottom surface of the disc, this could very well be a firmware issue.

Since Blu-Ray is a relatively new format, the technology is still being refined. Some newer discs may contain data that is incompatible with earlier generations of players, resulting in playback problems.

Luckily, this is relatively easy to resolve. All you need is the following:

• Computer
• Internet Connection
• CD Burner
• Blank CD-R

First, write down the model number of your Blu-Ray player. Then look for your model on this page:

http://www.blu-ray.com/firmware/

The download link on your model’s page will bring you to the official company website (Sony, Panasonic, etc.) where you can follow their directions to download and update your firmware. This will involve downloading a zipped .iso file (disc image) and burning it to a CD, which you then load into the player and input a series of menu commands.

You should ALWAYS follow the instructions provided by the manufacturer when upgrading your firmware. Failure to follow the steps they outline may “brick” your player, effectively converting it into a doorstop / giant paperweight.

yeah, i know this is a PS3.

If you cannot find your model at the above link, search for the brand’s site directly, locate your player in the product, download, or support pages, and there should be links to firmware upgrades there.

Once completed you should be able to play the most recent Blu-Ray discs without any problem.

In this particular post I will be focusing on the latter aspect: scripting.

Specifically, I will be covering the elements and commands found in a basic Avidemux script. I am currently using Avidemux 2.4.4 on a Mac, though I routinely use 2.5.1 on Linux, and even occasionally on Windows. For those who have multiple platforms available, I recommend the Linux or Windows versions for their increased stability.

Table of Contents

• Scripting Language
• The Basic Script
• Header
• Video
• Segments
• Postproc
• Audio
• Running Your Script
• More Information

Scripting Language

Avidemux reads and writes scripts in Javascript. While basic script modifications can be made without any prior Javascript knowledge/experience, it is recommended that those of you interested in creating more advanced scripts learn the basics of the language before getting in too deep (you will only be frustrated).

Here are some Javascript concepts you might want to be familiar with.
(this is in no way a comprehensive list)

• Declaring variables
• If…Else statements
• Arrays

The Basic Script

Now, let’s get down to basics. The easiest way to start learning about Avidemux scripts is to look at one. Lucky for us (since the documentation online is pretty weak), Avidemux project files are actually just basic scripts.

So, if you want to know how to do something in a script, first try accomplishing it from the graphic user interface (GUI), then save your project, and open the project file in a text editor to see how the resulting script is put together.

For the following example, I did just that. This script simply lays down a first video in its entirety, then appends a second video.

Important: Avidemux scripts do not have an extension. Even though they are written in Javascript, do not add a .js extension to the filename or they will not work. If you can’t get Avidemux to recognize your scripts, be sure there isn’t a hidden extension (some text editors will add .txt or .rtf to the end of files that do not specify an alternate extension)

//AD  <- Needed to identify//
//--automatically built--
//--Project: /Volumes/Media_G5/Ben/Tutorials/Test_Script

var app = new Avidemux();

//** Video **
// 02 videos source
app.load("/Volumes/MEDIA_G5/BEN/TUTORIALS/clip1.mov");
app.append("/Volumes/MEDIA_G5/BEN/TUTORIALS/clip2.mov");
//02 segments
app.clearSegments();
app.addSegment(0,0,3587);
app.addSegment(1,0,2707);
app.markerA=0;
app.markerB=6293;

//** Postproc **
app.video.setPostProc(3,3,0);

app.video.setFps1000(23907);

//** Filters **

//** Video Codec conf **
app.video.codec("Copy","CQ=4","0 ");

//** Audio **
app.audio.reset();
app.audio.codec("copy",128,0,"");
app.audio.normalizeMode=0;
app.audio.normalizeValue=0;
app.audio.delay=0;
app.audio.mixer("NONE");
app.setContainer("AVI");
setSuccess(1);
//app.Exit();

//End of script

Again, this script simply loads clip1.mov and then appends clip2.mov to that. Nothing more, nothing less.

Now let’s examine the code.

Header

//AD  <- Needed to identify//
//--automatically built--
//--Project: /Volumes/Media_G5/Ben/Tutorials/Test_Script

This is the header information. The first line must always be included, as it identifies the file as an Avidemux script. The second and third lines contain additional information that can be discarded or re-written.

var app = new Avidemux();

This is the first line of actual code after the header (always). It starts a new instance of Avidemux, so you need to include it (always).

Video

//** Video **
// 02 videos source
app.load("/Volumes/Media_G5/Ben/Tutorials/clip1.mov");
app.append("/Volumes/Media_G5/Ben/Tutorials/clip2.mov");

This section loads the videos that will be used by the script. You must always have one (no more, no less) app.load() command, after which you may list any number of additional clips using app.append().

Also, these scripts do not support relative paths. You must include the full paths to the source videos.

Segments

//02 segments
app.clearSegments();
app.addSegment(0,0,3587);
app.addSegment(1,0,2707);
app.markerA=0;
app.markerB=6293;

Here's the meat of the script. app.clearSegments() clears the timeline to ensure that you are starting with a clean slate. As far as I know, there are no arguments for this command.

app.addSegment() adds the specified frames to the timeline in the order that the app.addSegments() commands appear. They each require three arguments:

• Video clip number
• Starting frame
• Number of frames to add

The Video clips are numbered in the order that they are added in the previous section. The clip referenced by app.load() is always number 0. In this case, clip2.mov is clip number 1.

The starting frame should be self-explanatory, as should the number of frames to add, though it should be noted that the final argument is NOT equivalent to the ending frame. Also, because the starting frame is the first one added, the ending frame is not equal to (startingFrame + numberOfFrames) but rather (startingFrame + numberOfFrames - 1).

For example, app.addSegment(1,15,60); would add frames 15 - 74 from clip2.mov.

app.markerA and app.markerB are optional. They can be used to select a specific section of the timeline (by setting in and out points to specific frames), but if left out then the default is to simply count the whole timeline as selected. This is very fortunate because it keeps us from having to calculate the total number of frames in every script.

Postproc

//** Postproc **
app.video.setPostProc(3,3,0);

app.video.setFps1000(23907);

//** Filters **

//** Video Codec conf **
app.video.codec("Copy","CQ=4","0 ");

This section sets post-processing parameters. I don't really know what function app.video.setPostProc() serves, but i know that it isn't necessary to include this line. I leave it out of all my custom scripts and they still function just fine.

app.video.setFps1000() sets the framerate of the timeline:

• 1000 = 1 Fps
• 23907 = 23.907 Fps
• 29970 = 29.97 Fps
• 30000 = 30 Fps

You cannot set the framerate below 1 Fps (the value of app.video.setFps1000() cannot be less than 1000).

Filters would be listed under //** Filters ** but I haven't applied any to this timeline.

app.video.codec() specifies some codec settings. I often leave this out of my scripts and simply set these parameters via the CLI or GUI when I run the script.

Audio

//** Audio **
app.audio.reset();
app.audio.codec("copy",128,0,"");
app.audio.normalizeMode=0;
app.audio.normalizeValue=0;
app.audio.delay=0;
app.audio.mixer("NONE");

I'm not going to get deep into audio in this post (you won't find anything about codec settings here), but I'll run through some basics.

The normalizeMode and normalizeValue variables can be replaced with a single normalize on / off variable like so:

app.audio.normalize=0;

Where 0 is "off" and 1 is "on". The same goes for the delay variable, which determines how much of an offset there is between the audio and the video (in milliseconds).

app.audio.mixer can take values of "NONE", "STEREO", or "MONO".

app.setContainer("AVI");
setSuccess(1);
//app.Exit();

//End of script

app.setContainer() sets your container format (imagine that!). This accepts the following arguments: PS, ES, TS, OGM, AVI, AVI_DUAL, AVI_UNP, MP4

It may actually accept more that are not documented, MP4 was one that I found through trial and error.

I am not entirely sure what setSuccess(1) does, but I leave it alone and it doesn't bother me.

If you uncomment app.Exit() it will quit Avidemux upon completing the script. This, however, is not recommended unless you add a save command before it. I have never been able to get the save commands to work reliably, so I just incorporate them into the CLI commands I use to run my scripts. That said, app.save(filename_goes_here) is supposed to do the trick.

Running Your Script

You can run a script by opening up the GUI and selecting "Load/Run Project" or with the CLI, as below:

avidemux2_cli
--run YOUR_SCRIPT_HERE --save YOUR_OUTPUT_FILE_HERE
--quit

More Information

More information on this topic can be found here and here on the Avidemux wiki.

That wraps up today's lesson on the basic Avidemux script. Soon I will be posting some more advanced tips and tricks, including elements and commands not found in a basic Avidemux project file.

If you found this post helpful, please leave feedback in the comments section below. If there is anything that you need further clarified, or that you would like included in the next, more advanced post, do the same.

As a result, the easy Get Info permissions fix was not an option.

So, I dove into the Terminal to make some repairs. A simple chmod command didn’t work either, but here’s what did:

• Open a new Terminal window
  Located in ./Applications/Utilities
• Enter the following into the Terminal
  sudo chflags nouchg /Volumes/<drive name here>
  • If there are spaces in the name you will need to put double quotes around it like so:
    /Volumes/”<drive name here>”
• Change permissions
  sudo chmod 775 /Volumes/<drive name here>

Hope that helps. Permissions problems can be a real pain.

This is done entirely with freeware running on Windows XP.

Important: If you want to modify an existing menu, another post will be made soon to clarify some of the differences.

Contents

• Why?
• Setup
• Create new menu image
• Create menu PGC
• Import menu image
• Import Subpicture
• Edit menu buttons
• Create first-play and root-menu PGCs
• Build ISO / burn disc
• Conclusion
• Sources

Why?

This tutorial is written for anyone looking to replace the menu page on an existing, already authored DVD. This is for situations in which you don’t have access to the original DVD project files (if you have access to these files you should just re-author the DVD through standard processes).

It is also for those who would like to create a menu on a DVD that doesn’t currently have one.

Setup

You will need the following programs to complete this tutorial:

• PgcEdit
• MuxMan
• VobBlanker
• DVDSubEdit
• image editor (recommended: GIMP)
• ImgBurn

Begin by copying the VIDEO_TS folder from the DVD to your harddrive.

• You may have to right-click on the DVD icon in My Computer and choose Explore in order to display the folders, then simply drag the VIDEO_TS folder to an internal or external drive.
• If the disc is write-protected you may need to use software such as DVD Decrypter to rip the VIDEO_TS folder from the disc to your harddrive.

From now on, when I refer to a VIDEO_TS folder it is in regards to a folder on the harddrive, not on the original disc.

Create new menu image

Important: The method described here requires that all buttons be drawn as part of the menu BMP image. They will be mapped later on in the process.

• Create a new menu image using the image editor of your choice
• Start with a canvas size of 720×540 (4:3)
• After creating your image, resize it to 720×480 (NTSC) or 720×576 (PAL). This will correct for the difference in pixel aspect ratios between your pc display and DVD
• Save your image as a bitmap (.bmp). You can see my example below.

You must also create a subpicture, which defines where the button highlights are on the menu image.

• Choose two colors (one for background, one for highlights). I use green and black.
• The colors you choose here have no bearing on the color of the highlighted buttons, they are simply for defining what part of your subpic image represents the background and what part represents the highlights.
• Define where your highlights will be using the highlight color on top of the background color
• Here are two examples. The first will change the color of the buttons, while the second will create a square highlight over that whole section of the menu.

Create menu PGC

• Open PgcEdit

settings addressed in this tutorial are highlighted in red

• File > Open DVD
  select the VIDEO_TS folder of your source DVD

The PGCs present in the DVD will be listed on the left side of the interface. The important distinctions (for our purposes) are as follows:

• VMGM = menu
• VTST = video track

If there is no VMGM present then there is no menu. If there is a VMGM, but you want to create a new menu from scratch, then remove it by selecting one of the VMGM PGCs and clicking Menu > Remove Menu.

• Menu > New Menu
  create a new VMGM in the PGC list
• PGC > Edit PGC
  open Edit PGC window

settings addressed in this tutorial are highlighted in red

• Create new cell
  create an empty VOB cell associated with your menu (this is the cell that we will replace with VobBlanker later in the tutorial)

Click OK to return to the main PgcEdit window. Click File > Save DVD to save changes to the source VIDEO_TS files.

Import menu image

• Open VobBlanker

settings addressed in this tutorial are highlighted in red

To begin with, you must link MuxMan to VobBlanker.

• Settings > Configure Paths
  opens the PATHS menu
• Path to MuxMan
  browse to your MuxMan.exe file and click Open to set the path.

Click Ok to return to the main VobBlanker screen.

• Input Video Manager
  select the VIDEO_TS.IFO from the source VIDEO_TS folder
• Output Folder
  select a new, empty folder to output your modified VIDEO_TS folder.
  (Optionally, you can select Use Input Folder under settings in order to simply overwrite the VIDEO_TS folder specified in the Input Video Manager. This is not recommended unless you have a backup of that folder.)
• TitleSet
  select VIDEO_TS.VOB, should be the top item in the list, then click Menu on the right hand side to open a new window

settings addressed in this tutorial are highlighted in red

• Language Units
  select the menu you want to modify from the list of languages (generally there is only one option)
• Menu PGCs
  select the PGC that corresponds to the menu you want to modify. Most of the PGCs will list 00 Cells, 00 Buttons, 0:00:00.00 Duration, —- Action, etc. These are not what you are looking for. Find the PGC(s) that have data in these categories and click Preview on the right hand side to help locate the PGC that contains the menu image you are looking to modify
• Menu PGCs > Cells
  once you find your target PGC, select it and click Cells to bring up a new window

settings addressed in this tutorial are highlighted in red

• CELLS IN MENU
  select the cell that contains your target menu image, use Prev/Cut to preview
• Still
  select your target cell and click Still to bring up a new window

settings addressed in this tutorial are highlighted in red

• I Frame Selection > dropdown
  set this to “File”. In the following pop-up window, browse to and select the BMP image you created for your new menu (not the subpic file).
  (if you set the path correctly, VobBlanker will automatically call MuxMan to process the BMP into a VOB)
• Browse
  If you need to change the file you selected in the pop-up window above you can use this button to force the pop-up window again and select a new VOB file.

Click OK then click Apply then click OK to return to the main VobBlanker screen.

• TitleSet
  make sure that VIDEO_TS.VOB lists its Action as “Process”. If not, select it and click Process on the right hand side.
• Skip
  (optional) to cut down on the processing time you can select the non-menu VOBs under TitleSet and click Skip to ignore them during processing (assuming no changes were made to the audio/video tracks)

Click PROCESS!! to create your new DVD files.

• The new VIDEO_TS files will be exported to the specified output folder. These are the files that will appear in the VIDEO_TS folder of the final DVD.

Import Subpicture

• Open DVDSubEdit

settings addressed in this tutorial are highlighted in red

• File > Open VOB File(s)
  select the VIDEO_TS.VOB file in your new VIDEO_TS folder.
• Subpic Color / Transparency > dropdown
  select “Use automatic CLUT” from the dropdown menu.
• Subpic Color / Transparency
  • set b and p to the background color of your subpic BMP (must be exact color)
  • set e1 and e2 to the highlight color of your subpic BMP (must be exact color)
• File > Replace current subpic with .BMP file
  select your subpic BMP file
• File > Save all modifications
  save your project and quit DVDSubEdit.

Important: You must set the Subpic Color / Transparency settings before importing the subpic BMP. This is how DVDSubEdit knows which elements of your BMP represent the background and which represent the highlights.

Edit menu buttons

• Open PgcEdit

settings addressed in this tutorial are highlighted in red

• File > Open DVD
  select the VIDEO_TS folder of your source DVD
• PGC
  select the VMGM that you created at the start of the tutorial.
• Menu > Show/Edit Menu Buttons or BOVs
  select the target VMGM on the left hand side then click this menu option to bring up a new window

settings addressed in this tutorial are highlighted in red

Create / modify buttons:
This will show you how to map buttons on your BMP image. It will not allow you to create new visual images, but simply to define the areas occupied by image elements that are intended to be buttons. This is similar to creating image maps in HTML.

Also, by defining rectangular areas for the buttons, any part of the subpic image that is within a rectangular boundary will appear as a highlight when that button is selected.

• Edit
  The first time you click this it will ask if you want to create a new button, say yes.

settings addressed in this tutorial are highlighted in red

• Button > New button
  create a new button. Use this to create all the buttons you need, you can edit the parameters of each by toggling between them with the Edit button slider.
• X position / Y position
  set the horizontal or vertical position of the button
• Width / Height
  resize the button to fit your background image
• Adjacent Buttons
  set what button will be selected if a given arrow is pressed on the remote (generally, set position 1 to the button above or to the left of the selected button, position 2 to the button to the left or above the selected button, position 3 to the button below or to the right of the selected button, and position 4 to the button to the right or below the selected button)
• Use color scheme
  set this to 1 for all.
• Edit Color Schemes
  click this to bring up the Color schemes Editor window.

settings addressed in this tutorial are highlighted in red

• Color for Selected button
  you only need to edit these colors for a basic menu.
• Background and Pattern > Contrast (Opacity)
  set the Contrast (Opacity) of these to 0. Color doesn’t matter.
• Emphasis 1 and Emphasis 2 > Color index in PGC lookup table
  set these to the highlight color of your choice (both should be the same, though I think Emphasis 1 is the active one).
• Emphasis 1 and Emphasis 2 > Contrast (Opacity)
  set the transparency of your highlights.

Click Ok to return to the Menu Editor window.

• Click it to open the Command Editor.

settings addressed in this tutorial are highlighted in red

I am assuming in this case that you are simply targeting video tracks with your buttons rather than other menus.

In the Command Editor:

• Jump to… > VTST Title > JumpTT
  select this to target a video track
• Jump to the entry PGC of title
  enter the number of the VTST that contains the video track you want to target. To find this you may have to return to the main PgcEdit screen and preview the VTST entries on the left hand side by selecting them and clicking Preview > Preview PGC

Click OK and OK again to return to the Menu buttons window. Now repeat the above steps (from Create/Modify buttons through to here) for each button on your menu (creating new ones as necessary).

When you are finished editing the menu buttons, save your changes with File > Save DVD.

Create first-play and root-menu PGCs

This step is only recommended if you have added a menu to a DVD that previously had no menu.

This will make the DVD start out on the new menu, and return to it when you press the menu button during the video.

• Keep PgcEdit open
  or re-open it if you closed it after the last section (and load your project)

settings addressed in this tutorial are highlighted in red

• VMG, First-Play PGC
  select the first-play PGC. This will be the first PGC in the list, and is always present because PgcEdit will add it if it is not.
• pre commands
  the right hand window will show the current first-play commands, probably something like “(JumpTT) Jump to Title 1″. This means that the DVD will begin by playing the first video track. Select this command
• Edit Cmd
  this will bring up the Command Editor window

settings addressed in this tutorial are highlighted in red

• Jump to… > VMGM Menu > JumpSS-VMGM-pgc
• Jump to VMGM PGC
  enter the number of the VMGM PGC that contains your new menu (this is the VMGM PGC that you modified earlier in the tutorial)

Click OK to return to the main PgcEdit window.

Each video track (represented by VTST in the PGC menu) should have a corresponding VTSM. Some may not, in which case you will have to add them.

To add a VTSM to a VTST, select the VTST and click Menu > New Menu. Do this for each VTST that doesn’t have a VTSM directly preceding it in the PGC list.

By default, newly created VTSMs should contain the following pre command: (JumpSS) Jump to First Play PGC

Check each of your VTSMs, if their command looks like this then you can leave them be (pressing the menu button on the remote will repeat the first-play action, which we already set to the menu).

If a VTSM contains different commands, select it and do the following:

• Edit Cmd
  this will bring up the Command Editor window
• Jump to… > First Play PGC > JumpSS-FP

Click OK to return to the main PgcEdit window.

When you are finished editing the VTSMs, save your changes with File > Save DVD.

Build ISO / burn disc

• Open ImgBurn
  Upon opening, select “Write files/folders to disc” or “Image file from files/folders” to start a new project. Alternately, select Build from the Mode menu.

settings addressed in this tutorial are highlighted in red

• Source
  select the folder you set as the output folder in VobBlanker (this is your new VIDEO_TS folder). You can also set this through the File menu.
• Destination
  select ISO file or Disc as target using the Output menu, then select the specific ISO location or Disc in the Destination section of the interface
• Labels/Advanced
  You can also change some of the other settings on the right hand side, particularly under the Labels and Advanced tabs. These will allow you to make changes to the disc metadata such as the disc label that will appear by its icon on your computer. You can even force specific creation/last-modified times. Of course, all these right-hand settings are optional.

Click the Folder > Disc/ISO button to build.

• If ImgBurn builds without errors then you have successfully created a new, modified version of your source DVD (either in disc or .ISO format).

Conclusion

There is certainly a lot more you can do to modify existing DVDs. You can create submenus, create motion menus, remove the menus and/or autoplay the main video, modify subtitles, loop videos, combine multiple DVDs, and even add brand new audio/video content (which you will then need to create new menu buttons for).

If any of these topics, or related ones, are of interest to you, drop me a line at ben@backstar.com and I will see about putting together another tutorial.

If you have a project that you need assistance with, please let us know via my e-mail (above) or the Contact-Us section of our site.

Sources

• http://backstar.com/blog/2009/09/01/edit-video-on-an-existing-dvd/
• http://forum.doom9.org/showthread.php?t=99306
• http://wencas.profitux.cz/downloadmonitor/download.php?nazev=replace_menu_2&url=http://wencas.profitux.cz/vid/replace_menu_2.rar