Problem making slideshow. "Data rate to high"

Using Encore CS3 on Win XP. Trying make dvd on a short film and some slideshows. Total c 2,5 GB. Building stops telling me: PGC "Lenas" has an error at 00:01:31:08. The data rate is too high for DVD. You must replace the file with one of a lower rate.....ref, EPGC...." All pictures in slideshow "Lenas" are the same size, 2-2,5 MB, nothing special with the picture at 00:01:31:08. What does the info say?
Preview with no problems.
Regards Gunnar Löwenhielm

What are the pixel x pixel dimensions of those still images?
What is your Encore Project setting?
How many images do you have per SlideShow?
Good luck,
Hunt

Similar Messages

Another Data Rate Too High Error Question

Hi all,
I have seen quite a few posts about pgc errors, but most of them deal with slideshows and not video; and I can't find anything with the REF=KApgc error.
I'm just putting all of my home movies onto an authored DVD, not rocket science. I'm using the 'Film Submenu' preset with only 5 main movies, things like Easter, Birthday, etc. My transition for each button is a slate (for lack of a better word) that says exactly what it is and when it happened, before each movie plays.
After I had everything set up, I realized I didn't have an ability to "play all" that would include these slates. Simple solution, make a 'play all' button that links to a timeline that has everything in it - the slate, then the movie, next slate, next movie and so on. (When I say movie - they are all .mov files rendered out from After Effects, even the slates)
My transcode settings are NTSC DV High Quality 7mb VBR 2 Pass and the "maximum quality" box is checked.
When I run the 'Check Disc' all is fine. Preview the disc, all is fine.
Build Disc: Hours of Transcoding then the error: Data Rate Too High at *timecode* REF=KApgc.
When this movie is by itself with a button click, it's fine. It's only in the "play all" timeline that it produces the error.
If the data rate isn't too high in one place, why is it too high in another? It's the same thing, just a longer timeline.
Please Help!
Thanks.

Thanks Jeff,
I feel kind of silly for not thinking of that as a solution to my play all dilemma. That's why you're the expert I guess.
A better solution would be to create a playlist of all of your other timelines; that way, only one copy of each gets burned to disc.
Hopefully the "data rate" error will go away with these changes.
-Jeff
Can I place my slates that are just assets (.mov) in the playlist or can I only put timelines in there?
Thanks again,
-Jim

Why do I get data rate too high error after capture and save? (using AJA Kona)

I record(capture) about an 70 min program with Adobe premiere CS5 once a week. About a year ago I got the error *data rate too high" when stopping "capture" when saving program to Video HD(2TB). The video recorded was OK but after about 15 min the audio was out of sync and garbled. I thought I had found the problem by defragging the video drive. I have not had any problems for about 50 weeks.. until this week-it happened again. I know the video drive(2TB) was defragged and only half full. I was able to recover the program since I back up the program on a DVD but had to go through a lot of problems massaging it since I send the program to a local ABC broadcast station in 16/9 SD and the DVD is rescored in 4/3 .
I have the CS5 program on a separate 2.5 GB drive. I am running Win7pro and have a RAID series of Intel Xeon ES410 processors.
Any help as to why I get this "Data Rate too High" when saving program would be appreciated.
Thanks much!

I have three Mitsubishi broadcast quality cameras (two HD -waiting on money for switcher and 3rd HDcamera). They feed to their camera control untints and then to a switcher and then into video computer and the C5S. I probably am not answering your question. I can access the computers from my home(I also have a CG computer). Is there some way I can tell you from the C5S program which the info you need? I have it ready to record for next week.
I know how to manipulate various functions but I do not know all the ins and outs of the Premiere settings-an IT man set those up for me two years and he is no longer available.
Thanks

PGC...data rate too high

