osa Posted January 13 Report Posted January 13 Getting requests a few times lately for files to be 1x continuous take no breaks and so far has not been a deal breaker. Is there a quick trick to make it possible if not in the recorder through a 3rd party app (short of pro tools etc)? Quote
Bouke Posted January 13 Report Posted January 13 I have a tool that can cat Wave files and patch / rename tracks while at it. (And yes, in RF64 Wave format, retaining all metadata.) Contact me directly if you want to toy. But why? Segmented files 'should' be usable for any editor. Quote
osa Posted January 13 Author Report Posted January 13 18 hours ago, Bouke said: I have a tool that can cat Wave files and patch / rename tracks while at it. (And yes, in RF64 Wave format, retaining all metadata.) Contact me directly if you want to toy. But why? Segmented files 'should' be usable for any editor. Great yes I would love to try it! I know, though I get it, so many questions like this about editors and refusing to be outside of their comfort zones for multitude of reasons so I just give up trying to use force. All I could do is give them everything and hope for the best. i have some who insist on starting with my multitrack files and others who insist on camera audio only and my files are emergency backup. I educate where i can but ultimately I aim to please. Quote
Doc Justice Posted January 13 Report Posted January 13 As far as I'm aware, WildTrax is the only recorder that allows for custom file splits by size (example: 4gb, 10gb, etc.), duration (example: 10 minutes, 1 hour, etc.), or by a combination of the two. Quote
osa Posted January 13 Author Report Posted January 13 Someone correct me if I’m wrong, but I believe Sound devices recorders do it which was an example they gave in their spec sheet Quote
Conor Posted January 14 Report Posted January 14 4GB is an actual limitation written into the the WAV format itself, RF64 was created to allow for longer BWF files. If the recorder doesn't support RF64 it won't be able to do it Quote
Bouke Posted January 14 Report Posted January 14 RF64 is the 'new' WAV format. Even the extention is the same. And it goes back to 2007, (EBU – TECH 3306-2007) that is now almost 19 years. So there is absolutely no excuse for soft- nor hardware NOT to support it. It's just a small chunk saying "I'm RF64, so the DATA chunk might be larger than can be described in 32 bits." Splitting files 'might' be a way of securing parts in case of a crash, but since the header is in the front, and the metadata 'could' be in the front, there is no real risk of loosing data on a power failure or alike. Only thing missing in the file would be the total datasize description, and that is a very easy fix. (So 'custom size splitting' is marketing lingo, has no real purpose imho.) Quote
osa Posted January 14 Author Report Posted January 14 I put in a note to Howy to see if Zaxcom might offer this in the not too distant future. Quote
Bouke Posted January 14 Report Posted January 14 I think the problem isn't the RF64 format, but the hardware that has to support exFat formatting or alike. And, except for clients being stupid, there is no 'real' need as file segmenting gives the same result. Did you toy with my work already? Quote
Patrick Tresch Posted January 14 Report Posted January 14 EDIT: my statement is false... sorry On the Sonosax SX-R4+ you can change your card formatting from Fat32 to another formatting format and hence change the GB length of your file. I bet you can also do it on the Zaxcom. Quote
The Documentary Sound Guy Posted January 14 Report Posted January 14 2 hours ago, Patrick Tresch said: On the Sonosax SX-R4+ you can change your card formatting from Fat32 to another formatting format and hence change the GB length of your file. I bet you can also do it on the Zaxcom. You'd lose that bet. But, it might be technically possible for them to automatically merge segmented files when output using their ZaxConvert utility. That would be a worthwhile ask. Quote
osa Posted January 15 Author Report Posted January 15 13 hours ago, Bouke said: I think the problem isn't the RF64 format, but the hardware that has to support exFat formatting or alike. And, except for clients being stupid, there is no 'real' need as file segmenting gives the same result. Did you toy with my work already? Didnt get to test today but gonna try after tomorrows intv’s. Will report back! Quote
Patrick Tresch Posted January 15 Report Posted January 15 12 hours ago, The Documentary Sound Guy said: You'd lose that bet. But, it might be technically possible for them to automatically merge segmented files when output using their ZaxConvert utility. That would be a worthwhile ask. Hello, I think I made a confusion... It's on my camera that I can change the formatting method... sorry for the false statement. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.