AFAIK, QT7 does a fine job, but what I don't know is how it handles 422 encoded material.
I know for sure QT player 7 can't play it, but perhaps it is able to re-wrap.
On 21 Jul 2018, at 11:00, Bouke / VideoToolShed <bouke@videotoolshed.com> wrote:AFAIK, QT7 does a fine job, but what I don't know is how it handles 422 encoded material. I know for sure QT player 7 can't play it, but perhaps it is able to re-wrap.To send files, go here:On 21 Jul 2018, at 05:11, John Pale pale.edit@gmail.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:Yes, David...doing a "Save As" will present you with the choice of a Reference Movie or a Self Contained Movie.. Just choose Self Contained and you are good.Hopefully Bouke will let us know whether this results in a proper re-wrap from .mp4 to .mov. It seems like it ought to be.On Fri, Jul 20, 2018 at 3:59 PM David Ross speckydave@gmail.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:Does "Save As" in QT7 really create a self-contained file? I thought that would just create a reference file.I know in QT7 you CAN re-wrap as MP4 from an H.264 QT by Exporting and selecting "pass-through" for both video and audio - but I don't know if you can do it in the other direction (MP4 to QT).Mpeg Streamclip does (I believe) re-wrap with its "Save As" command though.D.
--
Sent from my mobile phone - please excuse spellung.
Yes I do have your Mp4toQT app. I am always amazed at all the extra features/functions your apps have. QT Change and this one have helped me several times along with the QT Map app that let me convert interleaved audio to discrete tracks. Thanks for reminding me of the added functionality.IIRC I got the Mp4toQT to help with go pro footage and to help give them unique reel numbers and time code. Unless I'm confusing the functionality with one of your other apps.It was also pointed out I can take the resulting AME H_264 and open it in QT Pro 7 and do a Save As. That was very fast. Does using QT Pro 7 Save As maintain all the proper essence and metadata to make it a non cheated .mov?
---In Avid-L2@yahoogroups.com, <bouke@...> wrote :And you can paint lead yellow, and sell it as gold, but you might get caught.In this case, it's true the essence is the same, but the container is not. Changing the extension does not do anything except changing the extension.Getting away with it is not the same as doing it right.(My Mp4toQT app does it properly, without changing the content. IIRC the OP has that, so that's not the issue.)You can change the extension on the .mp4 file to .mov, and you'll have what the client wants at the quality that you want :)
The H264s that AME make are indeed much better than the ones that quicktime will make.Jeff
------------------
Jeff HedbergDirector of Operations
Union Editorial
575 Broadway,6th floor
New York, NY 10012Having been in contact off list with Mr. Pale and Mr. Spano it seems the culprit is that I'm making a QT .mov in H_264 and not using the straight H_264 that makes a .mp4. I'm told when making the QT H_264 Adobe Media Encoder uses the QT engine which is inferior to the internal code AME uses to make a .mp4.Now my quandary is if Avid is using the QT engine in the custom export, which has always been my understanding, why when AME uses the same QT engine is the result so much worse and blocky?I did make a .mp4 in AME and it is much cleaner. Now I will have to see why the network wanted an H_264 as a QT .mov and if they are okay with a .mp4. I don't know why they wouldn't be able to accept either but you never know what the internal workflow is and how flexible the configuration is.
---In Avid-L2@yahoogroups.com, <bigfish@...> wrote :It's a quicktime with the H_264 codec. So it is a .mov. This was the network request to have a QT h_264 IIRC
---In Avid-L2@yahoogroups.com, <pale.edit@...> wrote :Are you rendering in Media Encoder to H.264 as a .mov or an .mp4?On Thu, Jul 19, 2018 at 4:34 PM John Moore bigfish@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
I don't make a lot of screener files but I have been using Adobe Media Encoder with QT Ref files out of Avid for various delivery files with good results.I'm finding that if I make a QT in H_264 codec frame size 640_360 data rate 1500kbps (1.5Mbps) quality 100 the Adobe Export is much blocky compared to exporting from Avid doing a custom export.Avid sequence is XDCam50 and DNX 175X. I render a safe color to DNX115 which is the delivery codec required. I export a QT Ref and use QT Pro 7 to do a save as. I use the resulting file in Adobe Media Encoder and get the blocks. Avid export to H_264 is soft but not blocky, which is more pleasing to the eye..I don't do a lot of experimentation with compression etc... but I am surprised how visible the difference is given the data rate is the same.I would think Adobe Media Encoder 2015 would have very similar results to Avid using custom export/QT Engine. Are there any under the hood tweaks I'm missing in AME?John Moore Barking Trout Productions Studio City, CA bigfish@....
__._,_.___
Posted by: Bouke <bouke@editb.nl>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (12) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
this is the Avid-L2
SPONSORED LINKS
.
__,_._,___
No comments:
Post a Comment