Ninetto Makavejev
Forum Replies Created
-
Nope, the new version of BootCamp still hasn’t resolved the problem with SATA drivers.
My original statement still holds. XP on Apple is still not perfect and probably never will be, since Apple’s strategy has always been monopolize its hardware with its own software.
There were some people who used a rather complicated workaround slip-streaming the SATA drivers from an XP-install disk, but it didn’t work for all:
https://forums.macrumors.com/showthread.php?t=223679&page=9
regards, n.m.
-
A simpler solution to a big headache:
if all you want to do is get rid of one shot/sequence, then you don’t have to use Premiere at all, and you won’t lose any quality due to recompression: just use one of the many freeware or cheap mpeg tools to cut out the “offending” scene. I recommend WOBBLE or MPEG2SCHNITT. Then re-author, finito.
Or you could use the original DVD and set a chapter point at the offending scene, and instruct Encore to jump to next chapter (after funny-but-not-so-amusing shot)
good luck,
n.m. -
Hello,
yes, I know that frustrating feeling, but there is something fishy going on here, as quite a number of people, who know all about graphic card settings by-the-way, still cannot get PremPro to ouput full screen video overlay. Neither on CRT-monitors nor TV. A lot of end-users stretch their workspace over two screens, and think this is the same thing, but obviously it is not.
Sooo here is what I know: depending on your configuration, Premiere’s project pre-sets may or may not work. The earlier post referring to Evanbuster’s method (see Adobe’s official forum) proves this. His custom configured XML-preset was the only way I was able to get overlay output out of Premiere.
That said, there is of course the easy mistake of your playback settings being wrong. Somehow these seem to change “by themselve” with Premiere. Check them once,twice, three-times and more, to make sure Premiere is doing what you told it to do, i.e. output to the correct device.
The issue I have with people suggesting that you always should output via firewire and then into TV is simple. Firstly I do not want yet another device attached simply to convert a signal that Premiere should be able to output natively. Secondly, I prefer to see my image on high-quality computer monitors rather than mediocre TV, even if the end result will end up on TV. Thirdly, with firewire there is the annoying “LAG” effect experienced by many: even if your image/audio are in synch they do not necessarily correspond with the graphic interface within Premiere is showing you!
So those are my gripes. Premiere IS an awesome program with incredilbe flexibilty/work-flow, but like I said, these recent issues are so severe, I am willing to give up some features just so the basics at least will function solidly… i.e. I am now editing with Avid.
regards, n.m.
-
Ummmm, excuse me, but isn’t it true that Boot Camp/APPLE still has no drivers for XP controllers, i.e. that all hard drives will be run via PIO not DMA when using boot camp to run XP???
There is just NO WAY that PIO is fast enough for transferring video data.
Thus a MAC running XP via Boot Camp would never be able to keep up even with the cheapest of current PCs.Or have the APPLE people got a fix for this now?
regards,
n.m. -
Sooooooooo, one last thought on this sad issue of video-overlay problems with Premiere:
Why should the firewire-TV route be any more reliable/stable for Premiere than using the TV-ouput of a ceritfied graphic card (PNY-fx540)? In fact, I would think that the graphic card would offer much more reliable calibration of the output signal than any firewire device.
So there is still an unanswered puzzle with the “truth” that Premiere prefers firewire output.
Besides that other than using the clunky “HDV desktop method” I still cannot get fullscreen video output from Premiere, even after using every possible combination of property settings (clone/dual…etc.).But, what-the-hey, like I said, I have thus hoisted the white flag, ad
-
Dear Vince,
it is reassuring in a strange way to read your “truth-be-told” comment, because I was sure it was me to blame for Premiere’s strange behavior regarding playback output. Now I know I am not crazy.One other point though, when you say PremPro SD was designed to playout via Firewire: why is it then that the other common problem using this (preferred) firewire-route is the video-playback/audio lag which so many people experience?
I had this one too, until the confusing issue of how/where audio and video sources are outputing/inputing was more-or-less solved. I say more-or-less, since you can ask ten different people how they output the “audio scrubbing” and still stay synched with video-via-firewire, and you will get ten different answers.
And who wants to have an intermediate DV device always running, just so you can get video output?These are such basic and annoying issues which, I’m afraid, have convinced me that the FCP and AVID crowd are right. Premiere is just too eccentric/ too inconsistent to configure for serious professionals.
regards,
n.m. -
UPDATE:
Someone on the Premiere forum WAS able to partly solve the problem:
Well I kind of solved the problem, at least half way, still have some work to do.
If you make a new custom preset in Premiere using Dekstop as the mode instead of DV and then set it for standard def resolutions and whatever aspect ratio you are working in you can then set the display device to a secondary or third monitor and it will work like it does for the HD presets just click on the Playback settings button in Premiere and change the external device to whatever Monitor you want and the Aspect Ratio handling to whatever you need, basically Premiere handles the full screen video, not the cards software. It will also allow you to select aspect ratio changes such as letterboxing for 4:3 displays. Only problem I have found so far is everything that is put into the timeline no matter what has a red un-rendered bar. But it still plays fine, in fact on my new Core2 system with a pair of ATI PICe cards I am getting way more in RT this way than I was on my Matrox RTX.
The added bonus is, as I have my third output patched to my LCD TV via DVI I can use it as a third display when not in Premiere and when I am in Premiere, the SD picture is uprezzed very nicely by the ATI to 720P. So all I need to do is get it to recognise SD DV footage in the timeline as not requiring rendering and I will be perfectly happy.NOTED: the fact that standard DV-footage has to be “rendered” is still not acceptable, but you DO get full-bvideo overlay in any case. This HAS to be a Premiere Bug, I have seen this problem on too many forums!!! Premiere somehow has a problem recognizing certain monitor/card cofigurations!!!
-
Hello Blast,
Thanks for the tip…a good point there. I did use the standard de-installer for Nvidia… I had heard that removing ATI-drivers is more difficult. Which is probably going to be my next problem… After trying every trick in the book, even resetting PremPros Presets, I think I will return to my Nvidia card, which although it is lower quality that the ATI, it worked with full-size video overlay.
Somehow I think there is a serious bug here. Maybe it has to do with DVI vs VGA… ATI vs. ADOBE vs WINDOZE? Who knows. After 10 years of being a loyal Premiere-User and fighting off all sorts of snide comments from AVID and FCP- users I am sorry to say this problem is the straw which broke-the-camel’s (my)-back. I used to love Premiere and its endless flexibility. After three days with the overlay problem, the love-affair is over.
With AVID XPRESS PRO, even though the ATI-card is not certified at all, the video-overlay works perfectly, in the exact same machine that Premiere refuses to talk to, regarding video-overlay.
Off to new horizons…
-
This is the million dollar question; when/why does AAF-export from Premiere work and when does it not. My attempts at the ADOBE forum got no replies, and here the posts seem to imply that AAF-export from Premiere usually results in a mess.
My own experience: with Prem.1.5 it actually worked -for a rather small project (20 min)- as an import into AVID XPRESS PRO 5.3. I just had to re-link the Media Files. When I tried a similiar export with PremPro 2.0 about six months later: the result was garbage.
Now as to the whys and wherefores, I am afraid I can’t help you further. I guess you might have to go the trial-and-error path… something the Software Developers actally get paid to do, not end-users!
Anybody else?
regards,
n.m. -
Thanks much for your explanation.
I will check the monitor’s specs, but I do believe it has true seperate component inputs. It’s just that I have to delve thru 2 sub-menus: the one on the monitor, which is complex enough, and then setting up the FX540 outputs in the graphic-card menu(s)… I wish this was easier!
best regards, n.m.