Zynewave@Pod_Boy wrote:
I actually got Podium to crash which is a rarity.
I have the file – it is consistently crashing. I have another file……….
like it which doesn’t. It doesn’t bother me, I worked around it.
Maybe you would be interested…..It happens when I import a midi
file from EnergyXT2………
If you mean Podium crashes when you in Podium try to import a MIDI file that was exported in eXT2, then please email me the midi file.
ZynewaveZynewaveThanks. I’m aware of this. It’s a sideeffect of the method I’m currently using for zooming beyond the end of the arrangement. I’ll fix this at some point.
ZynewaveBeta2 is up, with the following additions:
• Added “load default snapshots” and “save as default snapshots” commands to the snapshot button right-click menu. Snapshot defaults are saved in the Podium.ini setup file. New arrangements will automatically be set up with the zoom snapshot defaults, including the initial timeline and vertical zoom range.
• The default Podium setup is modified to include a set of six default zoom snapshots for horizontal and vertical zooming.
• Fix: Zoom snapshots were not copied when creating copies of an arrangement.
Furthermore, the snapshot options are now saved in the .pod project file. I removed the restriction of creating duplicate snapshots. I did not yet remove the zoom restore feature when re-clicking a snapshot button, but instead I changed it so that it should only restore the settings affected by the snapshot. Let me know if this still results in confusing behaviour, in which case I’ll remove the restore feature completely.
Zynewave@thcilnnahoj wrote:
Works nicely so far!
Thanks for testing.
#1
It appears the settings you chose for the last created snapshot are applied when you create a new snapshot. This causes more problems for me than it does good, though, as it becomes impossible to create snapshots in many cases…I think the simplest solution here would be to allow duplicate snapshots…?
Yes. I think I’ll remove the restriction of creating duplicate snapshots. It was a nice safe-guard for preventing accidental duplicates, but with the new options, it can be confusing.
#2
Clicking an active snapshot deselects it (remember this behaviour was changed for the editor profile bar buttons) – with multiple active snapshots, this can become confusing, I think.
Probably best if this is disabled like on the editor profile bar…Please see the video (with annotations) showing these two things.
Agreed. Something needs to be done about this. The purpose of clicking an active snapshot button to restore previous zoom settings, was to be able to for example select a zoomed out overview, and then click again to return to the last zoomed in view. That benefit will unfortunately become lost.
About default snapshots, it sounds good, but I can only see it working for zoom-only snapshots (which is good enough for me). I don’t see myself copying snapshots between arrangements, though – do you perhaps have an example of a situation for this?
If you have refined a set of vertical/horizontal zoom snapshots, you could then migrate these to other arrangements you are working on. The default snapshots could also include the current (non-snapshot) timeline/vertical zoom settings. New arrangements will then use these as initial settings, instead of the current fixed 4 bar range that you see when you enter the arrangement editor the first time.
ZynewaveI plan to continue working on Podium for many years. I do think that my 20 years of coding represent a significant value, so I don’t intend to release the Podium source code to public domain. I’m not that generous.
ZynewaveThanks for the suggestions. The issue with the automation lanes cluttering the track overview is something I’ll try to improve at some point.
The video you linked to in your first post seems to have been removed.
ZynewaveI have released a beta version with this feature. Please provide feedback in this topic:
Zynewave@chase wrote:
Well – i see Frits did an update… totally cool…
But… didn’t say how much for the source code…. hmmmm?
Sorry, I thought you were joking. Are you an experienced software developer? Are you rich?
Let me know how much you think 20 years of work is worth. 😉
Frits – how does Podium Process sound – Like Cubase or Nuendo or more like Premier?
I ask because the above mentioned plugin comes in two versions –
One for Cubase and Nuendo and one for Premier.So whcih would we use for Poduim? – The one meant for Cubase/Nuendo was my guess…?
Cubase/Nuendo would be my guess too.
Zynewave2.41 is now released, but without the feature discussed in this topic. As mentioned in other topics, I did not have much time for Podium development during the last couple of months. I have now started developing again, but the first few releases will just contain minor stuff and bug fixes. Eventually I’ll get back in the groove. 😉
ZynewaveZynewave@batman42ca wrote:
I figured out why I keep repeating this mistake. Normally, the timeline row is the top row. Once I enable looping or set a punch in point, the timeline row is no longer the top row. I keep forgetting and keep clicking in the top row to set the cursor except sometimes the timeline row is no longer the top row.
The loop, punch and segment rulers auto-hide when they are not active. This is done to maximize the vertical space available for the tracks. You can disable the auto-hiding in the region properties dialog for the three ruler regions.
ZynewavePodium should support up to 32 cores on a 32-bit Windows OS. Haven’t found a PC to test that yet. 😉
Zynewave@thcilnnahoj wrote:
Here’s another thing… I hope I can explain properly.
Concerning making copies of an arrangement – when you create a phantom copy, the sequences are linked in both the old and new arrangement.
A unique copy, on the other hand, converts all sequences to unique copies, meaning there are no phantom sequences at all anymore.I think there’s an option missing to create an exact copy, which has unique sequences (not linked to those in the original arrangement), but retains the relationship of unique and phantom sequences within the arrangement.
Thanks. I’ve now fixed the “New Arrangement as Unique Copy” command so that it properly recreates phantom copies within the arrangement.