Mark Krueger
Forum Replies Created
-
Mark Krueger
April 15, 2019 at 4:40 pm in reply to: Black Magic Intensity Pro not working with adobe premiereThanks David, I was able to download the 2018 Premiere , acutally that was pretty easy. With the creative suite you just click on the small arrow next to the open button and it allows you to open different versions. But even going back to the 2018 version the Black Magic did not work.
So I uninstalled the Black Magic and then used an older version of that … version 10.11.4 and YEAH!!!! it worked.
Two days of headaches, but I finally got some progress! Thanks again for your help… it made me think to get older drivers for the BM.
Hope this helps others Mark -
Thanks so much for clarifying this situation!
-
OK… Making much more sense to me…. I will let you know if I need more help… Thanks sooo much!! My next question is exporting settings… I don’t know if you are able to help here, but I know there is a bit rate settings to make for exporting, not sure what setting I should use for a bluray quality. Any help or advice would be apprecitated. Mark
-
Greg… I cannnot find where I can create custom presets for 4 channel audio… Can you give me a few directions or send some links to good tutorials on this. Thanks Mark
-
OK Thanks so much for taking the time with my questions. I am new at Premier and also with 4K so it is nice to get some help with specific questions. I will try out your suggestions. But I did not find the attached footage you said you included… maybe I am missing where to find this attachment.
You mentioned that I would probably not see much if any loss in quality if I keep the zoom to less than 120%. The zoom scale in the effects panel goes all the way to 200%. With a 4k clip in a 1080 sequence zoomed to 200% I am assuming I would not like that final export? Correct? -
Thanks Greg. I will give that a try!
-
Thanks so much Jeff…. Just to clarify… if I drop my 4K footage into a new sequence it will automatically make that sequence a 4K sequence. So I need to create a new sequence for 1080p before I drop in my first 4K clip. Then set to frame size for each clip. Viewing the effects panel for that clip I can see the scale which should be something less than 100% and I can then scale without loosing quality.
When I drop a 4K clip into a 1080 sequence I get a red line above the sequence…. do I need to render that before I can work on the clip?
If I use a 4K sequence, and use 4K clips… when I zoom in on the clip will I loose resolution quality if I export out to 1080? -
Thanks for the fast response! I shot in 3840 only to be able to zoom in on footage and not loose resolution. As far as I know there is no export that is 3840 only 1080? No UHD drives that I am aware of. And if there are, I don’t think I could afford them yet. So If I set my sequence to 1080, then I would need to scale the clips or set the clips to frame size. Which one would give me the ability to zoom in and not lose resolution. Also do you know, if I do not set the sequence to a particular frame size will it automatically use the first clip I put in as that resolution?
-
Thanks to all for your input on this question. I am still playing with it using your suggestions. At this point I think the best results I have had is using AE to capture the waveform and rendering that to a AVI file and using PIP of that footage in my video. I also tried using Chroma Key and other ideas. John, I am still working on your ideas, but I am having trouble making the waveform appear to be “live” using track motion, maybe you could explain that a little more. BUT THANKS TO ALL WHO TOOK THE TIME TO HELP! Mark
-
In an earlier post I indicated that the timecode appeared to be fixed with the new build. I take that back! I must have been using SVP 11. Here are two screen shots. They both are showing the same two clips on the timeline. Notice the timecodes at the end of clip one and the start of the second clip. In Vegas 11, They show a continous timecode. In the new build of Vegas 12 the timecodes start at 0 for each clip. According to the release notes that should have been fixed!

