I'm playing with 4.x and was curious about a couple of things regarding audio.
Since the recommended sample rate is 192kbps what happens if I tweak a sequence from last year that played on my FPP (different sample rate) and the audio is still loaded on the FPP.....can I use that old audio with the tweaked sequence or will I need to replace the audio with the 192kbps file?
Here's another one that's even more confusing.....Using HLS, as I do to run my 'army' of wireframe that uses dumb strings....I am required to use a .WAV file for the audio......Now, that being said, I can use an mp3 but Joe turns around and converts it into a .wav file so that he can generate a PCM file for the music. And .wav files have an entirely different sample rate than 192kbps (instead the .wav is like 1411kbps).
So if I drop an effect generated in XL that 'likes' a sample rate of 192kbps when I drop it into my HLS sequence will the 2 match?
Thanks for any comments....
SC
A small mixing of apples and oranges is going on here.
A sample is the value of the changing waveform, much like taking a multimeter reading. it is valid right now but as time passes, you will want to take another sample soon. CD quality a Redbook Standard, specifies the audio is sampled 44,100 times per second. Each sample is 16 bits per channel and 2 channel stereo. If you do the math not counting parity error corrections etc, just the data on a CD is 44,100 samples 32 bits in size. I you stream it out this produces a fast data stream of 1411200 bits per second. This is for UNCOMPRESSED raw wav audio.
MP3's use compression and data is streamed. Since not all bits are sent due to compression ( it is lossy ) most bits are not sent. MP3's have a data bit rate. More bits per second, the more of the original wave is recreated. 192000 bits per second is still highly compressed compared to the original raw data.
The term 192K is not a valid sample rate, but is a common bit rate. That bit rate can be valid for sample rates of 96K, 48K, 44,1K 22K or other sample rates.
Due to the compression algorithms used, some time is required to decompress audio and most sequencer software does not account for the delay as it varies on different processor and operating systems. This may cause music time shifts when played in relation to the time line and the waveform shown on the line. Wave is preferred for sequencing where you want light events smack on the beat.
Follow your sequencer recommendations. Changing bit-rates will affect the quality of the sound, not the speed. It can change the delay. Be aware of the degradation each time a lossy compression is re-compressed to another bit-rate. It is best to re rip from the original CD to prevent quality loss changing bit rates.
I would be fine using wav files but since the FPP uses mp3's it sort of short circuits that.
Actually, since HLS uses wav files I considered not using the FPP so as not to compromise my sound quality. But after a little testing I found that while I might hear a small difference on a good stereo system between the 2 but in my car....out in the yard....watching the display....heater running..... I can't tell a difference.....
I did find out that without sampling at the 192 rate one of my old mp3's from last year wouldn't work with V4.x....had to resample it.....or render it or whatever term is proper....maybe it was changing bit rate to 192....... I don't know all the technical ins and outs and the terminology is confusing....just trying to prevent a problem....
There is more to this story, it's not the 192k bit rate that FPP use's. The issue was that Amazon D/Ls are a variable bit rate and Sean was taking them into Audacity and resaving them as a 192k "fixed" bit rate. The 192k isn't the issue. It's changing the mp3 from a variable bit rate to a fixed bit rate. As the variable rate didn't stay synced with the sequencing software. I save mine at the 256k fixed bit rate. I used to rip cd's at 128k fixed bit rate. Both will work fine because they are a fixed rate.
Skunberg wrote:There is more to this story, it's not the 192k bit rate that FPP use's. The issue was that Amazon D/Ls are a variable bit rate and Sean was taking them into Audacity and resaving them as a 192k "fixed" bit rate. The 192k isn't the issue. It's changing the mp3 from a variable bit rate to a fixed bit rate. As the variable rate didn't stay synced with the sequencing software. I save mine at the 256k fixed bit rate. I used to rip cd's at 128k fixed bit rate. Both will work fine because they are a fixed rate.
That's interesting....and explains the Amazon piece.....
I know how to tell what the bit RATE is.....but how do you tell if it's "fixed" or "variable" bit rate?
Depending on your OS and/or your media player, check the Properties of the file. Often this data is listed. If using Windows, play the file and view the property of the currently playing file.
Attached is a screenshot of a Linux media player displaying the properties. It shows both the sample rate and bitrate. If it was a variable bitrate file it would indicate that. I believe Windows Media Player does the same thing. Note the file I used for the example is not stereo.
Technician wrote:Depending on your OS and/or your media player, check the Properties of the file. Often this data is listed. If using Windows, play the file and view the property of the currently playing file.Attached is a screenshot of a Linux media player displaying the properties. It shows both the sample rate and bitrate. If it was a variable bitrate file it would indicate that. I believe Windows Media Player does the same thing. Note the file I used for the example is not stereo.
Ahhhh....Windows media player.... I had that thing set to NEVER open....the logic of that piece of garbage player is so convoluted that I'd almost rather take a beating than use it......
But if that's the only way to tell...I suppose I can tolerate it long enough to find what I'm looking for....
Thanks for the info.....it might save me some head scratching later.....
Well.....after spending 15 minutes of pure frustration in WMP......I gave up.....that is the most maddening piece of software I've ever tried to use......well, maybe PhotoShop would give it a run for it's money..... :unsure:
In xlights 3.6 we did not display the sound waveform. The library we used supported ogg,MP4,MP3 and wav. When Dave Pitts wrote the waveform display he opened the MP3 files and read its entire content into a buffer. He then displayed the waveform, created ability zoom .etc.
When you click someplace into the waveform we need to tell the mpg123 library to start playing there. Example, click at 10 seconds and press play. On orig Amazon MP3 files even though we said 10 secs, actual playback was around 8-9 seconds. If u just open the Amazon files in Audacity and do a export audio, it fixes the problem. That new file (default 192 constant but rate) now will start playing exactly at 10 seconds. The issue for supporting wav files is we need to write the code for reading data into a buffer to display the waveform. It is on the todo list, it is not high on the priority list. Just open wav in audacity export audio as MP3. With a 15second workaround, that you only need to do once it won't bubble higher than many of the current 100 open issues/enhancements.
Thanks for the explanation Sean....it helps to understand the why. Those of us not in the development side of things just don't realize some of this stuff and by hearing about it that helps us know what to expect and to not try and get the software to do things it wasn't designed to do.....which is probably where most of my issues originate...
Slightly off topic. I second the Windows Media Player comments. Is Win Amp still around? It displayed bitrate by default. As you can tell by my screenshot, I don't use Windows Media Player either. I just checked, my screenshot was Movie Player, the default media player in Linux Mint if anyone cares.
Back on topic, Falcon does not use Wave due to the large file size. It would require a huge bitrate from the thumb drive. That overhead could cause buffering problems as it pushes the transfer limits on some thumb drives.


