Zynewave@German Fafian wrote:
In Piano Roll select random or only odd/even notes for moving them around form a group of notes or a measure.
No random select. Either select each event by clicking, or use the marquee drag selection.
Being able to save quantize patterns (swing, shuffle, etc)
You can create your own library of patterns by saving individual note patterns to a MIDI file, which you then can drag onto tracks. You cannot apply them as a groove template.
Create an automation lane with a sine wave, saw, triangle, etc shaped automation curve for tempo based constant variatons in the chosen parameter
You’ll have to draw a single single sine oscillation, and then repeat the curve sequence event on the track.
ZynewaveThe roll back option is currently the closest you can get to this in Podium. You can activate the punch in mode on the transport toolbar, and set the punch in position to bar 2. The recording will thus only start after the one bar count-in. The downside is that you’ll have to start your song at bar 2, and just reserve bar 1 for count-in.
Zynewave@thcilnnahoj wrote:
I’ve taken a shot at rewriting most of the toolbars chapter. There’re a few things I couldn’t think of a good way to explain. Those are marked with “FIXME” icons – I’ll try to fill them in tomorrow if nobody comes up with anything.
Oooh, we need to coordinate our efforts. I’ve spent the day rewriting the toolbars chapter (offline). 😳
I’ll take a look at what you have changed, and sync it with my changes. I hadn’t yet grabbed screenshots of the toolbars, so it’s cool you added those 8) . To avoid redundant work, it’s best if you don’t add further changes to that chapter. I’ve already written a section for the track toolbar as well.
The coming week I’ll probably revise some of the other pages in the main “Editors” chapter. If you announce in a post here if you are going to revise a certain chapter, then we could avoid doing double work.
I’m also not yet entirely sure about formatting conventions and what should be capitalized – will take a look at the already existing chapters tomorrow to find out more. More screenshots are on the way, too.
Many thanks.
There are some hints about guide conventions here:
http://www.zynewave.com/wiki/doku.php?id=guide_conventions
Zynewave@LiquidProj3ct wrote:
Something like “refresh devices” or something like the option “update plugin database (with new devices that aren’t added yet)”. But you’re using the word update like ‘manage’, which I don’t know if that’s right
Point taken. I’ve updated the text, so that it now uses “maintain” instead of “update”. I could also have used “manage”.
Zynewave@LiquidProj3ct wrote:
Yes, but you cannot update the device list from that menu (I think)
When I write “update” I mean that the list can be edited, organized, etc.
What did you think I meant by “updated”?
Zynewave@LiquidProj3ct wrote:
From the manual, device panel chapter:
The device list can be updated with the **Devices** menu and the list right-click menu.
List right click menu? I don’t see nothing in that menu :S
http://www.zynewave.com/wiki/doku.php?id=guide:project_start_page#devices_list_menu
ZynewaveZynewave@LiquidProj3ct wrote:
thcinnahoj, if you add or change something from the chapters of:
-Projects
-Project windows
-Project start page
Let’s me know, because I’ve those translated to spanish and I want to keep them in sync with english version, text&pictures. If I don’t know what’s changing, I’m dead. I’ll translate the Browser Window chapter in one or two days too.
In case someone doesn’t know:
Clicking the “Recent changes” button at the upper left corner on the wiki site will show if there are changes to any of the wiki pages. Clicking the “Old revisions” button at the upper right corner shows the revision history for the current page. Clicking the glasses symbol on the revision page will show only the changes that have been made to a page.
I have updated all dialog screenshots in these two chapters:
http://www.zynewave.com/wiki/doku.php?id=guide:preferences
http://www.zynewave.com/wiki/doku.php?id=guide:editor_profiles
The text in those chapters are not up to date with the screenshots. In case some of you want to get your feet wet with wiki editing, this would be the easiest place to start. Some of the dialog settings on those two pages probably don’t need an explanation, but if you find something in the dialogs that you think should be explained, you could add an empty bullet point for the settings. I’ll then go over them later on and fill in the missing text.
A bullet point is written as space+space+asterisk+space and then the text.
Bold text is surrounded by double asterisks. An example:
* **Show sequence event headers**: blabla.Don’t worry if you mess something up. Changes can always be undone.
Zynewave@thcilnnahoj wrote:
I’ve replaced the screenshots in the getting started chapter for now. It guess I don’t have enough permissions in the WIKI to replace or delete images, so I’ve appended the date to the new ones.
I also mistakenly uploaded a wrongly named image (start_new_project_2010_07.png) – please delete. 😳
Tell me if it’s acceptable. I can also work through the many out-of-date images in the guide if you’d like, if that saves you time.
Absolutely fabulous :D/
Many thanks. That saves me a lot of time.
I can easily update all the dialog screenshots in the guide myself. If you’d like to contribute more images, you could update the editor screenshots. The arrangement editor image from the getting started chapter can probably be reused in the Arrangement editor chapter. The sound and curve editor images need to be updated. The screenshots must not be wider than 640 pixels.
Zynewave@thcilnnahoj wrote:
You’re welcome to add this if you like. This will mean that the section will wrap around on a new page. I tried to keep the text in each section short enough to fit on one page.
Well, if the idea is that the Guide is actually supposed to be a community-aided effort (apart from translations), then I’ll certainly go over some chapters and try to help out.
I assumed that it was meant as read-only, as to not get a mix of writing styles and possible misinformation in it, creating more work for you in the end (having to double-check everything).
Case in point, I wouldn’t have known that the sections were to fit on one page each.
You’re welcome to add text about features that are not fully described in the guide. I may eventually revise the text so that it sounds like the same broken English I use throughout the guide 😛
There’re also a few weird page breaks in the current PDF – how do you create it? Print to PDF from your browser?
The main guide page in the wiki describes how it is made:
http://www.zynewave.com/wiki/doku.php?id=guide:index
ZynewaveIn the future I may look into whether it’s possible to reduce some of the activity when scanning. Podium needs to load the plugins and initialize them, in order to retrieve info about whether it is an instrument and how many speaker channels, presets and parameters it supports, etc. This info is all needed in order to set up the plugin mappings in the database. Other hosts may only use the plugin filename, and then retrieve the info once it is loaded on a track.
ZynewaveRewritten the “Browser Window” chapter:
http://www.zynewave.com/wiki/doku.php?id=guide:browser_window
It describes a couple of minor new features that will appear in 2.34.
Zynewave@LiquidProj3ct wrote:
If you do a simple click in a stretch point the clip is shortened one snap value. And clips cannot be resized to its relative value if this is less than one snap value (I think this last bug isn’t too important, though)
Many drag operations will only start once you have moved the mouse a few pixels away from the clicked point. This is to reduce the risk of accidentally moving stuff when you for example click an event to select it.
When you click the resize handle, the drag operation is started immediately, to allow for small changes. Thus, if you have snap enabled, the current size will be snapped immediately.
ZynewaveI think that when you use the energy saving mode (or whatever it is called), most laptops will slow down the CPU to reduce power consumption. Some of the newer mobile CPU chips will dynamically change their speed in response to software use. The best audio performance is achieved by disabling all power saving options, but your laptop battery will run dry sooner.
Zynewave