Floh Peters
Forum Replies Created
-
[Jason Rogerson] ” I wonder if the image would be crisper if I could import the EPS since it’s vector based.”
If you prepare the PSD in the right dimensions it will be as crisp as a EPS, since as soon as the file gets imported into the system it gets converted to a pixel-based format anyway.
-
I heard that the 10.5.7 update may cause issues. Haven´t tried it yet, but I will do some tests as soon as I find some time for it.
-
Not sure why it does not work, but I would suggest converting the EPS to e.g. PSD or JPEG in the correct resolution and aspect ratio for your project before importing.
-
[Doug Calhoun] “Will a blackburst generator solve the issue and if so, any recommendations?”
Most likely a BB generator will not change anything here. You should check if you can set your deck to PB instead of EE, and if this changes your problem, but I think not. As far as I know you have to disconnect the Y from your decks input.
[Doug Calhoun] “The signal is NTSC SD component in 525i 29.97 (601 4:3) brought in Media100i Codec as well as DV, DVCPro(25mb/s), DVCPro50 (50mb/s) and again over Firewire again minus the Media100i codec.”
What is your souce footage? DV? Then if you do a transfer via FireWire from tape into DV inside your Media 100 system, the files you get are identical to the material on tape. There is no transcoding/recompression/rewrapping or anything done to it, just a 1:1 copy of the digital data from tape to your HD. So if your source is DV (orDVCam or DVCPro25) it does make sense to acquire into the native codec.
[Doug Calhoun] “The signal is monitored out composite from the deck to the monitor”
For playback, you are now going via component out to your deck, and from there via composite to your monitor? Try to connect your monitor directly to your Y out cable on your Kona card, and set the video out from Media 100 to Composite&Y/C. This way you should see on your monitor how the output from the system looks. Then we at least know if you have a problem on the way into the system or back out again.
For mastering to DV you can again use the FireWire connection, regardless of the codec of your material on your timeline. So if you e.g. mix Media 100 i codec, ProRes, DV and other codecs on the same timeline you still can output it to DV over FireWire.
-
[Doug Calhoun] “1. I’m working w/component analog and have to disconnect my Yellow channel on the AJA breakout box “out” to digitize or the image jumps all over and loses “sync”.”
Hmmm, what Yellow cable? You have to disconnect Y (Luminance) from the deck input or you are creating a video feedback, which will cause the jumps. This is completely normal and I think it would also have happened with Media 100 i. There is not much you can do about it except e.g. getting a video patchbay, which makes disconnecting inputs easier.
[Doug Calhoun] “The image quality is substandard both in DV acquire and component. I’ve digitized to Media100i, DVCPro50 and DV Codec with miserable results. I was advised to get the AppleProRez422 codec from someone with FinalCut…..anyone have it? I was shocked to hear not to expect the image quality of my old 8.2.3a M100i system due to the fact that the P6000 was a dedicated video board.”
This is simply wrong. The codec of the P6000 board was a hardware device, since CPUs in these days were not fast enough to compress or decompress PAL/NTSC video. It has been reworked in Software, so that clips digitized into Media 100 i codec should look exactly the same, regardless if they are digitized on a P6000 board or an Aja board. If you are seeing issues this is not something related to a codec. Both DV and Media 100 i should look good. How are you monitoring your signal? How are you getting the signal into the system? Compoenent? FireWire? What kind of format (PAL, NTSC)? It sounds like there still is something very fundamentally wrong with your system. You can expect the video quality to be much better than with Media 100 i.
If you bought the system recently you should have free techsupport from Media 100. Try giving them a call, since they are very helpful and they should be able to talk you through your problems. Or post some more details about your setup (cabling for input and output, where you are seeing the problems,…) and I try to get back to you with some answers.
-
[Gary Stone] “I guess the trial version of 12.7 will give me a week or so before it expires. After that, I’ll probably get current with v13. Are you using that yet? Any thoughts? “
Yes, I think you have a week or 14 days. V13.0.2 is great, we´re using the multichannel audio mixing more or less daily. Plus, the-version-formerly-known-as-V14 already has been announced, so if you decide to upgrade I think you should make sure that you get the next release also with your upgrade.
-
[Gary Stone] “I thought all v12 improvements were included with a v12 upgrade”
No. I think V12.5 or maybe V12.7 had a new code which you can get if you are under software maintenance.
[Gary Stone] “Some play a little bit & then stop and tell me I have a bad frame; other files won’t even show a still frame in the subsampler window. “
This sounds like you have installed QuickTime 7.5.5. Make sure that you do not use QuickTime 7.5.5, either upgrade to 7.6 or downgrade to 7.5
-
[Jason Rogerson] “ny news on whether it works with OS X.5.5 with Media100 12.1.3? Or version 12.7 for that matter?”
As Wick said here, V12.7.1 does work with 10.5.6 and QuickTime 7.6
-
[Jason Rogerson] “Any latest news on the pros/cons of Quicktime 7.6 associated with Media 100????”
It does work on OSX 10.5.x with Media 100 V13
-
[Fermin Branger] “Have you changed the CODEC setting in Project Settings yet? “
Or if they do not show up in the Batch Reacquire window at all, click on the “!” button in the middle row. Most likely your clips will show up with a “standard mismatch” warning, which means that e.g. your clips are 16:9 and your hardware is currently set to 4:3, or that your clips are HD and your hardware is set to SD. Correct your hardware settings and your clips should show up.