[Adam Chesbrough]

Jeremy has the solution! Grabbing the “puck” is the solution. To clarify for everyone the “puck” Jeremy is referring to is the center circle. See below:

Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

OWC 4TB RAID0 (using esata)
Tempo SATA Pro ExpressCard/34 (3Gb/s)
Echo ExpressCard Pro Thunderbolt Adapter

[Adam Chesbrough]

Thanks guys. I am just used to repositioning within the window. It would be great if the inspector corresponded automatically to the clip in which the playhead was currently on. That way I wouldn’t have to use the mouse to click on clip, goto inspector and drag the x and y axes.

Ricky, are you saying that you shift drag in the viewer maintains the absolute x and y axes or are you referring to the inspector?

Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

OWC 4TB RAID0 (using esata)
Tempo SATA Pro ExpressCard/34 (3Gb/s)
Echo ExpressCard Pro Thunderbolt Adapter

[Adam Chesbrough]

Thanks Ron, so it looks like my issue is the 3gb/s expresscard. I am just wondering if it makes sense to wait and purchase a 6gb/s hub when it comes out. I imagine that I will get similar speeds to what I am seeing now with the lacie 3gb/s hub.

Macbook Pro Retina
2.6GHZ i7
16GB RAM 1600MHz DDR3

OWC 4TB RAID0 (using esata)
Tempo SATA Pro ExpressCard/34 (3Gb/s)
Echo ExpressCard Pro Thunderbolt Adapter

[Adam Chesbrough]

What type of speeds are you getting. I have the same setup and am getting:
read: 84mb/s
write: 200mb/s

The read is a major drop from when I would go directly into the expresscard of my 17″ MBP which sustained around 180mb/s read/write

I too went with the echo thunderbolt adaptor so I could utilize the tempo pro card that I already have. I spoke with sonnet and they said that because my HD RAIDs are controlled internally I would see a performance increase with the 6gb/s card (doesnt support port multipliers). I really need to 200+ if I want to take full advantage of the new computer.

What are your thoughts/experiences?

Macbook Pro Retina
2.6GHZ i7
16GB RAM 1600MHz DDR3

OWC 4TB RAID0 (using esata)
Tempo SATA Pro ExpressCard/34 (3Gb/s)
Echo ExpressCard Pro Thunderbolt Adapter

[Adam Chesbrough]

I am running 10.7.4 and FCPX 10.0.4. I installed FCP7 on the same disk earlier today, everything then felt sluggish although that is probably because of reading about potential issues (although no one seems to know what issues can arise). That being said I uninstalled all final cut pro versions and reinstalled FCPX to my 750GB boot drive. I am going to partition and then install FCP7.

My question is whether I need to wipe the drive, create two partitions, then install from my current time machine backup to one partition and install a clean version of lion to the other.

OR

can I just create a partition in disk utilities (easier) and then install lion to that partition (how would I go about doing that? On startup?)

Thanks

macbook pro 17″ i7, 8GB RAM
2 RAID 0 esata external HD 7200RPM

[Adam Chesbrough]

What are the specs of your system? I am in need of a new workstation and am basically waiting to see what mac is going to be doing with their pro lines. From what I understand the underlying structure of FCPX is what really sets it apart. Namely it’s ability to utilize video cards as additional processing cores (in addition to using them to their fullest in editing). I am forcing myself to use FCPX even because of the performance promises…

macbook pro 17″ i7, 8GB RAM
2 RAID 0 esata external HD 7200RPM

[Adam Chesbrough]

I have tested this in the past (and then just now) and rendering prior to “export” saves considerable time. With my workflow I usually create a project and then render so that I can watch in realtime to make sure that everything is all set. When exporting your computer computing is using all of its resources ie you can’t work on anything else (at least with the macbook pro); therefore my time is better spent letting it render while I am away, coming back to export, and then encoding overnight (especially if I have multiple projects to encode)….to each his own. That being said, “send to compressor” is not normally a viable option for me (I also like to have the uncompressed, contained, project to use in the future.

macbook pro 17″ i7, 8GB RAM
2 RAID 0 esata external HD 7200RPM

[Adam Chesbrough]

I render the project in the timeline; set the in/out points, “export media” then encode that file in compressor. Although a two step process, encoding this way is 3X faster then “send to compressor”. Below is a link that discusses this process:

https://forums.creativecow.net/thread/344/9418

macbook pro 17″ i7, 8GB RAM
2 RAID 0 esata external HD 7200RPM

[Adam Chesbrough]

Background rendering was off. It crushes my computer to keep that one.

macbook pro 17″ i7, 8GB RAM
2 RAID 0 esata external HD 7200RPM

[Adam Chesbrough]

Process=workflow

1. I did 0 prerendering in this workflow…very simple: I added the clip to the timeline, added the effect (now has orange bar), send to compressor, after 12 minutes I have a H264, .mov to upload to the internet.

2. After the timeline is rendered (took 2:20) the export (with current settings…cmd E) takes about 6 seconds (or as I mentioned in the post “marginal” ie not worth even considering since this second workflow is so drastically faster). That exported file is a ProRes file and needs to then be encoded with compressor (which took another 2:20.

macbook pro 17″ i7, 8GB RAM
2 RAID 0 esata external HD 7200RPM