Hallo,
message
nunew33, "Mpeg not valid error message" #4, 31 Jan 2006 3:29 pm describes a certain error message. The user had problems with an imported MPEG movie.
Now I receive the same message, but the MPEG that is causing the problem is created by Encore DVD itself!?
I am working with the german version, but here is a rough translation of the message:
"PGC 'Weitere Bilder' has an error at 00:36:42:07.
The data rate of this file is too high for DVD. You must replace the file with one of a lower data rate. - PGC Info: Name = Weitere Bilder, Ref = SApgc, Time = 00:36:42:07"
My test project has two menus and a slide show with approx. 25 slides and blending as transition. The menus are ok, I verified that before.
First I thought it was a problem with the audio I use in the slide show. Because I am still in the state of learning how to use the application, I use some test data. The audio tracks are MP3s. I learned already that it is better to convert the MP3s to WAV files with certain properties.
I did that, but still the DVD generation was not successful.
Then I deleted all slides from the slide show but the first. Now the generation worked!? As far as a single slide (an image file) can not have a bitrate per second, and there was no sound any more, and as far as the error message appears AFTER the slide shows are generated, while Encore DVD is importing video and audio just before the burning process, I think that the MPEG that is showing the slide show is the problem.
But this MPEG is created by Encore DVD itself. Can Encore DVD create Data that is not compliant to the DVD specs?
The last two days I had to find out the cause for a "general error". Eventually I found out that image names must not be too long. Now there is something else, and I still have to just waste time for finding solutions for apparent bugs in Encore DVD. Why doesn't the project check find and tell me such problems? Problem is that the errors appear at the end of the generation process, so I always have to wait for - in my case - approx. 30 minutes.
If the project check would have told me before that there are files with file names that are too long, I wouldn't have had to search or this for two days.
Now I get this PGC error (what is PGC by the way?), and still have no clue, cause again the project check didn't mention anything.
Any help would be greatly appreciated.
Regards,
Christian Kirchhoff

Hallo,
thanks, Ruud and Jeff, for your comments.
The images are all scans of ancient paintings. And they are all rather dark. They are not "optimized", meaning they are JPGs right now (RGB), and they are bigger then the resolution for PAL 3:4 would require. I just found out that if I choose "None" as scaling, there is no error, and the generation of the DVD is much, much faster.
A DVD with a slide show containing two slides and a 4 second transition takes about 3 minutes to generate when the scaling is set to something other than "None". Without scaling it takes approx. 14 seconds. The resulting movies size is the same (5,35 MB).
I wonder why the time differs so much. Obviously the images have to be scaled to the target size. But it seems that the images are not scaled only once, that those scaled versions of the source images are cached, and those cached versions are used to generate then blend effect, but for every frame the source images seem to be scaled again.
So I presume that the scaling - unfortunately - has an effect on the resulting movie, too, and thus influences the success of the process of DVD generation.
basic situation:
good image > 4 secs blend > bad image => error
variations:
other blend times don't cause an error:
good image > 2 secs blend > bad image => success
good image > 8 secs blend > bad image => success
other transitions cause an error, too:
good image > 4 secs fade to black > bad image => error
good image > 4 secs page turn > bad image => error
changing the image order prevents the error:
bad image > 4 secs blend > good image => success
changing the format of the bad image to TIFF doesn't prevent the error.
changing colors/brightness of the bad image: a drastic change prevents the error. I adjusted the histogram and made everything much lighter.
Just a gamma correction with values between 1.2 and 2.0 didn't help.
changing the image size prevents the error. I decreased the size. The resulting image was still bigger than the monitor area, thus it still had to be scaled a bit by Encore DVD, but with this smaller version the error didn't occur. The original image is approx. 2000 px x 1400 px. Decreasing the size by 50% helped. Less scaling (I tried 90%, 80%, 70% and 60%, too) didn't help.
using a slightly blurred version (gaussian blur, 2 px, in Photoshop CS) of the bad image prevents the error.
My guess is that the error depends on rather subtle image properties. The blur doesn't change the images average brightness, the balance of colors or the size of the image, but still the error was gone afterwards.
The problem is that I will work with slide shows that contain more images than two. It would be too time consuming to try to generate the DVD over and over again, look at which slide an error occurs, change that slide, and then generate again. Even the testing I am doing right now already "ate" a couple of days of my working time.
Only thing I can do is to use a two image slide show and test image couple after image couple. If n is the number of images, I will spend (n - 1) times 3 minutes (which is the average time to create a two slides slide how with a blend). But of course I will try to prepare the images and make them as big as the monitor resolution, so Encore DVD doesn't have to scale the images any more. That'll make the whole generation process much shorter.
If I use JPGs or TIFFs, the pixel aspect ratio is not preserved when the image is imported. I scaled one of the images in Photoshop, using a modified menu file that was installed with Encore DVD, because it already has the correct size for PAL, the pixel aspect ratio and the guides for the save areas. I saved the image as TIFF and as PSD and imported both into Encore DVD. The TIFF is rendered with a 1:1 pixel aspect ratio and NOT with the D1/DV PAL aspect ration that is stored in the TIFF. Thus the image gets narrowed and isn't displayed the way I wanted it any more. Only the PSD looks correct. But I think I saw this already in another thread...
I cannot really understand why the MPEG encoding engine would produce bit rates that are illegal and that are not accepted afterwards, when Encore DVD is putting together all the stuff. Why is the MPEG encoding engine itself not throwing an error during the encoding process? This would save the developer so much time. Instead they have to wait until the end, thinking everything went right, and find out then that there was a problem.
Still, if sometime somebody finds out more about the whole matter I would be glad about further explanations.
Best regards,
Christian

H.264 All-Intra Data Rates Significantly Higher

Does the built-in H.264 codec encode I-frame only files differently? I am trying to determine the optimal GOP length for high bitrate exports. Image quality seems to degrade, even in the I-frames, when using key frame distances greater than one.
After performing a series of tests to characterize the Adobe H.264 encoder, I discovered that exported files are significantly larger when key frame distance equals one frame (N=1). The average video data rate for a test file rendered with the Adobe H.264 encoder is as follows:
N=1 : 2.17 bpp : 24I
N=2 : 0.66 bpp : 12I + 12P
N=3 : 0.59 bpp : 8I + 8B + 8P
Note how the data rate drops 70% (from 2.17 to 0.66 bpp) even though 50% of the I-frames still exist when N=2. By comparison, here is the video data rate when exporting with QuickTime H.264:
N=1 : 0.89 bpp : 24I
N=2 : 0.70 bpp : 12I + 12P
N=3 : 0.64 bpp : 8I + 16P
The following chart shows data rates at key frame distances from 1-48 frames for Adobe H.264, QuickTime H.264 (via Adobe), QuickTime Pro, and Expression Encoder 4 Pro. Data rates are consistent among all encoders at GOP lengths greater than one. There is an anomoly with the Adobe H.264 codec compressing all-intra files.
The observed behavior occurs in all profiles, which were tested at Levels 4.1, 4.2, 5.0, and 5.1:
Image quality is better in the Adobe H.264 all-intraframe file, especially with respect to detail retention. The pictures below show sections of two consecutive frames magnified 400%. The file with N=2 is less accurate and contains noticeable blocking. Even the I-frames don't look as good in the files where N>1.
The test file was a seventeen second Premiere Pro sequence consisting of H.264, MPEG-2, and AE files with effects applied. Exports were rendered from the Premiere Pro timeline and from a V210 uncompressed 4:2:2 intermediate file of the sequence. The following settings were used:
Format: H.264
Width: 1280
Height: 720
Frame Rate: 24 fps
Field Order: Progressive
Aspect: Square Pixels (1.0)
TV Standard: NTSC
Profile: Baseline, Main, and High
Levels: 4.1, 4.2, 5.0, 5.1
Render at Maximum Bit Depth: Enabled
Bitrate Encoding: VBR, 2-Pass
Target Bitrate: Maximized for each Profile/Level
Maximum Bitrate: Maximized for each Profile/Level
Key Frame Distance: 1, 2, 3, 4, 5, 6, 7, 8, 12, 24, 48
Use Maximum Render Quality: Enabled
Multiplexer: MP4
Stream Capability: Standard
Software:
Adobe Media Encoder CS6 Creative Cloud v6.0.3.1 (64-bit)
Premiere Pro CS6 Creative Cloud v6.0.3
Windows 7 SP1
QuickTime Pro for Windows v7.6.9 (1680.9)
MediaInfo 0.7.62 (for GOP and data rate information)

I think the short answer is yes,
a h.264 encoder does I-frame only differently. I frames are complete expressions of a picture with no temporal compression information.
P frames use _P_redictive information. IE information from prior frames.
B frames use _B_i-directional predictive frame information.
h.264 gets the majority of it's bit saving from use of B and P frames. When you do I-frame only you only get the block compression and none of the advantages of P and B frames. Thus the GOP N=1 doesn't get very good bit's per pixel.
Having said all that I do find your comment...
Profitic wrote:
Note how the data rate drops 70% (from 2.17 to 0.66 bpp) even though 50% of the I-frames still exist when N=2. By comparison, here is the video data rate when exporting with QuickTime H.264:
... very interesting. Indeed, why is the datarate 70% less when it should at best be 50% for GOP N=2. 50% less should be the same I-frame information plus 0 bytes for the B frame between them. (GOP = I,B,I). Any more than that and it is throwing away bits from the I-frame. So, this seems to be to be a ratecontrol bug.
http://en.wikipedia.org/wiki/Group_of_pictures
"The GOP structure is often referred by two numbers, for example, M=3, N=12. The first number tells the distance between two anchor frames (I or P): it is the GOP size. The second one tells the distance between two full images (I-frames): it is the GOP length. For the example M=3, N=12, the GOP structure is IBBPBBPBBPBBI. Instead of the M parameter the maximal count of B-frames between two consecutive anchor frames can be used."

PE2 Data Rate too high

I am trying to burn a 15 minute video straight to the DVD. During the burning process (after rendering for about 10 hours) I got the following message: "The data rate of this file is too high for DVD. You must replace the file with one of a lower data rate. -PGC Info: name=, ref=Apgc, time= 00:07:44:23"
I successfully burned the same project a week ago; my only changes were adding some transitions and a few stills.
My project is video (most converted from VHS), music (ripped from CD or itunes), Audio (narrative recorded at home) and stills (almost all reduced to ~300Kb).
I am in the middle now of trying to burn to a file, but the error spooks me.
Any thoughts

Ned,
Some place, you have set the Data-rate above the DVD-spec. of 10 MB/s for ALL Assets, or have spikes above that. Now, since this is for all streams, Audio + Video, something below 8 works best. Then, if there is a momentary spike, it falls below the threshold of 10. In your Export settings, this has been set to high, either by you, or the program. PE is pretty smart about spikes, but can get fooled by the Assets, sometimes.
Check your output settings. I find that a setting of ~7 max. is better for player compatibility, though PE does allow one to go to 8 max.
Hunt

Can subtitles cause data rate too high errors?

I've been building a DVD in Encore CS5, using Sorenson as the transcoder. I've built the disc many times with no issues. Now I've added a Spanish subtitle track, and I am suddenly getting errors that the data rate is too high. Can the subtitles cause this?
These are my Sorenson settings. Ultimately this will be a commercially pressed disc. Do I need to adjust, and if so, how?
Target 8400 kbps
Min: 53% (4452)
Max: 115% (9660)
Total data rate: 8624
2-pass VBR, 720x480.
Audio: ATSC A/52
Data rate: 224
Sample: 48K
Stereo, 16

The question will be in part what the actual datarate is (and most particularly, datarate spikes). If we were using burned disks, I would worry. Since players don't have to play burned disks, they are less likely to be uniform in handling datarate variations. You are replicating; correct? So a player that fails to play correctly, is failing what it is supposed to do. As long as you are in spec, you should be okay.
The other way to answer this: no, I would not trust Encore failing to throw an error as a sufficient guarantee. Does the replicator test for datarate?

Data Rates & Cell Size

Hi all.
A few days back i was going through an article on High Density Wireless Deployments , and came through an extract which disabling Lower Data Rates , helps to reduce cell size.
How doe this work ? I mean are we exclusively allowing only those clients to associate by making the data rates disabled for slower clients ?
But isnt cell size , controlled by the Transmit power of the antenna ?
Or what we are looking here , is just reducing the cell size logically?
Thanks ,
Rahul.

No problem.... Look at it this way.... back in the days with autonomous, you could roam from one ap and not roam to the next two while walking down the hallway. So in high density, you want to have some sort of control on how many clients you want in a cell or on a particular AP. People always asked.... why an i connected to an ap 20 feet away and not the one above me. Well for one, the client chooses and also why would it roam is it is still connected at a rate that you are still supporting. There are so many tweaking involved with high density, well at least I do a lot of tweaking, but its so I can control the cell size for AP's in a high density area compared to areas where I need to extend the cell size a bit more. Data rates and TX power work hand in hand when determining this.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Encoded video does not have expected data rate

Hi
I've been encoding with Flash Media Encoder (CS3) recently
and come across a contradiction which I can't seem to make sense
of. Can it be possible that the longer the video, the harder it is
for the encoder to maintain data rate?
This was revealed when I started using FMS2 (space on a
shared server as opposed to my own server). I encoded a video at
what I thought was a data rate which was within my data rate limit
for my stream and it stuttered on playback over the stream. The FMS
supplier informed me that the FLV I thought I'd encoded at 400kbps
video 96 kbps audio actually had a data rate of around 700kbps in
total. But if I open the video in a FLV player, and look at info,
it still shows the setting I originally intended. However, my
supplier suggested checking data rate using this equation:
(filesize in MB x 8)/videoduration in seconds = video
datarate in kbits/sec
If you apply this calculation to my video it does indeed show
what they said:
Using Flash Media Encoder:
Encoded at 400kbps video - 96 kbps audio
Compressed filesize = 26,517 kbytes
Duration = 240 seconds
CALCULATION GIVES DATE RATE OF 880k/b a second
(note file contains an alpha channel)
Furthermore, applied to a shorter video, we get the following
more logical results:
Encoded at 400kbps video - 96 kbps audio
Compressed filesize = 6,076 kbytes
Duration = 90 seconds
CALCULATION GIVES DATA RATE OF 527 kb/sec
(no alpha channel)
The only differences between the two vids is the alpha
channel and the duration. Somethings doesn't add up here.
Any clues?
Thanks
Simon

I've just partly answered my own question. Funny how writing
a post can help you think your problem through sometimes.
The issue is the alpha channel, which adds to the file size
thereby making the data rate "incorrect". In other words, the same
file encoded without the alpha channel provides the expected
results. I guess this changes my question to: How do I create
predicatable data rates when encoding using an alpha channel. I
could just estimate of course and see what comes out, but is there
a better way?
SImon.

Another PGC Data Rate Error

Hi,
Like a few others out there, I've been having a "PGC Data rate too high, please switch with lower data rate" problem for a few weeks now. I've been searching online for the past week and a half for a solution and have tried everything suggested, from changing the transcoding max bitrates (down to 5.0) and lowering the audio bitrate, to recompressing, and reencoding the said video file that is having problems. I removed this certain video from my project and built it without any problems which leads me to believe that this one video is the culprit. No matter what I've tried, I still get the same message although the time of error varies by a second or two. Is there any other help someone may be able to offer about the subject? Thanks.
Leighton

Leighton.
This sounds like a somewhat esoteric way to do the conversions IMHO.
It is possible the total combined data rates do exceed - but in EncoreDVD 2 this is a warning more than anything else.
I got these when running HIgh Bitrate MPEG-2 CBR encoded files along with PCM audio - I ignored the warning & built the disc anyway. It worked just fine.
Bitrates in question were 8,000 for video & 1536 for Audio.
Within specs. The little yellow triangle triangle with an exclamation mark was clearly visible in the timeline, so I used the "Ignore warnings & build anyway" option as I knew it was "in-spec".
Can you please let us know some details about the project:
1 - Source of files
2 - Bitrates encoded
3 - Audio type
etc.
I wonder - and hopefully someone can confirm one way or the other - if Encore sets the limit for this warning from the setting made in preferences about the maximum bitrate?

Variable data rate

I have a question and I'm not 100% sure how to phrase it so Ill describe my problem and maybe someone can help me.
Im working on a video composed of Gopro and DSLR footage (all converted to Prores LT). My problem is that the Gopro shots need to have a very high data rate because there is alot going on and lots of fast movement etc so the quality is only acceptable when the data rate is set to about 35 mbps. However, the DSLR footage doesnt need a data rate that high, the quality stays very high with data rates as low as ~ 6mbps (Im not exactly sure why that is? less movement maybe?).
So I dont want to export an entire video at 35mbps because that is a HUGE file. Is there such thing as a variable data rate or does anyone have any suggestions for what exactly I could do here?
Thank you in advance!

I convert all my footage to Prores LT 1280x720 at 30 fps which gives my prores clips a data rate of approximately 42 mbps I believe? and yes I'm talking end use.
Essentially what it comes down to is after I have complete editing my video in FCP and I compress it down for end use (vimeo/youtube) the only way the Gopro shots are any good is if I use an extremely high data rate (A data rate that probably isnt even supported by most video sites). There has to be a way to obtain decent quality on final compression because there are literally millions of videos out there that people have shot with gopros that are atleast decent quality. However I have found if I decrease my data rate to anything below 15 mbps the quality (of just the gopro shots) is so poor its unwatchable. Hence wondering if there was a way to set variable data rates so some of the clips are high and others are low low? Or some other work around?

