I'm sure this is the same as everyone else...but.
I use Resolve Studio and the HyperDeck pre-defined format to create multiple videos for the HyperDeck Shuttle HD (HDSHD). When I add them to an SD card, the then place the card into the HDSHD. There are no videos displayed. I then FTP into the device, and the files are all there under the "1" directory. I then do the same for YouTube, 264 Master and while all the files are on the card, the device recognizes none of the videos.
When I connect an ATEM Mini ISO Extreme to the HDSHD. The ATEM connects to the HDSHD, yet shows no videos.
After restarting Resolve, it finally creates one video which is recognized by the HDSHD, so one would think this is success...but no. I attempted to create more videos, yet the HDSHD does not recognize them (as a note, all the files play back on every other device).
To add insult to injury: If I FTP files to the HDSHD, I have to eject the card, and then reinsert it into the HDSHD so it can reread the card contents. And the plot thickens even more when I attach an SSD to the HDSHD. It appears the HDSHD can't read more than one file system at a time. To prove this, I took the one file Resolve created and then copied that file to the SD and the SSD. To ensure I could tell which file system the HDSHD read, I labeled the files sequentially from 1 .. 10. 1 .. 5 were on the SD, and 6 .. 10 were on the SSD.
When I powered up the HDSHD, it read the SSD and ignored the SD. When I removed the SSD, the HDSHD instantly read the SD card. If I reinserted the SSD into the HDSHD, I could not make it re-read the SSD until I removed the SD and then power cycled the HDSHD.
And of course there was more wierdness in the IP stack. I removed the HDSHD from DHCP and assigned a static IP. Everything seemed to work, except I could not ping the address just assigned to the HDSHD; yet the system seemed to be fine. When I started the HDSHD configuration software, it could not find the HDSHD. I had to insert the USB cord to attach to the device. I then reset the IP address to the same static address, yet the setup software could still not find the device until I inserted the USB cable again.
I then went to the ATEM Mini Extreme ISO and the HyperDeck tab. The ATEM could not find the HDSHD after I inserted the correct IP address. I reinserted the USB cable, and reset the HDSHD. It got a DHCP address and worked across the whole ecosystem. I then set a static IP and the unit still functioned across the whole ecosystem.
One device with so many issues. Was this rushed into the hands of users?
I use Resolve Studio and the HyperDeck pre-defined format to create multiple videos for the HyperDeck Shuttle HD (HDSHD). When I add them to an SD card, the then place the card into the HDSHD. There are no videos displayed. I then FTP into the device, and the files are all there under the "1" directory. I then do the same for YouTube, 264 Master and while all the files are on the card, the device recognizes none of the videos.
When I connect an ATEM Mini ISO Extreme to the HDSHD. The ATEM connects to the HDSHD, yet shows no videos.
After restarting Resolve, it finally creates one video which is recognized by the HDSHD, so one would think this is success...but no. I attempted to create more videos, yet the HDSHD does not recognize them (as a note, all the files play back on every other device).
To add insult to injury: If I FTP files to the HDSHD, I have to eject the card, and then reinsert it into the HDSHD so it can reread the card contents. And the plot thickens even more when I attach an SSD to the HDSHD. It appears the HDSHD can't read more than one file system at a time. To prove this, I took the one file Resolve created and then copied that file to the SD and the SSD. To ensure I could tell which file system the HDSHD read, I labeled the files sequentially from 1 .. 10. 1 .. 5 were on the SD, and 6 .. 10 were on the SSD.
When I powered up the HDSHD, it read the SSD and ignored the SD. When I removed the SSD, the HDSHD instantly read the SD card. If I reinserted the SSD into the HDSHD, I could not make it re-read the SSD until I removed the SD and then power cycled the HDSHD.
And of course there was more wierdness in the IP stack. I removed the HDSHD from DHCP and assigned a static IP. Everything seemed to work, except I could not ping the address just assigned to the HDSHD; yet the system seemed to be fine. When I started the HDSHD configuration software, it could not find the HDSHD. I had to insert the USB cord to attach to the device. I then reset the IP address to the same static address, yet the setup software could still not find the device until I inserted the USB cable again.
I then went to the ATEM Mini Extreme ISO and the HyperDeck tab. The ATEM could not find the HDSHD after I inserted the correct IP address. I reinserted the USB cable, and reset the HDSHD. It got a DHCP address and worked across the whole ecosystem. I then set a static IP and the unit still functioned across the whole ecosystem.
One device with so many issues. Was this rushed into the hands of users?
Thomas Klinect