twobob
commented
4 years ago The 300 cap is enforced per theme as "maxDuration" as far as I can tell. Seemingly it is just tested for as that in Themes.json or defaults to 300. passing a large file results in 'Unexpected end of JSON input' very often though if one doesn't use Redis
as for passing it wavs I just get Audiogram Error decoding audio file So hard to help there
Hello. I am a relatively novice developer, so forgive me if I ask basic questions. I have installed Audiogram on a virtualbox ubuntu server on a windows machine.
For a few weeks, this issue never surfaced. But starting a few days ago, most times I upload a .wav file, the program tells me the length of the audio is 48695.8 seconds long, regardless of the actual length of the audio. Occasionally, it will report the actual length, almost at random. I cannot recreate the conditions to ensure an accurate report (uploading a file that it gets correctly will cause it to return 48695.8 again) I am not sitting in front of the installation now, but if you could tell me what logs or information to help debug the problem I will upload them at earliest convenience.
My first question, is can I eliminate the 300 second cap in the .js? I don't plan to ever use audio more than 300 seconds. Then, where does it get this 48695.8 number from? Is it in probe.js or something related?