Zynewave's Forum Page

For 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.

As 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.

@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.

Sounds 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.

@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.

Thanks for the video. You’re not doing anything wrong. It’s just that the render within punch range is meant to work a little differently. What you expect is that the underlying track bounce file will be the size of the punch range. In fact, the underlying bounce file is always the full length of the arrangement. If you for example work with a long track with heavy plugins that takes a long time to render, you can use the render within punch range to just render the part on the timeline that you are currently working on, thereby greatly reducing the time required to render.

Instead of saving the bounce, reimporting it and cropping it, you could use the “move bounced audio to new track”, split the event on the new track, and use the “convert to unique cropped copy” on the fragment.

@duncanparsons wrote:

I fear it’s the latter so I’ll have to save fxbs of current settings, remap to the devices first in the VST tree, import the fxb, then delete the unwanted nodes.. would I be right in that assumption?

Yes. Sorry about that. I guess the reason you ended up with multiple Devices folders, is that you used the deprecated import feature found in older Podium versions. The merge project command replaced the import command, and it handles remapping mappings from the merge project to the mappings in the current project. It does not handle remapping redundant mappings within a single project.