ZynewaveIt should not be necessary to buy a second PC. You can have both Podium x64 and x86 installed side by side. It does require that your plugins can also have both x86 and x64 versions installed. I don’t know if the SampleTank installation allows this. At the bottom of the following page I describe one way to have both x86 and x64 versions of plugins installed:
ZynewaveAdded two new sections in the guide for the marker and tempo menus:
https://github.com/zynewave/Podium-public-resources/blob/master/Guide/podium-guide.md#h.marker-menu
ZynewaveIf you right click on the marker or tempo lanes you’ll find a menu with ‘Select All Markers’ and ‘Select All Tempo Events’. Once selected, use the normal copy/paste menus to copy the events into another arrangement. Note that Paste will be applied at the edit cursor position, so you’ll need to place the edit cursor at the position of the first event in the arrangement.
I see that those menus are not described in the guide, so I think I’ll go add them to the new GitHub guide 🙂
ZynewaveHi Andrew,
Thanks for stopping by 🙂 Last year I linked to some of your videos on my YouTube channel, but I see you’ve made more since then. I appreciate your contributions.
Cheers,
Frits
ZynewaveZynewaveHi Tony,
The last time I received an email from you about this issue was November 2016. I sent you an email that I never received a reply to, so I assumed you had found where you could download the installer. I just now checked your account, and it appears that your original purchase of a license had been disconnected from your account. That is why you have been unable to see the download files on your account page. I found your original purchase from October 2006 in the database, and it used a different email address. I ported the old purchase database to the new zynewave.com website a few years ago, so the porting script probably got confused about the different email addresses. I have now relinked the original purchase to your account so your downloads should now be available on your account page. You may need to reactivate your lifetime license first.
Please post here when you have made progress.
Cheers,
Frits
ZynewaveThat would be ideal, but unfortunately my current shopping-cart setup does not enable me to do that. I would have to spend considerable time customizing the website php code. Also, I currently don’t keep older versions of the installer on the server. During an active upgrade period, the download page shows the following message: “The download links are only available during your upgrade period. Please keep a backup copy of the installer file.”
If you have lost the installer, send me an email with your purchase/account details, and I can send you the latest Podium version released in your upgrade period.
ZynewaveZynewaveHi Ben. It sounds like the Behringer driver is giving back an unexpected response to Podium when the device isn’t plugged in. If you are using Podium version 3.2.4 or newer, you can enable the generation of a debug log that can help me figure out why it crashes. Here’s the procedure:
ZynewaveHi Alex, welcome to the forum.
I’m glad to hear the purchase completed automatically even though there was a delay. After your purchase yesterday I received an email from PayPal saying that the transaction was under “PayPal Payment Review”, even though you were listed as a “Verified Customer” by PayPal. Today I received an email from PayPal saying the transaction was cleared.
Regards,
Frits
ZynewaveWow, every time I go to the Full Bucket website it seems he has released a new synth. All the older ones appear to also be updated regularly. I’ll probably just write ‘Various analog synth emulations’ in the list, and let the reader figure out which ones to download.
ZynewaveThanks for testing. The final 3.2.7 installer is now available.
ZynewaveBeta4 is up, which hopefully is the last beta before I release 3.2.7. This beta has a few more optimizations and code cleanup. If you test the beta, please let me know if you find any problems.
A little off topic with this, but could this update allow for multiple tracks to be selected & moved at the same time? If I import a bunch of, say, drum samples onto individual tracks, I then have to select them one by one to move to a drum group track. Not a big deal, until you have to repeat the same action 15 or 20 times. Just a workflow issue.
And maybe I’ve missed this, but a shortcut to select all events on one track would help the workflow too.
Multi-select of tracks won’t make it into this release. It’s on the roadmap, but I have a few other things I’d like to work on before that. A menu command for selecting all events on the focus track is one I’ve missed too, so I will put that in for the final 3.2.7 release.
ZynewaveQuick error report, don’t know if it’s related to the changes in this version.
Error message:
“A plugin has performed an illegal action.
[…] Twin 2 […]
This may have caused memory corruption in Podium. […]”
Plugin: FabFilter Twin 2 version 2.27 (newest at this time), x64.
This happened while switching preset from “Keys – Other – FM Piano 1 DJM” to “Pad – Soft A-M – Afterglow O” during playback of just one track. Didn’t crash Podium, but killed all audio until I powered the arrangement off. Doesn’t seem easily reproducible.
Tested this, and I can provoke the crash too. It can also crash in the previous Podium 3.2.6 release, so it is not related to the new update of the plugin loading. It seems that if the preset switch is done while a note is playing, the plugin crash then occurs at the start of the next note. I don’t think I can do anything to prevent that.
ZynewaveHi. How far should I adjust buffer size, now that I can? Or would it be best to leave at 128 default? The benefit of smoother automation makes me want to lower it a lot, but are there drawbacks to low buffer size? Sorry if I ask too much—
If you set it to 128, then the bounced audio should be identical to previous Podium versions (unless you use an even lower ASIO buffer size). Since the buffer size can affect the generated audio, I recommend leaving it at the ‘Audio driver’ setting. That way the bounced audio should be identical to what you are hearing during normal playback. The drawback to lowering the buffer size is that Reaktor will crash 😉 Other plugins may have similar problems. The bounce rendering process should also take longer with smaller buffer sizes, since the overhead of handling the buffer changes will be larger.