Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

English language manual + Troubleshooting/Frequent questions #39

Open
jpcima opened this issue Nov 5, 2018 · 3 comments
Open

English language manual + Troubleshooting/Frequent questions #39

jpcima opened this issue Nov 5, 2018 · 3 comments

Comments

@jpcima
Copy link
Owner

jpcima commented Nov 5, 2018

Translate the manual.
First, probably it is best to improve the existing manual as needed to avoid double-work later.

  • Add the section: Troubleshooting/Frequent questions

There go the questions about usage of ADLplug and problems encountered.

  • why does it sound wrong/no sound?
  • why doesn't it play the program indicated?
  • how to use the drums?
  • how to load instruments from the internet?
  • [...]
@ghost
Copy link

ghost commented May 29, 2019

@jpcima If you like, I'd be happy to translate the manual into English. I don't speak French, but I can probably Google translate it, then manually tweak that into correct, meaningful English.

PS: Great work on this plugin! I hope you don't mind, but I've added a link to ADLplug from the JuceOPLVSTi project. As far as I can see, ADLplug is an improvement over JuceOPLVSTi in every way.

@jpcima
Copy link
Owner Author

jpcima commented May 29, 2019

This would be a very welcome contribution @bsutherland, thank you.
Last time I checked, google translation was not too bad and can be an appropriate base for translating.

About ADLplug and future, I am myself rather satisfied with the state of things.
Next, focus will be set on libADLMIDI for a moment, in perspective of making improvement and permitting less contraining licensing.

@trebmuh
Copy link
Contributor

trebmuh commented May 29, 2019

Last time I checked, google translation was not too bad and can be an appropriate base for translating.

Just for information, deepl is usually working better for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants