Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@pj geerlings wrote:
What features will be delivered next?
The development path some times twist and turn in mysterious ways. Mostly it is prompted by discussions on this forum. I’m happy to follow these byroads, as long as I feel it leads in the same overall direction. I’ve previously made predictions or promises for what new features I’m going to work on next, only to find that the development focus shifts to something else. It pains me that I always have to disappoint some users, so I no longer make any promises as to what lies beyond the next version. All I can say is that on the surface, 2.40 will be a minor bug fix version. Under the hood, 2.40 has a lot of code “housecleaning” that I needed to do in preparation for things to come.
November 29, 2010 at 00:06 in reply to: Initialisation problem with Alesis MultiMix 16 Firewire #19886ZynewaveKeymaster@duncanparsons wrote:
Is there anything I can do to help with this? Debug version, etc?
I imagine I could spend several days trying to figure out what the problem is with the MultiMix device. I’d rather spend that time implementing support for the new Windows Vista/7 WASAPI audio driver model. Which Windows version are you using?
If I can avoid it, I prefer not to mess with the ASIO driver handling, as there is a real chance that changing the behaviour to suit MultiMix would break compatibility with other devices.
November 18, 2010 at 22:32 in reply to: Initialisation problem with Alesis MultiMix 16 Firewire #19849ZynewaveKeymaster@duncanparsons wrote:
Because I always have a number of projects on the go, I don’t update my main machine terribly often, only when there’s something I NEED. So I’ve been running v1.80. I’ve updated and now running 2.38 (for some reason 2.39 wouldn’t download).
1.80 is almost 4 years old :shock:. A lot of things have happened since then. I’d prefer not to backtrack my code changes for 4 years, to try to determine which update may have changed this behaviour.
I just tried downloading 2.39 and had no problems. Maybe just try again?
Does it show the error dialog also when using ASIO4ALL and Wave drivers?
ZynewaveKeymasterYou are not forgetting anything. Record enabling a track will mute it, even if you specified a punch range. In a future update I may implement playback of audio outside the punch range.
ZynewaveKeymasterIf you want to play on multiple MIDI channels on a VSTi, you need to set it up as a global multitimbral instance. If you just want to get the MIDI sequences onto a child track, but still only play on a single MIDI channel, you can convert the VSTi track to a group track, add a child track, and move the MIDI sequence to the child track.
ZynewaveKeymasterThe way I would do it:
1: Bounce the master track. You can opt to set the punch-in/out to limit the bounce range, in case a full track bounce render takes more time than it takes you to set up the punch-in/out locators.
2: Move bounced audio to new track.
3: Select the new sound event, and open the embedded sound editor.
4: Use the select or segment tool to mark out the range you want to export. This could be the loop range, which will be highlighted in the sound editor.
5: Use “export selection to sound file” in the sound editor file menu.
6: Delete the bounced track.
Is this still a showstopper? It may take a few more steps than an “export only loop range” option in the export dialog, but on the plus side it allows you a bit more freedom in what you want to export. You could for example quickly drag the segment selection to other bars, to export multiple loop files from the same audio bounce.
ZynewaveKeymasterI’ll consider extending the hot spot area in a future update to the note editor.
ZynewaveKeymasterI’m not happy with the way the library preset system works. It can be quite confusing that a preset that is assigned on a track is dynamically updated with changes in the plugin.
I plan to replace the library preset system with a disk based system using fxp/fxb files. Working similar to how track template files are managed. That will also mean the presets are accessible across projects. I recommend you use the “save preset file” or “save bank file” commands in the preset menu instead.
ZynewaveKeymasterIt’s possible that the transport buttons will work.
Currently you can’t use the faders to control the Podium mixer. If you use plugins that support MIDI learn, you can use the faders to control the plugins.
ZynewaveKeymasterThat was a bug that appeared in 2.38. It should have been fixed in 2.39. Let me know if you still see the bug with 2.39.
ZynewaveKeymasterThe competition is now closed. Thanks for all the contributions.
There were 11 replies. Using a range of 1 to 11 on http://www.random.org I got a random number of 4. Counting the posts from the start, this means that ansatheus is the winner of the free license. So, congratulations to ansatheus. =D>
To all the other competition participants: If you purchase a Podium license before the end of this month, I’ll give you an additional 1-year upgrade period for free (value 35$). That is a total of 2-year free upgrades for 50$.
ZynewaveKeymasterI’ve identified the problem when bounce rendering with plugins that introduce latency. I’m working on a fix for that. Whether this fix solves all reported bouncing issues remains to be seen. I expect to have a 2.40 beta ready for the weekend.
ZynewaveKeymasterHi rickshapiro,
Since this topic, I have not received additional feedback on the 01X. If 01X driver updates during the last five years haven’t changed the behaviour in Podium, then I can only suggest using ASIO4ALL. I believe the ASIO4ALL driver allows setting up multiple stereo I/O pairs, but I have not tried this myself.
ZynewaveKeymasterHi accordo. Thanks for the feedback.
@accordo wrote:
I was wondering if in the Pianoroll Editor Profile custom choices, the behavior of the mouse could be expanded. For example the Slide tool could be engaged by the RMB by simply detecting the initial movement of the cursor to bypass the right-click menu (similar to the iPhone in terms of detection/engagement).
Your suggestions for enhancing keyless mouse operation are welcome. At some point I’m going to enhance multi-touch operation of Podium.
One issue I see with using right-click+drag for sliding, is that currently any clicked events are selected on button down. That is the standard Windows behaviour when right-clicking objects. I think that needs to be changed, so that the objects only gets selected on button up, simultaneously with the menu popup. Or would it be ok if the right-click slide tool would affect the selection under the cursor?
Only if the mouse is moved a certain distance (4 pixels is the Windows default) will the slide tool jump into action. This is necessary, or else it would be very hard to reliably open a menu (unless you use a trackpad instead of a mouse).
For the most part, the Slide tool compensate for the scrolling of the wheel which could be use (by preference) for zooming in/out (Slide is faster and more natural than scrolling IMHO by reflecting the real world of pencil and paper hands movements).
This would allow to use the mouse in the pianoroll for writing, deleting, moving notes, right-click menu, zooming in/out and sliding without using any modifier keys.So you would like an option to change the default mousewheel action to do zooming instead of sliding?
Frits
ZynewaveKeymasterIt’s on the todo-in-the-future list. Simple note loop-recording would not be difficult to implement. It’s a bit tricky if it should support loop recording MIDI automation such as pitch-bend or modwheel, as that would require some new mechanism to handle parameter child tracks of each loop recorded note track.