Jay Bloomfield
Forum Replies Created
-
The measurements are shareware and if you like my work, you can donate to my PayPal account. 😉
-
I’ve never checked playback of the DNxHD MXF files via SDI out, but they do play back via HDMI out. Before they updated the firmware to also output DNxHD MOV files, that was the only way that I could pull anything compressed off the device (no Avid MC here). I used my Intensity Pro as a stopgap to capture the output via HDMI.
I think that there may be an issue with mixing and matching different file types and maybe that is the problem. I know you can’t mix 1080i and 720p and expect to be able to play both back. Maybe you can only play one file type (MXF, unc. MOV or DNxHD MOV) at a time also. I think that the Hyperdeck Utility setting determines what can play back. Just speculating though.
-
15.6 cm L
11.1 cm W
3.1 cm H (or 3.8 cm H with optional mounting plate)Note: these are the measurements (they could be off by a hair) of my Hyperdeck Shuttle 2 and you’re right, the BMD website doesn’t have any official measurements.
-
Jay Bloomfield
February 22, 2012 at 10:23 pm in reply to: INTENSITY PRO – recording on DVCPRO device material from hard diskIt should show up under “Sound, Video and Game Controllers” as two items:
1. Blackmagic Driver
2. Blackmagic Audio -
I doubt that this will help with those issues, but the most recent version of the codec is 2.3.7:
https://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=423319
-
Jay Bloomfield
February 17, 2012 at 7:53 pm in reply to: New HyperDeck 2.5 Beta software available now.Thanks. That helps a lot.
-
I’ve been using Crucial C300s (240GB) and they work like a charm. I bought a newer-technology VoyagerQ external single SATA drive enclosure from B&H (I’m using the USB 3.0 connector) and it makes for a convenient way of transferring files.
I would stick to the approved list of SSDs (the C300 is on it), though if you don’t feel like taking a chance.
-
@Kristian Lam,
I’d rather see Cineform as the codec with a MOV wrapper, but anything other than the DNxHD MXF op-atom file format, would be better for us non-Avid users. Another possibility would be to have BMD work out something with Calibrated, so that Calibrated would sell its MXF importer separate from the various decode bundles (which are not needed since the Avid QT codec is freeware), maybe in the range of $50-100 US. Unfortunately, even THAT option is considered a beta by Calibrated for the Hyperdeck DNxHD MXF files, though. I tried the demo version of the Calibrated MXF Importer with the Shuttle MXF files and it seemed to work, although you end up with 3 separate files to fool with in PPro5.
It’s too bad that the open source ffmbc doesn’t work with the op-atom MXF format either. Right now, all I can do is use my Shuttle 2 in uncompressed mode.
-
If you search this forum, you will find a few other posts about Intensity Pro cards not working in certain motherboards. Unfortunately, almost all of the information relates to Intel-based mobos, so it may not be helpful at all to you. However, the one thing that you can try is to boot your system and go into the CMOS setup. Often the BIOS will have a specific setting that tells the computer to look for video cards in a certain order. It usually looks like PCIE1–>PCIE2—>PCI, etc. If the motherboard has it’s own built-in graphics, make sure that it is disabled.
First write down what that BIOS setting is, but don’t change it. Turn off the computer and see what PCIe slot the Intensity Pro card is in. Your best bet is to put it in the short PCIe 1x slot, if you have one. Else, experiment with moving it to one of the PCIe long (16x) slots, but do not move your video card from it present slot. Make sure the card is well seated in the slot and also ground yourself when handling the IP, so you don’t destroy it with static electricity.
If all that fails to make the system boot properly, try testing the Intensity Pro in another computer. The card could be faulty. If none of that works, try opening a support ticket with BMD. They are usually pretty good about hardware issues.
-
You need to isolate whether the problem is with the capture or just the playback. What do various codec “appliances” such as GSpot or GraphEdit tell you about the codecs being used to render the file? Did you use the BMD MJPEG codec to capture? Is the result the same using uncompressed as the capture option? Which media players and NLEs have you used to play back the files? Do they all playback the files at double speed?