Jaap Verdenius
Forum Replies Created
-
It may be problem that occurs in PAL, not in NTSC …
-
Well I did, and then you the first frame has a duplicated field.
You should look closely.Jaap
-
Thanks Dana, I will try that! And I hope things will get better at 5.1.3 or 5.2 or 6.
-
How do I enlarge the waveform cache, John?
In System Settings > Memory & Cache I can find settings for Memory Usage and Thumbnail Cache, but no Waveform Cache. I also can’t find it in the manual.
Can I do it somewhere else?Jaap
-
Sorry for this very late reply, Luke; but I was on a holiday for a few days.
I tested as you said without the Decklink drivers and then there were no crashes – however as it remained difficult to open FCP I decided to reinstall MacOS, FCP and the Decklink drivers all together and now the problem seems gone.
It is impossible to define what exactly caused the problem, but my guess is that there is something in the Avid’s Mojo driver that may have conflicted somwhere with Decklink’s SD drivers – at least the fact that the problem was restricted to the PAL and NTSC capture settings of Blackmagic within FCP points in that direction. I’d be happy to know your thoughts on this.Jaap
-
I don’t think it is something between 5 and 5.1. Both my computers have 5.1.2 and the problem is still there.
-
Waveforms are on on both computers, and both are 5.1.2, Jeff. I should add that I noticed this problem since 5.1.
I am doing projects with timelines containing 6 tracks of 1 hour. Creating a wavefom is some kind of a background process and it takes some time for a waveform to be fully available at all levels of detail. For me it is really without doubt that the regions of the waveforms that are created by my PPC machine are neither displayed nor regenerated by my Intel machine (EXCEPT when I zoom in the timeline to the very max – but when I zoom out the little crosses reappear). It seems to ignore these regions.
I have no explanation, and it is very annoying to work without waveforms – I’d be happy with any solution -
Sorry Luke, you got me wrong – I uninstalled the BM drivers, then reinstalled them and then get FCP to crash when trying to enter any of the BM capture settings that relate to SD codecs – the PAL setting, the NTSC setting etc.
It quits after pressing “Edit…” or “Duplicate…” and before the capture settings window pops up; and it takes a few seconds.It doesn’t crash when I try the same with the BM HDTV settings or the native Apple settings.
Still sure it has nothing to do with the BM drivers?
Jaap
-
PS: Luke, I tried if I could get BM Deckcontrol to crash, but without success; then back to FCP I could duplicate and edit a BM setting, but only once; next time it crashed like before. I know it sounds irrational, but there it is.
Could it have anything to do with my having installed (and removed) Avid Media Composer and an extra FW card for its Mojo recently?
Jaap
-
Then it still crashes, Luke. Let me add that it only happens with all non-HDTV settings of Blackmagic (I can’t edit the setting, it quits before I get there), and that FCP recently also quits on open, sometimes 5 or 10 times in a row, and then mysteriously starts working as if nothing happened.
Jaap