Well im finally glad i realised what the red buttons were for on the channels in psycle.
I knew green was for solo, yellow for mute, and i knew red was record but i was always like "hmm doesn't it record notes already?".Yes and no, you need those for recording chords :P.Glad i figured it out so now i don't have to do each row one by one.
Man i feel like an idiot, iv'e been using this program for years clueless.
P.S. Just getting better from an upper respiratory infection, sorry i haven't posted in a while.
 Houston, Texas, USA
About me
the future?
Also mostly noodles go here --> My Gear
Psycle, M-audio axiom 25, korg poly 61, turntable, gameboy, casio CTK, worn out electric guitar and found sounds.
+Most Recent Blogs
|
Electronic Music other: I feel dumb...red buttons...
Store
Written January 23 2009 , Tags: psycle, record, dumb, polyphony, wow
Comments
so far i've been asked by alot of peers just starting making em about live and reason. it seems the largest barrier (and source of frustration) for beginning programmers is not knowing that "tab" means switch view. sorry to sound like an ass chaoxor, but i think if you start using a program, you should print a hardcopy of the manual and sit down and study it like you'd have to for school.
strangely whenever i buy hardware i will read the manual through, then walk through the manual with the hardware, then consult the manual constantly
but with software, if i have to go through more than just one or two tutorials, i just cant be bothered =S i think that's because software manuals are a pain in the ass to read. hardware manuals are usually paper, something you can flip through and find what you're looking for easily, whereas software manuals are usually giant pdf files that never seem to fit on your screen properly and are hard to "flip through". the search feature usually doesn't work the way you want it to, and navigating to/from the indexes/table of contents is a pain. if you've got a bit of spare change/access to a printer (that won't burn your own ink) i think it's worth it to make a hardcopy
thats actually quite true
if hardware doesnt come with a manual i will print it out then get it professionally bound with hard plastic covers and it goes on the bookshelf along with all my other prized books rather than being put in 'software manuals' several layers into my harddrive i use these guys to bind all my manuals link
I think part of the fun is the learning curve for software without reading a manual. :P
I used to think like that until I started programming seriously. Try developing software using a large library without thorough documentation and you'll figure out pretty quick why good documentation is absolutely essential. It amazes me how poor documentation for software is in general. As far as I'm concerned, you should have the documentation written even before the software is debugged. I absolutely will not deal with a poorly documented piece of software. This is why I won't use Ardour. I like to spend my problem solving energies on tasks other than the immediate problem of how the software works.
I'm a fan of e-texts, I don't use paper books for anything anymore. Try Sumatra PDF as your default viewer ( open source  ). It's fast and a low memory user. Also, UltraEdit is an excellent text editor for programmers ( commercial software  ). I find things faster with e-texts than with books. Also, I generally have the documentation open on my laptop while working on my desktop.eyesnine said: "It amazes me how poor documentation for software is in general. " true... actually, after years studying computer science, i eventually realized that coding is just half of the work (if not 30%) of developing a software. As for red buttons... yes, one should definetly read any manual of any software in use... even tho, as eyes noted, documentation is pretty difficult to write so most trick are still found only by thoroughly using a software on a daily basis. Signup to comment
|