Wickham Strub
Forum Replies Created
-
Hi Peter,
First thing to note is that DV comes in through the Mac’s FireWire port, completely bypassing all Media 100 Hardware. So… no surprise that it’s unaffected.
Second thing is, you’ve got HDx hardware. That means that component video in is only possible via the analog video cable bundle which plugs into the analog “mezzanine” card. It’s entirely possible that there is a problem with either the analog cable or the analog card.
You can try ‘jiggling’ the analog cable where it connects to the card and you can pull it off and check to see if the connectors are damaged. Other than that, there isn’t much you can do without another cable/card to compare and contrast.
~Wick
-
Sorry, but there’s no way that card is gonna work in that Mac.
There’s a whole list of reasons why, not the least of which is that the card you have is PCI card and you’re Mac Pro has PCIe slots. PCIe is two generations ahead of PCI.
To see what kind of stuff we (I’m the Product Manager for Media 100 these days) offer that WILL run in the Mac Pro, start at http://www.media100.com and give our sales dept a call.
~ Wick
-
Jim,
Did you get the email that I sent to you directly? The sooner I get the Activity Monitor Sample, the sooner my Engineers can take a look at it. I can’t promise a solution from it, but more information is always better.
~ Wick
PS – Does your DVD recorder support Component input? If so, have you tried going to DVD that way? I know it doesn’t explain why FireWire suddenly won’t work, but it may get your work done.
-
I agree, the increased machine noise should be the only potential “gotcha” with this plan. It’ll work fine, but the noise might drive you a bit batty. They were known as the “Wind Tunnel” Macs for a reason.
-
So… not to be a nitpicker but… this isn’t exporting, it’s playing out to tape, and it raises many questions.
– SD or HD?
– What codec?
– Are you simply playing the timeline or using Master to Tape?
– You write that it’s “after going to 13.0.1”, what version were you at before?
– With that “before” version, did this same workflow work fine? -
This just isn’t really the same thing. You’re playing out to tape, not exporting. It still shouldn’t crash… but it’s not the same thing.
I see that you also started a new thread so I’ll take it up from there.
~Wick
-
Send that report along to support at media 100 dot com. YOo can simply copy and paste info in the body of the email. Put my name, Wick, in the subject field so it catches my attention.
-
Try these steps:
1 – Quit M100
2 – Move the media
3 – Delete the media from the original location
4 – Launch M100
5 – Cancel Media Search for existing Project
6 – Close existing Project
7 – Create the New Project, setting the Media Destinations, Prefs, etc the way you need them to be
8 – Bring the Programs and Bins into the new Project (you can use the File>Open… method or drag and drop)
9 – Open them up one at a time, letting the media search do it’s thing
10 – Give it another go and see if you get the same results -
Hey Matt,
Looks like you’ve got a weird one here.
The “.rend” extensions are concerning because it’s not an extension that we (M100, that is) add to files. It makes me wonder what would happen if you started over with a new Project and completely eliminated whatever media drive you’ve been using up till now. I know Disk Utility “blessed” the drive but somethings not right.
~Wick
-
Good to hear that you’re back in business again.
Two things happened here.
1 – The hardware version of M100 (Suite) and the software version (Producer) share some system resources. Whichever is installed most recently, owns those resources and thus, the other cannot launch. It would be a problem if you NEEDED both on the same system but, as of yet, we haven’t figured out why one would need a hardware-based M100 and a software-based M100 on the same startup disk.
2 – The licensing scheme we use “remembers” the older versions you’ve installed and unlocked so, 9 times out of 10, there’s no need to re-register a version you previously had unlocked.
~Wick