ZynewaveI’ve uploaded a beta with the WaveShell support. Please check the topic below for a list of changes and reply in that topic with any problems you may encounter.
Zynewave@blackstar wrote:
Will the auto-sizing of the bounce tracks below the master track just be to the length of their child tracks or the whole arrangement?
I think it will be to the whole arrangement. The length of the child track may not be long enough, if there are reverbs or other effects that generate audio after the child note/audio tracks have stopped.
ZynewaveThe master track is the topmost track in the track hierarchy. Its main purpose is to route the combined mix of all the child tracks to an audio output. You can select the output on the master track header. As a secondary purpose the master track is by default configured as a bounce track. The bounce sound on the master track is thus used to render the master output of the arrangement to a wave file. You can remove the bounce option on the master track if you don’t intend to export your arrangement for mp3 encoding etc.
Is there a way to get it to automatically fit to the rest of the tracks?
Not currently. I plan to add an option to the track properties that will autosize sequence/sound events to the full length of the arrangement. Bounce tracks will have this option enabled by default.
ZynewaveI downloaded the Waves 360 bundle, and it installed without crashing :o.
I’ve now implemented full support for the WaveShell feature. This means that importing the WaveShell-VST.dll no longer pops up the menu for selecting a single Waves plugin, but instead automatically creates mappings for all installed Waves plugins. I am doing some further revisions of the VST support, and I expect to release a beta in a few days.
ZynewaveIt is not forgotten. I can’t say when I’ll get around to it. Currently there are quite a few features with higher priority on the todo list.
ZynewaveToday I decided to install the Diamond 5.0 demo bundle I downloaded from the Waves website. First time running the installer, it soon exited with a request to restart Windows. This made me anxious as this was an indication that it had installed some low-level service most likely related to its copy protection mechanism. On Windows restart the installer started again, and then presented the blue-screen-of-death with a message saying: “An attempt was made to execute non-executable memory”. Unbelievable! 👿
I can then power-off/on to reboot without the installer starting automatically, but running the installer manually again results in the same BSOD. This is on a standard Dell PC, 2GB memory, running XP Pro. The PC has never had a USB-dongle inserted, and there has never been any warez or cracked software installed. I now have to live with the uncertainty that Windows stability on my PC may have been compromized by this installer.
I experienced something similar many years ago (on an older PC), also with a plugin demo that installed some protection software. This is why I since have stayed away from any Pace/iLok kind of protection. But I figured that they would have got it working after so many years. I’ll try to download one of the other Waves bundles, to see if I can get something installed that will allow me to test the WaveShell implementation in Podium.
ZynewaveZynewaveConfirmed. I’ll fix this for the next release. Thanks.
ZynewaveThanks for all the comments.
@Conquistador wrote:
I guess the more recent transparent Beta process is making it bit tricky to keep track of all the changes. I am pretty sure you have a change log of sorts to reference as you go along so maybe this just slipped through the net, unless you think this change is not really worth a mention.?!?
I’ve added your swap panel text to the original feature post. I didn’t forget about it, as I figured it could go under the “redesigned inspector” part. Still it is worth mentioning as it affects workflow and not only appearance.
ZynewaveZynewaveThe downside of that (minimal but still) is that the “Podium User Community” command/link in Podium will not work if Podium has been blocked as an application from accessing the Internet.
That command only attempts to open a website link using whatever internet browser is installed on the OS, so I doubt that you would get a warning on this.
ZynewavePerhaps I have misunderstood you here, I said before in my previous post “the scan was successful” and AFAICT Podium adds a plugin to the quarantine list automatically..how would I manually edit this file?
If you do a rescan, and the scanning skips plugins found on the quarantine list, the message box appearing at the end of the scan has an “Open Quarantine List” button. You can also open the PluginQuarantine.txt with a file explorer. The file is located in the same folder as the Podium.ini file.
The firewall warning does not seem to appear once the plugin is on the quarantine list.
Makes sense, since I’m guessing it was the quarantined plugin that was the cause for the internet access. I would guess that this plugin is using an OS service to send a crash report to the developer.
You said that “Podium does NOT contain any code that accesses the internet” but even if the plugin is the culprit to a user clearly Podium is trying to access the internet based on the information in that screengrab I posted.
Podium.exe is calling functions in the plugin dll. The dll can do anything it wants, including accessing the internet, but to the OS it will appear as if the Podium “application” is the sinner. Likewise if the plugin crashes or mistakingly overwrites memory used by Podium, it will appear as if Podium is crashing. Podium cannot prevent this. There are alternative methods of isolating plugins in separate processes to improve security, but this will affect performance.
ZynewaveI like the change but…will we still be able to access undo history?
Of course. The undo/redo menu buttons are still available, so your setup will not change unless you load the default setup. And as I described above, the standard undo/redo buttons can now also show the history menu.
Zynewavei don’t understand how your suggestion works. i look at the bar/beat in the transport toolbar but it does not indicate verse. if i look at the tempo indicator i do not see verse 1 or 2, etc.
What I described was a suggestion of how it could be implemented. Currently it is only the timesig/tempo that is shown in the transport toolbar. This field could be widened to show timesig/tempo on the bottom line of the field, and marker name on the top line.
i also noticed that if the engine is not running and i move the time line…. the marker name changes at the left time sig/bpm each time the marker passes. this is the way i think the marker should work?
Both the marker name and the timesig/tempo written to the left of the lanes are hints to the events prior to the start of the zoomed time range. This is useful information when you are editing events on the timeline. Your request to see the marker at the play cursor is useful during playback, hence my suggestion that this info could be shown in the transport toolbar.
Zynewave@sam c wrote:
frits, the diamond bundle you are demoing must be 5.0 or 5.2. as i said, there is no problem there. it is new plugs that are 5.7 and higher.
SAW, reaper and tracktion are accepting these new plugs. both saw and reaper developers also do not have ilock. i only mention this to indicate there must be a way to overcome this…….i hope.
do you want a copy of my waveshell 5.7 and 5.9.5?
I’ll have a look at the waveshell technology once the 1.96 release is done. If it is not too timedemanding, I’ll try to add native support for the waveshell.
I doubt that having just the 5.7 waveshell will help me, and I also fear it could corrupt something if I try to mix a regular waveshell dll with the Diamond demo plugins.