Andrew Mehta
Forum Replies Created
-
Andrew Mehta
April 20, 2007 at 8:57 pm in reply to: There’s too much to fix before you can take Media 100 seriously.Oh, hearing of this particular error doesn’t really bother me, as I don’t use machine sync or timecodes.
Prefer to just write what it is as a reel name, and then when I’m looking for a clip later, I can tell what’s what by the filename, and it’s not just a bunch of numbers.
Also I’ve got some knackered tapes, and it’s annoying when you play them, and it auto-stops on a broken timecode, but I usually switch to S-Video instead of DV, and the signal maintains.I was aware of the checkbox in 7.5, that dictates whether or not to stop at timecode breaks. I assumed it was lacking from Producer, the way Jim was carrying on. But perhaps the answer to his woes is only a tick box away.
And Thierry is right – is great to have a choice between systems. If I didn’t want Producer, I could just get a tune-up to 8.2.3, or maybe even an SDe. In the meanwhile Media100i 7.5 has ensured my brand fandom. Although I agree with what Nick Griffin said about colour correction in FCP, due to the stylistic efforts some of the other producers I know had adopted for their pieces, that have been difficult for me to emulate with my ICEfx/Boris/M1007.5 setup. Still, I gave it a good try, using RGB Balance and a subtle Glow….unfortunately, I have G4 rendering times. =P
…all the more reason to upgrade at some stage!But congrats on 11.6 and keep up the good work guys.
-
Andrew Mehta
April 20, 2007 at 5:08 pm in reply to: There’s too much to fix before you can take Media 100 seriously.Jim may rant like a git,
but for someone still using 7.5 XR and thinking about upgrading later in the year(and since my budget is weak, may have to go for Producer instead of HDe), it’s interesting to hear tell of some stuff that isn’t working properly in Producer.
However annoying you find Jim, I hope someone is making note, so by the time I’ve saved up enough for Producer Suite, all the bugs will have conveniently been ironed out. ^_^. -
Thanks for filling us in.
There was so much hype going around about NAB this year, and such a huge build up, I was surprised the M100 board suddenly went a bit quiet. Guess all the regulars were in Las Vegas partying or something. =PI heard about the AJA IO in all the FCP6 write ups. Would be cool if M100 supported it too…^_^…not that I have the money to upgrade atm, but, ho hum. ^_^. I like to think they match Apple blow for blow, even if UB did take a while…
What happened at the M100 Users Group?
-
Yeah, I figured, just like Media100i lossless was still compressed, you just couldn’t tell the difference.
I just wonder if M100 can match them blow for blow…and develop or support a similar codec, or if they already have one as good as Apple’s already?
-
Did you get my other message? Looks like the Media100 support website has both a full install update ( https://www.support.media100.com/KBSearch/kbDocument.aspx?id=396 ), or a patch update ( https://www.support.media100.com/KBSearch/kbDocument.aspx?id=394 ), so the choice is yours. Although fair play to waiting for official word from Scott.
-
Looking at the website again, it looks like you can choose between a full install or a patch:
Download KB000394 Media 100 11.5.1 Patch Update 11/17/2006 
This is a patch update (non-full install). This update will only update Media 100 11.5. An encryption code purchase is required to run Media 100 11.5. This update is not for Media 100 Producer. A full description of this updat … Download KB000396 Media 100 11.5.1 Full Install 11/17/2006 
This is a full install of Media 100 version 11.5.1. This version is an update to Media 100 version 11.5. A Media 100 11.5 encryption code is required to run this update. Please refer to the Media 100 Release Notes document included … -
Well…I was going to suggest installing on a second harddrive, to avoid having to uninstall 11.5, but when I actually hit the link Scott gave you, the page says it’s a Patch Update, and *NOT* a full install.
In fact it says:
This is a patch update (non-full install). This update will only update Media 100 11.5
https://www.support.media100.com/KBSearch/KBDocument.aspx?id=394
Why not try it and see? -
I’m still using 7.5 myself, and haven’t worked with 8.2.3a yet, so the following suggestion is just a blind guess – but how about opening a new project in 7.5 then going to FILE>>IMPORT, and then browsing to your program and bins directory, and importing them in? (You’ll need to set the TYPE Dialogue from Media100/Quicktime, to “All” in order to see the program and bin files). If the programs and bins haven’t changed, they ought to still be 7.5 friendly.
I don’t have any experience with 8.2.3 or with CG Studio, so I’ll leave the rest for other people to answer. And like I said, the above is just a guess – dunno if it’ll work or not, but perhaps worth a try.
-
My point of referencing the other thread was to ask if it might be another track besides V1 that might be rendering opaque black and not letting V1 show. Try getting rid of any unused tracks in the boris timeline (unused text especially, but also any unused background colour tracks). Take another look at all the options on the V1 track also incase a setting is obscuring it upon render, maybe even try getting rid of the V1 track from Boris altogether, and putting the V1 video beneath your boris clip/graphics clip in the M100 timeline instead.
If none of these ideas work, then I’m the wrong person to answer your question, as this is where my limited experience ends.
Floh is the expert on these forums, and saviour of all…hopefully he’ll reply with wiser words of advice than I can give. Or else someone else may chip in?
Btw…Is this problem just when creating a graphics clip in the graphics track, or is it a problem for composition clips in the video track too?
-
Andrew Mehta
March 25, 2007 at 4:44 pm in reply to: There is a problem with Media 100 & After Effects. A real problem! BEWARE!Not just the wrong field order?
I use Media100i 7.5 and After Effects 5 both in OS9, and have no problem. But I have seen similar lines when I imported a quicktime movie into M100 once with the wrong field order.