[Toke]

Seems to be that pPro (I’m on a Mac) doesn’t either support any 10-bit YCbCr codecs neither…

[Toke]

Found a solution.
Problem was that I was using 10-bit RGB codecs (SheerVideo & AJA) and pPro doesn’t seem to like them. Straight alpha with SV’s 10bit4:2:2 seems to be ok…

[Toke]

Well, you guess wrong.
Been there, done that.

[Toke]

Conf1:
1900xtPort1:1920x1200dvi
1900xtPort2:1600x1200vga(menubar)
7300gt: no monitors
MotionMaxRez: 4096×4096

Conf2:
1900xtPort1:1920x1200dvi(menubar)
1900xtPort2:1600x1200vga
7300gt: no monitors
MotionMaxRez: 4096×4096

Conf3:
1900xtPort1:1920x1200dvi(menubar)
1900xtPort2:no
7300gt: no monitors
MotionMaxRez: 4096×4096

Conf4:
1900xtPort1:1920x1200dvi(menubar)
1900xtPort2:no
7300gtPort1:1600x1200vga
MotionMaxRez: 4096×4096

Conf5:
1900xtPort1:1920x1200dvi
1900xtPort2:1600x1200vga(menubar)
7300gtPort1:1600x1200vga
MotionMaxRez: 3344×3344

Conf6:
1900xtPort1:1920x1200dvi(menubar)
1900xtPort2:1600x1200vga
7300gtPort1:1600x1200vga
MotionMaxRez: 3344×3344

Conf6:
1900xtPort1:1920x1200dvi(menubar)
1900xtPort2:1600x1200vga
7300gtPort1:1600x1200vga
MotionMaxRez: 3344×3344

Conf7:
1900xtPort1:1920x1200dvi
1900xtPort2:no
7300gtPort1:1600x1200vga(menubar)
7300gtPort2:1600x1200vga
MotionMaxRez: 2364×2364

Conf8:
1900xtPort1:1920x1200dvi
1900xtPort2:no
7300gtPort1:1600x1200vga
7300gtPort2:1600x1200vga(menubar)
MotionMaxRez: 2364×2364

Conf9:
1900xtPort1:1920x1200dvi(menubar)
1900xtPort2:no
7300gtPort1:1600x1200vga
7300gtPort2:1600x1200vga
MotionMaxRez: 3344×3344

Conclusion: primary screen does affect maxRez, but not alone.
You can’t use 7300gt at all, if you want to have 1900xt’s maxRez…

[Toke]

[Shane Ross] “But I also want to add that the post workflow is EVERYTHING. What is the point of shooting all this footage if you can’t do anything with it? Or if working with it is difficult?”

You are so right in that…

[Toke]

[Jan Crittenden Livingston] “I think the problem for any of the developers is that it was not until late last year in 2005 that 720P was even going to be an accepted format in EU.”

If I still may continue on this topic; isn’t it quite irrelevant what format is chosen for broadcasting? It won’t be anyway same as acquisition format.

All I wanted to hear by joining this topic, was others opinion about would it be businesswise smart to offer NLE codecs with the acqusition hardware, rather than wait for 2 years (or more) for NLE manufacturers to add support. AFAIK, Panny has been offering 1200-vtr and varicam for Europe since 2004.
I also suggested that in future making your own codecs might be even more important. (RED will make its codecs, SI+CF will use their own, etc., this is the IT revolution, more and more depends on software…)

Since my nagging wasn’t considered quite productive, I’ll just shut up about this subject and patiently wait for those qt-codecs. Maybe next August, maybe not…

[Toke]

[Jan Crittenden Livingston] “Toke, this is not what I said and frankly I am a little irritated that you have decided to obscur my words. What I said was we do not write code, we do not know how to make a Quicktime codec to work in Apple.”

I’m sorry if I irritated, but I didn’t meant to obscur your words, I just tried to tell how it made me feel.
I’m also sorry if I have misunderstood that Panny does write a lot of code; lots of drivers to your products.
I was under impression that eg. hvx’s usb drivers, fw drivers, p2 drivers for pc-card slot and p2 viewer were written by Panny.
So if you do have an army of coders to write drivers for dozens or even hundreds of products, it might not be so big effort to write your own qt-codecs for your own compression format. If my assumption was wrong, I’m sorry again.

[Toke]

[Ron Lindeboom] “The truth probably is — and Panasonic is likely just too nice to tell you (but I am not) — that you have nagged and nagged on people so damned much with the same tiresome rhetoric that no one wants to take your calls anymore.”

Your guess is wrong.
I put a question in panny europe’s forum, got an e-mail answer to that over a month later, gave some feedback about four(4) detailed issues I’ve had with european hvx and got answer that feedback was sent forward three weeks later.

[Toke]

[gary adcock] “Toke
you keep getting the same answer every time you ask this (this being the 3rd or 4th time I have answered)
Asking Panasonic to write code for Apple is a tad foolish don’t you think? Apple writes the code for it’s application even for the FRC plug in for Final Cut Pro.
The codecs are there. Just because Apple did not implement them for FCP, does not mean they are in use everyday around the world in the cameras and with other edit systems.
The DVCPROHD codec is only for 100mbps data,
The DVC/PRO ( DV25) and (DV50) SD codecs work just fine in FCP at both 25p / 50i have been in use for a number of years all over the world.
Just because Apple does not currently support 720 @ 25p/50i does not make it Panasonic’s fault.
“

Sorry for repeating this question, I only repeated it, because Jan asked for it.
Asking hardware providers to support their hardware by offering drivers for their products (this time codecs) isn’t very foolish don’t you think?
Would you buy a printer without a driver for your system?
Well, I was foolish enough to buy a camera…

In the past, when cameras used just one codec, it wasn’t so necessary for camera manufacturer to release “drivers” (=codecs) for every model, since the NLEs usually supported the cameras already. Things have changed since. Today it seems a bit awkward to ask NLE producer to support every camera model, when each of them can have several unique codecs. I’d say that it is camera manufacturer’s responsibility to make sure that the product has a feasible workflow.

The codecs are there?
Well, 720p25 or 720p50 are not there (or at least here)!
And we all know that these are the sweet recording modes for hvx right now.
1080p gives only minimal increase to resolution and since we can’t get 8GB p2 cards over here, 4GB card’s limited recording time really cripples the camera.
And since there’s little use for 4GB cards, there’s no sense to buy a lot of them, since their value will drop near zero when 8GB cards will be available and 720p codecs are not.
And the other alternative to shoot SD isn’t very attractive either. Why buy hd camera with variable frame rates, if you can’t use them?
I bet that if there were a poll among US hvx users, 90% of footage is shot in 720p. 720PN is just the sweet spot for this camera with present p2 card prices (even if 8GB cards are widerly available in US).

I have a shooting next saturday, where variable framerates would be essential and man, I hate to do this, but I don’t see any other way than shooting 720p and dubbing to dv-tape. Goodbye to hd and tapeless workflow…

[Toke]

I’m sorry to hear this attitude from Panasonic; it’s like saying “we don’t care if you’re not getting support from apple, we won’t give that to you.”

Even small companies like BitJazz(SheerVideo) have made very nice codecs for QT that can be used very fluently in FCP.
So Panasonic would have muscle to produce the software for European mac users (like you produced P2 Wiever for windows users), but you chose not to do that.
Maybe you know then why dvcprohd isn’t so successful in Europe and you accept it.
And maybe apple has 720p codecs “in the works” and they will announce them before first products that uses it have been less than two years in the market.

Meantime Panasonic Europe’s support and service keeps surprising me.
Now, I got an answer after three weeks that the employee that I e-mailed has been sick ever since.
What kind of support does not forward e-mails of a employee to others that are not sick?
How basic these things are?