So after overnight foreground transcoding so far 7 of ll clips have trancoded without error. One other thing is the first 3 F55 cameras that transcode approx 20 clips with only two errors were recorded internally whereas the other 6 cameras were recorded externally and 3 consecutive clips errored out after transcoding over an hour in the background.
Meanwhile on my home system I've had it transcoding similar long Varicam 35 4K 4096_2160 media in the backgound and it's half way through without error. One difference besides camera and media type is at home I'm not baking in the LUT. I know this reduces transcode times by 50% or more but perhaps it also reduces the chance of an error from loopplayback no progress transcode aborted. Just guessing. I hope Avid is listening to this. We have a full tilt 4K series and transcode issues can not be tolerated on that type of show given the volume and variety of media to process quickly.
---In Avid-L2@yahoogroups.com, <bigfish@...> wrote :
I'll see if I can test that. For now transcoding in the foreground seems to work. It's strange how the progress bar resets about an hour in on these long clips that have durations over 50 minutes. It starts with an estimate of a bit over an hour. That time runs up and right when it's near that initial estimate the progress bar resets to 0 time and a new duration left comes up around 30 plus minutes. When that runs out the clip finishes transcoding. CPU usage during the first hour before is up around 1700% but when the progress bar resets for the second part CPU usage drops to around 50%.
I saw a similar pattern when transcoding in the background where towards the end CPU usage dropped significantly. Given the Playloop error mention no progress aborting transcode it almost feels like the background transcode is timing out and not realizing the transcode is proceeding but at a much slower pace. This is just a guess on my part but I'm wondering what the code really is looking at to decide no progress. I didn't see the CPU% drop to nothing just way low for the transerver CPU usage. I wonder if the code is in essence just too impatient to let the process finish.
I left the last 11 clips, 3 of which had already aborted with background transcode , transcoding in the foreground. It will be interesting to see if any of them error out. If they don't then there must be some underlying difference in the background transcode. I've seen issues before with background transcodes on clips with multiple LUTs creating whacky media and also problems with background renders of similar clips. I think those issues have been resolved a few years back. Clearly there are some processing differences in the background clips. If I get a chance I'll try your unlink method to delete the data track info. I guess I can unline and ama linked clip and then relink. I haven't done that before.
---In Avid-L2@yahoogroups.com, <cutandcover@...> wrote :
Isn't this the old Sony cam media recorded data track transcode bug? Link the cam files, then unlink, modify tracks to remove the data track, then relink, then transcode. That has always solved the problem for me.
Found this old thread but I'm having this issue on several F55 clips todayAnybody else seeing this?John Moore Barking Trout Productions Studio City, CA bigfish@...
__._,_.___
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
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