Instead of starting with a standard interface, I would simply begin with the ‘recommended interface’ and proceed to show key features. John graciously allowed me to share his reply which reads as follows, "Yes, training would be impacted, but only the starting point would be different. I recently asked John Fallahee of who has trained thousands of Logos users of all levels from brand new to advanced how toolbar customization might affect his job as a trainer.
#Reason 9.5 beta update#
In addition, in the last couple of years whenever an especially significant software update has occurred (8.7 Context Menu, 9.1 Factbook) Morris Proctor has made available free webinar videos nearly simultaneous with the update release. Every new Logos version that comes out requires new training videos and some effort to learn. I do not believe toolbar customization (everything on the toolbar hideable based on individual user preference) would present any insurmountable training obstacles. Within their toolbar customizing menu they include a “Reset” button to restore all default toolbar items. Perhaps within Program Settings a section could be added titled “Toolbar” with everything on the main toolbar listed along with the “restore defaults” option James suggests.Īccordance has allowed everything on their main toolbar to be hideable for a long time and it appears to be very popular with their users. I especially like the idea of a “restore defaults” option. New users would most likely want to become well acquainted with all elements on the toolbar before deciding what to customize. As for new users, I agree with James’ comments. If Faithlife decides to add toolbar customization, I would not want to be limited in what I could choose to hide. Thank you for the opportunity to provide this feedback. This very distracting bright green Go button hurts my eyes and since its introduction in Logos 8, I’ve had to hang a small cloth strip from the top of my monitor to cover the button while I use the program. I would especially hide the Go button and use the keyboard enter key instead which is already possible. If given the opportunity, I would hide the Store button if it remains as well as the Home, Factbook, Sync, and Profile Menu buttons since I never use any of these. Toolbar customization would also solve the problem of the main toolbar already being overcrowded. If Faithlife simply removes the Store button from the main toolbar, the objections expressed in this thread about this particular button would be resolved, but what happens later when something else just as objectionable or more is added to the toolbar? Allowing everything on the toolbar to be hideable based on individual user preference would not only solve this issue but any future one. I believe the ideal solution is toolbar customization in which everything on the main toolbar is hideable based on individual user preference. However, in its other location within the Library, I can understand how it would be beneficial to some users. I share the concerns expressed in this thread about the Store button and I hope users are allowed to hide it or it is removed from the program’s main toolbar. I don't think I will get that second wish but the first one would be popular.I am not a beta tester but have been following this thread with great interest. I would like to see some sort of chord tool like Chord Track like Cubase has and personally I would like a more user friendly drum programmer like the Redrum in Reason. I hope Sonar can pull a few tricks out of its own bag this year too. This is going to make Reason a lot more popular and even bring old users back. Ozone on the master channel which you could never do before.
Now technically I should be able to finish off my songs in Reason now. It will be interesting to see how things are in Reason 9.5 with VST support.
As I always start songs with the Drums my workflow just fell into place. The mixer in Sonar is better but the Redrum in Reason is just excellent at programming drums. I use to create projects in Reason and use Sonar to finish them off. I always found Reason easier to use from day one but I needed Sonar for the VST support. At that time it was Sonar 7 and Reason 4.
0 kommentar(er)
