Recent Posts

Pages: 1 ... 8 9 [10]
91
Announcements / Qube! 6.8-0 Release Update - Functionality
« Last post by pipelinescott on November 09, 2015, 02:40:58 AM »
Qube! 6.8-0 Release Update About Functionality
There was a recent post to the board with an update regarding the timing of the 6.8-0 release:
http://pipelinefx.com/forum/index.php?topic=1681.0

That timing has not changed, so that update is still valid.

This post is regarding a change in the functionality we are planning to release with 6.8-0.

Due to how VRED is written, we are unable to complete the support for VRED distributed rendering. We are speaking with Autodesk currently - they have acknowledged the issue, would like to correct it, and will be keeping us up to date on the fix. We hope to finish the work already started on distributed rendering for VRED, so maybe we'll see this in the 6.9-0 release, pending the Autodesk update.

Two other changes related to VRED - we have already added support for the VRED Sequencer into 6.8-0. This has been left out of the previous list, so we're making sure to add it now. Also, we'll be updating the VRED submission UI to move away from the HTML widget based submission to the latest protocol released by Autodesk.

If there are any other updates, we will let you know. The updated list of functionality is below.

Thanks!

**********************************
Qube! Release Version 6.8.0
**********************************

----------------------------
New Features
----------------------------   
   BETA release of job submission in ArtistView for major packages     
   BETA release of centralized preferences for job submission   
   JSON ingest support in ArtistView     
   Support for the VRED Sequencer
   Updated VRED submission UI - not HTML based 

----------------------------     
Performance Improvements
----------------------------         
   Optimizations to WranglerView originally found in 6.7-1c

----------------------------         
New Job Type Support
----------------------------     
   Toon Boom's Harmony job type

----------------------------         
Updated Platform Support
----------------------------         
   Windows 8   
   Windows 10
   CentOS 6.7
   CentOS 7.0
   CentOS 7.1
   Modo 9
   Houdini 14
   VRED on Linux
   VRED on MacOS
92
Announcements / Qube! 6.8-0 Release Update
« Last post by pipelinescott on November 03, 2015, 09:26:33 PM »
Qube! 6.8-0 Release Update


Hello Everyone,

The release of Qube! 6.8-0 has faced a few delays over the last couple of months for a variety of reasons. Not only were we affected by attendance to events like SIGGRAPH, but the tasks related to moving functionality out of WranglerView and into ArtistView has been taking longer than originally thought. It is coming along and is looking very nice, though. We think the work put into this effort to retire WranglerView will provide a much better user experience across the board.

We are targeting to release 6.8-0 by the end of this month - November. Please keep your eyes out for our announcements about the actual release day.

As a reminder, the features in 6.8-0 are seen below.

Thanks!

**********************************
Qube! Release Version 6.8.0
**********************************


----------------------------
New Features
----------------------------   
  •    BETA release of job submission in ArtistView for major packages      
  •    BETA release of centralized preferences for job submission   
  •    JSON ingest support in ArtistView      
  •    Distributed rendering with VRED   
----------------------------      
Performance Improvements
----------------------------         
   
  • Optimizations to WranglerView originally found in 6.7-1c
----------------------------         
New Job Type Support
----------------------------      
   
  • Toon Boom's Harmony job type
----------------------------         
Updated Platform Support
----------------------------         
  •    Windows 8   
  •    Windows 10
  •    CentOS 6.7
  •    CentOS 7.0
  •    CentOS 7.1
  •    Modo 9
  •    Houdini 14
  •    VRED on Linux
  •    VRED on MacOS
93
General / The job that wouldn't die!
« Last post by freelanceit on October 29, 2015, 11:44:28 AM »
Hi all,

We're running 6.4.0.b and I've got a job that's sitting rendering on one of our Linux farm nodes and I can't get rid of it.
Some of the instances failed, some have been killed but some remain running. In the job properties it shows as Status: Dying.
I've tried killing the job (it ignores this), I've stopped and restarted the worker, I've rebooted the box and strangely I can't see any process running on the box that might be the job?

Any ideas?

Adam.
94
Announcements / Qube! 6.7-2a WranglerView patch release is available
« Last post by jburk on October 28, 2015, 10:09:16 PM »
A 6.7-2a patch release is now available for the Qube 6.7-x WranglerView.  This is a recommended patch release for all customers running any version of Qube v6.7, and can be installed directly on top of any 6.7 version of Qube.

For those using the Qube Installer utility, the 6.7-2 manifest file has been updated.  If you are using version 2.1-0 or later of the QubeInstaller installer utility, it, will auto-detect if a manifest has a newer version and offer to download it.

Or you can download the patched version directly at: http://repo.pipelinefx.com/downloads/pub/qubegui/current/

Full release notes are available on our documentation site: http://docs.pipelinefx.com/display/QUBE/WranglerView+6.7-2+Release+Notes

