Ron Moody
Forum Replies Created
-
After looking deeper, it appears that only rendered segments are bad. If a title sits over video, the video before and after the title is fine, but during the title overlay, it’s like it’s running at 20fps. On the credit roll for example, the video and credit roll are not smooth, and in two places in the 25 second roll, it actually jumps like it missed a few frames or something. It’s on a 400 gig drive and of that, 25% is free.
Stranger and stranger.
I’m re-installing now.
-
Thanks, but no, I haven’t changed any of that. I dumped the main content into an older project and am rendering the credit roll now. News in seconds…
Not only is the credit roll not smooth, it actually jumps in two places. I am at a total loss. My deadline was two days ago and I’m still no closer to fixing the problem. It should have been to the caption people on Tuesday and today is Thursday (my day off, and I’m sitting here, sigh).
Oh well.
-
Not an authority but XP sometimes misses my external Maxtor 160. Strange, but I’ve noticed that sometimes it takes on a drive letter from another drive on the network that isn’t attached at the moment.
Sometimes the drive doesn’t show up at all.
On occasion I yank the USB cable in from the printer and plug it into the Maxtor, XP wakes up and sees the drive.
Yes, two separate behaviors, equally strange. I’ve never queried the Windows XP knowledgebase. I guess I just figure that as long as I can fool XP into seeing the drive when I need it to, I’ll just let it go.
ron
-
Maybe it’s just me ranting, but I took a project from Win2k/Premiere 6 and copied it to the computer running XP/PPro1. The computers were identical except the Win2k/Premiere6 PC had 256KB less RAM.
The XP/PPro1 computer took almost exactly twice as long to render the project as the Win2k/Premiere6 one (again, identical source files).
XP mostly works but doesn’t do anything especially well in my opinion. Each version since Win2k is slower, more bloated, and more resource hungry.
In essence, it takes but doesn’t give.
Rant over.
ron
-
Update:
I went to a previous week and checked the scroll at the end of the show. It played fine. I still don’t know what is causing it, but I plan to copy the previous week’s project and turn it into this weeks. We’ll see if it works. I’m wondering if it might have something to do with temp files, or maybe something got corrupted somehow.
-
Wow, that was great! Thanks for the link.
As I suspected, the Beta deck should be set to peak at zero dB on both tone and program. Jumping into Premiere, this means that tone must be about 7 dB below peak program, which everybody seems to agree, should be set to about -20dB within Premiere.
It also appears that somehow Premiere got it wrong in setting tone at -12.
What I still don’t understand is why, when bars and tone are set to a reference level… the same level in Premiere, that the 1800 still reads bars as 7dB louder, even though Premiere says they’re the same level.
I guess I’m willing to leave that as a mystery.
Thanks for the great input though.
rm -
Dave,
You say that Premiere should NOT exceed -9dB. I accept your statement but where does it come from? Is it part of the industry standard, or your experience, or a page in the manual that I missed? You say it with authority so I know you got if from somewhere but am curious as to its source.
Second, in my experience to date, tone and program within Premiere differ by 7-8dB. Your settings present an 11dB differential. I haven’t tried it yet, but is this what your experience has led you to set as standard levels?
I’m really curious about the peaks at -9dB thing.
rmPS: To an earlier post, my tone was set at -7dB in Premiere and program at zero (which I now understand is wrong.) Although I haven’t heard any distorition with levels set there.
-
I hear you, but I still don’t understand.
Premiere Pro’s meters say that BOTH tone AND program material are at zero dB. As such, you would think that it would output BOTH at the same level. But that is not the case. Tone outputs at 7 or 8 dB hotter, but only on the Bets’s meters, PPro says everything is at zero.
That’s what I don’t understand. If you are banging your head against the keyboard now, saying “He just doesn’t get it!” You’re right. I don’t get it yet.
rm
-
Unless I missed something, no-one has yet addressed the real issue (at least in the way I see it.)
Once the audio goes into Premiere, it’s digital. Tone, program audio, whatever; it’s all digital.
So then, why is the tone presented by Premiere at 7 (or 8) dB higher than program audio.
And even more important, why, when you zero the meters inside of Premiere, does tone come out 7 or 8 dB HOTTER than program?
I understand about mixers and -10 / +4db. But that doesn’t address the issue above.
I still don’t get it.
RM
-
Wow, you guys are on it! Here I was just venting and I get all these great suggestions in response. Thanks.
Yes, auto save is on, I forgot about it, but it didn’t help in this case. I just finished tweaking a title when it crashed and I was frustrated in wasting the time invested.
Honestly, PPro2 hasn’t crashed much in the titler; twice that I can think of over the last few months, but both times was a waste of my time, and it was time that wouldn’t have been wasted with the prior version’s implementation of titles (as separate files rather than folded into the project file.)
Related to a later post, I tried flipping back and forth between AFX and PPro once but the computer bogged down so much that I jumped the tracks on the “Get it done and move on” kind of project that I seem to do a lot of. It’s likely that I’m attempting this on an underpowered PC (3.2Gig with a gig of ram). I’ve considered investing in a dual processor with a couple gigs of RAM, but I’ll still be stuck with XP which is so wasteful of resources anyway that it seems kind of pointless.
Now if I could do it on Win2k, then it would be worth the investment. Alas, PPro and the rest of the bundle won’t run on Win2k.
Oh well…
Thanks though guys for the input. I sure appreciate it.
Ron from Maui