[ubuntu-studio-devel] Ubuntu Studio For Musicians handbook
lukefromdc at hushmail.com
lukefromdc at hushmail.com
Sun Jun 3 21:04:17 UTC 2018
One place you may need more detail (or to tell people to look online for it
is the mess created by UEFI and secure boot for new installs on
computers from the Windows 8 and later eras. The advice given about trying
from a USB stick and how easy it is applies only to machines with a real BIOS
(sold with Windows 7 and earlier or rare Linux preinstalls). or to machines on
which someone else has already disabled secure boot at least. Unless US
installers are using a SIGNED kernel(this I do not know), they are not going to boot US on
anything that still has Secure Boot turned on. Legacy boot should not be needed,
but will of course work fine if someone has already turned it on while turning Secure Boot
off. Also, there are some junk Lenovo laptops that do a string check to block everything
but Windows 8 and RHEL, but will boot other OS's if the boot executable is renamed to march
either of those.
I had to install Ubuntu on one laptop for a friend that was an almost exact copy of a
machine she had that died-except for a later UEFI version. The new version was buggy,
and could not boot any linux distro without updating the UEFI again, which had to be done
from within Windows 10. For someone not willing to activate Win10, that's a
return to the store. My friend had paid a local techician $90 just to rid her first of these
machines of Windows 10, and that second one would have been even more had I not been
able to find the issue. Without my own (running) machine to access the Internet it would not
have been possible to even research what was wrong other than from inside Windows 10.
There are some Win10 machines that cannot even get to the UEFI screen except from
inside Windows (and AFTER activating Windows) unless you can remove the
drive (not possible if soldered down or too hard to disassemble) or otherwise
forcibly cause boot failure. These are the ones with "fast boot" enabled. This skips
things like initializing the keyboard, USB etc in firmware, so there is no way to even
ask for a USB boot much less execute one until fast boot is turned off.
Some have reported success with repeated power cycling during boot to simulate
a failure of Windows to boot. but I have not played with one of those "fast boot" machines
so I do not know.
More recently, when I my good BIOS-based Atom netbook died, the closest
replacment was a bottom-barrel Chromebook. Unfamiliar with the process for
wiping Chrome and installing only a real distro, it took me hours JUST TO GET
ROOT so I could reset the bootloader to accept anything other than Chrome.
"Developer mode" was not enough, and getting to a terminal without creating
a Google Account required a lot of though and non-obvious procedures. I almost
returned it to the store before I finally figured it out. I had to among other things
create a dummy wireless hotspot with no Internet access to get past the "connect
to the Internet" part of intiial startup, not knowing it could F-2 to a terminal like
any other Linux install.
Had I removed the disk and directly installed to it first, I would have been unable
to turn on legacy boot, as the Coreboot varient used in that version of Google Chrome can only
be reset to allow USB and legacy boot from inside Chrome OS! Withing theChromeOS
command line, if you try to set a root password and fail, you are all the way locked
out until you "powerwash" to reset to factory. The OS I was installing was an image of
one installed on a BIOS machine, thus itself was only bootable by legacy boot on anything.
Newcomers would be much better off with either a desktop build new from parts
(so Windows was never installed, no Intel Boot Guard, and an easy to reach UEFI
setup page) or from a sufficiently powerful older machine with a real BIOS, meaning
one that came with Windows 7 or older. Newer laptops can be brutally difficult, and
I do not advise spending money on such a machine unless you specifically need a
laptop. Also especially avoid Lenovo-not worth a penny unless the exact model involved
passes an online search for bootability with Linux, or you aready have it. Lenovo is
infamous for actively malicious UEFI code, such as the above-mentioned string
check, and in another case reinstalling Windows bloatware removed by users.
Some Win10 machines (those shipped with Fastboot turned off) are as easy as BIOS machines that
were not factory set for USB boot to get going, others are impossible without updates to
buggy firmware. If buying a new or used Windows 8 or later machine, you need to check exactly
what you are buying oneline prior to purchase.
At least in the case of Chromebooks they are most consistant: actually harder to get to
boot real Linux with Chrome removed, but as they use Coreboot all of them can be
eventually rooted and made to run UbuntuStudio or any other recent distro. You may
very well need that external soundcard though, as the onboard sound may not work
or may work only when connected to a HDMI screen and external speakers due to
kernel bugs for which ChromeOS gets patches. On the other hand, even the cheapest
Chromebooks (as long as they are x86 and not ARM so the necessary software is available
in architecture-compatable builds ) are surprisingly powerful these days. All those die shrinks
have let Intel et all get more power into the low power budget chips. You won't edit video
on one (except in HW accelerated Avidemux) but you can play 1080p video and audio
editing should be fine.
On 6/3/2018 at 12:03 PM, "eylul" <eylul at ubuntustudio.org> wrote:
>
>I think even if it is a living document (as it should be) it would
>be a
>cool idea for it to have regular release versions to encourage
>people to
>update and have an offline copy of. In addition to html, an epub
>would
>be compatible with ebook readers and lightweight (which is nice
>when you
>can have your computer you work on, and the reference next to it),
>it
>should be pretty straightforward to convert it from epub to pdf
>too. (I
>can help with formatting converting aspect of this, if/when it
>comes to
>it and its pretty straightforward with calibre, when going from a
>libreoffice file)
>
>In the short term, we could probably attach a pdf/epub version of
>this
>to a blog post on the website when it is finalized, and have the
>file
>downloaded from there (or link it as pdf from one of the static
>pages
>for support etc as well), until we can find a permanent home for
>the
>living document version.
>
>Just thinking out loud. :)
>
>Best
>
>Eylul
>
>
>On 06/03/2018 06:05 PM, Peter Reppert wrote:
>> Here is the handbook in PDF format.
>>
>https://drive.google.com/open?id=1eKETJ5rhxHtntLvCATm7xu7JpuogOAcx
>> Only two people have read it and they did not mark it up - it
>> desperately needs some proofreading and editing.
>>
>> Anyway, please give it a read. To be clear - I was hoping to
>post
>> this somewhere like wiki.ubuntustudio.com
>> <http://wiki.ubuntustudio.com> - that is, I do not want to share
>a
>> link to my Google Drive with all Ubuntu users! This should be
>hosted
>> with other Ubuntu documentation. I think a wiki would be great,
>but I
>> don't see how to go about actually posting it and need step-by-
>step
>> instructions. So far I haven't found anything that makes sense
>as a
>> place to upload this. Not to get too far ahead of things, but
>could
>> this become part of the skeletal audio guide here:
>> https://help.ubuntu.com/community/UbuntuStudio/UserGuide/Audio ?
>> That is a great outline, by the way - I wouldn't want to alter
>it.
>>
>> So: *DO* download this if you are on the Documentation team. *DO
>*feel
>> free to upload it somewhere the team can access it. *DO NOT*
>post the
>> link to my Google Drive on any Ubuntu public pages. I will work
>on
>> making an editable version of this, and will be very happy to
>try to
>> post it to a Wiki, as soon as I see where and how to do so. Link,
>> please? I am hoping that once it has been reviewed a little, it
>ends
>> up somewhere that new users can readily find it from the main
>Ubuntu
>> Studio page, whatever that may entail.
>>
>> Let me know if you have any trouble accessing the PDF. I gave it
>a
>> quick check and everything seems to be there - it's a bit longer
>than
>> I said.
>>
>> Thanks, and looking forward to your feedback! Will get on IRC
>> sometime this week, most likely.
>>
>> Pete
>>
>> P.s. - at this point I should probably repeat that this PDF file
>is
>> hereby officially public domain. This is a way of paying back
>for all
>> the great software and contributions of others in the Ubuntu
>> community. Once this becomes a group project, I hope credit will
>be
>> given as due (to all who work on it).
>>
>> On Sun, Jun 3, 2018 at 8:00 AM,
>> <ubuntu-studio-devel-request at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel-request at lists.ubuntu.com>> wrote:
>>
>> Send ubuntu-studio-devel mailing list submissions to
>> ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
>> <https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-
>devel>
>> or, via email, send a message with subject or body 'help' to
>> ubuntu-studio-devel-request at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel-request at lists.ubuntu.com>
>>
>> You can reach the person managing the list at
>> ubuntu-studio-devel-owner at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel-owner at lists.ubuntu.com>
>>
>> When replying, please edit your Subject line so it is more
>specific
>> than "Re: Contents of ubuntu-studio-devel digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: Saturday's Meeting (June 2, 2018) (Ross Gammon)
>> 2. Re: Ubuntu Studio For Musicians handbook (Ross Gammon)
>> 3. Re: Ubuntu Studio For Musicians handbook (Peter
>Reppert)
>> 4. Re: Ubuntu Studio For Musicians handbook (charlie)
>> 5. Re: Ubuntu Studio For Musicians handbook (Ralf
>Mardorf)
>>
>>
>> -------------------------------------------------------------
>---------
>>
>> Message: 1
>> Date: Sat, 2 Jun 2018 15:14:23 +0200
>> From: Ross Gammon <ubuntustudio at the-gammons.net
>> <mailto:ubuntustudio at the-gammons.net>>
>> To: ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>> Subject: Re: [ubuntu-studio-devel] Saturday's Meeting (June
>2, 2018)
>> Message-ID: <8d6ea94c-81e5-6a95-75b4-ecefe7550e5f at the-
>gammons.net
>> <mailto:8d6ea94c-81e5-6a95-75b4-ecefe7550e5f at the-
>gammons.net>>
>> Content-Type: text/plain; charset=utf-8
>>
>> I don't believe it - I was likely to attend this week ;-)
>>
>> Sorry - I have been working overseas for the last 3 weeks,
>and
>> only just
>> caught up with a months emails. But I should be staying home
>for the
>> coming month or so.
>>
>> Are there any packages nearly ready for an upload that I
>could take a
>> look at and try to move forward?
>>
>> Ross
>>
>> On 06/01/2018 04:50 PM, Charlie wrote:
>> > good morning from California! I'm ok with cancelling the
>meeting.
>> >
>> > For me: I've yet to settle into a project to work on for
>Ubunu
>> Studio. I'm still very interested in starting with
>documentation
>> (since I feel like that's the 'entry' level project that I
>should
>> do since I don't have any programming skills yet).
>> >
>> > is there any need for wallpapers? i can work on some
>photos for
>> that.
>> >
>> > that's the end of my report.
>> >
>> > charlie
>> >
>> >> On May 31, 2018, at 21:24, Erich Eickmeyer
>> <erich at ericheickmeyer.com <mailto:erich at ericheickmeyer.com>>
>wrote:
>> >>
>> >> Hey everyone,
>> >>
>> >> Something has come up and I'm likely not to be able to be
>at
>> Saturday's
>> >> meeting. With that, I think it was just going to be a
>progress
>> report
>> >> anyhow, so I'm all for canceling the meeting this week.
>Perhaps
>> we can
>> >> just give progress reports on our various projects by
>replying
>> to this
>> >> thread.
>> >>
>> >> I'll start: I'm still working on rebranding
>> ubuntustudio-welcome to be,
>> >> well, Ubuntu Studio as opposed to other flavors. My
>progress is
>> >> slow-going, but if anybody wants to chip-in they can find
>the
>> git repo
>> >> on my Launchpad page, and it should also be listed under
>the Ubuntu
>> >> Studio project itself.
>> >>
>> >> That's all I've got. I would love to hear whatever else
>anybody
>> has.
>> >>
>> >> -Erich
>> >>
>> >>
>> >> --
>> >> ubuntu-studio-devel mailing list
>> >> ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>> >> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
>> <https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-
>devel>
>> >
>> >
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sat, 2 Jun 2018 15:24:27 +0200
>> From: Ross Gammon <ubuntustudio at the-gammons.net
>> <mailto:ubuntustudio at the-gammons.net>>
>> To: ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>> Subject: Re: [ubuntu-studio-devel] Ubuntu Studio For
>Musicians
>> handbook
>> Message-ID: <0bb59e13-83ed-7f02-f2f9-61a171a75268 at the-
>gammons.net
>> <mailto:0bb59e13-83ed-7f02-f2f9-61a171a75268 at the-
>gammons.net>>
>> Content-Type: text/plain; charset=utf-8
>>
>> Fantastic. This is just the sort of thing I needed when I
>stopped
>> using
>> Windows for music, and moved to Ubuntu Studio.
>>
>> I always wished that someone did a series of blog posts like
>this, or
>> sold the series to one of the Linux magazines.
>>
>> Finding people to help review it should not be a problem.
>>
>> If you are not so happy with the idea of a wiki, I could
>push some
>> html
>> to my http://people.ubuntu.com/~rosco2/
>> <http://people.ubuntu.com/%7Erosco2/> website temporarily.
>We could
>> probably put it on the ubuntustudio.org
><http://ubuntustudio.org>
>> website in the end. Having the
>> text in git would help others to propose merges.
>>
>> Cheers,
>>
>> Ross
>>
>> On 06/02/2018 04:29 AM, Peter Reppert wrote:
>> > Hi,
>> >
>> > I wrote a handbook called "Ubuntu Studio For Musicians"
>that
>> covers most
>> > of the out-of-the-box programs, recording, mastering,
>making a
>> CD, the
>> > basics of sound synthesis, and revkiews of some free VST
>instruments
>> > (see TOC below). I would like to put this guide in the
>public
>> domain,
>> > and would like to know the best way to go about it? Parts
>of it
>> could
>> > possibly be incorporated into the wiki pages (i just put
>in a
>> request
>> > for a wiki documentation account).
>> >
>> > I have been using Ubuntu Studio for a few years and relying
>> mostly on
>> > the forum for answers (along with the excellent online
>Ardour
>> manual).
>> > Let me know if you think this 50-page handbook would be
>useful,
>> and if
>> > so, could I get help editing it? Also where it might be
>posted as a
>> > standalone manual and easily found? This was written with
>version
>> > 16.04, and is intended for beginner/intermediate users.
>> >
>> > Table Of Contents
>> >
>> >
>> > 1. About this book
>> > Who this book is for
>> > Why buy this book?
>> > How to use this book – know what's possible
>> > Companion matter, if any - web site, disk, etc.
>> > About the author/acknowledgements
>> >
>> > 2. Getting started
>> > Gear on a budget
>> > How to find out if your old laptop can run Ubuntu
>> > System Requirements
>> > Running Ubuntu from media
>> > Installing Ubuntu Studio
>> > Configuring and testing your soundcard
>> > Connecting with JACK and Patchage
>> >
>> > 3. Overview of out-of-the-box instruments and effects
>> > Sound Generators
>> > Hexter
>> > Aeolus
>> > Synthv1
>> > Qsynth, drumkv1, samplev1
>> > Amsynth
>> > Hydrogen
>> > Audio Processors
>> > Guitarix
>> > Rakarrak
>> > Make your guitar a MIDI controller
>> > Tools and Utilities
>> > Major file types
>> > Tools for DJs
>> > Internet DJ Console
>> > SuperLooper
>> > TerminatorX
>> > 4. Basic recording for musicians
>> > Audacity
>> > Ardour
>> >
>> > 5. Using VST plugins
>> > Install Wine
>> > Install and run Carla
>> > Configuring and using Carla
>> >
>> > 6. Advanced recording in Ardour
>> > Punch-ins
>> > Looping
>> > MIDI tracks
>> > Fade-in Fade-out
>> > Automation
>> > Grouping tracks
>> > Creating a bus and inserting effects
>> > Additional advanced topics
>> > LinVST
>> >
>> > 7. Mixing and mastering
>> >
>> > 8. Creating your own SoundFont with Swami
>> >
>> > 9. Sharing your music
>> > Creative Commons
>> > Copyright registration
>> > Royalty collection agencies
>> > Making a CD
>> > Sheet music with MuseScore
>> >
>> > 10. Sound synthesis 101
>> > Knob acronyms
>> > Ten Things To Try On Any Synthesizer
>> > Approaches to sound synthesis
>> > Patch tutorials
>> > Funk Bass
>> > Arpeggiator
>> > Crafting Noise
>> > Siren
>> > Appendix
>> > Troubleshooting
>> > Using the command line
>> > Links and resources
>> >
>> >
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Sat, 2 Jun 2018 12:49:52 -0400
>> From: Peter Reppert <preppert at gmail.com
><mailto:preppert at gmail.com>>
>> To: ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>> Subject: Re: [ubuntu-studio-devel] Ubuntu Studio For
>Musicians
>> handbook
>> Message-ID:
>>
>> <CAK_4AvsDHXkYp5-
>ZhPHS9orX3A8=7zx5Mvcvb=Eg7g5Z4o5w3Q at mail.gmail.com
>> <mailto:Eg7g5Z4o5w3Q at mail.gmail.com>>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi,
>>
>> I am not sure how to properly reply to this mail list, so
>pardon
>> me if this
>> does not end up in the correct thread.
>>
>> Here is my launchpad account to join the documention team:
>> https://launchpad.net/~preppert
><https://launchpad.net/%7Epreppert>
>>
>> I wrote this handbook in LibreOffice Writer, so it's in ODT
>format
>> for now.
>> Please let me know if I should save it as something else,
>and it
>> would be
>> very helpful to know specifically where/how to post it. So
>far I
>> saw "a
>> documentation wiki". I hesitated to send it here as an
>> attachment, but let
>> me know if that would make sense prior to posting it. I am
>fine
>> with it
>> being open for editing and can put together a short list of
>things
>> I was
>> hoping to add.
>> This does not attempt to be a comprehensive manual, more
>of a
>> quick
>> survey and reference handbook with some tricks that even
>> experienced users
>> may have never tried or just want to refer back to quickly.
>> "Stuff I wish
>> I knew/had in one place when I first started using Ubuntu
>> Studio". I could
>> not find anything like it, and figured if there is, writing
>this still
>> wasn't wasted effort. Enough said until I'm better
>oriented. Glad
>> there is
>> some interest.
>>
>> Pete
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> <https://lists.ubuntu.com/archives/ubuntu-studio-
>devel/attachments/20180602/981f49c6/attachment-0001.html
>> <https://lists.ubuntu.com/archives/ubuntu-studio-
>devel/attachments/20180602/981f49c6/attachment-0001.html>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Sat, 2 Jun 2018 10:10:51 -0700
>> From: charlie <contact at charlieluna.com
>> <mailto:contact at charlieluna.com>>
>> To: ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>> Subject: Re: [ubuntu-studio-devel] Ubuntu Studio For
>Musicians
>> handbook
>> Message-ID: <b1dbaa3a-8976-e70c-5a1e-
>a404c29fbac0 at charlieluna.com
>> <mailto:b1dbaa3a-8976-e70c-5a1e-
>a404c29fbac0 at charlieluna.com>>
>> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>>
>> Pete,
>>
>> OH WOW!!! This is totally cool! I'm looking forward to
>reading this
>> handbook and contributing to the documentation team. I look
>> forward to
>> speaking with you at length over anything.
>>
>> Charlie
>>
>> IRC ID: hangar18
>>
>>
>> On 06/02/2018 09:49 AM, Peter Reppert wrote:
>> > Hi,
>> >
>> > I am not sure how to properly reply to this mail list, so
>pardon
>> me if
>> > this does not end up in the correct thread.
>> >
>> > Here is my launchpad account to join the documention team:
>> > https://launchpad.net/~preppert
>> <https://launchpad.net/%7Epreppert>
>> <https://launchpad.net/%7Epreppert
>> <https://launchpad.net/%7Epreppert>>
>> >
>> > I wrote this handbook in LibreOffice Writer, so it's in ODT
>> format for
>> > now. Please let me know if I should save it as something
>else,
>> and it
>> > would be very helpful to know specifically where/how to
>post
>> it. So
>> > far I saw "a documentation wiki". I hesitated to send it
>here
>> as an
>> > attachment, but let me know if that would make sense prior
>to
>> posting
>> > it. I am fine with it being open for editing and can put
>together a
>> > short list of things I was hoping to add.
>> > This does not attempt to be a comprehensive manual,
>more of a
>> > quick survey and reference handbook with some tricks that
>even
>> > experienced users may have never tried or just want to
>refer
>> back to
>> > quickly. "Stuff I wish I knew/had in one place when I
>first
>> started
>> > using Ubuntu Studio". I could not find anything like it,
>and
>> figured
>> > if there is, writing this still wasn't wasted effort.
>Enough said
>> > until I'm better oriented. Glad there is some interest.
>> >
>> > Pete
>> >
>> >
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> <https://lists.ubuntu.com/archives/ubuntu-studio-
>devel/attachments/20180602/93d26cf9/attachment-0001.html
>> <https://lists.ubuntu.com/archives/ubuntu-studio-
>devel/attachments/20180602/93d26cf9/attachment-0001.html>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Sat, 2 Jun 2018 19:32:17 +0200
>> From: Ralf Mardorf <ralf.mardorf at alice-dsl.net
>> <mailto:ralf.mardorf at alice-dsl.net>>
>> To: ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>> Subject: Re: [ubuntu-studio-devel] Ubuntu Studio For
>Musicians
>> handbook
>> Message-ID: <20180602193217.64a02a84 at archlinux>
>> Content-Type: text/plain; charset=US-ASCII
>>
>> On Sat, 2 Jun 2018 12:49:52 -0400, Peter Reppert wrote:
>> >Please let me know if I should save it as something else
>>
>> For downloads the PDF file format is quite common for that
>kind of
>> guide. For online reading it either should be plain text or
>HTML.
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> --
>> ubuntu-studio-devel mailing list
>> ubuntu-studio-devel at lists.ubuntu.com
>> <mailto:ubuntu-studio-devel at lists.ubuntu.com>
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
>> <https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-
>devel>
>>
>>
>> ------------------------------
>>
>> End of ubuntu-studio-devel Digest, Vol 133, Issue 3
>> ***************************************************
>>
>>
>>
>>
More information about the ubuntu-studio-devel
mailing list