Lindsay Simpson
Forum Replies Created
-
-
Good to know you are running CC 2017 successfully on 10.12.
My system has been super stable, hence my reluctance to upgrade. But alas, maybe it’s time. I can’t bump up to CC 2018 without upgrading another piece of software (not CC) in my workflow. Must wait for budgets to allow the upgrade…
I was able to fix the nesting issue by deleting PPro preferences and re-installing the software.
I’ve definitely found dynamic linking with AE to be too buggy to use, but haven’t had too many issues using pre-comps for warp stabilizing. I prefer to avoid building out stabilized Quicktimes to save storage space, but it’s the work around I had been using while this bug had hold of my software.
I appreciate the reply!
-
I have experienced this same issue with my DVX 200. I am using 2 duplicate cards (Speed and Brand) and I have the camera set to relay record. It will not automatically switch cards. I must enter hte menu and manually switch to the next slot.
-
Lindsay Simpson
February 7, 2017 at 3:55 pm in reply to: CatDV 11.1.8 Support for Premiere Pro CC 2017?Many thanks for the reply! I’ll touch base with sales.
-
Lindsay Simpson
November 11, 2016 at 9:43 pm in reply to: CatDV Sending Proxy Files to Premiere Pro Instead of Original MediaYep, definitely operator error on my end. I built my proxies after shifting/renaming bin folders and simply needed to update the media location…
-
Lindsay Simpson
October 20, 2016 at 5:33 pm in reply to: Proper Display of Multi-Check Box Custom FieldThank you! The multi-grouping solution is just what I needed!
-
Lindsay Simpson
July 19, 2016 at 2:59 pm in reply to: Feature Not Working After Update – Send to Premiere Pro CC2015 FunctionThank you for the status update! I look forward to the release of 11.1.7.
-
Lindsay Simpson
July 8, 2016 at 6:01 pm in reply to: Feature Not Working After Update – Send to Premiere Pro CC2015 FunctionEmail sent. Thank you for your reply here Paul.
-
Lindsay Simpson
April 18, 2016 at 4:50 pm in reply to: “XXX.cdv.autosave” file Versus “BackupOfXXX.cdv” ?Okay, I’m somewhat embarrassed that this thought only now dawned on me…
Why are these “autosave.cdv” files only now become “visible” in this common Drive storage location?
Again I think this is a Drive syncing issue as I am now experiencing some other inconsistencies. But, if CatDV has been building “autosave.cdv”automatically every X # of minutes since the creation of an individual catalog, I’m a bit baffled as to why I am just now physically coming across these files. And the “autosave.cdv” files are only visible/accessible for those catalogs that have received the Drive warning below.
Shouldn’t there be an “autosave.cdv” file for every catalog? Below are all of the current catalogs and any associated “autosave” or ‘Backup” files.
Thanks for you time, feedback and patience!
-
Lindsay Simpson
April 5, 2016 at 7:33 pm in reply to: “XXX.cdv.autosave” file Versus “BackupOfXXX.cdv” ?Thank you for clarifying the difference between these files types. This was immensely helpful.
I think I have pinpointed the source of this recent change in our system, and it’s likely human related.
Thank you!


