Waveform only generating in Chrome (mac)

  • Resolved Henry Cullen

    (@davethedrummer909)


    8 years ago

    Hi

    I am using AWS S3 for my audio, but I have set up the CORS config to allow the http requests to process the waveform.

    Waveform ARE generating but only viewable in Chrome (mac)

    The audio files are standard MP3s at 128Khz and are roughly 2min long
    The audio plays back fine with or without waveform, just the waveform does not appear in Firefox or Safari

    You can have a look here:

    http://drummer-dev.davethedrummer.co.uk/downloads/hydraulix-06

    Many thanks for any pointers you can give me, great plug in, thanks for putting it together. If I can just get this working it solves a big headache.

    https://wordpress.org/plugins/wavesurfer-wp/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author X-Raym

    (@x-raym)

    8 years ago

    Thanks for this detailed report !

    I confirm the issue just like you described.

    Weird.

    my php and jquery seems to work so I wonder if it is not an issue with wavesurfer-js.

    Can you please report your issue here on wavesurfer-js GitHub : https://github.com/katspaugh/wavesurfer.js/issues ?

    I think katspaugh can help us debug this.

    Tell him that you have backend: ‘MediaElement’.

    You can test (before to report) to switch var backend to ‘WebAudio’.
    https://github.com/X-Raym/wavesurfer-wp/blob/master/js/wavesurfer-wp.js#L47

    then, check, and go back to MediaElement, and make your report on GitHub to katspaugh.
    (but if it works, please tell me here too)

    Good luck !

    Thread Starter Henry Cullen

    (@davethedrummer909)

    8 years ago

    Thanks for the reply, I’ve posted this on the wavesurfer.js GitHub page

    I did try out var WebAudio as you suggested
    and I got nothing loading at all, just the buttons, but no audio or waveform

    If I get a reply that’s of use I’ll report back.

    Many Thanks

    Plugin Author X-Raym

    (@x-raym)

    8 years ago

    ok ! Hope a solution will be found !

    Plugin Author X-Raym

    (@x-raym)

    8 years ago

    According to katspaugh, this seems to be a problem with file encoding.

    I mark this as resolved as this is not an issue related to the wordpress plugin directly.

    Thread Starter Henry Cullen

    (@davethedrummer909)

    8 years ago

    I haven’t yet had a chance to try different encoding methods
    but I will.
    I guess that must be it, although I’m not doing anything particularly out of the ordinary.

    Thanks

    Plugin Author X-Raym

    (@x-raym)

    8 years ago

    Before reencoding your files, try to upload on your server files that are known to work with wavesurfer-js. Fom the code pen, you can try this one https://ia801404.us.archive.org/9/items/rad1993-09-09.flac16/rad1993-09-09D3T01.mp

    When you will probably have a more precise idea of the problem source.

    Thread Starter Henry Cullen

    (@davethedrummer909)

    8 years ago

    Hi
    I have now re-encoded my files to 192 Kbps using iTunes and everything is working fine in FF Safari and Chrome. I haven’t Checked IE but I think it’ll be OK.

    I took my 128Kbps files and converted them to WAV, then re-encoded them to 192kbps. (I’m not too worried about audio quality as they are preview tracks )

    The reason for doing this was to remove the subcode from the previous MP3 version, in case there was an error. Wav files do not carry a subcode.

    I haven’t checked other sample rates but it would seem that 128 is not supported so I would imagine anything below this is also not supported, or perhaps my encoding had errors as I did them in bulk using MP3 trimmer. I would recommend to test if unsure.

    I’m serving files from AWS S3 and using the WP AWS plug in and Offload S3 plug in, which are working fine, uploading my files to S3 on the fly. These files will work for wavesurfer straight away.

    If you want to use a custom folder on S3 to store tracks as opposed to uploading via the WP media area ( which will put files in the wp-content folder ) you must make the folder and it’s contents public or waveforms will not generate.

    That’s about it from me.
    if anyone has an update on the encoding issue please let me know.
    Thanks

    H

    Plugin Author X-Raym

    (@x-raym)

    8 years ago

    Thanks for the update 🙂
    I’m pretty sure 128 kbits/s is supported so I guess it was a problem with your original converter.

    Glad it finally works for you !

    Cheers !

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Waveform only generating in Chrome (mac)’ is closed to new replies.