[Studiotalk] Question Regarding Hindenburg File Storage

Nancy Gahagan nancy.gahagan at perkins.org
Mon Dec 30 12:32:11 CST 2024


Thanks to all who have responded either to the group or directly to me. I
am passing the suggestions on to our IT department. Sorry for the delay in
response. Most of it went to my Spam folder and I am now catching up
between holidays. Hope you all have a wonderful New Year!

On Fri, Dec 20, 2024 at 9:52 AM Andrews, David B (DEED) <
david.b.andrews at state.mn.us> wrote:

> I am not sure I can help much, but I am familiar with the issues.
>
>
>
> In MN9A we have 20 recording booths. They record stuff to, and store stuff
> on the cloud.  We had to get a 1 gig line, so we had adequate bandwidth,
> and responsiveness.
>
>
>
> We do not use Hindenburg for our basic recording. We use a program we
> wrote, and are in the process of writing its replacement.
>
>
>
> Hindenburg was designed as a stand-alone workstation product. It can’t be
> run from a network, but writing to a network should be ok. We don’t use it
> that way, we use it at the end of our process to prepare books for BARD,
> but everything is done locally.
>
>
>
> I would think you should be able to get your system to work, but you ma6y
> need to improve the performance of its parts, server, connection,
> bandwidth, and your network itself.  This is pretty detailed and messy IT
> stuff, and there is no guarantee, but it should be possible, I think.
>
>
>
> Dave
>
>
>
>
>
>
>
> *From:* studiotalk <studiotalk-bounces at islemail.org> * On Behalf Of *Nancy
> Gahagan
> *Sent:* Thursday, December 19, 2024 10:42 AM
> *To:* TBBS Recording Studio Info <studiotalk at islemail.org>
> *Subject:* [Studiotalk] Question Regarding Hindenburg File Storage
>
>
>
> *This message may be from an external email source.*
>
> Do not select links or open attachments unless verified. Report all
> suspicious emails to Minnesota IT Services Security Operations Center.
>
>
> ------------------------------
>
> This message was sent securely using Zix®
> <http://www.zixcorp.com/get-started/>
>
>
>
> Hi All,
>
>
>
> I am hoping for some feedback about some challenges we are facing in our
> studio in regards to storage of Hindenburg files both short term and long
> term.
>
>
>
> We use Hindenburg for the entirety of our process: recording, editing,
> markup and exporting the dtb. We have 4 recording booths and all of our in
> process books are located on a server. We access this server for all of the
> work we do. None of our files are stored locally on any computer. That way
> all staff and volunteers have access to the files from whichever station
> they are working from. We also store all of our completed projects on this
> server. It's a system that has been in place for many years even before we
> started using Hindenburg.
>
> Our current server is nearing retirement, and we are exploring storage
> options. This includes finding new storage for archival files and other
> material. But the primary challenge is how to store active Hindenburg
> sessions in such a way that recording, editing, etc. is not hindered. We
> find that Cloud storage has too many lag issues.
>
>
>
> So my question to the group is, how do you store your in-progress
> Hindenburg sessions? For those who use Hindenburg for the recording
> process, do you record to a Hindenburg file that is on a local computer or
> do you, like us, record from an external server? It would be most helpful
> to hear from studios that have multiple booths and produce large quantities
> of audio. We have considered storing directly on the computers at the
> booths, but it seems that would require either a way to access the internal
> storage of each booth computer from workstations elsewhere in the studio
> and via a VPN; or transferring each in-progress session to a cloud server
> at the end of each recording session, which would add to our already ample
> workload.
>
>
>
> Any suggestions about how you all manage all of this would be appreciated!
>
>
>
> Thanks so much,
>
> Nancy
>
>
>
>
>
> *Nancy*
>
> *Gahagan*
>
> (she/her/hers)
>
> Recording
>
> Studio Manager, Perkins Library
>
> Perkins <http://perkins.org/>
>
> School for the Blind <http://perkins.org/>
>
> 175
>
> N. Beacon St.
>
> Watertown
>
> MA 02472
>
> 617-972-7362
>
> [image: Perkins School for the Blind]
>
> [image: Facebook] <http://facebook.com/OfficialPerkins/>[image: Twitter]
> <https://twitter.com/perkinsvision>[image: Instagram]
> <https://www.instagram.com/perkinsvision/>[image: LinkedIn]
> <http://linkedin.com/school/perkins-school-for-the-blind/>
>
>
>
>
>
>
> This message was secured by *Zix <http://www.zixcorp.com/>®*.
> _______________________________________________
> studiotalk mailing list
> studiotalk at islemail.org
> http://islemail.org/mailman/listinfo/studiotalk
>




This message was secured by Zix(R).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://islemail.org/pipermail/studiotalk/attachments/20241230/0379eca2/attachment.htm>


More information about the studiotalk mailing list