[Mike Velte]

One of my peeves as well…choose Window>Workspace>Reset Current Workspace and then open the Titler.

[Mike Velte]

Try experimenting with the other 2 Desktop Display Modes…click on the wing menu button in the upper right corner of the Program window and choose Playback Settings.

Failing that, dig into your video cards display properties settings, specifically overlay options.

[Mike Velte]

While I agree that controlling quality with H264 and 2 pass VBR can be daunting, your “target bitrate” determines the resulting file size. The Target bitrate plus audio can be used to accurately predict the size of the resulting file.
Having too low of a Maximum Bitrate can result in pixelated high motion scenes and too high can result in poor low motion scenes.

[Mike Velte]

It is likely you have distorted the timeline, hiding the video tracks. Hover your mouse just above the words “Audio 1” at the left end of the timeline. When your mouse is between the top of the audio 1 track and the bottom of the video tracks your cursor will change indicating you can reduce the height of the audio tracks and make the video tracks visible.

[Mike Velte]

Pick up a copy of Premiere Elements 4. It edits mpeg and other consumer formats much better than CS3.

[Mike Velte]

Try configuring the tascam as the default device in Windows Control Panel (Sounds and audio…) first.
Use the Audio tab of the “Sounds and Audio Device Properties” window to do this. Also select “Use only default devices”.

[Mike Velte]

With a little use of Windows Calculator you can calculate any bitrate.
The basics are;
1. The size of video files sitting on your hard drive or this upload limit you have in question are measured in kilobytes, megabytes and gigabytes. Emphasizing BYTES.

2. The amount of data in one second of video or audio (or both) is measured in kilobits or megabits. Emphasize BITS.

3. 8 bits equals 1 byte.
4. Kilo=1,000 Mega=1,000,000

Note; bitrate is expressed as mbps megabits per second) or kbps (kilbits per second). Example; a good DVD bitrate might be 7 mbps or 7000 kbps (both are the same).

Ok, now for real life calculations. Your limit of 500 megabytes weekly involves plugging in one of 2 unknown values- the length of video in seconds OR the amount of data per second.

Lets begin with the unknown bitrate and plug it in as 500 kbps (which is ok for folks on a cable connection and half resolution-480×360). At some point in any of these calculation one must convert bits to bytes. 500 kilobits equals 62 kilobytes.

500 megabytes (500,000,000) (your limit) divided by 62 kilobytes (62,000) equals 8064 seconds OR/134 minutes.

So we can say if your total bitrate (video+audio) is 500 kbps, your 500 megabyte limit equals 134 minutes.

Now it does not make much sense to plug in duration as the unknown because the longer duration is, the lower the bitrate is and I guess you would like to have decent looking video.

In conclusion and in general, a good place to start is 500 kbps= 134 minutes. Twice that (1000 kbps) would be good for full resolution video and audio and half of 134 minutes.

[Mike Velte]

From the Adobe forums;

https://www.adobeforums.com/webx/.59b4f4af/2

[Mike Velte]

Ahhh, the old Canopus reference file disaster. Your problem is not Premiere, but the way Canopus creates video files…they are not self contained files like MS.avi. Each has a relationship with the others, with internal references to where the video is and where the audio is. Your only salvation is to put things back EXACTLY like they were (file path) before you changed the names and letters of drives and/or moved the files.

[Mike Velte]

[Joseph Laronga] “I digitized footage to an external hard drive.”

What audio format did you choose to digitize to? What hardware or software did you use?
Dolby ac3 is not supported for editing by Premiere.