@caco wrote:
Hi – I am unable to use 2.07 as it crashes on me every time I select a track. I was using 2.06 previously with out any problems.
I have uninstalled and reinstalled 2.07 and started a fresh project but get the same problem every time. Podium just hangs and about 10 minutes after ending the process in the task manager it eventually closes.
Anybody else had this happen? It is 100% reproducible for me 🙁
Please send me your Podium.ini file.
I assume the crash occurs even before you have assigned any devices to the tracks?
@koolkeys wrote:
So will bouncing the composite track get rid of the take tracks? If you have a long song and four or five takes, after bouncing the composite track, will the RAM be freed that all the takes are using?
Bouncing will not get rid of the take tracks. If you are sure you don’t need to do further edits to the takes, you can simply delete the take tracks. You can also move the bounced sound to a new track, and delete the entire composite track group.
This is related to the timeline ruler changes in 2.07. You need to enable the “use mouse wheel and left-click to zoom/slide” option in the timeline ruler region properties.
@koolkeys wrote:
First, it sounds like there won’t be any direct access to the take clips, but you have to select them and splice them using the comp track only? Can you expand a bit on how you would select parts of each take to composite?
So far I’ve only implemented the take selection on the composite track. I’m going to expand this so that you can do the selection on the take tracks. Maybe I’ll include the new take bar at the bottom of the take events as well, allowing for directly setting the desired take. Eventually I’ll also implement highlighting on the events on the take tracks, so that at a glance you can see which parts of the takes are active.
You’ll also be able to slice and edit the events on the take tracks, and with a command copy a take event to the composite track.
Next, I think it would be great to have a seperate button or option to bounce your composite track to a single “normal” track. In other words, a way to quickly compile the composites you’ve done into one tidy track. Or will bouncing the composite track automatically do this?
Bouncing the composite track would be the simplest way to do this.
@ronin wrote:
Usually the first takes are not very useful and I only want to keep the last (lets say) n takes. Would it be possible to have an option to configure how much take tracks are kept?
Something like “Keep the last : N takes” or if N==0 -> keep all takes. With this option loop recording wouldn’t produce too large comp folders (tracks) and the arrangement stays cleaner.
The existing “track limit in loop-recording group” setting in preferences is still valid, and defines the maximimum number of take tracks for each composite track. You can delete the individual take tracks that you don’t want to keep.
The CSPL buttons (and corresponding menus) are actually gone from the default setup in the latest 2.07 release.
I agree that it is not intuitive to have different types of edit modes, which was one of the reasons why I made the changes in 2.07.
I’ll look into this when I’m done with the 2.08 feature I’m working on currently.
@Conquistador wrote:
The changes in 2.0.6 and 2.07 are very welcome indeed thanks!
Need more time to dig into them but the timeline changes you made are a very thin whisker away from this FR configurable snap.
The Edit cursor snaps (which is fantastic) It just feels smooth and reliable. 🙂 But…it just by a tiny length falls short of the FR in that link. Can you extend the current functionality just a bit further please in 2.08? 8)
If it can be done already then excuse my ignorance. I just don’t know how 😳
The timeline changes in 2.07 were only UI changes. The change you suggest requires some work in the engine, so it’s a fair bit more than a “whisker” away :wink:. It will have to wait.
@kingtubby wrote:
I have a minor graphical bug to report though. When playing a midi sequence with the midi editor window open, the last number in the timeline disappears when the play cursor passes over it. If the sequence is looping then the number reappears when the cursor returns to the beginning.
Got it. Will fix it.
@DFusion wrote:
But if i load 2 instances at once and then select a soundset for instance 1 and make a midi loop in podiums sequencer and then tries to open instance 2 and add a soundset there then Podium just vanish from the desktop without any warning.
Still no crash for me (using the DK+ demo).
With Podium 2.05 and 2.06 i got a warning but 2.07 just shuts down and give me the desktop.
If the plugin are doing something illegal, such as overwriting memory not belonging to the plugin, then the outcome may be random. There are no changes in 2.07 that involves plugins, but just the fact that code has been added can change the memory layout, and thus cause different results with crashing plugins.
@Malcolm Jacobson wrote:
Hi Frits,
@Zynewave wrote:
- Clicking the middle mouse button in any of the timeline regions will set the edit cursor position.
I’m finding this very hard to use. My middle mouse button is a scroll wheel, so the timeline often scrolls when I try to set the edit cursor position. Is there some way I can customise the keyboard shortcuts in Podium?
Customization of keyboard shortcuts is not implemented yet.
If you are uncomfortable with using the middle mouse button, then you can still use any of the old methods of adjusting the cursor position.
I’m no expert on XT2, but perhaps there is some place in the preferences where you can specify the location of the license file?
Podium is not involved in the XT2 license file validation.
When Podium is exiting, it will “release” the drivers as one of the final steps. Thus if the driver somehow locks up during deinitialization, then Podium.exe may appear to hang.
I’ve tried the DK+ 1.50 demo. I followed your instructions and tried various other things using two instances, but I can’t get it to crash.
Maybe you could try the DK+ demo and check if you can get it to crash.