Why does FMS sets SAR to .mp4 to force 4:3 aspect ratio?

We record .mp4 file from live video stream from Digital Rapids and then process it with ffmpeg.
Live stream has 576x324 resolution (16:9 ratio is assumed).
It is recorded and seems fine, but has SAR value 3:4, which results in DAR equal 4:3.
It is taken into consideration by ffmpeg later on, and we get an oblate picture. That's a problem.
We came to a conclusion that SAR is set based on formula (4:3)/(width/height), so every recorded video has DAR equals 4:3.
Why is that happening? What can we do to have DAR equal to 16:9?

I've found a cure for this bug!! As apple support on the phone convinced me this realy was a bug, there is no way to fix it within Imovie, (and no one seems to have a reaction at all ... ), I checked the Apple site for downloads. There I found MovieConverter Studio. A shareware program which can take the simulated 16:9 DV input and make it into a DV input Imovie recognizes as 4:3.
It can do a lot more, but it does solve my problem.
Regards Raymond

Similar Messages

Why does the setting of trackpad always changes everytime i turn off my Macbook pro?

why does the setting of trackpad always changes everytime i turn off my Macbook Pro?

Sure , just refer to:
http://support.apple.com/kb/ht1379
http://support.apple.com/kb/HT3964

Dvd burned in premiere pro cc does not fill the screen. Desire a 4:3 aspect ratio

I am using premiere pro cc. I burned a dvd several times,trying different presets. On each occasion the dvd never fills the screen. It does not lool like letterbox ( 16 x 9 ). There is space all around the picture / video. Need assistance fast,project is already late.Thanks in advance.
Theo Smith

I sent the screenshot via an e-mail attachment. I wasn't aware that
attachments could not be forwarded this way. I will send it again. First time
I've utilized this service.
In a message dated 3/8/2015 10:15:23 A.M. Eastern Daylight Time,
[email protected] writes:
Dvd burned in premiere pro cc does not fill the screen. Desire a 4:3
aspect ratio
created by Peru Bob (https://forums.adobe.com/people/Peru+Bob) in Adobe
Media Encoder (AME) - View the full discussion
(https://forums.adobe.com/message/7264779#7264779)

Why does the "set automatically" button keep turning off in the my date & time area of my settings? When it is off I can not use facetime or imessages.keep during off on my iPad?

I wasn't able to use FaceTime or iMessages and found out it was because the "set auomatically" button was off under date & time in the settings area. Why does tha button turn off?

I wouldn't suggest going to get it yourself. You could find yourself in a situation you cannot get out of and could get hurt. Second, as stated before, it is more for misplaced or lost devices, not stolen devices. Many police agencies do not feel they have probable cause, just from your statement on a map location to justify attempts to recover the device. There have been many posts from others who have had devices stolen where the police will not confront someone based on that map location. I understand you are impacted by the theft, but this is what we have insurance for. To protect your content, from now on I suggest you put a passcode on the device. I hope you have changed all of the passwords for accounts you had on the device, since all of your content and data was accessible to the thief.

Mp4 to DVD in Compressor, aspect ratio

I'm trying to make a DVD of an mp4 movie I have. I put it in Compressor and chose DVD best quality 150 minutes (since it's over 2 hours) and I made sure the aspect ratio was 2.35:1 since that's what the movie is. It plays fine in the preview window in Compressor but when I export it the image is stretched vertically. How can I maintain the original aspect ratio? Thanks.

I'm not exactly sure. When I click "get info" on the file, it says the dimensions are 1024x576, which is 1.78:1, but the original aspect ratio of the movie on imdb says 2.35:1. I think I might've solved the problem though. When I put the file in Compressor, I changed the "padding" to "preserve aspect ratio" and did a test of a few seconds of footage and it looked correct, so now I'm doing the whole movie.

Why does FCP set 30fps TC Rate for certain audio clips that lack TC stream?

Hello folks,
I'm cutting a DVCPRO HD 720p50 feature at 25fps on FCS2 w fcp 6.0.3. (Used a PAL Panasonic HVX200)
When I import certain of the audio files from the location sound recordist, FCP lists the file as having a TC Rate of 30fps -- and puts a greenbar over my audio track in the 25fps timeline. the audio folks were not TC locked to the camera, so I'm in the midst of doing a manual post-sync (yeah, yeah) of all of these files and Merging them into new Master Clips (1V+6A) for editing.
I already learned the great trick from this forum of importing the audio takes folders from each day and then disconnecting them to set them all as dual mono, then reimporting -- makes my Merge clips work the way I had hoped they would.
But this 30fps/25fps issue is really holding me up. This phenomena of tracks mysteriously being picked as having a TC Rate of 30 is rare, like 50 of the 400 audio files, but I can find no way within FCP to correct this setting nor any indication why these files were chosen.
I can't change the TC from 30-25 when a clip is online or offline -- I get the message "The media of one or more selected clips does not support the chosen timecode rate of 25, and are left untouched."
Any help will be wildly appreciated -- I am eager to complete this sync project and get cutting!
matt

I got help for this issue over at CreativeCow's FCP pages -- it turns out, all I had to do was open a new project using an easy setting and project setting for vanilla PAL 25 fps SD stuff. All of the audio was correctly brought in -- then I disconnected all of the clips, made them dual mono, reconnected them, and copied them over to my old gristly project folder.
Now I can marry these dual mono 25fps files to the video files without having FCP incorrectly compensate for "30fps" by speeding these clips up slightly, so things stay in sync.

Why does firefos set my homepage to google when I reopen it after it crashes when I had yahoo set as my homepage?

when I'm using my computer, Firefox will sometimes crash. When I re-open it, it will no longer have the homepage that I saved, but will instead have Google saved as my homepage. This is aggrivating because I then have to go back and rest my homepage, and all of the tabs that I had set to open up automatically. It does this EVERy time it crashes.

It sounds like you have a third party program that has taken over your search engine, home page, and/or the default new tab page. Fortunately, this can be remedied easily:
# At the top of the Firefox window, click on the Firefox button (Tools menu in Windows XP), and then click Add-ons. The Add-ons Manager tab will open.
# In the Add-ons Manager tab, select the Extensions panel.
# Select the toolbar you wish to remove.
# Click the remove button.
# Click "Restart now" if it pops up. Your tabs will be saved and restored after the restart.
After Firefox restarts, install the [https://addons.mozilla.org/en-US/firefox/addon/searchreset/ Search Reset Tool]. This will remove the rest of the traces of this program from your Firefox.
For further information, please read [[Remove a toolbar that has taken over your Firefox search or home page]].
Did this fix the problem? Please let us know!

Why does one set of clients out perform another?

Greetings all -
When I execute sqlplus using this query "select * from SYS.COL$ where rownum<=50000;" from our linux client it, takes 12 seconds. When I execute it from any of several of our solaris clients it takes close to a minute. So the linux client will run the above SQL faster than all the solaris clients by a multiple of 4 or 5 times. The linux (el x86-64) data servers and the sun clients are all in the same room. Some of the solaris clients are virtual (zones) on a SUN t5220 box. Other solaris clients are physical boxes (sparc SUNW,Sun-Fire-V245).
The 2 linux dataservers are HP ProLiant DL380s. When one of these is used as a client and runs the SQL against the same database that the solaris clients are targeting it out performs the solaris clients significantly.
So allow me to restate - when I run the query from dataserver_2 against the target database on dataserver_1, it takes 12 seconds. When I execute the query from any solaris client against the target database on dataserver_1, it takes over 50 seconds.
We've also tested with a "back door" in place, putting the solaris client on the same network as the dataservers. This didn't make any difference. I've also tested by making changes to the kernal settings on the solaris client, bumping up the max-shm-memory parm from the default up to 7g and this also didn't help. The linux client which performs well is also a dataguard standby server. Why am I seeing such a difference in elapsed times to run this query - depending on which client I run it from? All the solaris clients query elapsed times are consistently around 55 seconds. When it runs from another linux client in a four miles away, it takes 38 seconds. What can I do to improve the performance for these solaris clients?
A side note: running an "ssh scp" against a 1-gb file also takes inordinately long when the source or target is one of our solaris clients. Our UNIX support tells us this just indicates scp doesn't work so great on these clients.
tia -
Jim

Hi Charles,
Here's some representative trace output....
<<<<<<<<<< snip from trace 10043 output from "good" client...(note the "ela" -elapsed- values are < 300
FETCH #1:c=0,e=114,p=0,cr=4,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183488152138
WAIT #1: nam='SQL*Net message from client' ela= 270 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183488152432
WAIT #1: nam='SQL*Net message to client' ela= 1 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183488152460
FETCH #1:c=0,e=24,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183488152476
WAIT #1: nam='SQL*Net message from client' ela= 225 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183488152721
WAIT #1: nam='SQL*Net message to client' ela= 1 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183488152748
FETCH #1:c=0,e=23,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183488152763
WAIT #1: nam='SQL*Net message from client' ela= 221 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183488153003
WAIT #1: nam='SQL*Net message to client' ela= 0 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183488153030
FETCH #1:c=0,e=24,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183488153045
<<<<<<<<<< snip from trace 10043 output from "bad" client...(note the "ela" -elapsed- values are all all > 800
FETCH #1:c=0,e=24,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183823787134
WAIT #1: nam='SQL*Net message from client' ela= 894 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183823788051
WAIT #1: nam='SQL*Net message to client' ela= 0 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183823788079
FETCH #1:c=0,e=25,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183823788095
WAIT #1: nam='SQL*Net message from client' ela= 890 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183823789010
WAIT #1: nam='SQL*Net message to client' ela= 1 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183823789038
FETCH #1:c=0,e=24,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183823789054
WAIT #1: nam='SQL*Net message from client' ela= 975 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183823790051
WAIT #1: nam='SQL*Net message to client' ela= 0 driver id=1413697536 #bytes=1 p3=0 obj#=-1 tim=1239183823790079
FETCH #1:c=0,e=25,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=1,tim=1239183823790095
The above pattern is repeated for 150,000 lines of trace output. There are no series of repeated "message from client" lines which might represent repeat ACKing if I understood you correctly.
The "good" trace output file has 150,099 lines and "bad" trace output file has 150,092 lines. No extra ACKs in the bad - just much longer "SQL*Net message from client" elapsed times.
I've just tested with arraysize set to 50000. No gain.
I also set SDU to 32768 in both the client tnsnames file and the listener/sid_list. No gain.
Thanks all for your helpful feedback.
Jim

Why does Quicktime not play this mp4 correctly

I can create an mp4 file (recording) from Belkin's @TV app but that file will not play correctly in Quicktime (or RealPlayer or iMovie, etc.). While the video playback seems fine, the audio plays a couple of seconds, at "chipmonk" speed, and then there is no sound out. However, if I move the playhead to any random place in the recording I can then hear another couple of seconds of audio, as before ("chipmonk" speed), and then silence. The VLC player will, however, play the file correctly.
So, seeing that the file itself was not bad, I decided to try Handbrake to re-encode the recording. And, to my surprise, Handbrake was able to handle the file correctly and produce an mp4 file that Quicktime (and the others) can play.
I don't know enough about these mp4 files to grasp what is wrong with the original Belkin output. The Quicktime inspector reports that the Format is
   H.264, 352 x 240
   AAC, 32000 Hz, Stereo (L R)
   FPS: 25.37
Any ideas? (Is there additional data I can look at about this file?)
I'm running the current version of Mavericks and Quicktime 10.3.

Jon Walker wrote:
Use a dedicated utility like MediaInfo to screen more information about the file and how each track is encoded.
Another user in the Belkin forum suggested that I look at the recording's header info, and pointed me to AtomicParsley, which I have now run (using some basic terminal commands).
This is what it reports for the initial, Belkin-app produced file:
Atom ftyp @ 0 of size: 24, ends @ 24
Atom mdat @ 24 of size: 195643428, ends @ 195643452
Atom moov @ 195643452 of size: 772515, ends @ 196415967
     Atom mvhd @ 195643460 of size: 108, ends @ 195643568
     Atom iods @ 195643568 of size: 33, ends @ 195643601
     Atom trak @ 195643601 of size: 674653, ends @ 196318254
         Atom tkhd @ 195643609 of size: 92, ends @ 195643701
         Atom mdia @ 195643701 of size: 674553, ends @ 196318254
             Atom mdhd @ 195643709 of size: 32, ends @ 195643741
             Atom hdlr @ 195643741 of size: 33, ends @ 195643774
             Atom minf @ 195643774 of size: 674480, ends @ 196318254
                 Atom vmhd @ 195643782 of size: 20, ends @ 195643802
                 Atom dinf @ 195643802 of size: 36, ends @ 195643838
                     Atom dref @ 195643810 of size: 28, ends @ 195643838
                 Atom stbl @ 195643838 of size: 674416, ends @ 196318254
                     Atom stsd @ 195643846 of size: 140, ends @ 195643986
                         Atom avc1 @ 195643862 of size: 124, ends @ 195643986
                             Atom avcC @ 195643948 of size: 38, ends @ 195643986
                     Atom stts @ 195643986 of size: 403840, ends @ 196047826
                     Atom stss @ 196047826 of size: 8476, ends @ 196056302
                     Atom stsc @ 196056302 of size: 28, ends @ 196056330
                     Atom stsz @ 196056330 of size: 253724, ends @ 196310054
                     Atom stco @ 196310054 of size: 8200, ends @ 196318254
     Atom trak @ 196318254 of size: 97713, ends @ 196415967
         Atom tkhd @ 196318262 of size: 92, ends @ 196318354
         Atom edts @ 196318354 of size: 48, ends @ 196318402
             Atom elst @ 196318362 of size: 40, ends @ 196318402
         Atom mdia @ 196318402 of size: 97565, ends @ 196415967
             Atom mdhd @ 196318410 of size: 32, ends @ 196318442
             Atom hdlr @ 196318442 of size: 33, ends @ 196318475
             Atom minf @ 196318475 of size: 97492, ends @ 196415967
                 Atom smhd @ 196318483 of size: 16, ends @ 196318499
                 Atom dinf @ 196318499 of size: 36, ends @ 196318535
                     Atom dref @ 196318507 of size: 28, ends @ 196318535
                 Atom stbl @ 196318535 of size: 97432, ends @ 196415967
                     Atom stsd @ 196318543 of size: 92, ends @ 196318635
                         Atom mp4a @ 196318559 of size: 76, ends @ 196318635
                             Atom esds @ 196318595 of size: 40, ends @ 196318635
                     Atom stts @ 196318635 of size: 1088, ends @ 196319723
                     Atom stss @ 196319723 of size: 16, ends @ 196319739
                     Atom stsc @ 196319739 of size: 532, ends @ 196320271
                     Atom stsz @ 196320271 of size: 88328, ends @ 196408599
                     Atom stco @ 196408599 of size: 7368, ends @ 196415967
Total size: 196415967 bytes; 42 atoms total. AtomicParsley version: 0.9.0 (utf8)
Media data: 195643428 bytes; 772539 bytes all other atoms (0.393% atom overhead).
Total free atom space: 0 bytes; 0.000% waste.
Movie duration: 2116.513 seconds (35:16.51) - 739.49* kbp/sec bitrate (*=approximate)
Low-level details. Total tracks: 2
Trk Type Handler                    Kind Lang Bytes
1    vide [none listed]              avc1 eng   178711864
     675.58* kbp/s 2116.243 sec AVC Main Profile, Level 3.1 352x240 (330 macroblocks)
2    soun [none listed]              mp4a eng   16931556
     64.00* kbp/s 2116.513 sec MPEG-4 AAC Low Complexity Profile    channels: [2]
Jon Walker wrote:
In most cases, users want answers but are unable or unwilling to provide the encoding information to explain most problems, it is usually simpler to ask users to post a sample file for examination on my own computer.
I have the equivalent for the recording's Handbrake output. I did a file compare but there were enough differences (and I'm not a technical person) so I could not spot which of the differences mattered. For example, I thought that the fact that there is "none listed" for the sound handler looked like an obvious clue until I saw that same thing in the Handbrake output.
Here is the Handbrake data:
Atom ftyp @ 0 of size: 28, ends @ 28
Atom free @ 28 of size: 132, ends @ 160
Atom mdat @ 160 of size: 100944363, ends @ 100944523
Atom moov @ 100944523 of size: 1606698, ends @ 102551221
     Atom mvhd @ 100944531 of size: 108, ends @ 100944639
     Atom iods @ 100944639 of size: 24, ends @ 100944663
     Atom trak @ 100944663 of size: 1288497, ends @ 102233160
         Atom tkhd @ 100944671 of size: 92, ends @ 100944763
         Atom mdia @ 100944763 of size: 1288361, ends @ 102233124
             Atom mdhd @ 100944771 of size: 32, ends @ 100944803
             Atom hdlr @ 100944803 of size: 33, ends @ 100944836
             Atom minf @ 100944836 of size: 1288288, ends @ 102233124
                 Atom vmhd @ 100944844 of size: 20, ends @ 100944864
                 Atom dinf @ 100944864 of size: 36, ends @ 100944900
                     Atom dref @ 100944872 of size: 28, ends @ 100944900
                 Atom stbl @ 100944900 of size: 1288224, ends @ 102233124
                     Atom stsd @ 100944908 of size: 186, ends @ 100945094
                         Atom avc1 @ 100944924 of size: 170, ends @ 100945094
                             Atom avcC @ 100945010 of size: 50, ends @ 100945060
                             Atom colr @ 100945060 of size: 18, ends @ 10094507 ~
                     Atom stts @ 100945094 of size: 403832, ends @ 101348926
                     Atom stsz @ 101348926 of size: 253724, ends @ 101602650
                     Atom stsc @ 101602650 of size: 24436, ends @ 101627086
                     Atom stco @ 101627086 of size: 56712, ends @ 101683798
                     Atom ctts @ 101683798 of size: 484536, ends @ 102168334
                     Atom stss @ 102168334 of size: 1352, ends @ 102169686
                     Atom sdtp @ 102169686 of size: 63438, ends @ 102233124
         Atom edts @ 102233124 of size: 36, ends @ 102233160
             Atom elst @ 102233132 of size: 28, ends @ 102233160
     Atom trak @ 102233160 of size: 317950, ends @ 102551110
         Atom tkhd @ 102233168 of size: 92, ends @ 102233260
         Atom mdia @ 102233260 of size: 317828, ends @ 102551088
             Atom mdhd @ 102233268 of size: 32, ends @ 102233300
             Atom hdlr @ 102233300 of size: 33, ends @ 102233333
             Atom minf @ 102233333 of size: 317755, ends @ 102551088
                 Atom smhd @ 102233341 of size: 16, ends @ 102233357
                 Atom dinf @ 102233357 of size: 36, ends @ 102233393
                     Atom dref @ 102233365 of size: 28, ends @ 102233393
                 Atom stbl @ 102233393 of size: 317695, ends @ 102551088
                     Atom stsd @ 102233401 of size: 103, ends @ 102233504
                         Atom mp4a @ 102233417 of size: 87, ends @ 102233504
                             Atom esds @ 102233453 of size: 51, ends @ 102233504
                     Atom stts @ 102233504 of size: 24, ends @ 102233528
                     Atom stsz @ 102233528 of size: 264600, ends @ 102498128
                     Atom stsc @ 102498128 of size: 28, ends @ 102498156
                     Atom stco @ 102498156 of size: 52932, ends @ 102551088
         Atom udta @ 102551088 of size: 22, ends @ 102551110
             Atom name @ 102551096 of size: 14, ends @ 102551110
     Atom udta @ 102551110 of size: 111, ends @ 102551221
         Atom meta @ 102551118 of size: 103, ends @ 102551221
             Atom hdlr @ 102551130 of size: 33, ends @ 102551163
             Atom ilst @ 102551163 of size: 58, ends @ 102551221
                 Atom ©too @ 102551171 of size: 50, ends @ 102551221
                     Atom data @ 102551179 of size: 42, ends @ 102551221
Atom free @ 102551221 of size: 132, ends @ 102551353
~ denotes an unknown atom
Total size: 102551353 bytes; 54 atoms total. AtomicParsley version: 0.9.0 (utf8)
Media data: 100944363 bytes; 1606990 bytes all other atoms (1.567% atom overhead).
Total free atom space: 264 bytes; 0.000% waste.
Movie duration: 2116.640 seconds (35:16.64) - 381.53* kbp/sec bitrate (*=approximate)
Low-level details. Total tracks: 2
Trk Type Handler                    Kind Lang Bytes
1    vide [none listed]              avc1 und   65533744
     247.74* kbp/s 2116.243 sec AVC Main Profile, Level 4 352x240 (330 macroblocks)
2    soun [none listed]              mp4a eng   35410611
     133.84 kbp/s 2116.640 sec MPEG-4 AAC Low Complexity Profile    channels: [2]

Why does 4k "Set to Frame Size" shrink on playback ?

When I add 4k video to a 1080 timeline and shrink (scale) to 50% to make it fit, it fits perfectly when paused, but then plays back at half size within the 1080 program sequence window. I believe this is the preferred way to put 4k on a 1080 sequence but I am not sure why my playback shinks the size of the video further when I play it. Thanks for helping me understand what's going on here or if there is a better way to bring 4k into a 1080 sequence.

PR CC 2014.1. I just tested some GH4 4K (3840X2160) in a 1920X1080 sequence, scaling the 4K to 50%. Program monitor settings 1/4 and Full are okay, and 1/2 gives me constant jumps from full frame to a small box in the monitor. (Same whether playback and pause settings are matched or not.)
Removing the scale, gives the same type of effect. Stepping through frame by frame, I see that most frame are showing as full frame, then "zooming" in to the "regular condition" (no scale should display the too large 4K centered, right?).
Generating previews results in relatively smooth in all combinations.
Also, using the "scale to frame" results in smooth motion even if not rendered.
GH4 4K clips are 100Mbps recording. I suspected my system (just on my laptop) was not up to the task. But since unscaled is not the issue, I really don't know. I'll try to test this again on my PC at home tonight.

Why does the set-up of the Creative Cloud app stop suddenly?

When I click on the set-up icon, it will open the installation bar, but will stop suddenly and close. What's wrong?

Link for Download & Install & Setup & Activation problems may help
-Chat http://www.adobe.com/support/download-install/supportinfo/
OR
http://forums.adobe.com/community/download_install_setup
-http://helpx.adobe.com/creative-cloud/kb/unknown-server-error-launching-cc.html

Why does Word in the dock shows only Force Quit not Quit most of the time

Has anyone experienced problems with having Word in the dock that will not show Quit and only Force Quit most of the time when I put the cursor on W. No problems with other closing apps located in the dock.

Support for Microsoft Word - Microsoft Support

Why does my audio slip out of sync when exporting?

I am exporting an HD edited video. I shot 1280x720 & editing in FCP 6.0.5. I am using APPLE PRO RES 422 1280x720 30fps 48kz . Should it be (HQ)?? - I do not select re-compress all frames or make self-contained. I just want a QT reference file to view and then burn a DVD. My clip is 43 minutes long. HOWEVER, the audio drifts out of sync BIG TIME. Why is that??
Here are my sequence settings:
1280x720 Aspect Ratio HDTV 720p (16:9)
Square Pixels
H.264
Audio at 48kHz

That's what I thought, however, when I play back the .mov file after exporting using "current settings", that's when I experience OUT OF SYNC audio. Do I ignore that and drag and drop that file into iDVD and let iDVD crunch it??? Is it just the playback of that .mov file that is out of sync?

Why do premium movie channels alter the widescreen aspect ratio?

Why do channels like HBO HD and Cinemax HD change the aspect ratio of movies? I have seen movies that I own on dvd or blu-ray that are 2:35:1 or 2:40:1 aspect ratio (meaning very wide and you see some thin black bars at the top and bottom of your screen) but when they are broadcast on these movie channels it looks like the films are partially panned & scanned down to a 1:85:1 ratio (not as wide and the bars are gone).
This is really stupid, and the movies are not being shown in their full widescreen orginal presentation. What do they have to gain by cutting off parts of the picture? I have noticed some channels like showtime don't do this, but most do. Obviously this isn't verizons doing its the channel providers, but it's annoying.
And what's with all the logos all over the premium channels nowadays? These are paid channels the screen should be clear of any and all logos and any add overlays. If I want to know the channel and rating I'm watching I'll just press the guide button, it's overkill.

film11 wrote:
They do this for the OnDemand movies as well. I agree...it is VERY annoying. There is NO reason for it. Sure,there are some people out there who want their screen filled, but they can always use the ZOOM button to do that. It's a terrible practice and I never watch movies on channels that crop them (and am cancelling the channels that do it when my contract bundle expires). The only channels that show movies in the correct ratios are SHOWTIME, THE MOVIE CHANNEL, and HDNet MOVIES. (EPIX shows old movies in OAR but crop newer films.)
The others, Notably HBO that started this practice, do occassionally show OAR. But usually only when the director specifically had in his agreement that his picture would only be so displayed when marked to TV channels.

Does LR handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?

Does LR 5 handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?
I'm planing to buy a 27" 16:9 monitor and use it as primary together with a 22" 16:10. Does any have any idea?
Thanks

Moreover, the two monitors can have completely different characteristics. As always, you really need to calibrate/profile any monitor (with a hardware tool - Spyder, Colormunki etc). That's no more important with two monitors, but you see for sure if you don't, as two dissimilar monitors will then probably look different.

Why does FMS sets SAR to .mp4 to force 4:3 aspect ratio?

Similar Messages

Maybe you are looking for