Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

X264 vs. H264...

Download is ok for me, i get a 5,26gb zip-file.. But when i open it, the mov-file inside is shown with a wrong size (something around 1,2gb).
I tried 5 different unpackers...

edit: zip's filesize on my computer is 5.257.244.957 bytes
md5: 21aef277f2f35e28a2427cd638d2fb28
 
Last edited:
I'm not getting hung up at 4 GB because my Windows 7 installation is always formatted as NTFS.

I'll try to redownload it now. There seems to be a connection with the download errors and people on Windows machines.
 
Downloaded full 2K ProRes file in 5 minutes. No problems at all- looks great.
 
My download manager sees the file as 4.89GB even prior to actually downloading it, and that's exactly what was downloaded.
I use NTFS only (and 4.89GB is more than 4GB), so that's not the problem.

I Can't see the full 5.26GB at all.

Could this be due to some Windows restriction/incompatibility on the server side?

Eric
 
the file was zipped on a mac. unpacks perfectly back on a mac, i've seen this happen several times before. the way mac os zips files doesn't translate well to PC's
 
My download manager sees the file as 4.89GB even prior to actually downloading it, and that's exactly what was downloaded.
I use NTFS only (and 4.89GB is more than 4GB), so that's not the problem.
4,89 GB is the correct file size. 5,26 is just the "not really converted into real gigabytes with the right divider (1024)"-size.
Apple calculates with 1000, thats why OSX-users talk about 5,26GB and Windows-Users see 4,89GB. ;)
 
Last edited:
Worked great on my Mac Pro - took awhile as I was getting about 2 MB/sec download. Plays nicely!

Get Info says it is 5.41 Gigs.
 
Consistent?

Consistent?

I was wondering if the H.264 gamma or brightness and contrast or color errors are consistent on ALL H.264 players, or do the results vary on different players and OS used to play the files?

If the results are consistent, but just do not match, it should be possable to re-grade the source files to get the target values in the encoded file. You can shoot test charts and endode them, then measure the results to make some LUT to compensate for the movement of the image tones in the gambit.

If the drift is not consistent, then how does anyone get anything to play right?

If you make an uncompressed AVI, that should play the same on ALL computers since its just a series of 24bpp BMP frames.
 
I have converted the original to .mp4. I had to make a correction to them so they would look correct in QT7 and QT-X, but now they look too dark and saturated in VLC. So I am now stripping the correction and doing a 2nd version that is correct for VLC. Ugh.

Jim
 
I was able to unpack the file (which i've downloaded on my win-machine) on osx.

To summarize:
- no download-problems with windows and red's server
- 5,26GB vs 4,89GB is just a misunderstanding because apple and microsoft use different dividers for their calculations (and btw, apple is wrong here)
- the correct filesize in bytes is: 5.257.244.957 bytes it's md5-checksum is: 21aef277f2f35e28a2427cd638d2fb28
- no need to re-download if your file matches
- unpack problems are a result of incompatibilities with the used zip-program
- i still don't know a win-program that unpacks this file, sorry
 
I am curious as to why my file is 5.41 Gigs on my Mac Pro - OSX 10.6.7, while the "official" size is supposedly 5.26. Yet, mine plays just fine. ???
 
I have converted the original to .mp4. I had to make a correction to them so they would look correct in QT7 and QT-X, but now they look too dark and saturated in VLC. So I am now stripping the correction and doing a 2nd version that is correct for VLC. Ugh.

Jim

Welcome to the world of colorists ... AKA : people who spend sooo much time to create looks etc...and than have to spend even 3 times more to figure how have the odiens seen it right....

g
 
I always use http://www.7-zip.org/]7-zip[/url] on Windows machines. I'll give it a whirl once my download completes.
I had no luck with 7-zip, WinRAR, WinZIP, ZipStar and Total Commander's zip-plugin. Latest versions and x64 if available.
 
I was able to unpack the file (which i've downloaded on my win-machine) on osx.

To summarize:
- no download-problems with windows and red's server
- 5,26GB vs 4,89GB is just a misunderstanding because apple and microsoft use different dividers for their calculations (and btw, apple is wrong here)
- the correct filesize in bytes is: 5.257.244.957 bytes it's md5-checksum is: 21aef277f2f35e28a2427cd638d2fb28
- no need to re-download if your file matches
- unpack problems are a result of incompatibilities with the used zip-program
- i still don't know a win-program that unpacks this file, sorry

Maik,
Thanks for the MD5. I'll check the file later and see if it's OK.
But I still need a way to unpack it on a Windows machine.

Any ideas? anyone?
 
I have converted the original to .mp4. I had to make a correction to them so they would look correct in QT7 and QT-X, but now they look too dark and saturated in VLC. So I am now stripping the correction and doing a 2nd version that is correct for VLC. Ugh.
Don't waste too much time on color-correcting for vlc, its really not a reference player. It could be the case that VLC doesn't detect the right colorspace (BT.601 vs BT.709) and/or calculates with different levels (16-235 vs 0-255). At least that are the most common problems with different results on different software-players....
VLC isn't the best player when it comes to those things.

Best thing you can do is testing your encoded file on some kind of hardware-player and calibrated display. If its fine there its ready for distribution
 
Last edited:
Back
Top