No, the media was not imported first. Empty project. Clips were added after import. Yes, reels were imported.
Ok, more info. If your database is local, then everything is ok. No issues. But if your database is on a shared database (MySQL) then the issue shows up.
For what it’s worth, we have MySQL Community Server 5.6 running on Win Server 2008.
1 Like
Hmmm… tried MySQL with an empty project and still can’t reproduce this. I did once see an error in the logs that looked like it could be related, but now I can’t make that happen either.
I tried using your manifest and one created here. LUTs are importing and sticking fine every time.
Server version: 5.6.13 MySQL Community Server (GPL)
Do you get any errors in the log when you import the manifest?
OK, I spent some time trying to nail down exactly what is happening and how to (hopefully) replicate it.
It appears to be more of a UI bug. But you can try these steps:
- Start a project on a shared database (Enterprise, MySQL)
- Add clips to project. Apply LUTs.
- Make a new reel and add the clips to the reel.
- Go to a different computer. Open the same project. Look in the Status column.
It seems that the major factors are A) if a clip has already been added to a reel and B) opening a shared project from a MySQL database.
This could possibly explain why I was seeing this issue when I imported the reel info from the manifest at the same time. I can go back and try importing without reels and see what happens.
One more thing - we’ve noticed this same UI behavior just sharing a project in 1.5.3 b5172 (so it’s not so much related to importing manifests as it is to sharing projects and having open reels).
Here’s what I’ve seen: Computer A started a project, imported clips, applied LUTs, added some (not all) clips to a reel. Computer B opened the project - the clips that were not in the reel had the LUT symbol. Clips that were not added to a reel yet did have the LUT symbol.
Edit: since this isn’t really related to importing manifests, I’m going to edit the discussion name.
I tried to reproduce that here, but didn’t have any luck. Do the clips that do not have the LUT symbol also not have the LUT applied on the other computer?
@peter - If computer A has the LUT applied (LUT symbol, color, etc) then I open the project on Computer B, the icon is not present on Computer B. The input/output LUT columns have a LUT name, but no symbol.
OK, I’m sorry if this seems like a problem on our end. Bear with me. Here’s what I do know:
- the Input LUT and Output LUT names are appearing in shared projects (this is great, it means there’s a LUT name applied)
- sometimes the LUT icon is not showing
- when the LUT icon is not showing and the clip gets rendered, it gets rendered without color
And our setup: the project has the Stills/LUTs folder pointing to a folder on a shared StorNext volume, mounted as X: drive (so the path is actually X:/zzzz_Cortex_Stills_DO_NOT_DELETE ). Looking in this folder I can see the project and in the luts folder there’s two XML files named with UUID names (ie d2b60df8fa50000e848dda8f8090805c.xml).
When I open a project, there’s no LUT icon in the Status. When I click on a clip, there is color. Then when I click a different clip, the LUT icon shows up for the first clip.
There’s nothing in the log that says it couldn’t load LUT or anything.
I know this is really weird and hard to nail down. If you want to jump on via TeamViewer to see, I can set that up.
@24pdailies I don’t need to log in to see this, but to me it sounds like the color isn’t being saved properly on the first machine somehow. Could you send us a database snapshot along with the names of the clips that don’t have the LUT icons showing up on the second machine?
@peter - yes, I can prep a database and will send to you shortly. But I believe the color is being saved correctly.
I think I have a very simple way to replicate this on your end. Could you try these steps:
- New project on a shared database
- Import clips (I am using F55 XAVC 4K MXF).
- Apply Input and Output LUTs to all clips.
- Close the project
- Reopen the project. Look at the status column. Compare to the Input and Output LUT columns.
I think the reopening of the project is where things get dicey. This could explain why the 2nd computer is showing problems while the 1st is not. Also why it’s not being replicated easily.
Let me try that here before you send a database. I’ll get back to you shortly.
I tried those exact steps here and I have a LUT icon next to all 127 clips I imported, and the two LUT names in each column.
Yeah I can’t reproduce the problem here either.
Well thanks for trying. But I swear I’m not going crazy (that’s what you’d expect a crazy person to say though 
It might be something to do with our setup and where the files are at on our network and such. Let me send you the database and stuff.
I do know (at least on our current setup) that if you open the project you’ll only see one or two clips with LUT icon, but the LUT names are in the columns. But if you start clicking on each clip, it “sees” that there should be LUTs, and when you click to a different clip, the LUT icon shows up in the previous clip. This actually “fixes” the issue; the next time you open the project the LUT icon shows up fine. (this might be, as peter said, the color isn’t being saved properly on the first machine)
But like I said, I’ll send you the database
Well, I can see the same thing you’re describing if I import your database. The LUT icon is missing from most clips, even though the columns show the LUT name for input and output.
Don’t understand much else yet, but we should be able to dig deeper with this.
OK, so somehow the project looks like it has some bad records saved for those LUTs which then cause problems whenever you try to use them. We don’t know how it got to be that way, but @peter has some checks in there now to attempt to fix the issue on the fly.
Here’s a test build that you can try out with that project.
Your LUTs should all load properly now if we did this right. If it looks good, let us know and we’ll roll this fix into the next v1.5.3 release.
@24pdailies - tests look good on this end so we’ll roll this into the next v1.5.3 release. Would still be good to get confirmation from you when you get the time to test it though!
Just tried this new version out. Looks good! The LUT symbol is showing up. What’s more, it appears that it repairs the database - when I opened the same project back in 1.5.3 b5172 the LUT symbol is showing up there as well.
Good job @dave and @peter! This was a slippery bug and I’m glad you were able to fix it.
2 Likes
Thanks for following up. We still don’t know what caused it but at least it won’t be catastrophic now with the automatic repair.
This topic was automatically closed after 2 days. New replies are no longer allowed.