Hello
I have been using the BM Hyperdeck shuttle very successfully for some time - my workflow is very practical - I record direct to DNXHD MXF files on the hyperdeck, I then create a new numbered file in the Avid media Files directory and copy all MXF files from each unique Hyperdeck SSD to this directory.
Once this copy is done I open Avid which automatically scans and indexes this directory and it places an MDB database file into said numbered directory.
I close Avid and I rename this numbered directory to something like 'Hyperdeck-Disk-01"
I reopen MC - create a corresponding bin called "Hyperdeck Disk-01" and then drag the MDB file from the directory called Hyperdeck-Disk-01 into this bin.
Avid immediately populates the bin with all the MXF files housed in that directory.
This is a fantastic workflow -
It saves time because except for copying the files from the source SSD to the Avid media Files directory there is no import or transacode required and all my video is immediately available inside MC
In addition, by renaming the numbered file to an alphanumeric file Avid essentially locks this folder in the media files directory and so isolates the master Hyperdeck MXF files in a single directory
Because Avid wont place any render files in non-numeric directories - I now know exactly where the master hyperdeck files are stored and I can back these up on another drive with no render or other MC created files clogging up the process
Lastly it saves a ton of disk space as the original master MXF files are also the Avid files and so Avid doesnt need to create its own copy of these.
All in all a great workflow and this has been a great time saver and it keeps all the original source files neat and tidey and in a single place.
Except now I am on a 5 day production shoot and this hyperdeck linked camera is shooting up to 3 SSD's a day each 128GB.
And
When I try the workflow above when I try to play the MXF master files inside MC in the source window I get -
Assertion Failed: consumerDur >=0 File ..\..\player\match.c Line 3236 - Create Report, Exit Application, Continue, Debugger
If I hit continue I get:
Exception FATAL ERROR msg: Assertion Failed consumerDur >= 0, ..\..\src\player\match.c. line 3236
But only on some of the files- others play fine - I just cannot find a pattern.
So I have 3 * 128 GB SSD based dailies coming in each day that cannot be edited in MC - this is a serious problem in itself - because even though they have been shot in MXF format specifically for MC and they play very well on VLC Media Player they dont play inside Avid - which is actually where I would get the most value from them.
They do transcode inside MC - but even the transcoded files crash with the same error.
The interesting thing is that I have tried them as per the above workflow in MC5.5 and they work and play very well there -
I can also export them as DNxHD out of MC 5.5 and then import them into MC8.3 and this works
But here is the thing-
This completely blows the efficiency factor away - I now have to find the time to copy all 15 * 128 GB SSD's to an old MC 5.5 machine - export them all as new dnXhd Mov files from 5.5 and then
Copy all of these back to the MC8.3 machine and then import them
The time required to do this is measured in days not hours!
A 'fast import' for a short file is at least 20 minutes - and it now doubles the space used on the disk.
Also it blows away my previous confidence in the above workflow and I will be better served returning to tape and going back 4 years because MC8.3 is now unreliable and not to be trusted.
This is not acceptable when the client expects a professional service and you spend all their time copying, exporting importing etc. In order to meet the clients exectations we have to have absolute trust in our tools that is why we pay for them.
Lastly
I tried to search for consumerDur but found nothing so this suggests a new bug!
Any suggestions would be very valuable
Regards
Neil
www.effectivevideo.co.za
Hi Neil, I´m using a shuttle 2 myself, have you updated to the latest firmware , it´s comes with 4.2 from memory
Tomas
Thanks Tomas - I have also upgraded to this version sometime back - as mentioned the files play in VLC media player and work in MC5.5 but not in 8.3
What format do you record to?I have changed the Hyperdeck settings to shoot to DNxHD mov format - this seems to work inside MC - but I lose all the benefits as per my original post and it makes me lose fatih in my tools if they are suddenly not going to work
Hi Neil, will do a test with my FS 700 and 1080 50i MXF 185x tomorrow to find out how it works here, I´m currently only using Mov files and those works, in the same way as in your new tests, well.
Hi Neil, just made that fast morning test with 25p and 50i and it seems like you have found a small issue with 8.3 , I might also have found a temporary workaround for it.
So, the very first clip recorded to my BM device after the startup of the device or cam will give me this error when played out from the source viewer, this does not happen with 8.2.
Workaround is to manually do a recording of that first clip and check that the cam automatically switches on the device in recording mode the second time, I have it set to record when tc runs and all the following clips after that initial errored clip plays well in the source viewer.
My guess is that this has something to do with the codec header.
Reported upstairs together with errored media.
Thanks Tomas - I am glad you were able to reproduce the error and appreciate as always the active interest you take in assisting members on this board.
I took off the "record when timecode runs" option as I got used to not shooting to tape - yes I understand that recording to tape offers me a backup but there hasn't been a reason to record to tape as well - until now.
When I identified the error I got the cameraman to shoot to both tape and to the shuttle on days 3 -5.
Day 3 I shot to DNXHD mov files and these dont seem to have a problem and they "fast" import into MC8.3 without a problem.
I am now using MC 5.5 to export all the MXF files shot over the last few days to DNXHD as I don't really feel like going back to 8.2.
Don't suppose we will see a fix for this anytime soon? - Seems silly for Black Magic to go to all the trouble of including a convenient Avid option in their product only for Avid developers to break it!
Makes the time and money spent by BM redundant!
Once again thanks for your help here Tomas - it is greatly appreciated
Happy to be able to assist Neil
and, about this
adamsonn: Seems silly for Black Magic to go to all the trouble of including a convenient Avid option in their product only for Avid developers to break it!
Seems silly for Black Magic to go to all the trouble of including a convenient Avid option in their product only for Avid developers to break it!
The 4,2 version of the software was released quite a while ago from BM, maybe they need to update it as MC 8.3 is rather newly released
Same problem with Blackmagic Hyperdeck files here...MC8.3
I will check on this one for you adamson.......
Marianna
marianna.montague@avid.com
Hey Neil
I created a case and sent to Video support for you.
Case #
HTH and let me know when you heard form support.
p.s. Tomas - thanks foe the repo. as that made it easier to escalate.
Marianna: p.s. Tomas - thanks foe the repo. as that made it easier to escalate.
My Pleasure MM
Is there any update on this? It's adding a lot of time to my workflow not being able to just pull the clips in.
Nick
Nick: Is there any update on this? It's adding a lot of time to my workflow not being able to just pull the clips in. Nick
I found, and have posted, a workaround for this , in some initial thread about this issue
edit.. ok , so it was this one, just look above if this works for you
Cheers, I worked out it was the first clip but now it seems to be on all clips. They were all recorded manually on the hyperdeck, not started from a camera.
Nick: They were all recorded manually on the hyperdeck, not started from a camera.
They were all recorded manually on the hyperdeck, not started from a camera.
That was what I also found out, having my FS 700 autostart it and the files was possible to use when that was done, how about that , what are you shooting with , any possibilities to try my steps.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller