-
Notifications
You must be signed in to change notification settings - Fork 7
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
General Site for JuliaMusic Org using Franklin.jl #9
Comments
There is a slack So I find this issue very low priority, you can of course feel free to start working on a site :P
I do scientific research using JuliaMusic but I don't think anyone else does. MIDI.jl has an associated paper but it doesn't have any citations outside mine. |
oK!!There seems a lot of work that could be worked upon then :) |
Regarding the team stuff, 😄 I have been busy developing and fixing MusicXML.jl itself. There is still some stuff to fix before I can help with other packages. For example, JuliaMusic/MusicXML.jl#30 or JuliaMusic/MusicXML.jl#46 and finally JuliaMusic/MusicXML.jl#3 |
I like to see a unified website. Especially, if it addresses the issue in #5. I prefer to write the documentation of each package in its repository. If there is a way to bring all those into a single website, it would be good. Similar to https://juliarobotics.org/ @Datseris I think this issue should move to https://github.com/JuliaMusic/JuliaMusic_documentation.jl |
@team pretty optimistic that there will be a need of a team to maintain this place in 5 years time :) |
Notice that we can re-use this website: https://juliadynamics.github.io/JuliaDynamics/ which comes from the main org I develop. |
We might need to fix JuliaDocs/Documenter.jl#688 first, for doing this. |
I saw the julia dynamics site,it is more science type than music type :p we could try for more colorful and interactive if that's allowed @Datseris :) Ofcourse,they have video tutorials which I am not sure if it is feasible right now,so we can create Ijulia notebooks if that is possible in HTML format like done by steven tjoa in ipython: |
for me this is a very low priority. The packages of JuliaMusic are very small and self contained, I doubt the existence of tutorials will make them so much more easier to learn, versus the gain tutorials have on organizations like JuliaRobotics. There of course things are much more complex. Besides, the MIDI, MusicManipulations and MusicVisualizations already have "tutorials" in the form of runnable code that runs from within the documentation pages, e.g. https://juliamusic.github.io/JuliaMusic_documentation.jl/dev/mm/quantizing/ thus spending time to make a tutorial for something already explained so clearly, is not time well spent I feel. I mentioned this in another PR as well, but I think what is discussed here should come after code improvements are done. For example, I load a midi file via using MIDI
midi = readMIDIFile("test.mid") Can I pass this |
Not yet. That is being tracked in JuliaMusic/MusicXML.jl#3 However, before that, I need to merge JuliaMusic/MusicXML.jl#49, which automatically sets the graphical representation of the notes based on their duration (similar to MIDI note duration). However, that is failing because of Julia crashes JuliaLang/julia#36269. MusicXML is different from MIDI in many ways. MusicXML works like how humans think of music. Humans think of time signatures, pitches, rests, etc and all of these are related to each other. To automatically find the graphical representation, the code should analyze the last time signature that is defined and then adjust all the notes based on that! This makes things complex since it requires intertype communication. |
I'd vouch for renaming this repository to juliamusic.github.io and generating the website in a manner similar to https://juliarobotics.org/. The current name, i.e. https://juliamusic.github.io/JuliaMusic_documentation.jl/dev/ seems overly complex for the task. |
If you know how to change Documenter.jl generated documentation links go ahead, because I don't... |
For you information, I made a fix for inter-repository linking. JuliaDocs/Documenter.jl#1351 However, I am quite busy right now. I can take a look at this in one or two weeks. That will fix the issue of cross-referencing. |
That's great, but I will be anyways including MusicProcessing.jl in the central docs as well (once it is updated of course). |
@team @Datseris
I believe there is a need to develop a community around JuliaMusic
Quoting Viral shah
We also only have documentation,we need to start collecting literature and people work's using JuliaMusic Packages..
I therefore propose we start working on it and develop the general site.I believe most of the people currently working on JuliaMusic maintain a blog and I also do it..So putting together a static site won't be that tough and it can be put together within a few days... I have quite a lot of time at my hand right now,so I can work on it...
Also @Datseris ,I have seen in bokeh that ("@bokeh/dev") is used to call for the whole development team,can It be made available here too??Probably also start a slack if there is not one already...
The text was updated successfully, but these errors were encountered: