hows the new update
So far no issues. Will post back if I encounter any.
hows the new update
Still dont see much reason to upgrade from iflicks 1, or am I missing something?
So @iflicksapp -what's different between 1 and 2? Trying to decide why I should upgrade
@Tobar26th more metadata, better video processing, more flexible and better yosemite compatibility (no more Perian etc.)
version 1 works fine on yosemite for me.
Me too, works great and was free. See no reason to buy 2.
How did you get it for free?
Still dont see much reason to upgrade from iflicks 1, or am I missing something?
http://support.iflicksapp.com/hc/en-us/articles/208998567-iFlicks-2-2-2
Has anyone updated to iFlicks 2.2.2 yet? Anything get screwed up in the update?
So to update or correct my previous post... I only assumed the conversion was taking 2-3 hours. I set a file to convert last night and the timer indicated 3 hours. When I went back this morning the file still hadn't completed and was only,half way done after roughly 7 hours. Something is clearly wrong. I assume it's due to something with the trial I used. I will uninstall then try again. What is a reasonable amount of time I should expect for a MKV file around 2 gb in size? I know my system will dictate that but I have an average setup so a "round about" estimate is fine.
First, I assume you have iFlicks set to the "itunes compatible" preset.
MKV is the file container, but it doesn't tell us anything about how that file is encoded. iTunes likes files encoded in h264, with the M4V container. Changing containers is very fast. Changing encoding is very slow.
So if your MKV is encoded with h264, then indeed iFlicks can just remux the file into the M4V container, which should take relatively little time - takes my computer about 30 seconds per TV episode or a minute per movie. (I also have optimize for streaming enabled, which adds a tiny bit of time to the process, would probably be even faster without that).
However, a lot of new releases and new shows out there in the unmentionable pirate sites are now using h265 encoding. In this case, iFlicks has to totally re-encode the file. This means it has to decode the entire file, and then encode it in h264, which takes a considerable amount of time - takes my computer about 10 minutes per TV episode or 30 minutes per movie.
I hope Apple updates iTunes to support h265 soon. Afterall, the iOS devices support h265 now - it is the encoding used for facetime.