Need Proofreaders
2008-10-26 by tacman7bay
Yahoo Groups archive
Index last updated: 2026-04-28 23:16 UTC
Thread
2008-10-26 by tacman7bay
I wrote a PDF about my experiences configuring the BCR with the Generic Remote in Cubase. Appreciate any help/suggestions. Thanks http://tacman7.com/CubaseBCR.pdf
2008-10-27 by timandmonica
Thanks for taking the time to do this. I think the main thing lacking from the concept of current forums is a clean, ordered summary of the knowledge gained from the individual posts written by the OP. It is often difficult to browse through a lot of posts and glean the useful stuff without being overwhelmed by the overall volume of content. I gave your PDF a brief look and will give it a deeper look as time permits. If I see anything that looks like it should be changed I'd be happy to respond. Back to my first point: I think there should be an unwritten forum etiquette that expects the original poster to summarize what the answer to the question was so people don't have to browse every word of every response looking for something useful IF THEY DON'T WANT TO. Of course we can learn things we don't expect will be relevant by reading every word, but I think there should at least be the option for a "quick answer". There could be the original question, then when the answer is arrived at (no matter how complex), the OP could edit the first post, draw a long line under the question, then add his summary of an answer under the line within the initial post. I understand not all questions can be so precisely summed up, so sometimes the best way to find the answer is to read everything; that is not what I am talking about in this case, as there are many times where a summary would be ideal. Just sayin' ;-)
2008-10-27 by rpcfender
2008-10-27 by timandmonica
Royce, This is a great idea as it addresses the exact shortcoming I was trying to point out: that there is typically not a quick way to find the answer to a specified problem if you have to comb through numerous responses to a post, which sometimes repeat the same points, drift off topic, and offer partially correct info. To be clear, I was only suggesting that the original poster come in after he has a good answer, then amends his original question to include the answer. I was not suggesting that any of the topic responders to anything different. So it would just be one small extra step for the one who originally asked for the knowledge in the first place. It would certainly be a good way to give back to the community they got the answer from. I like my idea and I like yours as well. I sincerely hope people who post questions and have them answered feel compelled to share both question and answer in your new Wiki section! --- In bc2000@...m, "rpcfender" <rpcfender@...> wrote:
> > Hi all > > > I think the main thing lacking > > from the concept of current forums is a clean, ordered summary of the > > knowledge gained from the individual posts written by the OP. It is > > often difficult to browse through a lot of posts and glean the useful > > stuff without being overwhelmed by the overall volume of content. > > The forum is basically just a chat to help with specific problems. > I wouldn't want to add requirements to the reply as I think that might > put a few people off replying. > What we really need is for the person that has been helped to add to the > Wiki. > http://bc2000.pingdynasty.com/ <http://bc2000.pingdynasty.com/> > > I have noticed that there are very few contributors and it hasn't been > added to for ages. > Perhaps we could ask anyone who has been helped to add the solution to > the Wiki as a gesture of thanks? > > I have created a new section called "Problems And Solutions" > And a small section you should edit (press the [Edit] on the right had > side of the line) > > == Edit This == > Copy and paste this with your heading. Here is a [[link to your > solution]]. > Change this to > > == Edit This == > Copy and paste this with your heading. Here is a [[link to your > solution]]. > > == Where is the Power Switch == > For ages I couldn't find the power switch. Here is one opinion on [[The > Power Switch Location]]. > > > Don't be afraid. Create an account, start a new section, if you need to, > and blast away at a solution that worked for you. I don't think that > anyone would mind if you cut and pasted from the help you got here. > > Any errors will be picked up by others and corrected. This group is very > friendly and I am sure that would continue to the Wiki > The effort of writing the solution that worked for you would save a lot > of time here. > > > Back to my first point: I think there should be an unwritten forum > > etiquette that expects the original poster to summarize what the > > answer to the question was so people don't have to browse every word > > of every response looking for something useful IF THEY DON'T WANT TO. > > Of course we can learn things we don't expect will be relevant by > > reading every word, but I think there should at least be the option > > for a "quick answer". There could be the original question, then when > > the answer is arrived at (no matter how complex), the OP could edit > > the first post, draw a long line under the question, then add his > > summary of an answer under the line within the initial post. I > > understand not all questions can be so precisely summed up, so > > sometimes the best way to find the answer is to read everything; that > > Searching through the Messages is a pain even if you just read the > subject. > Please contribute to the Wiki. > How about "How to fix the drivers" or "How do I get My BC to work with > Cuebase" or "Why BC Manager is the best editor" etc > > > All the best > Royce >