This content has been marked as final. Show 18 replies
The error refers to constructing a time value with a framerate of zero, which is illegal. Try importing the clip into a fresh project, let me know if it still comes in with the wrong framerate.
Since it's an MPEG, it has to be indexed by Premiere - you could also try to force Premiere to regenerate the index file. If you look under Preferences - Media, there's a path listed for the location of the Media Cache. Either use the 'Clean' button, or (as I prefer to do, just in case) navigate to that directory and blast the contents.
Thanks Wil - it worked :-)
Umm... which one worked? Importing into a new project or cleaning the Media Cache?
both, your suggestion for cleaning the Media Cache and the import of the M2T file in PPro CS3
Okay, I have the same failure. I have a new project.
I cleaned the media cache. No change. I then blew it away, no change.
Any other ideas?
OK, I have the same problem. Cleaning didn't help. This didn't happen before the last upgrade.
I captured with onlocation and now the file won't import into CS3.1.1
I found I can't capture directly into Premiere also. The capture seems to go smoothly, but when I try to save and stop capturing, Premiere has a problem. The file is actually saved but won't import into Premiere. It's that 105 error.
The file will play fine on VLC or in onlocation itself.
Also, Now bits and pieces of Premiere won't close. I thought I'd closed it but XP insists Premiere's not responding and I "end now".
Just this last time it said the Photoshop Server was not responding. I hadn't even opened Photoshop.
HP Pavilion a1240n
Photoshopserver.exe seems to only run when there's a .psd linked in your project.
OnLocation captures files that Premiere won't import????
Is this a bug or a design by Adobe?
Certainly not by design. Brad, any chance you could do a small clip capture (30 frames or less would do it) and upload it somewhere so I could take a look?
elmu Are you using any Cineform product?
I have Aspect. Sometimes I use it sometimes not. If I have to export a bunch of stills, I prefer to create a HDV project without Cineform first because the stills can be a bit cleaner. Then I create another project and use a Cineform avi from HDlink to edit.
Is there a problem with using both?
Is this the same problem discussed in this thread...
... and does this solution work?
" Okay, I have the same issue. I have no CF loaded.
But, I had QT 7.3. I removed this, and now the m2t file loads.
Anyone know root cause since I would like to put quick time back. "
Did the same thing, Dave, no change here either. Can we get our money back?
So is Cineform the culprit here or Adobe PP? Their Tech-heads better come up with something soon. I'm about ready to dump them.
Likely Dell is the culprit. My system was never so "dirty" as when I first bought it from Dell. I had to clean so much crap that they pre-loaded off the system that I finally gave up and re-formatted the drive, installing just Windows and my hardware drivers (which were all in need of serious updating, even on my brand-new system).
Then I installed my mission-critical apps, including the Adobe Production Studio.
I've been humming along great ever since.
Read you post, as far as software/hardware...it's been really getting my behind on my projects. Now you're saying its the Dell system. I can remember being really happy, finally getting the Adobe software. Thanks for the heads-up on the Dell and having to re-format, wow, that's drastic measures. Now I would have to start these projects all over again, oh man, talk about getting behind on things. Tanks for the advice. vinney
Save your projects and your media on a separate drive (or at least a separate partition) before you reformat. That way you won't have to start everything from scratch *unless* the project and/or media files already contain some corruption that will make the errors persist.
However, starting with a fresh project on a freshly reloaded system should make your editing life much sweeter.