Well, reading the description, I indeed expected it to work just like a horizontal flip function in image editing. That includes maybe having to adjust note starts on non-quantized material and such.
Because as I far as I’ve explored, it can really only be used on perfectly symmetrical (note length wise) sequences…
Don’t worry about it, though, if you and everyone else are happy with how it works! It’s just my usual nagging. π
Hmm, so you can’t reverse note “clusters” either (as in, simply swap two chords’ places on the timeline) unless they have the same number of notes (of which the note values can be swapped)…
Is there a workaround or trick to this, or is it just not what the function is intended for?
Gain strength: yes, that makes sense. Thanks for the example.
Is “gain strength” only relevant when using the absolute gain dial (the topmost one)?
Would you mind explaining its purpose to me, Frits? π³
Because the only way I can think of using it is to set it to either 100 or 0 in order to choose between applying an absolute or relative gain setting,
which seems like a strange way to handle it, in my opinion.
A bit late, but I only got to install and play around with 3.2. just now!
The adjust sound events dialog is fantastic! π
I’m having trouble with the reverse notes function though, as it seems to go crazy on drum grooves. Here’s a distilled example:
1. shows my original notes
2. is what I expected to get (judging from the function’s help text that it would simply flip notes horizontally)
3. is what it actually did
What am I misunderstanding? π
Secondly, I expected the notes to retain their velocity levels – instead, the lowest note (most quiet in the original) is now the loudest after using the reverse function.
Hey, nice to see some of the long-time users are still around (though usually quiet, it seems, like me nowadays)! :):
If you need any help rewriting Podium in JavaScript/HTML5, just let me know. π
Hi,
first off, do you want to export just this one take or render a whole song (with other instruments as well) to an audio file?
In the first case, your best option is to select the take (the audio sequence), open it in the sound editor, and select File -> Export to Sound File… from the menu. If you used Podium’s loop recording for the takes, each take should be in a separate audio sequence.
Let me know if this helps!
@bladerunner wrote:
It would make it complete if you could delete/hide parameters as so many plugins have reams of parameters simply marked as ‘unused’ or something.
Oh, but you can! π It’s a little tricky, though.
There’s a little button in the top right corner of the project page (called “Project page mode”). When you click it, it takes you to a different view of your project and all sequences/devices used in it.
Now you have to locate the plug-in you’d like to edit – first, select “Devices”, then navigate to it (remember the plug-in folder structure here is freely configurable and doesn’t necessarily have to mirror the structure of your VST folder).
For each plug-in, you’ll see a folder that says something like “Objects: 23”. If you enter this folder, then enter itssub-folder “VST Parameters”, you finally get the big list, where you can rename, reorder, or delete parameters to your liking.
Just remember that changes to parameters you delete of course won’t be recorded anymore. Unfortunately I don’t know of any way to only hide parameters, so make sure that you absolutely don’t need them before deleting.
You’ll also probably want to create a backup of your template before editing this deeply!
Did this happen in one and the same project? I just tried, and it remembers any changed names fine for me as long as it’s the same project.
Regarding changes to plug-in configurations, it’s probably best to make them in the plug-in database (PluginDatabase.pod) if you want them to appear in all (new) projects.
I’d say if you have figured out everything you need to make music, there’s no need to read the guide. Of course it won’t hurt if you do. π
Since Zynewave is just a one man show, the guide doesn’t always get updated on time. The last big cleanup and rewrite was about a year ago, which I helped out with a little.
Unfortunately neither Frits nor I have had enough time to continue working on it since then… The most noticeably missing chapters are probably about bouncing, track tags and a few nice little things not mentioned anywhere, like mixer strip zooming or the new zoom snapshot features, for example.
There’s also the video on the Zynewave.com home page that you’ve probably seen already, which might give you an appetite to try a few things.
@CDLMonline wrote:
So as you can see now I dont need Asio to use my midi keyboard…. (still funny that Asio works on VST host but not on Zynewave podium…)
Sorry if what I wrote was misleading – of course you don’t need ASIO to use your keyboard! It’s just that standard Windows sound drivers have terrible performance compared to ASIO drivers. You’ll be able to have far more tracks/plug-ins playing at once if you use them. All professional or semi-pro sound card manufacturers (RME, M-Audio, etc.) provide their own ASIO drivers. ASIO4All is just a generic driver that, unfortunately, doesn’t always work without problems, as we see here… π
Also, it’s possible to achieve much lower latency (die VerzΓΆgerung zwischen dem Tastendruck auf deinem Keyboard und dem Erklingen des Tons aus dem Computer – hast du bestimmt schon bemerkt :wink:) with ASIO drivers. This depends on the buffer size you have selected in the driver options – maybe you know about it already.
I’m sorry, I really can’t figure out what the problem with your sound card and keyboard could be… Like I said, I’ll be back in Vienna around the 20th. I could come by and take a look if you want but I can’t promise I’ll be able to make it work. π
If you have time and feel comfortable doing it, I’d say try re-installing Windows 7, especially if your current installation was done by the computer manufacturer.
I don’t think the problem is that some program is blocking the sound card… as you can see in the screenshot, Podium just can’t access the in/out channels when using ASIO4ALL – why it works fine in VST Host, I have no idea at the moment. π
Windows-wise I personally use Vista 32-bit, but I’ll try on a Windows 7 64-bit machine soon!
Thanks for the images… Sorry it’s taking so long to fix this – it seems to be a tricky problem indeed. :-k
I can guarantee that it has nothing do to with Podium Free, though!
Let’s try this simple test for now:
Please start Podium, open the MIDI/Audio Interfaces configuration window and
– first, make sure nothing is selected on the MIDI page,
– then switch to the audio tab, select ASIO type drivers and set the ASIO interface to none.
Now exit and restart Podium, start a new project and try to select ASIO4ALL in the configuration dialog.
Does it still display the message saying it can’t access your sound card?
Hmm, I could be wrong but I’m pretty sure you’ll actually only get the (stereo) master channel over USB, NOT each individual recording channel with this kind of mixer!