I’m sorry to report another problem with my most favoured Synth1.
Since this release it just ignores most settings (like panel size and colors) in its OPT dialog – they reset as soon as I ‘OK’ it. It also seems to have forgotten its patch bank locations, though it loads with the correct patches in existing projects.
I’d be very sad if compatibility with this was lost… 😥
@thcilnnahoj wrote:
I’m sorry to report another problem with my most favoured Synth1.
Since this release it just ignores most settings (like panel size and colors) in its OPT dialog – they reset as soon as I ‘OK’ it. It also seems to have forgotten its patch bank locations, though it loads with the correct patches in existing projects.I’d be very sad if compatibility with this was lost… 😥
Just tried Synth1 with 2.18. I still have the old problem with the disappearing MIDI options page, but I had no problem setting panel size and color. Changes to these settings were recalled correctly also after restarting Podium.
Hmm… it won’t let me change anything in normal mode (Vista 32-bit).
For the time being, I got my settings back by running Podium as administrator and then setting it up. However, this way Synth1 is now forced to use specific settings in Podium, whereas they should normally apply globally to all hosts it’s loaded into (not a problem for me).
Another little thing, though not related to this particular release:
MIDI patterns drag-n-dropped from Addictive Drums (the only plug-in I have to test this) are created in Podium only up to the end of the last note.
That means they’re almost always an 8th or 16th short, so I have to extend them by hand in order to duplicate them easily.
I tried with energy XT 2 and Ableton Live Lite 7, where it works fine. So I guess it’s probably something on Podium’s side.
One more:
Font anti-aliasing for the time/beat counter on the transport bar has become pretty bad compared to 2.17 and before, at least on my system.
(Comparison image with Big Transport setup)
@thcilnnahoj wrote:
One more:
Font anti-aliasing for the time/beat counter on the transport bar has become pretty bad compared to 2.17 and before, at least on my system.
(Comparison image with Big Transport setup)
Thanks. I’m fixing this now.
Btw. Be sure to check Synth1 again in the next Podium release. As mentioned earlier today in another support topic, I’ve changed some build settings in the new compiler tool so that UAC is no longer enforced. I think it’s likely this fixes the Synth1 problem.
It is not possible to add a device via drag and drop to an empty folder in the device list on the project page. It is possible if the folder holds at least one item. This makes the reorganization of loaded plugins/devices more complicated as it could be.
Is there a reason for this? Or is it a bug?
@swindus wrote:
It is not possible to add a device via drag and drop to an empty folder in the device list on the project page. It is possible if the folder holds at least one item. This makes the reorganization of loaded plugins/devices more complicated as it could be.
Is there a reason for this? Or is it a bug?
The reason is that it would not be possible to insert a dragged object between two folder objects (i.e. under the same parent as the folders) if it should always add it as a child to the folder.
If you hold the control key when you drop an object, it will be added as a child object of the object you drop on. This works for all object types and not just folder objects.