Hi to all,

I was very happy to see the timecode-effect is built in as a (semi)realtime-effect. It runs with the sequence-TC in Half-Video-resolution (gree/yellow-Tab in timeline).

But there is a strange failure in the mac version: While enabling clip-information instead of TC-generation, the AVID freezes in. On the WinXP-Pro-platform it was no problem to insert the source-tc and the clipname.

Any idea? I could even post the crash-report generatet by the os if it helps. Just let me know.

Thanks in advance,

thommes

IT's working fine here. I just output a 13 min show using that function and it went without a hitch. Also, RT TC plays fine in Full quality mode here too. 

Maybe you have a larger issue with your setup?

Hi,

thanks for your fast response.

I found out the following: When I have a sequence with black holes (or a black leader), then the AVID crashes when switching from TC to sourcename. Now I filled up the black holes with some black.tiff and it´s working again. great.

RT TC in best PB-Mode only worked in SD - but not in HD with dnxhd. should it work in hd also? please let me know if something is wrong in my setup.

Greetings from germany,

thommes

It should, yes. What type of storage are you using?

EasyRAID. RAID Type 5. Connected via 320SCSI on a ATTO ul5d (Atto anything 5d).

Avid adrenaline on mac 2xdual2.66GHz.

Maybe mc3.0 with adrenaline problems (mac os 10.4.11 and 3.0.1) we currently use 10.5.? with MC3.0.

Hope, this isn´t too confusing...

greets,

thommes

You may be running into the problems with Leopard and the DNA. That's why the DNAs are not currently supported on Leopard. You may have a better time with 3.01 and Tiger.

hmmmm.... what could go wrong...? what kind of problems...? until now, the system is running fine...?!?

Crashes like a champ for me. I added it to it's own track on a sequence with some filler at the head, switched to source and got the spinning beachball of death. If I didn't have it go all the way to the begining (starting after the first clip - not very useful) it wouldn't crash. And I'm on 10.4.11.

Ah...I thought you said "Source TC". 

I too, get the beachball when using the source option.

Same problem. Major Bug for a top 5 new feature eh?

I have been using a "black" image instead of filler.

I have also noticed this on title medea.

brent

Confirmed here as well.... beach ball city...

yes yes yes. It´s about the beachball. After killing the AVID-App with Apple-alt-ESC it´s no problem to start the app again. The behaviour of the TC-generator is then reproducable. Everytime when there is nothing on the videotrack beneath the effect-track (e.g. some clips on V1, got some black holes or even "nothing" in the beginning AND the TC-generator on V2), the beachball appears and spins itself to death. Absolutly reproducable.

This is no issue of using MacOSX10.4.11 or 10.5.x due to the fact that this behaviour also occurs when DNA is switched off and AVID MC is rur as software-only.

This brings me to a question I asked some posts before - what COULD go wrong when using adrenaline-DNA with V3.0 (not 3.01) on MacOSX10.5.x? Until now the system is stable and I bought 10.5 because it was a system-requirement some weeks ago when V3.0 was ready for download. And now it´s not... 129,- Euros for nothing...

cheers,

thommes

the Generator-overlay does degrade the HD-picture in that manner, that a light blur is receptable. I switch my sequence-video-quality to "blue". Then I add a TC-Generator-overlay to the upper videotrack. When switching the viewer between V1 (edited Videclips) and V2 (TC-generator), the picture I view on my HD-Display (connected to the adrenaline analog hd-component out) is slightly blurred when switched to V2. On V1 the Picture is sharp as a knife.

Any suggestions? Anybody else with this problem?

For me, this behaviour is not elementary, but as blkdog reported, the generator-plugin should be realtime even in highest video-quality setting and therefore sharp.

Reminder: I am on MacOSX10_5 with MC 3.0.

Greetings,

thommes

This TC Generator crash bug is already logged with Avid and being worked on... I'll check out and report to Avid on the blurriness factor as well. 

See the other million threads on what can happen if you use a DNA with OSX 10.5.x.  It's a firewire device error that you expect to happen every 10 minutes or so at worst.  It requires a full restart of everything, CPU, DNA, etc...

thank you, Todd! I will watch out for crashes like that.

cheers,

thommes