Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas and Cineform Issues.

  • Vegas and Cineform Issues.

    Posted by Israel Prophitt on September 10, 2009 at 12:26 am

    This is nuts! I am at my wit’s end! I hope someone can help. I will provide as much info as possible.

    OS: Vista64 Business Ed.
    NLE: Sony Vegas 8.0 and 8.1(64bit)
    IMPORT: Cineform NeoScene Codec v1.3.6 build 121
    CAM: Sony HDR-FX1
    CPU: 2x AMD Opteron 2218s
    RAM 16 GB
    VIDEO DRIVE: 2x SATA drives in RAID 0

    I have been having issues with Vegas 8.0 not rendering from cineform avi files. Vegas locks up and crashes. It would start rendering, but part way through the render (at random points) it would lock up. OS would be stable and fine. I would have to end Vegas task however.

    I was using an older version of the cineform codec at this time, so I decided to see if there was a newer version (a 64bit compatable version) so i could try it inside Vegas 8.1 (64 bit). I have always had trouble with 8.1 and cineform files. Great news … an updated … comptable codec from cineform … 64 bit!

    Uninstalled old neoscene, uninstalled Vegas 8.0 and 8.1. Re-installed new cineform software and both versions of Vegas … no problems.

    I create a new project in v 8.1 and save it. I import media (avi files), no problem. When it is in list view (project media tab) no problems. When I switch to thumbnail view vegas starts to create thumbnails, it creates 16 thumbnails and crashes. I tried different combinations of video clips, but the same thing #17 thumbnail doesn’t show, and Vegas crashes!

    I have had this issue with Vegas 8.1 (64 bit) for a while. I have just used 8.0 (32 bit) instead. I even tried importing new clips using the latest cineform codec directly from camera, but still #17 kills everything. Odd!

    If i keep the project media tab in detail view, nothing happens. I can drop video files onto the timeline and nothing bad … so far.

    So i just kept the project media in detail view and edited. I set the project to render while I was at work. My wife called and said that windows gave an error message that said It was running low on memory (16 GB). Vegas had ate 16 GB of memory, all of my screens went blank, explorer crashed. I was able to launch task manager and start sysInternals process explorer … peak memory usage was at 99.97%! I had to re-start.

    Help.

    John Rofrano replied 16 years, 7 months ago 2 Members · 7 Replies
  • 7 Replies
  • Israel Prophitt

    September 10, 2009 at 1:00 am

    ********** UPDATE ****************
    I just uninstalled NeoSceneV136b121b-090812 and installed NeoSceneV135b120-090723 as suggested in these forums. I get the same problem. : ( NO VICTORY!

  • Israel Prophitt

    September 10, 2009 at 1:58 am

    ************ UPDATE ***************

    I can import 16 files all day long … no problems. I tried to import 16 at at time … several times … different clips from different projects I am working on. Great. Try to import 17 … BAD!

    In this test project, i imported several sets of 16 without trouble. I saved the project … I re-started vegas. loaded the project. switched to thumbnail view … and on the 17th thumbnail … CRASH!

  • John Rofrano

    September 10, 2009 at 9:50 am

    I was able to reproduce your problem on Vegas Pro 8.1 as well. My number wasn’t 17 but at some point, Vegas could not display thumbnails and just stopped responding. I could not reproduce this error with 113 CineForm files in Vegas Pro 8.0 or Vegas Pro 9.0 32 & 64-bit. I seems to only be a problem with the rather buggy 8.1 release (which I wouldn’t recommend using for any production work). If you want to work in 64-bit you really should upgrade to Vegas Pro 9.0.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Israel Prophitt

    September 25, 2009 at 5:46 am

    Mr Rofrano, thank you for a response. I’m glad the issue isn’t mine alone. My reply is delayed because of an email being classified as junk. I just found it. : )

    The move to v9 (64) wouldn’t come cheap. It is my goal eventually though(I really like the additional headroom for RAM previews since I have 16GB RAM).

    I need to know is it WORTHWHILE to upgrade from v8 (32) to v9 (32/64)? I wont upgrade unless there is a significant feature that will help my workflow. I used v6 for a LONG time. I only upgraded to v8 because of the 64 bit option(8.1). 8.1 doesn’t work. STEPPED ON! LIED TO! SWINDLED! BAMBOOZLED!!

    What version do you use for the main portion of your work?

    Israel

  • John Rofrano

    September 25, 2009 at 10:45 pm

    > I need to know is it WORTHWHILE to upgrade from v8 (32) to v9 (32/64)?

    IMHO, it is just because of the enhancements in handling HD formats like AVCHD.

    > I wont upgrade unless there is a significant feature that will help my workflow.

    So… is having your CineForm files actually work “significant” enough for you? 😉

    > I used v6 for a LONG time. I only upgraded to v8 because of the 64 bit option(8.1). 8.1 doesn’t work. STEPPED ON! LIED TO! SWINDLED! BAMBOOZLED!!

    Vegas Pro 8.1 was a “technology preview”. If you read the Sony forums it should have been clear that it was buggy. CineForm didn’t even work in 8.1 until 9.0 came out! You have to do your homework before purchasing.

    > What version do you use for the main portion of your work?

    I use the 32-bit version of Vegas Pro 9.0 on Vista 64 for all of my work.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Israel Prophitt

    September 26, 2009 at 2:36 am

    Thank you sir for your reply. Working with Cineform is a significant reason, but since Cineform works with 8.0(32 bit), v9 isn’t needed as much as I had thought. As far as 8.1 is concerned, you’re right, I should have done more research. I’m glad you are here to help with my v9 homework.

    BTW I tried installing Vegas 9 trial the other night, and it would get part way through the installation, and back peddle through uninstalling itself. Perhaps this was a sign that I should just stick to v8 (32 bit). I’m more productive when I don’t worry about “versions and bits.” 😉

    Thanks again Mr Rofrano for your time. Your information, and choice of NLE(32 bit) helps me a great deal to put some issues to rest.

  • John Rofrano

    September 26, 2009 at 4:50 am

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy