Is there any way to detect when a morse audio has ended? What I want to do is to change the class of a button after the audio has ended. Thank you

Is it possible to send HTTP requests to https://morsedecoder.com/ with content and get the encoded value?
If it's not possible, is it possible to add it as a new feature to the site?

const oscillator = offlineContext.createOscillator();
                                      ^

TypeError: Cannot read property 'createOscillator' of null

I can't resolve this error, something can help me?

This is a weird bug that I found recently. I have not had a chance to try it on a MacBook or an emulator, but I tried with both iOS 11 and iOS 12 in Safari Mobile and I still could not figure it out.

If you click to the Play button, not only you may not stop it from playing, but also you may not make it play more than once.

You can find an example and test it out on JSFiddle.

Note: There are many Stack Overflow issues like this for reference.

Example Issue 1
Example Issue 2

Hi @ozdemirburak
When i am clicking first time on the playicon then the audio has been start playing but as soon as i am clicking again to pause the audio it showing me this error "Failed to execute 'stop' on 'AudioScheduledSourceNode': cannot call stop without calling start first."

I am unable to understand what i am making wrong. Please help some one.

const morse = require('morse-decoder');
const togglePlay = (event) => {
      const audio = morse.audio('My Text');
      if (event.target.className === 'playicon') {
          audio.play();
          event.target.className = 'pauseicon';
      } else {
          audio.stop();
          event.target.className = 'playicon';
      }
  }

<div className="playicon" onClick={togglePlay}></div>

Currently, there is only one typescript file, index.ts.

To split the logic, you can create files like:

• characters.ts
• audio.ts

You have correct icons but wrong labels on it.

7 rakamının görsel açıklamasında hata var.

Thai alphabet characters are missing, someone who knows Thai can implement it.

You can add the Thai Alphabet after the Korean one.

'12': { // Thai Alphabet => https://th.wikipedia.org/wiki/รหัสมอร์ส
  'ก': '110'
}

Wikipedia Page as the Source

Currently, the library misses a feature that is a bit challenging: exporting the Morse code audio to WAV.

Not sure how to do this effectively, but the gist below clearly shows how to create WAV from the buffer, which may help in the beginning.

Link to the Gist

TypeError: Cannot read property 'createOscillator' of null
at Object.audio in morsify/src/morsify.js — line 192

Currently, there are two variables that control the sound - unit and fwUnit. And these confuse most users about the Audio generated.

Instead of these two, taking PARIS (50 units) as the standard word (60 seconds / 50 units = 1.2), a WPM parameter for an end user would be better.

Here is a great resource on this: https://www.morsecodeclassnet.com/ch3-timing/

Other than this, the current default frequency value is 500, but a more common value would be better.

Lastly, a volume parameter can also be added.

Here is the expected output:

 const options: Options = {
    ...opts,
    dash: opts.dash || '-',
    dot: opts.dot || '.',
    space: opts.space || '/',
    separator: opts.separator || ' ',
    invalid: opts.invalid || '#',
    priority: opts.priority || 1,
    >>>>>>>wpm: opts.wpm || 20,
    >>>>>>>volume: opts.volume || 100,
    oscillator: {
      ...opts.oscillator,
      type: opts.oscillator?.type || 'sine', // sine, square, sawtooth, triangle
       >>>>>>>frequency: opts.oscillator?.frequency || SOME_ANOTHER_VALUE, // value in hertz
      onended: opts.oscillator?.onended || null // event that fires when the tone has stopped playing
    }
  };

Although there's a decent workaround to being able to seek, pause and stop the audio by binding the wave to an audio control (see #25 (comment)), the underlying API is a little confusing and/or lacking in function:

• Calling stop() effectively causes disposal of the audio source, meaning subsequent plays do not work without re-creating the audio
• There is no in-built way to seek or pause the audio
• There is no in-built way to retrieve information about the audio playback such as currentTime and totalTime

All of these items make it difficult to build a complete UI to interface with the library.

Proposed solution

1. I see no reason why we couldn't just re-render the audio if necessary when someone hits play again. Their intent is obvious, and the audio becoming unplayable after stop is not obvious.

2. The use of the offline audio context makes it possible to keep the audio buffer in memory and re-use it!
   This has the downside though of potentially keeping a large audio buffer around though, so this could be an optimisation option.
   e.g. perhaps stop could take in a boolean parameter that indicates if the buffer should be disposed - stop(true) and otherwise you could call audio.dispose() to remove the buffer.

3. Add seek (or setCurrentTime()) to allow playback from any point in the audio, pause would act the same as stop except that it would not reset the currentTime to 0, so a subsequent play would resume from that point.

4. Expose getCurrentTime() and getTotalTime() on the audio object. These would be functions because it might be expensive/unnecessary to poll and update a current time property; getTotalTime would need to wait until rendering had completed (although you could get the total duration time before even playing the audio)

5. One gotcha with having re-playable/pausable audio is the onended event as this will now be triggered every time the playback stops (even on pause); we could simply rename this event to onstopped and include the current time in the event object (so you could see if it was paused or completed), or make onended only trigger at the end of the audio or when disposed. It might also be useful to know when the audio has finished rendering - onready, and we could re-work the API to allow synchronous usage via this callback if that seems useful.

https://www.typescriptlang.org/docs/handbook/migrating-from-javascript.html

Currently, source code is outdated. It would be great if we turn it to ES6.

Hint: You may check online tools like Lebab.

You can see the letter Ґ here http://old.plast.org.ua/files/files/users/10701/Morse_alphabet.pdf or on Ukrainian wiki page about Morse code.
Morse Code for ґ\Ґ — "--."