Luis de la Cerda
Well-known member
- Joined
- Sep 19, 2007
- Messages
- 132
- Reaction score
- 0
- Points
- 0
Is it planned to have redcine export to avi at any point? It would be really really really really really nice 
Welcome to our community
Be a part of something great, join today!
AVI export
- Thread starter Luis de la Cerda
- Start date
BASSAM MSSALATIE
Well-known member
- Joined
- Jun 26, 2007
- Messages
- 1,720
- Reaction score
- 1
- Points
- 0
- Location
- Abu Dhabi-Germany
- Website
- vimeo.com
yes it is good news .but do you think it is scary news cause already anyIs it planned to have redcine export to avi at any point? It would be really really really really really nice
avi export for 720*576 will need big space and storge so can you imagin
avi export for 4k or 2k sequences:angry01:
Stacey Spears
Well-known member
- Joined
- Sep 15, 2007
- Messages
- 3,130
- Reaction score
- 2
- Points
- 38
- Age
- 56
- Location
- Sammamish, WA
- Website
- www.spearsandmunsil.com
AVI and QT are nothing more than containers. Think of them as candy bar wrappers. It is what is inside that determines the size, quality, etc...
You can put almost the same thing in either. You can us Cineform, uncompressed (v210, UYUV, IYUV, etc...) or compressed.
One of the problems with QT is how the data is read. Many apps use the default SDK processing that comes from installing QT. This means your data will get converted to 8-bit RGB (most often using the incorrect color matrix) and then back. Inlet was nice enough to write a DShow QT reader that does not use the QT SDK. They wrote their own parser. It simply passes the data out of the container as is.
AVI has similar issues. VirtualDub is a great example of a tool that may do bad things to video in an AVI. It uses 601 (if the source is YUV) to covnert to RGB for processing. It also expands video to PC levels. All processing is done in 8-bit. I like VirtualDub, but I always use the directstream mode so no processing is done, including color conversion. It is a glorified AVI cutting tool for me. AVISynth has its share of gotchas, but tries to not convert if it does not have to. Its a great model, just needs higher quality support.
All in all, trust no one!
With the release of Leopard, Apple can now fix some of the QT issues or so they tell me.
You can put almost the same thing in either. You can us Cineform, uncompressed (v210, UYUV, IYUV, etc...) or compressed.
One of the problems with QT is how the data is read. Many apps use the default SDK processing that comes from installing QT. This means your data will get converted to 8-bit RGB (most often using the incorrect color matrix) and then back. Inlet was nice enough to write a DShow QT reader that does not use the QT SDK. They wrote their own parser. It simply passes the data out of the container as is.
AVI has similar issues. VirtualDub is a great example of a tool that may do bad things to video in an AVI. It uses 601 (if the source is YUV) to covnert to RGB for processing. It also expands video to PC levels. All processing is done in 8-bit. I like VirtualDub, but I always use the directstream mode so no processing is done, including color conversion. It is a glorified AVI cutting tool for me. AVISynth has its share of gotchas, but tries to not convert if it does not have to. Its a great model, just needs higher quality support.
All in all, trust no one!
With the release of Leopard, Apple can now fix some of the QT issues or so they tell me.
Mike McCarthy
Well-known member
AVI does not necessarily mean uncompressed, so the data rates have little to do with it. AVI support would be all about application compatibility.
Gavin Greenwalt
Well-known member
- Joined
- Dec 29, 2006
- Messages
- 7,614
- Reaction score
- 0
- Points
- 36
- Age
- 40
To quote my Avatar "O RLY?".
Have they been too busy working on Leopard for the last 7 years? :usd: