Zynewave@batman42ca wrote:
I think one solution to my problem might be to connect the output of my sound card to the input of my sound card. Podium could output on midi port 10 and record from the audio in. I was just hoping there was some internal way to do that.
That may be the only solution, if you want to record the audio output of the synthesis engine on your soundcard. Some soundcards expose an alternative “loopback” audio input that you can assign to an audio track. This audio input will then record the synthesis output before it goes to the physical audio output. My old Yamaha soundcard supported this. I don’t know if soundblaster cards support it.
ZynewaveBeta2 is up, with a fix for the zPEQ display bug.
Zynewave@thcilnnahoj wrote:
It seems zPEQ got under the wheels during the restructuring:
Ouch 😯
I’ll look at that right away. I recommend everyone else wait with testing until I have beta2 ready in a few hours.
Zynewave2.40 beta1 is available with fixes for rendering latency-compensated plugins. Please post your test results in the 2.40 preview topic in the future forum. Sorry it took so long. I had started on some code restructuring that I needed to finish before I could make a release build.
ZynewaveHi Mike,
I agree that the Podium guide is written more as a reference guide than an introduction for newbies. Writing it as a reference is the quickest way for me to document features, so that at least I’m not the only one in the world that are aware of how to use certain features. If you want to change something in the Podium guide, you can do that on the wiki site. The Podium pdf guide is printed from the wiki pages. If you have suggestions for major changes or additional chapters, I suggest you post your ideas on the forum first for discussion.
Frits
ZynewaveWell, I agree this may be confusing. Podium tries to make the intelligent decision, that the input selector should be hidden from all tracks in the bus return section, since having an input assigned in the return section is useful only in rare cases. When you assign a child track as a bus return, the entire group under the master track will become part of the bus return section. Perhaps it would be less confusing if the input selector always remain visible?
ZynewaveFrom your report: ASIOStart error: -1000
-1000 is an error code for “hardware input or output is not present or available”.
So it’s not certain that the problem can be fixed by simply not setting the sample rate. Since your report does not show errors for “ASIOSetSampleRate” or “ASIOGetSampleRate”, it would appear that the driver did not report problems when setting up the sample rate.
Zynewave@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.
Zynewave@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.
Zynewave@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?
ZynewaveYou 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.
ZynewaveIf 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.
ZynewaveThe 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.
ZynewaveI’ll consider extending the hot spot area in a future update to the note editor.
