Interestingly enough, John, the issue was present regardless of whether
IN/OUT points were marked and whether either/both of the check-box
settings to which you referred were enabled/disabled.
Our vendor duplicated the issue in-house with their Nitris BOB, then
tried it with their DX BOB. The issue is not present with DX hardware
attached. They're suggesting it's a bug with the Nitris Bob.
Best,
--Jess--
--- In Avid-L2@yahoogroups.com, "johnrobmoore" <bigfish@...> wrote:
>
> There is a setting in the export to use marks and active tracks.
Unchecking the use marks will eliminate the need to mark in and out on
the export frame or I just usually clear all marks and it works for me.
Perhaps I'm missing something or there was a bug. I'm on SNDX 4.0.5 and
haven't had the problem you originally described.
>
> --- In Avid-L2@yahoogroups.com, "Jesstator" jesstator@ wrote:
> >
> > Or . . .
> >
> > 1. Park on the frame.
> > 2. Mark an IN and an OUT
> > 3. Render ***ALL EFFECTS*** IN-to-OUT
> > 4. Export to desired still frame.
> >
> > 5. Facepalm yourself.
> >
> > (grinning)
> >
> >
> > --Jesse--
> >
> > --- In Avid-L2@yahoogroups.com, Benjamin Hershleder <Ben@> wrote:
> > >
> > >
> > >
> > > Hi Jesse,
> > > A quick look at my own Settings folder shows no TTState file
either.
> > > It's a file that was associated with the Title Tool. Maybe it's
not a
> > file that's not created any longer (?).
> > > I was just guessing that since an import somehow involves the
Title
> > Tool, that possibly an export did as well.
> > > Forget I even mentioned it. It was a bit of a stab in the dark.
> > >
> > > The usual suspects are:
> > > -MCState file
> > > -User Settings
> > > -Media Databases (trash them as a last resort).
> > >
> > > Other things that come to mind are making sure there's room on the
> > drive you're writing to, and making sure you have permission to
write to
> > that drive. Yet another one is making sure the media is not LongGOP
-- I
> > don't think you can export LongGOP without first transcoding or
doing a
> > video mixdown to another codec.
> > >
> > > The gang here on the L probably have other suggestions & opinions.
> > That's all I can think of at the moment . . . sorry.
> > >
> > > HTH,
> > >
> > > B
> > >
> > >
> > > Benjamin Hershleder
> > > http://ContactBen.com
> > > http://Hershleder.com
> > >
> > > Wear It In Post!
> > > Fun T-shirts, mousepads, mugs & more
> > > for Post Production Professionals
> > > http://www.WearItInPost.com
> > >
> > > On Nov 10, 2011, at 2:52 PM, Jesstator wrote:
> > >
> > > > I don't recall ever dealing with that file, Benjamin. I don't
see it
> > in
> > > > my user settings folder and a search using the name "TTState"
yields
> > > > nothing. Can you direct me to the right file path?
> > > >
> > > > I'll delete both MCState and TTState and try again. Failing that
> > I'll
> > > > try creating new user settings.
> > > >
> > > > Thanks,
> > > >
> > > > --Jesse--
> > > >
> > > > --- In Avid-L2@yahoogroups.com, Benjamin Hershleder Ben@ wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Trash the TTState settings too and also try creating new user
> > > > settings.
> > > > >
> > > > >
> > > > > Benjamin Hershleder
> > > > > http://ContactBen.com
> > > > > http://Hershleder.com
> > > > >
> > > > > Wear It In Post!
> > > > > Fun T-shirts, mousepads, mugs & more
> > > > > for Post Production Professionals
> > > > > http://www.WearItInPost.com
> > > > >
> > > > > On Nov 10, 2011, at 1:20 PM, Jesstator wrote:
> > > > >
> > > > > > Thanks, John.
> > > > > >
> > > > > > I tried deleting MCstate and the issue remains. What other
> > > > > > troubleshooting items fall under the "usual stuff" category
for
> > an
> > > > issue
> > > > > > such as this?
> > > > > >
> > > > > > --- In Avid-L2@yahoogroups.com, John Beck jb30343@ wrote:
> > > > > > >
> > > > > > > Jesse, I vaguely remember a little problem exporting
stills
> > around
> > > > the
> > > > > > > time I would have been on 4.0.x. I don't remember the
details
> > but
> > > > I'm
> > > > > > > sure it was a quick and easy fix. Have you tried the usual
> > stuff:
> > > > > > > settings, MCstate...? --J.B.
> > > > > > >
> > > > > > > Jesstator wrote:
> > > > > > > > I've not been able to find anything related to this
issue in
> > the
> > > > > > > > Symphony forum at the Avid Community, only what's listed
at
> > this
> > > > > > link:
> > > > > > > >
> > > > > >
> > > >
> >
http://community.avid.com/search/SearchResults.aspx?q=export+still+image\
\
> > \
> > > > \
> > > > > > \
> > > > > > > > &s=56
> > > > > > > >
> > > > > > > >
> > > > > > > > --Jesse--
> > > > > > > >
> > > > > > > >
> > > > > > > > --- In Avid-L2@yahoogroups.com, "Jesstator"jesstator@
wrote:
> > > > > > > >
> > > > > > > >> Hi, folks.
> > > > > > > >>
> > > > > > > >> Both Symphony workstations in my office are unable to
> > export
> > > > still
> > > > > > > >> images (or image sequences) of any kind to any local or
> > > > networked
> > > > > > > >> location. Either system fails to generate a progress
bar.
> > > > Typing
> > > > > > > >> [CTRL] + [period] snaps either system out of its hang.
The
> > > > > > workaround
> > > > > > > >> is to export a one-frame QuickTime movie then use
QuickTime
> > Pro
> > > > to
> > > > > > > >> convert that movie to the requested image format (I'd
use
> > > > > > Photoshop,
> > > > > > > >>
> > > > > > > > but
> > > > > > > >
> > > > > > > >> don't have it available if you can believe that).
> > > > > > > >>
> > > > > > > >> Is this a known issue? Has it been discussed here or at
the
> > > > Avid
> > > > > > > >> Forums?
> > > > > > > >>
> > > > > > > >> Here are the specs for each system:
> > > > > > > >> Symphony Nitris v 4.0.5 PC / Nitris / Unity
> > > > > > > >> HP XW 9300 (AMD)
> > > > > > > >> Win XP_SP-3
> > > > > > > >> AMD Opteron 270 @ 1.99 GHz
> > > > > > > >> 2.61 Gb RAM
> > > > > > > >>
> > > > > > > >> Thanks in advance,
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
No comments:
Post a Comment