Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
23
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by darkflame23 -
Yes, thanks Case, it was my brain fart, sorry...

Is there a way to get the "LUFS" text removed from the end of the LUFS scan results/readouts? I just want the number as the LUFS text is already the Column header in my Playlist, and it takes up a lot of unneccesary room.
25
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
Like I said in the earlier post, you are not using the context command that scans for the clipping information. Historically this component only scanned True Peaks and optionally True Peaks and clipping info + peak positions (that's why there are the different context entries for them). Then feature requests popped up and I didn't want to fill the context menu with all the different modes, so all extra scan modes were toggles in the settings.

If you want the clipping info, you need to use the context command "Scan True Peaks and positions...".
27
Scientific Discussion / Re: Are complex-input FFTs really useful for audio analysis?
Last post by TF3RDL -
Also, I think this topic is little bit de-railed; it went into performance improvements of multichannel audio spectrum analyzers by using complex-input FFTs, which is true considering calculating two or more FFTs can have significant performance impact. But what I really mean is that is complex-input FFT as in spectrum of I/Q signals in SDR really useful for analysis of stereo audio, which is basically the same minus the "unscrambling" operation?

I don't see any reason you would want the scrambled output when you could have the regular unscrambled one instead. 
Perhaps, it could be a different (but possibly novel) way to visualize stereo audio spectrum (higher amplitude on one graph than other means closer to 90 degrees out-of-phase on certain frequencies, as opposed to full 180 degrees out-of-phase as in traditional L/R spectrum analyzers), where two differently-colored graphs represent magnitude part of complex-valued FFT; the first one is as it is, and the second one is same as the first, but the order is flipped since the input to the FFT data is complex-valued, thus not symmetric in the full FFT output and to be able to visualize complex-input FFTs with the frequency range of 20Hz to 20kHz and a logarithmic frequency scale
29
Scientific Discussion / Re: Are complex-input FFTs really useful for audio analysis?
Last post by saratoga -
Also, I think this topic is little bit de-railed; it went into performance improvements of multichannel audio spectrum analyzers by using complex-input FFTs, which is true considering calculating two or more FFTs can have significant performance impact. But what I really mean is that is complex-input FFT as in spectrum of I/Q signals in SDR really useful for analysis of stereo audio, which is basically the same minus the "unscrambling" operation?

I don't see any reason you would want the scrambled output when you could have the regular unscrambled one instead. 
30
3rd Party Plugins - (fb2k) / Re: foo_uie_lyrics3
Last post by ngs428 -
Anyone else see large random negative offsets being put in sycnched lyric files with V0.6. I think it happened with previous versions too.  If I remove the large offset, can be somewhere around -78000, then the lyrics are prefectly synched.  So it seems to be put in in error.  It seems to happen comtinuously for a while, then it goes back to working fine.  Lyric sources are from MusixMatch or Deezer. 



As a follow-up, this only happens when I manually search for lyrics. Right click - Lyric Search...

Anyone else see this random offset be applied 75% of the time. It can be a large positive or negative offset.  Just got a [offset:-86000]