Code Monkey home page Code Monkey logo

manual's People

Contributors

be-ing avatar daschuer avatar deborahtrez avatar dependabot[bot] avatar djantti avatar djphatso avatar esbrandt avatar git-developer avatar goodiec avatar h67ma avatar hannydevelop avatar holzhaus avatar joergatgithub avatar josepmajaz avatar jusko avatar kain88-de avatar leifhelm avatar mixxxbot avatar notyouraverageal avatar pegasus-rpg avatar robert904 avatar ronso0 avatar rryan avatar swiftb0y avatar tandy-1000 avatar toszlanyi avatar uklotzde avatar williamlemus avatar xeruf avatar ywwg avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

manual's Issues

make latexpdf fails

I checked out manual HEAD and tried to make a pdf, and got:

! Package pdftex.def Error: File `chapters/../_static/Mixxx-112-LateNight-Effects-Deck.png' not found.

Did someone forget to git add some files?

2.3 release checklist

We have some stuff to do before the 2.3 release.

  • Document cue colors and palette editor/replace tool (#127)
  • Document Intro/Outro cues (#323)
  • Document AutoDJ changes (#323)
  • Document Deck Cloning (#330)
  • Update all screenshots to new default theme
  • Update the Version History
  • ... (feel free to edit this post and add more items)

Exit 1 from Fabric when subtasks fail.

Warning: local() encountered an error (return code 1) while executing 'pdflatex -interaction=nonstopmode Mixxx-Manual.tex'

PDF builds currently return 1 all the time even though they produce PDFs. This prevents us from being able to block the manual build when a real error occurs. We should fix the problems that are causing the PDF build to exit 1.

Versioning

I'm currently writing a sphinx extension that allows us to build multiple versions of the manual.

What tags/branches do we need? I guess all tags and the master branch. I'll mark the tag with the highest version number as the latest version.

We can use that information to show a warning for all other tags that this is an outdated version of the manual. For all branches we can show a warning that it's a development version.

Can we switch to standard versioning tag names (v2.2.3 instead of release-2.2.3)? That would make parsing easier and will look better in the version switcher.

change diagrams to depict a 4 channel sound card

4 channel sound cards are recommended, so they should be depicted in the diagrams. The current diagrams depict a Behringer U-Control UCA202/222 or U-Phono 202, which are 2 channel output sound cards. I suggest changing the diagrams to depict a generic representation of a sound card rather than a particular model.

splitter cable diagram

PR #35 introduced a section of the Hardware Setup chapter for using DJ splitter cables. This section is missing a diagram.

[MIDI scripting] Wrong info about controller ID in the doc

Hello ๐Ÿ‘‹

The documentation about MIDI scripting states that the id parameter received in the controller's init function is what is defined in the related xml file, but actually the given value is the name of the controller that is listed in the Controllers tab in mixxx's preferences.

What the doc says :

The ID parameter of the init function is the controller id attribute from the XML file.
This can be used to identify the particular controller instance in print statements.

What is actually passed :
https://github.com/mixxxdj/mixxx/blob/fa797d239d4331d13ca73863391262612ea5d5ed/src/controllers/engine/controllerengine.cpp#L277-L282

Is it possible to fix the doc (or even better, to change mixxx behavior to match the doc ?)

Preferences chapter?

Only a small portion of the Preferences window is documented in the manual. Currently, each of these sections explaining a part of the Preferences is scattered around the manual. Should a new chapter be started for the Preferences window that documents all the options?

@Pegasus-RPG , are you planning on reorganizing the Preferences window for 2.1? Should writing this manual chapter wait until then?

Update all screenshots

Gui and Preferences dialog look different then in 1.11, so update all images accordingly.

Relink should be better described

The library relink function should be better described. I used it to set up a training instance on a second machine and was not certain how and after which user interaction it worked, even after reading all manual content about it.

A typical scenario is, that a harddisc is defect and the user sets up a new machine with a different library path. A step by step howto to set it up with backups of music dir and mixxx dir would be great. Keep in mind, this is a critical situation, the DJ can loose a lot of his work, when playlists and crates are not usable any more. (Analyze results the same). This would be a worst case user experience, so the manual should be more explicit here.

What I miss:

  • Does the relink require a select of one library path before (even if only one library path exist)
  • When does the relink happen? When I press apply in options dialog or during the next library scan? When can I see it in the location column of the playlists for prove?
  • Which parts of the library are touched by the relink (playlists, crates, missing tracks, analyze results). How to prove?
  • In my experience, during the next library scan after relink, mixxx takes a lot of time a one track with a path from the old location. At this moment the program seems to be stalled (my lib is large), and I had not enough patience to wait for the first try, killed the process and so the relink. Only after a full run of library scan, the relink was successful. Correct?
  • for experts: what are the SQL steps in the sqlite db to fix it, when relink does not help or the db structure is partly corrupt

section titles at different levels break visual flow

I asked my friend to read part of the Mixxx manual and she found the visual presentation very distracting. She said the section titles on different levels are confusing and it feels like sections end abruptly when reaching a subsection title because they look so similar.

DJing With Mixxx has become a dump settings descriptions

We explain a lot of the different settings in the Djing with mixxx chapter. Eg Bpm settings. This is intuitive. It takes me a while to find the settings descriptions by just looking at the TOC of the manual.

All this stuff should be moved to Configuring Mixxx and then referenced in Djjing with Mixxx.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.