Mont Sherar
Forum Replies Created
-
Hello Brian and thank you for taking the time to try and help me.
Re. system issues, I have repaired permissions, trashed preferences, and even just ran Onyx as you hinted to. But none of this has any bearing on the issue.Here are some better explanations.
If I start from scratch. Make a material. Texture/”load image” if it is any still image in any format it is applied to the material. But no matter the size, no matter the format, if it is a video clip, it comes in black and in fact will always display “texture error” as well if I try and render it out (with the video image). This is the same even if I put a .jpg and a quicktime movie in the same folder. The .jpg will be applied to my material but the video will display black and will not render. No matter the size or format.
I realize if I did the video as a sequence of stills, that might work but it must be possible to simply apply a perfectly good quicktime movie clip to a material as well.
The odd thing is, I have done this in the past with no problem but now this has reared its ugly head.
Any idea why no matter what video file is applied, C4d refuses to apply it to a material considering the details mentioned above?
Thanks again Brian for your time and effort in trying to help me :-)))
-
Could someone please help me with a related problem to the above. Running r13. Mountain Lion. Yesterday, textures that used video clips were fine as expected. Then today for some reason, they show up as “black”. If I try and reload the video clips into the texture, the same happens. If I try and make a new material, I can load any still image fine, but no matter what format of video clip, it only shows up as black. Can anyone guide me to what could be wrong? I even reloaded in an older file that had video for textures, that too is now black for those textures. I havent made any updates to the system software (such as quicktime) so I cannot for the life of me figure out what is going wrong here? Any help would be more than appreciated greatly 🙂
-
U r correct. Today 🙂 this has been changed recently from “”january” to Early 2012″ .. Hmmmm….
________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont -
VERY well said!
________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont -
This problem of the player not playing in the proper viewing window is definitely a pain in the bug ;-)))
What I have found is that switching between command 2 and 3 does work SOME of the time, but not ALL of the time – at least not on the first try every time :(.
So what I do now, is click on any show/hide icon in the “effects” menu area (titles browser, effects browser etc) then immediately click it off again. That works 100% on the first try every time 😉
________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont -
Hi John,
I couldnt agree with you more. We need a scrolling timeline without a doubt (and a host of other things lol).
Doesnt seem to be implemented as of yet anyway…________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont -
Great story, nice video, and man would I LOVE to own that lens!!!! ;-=)))))
________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont -
So 6 weeks on from the last update, you think it means a company with no present update makes you “worry” that said company will drop the program? Hmmmm… nuff said.
I think its reasonable to expect a QUALITY update, (which means TIME) than to just spit out a minor tweak in a short period – because here is what we’d hear in that case:
“Arghghgh is THIS all we get from this update????”””Plus it says right on the Apple site that an update is expected in JANUARY. It does not say WE ARE DROPPING FCPX. Why would they do that anyway?
Patience is a virtue.
But yes, I do understand the frustration of bugs. There are plenty for sure, but as others have pointed out, this is not V10, it is V1.
________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont -
Thank you for the warm welcome :-)))
I dont doubt your competence/expertise one iota, just pointing out that it seems there are a few “connection” issues (ie. anything related to the app not seeing or showing things that are definitely there) with the data structure itself, and not user error (as evident by these guys in the video whom are very savy to FCPX.
And you are 110% correct that because it is a new approach being introduced , there are bound to be plenty of user errors as well – me not exempt either ;-)))))
P.S. I’m not at all a “nay-sayer” I truly welcome the new interface and approach. FCPOS (Old School) was truly getting to be long in the tooth. OSX had long outpaced the app so a change was inevitable. Bugs or not, I’m willing to give it a fair shot – the future looks bright, and in the meantime FCPOS has not vanished from my machines;)
________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont -
Sure – that is correct.
Therefore it must be explainable by preferences or disk repair issues lol!
Point is, some things are not explained in simple solutions – we have to wait until they are fixed in a coming update because the problems lie within (bugs) within the app itself.
________________________________
Mont Sherar Photography
https://www.fotoblur.com/portfolio/mont