-
APP v2.0… pain in the a*?????
Hello…
Well following error occurs on rendering: “Sorry, a serious error has occurred that requires Premiere to close…”
I reinstalled the whole xp by scratch, this error doesn’t goes off. I started the project in 1.5, and took it over into 2.0. No rendering possible, it always haltet, on any export format.
On the adobe site, nothing about, just try this, try that, maybe it may this, if not, try this… and so forth, nothing concrete!
Now I tried a render on an other ‘old’ project from 1.5, it works fine… on the actual project, the base avi makes 12Gb, does APP2 badly handles big files now?
Any suggestion welcome… the last thing I may try is to restart the project by scratch, but… will take me at least 5 hours again :/
tia
cheers
bs -
6 Replies
-
Can you give us a little more info regarding the clips you are using? Also, what project settings are you using? Where was the media acquired from?
-
hi,
well, i’m sure it’s not relevant which cam or clips I use, as it worked 100% in 1.5. Anyway, my cam is a pana NV-GS22, i importet the content through Pinnacle 8, as APP1.5 dropped all the time frames, don’t know why. Anyway, the avi file is 11gb big…
Now it works, and I explain what I did, in case it cold interrest somebody a day:
After reinstalling XP by scratch and so forth, the project from 1.5 still crashed at rendering in 2.0. So I tried last one thing, whiuch was successful:
I opened a new project, and importet all audio and video clips I used in my clip, started in 1.5. I re-created the same Sequence names (had 3 sequences).
Now I saved and closed the project, an opened the one which causes problems on rendering.
I selected all tracks on the first sequence, copied into memory (ctrl-c), CLOSED the project and opened the new one I just created before. here I pasted the tracks in the right sequence.I did this for all sequences. The only thing I had to change in the new porject, was deleting the audio tracks and replace them again, as the sound was strangely somwhat busted. Anyway, the most important to me were all effects and changes to the video files.
And now, it renders all well 🙂 – looks like that the 1.5 project had some difficulties to be accepted by the 2.0… anyway, now i’m happy, SO FAR 🙂 🙂
cheers,
bsPS: on any questions: send me an e-mail (forum.answers AT gmail.com)
-
Shut off your desktop playback and monitoring and play your video back to an external monitor only. You’re overloading your PCI bus and causing a data bottleneck. If you can’t capture without dropped frames, that might be due to the fragmentation level of your capture drive, a bad FireWire port or loose connections, slow proc or a number of other data-related proccesses that can, and will slow a great capture. Obviously, you shouldn’t try to capture to an external drive and should try to capture video to drives exclusively for that purpose. My gut screams throughput trouble however.
Michael Munkittrick
Managing Creative Director
Evolve Media SolutionsForum COWmunity leader for:
Sony DV
Magic Bullet -
hi… well, didn’t tried on 2.0, but on 1.5 it didn’t worked properly. Now tell me why I should change anything… also the drives are fast enough (100% emptied scsi-uw!). As it works 100000% under pinnacle, there is NO reason not to do same under APP….but, it simply didn’t. Anyway, that doesn’t disturb me…. 😉
thnx for feedback
-
[blacky] “also the drives are fast enough”
“Fast” is all relative to the application and project settings that you use. I can capture 10 bit uncompressed to my 320UW SCSI raid and still hav DV clips drop frames with no apparent reason. If the bus is bogged down or you are having an issue which is throughput related, you’re going to need to change your settings to find the error on your end. The truth is that there COULD be thousands of probable errors, but yours is almost certainly related to the PCI bus.
[blacky] “it works 100000% under pinnacle”
Well, that being the case, it sounds like you’ve solved your own problem…so I applaud your efforts. If one software package doesn’t work for you and you’re not interested in finding the proper settings for your machine (assuming that they exist), your options always provide the possibility of another piece of software that requires less technical savvy solving the enigma.
I’m sorry we couldn’t help more.
-
hmmmm, I feal some ironic back here… hope you didn’t understood wrong… well, i’m working with (damn) softwares now since… something over 15 years now… and, using stupid solutions, are sometimes, when it gets too time consuming on error tracking, the cheapest and best solution.
remember that stupid win95 system? I can’t remember the number of times I had to use ctrl-alt-del… even in my today’s job, there are very silly things happening. It’s a social phenomen: building fast, to sell fast and as much as possible… the bugs then belong to us, i don’t fight ’em anymore.
the frame drop on 1.5…. i “played” some times around to understand why (and i’m an experienced troubleshooter), and curiously it worked without any problem under pinnacle… so why the hell loosing time trying to find out why it doesn’t work with app 1.5 – one thing for sure: it’s not my HW at all, that’s a fact. I’m fed up of trying to understand things, which programmers didn’t worried about (i’m talking in general!) qnd left to others… that’s all 🙂 🙂
wishing everybody a good and painless work-week started…. 😉
cheers
bs
Reply to this Discussion! Login or Sign Up