View Full Version : CineForm Neo 5.0.7 build 267 live


David Newman
August 3rd, 2010, 10:56 PM
The latest version has now been released and available for download through the CineForm web site. CineForm Product Downloads (http://estore.cineform.com/downloads.aspx)

Build 5.0.7.267, released 3-August-2010
Enhanced -- now using fewer threads if there are more than two decoder running in a process.
Enhanced -- the auto 3D muxing option with FirstLight.
Enhanced -- 3D editing features in CS5 with far great speed through the OpenGL control panel's
"Fast 3D" option.
Enhanced -- restored Vegas 9 smart rendering (Sony, you moved the goal post again.)
Fixed -- Parallax 3D filter for support all 3D mode (some were broken in 5.0.6.)
Fixed -- converting QTPro trimmed Canon DSLR MOVs in HDLink.
Fixed -- a transcoding crash, more typical of large source files.
Fixed -- a conflict between MainConcept components and Windows Media Player /
DirectShow playback.

+ many minor tweaks.

Leo Baker
August 4th, 2010, 07:41 AM
Hello David,

I have tried a few times and just now today to get ther download link of neo 4k via the download page as an update, but no email is being received?

Also what was the Mainconcept fix, what was the problem previous that needed to be fixed?

Thanks,

Leo

David Newman
August 4th, 2010, 08:53 AM
We license a range of Mainconcept filters, but until 5.0.6 we left them unregistered (not used by the system as defaults). We did register them in 5.0.6 as a shortcut to new features, unfortunately one the MC demuxer broke some AVI functionality (very weird.) So 5.0.7 we no longer register the MC components, but have had the need features by programmatically evoking the needed filters.

We will give the license server a kick this morning -- it was working last night.

David Newman
August 4th, 2010, 01:14 PM
Leo,

email should be going out now. If you didn't get it, please re-request the update.

Leo Baker
August 4th, 2010, 07:38 PM
Hello David,

Thank you I have got the email download links now. Did you manage to find out about the clips when converted into nested sequences and the cross dissolve or transitionbeing added that it crashed.

Thanks,

Leo

Roy Feldman
August 5th, 2010, 07:04 AM
Uninstalled old> installed latest 267> log stopped at "could not find common files". Uninstalled new went back to Build 265: works fine.
Submitted report

David Newman
August 5th, 2010, 09:28 AM
Hello David,

Thank you I have got the email download links now. Did you manage to find out about the clips when converted into nested sequences and the cross dissolve or transitionbeing added that it crashed.

Thanks,

Leo

It is crashing in the Adobe part of the SDK, so I forwarded the information to Adobe. Hopely they can point out what we are going wrong or get a fix for us. This is not in Premiere itself, but in the stub code we use to hook to the SDK, so turn around time should be faster.

Roy Feldman
August 6th, 2010, 09:37 AM
got this from support:
ok. i checked with an engineer and i'm told that build 267 installs the encoder in the wrong place. so stick with 265 until we get that fixed.

David Newman
August 6th, 2010, 01:02 PM
That is little out of context. We had some issue, with the installation order, now fixed, the 267 build downloads where updated and are fine.

Stephen Armour
August 6th, 2010, 04:01 PM
Please see my other post on First Light's white balance picker (color picker) tool NOT WORKING in either of the last two versions.

David Newman
August 6th, 2010, 04:03 PM
Turn off OpenGL, and it will work again. We know aout this one.

Stephen Armour
August 6th, 2010, 04:04 PM
Gotcha, thanks.

Roy Feldman
August 6th, 2010, 06:34 PM
That is little out of context. We had some issue, with the installation order, now fixed, the 267 build downloads where updated and are fine.

My "out of context" is a direct cut and paste from CF support but based on your reassurance I requested download again, installed it, and found it still does not work... guess I should have believed Mr. Segraves who wrote my open trouble report status when it says "work in progress". I hope I am updated on that progress

Leo Baker
August 7th, 2010, 04:20 PM
Hello David,

I put on the latest build

http://www.cineform.com/downloads/Neo4Kv507b267-100803.zip

When I go to the Cineform C at the bottom right of my task bar, I click on the About tab and get this error.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Convert.ToInt32(String value)
at CineForm.AboutBox.refreshStateOfUpdateButton()
at CineForm.SystemTrayApplication.launchAboutBox()
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
CineFormActiveMetadataStatusViewer
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/leo/AppData/Roaming/Microsoft/Windows/Start%20Menu/Programs/Startup/CineFormActiveMetadataStatusViewer.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Robert Gadsdon
August 10th, 2010, 05:45 AM
Updated to NeoHD 507b267, and when attempting to convert/split a single HD 50i MPEG2 (M2T) file from my Canon HV30 to Cineform AVI clips, the Log showed:
..............
Capture device is in camera mode.
Converting C:\xxxxxxxxxxxx.
Building conversion graph.
Using MPEG Audio Decoder 3.

and then NeoHD gives the following error (displayed twice):

"You are attempting to encode a stereo/3D format for which this system is not licensed. Please contact support@Cineform.com."

The same type of file from that camera had worked OK with previous versions of NeoHD, and reverting to 506b265 'fixed' the problem.

System is an Intel Core/Duo running WinXP SP2.

Update:
Tried reinstalling 507 after deinstalling - still getting same error, but also:
"Returning from encode sample, error: 55. Please contact support......."
Then HDLink hangs..

Jake Segraves
August 10th, 2010, 01:06 PM
My "out of context" is a direct cut and paste from CF support but based on your reassurance I requested download again, installed it, and found it still does not work... guess I should have believed Mr. Segraves who wrote my open trouble report status when it says "work in progress". I hope I am updated on that progress

this was an issue in Neo Scene build 267 only. i believe that's what david means when he says this is out of context. its not relevant to the other products. I replied to your ticket, by the way.

Roy Feldman
August 11th, 2010, 09:24 PM
Mr. Segraves from CF support spent a lot of time with me and resolved the issue I was having, it seems that my particular problem was unique to my computer. Support stuck with it and resolved my issues in a fast and professional way that should be the standard for tech support.
Thank you CF

Robert Kennedy
August 13th, 2010, 12:32 AM
Nice update. I am now able to manipulate the 3D file in First Light while Premiere is open without it crashing. I also can playback full res 3D 1080p on an external monitor in Premiere without dropping frames (pretty sure.. but see below).

Is there a way to determine if Premiere is dropping frames (in the internal window or external display)? There seems to be no default indication this is occurring unlike other NLEs (vegas displays the actual playback rate, FCP stops playback and issues a warning.. etc...) I would rather not have to keep a sharp eye to figure whether it's the NLE or the footage with motion issues.

The Fast 3D option seems to have greatly increased the ability of Premiere to playback Cineform 3D files full-screen on an external monitor. Unfortunately it seems to force the internal window to display over/under. I have tried changing the 3D display type but it always displays over/under. Am I missing something or is that part and parcel of having full screen 3D on an external monitor?

Finally, I have not been able to get OpenGL 3D working with nVidia 3D Vision via First Light yet. Works fine in Premiere, but neither internal window, Full Screen Primary nor Secondary External Monitor will work. I tried the same trick it took to get Premiere to work but all this did was corrupt my 3D Vision/OpenGL (even after reboot) requiring me to do a full recovery of the Win7 installation. It would be really handy to get this feature working with 3D vision to make 3D adjustments without having to float between Premiere and FL to see the adjustments full screen. Should I contact tech support on this?

Thank you,
Robert

David Newman
August 13th, 2010, 11:29 AM
Dropping frame indicator is not planned, we don't have that in 2D either, never have as there are to situations that generate false positives. For HDSDI play out to tape we used the AJA frame buffer to give an real indicator, after all you particular need to know when laying back to tape. We internal know we skip decoding of the frame (that is visually obvious), but we don't know in OpenGL presents the frame 1/60th later than it should (I guessing that can happen.)

We will like make the internal monitor preview left only in a future undate, but currently there are a few places where under-over pops-up when it shouldn't.

This is weird, as it is the same code in FirstLight as Premiere to drive OpenGL 3D. I expect these new NVidia 3D Drivers are still settling in, and this will be fixed by an NVidia driver update. It is working with our FX3800 to our Samsung 3D 120Hz page/flip monitor, but it toook a few driver updates to get it work correctly.

Leo Baker
August 22nd, 2010, 12:51 PM
Hello David,

Using the latest build and still getting this error see my previous post when I click the about Cineform on the C CIneform icon on the taskbar.

http://www.dvinfo.net/forum/cineform-software-showcase/482867-cineform-neo-5-0-7-build-267-live.html#post1556603

I am on Windows 7 pro 64bit.

Thanks,

Leo