I have recently updated to Aspect HD5. Several of my projects do not require using an intemediate codec so I capture using AspectHD but directly to .m2t file. I have Canon 30f footage from an H1 spread across 4 tapes and I am capturing into a 30f preset. I also tried other presets and the errors still occur.

This worked fine with version 4. However now I get the following error when inporting into CS3.

Premiere Pro has encountered an error.
[..\..\SRC\Time.cpp-105]

So now i have 4 hours of raw .m2t files that will not import into PPro Cs3.

Any ideas what this means? I know .m2t files shoud be a digital copy of what is on the tape, but something is happening. The files I already have on my PC captured using aspect HD 4 import fine. The Aspect HD 5 files don't. I tried importing in CS3 directly and the clips are fine.

The problem I have with CS3 capture is if I walk away and it gets to the end of the timecode and I do not stop it, the file becomes corrupt. In other words the entire clip is there but when PPRO trys to conform the audio it gets hung up at about 50% and then locks up for days. If I capture the same clip in PPRO but make sure to manually stop it before any time code breaks then all is well. Aspect was my tool to work around this Adobe glitch. Now I have an aspect/Adobe glitch.

By the way, neither of the issue I described occur in PPRO 2. They show up exclusively in CS3. I should just use 2 but I have a quadcore processor and the speed of CS3 is amazing! But it is so buggy!

Thanks....hope someone can help.

I removed Aspect HD completely and tested and the .m2t files import without a problem. I downloaded the lastest update (oct 4) which I had not yet applied. Guess what? It all works now!

I am not sure what the issue is but I think it may have to do with the Aspect Installer. It ran when I updated from Aspect HD 4 but it seemed to get caught in a loop of uninstalling the old version, prompting for reboot to finsih the update, and then after a reboot doing nothing more. Then when I run the setup again it asks to remove the old version, and the cycle goes on.

This time it removed the old version, asked for a reboot ( I did) and then comes back and does nothing. I ran the installer again and it asks if I want to unistall the Aspect HD. This time I say "no" and the installer finishes installing aspect 5.

Without even rebooting everything begins working the "right" way.

All is good in the end but it is not particularly clear what is going on during certain stages of an upgrade.

Peace!

One last quirk.

HDlink is reporting that it captured 0 bytes in the "captured clips area". However I can clearly find the captured files and they are of the proper size. Is this normal?

Okay. I spoke too soon. After I went and captured the last 15 minutes of tape using HDlink, I went to import it into the same exact Premiere project that imported the other four .m2t files, and it gives me the same error message:

Premiere Pro has encountered an error.
[..\..\SRC\Time.cpp-105]

This is with the latest build of Aspect and CS3.

Any new thoughts?

This is really starting to irk me!

Thanks.

A bit more info.

I can import the clips that I captured using HDlink prior to this update.

In other words I can open a new project and import the 4 .m2t files that were captured with the previous build of Aspect HD. I captured the last 15 minutes of the final tape using the latest build of Aspect HD. It will not import at all, but all the others will.

This is seriously becoming a nightmare. I need to get this work done this week and can not afford to be messing around with this. I chose to edit in .m2t instead of aspect to speed up the process (simplify it is more accurate as I do not need any of the advanced features of Cineform for this)....but somehow Aspect is messing up even straight mpg projects.

Please help! Someone.

Peace!

I am going to bed and try to forget about this until the morning......fat chance!

Same issue here with latest build of prospect 2k. Might not be a cineform issue though, as I'm working on an HDV project. Trying to import some m2t clips via HDVsplit.

Same issue here with latest build of prospect 2k. Might not be a cineform issue though, as I'm working on an HDV project. Trying to import some m2t clips via HDVsplit.

For me it is clearly related to Cineform. If I uninstall it from my system Premiere Pro Cs3 imports all of the mpg files just fine. When it gets installed, even on "non cineform" projects, I have all kinds of problems importing mpgs.

So if it is not cineform, then there is something that happens only when it is installed that caused this problem.

I have figured something out. After trial and error, I have determined that the file that is causing the problem is the Cineform Quicktime Importer.

CFQTimporter.prm is located in the cineform directory inside premiere plug-ins folder. If I delete it or rename it .bak, Premiere now imports all of my mpgs just fine.

It must tie into the import or indexing somehow. I renamed it and imported a 1 hour m2t file no problem. PPRO started to index the file and conform the audio. I save and did not let it finish indexing or conforming before closing the program. I renamed the CFQTimporter.prm back to normal and started PPRO again. When I tried to load the previous project I immediately got the error again. Premiere was trying to finish conformong this file and crashed. So I renamed it back to .bak again and loaded the project and it worked. This time I let it conform and index the entire file. After that, I closed it yet again, renamed the file back to normal and loaded the same project and it was fine.

Files that had already been conformed worked fine, however I still cannot import any new files. SO why is the CF Quick time importer affecting a standard HDV preset? I am not using a Cineform preset.

Any Idea why this is?

Thanks all.

Confirmed. It's the Quicktime importer. Nice catch Marty.

Awesome. I was experiencing this problem myself last weekend and now I'm happy to find out there's a workaround. I really wasn't sure what the problem was.

Here's hoping there will be an Aspect HD build-upgrade soon with this patch. :)

As it does not happen here, M2T file import correctly into CineForm projects, I don't think is a general fault with CineForm Quicktime Importer, which is not used for M2T files. Do the affected PCs have the latest QuickTime components (from Apple) installed? It would be nice to get to the bottom of this weirdness.

I will check the quicktime thing when I get home. I do know that I hate that Apple updater that keeps asking me to install Itunes! I always say no but I will check for the latest QT version.

I can confirm that it happens for me also. I get the same error as Marty unless I rename CFQTImporter.prm to something PPro can't read, in which case pro imports without problems. I'm using Prospect build 138.

I have the latest quicktime....build 7.2

There was a security update for it so I snagged it and rebooted but I still get the same error.

What will I be missing if I leave this file marked as a .bak file?

Marty

I just reformatted my computer and loaded a fresh copy of CS3 and AspectHD and I still need to workaround the problem by renaming CFQTImporter.prm to .bak

Does this issue plan to be resolved in a future build of Cineform, and is there a downside to removing the file entirely or renaming it to .bak?

We don't believe there is a fault in CFQTImporter.prm, as it is the same as that in PPro2. So there is some QT, CS3, M2T clash that doesn't seem to be under CineForm influence, plus it also doesn't happen here, so it is PC configure dependent. Renaming the filter will only remove deeper than 8-bit MOV CineForm support, MOVs will still work as 8-bit using the default importer.

I had this problem, then it went away the other day for no reason. Wierd? However I got a notice that there was an update to Premiere Pro CS3. I downloaded and let the Adobe installer update CS3 and when I started it the next time I got the error again. I am back to having to rename this particular file again.

Strange Days indeed. Most peculiar mama.....

i have the same issue on my two workstations.
one is on WinXP + Premiere 3.1 + AHD 5.1.2 and QT7.2
The new one is on a fresh install of Vista 32bits + AHD5.1.2 and QT7.1.5

i can't open m2t files. same error.
with premiere 3.0.0, sometimes it works and sometimes not. i have noticed that if you want to open a file that has been opened previously in a project, it fails.

maybe it's a issue QT, i remenber that when all was ok, i was with 7.1.0

Sometimes Premiere needs to refresh its plugin list (i.e. a smack on the side of it head.) Start Premiere with the SHIFT key held down until it asks for the project -- this fixed the only PC that had this problem here.

Exact David! This seems to have resolved the issue.
thanks

