I had been strugling with this just recently.  Found a solution posted here on page 2.  Looks like it should be resolved in NeoScene 5.3.  Here’s the solution copied below:

We have found this playback freeze and are working on the best solution now (we have one that works, working on an cleaner solution for this next release — 5.0.3 is waiting for it.)

This works. Replace
C:\Program Files\Adobe\Adobe Premiere Pro CS5\Plug-ins\Common\CineForm\CFHD_AVI_Importer.prm
and
C:\Program Files\Adobe\Common\Plug-ins\CS5\MediaCore\CineForm\CFHD_AVI_Importer.prm

with the contents of:
http://www.cineform.com/downloads/CF…porterV503.zip

1920x1080 2.35 letterbox

Click on the image above to get the png.

I searched all over the interweb for this but couldn’t find it so I decided to just create it myself.  If you’re trying to letterbox a 1920×1080 video so that it ends up being the typical cinematic format of 2.35:1 (actually 2.39:1) then you can use this PNG image as your last layer of the composite.   If you’re confused why it’s 2.39 vs 2.35 but still called 2.35 read here.

To break it down, the image size 1920×1080 exactly with black bars on top and bottom with each bar being 138 pixels high.  The result is a transparent area of 1920×803 or in other words 2.39:1 where the rest of the composite layers can be seen.

Some people prefer to just crop in their NLE but I found my approach to be much more useful for  a few reasons:

1. You can implement the letterboxing across the entire project without having to set crop settings on each clip or track
2. The letterboxing is just a composite so any of the tracks or clips beneath it can be repositioned vertically without changing the letterboxing.  This is tough to do when you use cropping becuase you’re always readjusting the crop size to however you’re adjusting the vertical positioning.
3. I’m not absolutely sure about this, but it seems as though preview playbacks and rendering are a bit faster compared to cropping. 

I’m mainly using this technique on Adobe Premiere.  For those of you using Sony Vegas you should know your Pan/Crop settings can already handle this for you, but still you have to set that on every track but my method should alleviate that work.   And of course if you want a different aspect ratio, just adjust the image or make  new one.

If you’re programmatically adding items into your document library or list you can use this piece of code to retrieve a folder structure based on the current Date Time.  It will created a nested folder structure so that you will never have more than 2000 items in any folder.    For example a new list item would be stored in the following structure:

Year – 2010
   Month – 4
      Day – 20
          Hour – 14

        private SPFolder getCurrentDateFolder(string listName)
        {
            SPFolder currentDateFolder = null;
            DateTime now = DateTime.Now;

            SPSecurity.RunWithElevatedPrivileges(delegate()
            {
                using (SPSite site = new SPSite(SPContext.Current.Site.ID))
                {
                    using (SPWeb web = site.OpenWeb(SPContext.Current.Web.ID))
                    {
                        SPList list = web.Lists[listName];

                        SPFolder yearFolder = null;
                        SPFolder monthFolder = null;
                        SPFolder dayFolder = null;
                        SPFolder hourFolder = null;

                        string year = "Year - " + now.Year.ToString();

                        if (doesFolderExistInSubFolders(list.RootFolder, year))
                        {
                            yearFolder = list.RootFolder.SubFolders[year];
                        }
                        else
                        {
                            web.AllowUnsafeUpdates = true;
                            SPListItem newFolder = list.Items.Add("", SPFileSystemObjectType.Folder, year);
                            newFolder.Update();
                            list.Update();
                            yearFolder = newFolder.Folder;

                        }

                        string month = "Month - " + now.Month.ToString();

                        if (doesFolderExistInSubFolders(yearFolder, month))
                        {
                            monthFolder = yearFolder.SubFolders[month];
                        }
                        else
                        {
                            web.AllowUnsafeUpdates = true;
                            SPListItem newFolder = list.Items.Add(yearFolder.ServerRelativeUrl, SPFileSystemObjectType.Folder, month);
                            newFolder.Update();
                            list.Update();
                            monthFolder = newFolder.Folder;
                        }

                        string day = "Day - " + now.Day.ToString();

                        if (doesFolderExistInSubFolders(monthFolder, day))
                        {
                            dayFolder = monthFolder.SubFolders[day];
                        }
                        else
                        {
                            web.AllowUnsafeUpdates = true;
                            SPListItem newFolder = list.Items.Add(monthFolder.ServerRelativeUrl, SPFileSystemObjectType.Folder, day);
                            newFolder.Update();
                            list.Update();
                            dayFolder = newFolder.Folder;
                        }

                        string hour = "Hour - " + now.Hour.ToString();

                        if (doesFolderExistInSubFolders(dayFolder, hour))
                        {
                            hourFolder = dayFolder.SubFolders[hour];
                        }
                        else
                        {
                            web.AllowUnsafeUpdates = true;
                            SPListItem newFolder = list.Items.Add(dayFolder.ServerRelativeUrl, SPFileSystemObjectType.Folder, hour);
                            newFolder.Update();
                            list.Update();
                            hourFolder = newFolder.Folder;
                        }

                        currentDateFolder = hourFolder;
                    }
                }
            });

            return currentDateFolder;
        }

