Corey Sullivan
Forum Replies Created
-
I have 4 NLE’s set up, all in the same configuration, but I’m having that issue on just one system. I’ve checked the drivers, cleared the cache, and even swapped video cards, but this one system continues to have the problem. The other three systems are fine, so I guess I need to dig in and figure out what’s different with the one that’s sick.
-
Yes, we’ve used the C:/volumes function and run into the same issue. It doesn’t seem to make a difference whether I’m mounted to C:/volumes or to a letter designated volume.
And I tried testing with DVCPro50 footage from tape vs. DVCPro 50 footage from the P2 card. DVCPro50 from tape was fine when editing, but from the P2 card I had the delay.
-
We’re working with PC’s and they’ve only got the one drive installed, so I used it as a test. I had no problems working off the C: drive, even with P2 footage.
I’ve been chatting with our vendor (who’s also been on the line with Facilis), and they think that the way Adobe maintains a constant path to the media could be making it hard to handle P2 footage in a SAN environment.
-
We’ve tried loading projects up with DVCPro 50 footage (from tape), and haven’t had a problem with that. But as soon as I added 7 gb of P2 footage the delay issues returned. When I deleted the P2 media files, once again, there was no delay. Then I brought in about 7 gb more of DVCPro footage to see if it was a space issue, but I didn’t have any problems.
Corey
-
The “waiting” pinwheel pops up for 15 – 40 seconds when I switch out of Premiere Pro and then try to re-enter the program. So if I’m working in After Effects, then try to pop back into Premiere, there’s a delay. It doesn’t happen if I move everything to a local drive.
As for the RAM, we’re working wth 16 Gb of RAM, 12 gb dedicated to Premiere, and we have no e-mail programs running on the system, it’s just a straight production box.
As for the 5 – 10 minute delay when you first open Premiere Pro, we get that too, and the time we wait seems to be based on the amount of footage that’s in the project bins. Even more RAM doesn’t help here because I think Premiere goes and checks for changes in each clip before making it accessible.
-
We’re set up to use fibre for the data transfer during editing. Supposedly, ethernet is not in play when we edit, and we’re using that when we flip completed projects to our playback server. But your comment about the metadata controller using ethernet makes sense and I’ll look into that. Thanks!
Corey
-
We’re using a Facilis Terrablock 24D with the Fibre/Ethernet combo. It’s been very reliable.
-
A SAN is a storage area network with a very high data transfer rate. It’s a central storage location that multiple edit suites can be networked to. We have projects that go to different editors for different stages or segments of editing/graphics work. In some instances we share footage across different projects, so the SAN is supposed to offer us an easy way to share/transfer media and projects.
-
Premiere works great on local drives, but I’ve run into issues when trying to run it on the SAN. I’ve got 4 workstations, running 3.2 GHz Xeon quad processors with 16 gb ram, over an 8gb fiber connection to a 24 TB SAN.
In speaking with Adobe tech support they don’t recommend editing from the SAN with P2 media. They said it’s a known issue… and that’s where we’re experiencing the lag. Again, I have no problems editing on local drives, but that’s not how we planned our workflow.
As for the cache, the tech support guys still recommended that I put the media cache on a separate drive.
-
I’m running into the same problem with the delay, and I’ve got 16 gb of RAM with an Intel Xeon W3565 @ 3.2 ghz on Windows 7 64 bit OS. Even with just a few minutes of video in the project, I get the delay. I’m also tied to a 24 TB SAN with an 8gb fiber optic connection… but I’m told that’s where my problem is… Adobe doesn’t recommend using a SAN with uncompressed video.