FORUMS: list search recent posts

Lost My Media Folders

COW Forums : Autodesk Smoke

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Patrick Morrow
Lost My Media Folders
on Aug 6, 2012 at 12:16:44 am

How can I add a new media folder. I made one in my drive and tried to connect to it and Smoke gives me an error on launch. Please help!!!
Patrick Morrow


Return to posts index

Brian Mulligan
Re: Lost My Media Folders
on Aug 6, 2012 at 1:20:26 am

Try this?...
http://wikihelp.autodesk.com/Smoke/enu/2013/Help/z_Release_Notes#trouble

Brian Mulligan
Senior Editor - Autodesk Smoke
WTHR-TV Indianapolis,IN, USA
Twitter: @bkmeditor


Return to posts index

Robert Adam
Re: Lost My Media Folders
on Aug 6, 2012 at 12:31:39 pm

Hi Patrick.

Please let me know if you were able to perform the procedure Brian recommended or if you need my help with that.

Regards,
Robert.

Autodesk M&E Support
http://www.facebook.com/AutodeskMECF


Return to posts index


Patrick Morrow
Re: Lost My Media Folders
on Aug 6, 2012 at 8:22:28 pm

I tried this but smoke will not recognize my new folder no matter what. Please help.
Thanks,
Patrick Morrow


Return to posts index

Robert Adam
Re: Lost My Media Folders
on Aug 7, 2012 at 3:02:48 pm

Hi Patrick.

Please open the Terminal app from the Applications > Utilities folder and type:
cat /usr/discreet/sw/cfg/stone+wire.cfg

Post the output here.

Thanks!
Robert.

Autodesk M&E Support
http://www.facebook.com/AutodeskMECF


Return to posts index

Patrick Morrow
Re: Lost My Media Folders
on Aug 7, 2012 at 5:13:36 pm

Last login: Tue Aug 7 13:11:40 on ttys000
p-mo:~ protouchvideo$
Last login: Tue Aug 7 13:12:47 on ttys000
p-mo:~ protouchvideo$ cat usr discreet sw cfg stone+wire.cfg
cat: usr: No such file or directory
cat: discreet: No such file or directory
cat: sw: No such file or directory
cat: cfg: No such file or directory
cat: stone+wire.cfg: No such file or directory
p-mo:~ protouchvideo$


Return to posts index


Robert Adam
Re: Lost My Media Folders
on Aug 7, 2012 at 5:16:11 pm

Hi Patrick.

Looks like slashes were replaced by spaces when you copied the command into the Terminal.
Please type the command exactly as you see it below:

cat /usr/discreet/sw/cfg/stone+wire.cfg


Regards,
Robert.

Autodesk M&E Support
http://www.facebook.com/AutodeskMECF


Return to posts index

Brian Mulligan
Re: Lost My Media Folders
on Aug 7, 2012 at 5:26:40 pm

You need to type the slashes as well.

cat /usr/discreet/sw/cfg/stone+wire.cfg

Brian Mulligan
Senior Editor - Autodesk Smoke
WTHR-TV Indianapolis,IN, USA
Twitter: @bkmeditor


Return to posts index

Patrick Morrow
Re: Lost My Media Folders
on Aug 7, 2012 at 5:46:10 pm

It now gives me no feedback when I type it in. Should I just reinstall smoke I deleted the original folder instead of adding the hash marks leaving me with my own folder that Smoke will not recognize.
Thanks,
Patrick Morrw


Return to posts index


Robert Adam
Re: Lost My Media Folders
on Aug 7, 2012 at 5:50:33 pm

Hi Patrick.

If the path to your new folder has been correctly entered in the stone+wire.cfg file, Smoke should recognize it.
I'm surprised that the command I gave you returns nothing.

What if you open the Smoke Setup app, go to the Media Storage tab and click "Manual Edit".
Is there anything in the pop-up window that opens? If so, please post the content here.

Thanks!
Robert.

Autodesk M&E Support
http://www.facebook.com/AutodeskMECF


Return to posts index

Patrick Morrow
Re: Lost My Media Folders
on Aug 7, 2012 at 6:52:17 pm

Nothing comes up at all in the window.


Return to posts index

Robert Adam
Re: Lost My Media Folders
on Aug 7, 2012 at 6:58:18 pm

Oh. then the file got deleted somehow.

Here's what should be in that file.
Please paste the following text in that empty window and make sure to change the Path line to the path of your autodesk media storage folder:

Don't forget to press Apply after you enter this text and close the text editor window.

#
# S+W configuration file
#
# Each S+W partition can be independently configured.
#
[Partition7]

Name=AutodeskMediaStorage
Path=/Volumes/Storage/Autodesk Media Storage

