Wickham Strub
Forum Replies Created
-
I got it. It crashes for me too. I’m already onto something. Stay posted.
~Wick
-
Andy,
Send an attachment of the offending XML to support-at-media100-dot-com and I’ll see if it crashes for me too. If so, I can have some folks smarter than me take a look at it and we’ll see what we can do.
~Wick
-
Hey guys,
Sorry for the delay, I spent the last two days talking to a lot of people about how to answer this and, unfortunately, I can’t.
I hate to do it but, in this case, the stereotypical lawyer-speak answer really is the appropriate one. We simply do not publicly discuss features that we have not publicly announced.
I CAN tell you that this sort of support is not out of the question, it’s something that is discussed frequently in house and something that we would certainly “like” to do. We are constantly making decisions about where to focus our resources. Sometimes this means our customers will feel like a feature or two is “missing”. We are not the only company in the world that has to make these sort of choices. I personally would LOVE to be able to go straight to Blu-ray out of DVDSP, but Apple hasn’t put that in there yet.
So, again, sorry I can’t always answer your questions, but PLEASE don’t stop asking them.
~Wick
-
Hmmm…
What codec are these files being capture to in Media 100?
-
Hi there,
I have been unable to nail down an answer to this question because I do not have access to this camera to test with.
I’m thrown off a bit by the specs on the camera. The “progressive” on the camera are marked as 24f and 30f, not 24P and 30P. The best info I can find thus far states that it actually records “fielded” media with each field in a frame containing the same image, giving the illusion on playback of a progressive image.
The first question is, is this really just a different name for PSF (progressive segmented frames)?
The second question is, is it REALLY 24 fps or is it actually 23.98? MANY cameras from all the big manufacturers are guilty of putting “24” in the camera menu when they are actually capturing 23.98.
A final possibility is, the camera may actually be capturing and playing at 29.97 while inserting 3:2 pulldown, in which case none of this matters.
Sorry to throw this back in your court but…
Do you have any idea what your camera is really capturing when you set it to 24f? Does anyone else out there with the same camera know? The answers may help me work out an answer the the original questions.Having said all that, Media 100 v13 is available as a Try and Buy. It is fully functional for 2 weeks with no watermark and no hindrance whatsoever. You could always give it a try and see what happens. This would be the fastest way to answer your question for now.
-
Paul,
I ended up not responding to your post earlier this week as I had promised because…
1: Floh got to the versions question first.
and
2: I realized that you had already provided the answer to the price question yourself by including the link to our online store.As for THIS post, what is your point? Are you honestly still confused? It’s not that complicated. I don’t want to drag this on and on in a pointless flame-fest, I’m only continuing with this for the benefit of those following along that may be swayed by you into thinking that it’s actually that difficult to figure out.
Media 100 Producer is a software-only application. It does not use 3rd party I/O hardware. You can bring media in and out via FireWire or Import and Export. It also includes Boris RED as the titling and compositing application, software that normally costs $995 on it’s own. The price for Media 100 Producer in North America is $995 USD.
Media 100 Suite requires I/O hardware. It uses three different OEM cards from AJA, the LSe, the LHe and the K3. Each card has different capabilities and therefor lends different capabilities to Media 100. It also includes Boris RED as the titling and compositing application, software that normally costs $995 on it’s own. The price for Media 100 Suite in North America is $1495 USD.
~Wick
-
I’m guessing from the time/date stamp on your post that you’re not in North America so… that complicates things a bit.
It’s still Feb. 4th here, almost 10:00pm. I’ll check in with some other people at the office tomorrow morning with the details and get back to you then.
-
Wickham Strub
February 4, 2009 at 5:08 pm in reply to: Unusual renders and Serial Wrap hardware test errorsHey Patrick,
I have to preface this by saying that Media 100 i is an OLD product by almost any standards (it’s been out of active development of over 3 years now), so I apologize for not being able to say exactly what your errors mean.
Having said that, when I was doing Tech Support full time there were certain errors that stuck in my head either because they sounded funny (for some reason “Serial Wrap” always tickled my funny bone) or because they ALWAYS ended up meaning broken/dead hardware. I remember your errors as being ones that point to broken/dead hardware.
~Wick
-
Hmmm…
Did you log out and back in to the OS? Restarting covers that.
Other than that, are you SURE you downloaded the Intel-friendly version of the codec? Did you already have the PPC-only one installed first? Maybe it didn’t get overwritten by the new one.
Sorry that it sounds like I’m taking shots in the dark, but I am. This just shouldn’t be happening the way you’ve laid it out.
Another idea… Sometimes creating a new user account and trying under the new account “fixes” problems like this.
~ Wick
-
Wickham Strub
January 28, 2009 at 9:10 pm in reply to: QuickTime 7.6 Resolves Issue with Media 100 i and MJPEG B CodecsGood point Floh (DAMN he’s good). Unfortunately, it’s a scenario I am completely unable to test right now. Anyone out there successfully running the following config:
– OS 10.4.11
– QT 7.6
– M100 v12.1.3or perhaps and even older setup?