ZynewaveHi,
Thanks for your feedback.
@Infinitoar wrote:
As for the other things you asked: I am using a standard MME Windows Audio Drivers
If possible, avoid using MME drivers and go with ASIO instead. You’ll get horrible performance with MME, and you need to set a large buffer size to avoid pops. I added support for MME a long time ago, and I’ve kept it in case there are Podium users that don’t have an ASIO driver installed. If your soundcard does not come with an ASIO driver, you should try the free http://www.asio4all.com driver.
ZynewaveWith the help of another Podium user, I now know that it is the writing of the Podium.ini file that causes long delays with a lot of anti-virus programs. In a future update I’ll implement a different method for writing .ini files so that it won’t cause problems with anti-virus software.
Zynewave@bacon wrote:
@Zynewave wrote:
On some laptops I know that Wi-Fi or network adapter cards can cause spikes. Try disabling these.
That did the trick.
How on earth can the Wi-Fi drivers be so badly written as to take over the whole system for a fraction of a second? Or is it a problem inherent to Windows and/or the hardware?
I think it is poor driver support, but it is a common problem with a lot of laptops. I don’t know specifically why Wi-Fi drivers are prone to blocking the system for a long period.
ZynewaveI don’t plan to add support for other host drum map formats. From the files I checked on google, it appears that the Reaper .txt format is the simplest and easiest to convert to the Podium format.
ZynewaveZynewave@bacon wrote:
I get audio dropouts every few minutes. This happens whether I have one plugin active or dozens. Podium runs along at 20% CPU, or even as low as 4%, when suddenly it spikes at 100% and all sound cuts off for half a second. This happens during playback and recording, and even when the transport is stopped. It doesn’t matter if there are any audio tracks playing or only VSTis. I first thought this was a problem with my laptop’s built-in soundcard (which I used with ASIO4All), but the problem persists with my Cakewalk UA-25EX with the latest drivers from the manufacturer’s homepage. Oh, and sometimes the audio dropout comes without the CPU meter going red.
When I use the soundcard outside of Podium I haven’t experienced this problem. Admittedly, I haven’t used it extensively; I only got it earlier this week.
The spike can be caused by some high-priority system software. If you for example have the Windows task manager open, it can cause a spike each time the task manager updates its curve. If you have any background software installed, such as anti-virus, try to temporarily disable these to see if this gets rid of the spikes. On some laptops I know that Wi-Fi or network adapter cards can cause spikes. Try disabling these.
When I go into Options, change the soundcard settings, and click Apply, Podium crashes.
It have this on my todo list. I believe you can avoid the crash if you switch off the power button in the arrangement editor, before you change the sound driver in the interfaces dialog.
Zynewave@German Fafian wrote:
In that pic.
It says your outs are not connected?
Agreed. You probably just need to enable the outputs (toggle the power button on) in the ASIO4ALL control panel.
ZynewaveThe long delay when exiting Podium has been reported quite a few times. It is most likely caused by your antivirus software. If your antivirus software setup allows it, you could try to add the Podium.exe process to the antivirus trusted programs. In Microsoft Security Essentials, this is under the “excluded processes” tab.
ZynewaveIf it is the Native Instruments Kore player you are trying to use, you may find some tips in this video:
http://www.youtube.com/ZynewaveDotCom#p/a/u/0/ywp_Ih0XozM
There are a couple of other videos on the YouTube channel that show how you can use step input of notes by clicking the piano keyboard or drum map headers in the editor. Like this video:
ZynewaveThe next Podium 2.38 release will have new font options. “Font name” and “scale font size to button size (%)” settings are added to the appearances page in the preferences dialog.
Zynewave@thcilnnahoj wrote:
@Revision attempt wrote:
The track hierarchy concept applied in Podium essentially describes that the signal flow is determined by the visual track layout, making it easily apparent at all times.
I found it hard to understand this sentence. Perhaps it could be broken down in shorter sentences. When I get caught up in long sentence construction, I usually have to remind myself that many users reading the guide are not fluent in English. Other than that, I’m fine with your revision.
Zynewave@thcilnnahoj wrote:
– I didn’t add anything about how fades, time-stretching, etc. are totally unrelated to phantom copy stuff. Do you think it’s easy enough to grasp the phantom copy concept (I would assume most sequencers have something similar), or should it be explicitly mentioned that it only affects events at the arrangement editor level?
Either way is fine with me. I see that phantom events are explained. On the other hand it can’t hurt to point out that all the event properties are unique to each event, and does not affect the linked object.
Are there any more chapters that need urgent updating? Otherwise I’d like to start on a bounce chapter as soon as I find some more time. Unless Frits wants to keep it for himself. 😉
Feel free to start on a “Bouncing” chapter. I had prepared some text for the bounce submenu in the track menu chapter, but I think it is better to include this in the bouncing chapter, especially since there now is a bounce button that opens the menu. You can grab this text if it can help:
* **Enable Offline Render Bouncing**:
* **Enable Realtime Record Bouncing**:
* **Unload Plugins when Bounced**: When a bounce track is activated, any plugins in the bounce track tree will be excluded from the audio processing, thus saving CPU resources. When this option is enabled you furthermore free the memory and other system resources that the plugins may occupy. This option is mainly intended for use with large sample-based instruments.
* **Render**:
* **Render Within Punch Range**:
* **Playback Bounced Audio**:
* **Move Bounced Audio to New Track**:
* **Export Bounced Audio to Sound File…**:
ZynewaveZynewave