|
»
Ardour Manual Updates
|
View:
New views
14 Messages
—
Rating Filter:
Alert me
|
 |
Ardour Manual Updates
by Thomas Vecchione-2
::
Rate this Message:
Howdy Folks-
Ok so time for updates again, and a request to get the last bit of work done in order to get the manual out the door, at least in a preview state, in the next 3 weeks. So in an effort to recruit some more help in doing this as my schedule has been fuller than I anticipated lately, I am posting a punch list here for people to hopefully see. Screenshots: As we already discovered, PNGs need to be made without the Alpha channel. Ok old news aside, time for new things. We have discovered that Daisy doesn't render to PDF with text flow around images very well(At all). So as a result we are trying to consolidate down our screenshots so that there are fewer that need to be inline. As a result I have been working on a new(ish) method of annotating our screenshot, doing one larger screenshot at the top of a section, which would then be labeled in the text of the article that the screenshot is embedded in. So, putting a call out to anyone that can use Inkscape or Gimp(Or similar). The basics of the new screenshot annotation style is here... http://vm-nice.stackingdwarves.net:8888/ardour-en/384-ARDOUR.html We need to embed PNG files into the articles of course, but I would like to keep the source files as SVGs and attached to an article on Daisy I set up for this here... http://vm-nice.stackingdwarves.net:8888/ardour-en/388-ARDOUR.html The main purpose to this is to allow easy editing if needed. Ideally we won't have to edit them, as the actual text to translate will be in the article itself and we are only labeling, but this keeps us safe. For the record, neither of these articles is in the manual of course;) Variables: Ok one function of Daisy that we need to start taking more advantage of is variables. Right now there are variables for Button-1, Button-2, and Button-3 Click, etc. Pretty much this ends up becoming left, right, and middle click mapped correctly. I have also set up variables for the various modifier keys (SHIFT/ALT/etc.). I am also looking at the possibility of creating variables for various default keybindings as well but am not certain that I am going to do this. At any rate what I need for now though is people to start going through and make sure that all articles that reference either a button click or modifier key for a shortcut, take advantage of these variables. Dialogs: Any command that would open a seperate dialog, that dialog needs to be documented in the Other Windows Section. If there is a command that opens that dialog, this should be described in brief and linked to the article describing the dialog. Punch List: There is a punch list forming at http://vm-nice.stackingdwarves.net:8888/ardour-en/4-ARDOUR.html on things to do. As you complete one please make it a strikethrough text and put your name in parens near it so that we can know it has been taken care of. Goals: Ok the goals of all this is to release a preview render of the entire manual within 3 weeks. The sooner we get this done the better. If everyone with an account takes out one line of the punch list a week, we will have no problem meeting that goal. I would ask while people are doing this we also look into the above as well. Please let me know if there are any questions. I am sure I missed several things here and I am hoping people that have been kicking me in the head to get this done jump on me to clarify things;) Seablade _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Dave Peticolas
::
Rate this Message:
Thomas Vecchione wrote:
> Howdy Folks- > > Ok so time for updates again, and a request to get the last bit of > work done in order to get the manual out the door, at least in a preview > state, in the next 3 weeks. So in an effort to recruit some more help > in doing this as my schedule has been fuller than I anticipated lately, > I am posting a punch list here for people to hopefully see. > > Screenshots: > > As we already discovered, PNGs need to be made without the Alpha channel. > > Ok old news aside, time for new things. We have discovered that Daisy > doesn't render to PDF with text flow around images very well(At all). > So as a result we are trying to consolidate down our screenshots so that > there are fewer that need to be inline. As a result I have been working > on a new(ish) method of annotating our screenshot, doing one larger > screenshot at the top of a section, which would then be labeled in the > text of the article that the screenshot is embedded in. > > So, putting a call out to anyone that can use Inkscape or Gimp(Or > similar). The basics of the new screenshot annotation style is here... > http://vm-nice.stackingdwarves.net:8888/ardour-en/384-ARDOUR.html > > We need to embed PNG files into the articles of course, but I would like > to keep the source files as SVGs and attached to an article on Daisy I > set up for this here... > http://vm-nice.stackingdwarves.net:8888/ardour-en/388-ARDOUR.html > > The main purpose to this is to allow easy editing if needed. Ideally we > won't have to edit them, as the actual text to translate will be in the > article itself and we are only labeling, but this keeps us safe. > > For the record, neither of these articles is in the manual of course;) > > Variables: > > Ok one function of Daisy that we need to start taking more advantage of > is variables. Right now there are variables for Button-1, Button-2, and > Button-3 Click, etc. Pretty much this ends up becoming left, right, and > middle click mapped correctly. I have also set up variables for the > various modifier keys (SHIFT/ALT/etc.). I am also looking at the > possibility of creating variables for various default keybindings as > well but am not certain that I am going to do this. At any rate what I > need for now though is people to start going through and make sure that > all articles that reference either a button click or modifier key for a > shortcut, take advantage of these variables. > > Dialogs: > > Any command that would open a seperate dialog, that dialog needs to be > documented in the Other Windows Section. If there is a command that > opens that dialog, this should be described in brief and linked to the > article describing the dialog. > > > Punch List: > > There is a punch list forming at > http://vm-nice.stackingdwarves.net:8888/ardour-en/4-ARDOUR.html on > things to do. As you complete one please make it a strikethrough text > and put your name in parens near it so that we can know it has been > taken care of. > > > Goals: > > Ok the goals of all this is to release a preview render of the entire > manual within 3 weeks. The sooner we get this done the better. If > everyone with an account takes out one line of the punch list a week, we > will have no problem meeting that goal. I would ask while people are > doing this we also look into the above as well. > > Please let me know if there are any questions. I am sure I missed > several things here and I am hoping people that have been kicking me in > the head to get this done jump on me to clarify things;) I'd like to try to make a few screenshots. Is there a list of the ones that need to be done? thanks, dave _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Thomas Vecchione-2
::
Rate this Message:
Some of them are mentioned in the punch list that I linked to. If
those all get done and I don't notice, let me know and I can come up with many more I am sure;) Thanks. Seablade On Wed, Oct 7, 2009 at 1:05 AM, Dave Peticolas <dave@...> wrote: > Thomas Vecchione wrote: >> >> Howdy Folks- >> >> Ok so time for updates again, and a request to get the last bit of work >> done in order to get the manual out the door, at least in a preview state, >> in the next 3 weeks. So in an effort to recruit some more help in doing >> this as my schedule has been fuller than I anticipated lately, I am posting >> a punch list here for people to hopefully see. >> >> Screenshots: >> >> As we already discovered, PNGs need to be made without the Alpha channel. >> >> Ok old news aside, time for new things. We have discovered that Daisy >> doesn't render to PDF with text flow around images very well(At all). So as >> a result we are trying to consolidate down our screenshots so that there are >> fewer that need to be inline. As a result I have been working on a new(ish) >> method of annotating our screenshot, doing one larger screenshot at the top >> of a section, which would then be labeled in the text of the article that >> the screenshot is embedded in. >> >> So, putting a call out to anyone that can use Inkscape or Gimp(Or >> similar). The basics of the new screenshot annotation style is here... >> http://vm-nice.stackingdwarves.net:8888/ardour-en/384-ARDOUR.html >> >> We need to embed PNG files into the articles of course, but I would like >> to keep the source files as SVGs and attached to an article on Daisy I set >> up for this here... >> http://vm-nice.stackingdwarves.net:8888/ardour-en/388-ARDOUR.html >> >> The main purpose to this is to allow easy editing if needed. Ideally we >> won't have to edit them, as the actual text to translate will be in the >> article itself and we are only labeling, but this keeps us safe. >> >> For the record, neither of these articles is in the manual of course;) >> >> Variables: >> >> Ok one function of Daisy that we need to start taking more advantage of is >> variables. Right now there are variables for Button-1, Button-2, and >> Button-3 Click, etc. Pretty much this ends up becoming left, right, and >> middle click mapped correctly. I have also set up variables for the various >> modifier keys (SHIFT/ALT/etc.). I am also looking at the possibility of >> creating variables for various default keybindings as well but am not >> certain that I am going to do this. At any rate what I need for now though >> is people to start going through and make sure that all articles that >> reference either a button click or modifier key for a shortcut, take >> advantage of these variables. >> >> Dialogs: >> >> Any command that would open a seperate dialog, that dialog needs to be >> documented in the Other Windows Section. If there is a command that opens >> that dialog, this should be described in brief and linked to the article >> describing the dialog. >> >> >> Punch List: >> >> There is a punch list forming at >> http://vm-nice.stackingdwarves.net:8888/ardour-en/4-ARDOUR.html on things to >> do. As you complete one please make it a strikethrough text and put your >> name in parens near it so that we can know it has been taken care of. >> >> >> Goals: >> >> Ok the goals of all this is to release a preview render of the entire >> manual within 3 weeks. The sooner we get this done the better. If everyone >> with an account takes out one line of the punch list a week, we will have no >> problem meeting that goal. I would ask while people are doing this we also >> look into the above as well. >> >> Please let me know if there are any questions. I am sure I missed several >> things here and I am hoping people that have been kicking me in the head to >> get this done jump on me to clarify things;) > > I'd like to try to make a few screenshots. Is there a list of the ones > that need to be done? > > thanks, > dave > Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
clarification needed: denormal handling
by Jörn Nettingsmeier-5
::
Rate this Message:
Thomas Vecchione wrote:
> Howdy Folks- http://vm-nice.stackingdwarves.net:8888/ardour-en/8-ARDOUR/289-ARDOUR/298-ARDOUR/327-ARDOUR.html here's the excerpt. i'd appreciate some verification of the introduction, and clarification about FTZ/DAZ mode (see below). > What is a denormal? > > A denormal is a floating-point value that is too close to zero to > allow its representation in the "normal" floating-point binary > format. The processor attempts to maintain precision, at the expense > of CPU time. Lots of CPU time, in fact. Processing denormals takes > hundreds of times longer than processing normal floating-point > values. When the CPU goes into denormal mode, things slow to a crawl. > Since audio machines are typically used at close to maximum CPU load, > denormals will lead to overloading, causing dropouts or even crashes. > > > If you're sending a rocket to Mars, it's very important to maintain > precision. This is the assumption made by some CPU designers. For > audio, when values are very close to zero, processing speed is more > important than precision. There are several techniques that may be > used to keep the CPU out of denormal mode, trading off precision for > speed. > > In audio processing, denormals are frequently produced by reverb > tails and similar operations involving highly attenuated feedback > loops. Problems usually arise when a sound is decaying to silence. > There are a number of ways to avoid denormals and thus > non-deterministic CPU overloading: Use DC bias > > Adds a constant, very small value to each sample to keep it out of > the denormal range (known to electrical engineers as a "DC" or > "direct curent" offset, as opposed to the alternating current that > makes up the actual sound in the signal). A DC component as such is > inaudible. However, some DSP operations are sensitive to DC offsets > and might behave slightly odd [FIXME: good example?]. But since the > amount of DC used here is very small, any artifacts will usually be > negligible in practice. No processor handling > > Don't do anything about denormals (at the risk of overloading theCPU > and causing dropouts if/when they occur). Use FlushToZero Use > DenormalsAreZero Use FlushToZero/DenormalsAreZero > > [FIXME: the difference between FTZ and DAZ seems to be very subtle > indeed (scroll down a bit). Maybe a developer can explain? And what > is the reason that such intricacies are exposed to the user? IIUC, > any processor that does FTZ is also capable of DAZ. Are there any > reasons not to enable either or both of these by default?] thanks, jörn -- Jörn Nettingsmeier Meister für Veranstaltungstechnik Audio and event engineer Ambisonic surround recordings http://stackingdwarves.net +49 177 7937487 _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
|
|
|
Re: Ardour Manual Updates
by Stephen Doonan
::
Rate this Message:
Thomas Vecchione wrote:
> Screenshots: > > As we already discovered, PNGs need to be made without the Alpha channel. > ... > So, putting a call out to anyone that can use Inkscape or Gimp(Or > similar). The basics of the new screenshot annotation style is here... > http://vm-nice.stackingdwarves.net:8888/ardour-en/384-ARDOUR.html > > We need to embed PNG files into the articles of course, but I would like > to keep the source files as SVGs and attached to an article on Daisy I > set up for this here... > http://vm-nice.stackingdwarves.net:8888/ardour-en/388-ARDOUR.html Regarding the annotating, drop-down menus are mentioned, but what about pop-up menus? For example, how would you like the screenshot of the mixer window to look? With the popup menus that occur when one right-clicks the Strips or Groups pane, and/or the popups when one clicks the Input and Output buttons, or the space for plug-ins? If too many of the popups are visible, the screenshot for the window will be obscured and perhaps too many areas covered up. I'm just trying to get an idea of how to do this, and the answers may be helpful to others who may consider the idea of making a screenshot or two. Best wishes, Steve New Mexico, US _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Thomas Vecchione-2
::
Rate this Message:
On Wed, Oct 7, 2009 at 5:26 PM, Stephen Doonan <stephen.doonan@...> wrote:
> Regarding the annotating, drop-down menus are mentioned, but what about > pop-up menus? For example, how would you like the screenshot of the mixer > window to look? With the popup menus that occur when one right-clicks the > Strips or Groups pane, and/or the popups when one clicks the Input and > Output buttons, or the space for plug-ins? If too many of the popups are > visible, the screenshot for the window will be obscured and perhaps too many > areas covered up. > > I'm just trying to get an idea of how to do this, and the answers may be > helpful to others who may consider the idea of making a screenshot or two. > Good questions and thank you for bringing them up. Regarding Popup Menus, and what I will call 'Context Menus' which come by right clicking on something... No, I do not believe we need a screenshot for them. Instead what I am playing with and seems to be working so far, is to use a borderless table, on the left hand side put the Menu option, and on the right hand side a description of what it does. This also works for ANYTHING that is a series of quick options that need to be described. I just changed the 'Automation Tracks' article in this fashion for the automation modes, and it seems to work well. I have to tweak the column widths to fit each table manually though, so if you look at a PDF of a table you just made and it doesn't look good(The columns evenly split the page) that is only because I have not tweaked the width of them in the PDF output manually yet. Make sure I know about it somehow, or do it yourself via the table settings icon in the editor. Speaking of which, to create a borderless table, in the table settings(Click on the icon that looks like a hand/finger hovering over a table) at the bottom is an option called classes. Set that to borderless by utilizing the dropdown menu. I will be going through and doing this to many things over the next few days most likely(Though I likely won't be doing much tomorrow at all due to work). Please keep questions coming as you get them! Seablade _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
|
|
|
Re: Ardour Manual Updates
by Stephen Doonan
::
Rate this Message:
Thomas Vecchione wrote:
> > We should also probably highlight the Strip List and Group section, a > seperate Bus vs Track strip, as well as pulling out a few specific > buttons in the mixer strips, the TrackName button, Input Button, > Output Button, Record, etc. How do you want the highlighted (haloed) sections to be annotated, with just numbers as in the example you mentioned at the beginning of this discussion-- http://vm-nice.stackingdwarves.net:8888/ardour-en/384-ARDOUR.html --or with the name of the object being highlighted? Will the text of the manual refer to the various highlighted regions by number? For example, would the text of the manual say-- The Strip List (1) provides a simple interface to the layout of the mixer strips on the mixer. (The "(1)" above would refer to a numbered object in the screenshot?) Or would the manual omit numeric or other references to specific objects within the screenshot, in which case the Strip List object/highlighted-area in the screenshot would be annotated with "Strip List" in 40 pt. Bitstream Vera Sans? By the way, have you considered using Redhat's gift to the community, their Liberation typefaces? Liberation Sans? Best wishes, Steve _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Thomas Vecchione-2
::
Rate this Message:
On Thu, Oct 8, 2009 at 10:44 AM, Stephen Doonan
<stephen.doonan@...> wrote: > Thomas Vecchione wrote: > How do you want the highlighted (haloed) sections to be annotated, with just > numbers as in the example you mentioned at the beginning of this > discussion-- > > http://vm-nice.stackingdwarves.net:8888/ardour-en/384-ARDOUR.html > > --or with the name of the object being highlighted? Will the text of the > manual refer to the various highlighted regions by number? For example, > would the text of the manual say-- > > The Strip List (1) provides a simple interface to the layout of the mixer > strips on the mixer. > > (The "(1)" above would refer to a numbered object in the screenshot?) > Similar. On the same article that the annotated screenshot exists, likely in the caption for the screenshot itself, needs to be a 'key' of Numbers and the Name of the object that number refers to. On the image itself should only be the numbers. Let me see if I can update the sample article to give an example(And it would only be an example of course). If we need to reference an object within another article, we need to link to the article that describes that object, instead of using numbers in parenthesis. > > By the way, have you considered using Redhat's gift to the community, their > Liberation typefaces? Liberation Sans? > We are limited in our selection of typefaces to what Daisy can handle at the moment, and I am not anxious to dig into it to see if we can change it at the moment. To much else to do when what they provide for output works pretty well. In the images obviously we can use any type face, and in that case, no I did not look at those. I was primarily just looking for soemthing that would work and be clear for it, and am open to change it, but it should be something availiable easily on both Mac OS X and Linux. Seablade _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Thomas Vecchione-2
::
Rate this Message:
I just updated the sample article with an example of what I am looking
for in how to handle the annotations. It was a poor example just because of the screenshot I used, sorry. But hopefully it gives the basic idea. The difference is that in the end, the Annotated Screenshot, Caption, and Key(Table), I am hoping to get on a page by themselves to start a section. I am working out the details on how exactly to do this, but lets assume I succeed in this regard for the time being:) Seablade Still working through fun with Daisy on occasion as we get farther along:) _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Thomas Vecchione-2
::
Rate this Message:
By the way, if you haven't discovered this already, if you go to
Actions>PDF on any article, Daisy will render a PDF of that article so you can preview what it might look like. Note that links will be handled a bit different because we aren't publishing a full book, but in general it will be close enough to preview your work. I would suggest doing this to see for example how the sample image gets rendered in PDF output, as it looks different than it does in the Wiki itself. Seablade On Thu, Oct 8, 2009 at 11:12 AM, Thomas Vecchione <seablaede@...> wrote: > I just updated the sample article with an example of what I am looking > for in how to handle the annotations. It was a poor example just > because of the screenshot I used, sorry. But hopefully it gives the > basic idea. The difference is that in the end, the Annotated > Screenshot, Caption, and Key(Table), I am hoping to get on a page by > themselves to start a section. I am working out the details on how > exactly to do this, but lets assume I succeed in this regard for the > time being:) > > Seablade > > Still working through fun with Daisy on occasion as we get farther along:) > Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Stephen Doonan
::
Rate this Message:
Thomas Vecchione wrote:
> Screenshots: > > As we already discovered, PNGs need to be made without the Alpha channel. Do you mean the final exported-bitmap PNG from Inkscape? Or do you mean all imported PNG elements from original screenshots to Gimp parts and pieces of the screenshots saved as PNG and imported into Inkscape? Or both? Thanks-- Steve _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Ardour Manual Updates
by Thomas Vecchione-2
::
Rate this Message:
On Thu, Oct 8, 2009 at 11:57 AM, Stephen Doonan
<stephen.doonan@...> wrote: > Do you mean the final exported-bitmap PNG from Inkscape? The final exported raster image. Seablade _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
| Free embeddable forum powered by Nabble | Forum Help |
