GearShift Problem

InterceptPoint wrote on 2/16/2008, 5:47 PM
After working flawlessly during the 30 day trial period I suddenly find that GearShift isn't working anymore.

It will create the proxy files just fine. Input files are:

0001mts
0004mts
0005 mts

And the proxy files that are generated are:

GSP0001.avi
GSP0004.avi
GSP0005.avi

But shifting gears from the .mts to the proxies fails. I get an error message:

GearShift Error: "No Media Files Were Replaced"

I've now seen this with two different projects.
Any ideas?

Comments

JohnnyRoy wrote on 2/17/2008, 5:55 AM
It depends on what options you are using. There are three modes in which GearShift works and they have different options/restrictions.

Please open the about box by clicking on the VASST logo and click the Contact Us link to send ultimatesupport an email on the problem. Give as many details about what you are doing as possible to help us try and recreate the problem. A screen shot of the options you have selected will also be helpful.

I would be surprised if the proxies are named GSP0001.avi since the GSP prefix should have an underscore in the name like this: GSP_0001.avi. (or perhaps that's your problem). Anyway send us an email and we'll help you get it sorted out.

~jr
InterceptPoint wrote on 2/17/2008, 10:37 AM
You are right about the underscore. They are there.

I am generating the proxies using the media folder option.
The original files are in a Capture subdirectory.
These files are in a Media Subdirectory called AVCHD
The proxies get generated and added to the Capture subdirectory and show up in the Media Subdirectory
I am running in proxy only mode. Not generating the Intermediaries.

That all works. It just won't switch.

What other options are there that I should worry about?
JohnnyRoy wrote on 2/18/2008, 11:47 AM
Are the original media files and the proxy files in the same directory? They must be for the swap to work.

~jr
InterceptPoint wrote on 2/19/2008, 4:04 AM
Yes. The files are in the same directory as the originals.
Laurence wrote on 2/19/2008, 5:26 AM
I thought I would just mention here that Gearshift doesn't recognize the "m2ts" extension which is often used for AVCHD clips. For instance, if you have a Sony AVCHD camera and use the VRD-MC5 to burn AVCHD discs of the footage, the extension on all the clips will be "m2ts" and Gearshift will not work on these clips until you change the extension.
Laurence wrote on 2/19/2008, 5:31 AM
It sounds like a naming problem. In the first post, there is no "." between the file name and the extension. Most likely this is just a typo, none-the-less, check the exact syntax of your file names. Windows could be hiding the real extensions as "common extensions" and if that was the case, the "mts" you see in the name could be part of the prefix and not the suffex like Gearshift expects.
InterceptPoint wrote on 2/19/2008, 1:21 PM
I guess I was just in to big a hurry to type the right filenames. Here they are correctly:

Input files
00000.MTS
00004.MTS
00005.MTS

and Gearshift generated files

GSP_00001.avi
GSP_00004.avi
GSP_00005.avi

Note: Gearshift also generates a set of .sfk files and a set of .sfl files as well, one each for each .avi file.
JohnnyRoy wrote on 2/20/2008, 6:48 AM
> I thought I would just mention here that Gearshift doesn't recognize the "m2ts" extension which is often used for AVCHD clips.

Yes it absolutely does! M2TS support for AVCHD was added in version 1.7.1. We (VASST) have done a poor job of advertising the free improvements we've made to GearShift over time.

Laurence, Make sure you have the latest version of GearShift 1.7.1. It now supports AVCHD. If something about it doesn't work, let us know so we can address the issue.

~jr
JohnnyRoy wrote on 2/20/2008, 7:11 AM
> and Gearshift generated files

It is impossible for the last two filenames to have the same name. Windows won't allow it. Based on the filenames 00000.MTS, 00004.MTS, & 00005.MTS you should have GSP_00000.avi, GSP_00004.avi, & GSP_00005.avi. I don't know where a GSP_00001.avi would have come from.

Have you tried using the Filesystem option? If you are trying to make proxies from whole files, this is the best method to use (and the way most people use GearShift). I have tried to recreate you problem but I cannot. I created three files called 00000.MTS, 00004.MTS, & 00005.MTS and placed them in a media bin, I generated proxies from the media bin, placed them on the timeline, and then swapped back and forth several times with no problems.

It would be really be helpful if you could contact our support and send some screen shots or even the VEG file so that we can try and recreate your problem. Step-by-step instructions on exactly what you did would be very helpful. Also include what version of GearShift and Vegas you are using so we can test with those.

~jr
Laurence wrote on 2/20/2008, 8:31 AM
>Yes it absolutely does! M2TS support for AVCHD was added in version 1.7.1. We (VASST) have done a poor job of advertising the free improvements we've made to GearShift over time.

You missed what I am saying. Gearshift works wonderfully well with AVCHD clips, but only with the "m2t" extension. If your AVCHD clips have the "m2ts" extension, Gearshift currently doesn't recognize this as an AVCHD disc file type and won't swap out the files.

Here is how this affects me: I shoot video with my CX-7. If I transfer the clips from the memorystick, the clip extension is "m2t" and Gearshift works exactly as it should. If however, I copy the clips to a DVD-R using my VRD-MC5 and it's AVCHD disc copy mode, the extension on the clips is changed from "m2t" to "m2ts". When I copy the clips from the disc to my hard disc for editing, Gearshift won't recognize the new extension as a valid and won't swap out the files. I get around this by using http://www.snapfiles.com/reviews/Bulk_Rename_Utility/bulkrename.htmlthis[/link] excellent batch file rename utility. It would be better however if I could just swap clips with an "m2ts" extension directly though.
InterceptPoint wrote on 2/20/2008, 9:46 AM
My apologies to anyone trying to follow this thread for screwing up the file names not only once but twice.

OTOH, as noted by Laurence, the problem is with the filename extensions. In my case I simply copy the files from a memory chip in my CX7 to a folder. This yields files with .mts extensions. Gearshift processes these just fine into the corresponding .avi files but apparently doesn't recognize the .mts when it comes to swapping them back and forth. I changed .mts to .m2t and everything works just fine.

BTW, this .mts to .m2t extension switch worked even after the Gearshift render. You have to shut down the project, make the change in Explorer and then open up a new project with the .m2t version of the original .mts file and the Gearshift .avi in the same subdirectory and the switch works fine.

It would seem to me to be simple for the Gearshift team to fix this. They just need a few lines of code in the swap routine to look for the other legit file extensions before they declare an error and no-swap.
JohnnyRoy wrote on 2/20/2008, 10:27 AM
> It would seem to me to be simple for the Gearshift team to fix this.

Yup... and you're talking with him right now. ;-)

OK, I see what's going on now. I did my test with .m2t files but you are talking about .mts files. GearShift 1.7.1 is not looking for this extension. I will modify GearShift to look for .mts extensions and then all should be OK. Unfortunately I cannot make this change until tomorrow because I'm on the road today and don't have the proper environment on my laptop to make the change. :(

I'll report back in this thread tomorrow when GearShift 1.7.2 is posted. Thank you both for helping resolve this.

~jr
Laurence wrote on 2/20/2008, 10:55 AM
FWIW, there's .m2t .mts and .m2ts

Have I missed any?
JohnnyRoy wrote on 2/21/2008, 10:45 AM
> FWIW, there's .m2t .mts and .m2ts

...and GearShift 1.7.2 supports all three in any combination. ;-)