Bridge 1300 building to building link for VOIP Data Rates settings and QoS

Hi,
What are the recomendations for data rates settings of wlan fo using voip in a link building to building.
Default is
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0
54.0
Should i maintain or change to what?
Also what QoS should i apply?
Thks
Best Regards
Marco

OFDM is a physical layer encoding technology for transmitting signals through the RF. This method breaks one high-speed data carrier into several lower-speed carriers that transmit in parallel across the particular RF spectrum. OFDM, when used with various modulation types such as 802.11g and 802.11a, is capable of supporting data rates as high as 54 Mbps.
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7921g/5_0_1/english/administration/guide/7921wrnt.html#wp1085347

Upload Maximum Date Rate Lower Than Upload Data Ra...

Hello there,
I have just brought up my BT Home Hub 5 stats and my upload data rate is higher than my upload maximum date rate. Is this normal? My upload noise margin has dropped to 4.9 - 5.1 dB. I've had BT Infinity just over 2 days and was wondering if this was normal for FTTC connections?
Many thanks,
William

normally the data rate will be lower than max data rate but yours is that close I would not bother unless it starts to affect your connection which is unlikely
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Files failing to adhere to set data rate on export from Quicktime

I am hoping somebody can shed some light on this.
I open an uncompressed .mov file (output from FinalCut) with Quicktime with the intention of compressing it for the web. After File: export, in the options dialog box, in the field where you can restrict the data rate, I put a number, say 488 kbs/sec. But every time I do this, the finished compressed file has a data rate wildly higher, like 2000 kbs/sec, and so is too large for my purposes.
I feel like I used to do this all the time- I have plenty of .mov files with data rates around 500 kbs/sec that I posted on my website, so this had to have worked at some time in the past.
Anybody? Thanks

Just a bump-

Quick Notation Question - Data Rates/Frame Rates/Interlacing

Finally upgraded to a decent prosumer camera and I'm trying to decipher what the manual is telling me about the many different formats it shoots and and the associated options. I keep seeing things like "There are two basic shooting modes: 720p and 1080i/p.", which I'm finding confusing. In my understanding, the "p" in 720p means progressive video and the "i" in 1080i means interlaced. So what do I make of 1080i/p?
On top of this, my camera shoots in "native" mode, which drops duplicate frames used in "over 60" formats. This will give me variations in the notation like:
720/24pN
720p Native 60 fps
1080i/24p
1080/24PN
Can someone give me a quick primer about frame rate vs data rate and explain how to read these notations? I'd appreciate it quite a bit.
Thanks!

There are so many cameras, capable of so many different formats that providing a manufacturer and model could be helpful in this discussion.
Jim's answer is absolutely correct but I'm going to re-state for clarification.
The i/p designation means you can chose to record as interlaced or progressive for a given resolution.
It sounds like your camera is designed to "capture" images at 60 frames per second, selecting "native" mode means extra frames are deleted and only the desired frames, based on frame rate setting, are recorded to memory. The advantage of "native" @ 24fps is you save space on your memory card. The advantage of NOT using "native" mode is that all 60 frames per second are recorded, but the file metedata tells playback software to only show the frames needed for the specified frame rate (i.e. 24). Since all 60 frames per second are recorded, you use more memory but you also have the option of retrieving all the those frames, if you so desire, at a later time (i.e. for smoother slo-mo).
To be honest I don't know what your spec of 1080i/24p means. If that is truly an option then I would guess it means it will record a 24p image but the metedata would indicate the file should playback at 30fps interlaced by adding the proper 3:2 pulldown. This would give you that "film" look in a broadcast compatible format.
For the most part, you don't want use use any interlaced settings. Very few display devices still in use can properly display interlaced images. Interlacing is only required in some broadcast specifications.
To answer the second part of your question;
Frame rates are an indication of how many times the moving image is captured over a given period (per second). Higher frame rates means smoother, more "real life" motion. Data rates can generally be considered an indication of image or audio quality. Higher levels of compression result in lower data rates and (generally) lower quality. If squeezing more hours of footage on fewer memory cards is more important than getting the best image quality, choose a lower data rate. Higher frame rates (more images per second) inherently require a higher data rate to retain the same quality as fewer frames at a lower data rate.

Problem making slideshow. "Data rate to high"

Similar Messages

Maybe you are looking for