-------------------------------------------------------------------------------
6.7-2a FEATURES AND FIXES
-------------------------------------------------------------------------------

This patch was only made available on Windows.

6.7-2a was primarily released to address a build-related error that prevented
WranglerView from starting on Windows Server 2008 SP2 and Windows 10.
It also incorporates changesmade after the release of 6.7-2 that were originally
intended for 6.7-3.

=========================
    New features
=========================

==== CL 14607 ====
@NEW: add additional messages to regex_errors for nuke cmdline and loadOnce jobs (CL 14597)


=========================
    Fixes
=========================

==== CL 14799 ====
@FIX: Regex and wildcards broken in performance charts job name filter

==== CL 14725 ====
@FIX: upper limit on processors reservations set to 48; limit removed entirely

==== CL 14722 ====
@FIX: "Object of type function found where a Number, Array, or Property is
needed" when submitting from inside AfterEffects CC 2015

==== CL 14720 ====
@FIX:Include output path regex for Blender jobs so Blender jobs properly report
their output image(s).

==== CL 14711 ====
@FIX: job->interrupt not interrupting shortest-instance, not shortest-running work

==== CL 14607 ====
@FIX: ERROR: unable to successfully execute command "nuke.scriptOpen"  - don't
double-quote the path to the Nuke script (CL 14599)


=========================
    Changes in behavior
=========================

==== CL 14607 ====
@CHANGE: starting up a pythonChildHandler to manage a "LoadOnce" application
does not implicitly start the application, must now call the handler's start(),
and pass server port number to the subprocess args. (CL 14598)


95
General / Re: Jobs completing but some frames not done
« Last post by jburk on October 20, 2015, 04:51:22 PM »
Nuke will happily render to thin air without an error, going through all the motions and then writing the frame to the bit bucket.  This often happens when the destination folder for the rendered frame is either not accessible, prohibits writing due to permissions, or is full.

Permissions can be hard to track down; some workers may be running under a different proxy_account than others, so you may want to check and see if the failed frames are all from the same worker or workers, and if those workers are able to write earlier or later frames.

If a worker can write frames for a while, then fail to write, then be able to write again all within the same job, the usual cause for that is the file server is running a Windows desktop O/S version, which only supports a limited number of concurrent connections and will silently drop a connection to pick up another one.   The client on the other end has no clue that the network connection to the filesystem is dead.  The clue to this is when the number of dropped frames goes up as the number of running instances for all jobs on the farm goes up.
96
General / Re: Jobs completing but some frames not done
« Last post by freelanceit on October 20, 2015, 09:32:40 AM »
Are you eligible for support? 

No, our support is long gone. I'm kind of building a case for an upgrade so was sort of hoping someone would just say "Oh, that's fixed in patch 6.X" so we'd have another reason to upgrade.  8)

Quote
Are the unrendered frames on disk but the wrong size or black, or are they missing altogether?   Another thing to test is if this never happens when you render a Qube job with only a single job instance running; if the number of missing frames goes up the more concurrent job instances are running, it's likely that your file server is dropping connections.

The frames just didn't render.
We have about 20 operational nodes on the farm but I'm not sure if all of them were being used for the job, probably more like 10.
97
General / Re: Jobs completing but some frames not done
« Last post by jburk on October 19, 2015, 06:02:35 PM »
Are you eligible for support?  If so, I'll ask you to open a case on our helpdesk and send the job log directories, add the URL for this forum thread as well.

Are the unrendered frames on disk but the wrong size or black, or are they missing altogether?   Another thing to test is if this never happens when you render a Qube job with only a single job instance running; if the number of missing frames goes up the more concurrent job instances are running, it's likely that your file server is dropping connections.

Think of Qube as Fedex (especially for simple-to-start jobs like Nuke cmdllne-based renders): once Qube gets the job to the worker and gets it started, it's out of our hands.  Fedex doesn't know what's in the packages they deliver, nor do they know what you do with the contents.
98
General / Re: Jobs completing but some frames not done
« Last post by freelanceit on October 19, 2015, 04:05:00 PM »
There didn't seem to be any errors in the logs. The user rendered the job locally out of Nuke and it was fine.
99
General / Re: Jobs completing but some frames not done
« Last post by jburk on October 19, 2015, 03:04:04 PM »
No, the issue isn't with Qube, this would be happening regardless of the Qube version.  What's most likely occurring is that the Nuke command to render the frame is returning an exit code of 0, indicating "no errors".

Is there anything in the job's stdout or stderr logs that gives a clue as to why a particular frame is not being output?
100
General / Jobs completing but some frames not done
« Last post by freelanceit on October 19, 2015, 01:42:03 PM »
We're using an ancient version of Qube (6.4.0b) and sometimes when jobs are submitted from Nuke 9 v 04 the job says it's completed but a few of the frames haven't rendered. Is this a known error in old versions of Qube?

Thanks,
Adam.
Pages: 1 ... 8 9 [10]