OK, the updates have been made and tested. GearShift 1.7.2 is now available from the VASST web site. It now supports HDV *.M2T, ACVHD *.MTS, and *.M2TS files as source to be converted to Intermediary Cineform or Sony YUV or to DV Widescreen proxies.

InterceptPoint, Please let me know if this does not fix your problem. Sorry for any inconvenience this may have caused you and thanks for your patience and perseverance in helping me figuring this out.

~jr
Laurence wrote on 2/21/2008, 1:33 PM
I upgraded my computer with the idea of not needing to use Gearshift anymore, but am finding that I miss the absolute smoothness of proxy editing. Thanks JR.
InterceptPoint wrote on 2/24/2008, 6:15 AM
JohnnyRoy wrote: "Please let me know if this does not fix your problem."

Finally ran the test with version 1.7.2 and it works just fine.

One of the great luxuries of life is being able to talk directly to your local software developer and have him actually answer you and help fix your problems. It really doesn't get any better than that.

Thanks again.
Laurence wrote on 2/24/2008, 10:39 AM
IMHO, Vegas with Gearshift is the only practical way to edit AVCHD footage right now. This latest update seems to be working perfectly. Well done JR.
JohnnyRoy wrote on 2/24/2008, 4:29 PM
Thanks guys. Glad it's working well now. If you have any issues you know where to find me. ;-)

~jr