Type: New Feature
Affects Version/s: 13
Fix Version/s: None
Recordings Module 22.214.171.124
To reproduce when adding a New recording:
-Upload a high quality test audio file such as a mono 48KHz WAV, SLN48, SLN16 or G722
-Select ULAW, G722, WAV, SLN16 as the convert formats you want
-Go back into that recording and hit save again with ULAW G722 WAV SLN16 selected
At this point, it has recreated all the file formats using the 8000Hz WAV as the source, so the G722 and SLN16 will now sound horrible (8000hz)
To reproduce when making a Compound recording:
Create/Add a new recording
-Add 2 system recordings that are pre-existing in g722 format such as vm-login then vm-sorry
-Upload a high quality 48KHz WAV or g722 custom file as the third file
-Select G722, ULAW, WAV as the convert types and hit save
It has just overwritten the 16khz system files vm-login.g722 and vm-sorry.g722 with new converted versions that were sourced from 8000hz vmlogin.wav and vm-sorry.wav
Ideas to fix this:
---Don't convert a file/format if it was pre-existing, only convert newly uploaded files.
-Always use the highest quality format as the source when converting instead of defaulting to the pre-existing .WAV which is likely 8000hz. ie. use the following formats as the source in order SLN48, WAV 16khz, SLN16, G722, WAV less than 16khz, ulaw, gsm
-If the file is a newly uploaded file when creating this recording, use it as the source.
-Add indicators beside each file added to the recording indicating what formats that file is available in on the server
I have a fear someone will modify a compound recording that is all g722 and hit save and after all that work it will covert them back to 8hz quality inside g722.