Now here's a funny one. On occasion, I make MPEG1 files of rushes for clients (because its a format that any computer will play) and burn them to a CD - but Roxio has to be 'fooled' into letting me do it.
My Roxio 9 (using its Creator Classic app) will not allow a file with the extension .mpg to be selected and placed ready for burning. It brings up an error message. However, if I rename the extension as .mph (or anything else) , it will. Not only that, but it will allow me to rename the file back to .mpg once in position and then burn it.
So it's just something about .mpg file extensions that it doesn't like. These are .mpg files created from material that I've shot so there are no DRM issues. I seem to remember that when first installed, it didn't object to to .mpg files and probably if I wiped and reloaded it the fault would go, but is just very odd.
Ray L
Ray,
Would it be that if it sees a file with .mpg file extension, it assumes that it will fit exactly into one or more very precise profiles in terms of bitrate, metadata etc. whereas if it is called anything else, it just deals with it as a (potentially) non-conforming file, recompressing if necessary.
Maybe you are now feeding it with .mpg files that have some subtle deviation from Roxio's idea of standard.
Steve
Steve
If Roxio had indeed got such a tight spec built into it then its designers would have failed, because mpeg files by their nature can have a wide range of birates, etc. No, it seems to be just the extension itself that it won't accept on an incoming file. Once the file has been accepted (using my little subterfuge), Roxio will burn it quite happily. Very odd.
Ray