Sorry if I'm introducing a tangent here. I've had this same problem on my system of late, and (as I'm sure many of you have noticed) there's very little concrete information turning up if you do a google search on it. However, from what I've read, I had thought it was a quicktime issue. I had tried the latest version of Quicktime as well as Quicktime Alternative on my editing system (Windows Vista x64, by the way) and I found that I got this message and the associated problems in one form or another when either of them were installed. Hence, I'm currently running "quicktime-less," which is superbly annoying. However, Premiere Pro CS3 works GREAT at the moment so I'm hesitant to change again. That said, here's the facts and questions:
1. I have the Aspect HD trial installed, though I'm not currently using anything but the codec.
2. When I have the latest version of Quicktime or Quicktime Alternative installed Premiere will start once and then give me the time.cpp-105 error. Afterward, I cannot open Premiere at all. It just crashes.
3. When I install an older version of Quicktime Alternative I can open Premiere (though it takes forever) and edit, but it crashes a lot and won't let me import any new clips (It gives me the time.cpp-105 error when I try).

I'm sure this sounds lazy, but I really don't want to mess with quicktime again unless I can be reasonably sure of some positive results. My system is working really well right now and I'm in the middle of a big project. Hence my question:

Were I to reinstall one flavor or another of quicktime and start Premiere with the SHIFT key to refresh the plugins, as David has suggested, is it likely that the above problems will be alleviated? I would really like to have my iTunes library back, but I really need to get this project done too. Thanks in advance for your help!

I have the same issue, which I thought folks on the adobe forum
said started with cs3.1.1. But, anyway, when I unload QT, everything works.
They way if you unse 7.1.3 I think then it works. I see not solution
being posted yet.

Dave

No issue with Quicktime here. Premiere can get confused, so when Premiere starts hold down the shift key while the plugins load, this normally fixing random QT issues.

Dave Campbell,
You're right. Mine quit working when the autoupdater installed the update to 3.1.1. I had no problems before that. I'll try the 7.1.3 thing if David Newman's fix doesn't work.

David Newman,
Thanks for watching these forums, by the way. It seems that this problem really isn't your problem at all, but it's really nice to know that your company is watching out for the people using your product. That kind of thing is really appreciated. Thanks. It would sure be nice if someone from adobe could pop their head in now and then, but alas, it appears that they don't.

As for this little problem, does anyone know if it's possible to uninstall the 3.1.1 update? I had no issues before it installed, so it has definitely been a step backward for me. I haven't seen anything official from either Apple or Adobe either. It would be a lot more tolerable if there was at least some indication that this was being worked on by whichever party is culpable.

David Newman,
You're the man. I reinstalled Quicktime (latest version) and started Premiere Pro whilst holding down the SHIFT key and I now have a crash-free system once more. Life is good! Thanks a ton!

If only all bugs where this easy. We discovered this mysterous fix a couple of months ago when people where claiming our QT importer was crashing M2T clips, when to weren't related. It seems Premiere sometimes get it plugin plumbing wrong, and the shift resets this.

I had the same problem. Holding down the shift key gives me a blackscreen error message and aborts the load. Renaming the importer worked. I don't import mov files anyway.

Holding down shift worked for me too.

It's definitely related to indexing the files, I imported about 5 HDV files, after the 4th one I started getting the error and it happened every time after that.

did the hold shift on load and it's working now, thanks.

Hey everyone, sorry to resurrect this old thread again.

I know it's a QT problem w/ Cineform, because when I remove Quicktime it works fine. But then I can't run iTunes, so I need Quicktime. When I install it back, it cripples support for MPEG-2 again. I've seen this pattern many times after many reformats of my computer.

I've tried holding down SHIFT but that has never resolved it for me. Is there a particular version of Quicktime people have found is compatible? I'm running the latest now, but maybe downgrading to an older version would help?

That's what people seemed to do to resolve the After Effects bug recently (not Cineform related of course).

We know it is NOT CineForm, rather Abobe's plugin cache is calling the wrong importer in your case (maybe you shift key is broken -- only joking.) If you not using CineForm MOV files, remove CFQTCompiler.prm from C:\Program Files\Adobe\Adobe Premiere Pro CS3\Plug-ins\en_US\CineForm