Stefan Scheidegger
Forum Replies Created
-
I didn’t find out much about the bugs in the Sony Vegas OFX interface. But I think I know by now what are the three instances good for:
instance_1 creates the plug-in and the user interface
instance_2 will render the frames
instance_3 to x are more renderers to accelerate the render process. ImageEffectDescriptor::setRenderThreadSafety() can be used to change that behavior. If I set for example setRenderThreadSafety(OFX::eRenderUnsafe), then only instance_2 will be created to render.If someone knows more details about this, feel free to share.
-
Stefan Scheidegger
July 2, 2012 at 3:50 pm in reply to: SD 50i to HD 50p upconversion and deinterlacingI think I found the solution for this problem in Sony Vegas:
1. Open a Vegas project with HD settings
2. Import the SD footage
3. Apply the de-interlacing filter not as a track or event effect, but as a media effect. That way apparently it will work with the source media resolution and successfully de-interlace my media.
4. Apply all the other effects as usual as track or event effects and profit from HD resolution.
5. Render to HDSome important points in my case:
– I applied BCC deinterlace in Boris RED as a media effect. But Boris RED recognized my HD project settings and used those. I had to manually change the Boris RED project settings to SD for the de-interlacer to work!
– My SD footage is quite blurry. Boris uprez didn’t make a big difference compared to just importing the SD footage to Vegas. But applying BCC unsharpmask in an HD project instead of an SD project made a huge difference!Best,
Stefan -
Stefan Scheidegger
June 29, 2012 at 7:07 am in reply to: Two Problems with BCC deinterlace / RED deinterlace in Sony Vegas 11.0Peter,
did you hear anything about these issues? Were you able to reproduce them? Is there a bugfix release for BCC scheduled?
Thanks a lot for your help,
Stefan
-
Stefan Scheidegger
May 25, 2012 at 6:52 am in reply to: Two Problems with BCC deinterlace / RED deinterlace in Sony Vegas 11.0Perfect, thanks a lot! Looking forward to hearing from you.
Stefan
-
Stefan Scheidegger
February 20, 2012 at 10:23 am in reply to: RED motion stabilizer and long footageThanks a lot for the hints! I think I’d prefer to keep working on the whole one hour clips. I have about 40 of them to stabilize and the result is good. As I said, it just needs time.
I was zooming 400% to 800%. But with 1 hour of tracking points (about 90’000) it’s still not possible to select the desired point. I wish there were some keyboard commands for moving the current tracking point (e.g. arrow keys) and for also selecting the neighbours of the selected tracking point (comparable to text editing: shift – arrow keys). (Yes, I’m one of those who do everything with keyboard short cuts!)
About locking points I didn’t know. I’ll definitely give it a try. Thanks for the hint!
Best,
Stefan -
Hi Peter,
Thanks a lot for the information. Looking forward to it!
Stefan
-
For the moment I found a workaround for this issue: When I want to do motion tracking in Boris RED as a Vegas Plug-in, I close the Vegas video preview window and I hide the timeline. Like that I face fewer problems with RED changing to the green V1 footage.
Is there an estimated release date for the RED update solving these issues?
Best,
Stefan -
Thanks a lot, Bob.
Maybe I should rephrase: I’m looking for the least bad U-Matic machine.
So far I use an old VO5850 with an external TBC to play back. But I hope to get maybe a few less drop-outs or tracking problems when using a later model. (Unfortunately I didn’t find any NLE filters that automatically treat those problems of old analog material.)
Now I’m undecided whether to go for a BVU-900 with TBC and noise reduction or for a VO9800. Well maintained is a prerequisite anyway.
-
Stefan Scheidegger
July 29, 2010 at 3:32 pm in reply to: Boris RED/FX – Sony Vegas crash: Memory leak?I have just run another test: I used RED Engine (without Sony Vegas) to apply a filter (BCC dust/scratch removal) and render to an uncompressed .mov file. The behaviour is the same: The memory used by the RED Engine process keeps growing while rendering until it crashes (after rendering about 15 minutes of footage, the process used more than 2 GB RAM). There was no error message, the application just closed! Even when I successfully render a short clip, the memory is not freed afterwards!
So this is actually not a problem of the combination of Vegas and RED but of RED itself. I’m sure I’m doing something wrong here! Any suggestions?
Thanks a lot!