Fyi: N5 64-bit version - no Decklink or AJA until QT goes 64 bit

[kdm]

Just an FYI, in reading some of the docs on the new video engine in N5 - since there is no 64-bit QT on Windows yet, the 64-bit install of N5 can't play video out Decklink or AJA cards. The install has to be 32-bit to use the 32-bit version of QT with these cards.

QT works in the 64-bit N5 apparently via a wrapper - just no playback via Decklink/AJA.

Question is, will Apple ever release a 64-bit version of QT for Windows. Seems Apple is dragging their feet on a lot of support for various things like 64-bit, Flash on i-devices, etc. Where does that leave us with N5 for post looking forward? 32-bit on 64-bit systems as the only solution?

What if Apple never delivers? I would like to move to full 64-bit later this year, but it isn't looking possible, at least not running N5 full 64-bit.

[MattiasNYC]

Wait, so you're saying there is NO solution for playing out via Decklink/AJA in N5 at the moment.....

[LEX]

Wait, so you're saying there is NO solution for playing out via Decklink/AJA in N5 at the moment.....

Sounds like it.

LEX

[kdm]

The only solution to use Decklink, as I understand it, is to run N5 as a 32-bit app, just as many have been doing with N4.

It's no different than with N4 since there is no 64-bit QT.

[Daryl]

How funny. I remember saying that using QT as a basis was a bad idea right back when we first heard about the new video engine. Shame that I've been proved correct. The reason that I had to get my Intensity card in the first place was that when I used the onscreen video it caused terrible audio glitching, and could only be solved by setting the audio priority to boost (thanks kdm). Of course this caused other problems, hence the Intensity card. So I wonder if the QT playback has now been fixed?

D

[paulwr]

I don't do post work, but for composing I'm fine with converting QT to AVI so I can work in 64bit envirornment in C5. I wonder if there is a way to now do offset with avi going to a video card on Nuendo? Can't do that yet with C5.1

-Paul

[Daryl]

I don't do post work, but for composing I'm fine with converting QT to AVI so I can work in 64bit envirornment in C5. I wonder if there is a way to now do offset with avi going to a video card on Nuendo? Can't do that yet with C5.1

-Paul
That's why I can't use Direct Show. I've been banging on about Frame Offset for Direct Show for years, but as usual SB is not interested. :>(

D

[paulwr]

Got to get these basic fundamental things working correctly for people that actually make money with the product. So many great things about the program, but this is one of those basic basic things that needs to work properly. I don't have any recent experience with other programs....... is it a difficult thing to create offset capability in all the video formats that Cubendo uses?

-Paul

[TAFKAT]

Maybe Steini really are shifting the focus of Nuendo to OSX ?

I can't see a 64 bit QT from Apple any time soon.

Thing is the Media Player engine in Win 7 natively plays QT, N5 supports video out to firewire natively , what am I missing here ?

[kdm]

I would have guessed it was easier for cross platform development, but with Apple's tradition of dragging their feet, esp. with Windows development, and zero/zilch motivation to support QT on Windows, it does seem either extremely risky, or a sign of an OSX move. Either way, doesn't instill confidence.

[Daryl]

Got to get these basic fundamental things working correctly for people that actually make money with the product. So many great things about the program, but this is one of those basic basic things that needs to work properly. I don't have any recent experience with other programs....... is it a difficult thing to create offset capability in all the video formats that Cubendo uses?

-Paul
The reason that the Frame Offset exists for QT is that it was designed for Mac users to be able to play video out via Firewire. At this point in time people weren't using LCD televisions, so there was no reason for Frame Offset for Direct Show, as Firewire video out wasn't implemented in Windows.

However, SB have known about this issue for years, so there is no excuse for not implementing it, IMO.

D

[TAFKAT]

At this point in time people weren't using LCD televisions, so there was no reason for Frame Offset for Direct Show, as Firewire video out wasn't implemented in Windows.

It is now....

[Daryl]

It is now....
However, as the new engine is QT only, nothing has changed. :>(

D

[Tumppi Järnefelt]

http://www.nuendo.com/phpbb2/viewtopic.php?t=22198&highlight=bit

Bye / Tumppi

[TAFKAT]

?

[paulwr]

So Fredo says there is a wrapper for 32bit QT to 64bit. If that works well, I sure hope that it is also implemented in Cubase 5.5. Composers need that badly, not just Post guys. Would still be nice to have other video formats have offset capability.

-Paul

[kdm]

Yes, the wrapper is there, but according to the N5 info-base, it doesn't work via Decklink/Aja - only within Nuendo/onscreen. To use Decklink, you have to stick to the 32-bit version of Nuendo (4 or 5).

[LEX]

Yes, the wrapper is there, but according to the N5 info-base, it doesn't work via Decklink/Aja - only within Nuendo/onscreen. To use Decklink, you have to stick to the 32-bit version of Nuendo (4 or 5).

Is that because of Decklink or QT 64bit?

LEX

[kdm]

Apparently it is an issue Decklink (and AJA), and the apps are stuck with as long as QT is only 32-bit - http://www.blackmagic-design.com/support/detail.asp?techID=160

Typical Apple.

[paulwr]

I have zero experience going out firewire with video. Maybe there's a smooth way to go that way somehow. Just be nice to offload the video work and have a nice big display not costing resources at the daw.

-Paul

[paulwr]

Cubase 5.5 64bit / W7 x64
Well, I got a no-fan Gigabyte video card / Nvidia GeForce 9800 GT. On first install, W7 (64bit) supposedly installed the drivers, but though QT and Mpeg Streamclip worked fine, Cubase was very slow video response..... missing a lot of frames so jerky. So I installed drivers from the video cards disk and all is fine. One thing, though, I have to offset video about 105 ms to be in sync. Is that a lot? I never needed to use offset before, but now I know the card is handling the grunt work and maybe that is why. Using the Open GL on the card.

I grabbed a video file I had trouble with earlier in the year due to frame rate of 23.98. QT .mov file H.264. Runs perfectly now, and not a hint of asio meter being affected by running video at highest resolution. So at first glance it looks like the new video engine is working great with the card doing the work. Hope the other framerates work as well as this. I need more time to mess around with it. On my system, I had no issue with getting the audio from the video file. Someone was mentioning it was a problem somewhere. Also, I'm not seeing any problem running in 64 bit with Quicktime at all.

This is granted not with a large session yet. But before now, video always took away resources from my audio and could be seen on the asio meter. Now, there is nothing showing. Just hope it is for real.

I'm only running video on a 19" screen now, but the card is supposed to handle 32" displays. Anyone run a large monitor yet with the new video engine? Able to use the card's processing well?


>>after some more testing...... the video in cubase still does hit the cpu. My Q6600 is at about 20% at the 100% video quality and full size. (on the task manager) and 10% cpu at 50% video quality. It seems much smoother, though. Before, there was spiking on the asio meter, now none. This is all with QT file 23.98 frame rate.

With an .avi file, it used less cpu .... .about 25% less. Not too scientific a test, but seems to be working a lot better than before with what I'm doing, and nice to have more framerate choices. For composing, this is looking nice. Post work..... I'm sure that may be another story with the Decklink issue.

-Paul