![]() You're right, there is no such thing as 16/32. If it started using 12/32 for whatever reason, that's just bad luck (and you guessed it, they are ALL known to have compatibility problems). The default on cameras - consumer or pro - is supposed to be 16bit/48kHz. (Like, is it some kind of deterministic compression like gzip, where it doesn't matter what machine does it, or is it sort of a "secret recipe" kind of decompression, where a good editing program might result in a better quality final sound than whatever WMM is doing on the fly.)Īnother possible explanation that occurs to me is that it could just be user error- like, maybe looking at what VLC or QuickTime say the codec is, isn't what I'm supposed to do- maybe I'm supposed to look, say, in a video editing program to see what it says about these imported clips.Īnyway, if I ever figure out a definitive answer to what the story is I'll update here- or if anyone else has any insights what the reason is for this discrepancy I'd love to know. I still would like to know for sure so I don't have to keep feeling like maybe my captures (and I'm doing a lot of them) are all bad and will need to be redone. ![]() I do remember reading somewhere that the 32 kHz / 12bit audio on MiniDV cassettes is compressed, and the 48kHz/16bit isn't, so maybe it's just the exact same stream uncompressed. The theory that it's decompressed already, doing a conversion I'd have otherwise have had to do myself, also makes a lot of sense. and maybe my WinDV captures were OK all along. At the time I thought that was a bug in WinDV but now I'm wondering if there is some kind of correctness about it, since both WMM and WinDV appear to do it. ![]() Interestingly, I looked back at some of my WinDV captures from last year, and I see the exact same thing with WinDV- the 32 kHz files all say the audio is 16 bit, even though I know 32 kHz / 16bit isn't supposed to be a legal DV audio format. dv stream files, and as yet the only one I'm aware of is Enosoft (which I haven't yet tried.) I still haven't managed to capture a 12 bit file and attempt the conversion myself- I think to do that I'd need a Windows based tool that can save raw. I realize 32 kHz / 12 bit may not have been common in higher end production, but consumer level dv cameras like mine, inexplicably made that the default audio mode, so for people like me who didn't at the time know to change it, it was common. (PS, I should add, sometimes the audio doesn't sound right in VLC, but so far all the movies I've captured sound fine in Windows Media Player.) (The Digital8 tapes, where I used 48kHz/16bit, all do say 48kHz/16bit in the codec description.) Is this OK? Why would it say 16bit instead of 12bit, if the tape's audio is supposed to be 12bit? The audio doesn't sound bad or anything, but I'm still a little unsettled by why it says 16bit on the capture instead of 12bit. But most are the more common MiniDV, with the more common 32kHz/12bit audio.īut what I don't understand is, when I look at what codec is on the captured audio (i.e., using VLC), it reports 32kHz/ 16bit for the audio of my MiniDV tapes. Some of my tapes were 48kHz/16bit audio, in particular most of my Digital8 tapes. One thing that keeps puzzling me, though, and I was wondering if anyone reading this might know. It is a simple tool but it seems to be adequate for my needs (in fact I prefer simple.) Thanks By the way, when I looked at all the software StaticZ produces, NOTHING has been updated in a long time, not just Sound Siphon, at least from what I've observed looking at the website.I have been using Microsoft's Windows Movie Maker on my Win7Pro 圆4 laptop, and so far so good. So if Anyone who reads this, has any updated info at this point, would appreciate it. I needed to have a working compatible app to use when needed. I had no problems with SS, but since there has been no info about what's going on that's been released. (AppDelete example here) As I mentioned in a previous comment, I've purchased AudioHijack to replace Sound Siphon until further notice. I've had that happen with apps before and didn't find anything out until a year or two later. Considering that in years past, the developer was always responsive, and updates were very timely: makes me wonder if the company went under, or the developer passed away. Since the other poster has not provided any information, I'm assuming they haven't heard anything either. It's been a few more months, and the Sound Siphon website seems unchanged, and has no updated info regarding Big Sur support.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |