ZynewaveHi Stephen, and welcome to the forum.
@darthstephen wrote:
also, podium crashes when i change the input sound driver before the output driver.
I could not reproduce this bug. Could you be more specific about how you provoke the crash?
Zynewave“Add ‘Abort’ button to sound copy/processing progress dialog box.” is added to the future list. It will require that all copy/processing is done in a background task rather than in the UI task, so it will take a while to implement. Doing this in a background task will also get rid of the frozen UI/white windows that you’ve mentioned you get when copying very large sound objects.
ZynewaveI’ve added ‘select all from cursor’ to the edit menu. Will appear in 1.61.
ZynewaveI still haven’t purchased the additional development tools, but I think I have delayed looking into this problem long enough. After the next release, I’ll start on this. I have created a test arrangement with 30+ stereo 16-bit files, which causes drop-outs on my system when starting the arrangement. This should be a good starting point to research various optimization solutions.
ZynewaveBut what is the reason for the auto extending?
The reason to implement the auto extending was mainly to allow recording without having to manually create the events beforehand. However, I can see your point that if you stop and restart recording at a later time, perhaps the previous event should not be extended, but rather a new event created that will be auto-extended for the duration of the recording. Anyone else have opinions on this?
And will the part in between consume space on my hard drive?
Yes, if a single event covers a section with silence, then the silence is stored in the wave file.
ZynewaveWe emailed back and forth a couple of times. Holger apparently figured out a way to avoid the problem. I’m glad that it is working too ❗
ZynewaveThere are a couple of ways you can get around it. You can enable punch-in and set the punch-in start position to where you want the second sound event to start. Or you could double-click to manually create a sequence-event at the desired position. If you start recording where this event starts, then the previous event won’t be extended.
Zynewave@Podianer wrote:
Perhaps we all could contribute to that..
The “tutorial” that is made sticky here in the forum could be opened. Then we could all start to gather hints, or tips, FAQ or even tutorial projects for certain “operations” in podium. There could be pictures to underline the certain workflow. Frits could intervene if something is described the wrong way for example. I’ve seen a similar thread over at KVR concerning eXT.
How is that?
Today I surfed the web for some easy-to-use Wiki solutions. There are almost too many alternatives to consider 😯
There are some pretty advanced packages, many which are based on MySQL databases. A tempting example is the MediaWiki, which is used for http://www.wikipedia.com. However I am going to have a look at some simpler text-based solutions, such as: PmWiki, TWiki and DokuWiki. Anybody have any Wiki experience or recommendations they want to share?
ZynewaveIs there a way to import the whole midi arrangement for a project and using the drumlayout without having to re-do the whole she-bang over and over for each project?
If you import your MIDI files in the browser page, you should get an arrangement with a track layout similar to how you saved the MIDI file. You could then copy the ‘drum group’ track from your template arrangement (collapse the group before copying, to copy all tracks in the group), and paste the tracks into your imported MIDI arrangement. Then just move the MIDI drum sequences to the ‘ezdrummer midi’ track.
Zynewavesince there’s no “Podium Power” book out yet.;) Maybe it’s too early?
I’m looking forward to reading a Podium Power book too ;). Hopefully some day someone will find it worthwhile creating alternative documentation, and make some money selling it. It’s hard for me to find the time to expand on the documentation. There’s just so much coding to do still 🙂
As far as I can tell, the only difference in your two layouts, are that one has all the tracks inside a group track. Either is fine. The group track version is preferrable if your arrangement contains a lot of other tracks.
I also notice that you have placed the MIDI channel tracks as children of the audio output tracks. That would only make sense if your plugin is set up so that anything played on MIDI channel 1 is only output on 1+2, and MIDI channel 2 only output on 3+4 etc. Otherwise I would recommend putting all audio and MIDI mappings on the same group level.
ZynewaveI read on KvR that a new beta is due tomorrow. Let me know if this still has the problem, and I’ll try it out.
ZynewaveZynewaveThe output level of a bounced track should be exactly the same as the level when bounce is deactivated. The gain you set on the bounce track will be applied to the bounced audio.
Another thing that can influence the level is the mono panning law. If your drum output mappings are mono, then the default -3 dB law will reduce the centered mono signal by 3 dB. Some sequencers (I don’t know about Cubase) will instead boost the signal when panned left/right.
Does the fact, that Podium creates 32 bit files during bouncing, has something to do with it?
That should not have any influence on the level.
ZynewaveSo it would require a specific “event name” ?
Yes.
For example, if I make a (phantom) copy of an audio event I will be able to set different fades and volumes for each one witout having to copy the sound datas ?
Yes. Event fade-in/out will be properties of the event and not the linked sound.
ZynewaveWhen we split a long file in different sequences, it is very usefull to give different names to distinguish them
When you split one file into several sequence events, are you using phantom copies or are you creating new unique sound objects?
The name you see in sound/sequence events on tracks are the property of the sound/sequence object. The name is not stored as part of the sequence event. Phantom copy events thus show the same name.