Beta 5.1.2.271 should address many issues

[David Newman]

This version mainly adds the missing libraries that made many features in 5.1.1 not work correctly, so the release notes are short. Learned lesson, this version will be label beta. Do not install if you are in the middle of a project.

Added: support for the 3D video mode of the Fujifilm FinePix W1/W3 into the FirstLight 3D Muxing tool.
Fixed: NLE Sync functionality in FirstLight
Fixed: adding the missing Microsoft and Intel redistribution libraries to make it all work better.

Neo3D http://cineform.com/downloads/Neo3Dv512b271-100902.zip
Neo4K http://cineform.com/downloads/Neo4Kv512b271-100902.zip
NeoHD http://cineform.com/downloads/NeoHDv512b271-100902.zip
NeoScene http://cineform.com/downloads/NeoSce...271-100902.zip

If something doesn't work that did work in 5.1.0, that might be another library we missed. Please report any such findings to support, and we will turn the fix around quickly.

[Ariel Gilboa]

Originally Posted by David Newman

This version mainly adds the missing libraries that made many features in 5.1.1 not work correctly, so the release notes are short. Learned lesson, this version will be label beta. Do not install if you are in the middle of a project.

Well, if one has this problem :

Originally Posted by David Newman

Fixed: NLE Sync functionality in FirstLight

...then he's kinda compelled to update, despite being "in the middle of a project".... no ? :-)

Thanks !

BTW

What is the latest version BEFORE you moved to the new development environment ?

[David Newman]

5.1.0 was the last release under the older dev. tools. The new tools are much better.

If you are compelled to get new features and bug fixes mid-project, there is little risk as can always go back to an older version.

[David Newman]

Anyone care to comment if 5.1.2 is working better for them?

[Leo Baker]

Hello David,

NLE Sync is working fine for me. I am getting the occassional stack hash error message from Firstlight which then closes when either cycling through my clips in a list in Firstlight or about to ctrl+v paste a look I created for a clip.

I am using the NEO4k on Windows 7 64bit.

Leo

[David Newman]

If you have a repeatable proceedure for that error, please send it to support. Otherwise it seems we have improved things.

[Julian Frost]

With this release, PPro CS3 successfully loads the presets...

But it doesn't successfully load the CF AVI files!

One of two things happens:

1) If I open an existing project containing CF AVI files, *some* of the AVI files are listed as Offline. If I try to link them to the original file, it says they are not of the same type. If I close the project without saving it, and reopen it... different files will be effected.

2) If I create a new project (using a Prospect 1920x1080 30F preset), containing CF HD AVI files, *some* will load properly, and will show in the project window as Video files with audio. Others, will show as Video files with no audio! All of the files were converted from MOV to CF AVI at the same time, using the same version of HD Link. If I preview a Video without audio file by selecting it, then clicking the play button in the Project window, there is no audio. If I play it in Windows Media Player, there is audio.

When I go back to 5.1.0.268, everything loads properly.

[David Newman]

Julian,

As I'm CS3 finding is working fine now, we have to determine what is making is random on your system. Bugs normally don't behave that why. More likely there are two components, one that works and one that doesn't Premiere is using both (the strange part.) Uninstall 268, the search in C:\Program Files (x86)\Adobe for any files with this pattern *CFHD*.prm and delete any that remain. Reinstall 271, see if it is now working.

[Stephen Armour]

David, call me stubborn for beta-ing a system in the middle of a complex project, but I was blown away by the changes in this latest beta on one CS3 system we had going! I loaded it in spite of it being in the middle of a project :) just because....I had a sneaking feeling you'd babied this one through...after getting your fingers burned on the last one...

I repeat...I was totally blown away! It was the smoothest playback experience I have ever had on that old system that has a very large and complex project on it at the moment . I did not have time to fully test things, but if nothing serious shows, this "beta" is very different, very fast and very smooth. What did you guys do that made such a difference? I even changed to full resolution playback and it was smooth as silk, almost like I was using our CS5 workstation! Even scrolling back and forth and using the Bella wheel on the keyboard of that system was smooth as I have ever seen it run.

Whatever you did different...KEEP DOING IT! I retract the grouching on the last beta! All is much better so far.

One comment on Julian Frost's post: One CS3 system of ours did exactly the same thing as his, but when I closed that project without saving and then reopened it, things were totally normal and quite smooth. I haven't checked the other to see if the behavior was the same.

[Julian Frost]

I uninstalled 268, searched for *CFHD*.prm in the Adobe folder (and sub-folders) and found the following files:

c:\Program Files\Adobe\Adobe Encore CS3\Plug-ins\en_US\im-CFHD_File_Import.prm
c:\Program Files\Adobe\Adobe Encore CS3\Plug-ins\en_US\Backup\im-CFHD_File_Import.prm

I deleted the files, and installed 271.

Same problem: Random AVI files are loaded as if they do not contain audio.

Attached are some screen shots. The first one is an existing project, as opened the first time. You will see there are 2 AVI files on the timeline which were not imported correctly.

I closed the project, and opened it again. As you can see in the second timeline, there are 6 AVI files which were not imported correctly!

I included a shot of the project window so you can see how PPro CS3 sees these files.

Again, this is the same project, opened once, closed, and then immediately opened again.

This random incorrect importing happens on every project I open.

[Stephen Armour]

I am sorry to report that I was gushy too soon....

I went back to that same system, as I couldn't believe what I was seeing. It's true, but alas...all is not well in beta-land. I decided to push it with a little Premiere prob that has plagued us in the past. We had a whole track of black video below all the video in that project, due to the red prob. When I re-activated the black video and then re-rendered the few sections that had transitions to black, it crashed Premiere repeatedly after a minute or two of rendering.

I will reload the 5.1.0 again and see if this behavior is still present.

Sigh.

[Stephen Armour]

Same prob in 5.1.0, so it could be something else. Might have nothing to do with the beta at a all. Will try to work through this tomorrow.

[Stephen Armour]

It looked suspiciously like some old CS3/CF mem probs of the past, so I killed all non-essential processes, to free the maximum physical memory, and sure enough, it rendered no problem.

It came very close to using every bit of free memory on that old system with only 4 GB RAM and Win x64, but managed to keep it's head above the water to the end. Looks like purely an old CS3 memory prob that even Win 7 x64 couldn't pull through without help. Jack that mem up to 8 GB and it'll probably be fine.

I wil try the same thing with the newest beta and if it's the same story (which I'm sure it probably is), I'll reinstate my gushing for that new beta...

Just a quick update...it's late. The newest beta apparently uses quite a bit more free memory, but I'll try to verify that later tomorrow. If so, that would explain the CS3 crash on that system. Is that why the playback is smoother?

[Randy Johnson]

I downloaded the 5.1 demo and I cant even get it to run. I dont feel like going back through the reg process to see if 5.12 runs.

[David Newman]

Randy,

There is no registration process, just download directly from the links in the first post of this thread.