<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.pinnaclesys.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Studio - Feature Requests</title><link>http://forums.pinnaclesys.com/forums/75/ShowForum.aspx</link><description>Share your requests</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20416.1)</generator><item><title>Re: APIs for Studio. Opening Studio architecture</title><link>http://forums.pinnaclesys.com/forums/thread/317946.aspx</link><pubDate>Thu, 25 Jun 2009 21:13:50 GMT</pubDate><guid isPermaLink="false">aa940761-2c49-4a35-95b6-427f0f08353f:317946</guid><dc:creator>palibidamba</dc:creator><slash:comments>0</slash:comments><comments>http://forums.pinnaclesys.com/forums/thread/317946.aspx</comments><wfw:commentRss>http://forums.pinnaclesys.com/forums/commentrss.aspx?SectionID=75&amp;PostID=317946</wfw:commentRss><description>&lt;P&gt;Thanks Bittman, after I'd sent the post, I found this SDK. I'm partially succesful with examples from it. The biggest problem I've encountered so far is that the clip&amp;nbsp;resolution passed to the plugin&amp;nbsp;is always 720x540, even for HD clips(I have Canon HV30). Don't know how to overcome this. The SDK documentation doesn't mention about HD.&lt;/P&gt;
&lt;P&gt;Thanks for the answer&lt;/P&gt;
&lt;P&gt;GK&lt;/P&gt;</description></item><item><title>Re: APIs for Studio. Opening Studio architecture</title><link>http://forums.pinnaclesys.com/forums/thread/317567.aspx</link><pubDate>Wed, 24 Jun 2009 16:42:21 GMT</pubDate><guid isPermaLink="false">aa940761-2c49-4a35-95b6-427f0f08353f:317567</guid><dc:creator>bittmann</dc:creator><slash:comments>0</slash:comments><comments>http://forums.pinnaclesys.com/forums/thread/317567.aspx</comments><wfw:commentRss>http://forums.pinnaclesys.com/forums/commentrss.aspx?SectionID=75&amp;PostID=317567</wfw:commentRss><description>&lt;p&gt;&lt;a href="http://www.pinnaclesys.com/docloaderplain.asp?doclink=/developers/s9developer.html" target="_blank"&gt;Here is the page for the old S9 SDK&lt;/a&gt; (still mostly-applicable to S10 and later) for RTFx and VST plugins.&lt;/p&gt;&lt;p&gt;Don't have any idea about transitions, but does work for effects.&lt;/p&gt;&lt;p&gt;If you have an effect that you can make/use/develop for VirtualDub,&amp;nbsp; then &lt;a href="http://www.hlinke.de/Home_e/VDub2RTFX_Plugin/vdub2rtfx_plugin.html" target="_blank"&gt;Harold Linke's Virtualdub Filter plugin&lt;/a&gt; might be good enough.&lt;/p&gt;&lt;p&gt;But like I said:&amp;nbsp; No idea if that'd work for transitions.&lt;/p&gt;&lt;p&gt;BittMann &lt;br&gt;&lt;/p&gt;</description></item><item><title>Re: APIs for Studio. Opening Studio architecture</title><link>http://forums.pinnaclesys.com/forums/thread/317520.aspx</link><pubDate>Wed, 24 Jun 2009 15:00:09 GMT</pubDate><guid isPermaLink="false">aa940761-2c49-4a35-95b6-427f0f08353f:317520</guid><dc:creator>Tribal</dc:creator><slash:comments>0</slash:comments><comments>http://forums.pinnaclesys.com/forums/thread/317520.aspx</comments><wfw:commentRss>http://forums.pinnaclesys.com/forums/commentrss.aspx?SectionID=75&amp;PostID=317520</wfw:commentRss><description>Although this is a great idea, it just won't happen, at least any time soon. Being a commercial piece of software, programmers would actually have to buy the rights to do any kind of modifications, otherwise it would propose a paradox to the terms of service that the user agrees to adhere to during installation. In the License Agreement, it states that user is not permitted to reverse engineer the software, although this probably only applies to people that would re-sell the software. Nonetheless, your suggestion is a great idea, and I totally agree with it. Over the years I've seen numerous pieces of software go open source (or somewhat restricted open source), and it has always been beneficial. But, there are a list of problems when it comes to releasing your source code (or an API). So, for now, I agree with your suggestion, but I don't think anything like this will happen any time soon, especially with speculations that Studio will merge with Liquid.</description></item><item><title>APIs for Studio. Opening Studio architecture</title><link>http://forums.pinnaclesys.com/forums/thread/313740.aspx</link><pubDate>Sun, 07 Jun 2009 19:05:35 GMT</pubDate><guid isPermaLink="false">aa940761-2c49-4a35-95b6-427f0f08353f:313740</guid><dc:creator>palibidamba</dc:creator><slash:comments>0</slash:comments><comments>http://forums.pinnaclesys.com/forums/thread/313740.aspx</comments><wfw:commentRss>http://forums.pinnaclesys.com/forums/commentrss.aspx?SectionID=75&amp;PostID=313740</wfw:commentRss><description>&lt;P&gt;Pinnacle, please provide&amp;nbsp;APIs for Studio! Probably only software engineers know what I'm asking for, so let me explain:&lt;/P&gt;
&lt;P&gt;It is very technical feature request, but a crucial one for a software package to be successful. Application Programmer Interface (API)&amp;nbsp;is specification for developers to write their own extensions (aka: plugins) for the product.&amp;nbsp;Making them public by publishing&amp;nbsp;relevant specs is crucial for the success.&amp;nbsp;Studio seems to be a good candidate for opening the architecture, because it is&amp;nbsp;a relatively simple framework for clips and scenes manipulation with all more sophisticated tasks already delegated to plugins, like transitions or filters. Why not disclose how to write these plugins, so millions of developers could have a chance to enhance your product.&lt;/P&gt;
&lt;P&gt;BTW: What is&amp;nbsp;your current&amp;nbsp;policy to get these specs? I'm very interested in writing&amp;nbsp;a plugin for a&amp;nbsp;transition (between scenes).&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR&gt;GK&lt;/P&gt;</description></item></channel></rss>