Matt Riley
6
COW Coins
7
Storage & Archiving Coins
Forum Replies Created
-
[Tucker Dansie] “I’m just totally confused as to why things would be different based on the USER! “
This sounds like a permissions/ownership problem.
Xsan – and any other shared workgroup environment – depends on users and groups to determine file ownership. If User A captures video files to the Xsan then User A, by default, is the owner of those captured files. Unless User B is granted permission via some method (explicitly redefined or by being part of the same group, etc.) then User B will have no access to the files User A captured. Try putting your users into a new group and give that group full R/W access to your capture scratches on the Xsan volume(s). This would hopefully rule out most or all of any permissions problems you might have.
As for the file renaming problem, I suspect you had illegal characters in your file name. A trip to the command line of the Xsan metadata controller would’ve probably allowed you to rename the file in-place.
-Matt
-
I almost always recommend doing an archive and install rather than a straight upgrade. In the case of cs3 apps, you should be all set with no reinstallation of the suite necessary.
Doing an A&I gives you a clean system while preserving your user and network settings and also keeping your application installs intact (save for some instances).
-Matt
-
A rendering we go indeed.
I’m going to need new Apple and R keys before too long. I guess there is always key remapping. 😉
-Matt
-
It’s no joke: It is not recommended to use the DS Nitris’s BOB SD downconvert for anything other than preview purposes.
There are lots of things that are unacceptable on the DS/Nitris platform, especially given the price and the market it is aimed at. That’s a whole thread by itself in a different forum. 😉
-Matt
-
It’s no joke: It is not recommended to use the DS Nitris’s BOB SD downconvert for anything other than preview purposes.
There are lots of things that are unacceptable on the DS/Nitris platform, especially given the price and the market it is aimed at. That’s a whole thread by itself in a different forum. 😉
-Matt
-
Ugh.
It’s a sad day when Final Cut Pro – with it’s lack of sub-pixel precision – is able to make a better scaled image than hardware. 🙁
No offense to you, but it sounds a bit like an Avid response. Avid has pulled the same sort of deal with their DS Nitris and HD to SD downconversions…
“See that feature? Cool, isn’t it? You can playback HD and SD at the same time on this $150k box. Nifty, eh? Yeah, don’t use it for anything but preview purposes, though. It’s not as cool as you thought, now is it?”
-Matt
-
Just because Apple isn’t having a booth at NAB doesn’t mean they won’t have any major news around that time.
They’ve already proven the opposite is true: That just because they DO have a booth at NAB doesn’t mean they actually have anything major to announce. Two years ago, they announced… wait for it… the 17″ Intel MacBook Pro. Oh, and an Intel-native port of Shake. Big whoop. They didn’t need a gigantic booth at NAB to announce that.
That was it. Nothing else. Last year, of course, was FCS 2, which was a big deal. Three years ago was FCS 1, which was also a big deal. So, Apple has proven that NAB essentially guarantees exactly nothing in regard to what they release. Sure, it’s nice to have a major new release coincide with a major event like NAB, but it isn’t necessary.
Also, consider that Apple is a big enough player to warrant their very own PR extravaganza for just about anything they wish. They don’t need NAB as a vehicle for their product publicity; Apple has enough industry pull and cash to throw their own big launch party for any product at any time and get all the press coverage they want, especially from the video/post industry rags.
I have no inside knowledge of anything, but to me Final Cut feels old compared to the rest of the suite. I personally believe there are some pretty interesting signs pointing to rewrite or at least a significant upgrade to Final Cut in the near future – maybe this year, maybe next.
First of all, it is the only app in the suite that still uses an essentially OS 9 interface. Think about it: FCP looked exactly the same on OS 9 as it did in OS X. It has some deep carbon roots that I suspect are holding it back from really growing (64 bit native) and taking advantage of core OS X technologies (look at Motion’s UI).
If you look at FCP 6, there are some things in there that to me indicate some big things ahead. One example is the ability to monitor background tasks. This is how you see the progress of the smoothcam filter, which, if you all remember, is really shake technology that found its way into FCP. But not really. That little monitor background tasks window doesn’t look like it belongs in FCP – it looks like the rest of the FCS suite (save for Color, which is a different story). Also, the Log & Transfer window has the standard “Pro App” look the rest of the suite does and feels more like a mini-app that lives within FCP rather than just a window into an internal FCP process. The fact that you can continue work in FCP while an import is happening in L&T turns over a couple tea leaves for me. 🙂
I would really like to see Apple take all of that wonderful shake technology they are letting rot and build it better into FCP. They’ve built a good deal of it into Compressor, which is the ONLY app in their suite able to fully leverage multi-core processing. Why shouldn’t FCP be able to tap that same power when rendering? I feel the answer to this is because FCP’s code base is old (tried and true, yes, but old) and it is simply unable to take advantage of useful things like network rendering, 64 bitness, advanced GUI, etc. without a significant update to the code.
The big question – aside from “if” – is “when?” I suspect later rather than sooner but I am always willing to be surprised. 🙂
-Matt
-
NEVER type an entire message in all caps unless you are really pi**ed about something. Seriously, it’s offensive to the eyes.
That said, try trashing this folder:
disk/
/Library/Application Support/Soundtrack Pro Where “
” is the short user name of your home folder. After you pitch the aforementioned folder, try launching Soundtrack Pro again and see if it fixed it. -Matt
-
Hmmm… After doing some more testing I’m starting to wonder if the 24p part of the files is throwing Compressor off.
I had a few NTSC captures that I threw into Compressor and the TC showed up correctly in those. All the other media I’ve been trying has been 24p (P2/DVCPRO HD 720p/24 and 1080p 4:4:4).
I don’t see any obvious way to have Compressor interpret the TC as base 24, though. Maybe that’s not it. Just throwing ideas out there out of frustration.
-Matt
-
[Chris Seguine] “You could also use Episode to do the conversion, you can tell it to copy the original timecode, or set the timecode start. “
I just tried using Episode but it gives me an error when trying to preview the file.
Not surprising to me. I have little confidence in Episode. Different thread. 😉
-Matt