# Name of the partition.
#
# Default for partition 0: Name=stonefs
# Default for partitions 1..7: Name=stonefs#
#
#Name=
# If specified, the path denotes that media should be stored in the file path
# specified, as opposed to the Stone. Typical standard fs path will be
# /mnt/<device>/fs<id>/part<id>/ where <device> is the device name, fs<id> is
# the framestore identifier and part<id> is the partition identifier.
#
# Default: Path=
#
#Path=
# A partition can be flagged as shared to allow another station running
# Stone+Wire to read the media directly from the device, instead of going
# through the Stone+Wire server. This is particularly useful for a SAN/NAS
# environment. The *device* mount point must be identical on ALL stations
# that access this partition.
#
# Bandwidth managed partitions should NOT be Shared. This is to enforce that
# their media will always be accessed via the bandwidth aware S+W Server.
# Otherwise, remote hosts will steal your bandwidth by directly accessing
# the files via NFS.
#
# A shared partition does not mean that two separate systems can use the path
# defined above as their media cache. Each system must own and *manage*
# its own media cache, self contained within its own path within the device
# mount point.
#
# Default: Shared=False
#
#Shared=False
# Optionally, if the Shared flag is on, you may specify the list of hosts
# the partition will be shared with. By default, if the Shared flag is on,
# the partition will be shared with all hosts on the Wire network.
# Hosts are specified on one line as the list of their framestore name or id
# separated with space, e.g., SharedWith= station1 station2 123 23
#
# Default: SharedWith=
#
#SharedWith=
# Video Media Pre-Allocation Strategy
#
# By default, video media files are allocated on the fly as they are rendered or
# written. No file pre-allocation is performed when clips are created.
#
# On shared filesystems, or when background IO operations occur, media file
# interleaving can occur. This causes clip fragmentation and reduces IO
# performance.
#
# To circumvent this, a media file pre-allocation strategy can be deployed to
# ensure that the media files exist before being written, at the expense of a
# performance hit at clip allocation.
#
# The available strategies are listed below:
#
# FALLOCATE - The files will be pre-allocated and zero-ed out on the
# allocation. On most file system this operation is as expensive
# as writing the files.
#
# RESERVE - The space on disk necessary for the file will be reserved
# but not written. The apparent size of the frame will remain 0.
# This operation is typically much faster than FALLOCATE but supported
# only on selected filesystems such as XFS.
#
# F_PREALLOCATE - The space on disk necessary for the file will be reserved
# but not written. The apparent size of the frame will remain 0.
# This operation is typically much faster than FALLOCATE but
# supported only on selected filesystems such as HFS/HFS Plus.
#
# NONE - No pre-allocation is done. Space will be allocated when the
# frame is written.
#
# Note: Pre-allocation when using compressed media (such as JPEG) will
# not be performed since it is impossible to know the size of a
# compressed file in advance. The strategy will be ignored in
# these cases.
#
# Default: Preallocation=NONE
#
#Preallocation=NONE
[DefaultFileFormats]


# The following file formats denote the file types to use when creating image
# files for the 5 possible bit depths. Each specified file
# format/compression/quality combination must be valid and support the listed
# bit depth. If not, S+W will not be able to create the image files on the
# application storage.
#
# These settings can also
# be applied to each storage partition by copying the line to a partition
# section listed above; partition settings always override the format settings
# listed below.
#
# Each file format is defined as follows:
#
# <Type>[:[<Compression>][:<Quality Level>]]
#
# <Type> is the format type
#
# <Compression> is the compression algorithm (if available)
# Choices are: None(leave empty),RLE,ZIP,ZIPS,PIZ,PXR24,B44,B44A
#
# <Quality Level> is the compression quality level [0-100] (if available)
# where 0 is the lowest quality / highest compression and 100 is the
# highest quality / lowest compression.
#
# Example:
#
# 8BitIntVideo=DPX
# 8BitIntVideo=TIF:RLE
# 8BitIntVideo=JPG::50
# floatVideo=EXR:ZIPS
# Supported 8 bit formats: DPX,TIF,JPG,SGI,RAW
#
# Default: 8BitIntVideo=DPX
#
#8BitIntVideo=DPX
# Supported 10 bit formats: CIN, DPX, RAW
#
# Default: 10BitIntVideo=DPX
#
#10BitIntVideo=DPX
# Supported 12 bit unpacked formats: DPX, RAW
#
# Default: 12BitIntVideo=DPX
#
#12BitIntVideo=DPX
# Supported 12 bit packed formats: RAW
#
# Default: 12BitPackedIntVideo=RAW
#
#12BitPackedIntVideo=RAW
# Supported float formats: EXR, RAW
#
# Default: floatVideo=RAW
#
#floatVideo=RAW
[MetadataDirectory]


# Metadata Root Directory
#
# The ROOT directory under which all metadata associated with the
# media ( stone or standardfs ) is located.
#
# Warning: This setting does not affect IFF/FS metadata ( project/clip ).
#
# Default: RootPath=/usr/discreet/
#
#RootPath=/usr/discreet/
# A centralized directory path must be unique across all systems to ensure
# metadata integrity. To this end, the framestore ID will be appended to the
# root path (see above) if the path is flagged as centralized (see below).
# This setting is normally used in conjunction with the clip library and
# project central path defined in /user/discreet/cfg/centralPath.cfg.
#
# For example an host having a RootPath of /mnt/nas/data and a framestore id of
# 54 will have a effective Metadata Root Directory of /mnt/nas/data/54/.
#
# Default: Centralized=False
#
#Centralized=False
[StandardFSMediaOptions]


# This option controls whether or not requests to soft-copy (Link) standard FS
# media files should create symbolic links across filesystems if hard-links
# cannot be created. A hard-link can only be created within the SAME
# filesystem.
#
# Default: SymlinkAcrossFilesystems=True
#
# SymlinkAcrossFilesystems=True
[Initialization]


regards,
robert.

Autodesk M&E Support
http://www.facebook.com/AutodeskMECF


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2017 CreativeCOW.net All Rights Reserved
[TOP]