Jon Kozenko
Forum Replies Created
-
Jon Kozenko
May 13, 2016 at 3:08 pm in reply to: using multiple BCU Image Restoration features on same footageHello Jim,
To start off, quickly, has your footage been DeInterlaced as of yet? I ask because if not, you will very much want to do this first, as everything else will adjust the fields and potentially make DeInterlacing more difficult.
If it is already DeInterlaced, I think going in the order you have above (DV Fixer, UpRez, Optical Stabilizer and Noise Reduction) would be the best way to go. As for your primary question, I would strongly recommend that you either Export/Re-import or PreComp your footage after going through each of these cycles, as both UpRez and Optical Stabilizer work with the source clip rather than a timeline render, and as such working on an unaffected clip would be the way to go for optimal results.
Thanks.
-
Hello Mike,
You mention that you had BCC OFX 9 earlier – I presume that you Uninstalled BCC OFX 9 before installing version 10? One thing I would recommend quickly would be to Close Vegas and delete the ‘13.0’ folder from this location –
C:\Users\[username]\AppData\Local\Sony\Vegas Pro\As for the Damaged TV and Glint, those are OpenGL effects. Do other OpenGL effects, such as Prism and Lens Flare 3D also crash? If so, try some other effects, non-OpenGL, such as Gaussian Blur or Rays Streaky, and see if these operate okay.
Thanks,
Jon
-
Hello Norman,
There is actually a known issue with Media 100 where the video appears darker than the source footage – This is, however, a Playback bug rather than an Import bug, so what you try quickly is, right after Importing, try Exporting again and opening this new Export in Quicktime Player. If it’s the same IRE/Brightness-Contrast as the original file, then it would appear that what you’re seeing is actually the playback bug, in which case the video itself is being accurately imported and processed by Media 100, and any exports you make once your project is done should be correct again.
If the export is showing the clips as being darker than originally, then this would indeed suggest an Import problem, in which case I might recommend possibly trying different codec options when importing.
Thanks,
Jon
-
Jon Kozenko
April 26, 2016 at 5:54 pm in reply to: Old M100 projects compatible with new M100 on newer system?Hello David,
Going from Media 100 13 to Media 100 Suite 2 should work just fine, as the metadata hasn’t really changed and M100 still uses Quicktime to read and write media. The primary things you would want to make sure of are that the Quicktime Components on your old Mac are present in the Quicktime directory in your new iMac, and that the media files have the same Created/Modified dates as they do on the current setup (although this wouldn’t be a problem if the files are already on an external drive).
Thanks,
Jon
-
Hello Sean,
You should be able to do this with FX10, although it would be done so using a sideways approach. With FX10, what you would need is an image (moving or static) of the figure/object that is conducting the wipe, such as a silhouette of a person over Alpha (you can establish the Alpha in FX10). Once you have established the image and the movement across the screen, you would then simply use this as a cover-up for a simple spline-based wipe effect, where the splines are actually creating a removal of V1, showing V2 in its place.
At this point, your Custom Wipe should be complete. You can save this to the Library Browser by going under the File menu and selecting ‘Save Project Copy to Library’, and it will perform a ‘Save As’ function, but pointing toward the ‘BFX10 Keyframe Library’ directory, which is where the Library Browser loads from. The one thing to note is that this media that you used for the wipe (such as a person jumping from side to side) will be seen, by FX10, as a media asset, so this clip/image will need to remain online.
Thanks.
-
Jon Kozenko
March 14, 2016 at 2:16 pm in reply to: Turn object around axis not in the middle of the objectHello Palo,
The most effective way I found would be to do this. First, create the Text track or import the asset into your Graffiti timeline, and then highlight the main track for this asset (rather than a sub-layer such as Face or Transformations).
Inside the Controls window, go to the ‘Pivot’ tab and you will see three locked XX-YY-ZZ Position/Pivot sliders. What you will want to do is Unlock the XX and YY tracks (and possibly the ZZ tracks, if you are going to use them), so that you can manipulate the ‘Pivot X’ and ‘Pivot Y’ sliders without adjusting the Position X and Position Y.
Use the Pivot X and Pivot Y sliders to move the pivot center, represented by a blue crosshair, for this asset, and any form of Tumble/Spin/Rotate for this asset should correspond to this Pivot X/Y point.
Thanks.
-
Hello Andrew,
In Graffiti, you will see a frame at the very end that would not exist, but this should only be a preview frame, and shouldn’t appear once you Apply back to your Host. Have you noticed the problem after Applying back and performing the clip as a loop? One thing you can try would be to move the final Keyframe(s) back one frame to off-set this extra frame.
Hope this helps.
Thanks.
-
Hello Matthew,
In case you did not get my email from Support earlier, if you can reproduce this with a short clip in a test project, I can take a look at the project with this clip and hopefully see what you are seeing, in which case we should be able to find the cause of the problem.
Thank you,
Jon
-
Hello Dorian,
Do you have an example, say something on YouTube or Vimeo, that does show a similar type of look to what you’re looking to recreate? If so, send me an example to support@borisfx.com (not so sure if you should post it on the forum) – Put the email to my attention, and I’ll correspond with a few people here and let you know the best approach.
Thanks,
Jon
-
Hello Alon,
I believe AJA dropped support for the LS/LSe line a while ago, so in that case, you would want to use the last driver (9.0.5), which is located here –
https://www.aja.com/en/support/legacy/kona-lseOne thing I would recommend is going with the regular driver, rather than the “NDD” version.
Thanks.