ZynewaveZynewaveZynewaveZynewave(I don’t know how to send you a regular email)
The email-address is listed on the contact page.
When I load your project they appear as in your ‘old’ screendump. If I change the sample-rate in the arrangement properties from 48000 to 44100, then the automation curves will appear like in your ‘new’ screendump. Could you verify that your problematic arrangement is set to 48000? Changing the samplerate will however also scale the audio events, which you say are ok. Are your soundfiles recorded in 48000?
One of my items on the future plan is samplerate conversion. Currently you need to have your soundfiles in the same samplerate as the arrangement is configured to.
ZynewaveThat is indeed weird. I don’t recall changing anything in 1.31 that should influence this. Could you email me your ‘good’ project file, without the wave files?
On the PC where you went from 1.31 to 1.30, did you save the project with the 1.31 version?
ZynewaveSo turning off the waveform should help ?
Yes it would. But I’d rather spend time on optimizing the waveform display. It should be possible to make the graphics very smooth.
Zynewave@acousmod wrote:
when we move the slider of an automation parameter (mixer or vst) for setting the values while in pause, the point is always recorded as Bar, even if it is the Line mode which is selected in the curve editor. This is very annoying, especially for volume envelopes…
What do you think about Frits ?
The edit mode of the curve editor has no relation to the actual curve sequence, so the mixer cannot use this setting to decide the type of event it should create.
I can imagine certain situations where you would want to create bar events, if you e.g. are using level automation to mute certain passages. What I could do is to create a bar/curve point depending on the type of the neighbouring events in the curve sequence. If you start with an empty curve sequence, the first event created will be a bar event. If you go in and convert this to curve events, then subsequent mixer fader movement will create curve events. This would apply both when playing and when stopped. Good solution?
ZynewaveI think it is the graphical waveforms of the audio files that are the major cause for the slow graphics update. I don’t think the meters are to blame. Try to hide the audio events, either by sliding them out the top of the window or by maximizing the mixer region. Does the mixer meters then become more responsive?
I will put on my list that the audio event drawing should be optimized.
ZynewaveGenerally I try not to make any promises of when certain features will be implemented. There are a lot of feature requests being made, and putting a time estimate on all of them will just put me under a lot of stress. The development plan is changing frequently too, which futhermore makes it difficult to set deadlines for major features.
The things you mention here is on the plan, but I don’t think I will have all of them ready for the end of June.
Zynewavedoes each vocal track need to be wrapped in two tracks for each FX?
If you want to apply different Comp and EQ to each vocal track, then yes. Enabling the use of multiple plugins on a single track is high on my list, but it will require some careful design and so will take a while before it is implemented.
I create a group track for the vocal track, which has a compression plug on it which flows upwards towards another second group track which has an EQ plug in it…correct?
Yes.
Is there any other way to create track FX in Podium without having to create a group track for the FX? For instance, dragging an insert FX directly to the track without having to create a group track?
You can drag mappings onto the bottom blank area of the tracks region to add a new track with the plugin. Dragging a mapping to insert between tracks is not possible yet, but I will be working on that later on.
So are FX only added to a track by wrapping an instance of the FX around a track?
Yes, but it is only necessary if you have mappings further down the hierarchy that is feeding the effect. Tracks with audio events can have the effect mapping assigned directly on the track.
Also is there a limit to the number of FX a single track (wrapped around another) can have?
The engine can handle any number of cascaded effects. The UI limits the maximum track group level to 9.
ZynewaveNot available currently. I’ll put it on the list.
ZynewaveI just tried installing Podium on my D: drive, and I get the same error. I’ll get this fixed for 1.32. The guide files are still installed to the correct place, so you can open the guide with the ‘Podium Guide’ item under the Zynewave group in the Windows start menu.
Thanks.
ZynewaveThe guide should be located at:
C:Program FilesZynewavePodiumDocumentationguideindex.htm
Could you check if the files are there on your system? Have you succeeded in opening the guide in the previous demo versions?
ZynewaveI actually had planned to start experimenting with docking the note/drum/curve/sound editors inside an arrangement editor. I don’t know if it will be ready for release 1.32.
ZynewaveMIDI notes go from 0 to 127, so the max possible transpose is -127 .. +127. Limiting to a more reasonable range like +/-4 octaves (-48 .. +48 semitones) would make it easier and more precise to set the transpose value with the dial.