Jay Bloomfield
Forum Replies Created
-
Freeware/shareware like ffmbc will rewrap files from MOV to MXF without transcoding, but it will not do DNxHD. It can do the reverse, however, which unfortunately is only somewhat helpful to you (see below).
There was another recent thread about this issue with Resolve, but since that time the Hyperdeck Software has not moved beyond the version 2.5 beta 3, so there hasn’t been any visible progress. I’m sure somebody will post here, if the problem is resolved.
In the mean time, you are better off leaving the Shuttle in DNxHD MXF mode and re-wrapping the file to MOV with ffmbc. The ffmbc command line has been posted on another video website and if you Google the proper keywords, you should be able to find the thread. That way you will have both wrapper types of the same file, so you can work in a variety of NLEs and other software.
Here’s example of what has been used for a ffmbc command line:
ffmbc -y -i Capture0001V.mxf -i Capture0001A1.mxf -i Capture0002A1.mxf
-vcodec copy -map_audio_channel 1:0:0:0:1 -map_audio_channel 2:0:0:0:1 -acodec
pcm_s16le -ac 2 -f mov Capture0001.movI’ve checked it with my Shuttle files and it works fine (and very fast, since there’s no transcoding involved). You can speed up the workflow by using any GUI that will work with ffmpeg as they also work with ffmbc, which is just a broadcast industry specific branch of ffmpeg.
-
“Comaptibility” is mostly a matter of speed and should only be a consideration with an SSD, when capturing uncompressed.
-
I’m guessing that there is an error in the INF file, which is part of the installation package that tells the installer what files to copy and what registry changes need to be made. My guess is that the unknown device entry is not for the Intensity Pro, but some other BMD hardware product. Since the installer doesn’t contain the file for the driver, the entry shows up in the Windows Device Manager, but doesn’t have a driver. Just a guess, but I’d bet that you could uninstall the device and nothing bad would happen either.
-
I have that device now also. Something like A/V Decklink …? It doesn’t seem to “hurt” anything.
-
That’s about as fast as you can expect from this type of setup. Except for copying immense files, that’s fast enough, though.
-
As an aside,I just wanted to update some information. The new version (0.7-rc7) of ffmbc (freeware, with donations accepted):
https://code.google.com/p/ffmbc/
will now read the op-atom DNxHD MXF files from the Hyperdeck series. I tried it out myself and ffmbc does work for rewrapping those files to MOV.
One advantage of recording with a MXF wrapper is that it not only works with Resolve & Avid MC, but when you use ffmbc to do a rewrap to MOV, those files work in AE CS5.5, unlike the native Hyperdeck DNxHD MOV files. You still have to open the audio MXF files separately or use ffmbc to mux the audio and video together.
-
Just because a file has a MOV extension doesn’t mean Resolve will display it in the list of files, even though it actually exists in that folder. The file must be in both a wrapper and encoded with a codec that Resolve will read. For example, Resolve just ignores DNxHD files with a MOV extension. It reads many other MOV files (Red, Cineform, H.264, etc.) with no problem. It will read DNxHD files in an MXF wrapper.
-
Just because SATA 2 is spec’ed at 3 Gb/s (~375 MB/s), doesn’t mean that anyone actually could get those transfer speeds in the real world. Also, BMD Speedtest reports in Mbytes not Mbits per sec. The speeds that you are reporting look a bit low for an SSD and somewhat below what I get with my MacDrive SSD and my USB 3 dock (190-200 MB/s). That’s probably due to the MacDrive layer.
You could try buying a SATA 3 PCIe card, but I doubt it would improve throughput. The only way of really knowing, would be to try temporarily reformatting the SSD as NTFS and see if there is a major increase in speed. If it gets a lot faster, the bottleneck is probably MacDrive.
-
Is the dock connected via SATA 2 or USB 2.0? In any case, do your Speedtest results match up with the read and write speeds reported by Windows Explorer via the copy command to another SSD? The reason that I’m asking is that many of the disk speed testing program bypass the OS and do direct IO to disks. This could lead to inaccurate test results.
If you have the MacDrive emulator (or any software that allows Win 7 to read and write HFS+ formatted disks) installed, it adds a layer of overhead to disk IO, so some performance loss is unavoidable. I have a newertechnology Voyager Q dock connected via USB 3.0 for my SSD and I get excellent performance under Win 7 x64. It’s not as fast as when I had the same SSD formatted as NTFS and connected via SATA 3, but it’s still pretty fast.
-
Maybe I’m missing something here, but don’t you just need one of those cheap, $40 analog DJ mixers? They usually take the input (red/white RCA plugs) from an audio device and let you voice over a microphone. Then you take the mixer outputs and plug them into the IP analog sound RCA jacks.