Joseph Hung
Forum Replies Created
-
You were right. At 100% I can see the fields and the ghosting is there. “Fit to window” does not show these errors.
So, what I did was drop the clips into the Timeline, added deinterlace filters to each, set it to Lower (even), render and output the files at current settings and now the clips play fine.
I would love to know why this is? Why does FCP hide these issues at smaller viewing sizes? Deinterlacing the clips worked out, but maybe I don’t know enough about how deinterlacing actually works? I plan on doing more VHS captures, but the more I know the better I’ll be.
Thanks for your help!
Joseph -
If you haven’t already, set Premiere to treat stereo tracks as two mono. You can bring them into track pairs, panning one left and the other right, without much hassle.
Great this makes sense for stereo tracks.
If you have a mono channel, it can live as mono as the bus will pump it to each speaker in equal amounts. If you pair it with another copy, not only is it redundant, you’re also mixing each side in phase which will lead to higher amplitude.
To be sure I understand, for those mono tracks, I shouldn’t double it up and pan L/R? I should keep it as a single mono track and pan center? For the tracks with both boom and lav I can treat each separately provided that I keep the pan center?
-
Dang all sort so of people I recognize from the FCP forum is over here too! Add me to the list…
7) the shift+opt+drag technique doesn’t work for me in PP CS5.5. I can’t seem to get it into the shortcuts either. Any ideas?
-
I learned a work around on the forums, either collapse all of your audio tracks or set the display mode of the audio track to “show name only”. It has something to do with the audio waveforms and loading the preview of the waveform. Pr cs5.5 was virtually unusable, and now I haven’t gotten one error message. Yet.
-
Hey Mark, how’s the CS6 going?
I am realizing I can’t use Pr on my Mac Pro 2,1 as Adobe has cut off 32bit EFI support as of CS6. Bummers.
Here is a thread on Adobe forums detailing the many issues with this same exact error issue that we’re experiencing. Many people have been having issues with CS6 on Macs, some that seem resolved for a month after extensive system rebuilds uninstall/reinstalls etc and the serious error comes back.
You may find this interesting, and when/if your Pr starts crashing again.
https://forums.adobe.com/thread/1016670?start=0&tstart=0
Keep us updated!
Joseph -
Yeah, I’m doing some research and and checking the bank account now. Very interested in CS6 but can’t throw down on a full license, which would be ideal, but now is not the time. Buying just Premiere is an idea. However, as I’m an FCP7 editor since FCP1 and looking for options other than FCPX, I naturally decided to give PPro a go. This is my first time using it honestly, but I think I have been doing everything correctly (it’s not all that different from FCP7 in some ways). For these random debilitating errors to be happening now, when I’ve barely even begun editing (this is happening while I’m just creating bars and tone and 20 second leader with countdown and 2 pop! Geez!), it hasn’t been a great start to my learning curve 🙂
I’ve read many people having similar errors with paths that are virtually the same. Noone seems to have fixed the issue other than the constant grind teeth, squeeze ball, reboot.
Thanks for the help
-
Any solutions to this? I’m getting the same exact error. Your posting is the only one that comes up for this specific error, however many people are getting seemingly random errors of this type.
When it first happened, I hit Continue about 10 times and the window went away. The second time the window stays no matter how many times I continue. However, I am able to continue editing “underneath” this window. I even saved and tried to shut down PPro, but in the end had to force quite, then the Continue button works and it goes away.
Just started my first project in PPro, a short one, so I’m barely in deep in the project.
Any thoughts welcome,
Josephhttp://www.tulpapictures.com
Twitter: @tulpapictures
Facebook: http://www.facebook.com/tulpapicturesMac Pro 3.0 GHz 8-Core Intel Xeon (2,1) 8GB RAM
Macbook Pro 2.3 GHz Intel Core i7 (8,2) 4 GB RAM
OSX 10.6.8
FCS2
CS5.5
Blackmagic Intensity Pro
NVIDIA GeForce 8800 GT (CUDA)
RocketRAID 4322 via dual MiniSAS
ProAvio 8TB RAID 5 Dual Mini-SAS
Panasonic Lumix GH2 (hacked), Canon 5DMKII, 7D, Panasonic HVX200A, Panasonic DVX100A -
Actually, I realized my sudo nano path in Terminal was incorrect. I altered it a little bit and now Terminal lists supported cards. I added my card, and voila I can now choose Mercury Playback Engine GPU Acceleration. It seems to be still a question in the forums about booting in 32bit kernel so I’m not entirely sure if I’m using the CUDA capabilities at it’s fullest. I am seeing a little difference in performance however, so maybe it does work? I’m no expert and don’t have hard numbers so it’s just a visual feeling I’m guessing from…
-
Well, that answers all of our questions I guess. Thanks.
-
I was in the same position and went ahead and upgraded my Mac Pro 2.66 GHz Quad (1,1) to a 3.0 GHz 8 core (2,1) by swapping out the CPUs. I also went ahead and bought an Nvidia GeForce 8800 GT 1GB VRAM from Macvidcards on ebay. The ebay auction states that this will work with 2,1 Mac Pros and with the CUDA hack for GPU acceleration.
I would recommend to the OP to do this, HOWEVER, I’ve come across a little problem.
I updated to the latest cuda drivers from Nvidia. The latest Nvidia driver (256.02.25f1v1) will not install on my computer (states: This computer will not support this NVIDIA graphics solution). This makes sense since the driver is for Mac Pro 3,1 and up, as stated by Nvidia. I also found on some forums that I don’t need to update to this as it’s already bundled with the OS. So I skipped this step. I proceeded with the hack, followed the instructions perfectly. In Terminal, I got the “1 device supports CUDA” confirmation. I went to modifiy the cuda_supported_cards.txt file in Terminal, and nothing comes up. No list of supported cards. I added my card’s name anyways, and Terminal tells me that the txt file doesn’t exist.
Fired up Premiere Pro CS5.5 (master collection) to check this and yep, the Mercury Playback Acceleration software only is greyed out.
Any ideas out there? many thanks.
http://www.tulpapictures.com
Twitter: @tulpapictures
Facebook: http://www.facebook.com/tulpapicturesMac 2.66 GHz Quad Intel Xeon
OSX 10.6.8
FCS2
CS5.5
8GB RAM
ProAvio 8TB RAID 5 Dual Mini-SAS
Blackmagic Intensity Pro
ATI Radeon X1900
RocketRAID 4322 via dual MiniSAS
Panasonic Lumix GH2, Canon 5DMKII, 7D, Panasonic HVX200A, Panasonic DVX100A