Txt pro file manager
I have bought this mobile phone for a week but I didn’t know this mobile phone is different from other sony ericsson mobile phones and does not have file manager. I read the solutions about this problem but I have a suggestion if company make a soft ware update that it has file manager it will be better. thanks
Solved!
Go to Solution.
this isn't a smartphone so you can't quite add apps, check playnow
Don't forget to mark the Correct Answers & Helpful Answers
unrelated topic, if you have some time please check this thread
http://talk.sonymobile.com/thread/44888
"I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994)
Similar Messages
-
I suggest to solve this problem with new version of software update but it answered it cant be .ok if it cant be solve with update please guide me to solve this problem.mobile phone with out file manager doesn’t have any mean and its very hard to work with that.i most said that I check other applications ( jar apps) but every one had a problem with mobile phone.please help me….thanks
I will pass on your suggestion to concerned developers.
- Community Manager Sony Xperia Support Forum
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page. -
Final Cut Pro X File Management Issues
I have several issues
1. Does anyone know if it is possible to import from camera to the standard Mac file system? I can't see a way to avoid importing media in the FCP library and I definitely DON"T want any of my media files in the FCP library.
2. Also I know I can copy the media files out of FCP back into the file system but I am not sure how to delete the FCP copy and re-point everything to the media I have stored in a proper file structure on a specific media disk.
3. It doesn't seem to be possible to have FCP default new libraries to a media drive - it only wants to create them on the boot drive and the library has to be moved manually. Am I missing something?
4. Backup is an issue now - it looks like a change to any component within a library will trigger a backup of the whole library - it certainly does with the backup software I am using, and who knows what Time Machine does with FCP libraries... (but Time Machine DOES appear to delete files without notice when it runs out of space, so it is not suitable for any environment where permanent data retention is an issue - so beware...)
ps: don't EVER use the "move to library" function. If it crashes you won't get a reason, you can't undo or recover, and the originals may be deleted even though the media never made it to the other library. This is not good...Hi Tom: It was "Move Event to Library" that crashed, deleting the media from the originating library but not copying it to the new library.
I lot of my issues are down to lack of familiarity with the new interface after migrating from the old Final Cut; manuals which are incomplete or in error; courseware created in earlier versions of Pro X and which have not been updated, and what I regard as counter-intuituive defaults and assumptions by the Apple development team. I spend a lot of time searching for answers: For instance I spent at least an hour searching in the manual and on the net for a way to extract or move the media from an FCP library. I came up with nothing. It would never have occurred to me to search for the term "consolidate".
Another thing that caused me an issue was that I copied a library from one drive to the other to create a backup before I started trying to regularise the media locations in the original library. I changed the name of the backed up library in file manager. When I open it, FCP still uses the old name - hence a library which is opened on one disk and appears to point to data on another. In fact I hadn't noticed that there were two libraries of the same name open at the same time in FCP - the apparently duplicated library was in fact the backup library on the other disk which was renamed in file manager but not in FCP.
In iTunes and Aperture, which both use this bundled library approach, you can only open one library at a time. FCP is different - and I have no problem with this, but any user familiar with the other products would assume, as I did, that FCP worked the same way. That it does not gives rise to the possibility of confusion.
FCP is a very complex piece of software. That means it is impossible to make it easy for a first timer to understand - an experienced Final Cut user has to unlearn as much as he or she has to learn - and all this places much greater reliance on the manuals. The writers of the manuals need to try and put themselves in the heads of their users and make sure that their TOC, Index and terminology corresponds to the thinking of the user - not the new terms they have created for the new version (e.g.: "consolidate media" - which means extract media from the library and move it into the file system, but who would know?)
In an environment where the file sizes are enormous; a library may contain several hundred clips and audio tracks organised in various events and projects; FCP can crash and "disappear" media; the manual is hard to search and the software behaves in an unexpected manner (library names in FCP do not necessarily correspond to the actual name of the library on disk and multiple copies of a library can all be open at the same time, with the same name) this all creates a great deal of stress. One mistake and a great deal of work can be lost irretrievably.
However, with your advice, I have consolidated the media files from my largest library and confirmed that the library holds only the metadata now. However, the new file organisation is unusable, so I will now need to change the file names and reorganise them into subfolders that make sense to me - I guess I will find out if this breaks FCP's links. At the same time I have to figure out which files in the original file structure correspond to the newly extracted files so that I only have a single set.
My big mistake was to copy the files into the library in the first place. This is the default, and also recommended on the Lynda courseware (which was created on an earlier version of FCP). Since most of my existing files were imported in the old version of FCP prior to the upgrade (so already on disk), this meant creating duplicates of all files initially. However, all the newer files are only in the libraries and not in the file system - reconciling this now is tricky. Since I retrieve SD cards on my notebook in the field and then copy to my Mac Pro, some of the new files have ended up in the file system and not in the library. I am yet to find out whether FCP will automatically pick up new files added directly to the file system, or whether they have to be "imported" through FCP before FCP can see them.
The overhead of all this duplication is enormous and the inconsistencies tricky, and it is only now that I understand better how FCP Pro X works (and that it can lose stuff) that I now realise I have to undo all of this and move the media back into file manager and out of the libraries.
If you have to transition to a new, and radically different, version in the middle of a project you really need to understand all the implications. I did not. And now that I do, it is difficult, stressful and time consuming to sort out.
If I were able to go back and give myself some advice it would be to ignore the defaults, create logical and sensible file structures for all your media, keep all media out of the libraries and use the file structure to force FCP to organise your clips in a logical manner so that you don't then have to go through and laboriously assign keywords to organise them in FCP.
I don't know if the way I work is very different to other film-makers. This is a doco - typically around 5% of what is shot will make it into the final program, and I double that because I use three cameras a lot of the time. That's about 40 hours of HD plus WAV audio files. Some of the clips are an hour in length and impossible to synch between the cameras until they are chopped up and new combined clips created - this is very laborious! An hour of HDD is about 400GB (more if I shoot raw) - so there will be about 2TB of data associated with this doco by the time I finish shooting. In an interview I record a separate audio track - and I generally use this as the master track since it is the only clip which can be guaranteed to run for the full duration. But FCP Pro X assumes that the master track will be a video file and it is not possible to add an audio file to the timeline first. I found a workaround - but, again, I am fighting FCP and the developer's preconceived ideas about how people might use this software.
Apart from the doco itself various other projects use the same media - but I don't want these projects cluttering up the doco library which is already cluttered enough. If the media is in the library I have to copy clips to other libraries for these other projects, leading to more duplication. Its another reason to move the media out of the library and another indication that FCP was not really designed for large projects.
Even just within a single library, file management is unsuited to the volume of files I use. For reasons known only to themselves, the FCP developers have used a very specific view of the file organisation - and its not the view I use in file manager (which is the column view). That makes using the file management in FCP very cumbersome - but its essential if you have a large number of clips. My smallest library takes 30 minutes to copy from one Thunderbolt2 disk to another, so creating a backup before changing things in a library is not a trivial event.
Also, the keyword process is clumsy and, I think, poorly conceived but it is the only way to organise clips if you haven't created a file structure prior to import. I haven't yet figured out how to erase the keywords I used for one event so that I can reassign the keywords for use in another event. But I assume that means that if I go back to the first event, I will have to put all the keywords back in - or ignore the shortcut keys and type them manually (which is necessary for much of the time anyway because there are only 9 - a good indication of the size of the projects for which this software was designed). Also, oddly, there is no shortcut key that I can find for turning on/off the keyword window - which is annoying because it takes up a lot of screen real estate). It is issues like this that leave the impression that FCP has been conceived as a kind of iMovie + and that it just isn't architected for real-world proper film making. It can be bent to that, and it has some nice features, but I find myself fighting it a lot of the time.
After all of this I can't find a reason why Apple would create library "files" anyway. What advantage does this provide over the standard file system? What are the implications for backups? (If you are backing up incrementally only the components within a library then how can you be sure any version of the actual library file is current? And if not, then is any minor change to any file in the library going to trigger a full backup of everything - (in this case 1TB+)? And how does this differ between various backup options? Again, assuming FCP users are mostly making home movies, with small file sizes and using Time Machine then a library concept might make sense. But that is iMovie thinking. And that Apple have implemented a "move to library" function without any transactional integrity (no deletions should be made until the successful copy is confirmed) further underpins the non-professional positioning of this product.
I hope it improves with age...
But thanks again for your help - it was timely and very much appreciated.
Stephen -
File Manager Pro app --- WIFI won't connect to PC
The File Manager Pro (free) app won't let me connect to my home network URL. I am trying to download files from PC to iPad.
In the iPad app (File Manager Pro), it recognizes the Router with the unique iPad address 192.168.1.13 and gives the instruction to go to your PC (in my home on the same router) and in your browser, type in http://192.168.1.13 to link the iPad with my PC. I am trying to do so in order to copy files from my PC to my iPad without a cable or without using iTunes. File Manager refers to this as a WIFI link using the address of your local router (in my home).
I really like all the features of File Manager Pro and believe that the above is how I am able to exchange files. -
File Manager Pro.....Advice from other users please
I uploaded much of my music collection to Skydrive in anticipation of iPad ownership.
I planned to hold a small selection on the device and refresh/replace albums from Skydrive whilst on my travels using Hotel WiFi.
I have discovered that even using the "Skydrive App" one can only stream such media content, not download it.
Enter "File Manager Pro".
...This promised to be the answer to a maiden's prayer.
...alas, no.
Though I can now download music using the App, it remains imprisoned within the application, only being playable on the "One Shot" rudimentary in-built player.
Does anyone know of a way to transfer these music files to the iPad library where I could then access them from the iPad player?
Alternatively, is there some other way of downloading music from Skydrive directly to the iPad music library?> Any other user please advice how do you transfer files
to your Server
> through
> FTP from dreamweaver?
All I've ever used is DW.
> i am doing, like Save to Remote Server, just saves the
page, not image.
> what do you do , if you can advice, instead of not
telling to to visit a
> link
> or help file or such, Just a Quick tip, shall help.
If you are seeing Save to Remote Server, then your site is
not properly
defined. It should be defined as an FTP site, NOT as an FTP
and RDS Server
site (unless you REALLY know what you are doing).
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"owaisrauf" <[email protected]> wrote in
message
news:ekg1ff$lql$[email protected]..
> Any other user please advice how do you transfer files
to your Server
> through
> FTP from dreamweaver?
> i am doing, like Save to Remote Server, just saves the
page, not image.
> what do you do , if you can advice, instead of not
telling to to visit a
> link
> or help file or such, Just a Quick tip, shall help.
> -
Need help with Premiere Pro 6 media/file management!
I've been an Avid editor for 20+ years and understand media management in that world. I've recently learned FCP 7 and understand media management in that world. But for the life of me I cannot wrap my head around how Premiere Pro 6 manages media. I am looking for a very straightforward explanation, chart, anything to make sense of this. Thanks in advance for helping an old dog learn new tricks!
More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
Exactly what is INSIDE the video you are editing?
Codec & Format information, with 2 links inside for you to read http://forums.adobe.com/thread/1270588
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download -
Premiere Pro Project Manager does NOT include After Effects files.
Warning: Premiere Pro "Project Manager" does NOT include the After Effects 'dynamic linked composition' files associated with the project when "Collect File and Copy to New Location" resulting in the incomplete and loss of all dynamic linked compositions in the new project destination ( folder or disc drive ) .. I know this also includes Photoshop dynamic links and assume includes Audition audio files as well.
Here's the best way: Personal Responsibility.
Put all of your project files in one file. Stop asking PPro to do it for you. It's simple. This is a no-brainer. If you create a linked comp, create it in the same file as your PPro project and files. When you send it to Encore, create the Encore project in the same folder. Works all the time, every time. When you're sure that you're finished with the project for the forseeable future, move the entire folder off your workstation into storage. Do I move a copy of each asset (video clip, image, audio, etc.) into this folder before I import it to my AE or PPro project? Yes I do. Is it overly time-consuming? Not really. I can fly on my machine. Does it beat not being able to open a project later. Oh yes. Yes it does. I'd say I did 50 projects last year this way. When I occasionally had to move a project folder back to the workstation, I had no problems. Everything worked as it did before I off-loaded it. That's because I take personal responsibility for my projects. It's imporatnat that theyt work, especially if I end up having to hand it off to a third party down the road.
BTW, my workstation is RAID 0. If you are using anything less, you need to upgrade. What I'm trying to tell you is that my system works very well. I have not always done things the right way. I have had my share of frustration. The point is that I learned. Now I'm passing that on to you. I use CS5 on an HP Z800 with a measely 12 gigs of ram and a single i7 quad core and the aforementioned RAID 0 configuration and a hacked Nvidia GTS 450. It works quite well. I'm sure I would do even better with another i7, 12 more gigs of ram and a Quadro 4000, but this is what they give me to use.
Additionally, I'm using CS5 at home on a MUCH older HP xw8200 dual dual Xeons, 12 gigs of ram and software-only MPE. Guess what? It works quite well. -
New owner of a Macbook Pro, can't delete or move to trash a txt.rtf file
Hi new member here with my first Apple product. I recently tried the Stickies app to write a note and save it in my documents , as i am new i didn't know what format to save in from the choices anyway i have ended up with a txt.rtf file in "All my files" and i cant delete it or move it to trash , i get a message about an original Alias is missing , then error -43.
Is there anything you can reccommendHello,
This may not be directly related, but I just (March 2015) ran into a problem I have not seen before and we move LOTS of PDF files across all kinds of networks and network locations.
We have seen a related behavior.
If the PDF worked BEFORE the MOVE, COPY, or RENAME, it should work AFTER the move, copy, or rename.
However, we have seen where if AFTER the MOVE that you cannot OPEN the PDF with Adobe (or move or copy the file to a new location) that perhaps your NEW PDF File name and DATA PATH structure is not well under 255 characters.
For some reason either ADOBE or WINDOWS (XP for sure) has a problem with PDF File name and DATA PATH structures that near, equal to or are great than 255 characters.
Make sure AFTER (ideally BEFORE) you MOVE, COPY, or RENAME PDF Files, that your resulting PDF File name and DATA PATH structure is under 255 characters, otheriwse you will may not be able to MOVE COPY RENAME or OPEN the PDF's in the NEW location until after your PDF File Name and DATA PATH structure is under 255 characters in total length.
PDFUser1941 -
Have done a lot of reading to get prepared to convert to Aperture 3 and have this question regarding setting up my library type.
I'm not a professional -just a heavy user hobbyist.
It appears that the major factors in using reference style is to backup the images with Time Capsule and always do moves or deletes from within the Aperture application.
If my architecture matters here's what I have that may be involved in photo management and editing:
iMac (latest 27" high power version with lots of memory)
Internal 2TB HD where the library is stored
External (FireWire) 2TB HD where the images are stored
External (FireWire) 6TB HD backup drive
In the future an iPad for remote work on images (when/if available) and a Mac laptop (for same remote use)
I see major downside issues to letting the library manage my files - such as inaccessibility (or awkward accessibility) to the images for other programs, and performance issues when the library gets large (thousands of images or 100+ gb in size)
The chief complaints I've seen regarding using a reference mode is the broken link issues created if file management is done outside of Aperture (adds, deletes, moves of files) and the inability to use the Vault function for backup.
One feature that I imagine I'd like to have is maximum integration with Final Cut Pro X and that's one area I haven't seen much on and would be interested to hear about if that integration is affected with the choice of managed vs referenced library types. (I like to produce film clips that are combinations of pics and video and want to be set up so that is done in the easiest fashion when working in FCP X)
I'm sure I've not seen all sides of this issue and would like to see some discussion around this question.
Thanks to everyone contributing!
CraigGoody, Goody, you hit a few of my favorite subjects! Herewith some comments, with the usual caveats - true to the best of my knowledge and experience, others may have different results, YMMV, and I could be wrong.
I run Aperture on two machines:
-- 2007 Mac Pro with 2x2.66 GHz Xeon, 21 GB of RAM, a 5770 GPU, and multiple HD. I have about 11,000 images, taking up 150 GB. (Many are 100 MB TIFF, scanned slides)
-- 2006 Mac Book Pro with 1 2.0 GHz Core Duo, 2 GB of RAM and a 240 GB SSD.
Two very different machines.
-- Aperture Libraries are all the same - Managed or Referenced. If Managed, then the Master image files are inside the Package, if Referenced, they are outside, and you can have any combination you want. Managed is easier, but Referenced is not hard if you are the least bit careful.
-- While the sheer size of an Aperture Library is not a big issue, the location on disk of the different components can have a tremendous impact on performance.
-- Solid State Drives (SSD) read and write faster than regular Hard Disks (HD) and, what is more important, empty HD read and write much faster than full HD.
-- Aperture speed requires a combination of RAM, CPU, graphics processing unit (GPU) speed, and disk speed. The more RAM you have, the less paging you will see. With enough RAM, the next bottle neck is CPU (speed and cores) and GPU speed. But even then you will still have to fetch an image (longer if you pull the full resolution Master, read and rewrite the Version file, and update the Preview and Thumbs.
So what works?
-- RAM, RAM, and more RAM. 4 GB will work, but you will page a bit. 8 GB is much faster. On my old MacPro the sweet spot was about 16 GB of RAM.
-- Keep your Library on your fastest (usually internal) drive. Keep that disk as unloaded as possible. How do you keep it unloaded? Either buy BIG, 1 TB+ or move your Masters off onto another disk. The good news here is that as Master files are written only once and never rewritten, speed of this disk, as opposed to the disk that holds the Library, is not important. There is a one second pause as the Master is read into memory and, if you have enough RAM, that is it - the Master will never be paged out. If, on the other hand, you do not have enough RAM, and you do a lot of adjusting at full resolution, then the speed of the disk that holds your Masters will become very important due to paging.
-- I found that I picked up a tiny bit of speed by keeping the Masters on a dedicated disk. Thus, in your configuration, if you can dedicate that 2 TB FW HD to your Masters, you should see very nice performance.
Final notes on backups and archives:
-- One conventional wisdom is that you should make an archive copy of every image file before or as you load them into your system. (Aperture in this case.) This archive is then never touched or deleted.
-- An alternative approach is that you do not keep such an archive, but only the images that you have in your Aperture Library. And when you delete from the Library, you no longer keep a copy anywhere.
I do the following:
-- Card to Aperture. Card is then kept at least 24 hours until all of my backups have run. (I use three - Time Machine, Clone, and off site.)
-- I do not keep archive copies. If I decide to delete a file, my only recourse is to recover it from Time Machine during the six month cycle of my Time Machine backups. Thereafter, it is lost.
There are merits to both approaches.
Hope this is clear, correct, and responsive to your needs.
DiploStrat -
Prompt Command File Manager: tiny bash FM
Last year pyfmii, now this. What's with these crazy file managers.
http://paste.pocoo.org/show/175499/
wget http://paste.pocoo.org/raw/175499/ -O ~/bin/pcfm; chmod +x ~/bin/pcfm
PROMPT_COMMAND=pcfm
By avoiding ncurses the program only takes up a few lines and doesn't clear the screen (and speed is still OK). It can paste right into the bash prompt using xdotool and xsel for a very transparent approach to the "subshell" in some file managers (like mc).
Features include bookmarks (you can actually call the program as a general selector for a list (try pcfm ls /)), sessions to keep track of last selected/marked files in a dir, searching in the list, some navigation things like trying to find the closest match when the previously selected item was deleted and auto-selecting the parent directory on `cd ..`, and a launcher for filenames.
It can generate the file list with any command you want, but will need a few functions to get the filename, and tell whether it's a directory and such. I have added a few of these "profiles".
The bad thing is that it needs xdotool and xsel, which I mentioned in this thread. xdotool can give bugs (I ran into shift lock a lot, which can be avoided by using an emulated click instead of Shift+Insert), will be a bit slow, and when you use it to paste, the mouse needs to be on the window. I actually wrote a function that moves the mouse on the window! So that is quite bad.
On the other hand, if a string only has ascii ([[:print:]] in C locale), it can be typed by `xdotool type --window xxx ...`, and xsel and pasting won't be needed. This speeds things up and makes it a little more stable (mouse doesn't have to be on the window, etc).
Anyway, if you use screen and like this file manager, be sure to try the different approach in the linked thread.
Screenshot:
Screenshot? Try your ls alias. On a related note, make sure you have a good LS_COLORS variable.EDIT: wget 'http://echtor2oo3.de/paste/9769876.txt' -O - | tr -d '\r' > ~/bin/pcfm; chmod +x ~/bin/pcfm
(before edit version: 'http://echtor2oo3.de/paste/7936610.txt', it didn't restore selected files if you didn't have a dir-specific profile)
github and an rc file is a bit too much for a tiny program. In a case like this, an rc file is good if you have frequent updates, but unless someone has more good feature requests, there won't be anything to update. (new profiles, keybindings, file associations, it's all up to the user)
I made the start of the file look more organized so it's easier to change. Note that F9 takes you immediately to edit the script.
find-as-you-type searches the entire line: directory entries start with d.
alias is a good idea (up to the user), auto-setting the prompt requires sending a command, so that's too tricky.
I added a command line switch -t, to set the default profile.
The profile keys are now:
^H: toggle iso / iso-no-hidden
(commented) ^H: iso-no-hidden
^S: time sorted (based on iso)
^E: extension sort (based on iso)
^T: traditional (full ls -l)
^I: iso (-g -G and long-iso time) (^I is also TAB)
^N: minimal (size, filename, ID character)
^U: custom (e.g. `find -maxdepth 1`, it brings up a prompt), since directory status can't be checked (actually you can, with `file`, I will look into it later), you have to type F2 and cd
^P: show the profile list and choose one (like bookmarks)
Last edited by Procyon (2010-02-13 13:28:46) -
Would someone be so kind to steer me towards the literature that explains how PPro manages media.When I capture I end up with files scattered across multiple locations. I've tried leaving the scratch disk setting at "same as project" and I've tried indicating specific folders. What happens in both instances is that PPro still makes it's own folders, for instance, "encoded files", "preview" and "auto-save". I just want to keep things tidy and in separate folders. Ideally if all of the encoded media went in one folder and all of the auto- save in another etc. The other ideal alternative would be everything contained in it's own project folder. If that is the default and I've changed something to prevent that then ....help. Also as a test I saved some things to the desk top and now I have these Peak files scattered across the screen. So basically is there a good resource to understand the files that PPro creates when capturing and in the course of making a project, where does it like to put things and is it customizable.
I'm on windows vista 64
TIAAh, now I understand. Yes, I can assure you that you will get over it. How do I know? Well, I come from an Avid pedigree as well. I spent over ten years on Avid systems before switching to PPro (motivated by cost, as I went from the corporate sector to being self-employed)--in fact, I purchased my first Adobe bundle without ever having used PPro. I went through all the same gnashing of teeth when I switched over, not so much because of the user interface or the general operation of the software, but because file management was so foreign to me!
With Avid, everything you capture or even import is converted into an OMF or MXF file, and subsequently dumped inside of OMFI Media Files or Avid Media Files folders. It's because of the Media Manager (which is the best of any NLE, hands down) that this can be done. However, this is a wholly inefficient way of dealing with a great number of media sources. For example, if you import a graphic file, you don't actually use the TIF or TGA or PSD or whatever it is. Instead, the import process turns it into what basically amounts as a fixed-duration video clip. Well, this makes sense if all you've ever done is worked in the Avid arena, but it's pretty dumb when you look at it from the perspective of any other editing application. Why would I want to go through an import process AGAIN if I decide to make a change to my graphic? I don't; that's a WOMBAT (Waste Of Money, Brains, And Time). With PPro, FCP, and others, you work on the graphic file itself, so all you have to do is make changes to that file in your graphics app and the changes are automatic inside of the NLE. The same goes for tapeless acquisition formats, like P2 or XDCAM EX--Avid imports and rewraps these; another WOMBAT. Now, that's changed in the latest revisions of the Media Composer because there is a new feature called AMA (Avid Media Access) that allows you to much more quickly get media into your project. It's been a few years since I've touched an Avid, but this represents a quantum leap for media management within the Avid-sphere. You're still shackled to some extent by the way media files are treated in the Avid, but since it's a platform that's been around since the dawn of desktop video editing, it's understandable that they can't break out of that thread.
PPro and other applications work with media in a far different way. With them, there is no converting of imported media to a "preferred" container file like Avid does. Because Avid works that way, it requires no user intervention to point the application to the correct folder to store that media--it just "knows". But PPro is working directly with your captured and imported AVIs, MOVs, JPGs, PSDs, WAVs, P2 MXFs--you name the media file, and there is no "changing" of the media happening (unless you do it before import). PPro doesn't really care what the file is (within reason) or where it is; if you import it, it'll work with it wherever it's located on your computer. Obviously, this represents a sea change from the way you operated in Avid, but it's much more liberating when you get down to it.
That said, for those of us who have been accustomed to working on Avid and the way that it deals with media, it's daunting at first. It requires more organization on the user's part, and a little bit of set-up work to make sure that everything's in its right place. It seems a little kludgy to have to point PPro to the folder you want to capture to every time you create a project, but it only takes a few seconds, and it provides incredible flexibility. For example, if you're capturing all of your tape-based media to a specific folder on your media drive, it's a simple thing to just drop that folder onto an external drive for backup. Likewise, you can drop your project folder (as I've outlined how I set mine up in previous posts) on that same drive, and you have a total backup that can be restored very quickly. Media management, like deleting unused files or old renders, isn't quite the same as Avid, I'll grant you. However, there are ways to accomplish these and other media management tasks, both within the software and at the OS level.
Let me address a few of your points now:
For instance when I read the words Master Clip my ears perk up because those are pretty important in Avid Media Composer. But the "log clip to" option is just a way to indicate a bin/folder to store your logged clips in case you want to batch capture later or if you like to keep things tidy in the project window like I do and have all of the stuff you brought in from tape in a specific bin. FCP has that feature but they call it something else "default capture bin". Same thing different name.
Master clips are pretty much the same in PPro as they are in Avid--they are your virtual representations of the media files on your disk. They are part of the project, not separate free-floating beings. I liken them to "Shortcuts" on Windows and "Aliases" on Mac OS; they're just pointers.
"Log Clip To" not only points where logged clips go, but also where clips that you capture on-the-fly are stored, within your project. Avid provides the same in their Capture tool, if I remember correctly, and FCP does this by setting the "Logging Bin". Potato, potato.... that doesn't work so well in print.
I found it odd that an "encoded" folder is an automatic when encoding is not a given - you may lay off to tape most of the time or dynamic link to Encore. It led me to believe that that was were the captured footage would be sent to by default and when it wasn't there when I chose "same as project" I was like WTF.
Yeah, I get this. It seems rather pointless; as I mentioned previously, sometimes I use this folder, sometimes I don't. I have a sneaking suspicion that this is some kind of holdover from the pre-"Pro" days of Premiere. Unfortunately, the only recourse is just to ignore it.
Different editing programs call captured footage different things. Avid calls it digitizing, FCP calls it capture. I used one package once called it the "magic morphing mechanism" (kidding) In Avid all of your digitized files have to be in a folder named OMFI or MXF which of course can be put on the scratch disk of your choosing but they have to go in that folder and it's automatically created. But the inside of an Avid OMFI or MXF folder is a real conglomeration of file types all spread out a lot like this PPRo (at least PPRo creates the folder named after the project for the captured footage). However, AVID has a very robust media manager that helps you find asssociated media by project, type and location.
Does Avid still call it "digitizing"? I can't remember what they called it, last time I used it. Again, that's due to Avid coming online sometime around the late Cretaceous period when people still shot on analog tape (gasp). Nowadays, with most shot tape being digital, "Capture" is probably the more accurate nomenclature, as the video is already in a digital form. I like the "magic morphing mechanism" though--I need to get me one of those.
I touched on the Avid points above; I won't re-spew.
Premultiplied files are AVID's name for previews so you can do a search for those, it finds them all for that project in the one OMFI folder for example and you can delete them or whatever.
Now, now--as an Avid editor, you should know they're called "precomputes" Just ribbin' you...
FCP calls them rendered files and puts them in a centrally located folder called rendered that it creates seperate and automatically for each project but all the projects are in that one render folder. In FCP you get a quicktime inside your automatically made centrally located capture folder/inside a folder with the project name. And you only set that capture location once.
FCP probably has the most flexibility of any of the NLEs when it comes to media folder creation, but it's also the most dangerous. I spend some of my days on this system, and it's sort of weird, powerful hybrid of how Avid handles media and how PPro handles media. The problem is that it's REALLY easy to screw up, and you can end up with "Capture Scratch" folders stacked inside of others to the nth degree if you're not careful. FCP creates just as many (in fact, I think more) "system" folder as PPro--like the Waveform Cache folder, and the Constant Frames folder, and Renders folder, and lions and tigers and bears, oh my. I've grilled a buddy of mine who is an FCP editor for hours about this (he also came from Avid) and he said he finally just gave up trying to make it make sense, and just goes with it. Apparently it's some sort of zen thing.
My point is, you can make it work the way you say, and to an extent I'd like to see PPro offer this as an option, though not a standard.
Maybe it's a windows thing but I wasn't expecting anything but the .mpeg or whatever and now I have multiple file types associated with the one capture. .caf .pek. I just like to keep things in tidy but simple folder structure and understand what the files are so when I go to clean my drive I know what to delete and what to save. To me it's a bit of an annoyance to have to set these locations for each project. I'll get over it, maybe.
Well, in the case of .CFA (ConFormed Audio) and .PEK (waveform PEaK) files, those are generated when you import/capture media with audio. CFA files are created when an audio clip doesn't match the sampling rate of your project's audio, and PEK files are the waveforms that are drawn on audio clips. FCP does the same thing; that's what the Waveform Cache folder is all about. You might also come across things like .MPGINDEX files, which are index files created when an MPEG clip of some sort is imported (it tells PPro where independent frames in an MPEG-encoded video stream are located). You don't see things like this on Avid because of the "rewrapping" that goes on--Avid simply forces every imported clip to play by its rules. Because PPro is all kumbaya about media, it has to create this "helper" files. It might seem a bit messy, but for the most part they'll be stored with your media files. In fact, there's a preference in Edit > Preferences > Media to save these generated files next to the media they are sourced from. They're typically small files, so they're not much to worry about. I assure you, you'll get over it.
I think your method of creating a project folder on a seperate drive of course and then pointing everything to that is a good method and should keep me organized and sane.
Honestly, the way that I've set up my projects and media drive is influenced by my time on Avid. Using the present options available within Premiere, it's the closest approximation that I've been able to create that mimics the media file/folder relationship as it is in Avid. It's not perfect, at least not when you compare it to how you're accustomed to working in the Avid, but in time I really think you'll start to like it even better.
...maybe you know if there a way to decompose a sequence or batch capture a sequence with PPRo?
No way to decompose as you do in Avid, but you can try a couple of things to slim down a project if this is what you're trying to accomplish. For one, go to Project > Remove Unused and that will remove all media from your project that is not being used. It doesn't delete the media from this disk; it simply gets rid of all the master clips that are not being referenced by any sequence in your project. Additionally, you could try the Project > Project Manager. It's not the Media Manager from Avid, by any stretch of the imagination, but what it will allow you to do is either collect all files used in your project and move them to a new destination, or you can trim your sequences (with handles) and move that trimmed media to a new location. Check it out on a COPY of your project first, just to be safe.
To batch capture, simply highlight your offline clips in the Project panel, and select File > Batch Capture. The Capture tool will open up, and will prompt you for tapes as they're needed; I'm sure you've done this in Avid, and it's not a whole lot different from that. Here you can read all about it...
Hope some of that is helpful... -
Can't open file - file manager error
I can't open a couple files I was working on this afternoon. I shut down my computer when I left the office, now that I've booted again, when I try to open either of these 2 files I can a message that says "While attempting to access "file name" the file manager reported an error - 39."
I haven't made backups of these files, so that isn't an option.
I've rebooted a couple times, I've repaired disk permissions, but nothing works.
Previous files I worked on DO open correctly.
HELP! PLEASE!I'm not sure if you have time to hold the hand of a "newbie" to Terminal
Of course! I'm always happy to introduce people to the command line
1) prompt$ - is my name bryceinman$
Most likely, yes. The default prompt usually contains the machine name, and sometimes the folder you are sitting in, and will usually end with a $ or a % (for a normal user), and typically a # for the root user.
2) cd - is that the name of the hard drive or do I just type "cd"
That is a command which means "c"hange "d"irectory (when you hear "directory", think "folder") and is how you move from one directory to another from the command line.
3) after that, it appears that I'm simply typing the path to the location of the file.
Yep.
Are you saying the "filename" will be the next string displayed by Terminal if, indeed, the file can >be found correctly? (Right now I'm getting the following: -bash: Macintosh: command not found)
That's correct. Once you've changed directories to the directory/folder that contains your problem file, you type at the prompt "ls -l filename", except that you will substitute the real file name for the word "filename" in my example.
And yes, using this same logic, the "cat filename > /dev/null" you will use the actual file name in place of "filename".
Maybe an example will help. Let's say I have a machine named tomservo, and a file called SmithDoc.txt, and it's located in my Documents folder, in a sub-folder called Work. To perform my above suggestions from the command line, I would do the following (I also show example output):
(Launch Terminal from Applications->Utilities)
tomservo$ cd Documents/Work
tomservo$
tomservo$ ls -l SmithDoc.txt
-rw-r--r-- 1 glsmith staff 512 Jun 10 22:01 SmithDoc.txt
tomservo$ cat SmithDoc.txt > /dev/null
tomservo$
A few things to note here. Since I added example output to the above steps, you may wonder why there is a blank prompt after the "cd" and the "cat" steps. This is normal Unix behavior. Many times, commands will not print out anything if they operated correctly. So, since I was able to change directories correctly in the first step, I got no output. In the second step, I'm asking the system to print information about the file ("ls" means "list", think "dir" in Windows), so that's why we see output. In the third step, I'm asking the system to read the file ("cat" means "concatenate"), but to redirect the output to the system bit-bucket (/dev/null). Don't worry too much about what /dev/null is -- think of it as a black hole. Anyway, since all the output is going there, that's why we don't see any output there either.
Why do I want to do this? Well, since "cat" will read the file without caring about what application created it, it's a good way to test the file's integrity in the filesystem itself. If there is something wrong with this file, the "cat" will get throw an error.
One last thing to mention, and hopefully this won't confuse the matter. If you have a file that doesn't have spaces in its name, please use that one to test with. That's why I used SmithDoc.txt. The command line can certainly interpret files with spaces in the name, but you must enclose the filename in quotation marks, or escape the space (don't worry about what that means). So, if my filename was actually Smith Doc.txt, anytime I typed this on the command line, I'd have to do:
prompt$ ls -l "Smith Doc.txt"
and
prompt$ cat "Smith Doc.txt" > /dev/null
Hopefully this all makes sense! -
WebDAV access from File Manager gone from Belle
The Files (formerly File Manager) app has been stripped of its WebDAV feature.
For me, this is a big inconvenience, as it means that N8, E6, 701 now has no built-in means of exchanging files with our home Synology NAS box. (AFAIK, Belle has no FTP, NFS or AFP client "out of the box" or available in the Store, and I'd have to cough up £3 for MyExplorer to add a Windows file-sharing (SMB) client to N8, E6, 701 etc.)
I don't know if anyone involved with Belle on the Nokia side, reads this forum, but after asking them why they felt they had to remove a genuinely-useful feature, I would plead with them either to restore the WebDAV client functionality to Files, or provide a separate app to enable some kind of file-sharing (WebDAV, SMB, FTP, whatever).
If I have to pay for a third-party client to give me this functionality, no problem, then so be it, but I do have to ask why a 2012 smartphone platform is shipping without a single means of exchanging files over a network (and I don't count USB or Bluetooth file-transfer). For that matter: does anyone know why WebDAV was removed from Files?
Maybe I'm the only user who even noticed that WebDAV was gone, but I just had to "vent" a bit...
Nokia 808 again (delight Belle), Nokia E7 and X7 ( again, all on Delight Belle...after some time on Nokia Lumia 925 (retired), 1020 (not that great)and Lumia 820 (Replaced my router at home, great for internet sharing).., N9 The best device ever (use it as much as Lumia 1020), Nokia 700 (Sport Phone/My Love :-) ) Nokia 701, Nokia E6 (Should have a follow-up from Nokia among with larger screen, NFC, Autofocus), Lumia 800 (Retired After 6 weeks), -Sports Tracker-Nokia Internet Radio-Handy Safe-Skype-Bambuser-Screenshot app pro-fMobi-ComingNext-Manual TaskSwitcher-jagiTimer-Easy StopWatch-Boldbeast-Equalizer-Financial Calculator-WiMP Music-YTasks-Davi-Thumbnail Folders-BizCalendar-Tiny7-Situations-nn reeder-Sport Timer-CameraLover-CameraPro-GrabRadio-LiveScore-Poddi-Gravity-SkyFilesProAnd this answer I received from th devoloper of myExplorer in March;
Hello!
Unfortunately, myExplorer does not support WebDAV. However you can still connect remotely to your NAS or other file server in two ways:
A. By forwarding the SMB port in your router.This is easy to setup but it is not very secure. While authentication information (user name and password) is protected, as they are never transmitted unencrypted, the rest of the traffic will go over unsecured connection. Here is what you have to do for this to work:
1. Forward port 445 (or 139) on the file server (or NAS) in your router to another port (for example 22678 - the number is not important, what is important is to write it down for later).
2. Create a new network share in myExplorer and type the external IP address of your router in the field "Computer IP address). If your external IP address is dynamic and you are using some kind of dynamic DNS, instead of IP address, please fill the DNS name of the router in the field "Computer DNS name".
3. Fill in the port number from step 1 in the field "Port number"
4. Select "Always ask" as access point because you may need to use different access points depending on your current physical location (3G on the road or Wi-Fi in the office, etc.).
5. Please note that you will have to add exception to your firewall for port 445 or 139 as most firewalls block the ports 445 and 139 when the other IP address is not local. This is true even for the built-in firewall in Windows.
B. By using VPN network. This method is better from security point of view but it requires more work to setup. First you need to setup a VPN network from your phone to the LAN where the NAS is located. This can be done in few different ways and the concrete steps depend on what kind of VPN you are using. After you have working VPN, all you need to do is this:
1. Fill in the NetBIOS name or the (local, not external) IP address of the computer.
2. Select the created VPN access point as the access point for this network share.
Please note that both methods above require some knowledge about the networks. We are planning to create a tutorial, which explains the needed steps but it is not ready yet.
Best regards!
myExplorer
I wrote; 2 questions,
Can I log in to a nas through webdav and using 3G
Can I have the address as https://mynasserver.no-ip.org:7001 when connecting over 3G. The server don’t have a 192.168.1.1 adress over the webb
Regards
Ztuka
Nokia 808 again (delight Belle), Nokia E7 and X7 ( again, all on Delight Belle...after some time on Nokia Lumia 925 (retired), 1020 (not that great)and Lumia 820 (Replaced my router at home, great for internet sharing).., N9 The best device ever (use it as much as Lumia 1020), Nokia 700 (Sport Phone/My Love :-) ) Nokia 701, Nokia E6 (Should have a follow-up from Nokia among with larger screen, NFC, Autofocus), Lumia 800 (Retired After 6 weeks), -Sports Tracker-Nokia Internet Radio-Handy Safe-Skype-Bambuser-Screenshot app pro-fMobi-ComingNext-Manual TaskSwitcher-jagiTimer-Easy StopWatch-Boldbeast-Equalizer-Financial Calculator-WiMP Music-YTasks-Davi-Thumbnail Folders-BizCalendar-Tiny7-Situations-nn reeder-Sport Timer-CameraLover-CameraPro-GrabRadio-LiveScore-Poddi-Gravity-SkyFilesPro -
[Request] BSCommander (File manager)
Light , QT file manager..
Home page = http://www.beesoft.org/bsc.htmlhere you go, thanks for the cool link, I've been looking for something like this.
# Contributor: mpie <[email protected]>
pkgname=bsc
pkgver=2.17
pkgrel=1
pkgdesc="Qt filemanager"
url="http://www.beesoft.org/bsc"
license=""
depends=( 'qt' )
makedepends=()
source=(http://www.beesoft.org/download/bsc_2.17_src.tar.gz)
md5sums=('78587d9e25e79ab79ecd8809f0401f3b')
build() {
cd $startdir/src/$pkgname
qmake bsc.pro
make
install -d -m755 $startdir/pkg/usr/bin $startdir/pkg/usr/share/bsc/images
install -m755 bsc $startdir/pkg/usr/bin
cp images/*.png $startdir/pkg/usr/share/bsc/images/ -
Slow copy speed using file manager(s)
Hi everyone!
I have a strange problem:
When I copy files over the network (smb) using a file manager I just get ~100 MBit speed.
The same copy opreation via command line runs on full Gigabit speed.
Doing more than 1 copy (or move) via file manager results in 100 MBit for each operation (up to 3/4, then they are getting slower).
The very strange thing is: I get the same behavior using Thunar / XFCE on my current Arch setup as well as on previous Ubuntu based setups (Xubuntu and Kubuntu).
Installing an Intel Server NIC also doesn't change this behavior.
The other hardware also should be no issue. Copy target is a QNAP TS-459 Pro II. The PCs are quite new 8-Core AMD and Intel Core i7.
Copying files in Windows (7 pro) also gives me full Gigabit speed ~110 MB/s.
As searching for this topic turned out more or less impossible I hope someone here can help me.
Thank for any hint!
BurnsSame here. I also am posted on the crashing thread since the 3.3 update.
I noticed the speed thing too, just kind of ignored it for the moment. If I copy to 2 or 3 Macs it works, still slower than it should be. If I try to copy to 10 or more Macs, it is very slow or just fails to work. Did not have this issue with 3.2.
Clients and admin Macs running OS 10.5.8.
Maybe you are looking for
-
How can I talk to a live agent
HOw. Can I talk to a live agent. Need to cancel orders placed by mistake
-
Can I set up safari to automatically open PDF documents in the pages app?
Can I set up safari to automatically open PDF documents from the internet into the pages app?
-
Deleting locked file on desktop
Greetings- This is more a software question. I transferred QuickBook files from a PC to my Mac. I can run QB for Mac easily, but the transfer left a locked .qbw file on my desktop. I think this is a QB backup for Windows file. I am trying to delete i
-
Oracle Extensions Examples & WebLogic Server
I've run the oracle extensions examples with weblogic server and cannot get the string representation for the addresses, as indicated in the examples documentation. I get a hexadecimal representation. I'm running structs, refs and arrays business obj
-
No sensor values have been generated for this instance.
Hi We are trying to insert values of a sensor variable into Database using a Sensor Action. Sometimes,it is working fine.and sometimes not. We couldn't even find any logs regarding this issue. Please help me at the earliest. Thank you.