ZynewaveThe KeyMCE site is down at the moment, but I’ll take a look at it later on. I’m currently working on improving the Mackie emulation support, so there is a good chance it will work with the next Podium release.
ZynewaveI believe the Acousmodules plugin are 32-bit only. In case you are using Podium x64, try the normal Podium 32-bit (x86) version to see if the plugins will load.
Zynewave@thcilnnahoj wrote:
3.1!? Oooh, you’re doing that on purpose – cheating us out of 303 like that! 😉
In any case, I hope you’re doing alright!
Ooh, missed opportunity. Well, I’ll have to wait until version 6.0.6 to release that built-in drum machine. 🙂
ZynewaveI’m trying to wrap up a 3.1 release, which will feature support for using multiple control surfaces simultaneously, including those MCU emulating devices that don’t support automatic detection.
The automatic detection option on the MIDI input page has been removed, and replaced with a new “Control Surfaces” page in the interfaces dialog.
I’m hoping to have a beta ready soon.
ZynewaveSorry, this is not supported in any of the Podium versions.
ZynewaveFor reference, I assume you refer to this topic:
http://www.zynewave.com/forum/viewtopic.php?t=2531
I felt there wasn’t an overwhelming interest, so I haven’t been working on the iOS port since then. I wrote that I didn’t see Windows 7 tablets happening, which was a big reason why I started to look at an iPad port. Since then, Microsoft have started to take this form-factor seriously with the Phone 7 inspired UI announced for Windows 8. There should be a flood of Windows 8 tablets in 2012. I have done some experiments with touch support in Podium, using the multi-touch features already present in Windows 7. I bought a 21″ Dell multi-touch screen to test with. I aim to have support for multi-touch in Podium in time for when Windows 8 hits the market.
Zynewave@pbattersby wrote:
My best guess (without knowing how Podium works internally) is that the ghost notes in the drum track are currently sitting in an output buffer the length of which is not being reset when the song becomes shorter. This would explain why I can play the master bounce within Podium and the song ends when it should but when I export, I get the ghost notes (from the buffer) that are no longer part of any track. This would represent a memory leak if I’m right.
It’s not a memory leak. It’s because the wave file used to store the bounced audio does not get cropped when you shorten the arrangement. It’s on my todo-list, that a new bounce should crop the existing bounce wave file to the new arrangement length.
ZynewaveAs long as you haven’t enabled the “microsoft gs wavetable synth” in Podium interfaces dialog, then it shouldn’t matter. Don’t bother trying to delete it from Windows. It is there so that Windows can play MIDI files.
Yes, you should use ASIO drivers. If you haven’t got one for your audio card, try the ASIO4ALL.com free driver.
If you still get the MIDI input error, check if you have any MIDI utilities/programs that are automatically started when you boot Windows. Check the system tray, or the Windows Task Manager.
Also, verify that you have the latest driver installed for your MIDI keyboard.
ZynewaveHi,
Try to disable all the other audio and MIDI devices you have enabled in the interfaces dialog, and see if you still get the error message for the MIDI input.
Some devices can indirectly block other devices, which is the case with for example the “microsoft gs wavetable synth”.
Frits
Zynewave@siegfried wrote:
Is it hard to implement, Fritz?
It’s not a difficult thing to implement, but it will take some time. I have a few other things on my todo list that have a higher priority.
ZynewaveSorry, rx2 file support is not on my todo list.
ZynewaveSounds like you’ve set it up correctly if you intend to mix multiple stereo tracks into the rear channels reverb. If you only need to add the reverb to the one stereo track, then you could insert the reverb on that stereo track, and then skip the first send/return routing.
ZynewaveThe 3.0.2 release is now mentioned in the latest news section. I had forgotten to update it.
Zynewave@Infinitoar wrote:
But just a question: Have you ever thought that feature should do that? And if so, “would” you implement it?
It would mess up the underlying bounce system if the bounce file should not cover the entire arrangement length. If you did multiple renders within punch range in different timeline positions, the bounce track would include a growing number of fragmented bounce files.
ZynewaveThe project looks clean now.
Still not seing any problems when I use my RME driver. Tried the audio driver disabling, entering arrangement, enabling driver, reentering arrangement, without problems.
Do you see the problem with the latest Podium 3.0.2?
My best guess is that this is caused by a plugin. You could try to pinpoint the issue by making a copy of the project, and gradually remove tracks/plugins, until you get the absolute minimal arrangement that can produce the issue.