Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterI 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.
September 17, 2010 at 11:59 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@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.
ZynewaveKeymaster@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.
ZynewaveKeymasterThe 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.
ZynewaveKeymasterIf 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:
ZynewaveKeymasterThe 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.
ZynewaveKeymaster@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.
ZynewaveKeymaster@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…**:ZynewaveKeymasterZynewaveKeymaster- MIDI files can be auditioned in the browser, and dragged onto the note editor.
- Insert key can duplicate a multiple event selection.
- Improved realtime bounce recording.
ZynewaveKeymaster- Bypassing inputs only disables monitoring and not recording.
- The width of mixer meters resize with the zoom setting.
- Mixer faders can be adjusted with mouse wheel.
ZynewaveKeymaster@thcilnnahoj wrote:
@Zynewave wrote:
@thcilnnahoj wrote:
Quick question: What’s the reason the meter isn’t moved to the bounce track after bouncing? If you disable bounce playback you’ll get a pre-fader reading unless you set it manually.
If the meter is set on an effect track below the bounce track, then the displayed meter will automatically switch to the output of the bounce track when bounce is enabled. Otherwise the meter would be inactive. When you deactivate bounce playback, the meter reverts to show the output of the configured meter track. I think this behaviour is better than actually moving the assigned meter to the bounce track when enabling bounce. Or did I misunderstand what you’re saying?
Perhaps it does make more sense… If you’re only using bouncing to freeze tracks, though, you’ll get a ‘wrong’ reading when you disable bounce playback, as the fader position is moved to the bounce track, but meter position stays pre-fader.
Here’s the scenario:
– You have a track without effects that peaks at -6 dB, track gain is also set to -6 dB. The meter shows -12.
– Bounce the track. The fader position is moved to the bounce track, the meter is now set pre-fader (just not during bounce playback) and shows -12.
– If you disable bounce playback now, the track’s meter shows -6 dB.Ok, now I see what you mean. Yes, the meter should actually be assigned to the bounce track, like the fader is. Enabling the bounce track should behave just like when adding a new effect. I’ll look at that tomorrow, and then release 2.37. If you have further bug reports, please post those in the 2.37 preview topic, as this topic will be locked when 2.37 is released.
ZynewaveKeymasterHmm. I haven’t made any fixes on this issue yet. I still have this topic on my todo list.
@thcilnnahoj wrote:
hmm. What would you think about having additional submenus for all effect tracks’ parameters in the track context menu parameter submenu?
This way you’d have access to all parameters in the track effect chain when the individual effect selectors are not visible.
I think that can become a bit overwhelming. But I’ll consider it.
September 7, 2010 at 01:06 in reply to: Preview 2.37: Changed input bypass and meter behaviour. #19422ZynewaveKeymaster@thcilnnahoj wrote:
Frits, have you thought about using some sort of logarithmic scale for mouse-wheel fader adjustments? You can try it on knobs in FabFilter plug-ins – I find it to be super-comfortable!
I could just remove the code I put in to make it snap to full dB steps. I thought it convenient that each wheel click adjusted a fixed dB. Easy to set the fader to -3 or -6 dB for example. Do anyone prefer the wheel to adjust in proportion to the fader range, rather than in dB steps?
Also, shouldn’t scrolling up on a pan control move it left instead of right…? After all, the highest (top) value in pan curve sequences and on pan parameter faders is 100% L.
There are pros and cons of both methods. The reason I chose down to be left, is because it then matches how you adjust horizontal gain and send sliders. I think it would be weird that using the wheel over a pan slider would make the knob move in the opposite direction than gain/send sliders. Perhaps it is the pan parameter that should have L/R swapped :-k