SPListItem li = list.Items[0];
SPContext.Current.Web.AllowUnsafeUpdates = true;
li.BreakRoleInheritance(false);
SPContext.Current.Web.AllowUnsafeUpdates = true;
li.Update();

I originally found the solution from this post here.  http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=648182

I’m using Vegas 9.0c 32 bit on Windows 7 64-bit and have noticed this issue when using Magic Bullet Looks 1.2.  If you monitor the memory in task manager you’ll see it grows and will never come back down.   I have a machine with 8GB of RAM so the solution presented in the post  is to change the switch in the exe to allow it to utilize more than 2GB of RAM.  This has worked perfectly for me. 

Here’s a run down of what you need to do:

1. Get CFF Module from http://www.ntcore.com
2. Open the exe file for vegas.  This should be like “vegas90.exe” or “vegas80.exe”.
3. Click on FILE HEADER under NT HEADER on the left side.
4. On the right there is a table and on the very last cell to the right on the bottom click on “CLICK HERE”
5. Check the option that says “app can handle > than 2gig address space”
6. Save the file as a different file ie vegas90_new.exe.  
7. Run the new exe.

 Now if what you’re rendering is so massive its going to grow beyond your RAM then you’re still out of luck and will have to render in pieces but at least you can get longer clips to render.

http://support.microsoft.com/kb/972535

<?php include (ABSPATH . '/wp-content/plugins/wp-featured-content-slider/content-slider.php'); ?>

http://wordpress.org/extend/plugins/wp-featured-content-slider/installation/

The problem in our situation was that we previously had set the property to be able to search the forest which in our case was called contoso.local.  SharePoint was not returning users from the trusted domain in people picker but  what was more confusing was that people picker would return users from the trusted domain who had been previously added.  So initially, we couldn’t diagnose that it wasn’t returning all users but thought it was only having a problem with a few users.  In the end, we found the problem to be that contoso.local was no longer being recognized as a forest but rather just as a domain.

Why was it being now recognized as a domain and not a forest anymore?  No clue.  If you have any ideas please chime in because that is still a mystery to me.   I’ve tripple checked and our forest is still the same name. I did notice this issue happened after the April cumulative update although I’m not sure it is related.

So our property value for peoplepicker-searchadforest had to change from:

stsadm -o setproperty -url http://contoso.com -pn peoplepicker-searchadforests -pv “forest:contoso.local“,contoso\account,*****;”domain:contoso.local”,contoso\account,****

 to the correct value:

 stsadm -o setproperty -url http://contoso.com -pn peoplepicker-searchadforests -pv “domain:contoso.local“,contoso\account,*****;”domain:contoso.local”,contoso\account,***

 It took us 2 support technicians and an escalation then finally after 2 weeks the issue was fixed with Microsoft support.  We spent a lot of time making test sites with multiple configurations but had completely missed this one detail of trying domain instead of forest.   Hope this saves someone else some time!

Here’s some points I’ve come accross that may help decide when to use either solution:

When to use Active Directory

• Users are already part of AD
• Accounts must be centrally managed by IT
• Accounts need to follow certain policies maintained by IT (password expiration,  password strength)
• Users absolutely need SharePoint features only available from NTLM ie. windows explorer view for lists
• No need for forms auth and need true Windows auth integration
• Ideal for company intranets where the users of SharePoint are all from AD

When to use ASP.NET membership

• For using ASP.NET login controls (http://msdn.microsoft.com/en-us/library/ms178329.aspx)  right out of the box.  Saves incredible amount of work!
• There is a need for an account creation process, i.e. registration where the user will be granted with certain rights upon completing the registration.  
• Need for more self service features for accounts such as “Forget Password” with a challenge and response, and a “Change Password” feature.  These come out of the box.
• If the site is primary accesssed by users outside of the organization, AD will be convoluted with users that otherwise do not use internal resources.   Using ASP.NET membership segregates these users which also provide better protection for assets that could be accessed by internal AD users.
• SharePoint developer/admin can support user accounts all from with the SharePoint server rather than an IT resource with rights to AD.  This is helpful where there are large bureaucracies for IT that need to be bypassed.
• Ideal solution for partners, extranets, and public facing sites where the users do not need to be in AD. 

The original post I found related to this was http://www.slightlyrational.com/it/sharepoint/extending50sitelimit.

<siteMap…>
<providers>
        <add name=”GlobalNavSiteMapProvider” description=”CMS provider for Global navigation” type=”Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” NavigationType=”Global” EncodeOutput=”true” DynamicChildLimit=”0″ />
        <add name=”CombinedNavSiteMapProvider” description=”CMS provider for Combined navigation” type=”Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” NavigationType=”Combined” EncodeOutput=”true” DynamicChildLimit=”0″ />
        <add name=”CurrentNavSiteMapProvider” description=”CMS provider for Current navigation” type=”Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” NavigationType=”Current” EncodeOutput=”true” DynamicChildLimit=”0″ />
        <add name=”CurrentNavSiteMapProviderNoEncode” description=”CMS provider for Current navigation, no encoding of output” type=”Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” NavigationType=”Current” EncodeOutput=”false” DynamicChildLimit=”0″ />
</providers>
</siteMap>