Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@pquenin wrote:
OK. Do you know when midi plugins will be supported ?
I don’t know. I’ve tried giving out time estimates for new features in the past, but these estimates seldom come through. Feature suggestions and discussions on the forum often makes me change the focus of the development.
In the plugins preferences, what is “Enable recording of VST plugin MIDI output” for ?
If you for example have a pattern based drum plugin that supports output of MIDI notes, you can use this option to record the patterns as a note sequence on a Podium track. You can then reuse the pattern on other tracks.
Do you plan to improve the midi controllers support (a tool where we can make and save our own mapping to the Podium functions : transport and mixer) ?
I do plan to extend MIDI controller support, but again, I can’t give you a time estimate.
ZynewaveKeymasterYou could try placing the 700 MB sound file on a track, use the scalpel tool to split it up in the pieces you want, select all the pieces, and then use the “Convert to Unique Cropped Copy” edit menu command.
If you want to avoid the undo history issue, you could also select the segment you want in the sound editor, and then use the “Export Selection to Sound File” file menu command.
ZynewaveKeymasterVST midi plugins are not supported yet.
If your MIDI controller supports sending stop/start MIDI real-time messages, then Podium should respond to those. Loop and record mode cannot be controlled with the real-time messages. For that, you’ll need a Mackie Control Universal compatible controller.
ZynewaveKeymasterThe toolbars chapter rewrite is now done:
http://www.zynewave.com/wiki/doku.php?id=guide:toolbars
I’m currently writing on a couple of new editor chapters with the titles: “Zooming & Sliding” and “Editor Menus”.
ZynewaveKeymaster@LiquidProj3ct wrote:
Getting started–>Mixing–>Last paragraph:
The bus send sliders will control the level of the “wet” signal that is sent to the busses. The gain fader on the track will control the level of the “dry” signal going out of the track.
I think it should be:
the level of the “dry” signal that is sent to the busses
or
the level of the “wet” signal that is come back from the busses
or delete the words “wet” and “dry” and everything will have sense:
@fixed wrote:
he bus send sliders will control the level of the signal that is sent to the busses. The gain fader on the track will control the level of the signal going out of the track.
I did not swap dry/wet by mistake, but I can see why the description can be confusing. I’ve changed the text, and removed dry/wet references.
ZynewaveKeymaster@thcilnnahoj wrote:
If you announce in a post here if you are going to revise a certain chapter, then we could avoid doing double work.
I’ll do that – but maybe a new topic (in the VIP lounge?) would be in order as to not bump an older preview thread. For now, I’ll try to replace all old screenshots I can find.
I think it’s ok to keep posting about guide updates in this topic, until I create a new preview topic.
Thanks for the screenshots 🙂
ZynewaveKeymasterThe disk activity is because Podium stores the part of the 700mb that you crop away into the undo history. In order to “fix” this, I’ll need to implement a new “maximum storage size used by undo history” setting next to the existing “maximum sequence/sound undo levels” option. This would mean that if you crop away wave data beyond the set maximum size, you would not be able to undo the crop action.
I’m not able to import the full file again from the file browser, everytime I import it I only import the cropped loop (and I cannot slip edit it), but the 700 is there, because I can hear it with browser’s preview
If you try to drag in a sound file that is already imported in the project, the import is skipped. So the sound object that you cropped is still the one used, although it has not been saved to file yet.
ZynewaveKeymaster@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.
ZynewaveKeymasterThe 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.
ZynewaveKeymaster@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_conventionsZynewaveKeymaster@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”.
ZynewaveKeymaster@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”?
ZynewaveKeymaster@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
ZynewaveKeymaster- Updates to the Podium guide and minor UI improvements.
ZynewaveKeymaster@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_profilesThe 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.