ZynewaveHi,
@le N?KO wrote:
Is it something that will happen in near devellopment ?
It’s not something that I’m working on currently, so I can’t say for sure when this will be supported. I’m hoping to get to it some time in 2009.
Zynewave@H-man wrote:
Can you tell me though what control dictates the inital length of the composite track before it starts looping?
I was trying to use the loop markers howver the recording would go back to the start before the loop marker end.
Is it the punch in markers even though they are not active?
I found a silly bug which I think explains this issue. Fixed in the new beta2.
Also, when comping, what is your intened method for building the various parts on the comp track? Split up the existing comp track or delete it and create new events.
Either works fine, just curious as to your intended work flow.
I would think splitting the event on the comp track is the best way. I’m planning to extend the scalpel tool so that you can click and drag horizontally to set a crossfade range, rather than just clicking to create a sharp split.
Beta2 also has the following new feature, which I’m happy to finally cross out on my todo list:
Each recording session and each recorded loop can now be undone in a single undo step. The undo command will undo all created tracks and events. The edit is labeled as “Recording started at [time of day]” in the undo history. If you are manually editing the arrangement during the recording, a new record edit will be started after each manual edit, so that you can undo recording and manual edits in the order they occurred.
ZynewaveI’ll test DrumCore once I’m done working on the composite track feature in 2.08.
ZynewaveBeta1 of 2.08 is now available. The change-log so far:
• Added composite track feature, allowing for easier splicing of multi-take recordings. Composite tracks are handled similar to group tracks, where each take is a child track of the composite track. You can access the multiple takes from the events on the composite track. You can also expand the composite track group to make edits to the individual takes. The composite track option works both for audio and MIDI tracks.
• A track can be made into a composite track with the new “use as composite track” option in the track properties. A track is automatically converted to a composite track if looping is active during recording. The old loop-recording method of putting the recording track into a group track is thus no longer needed.
• Hovering the mouse over an event on a composite track shows a take selection bar at the bottom of the event. Clicking the bar will cycle through the available takes. Right-clicking the bar shows a popup menu with all available takes.
• Soloing a take track in a composite track group will make the take play instead of the main composite track. Pressing shift+solo will solo the take track and unsolo any other soloed take tracks within the composite group.
• Added “use as group track” and “use as composite track” options to the track properties submenu.
• The “fade properties” dialog is renamed to “sound event properties” and is extended with an “event name” setting. This makes it possible to enter different labels for track events, even if the events links to the same sound object. Leaving the event name blank will display the sound name as in previous Podium versions.
• Split the timeline ruler “zoom/slide” combined option introduced in 2.07 into two separate options.
Note that the .pod file format has been updated, so please make backups of your old projects before saving with this beta.
There are still plenty of improvements that can be made to the composite feature, so please share your thoughts.
Zynewave@Conquistador wrote:
Been trying to access this site for most of the evening..
My host provider was moving the server physically from LA to San Diego, so that’s why zynewave.com was offline for almost a day.
After some more testing the Task Manager appears to be the problem…at least in part. Plugins are much less likely to starve Podium graphically when knobs are moved…if the task manager is not open.
Leaving the task manager open was one of your suggestions though (if you are wondering) in response to a similar problem I had with Podiums CPU meter some time ago. 🙂
Can’t remember the topic, but I certainly didn’t intend to recommend that you should keep the task manager open at all times. Only open it during diagnostics of the CPU usage. The task manager uses a high priority thread to measure the CPU usage, which can lead to audio dropouts each time task manager updates the CPU graph.
Please try to disable the “enable plugin multiprocessing” option in preferences, and see if this changes the behaviour of the problems.
ZynewaveOuch. This bug is a consequence of the recent changes to the solo behaviour. I’ll make some adjustments so that this won’t happen.
Thanks
ZynewaveHave you used Drumcore successfully before with earlier Podium versions?
Does the error occur if you bounce the master, or another track?
If you try to switch to realtime bounce, does the error appear?
Zynewave@ronin wrote:
again I have two small feature request and one concerning the actual loop recording improvments.
It would be nice and useful if loop-recorded events are just one “cutted event”. In the present form the recorded loop events seem to be events with each having its own audio file attached. This means that stretching these events results in an abrupt end of the audio material since the corresponding connecting part is on the next loop track.
Usually I loop events in the arrangment and therefore I let them overlap a little bit so it sounds nice with crossfading. this is difficult at the moment.
I’m not sure I would like the multiple recorded takes to be one continuous sound. If you are not wary of this, you could end up with several huge sound files of which you may only use a small part, even if you delete the events of unwanted takes. It also makes it difficult to edit the sound, if you e.g. want to normalize one of your takes. If you want to record a tail of each of your loops, could you not just extend the looped range? Or you could drag a phantom copy of the next recorded take up to the end of the previous take, and then merge the two.
the second request is about stretching (lengthen) midi events in both directions. at the moment you can only lengthen midi events in the “playback direction”. Sometimes I want to add an upbeat or similiar at the beginning.
I’ll implement this eventually. At the time being, you need to draw a blank sequence event right before your existing sequence, and then merge the two.
Zynewave@caco wrote:
Yep it happened whether the power button was off or on.
I unistalled Podium again and then deleted the entire folder containing the podium.ini file which the uninstaller does not seem to remove. Anyway, this seems to have done the trick and I have 2.07 working 🙂
Great. Although, I would still like to find the cause for the crash.
Did you use the mouse or keyboard shortcuts to select the track?
If you used the mouse, where on the track lane header did you click?
ZynewaveI have never experienced this symptom myself, and I’m on Vista Business 32-bit.
So this can happen with just one plugin loaded in the arrangement?
Can you refer me to a plugin (freeware or demo) that shows this behaviour? If you can only refer me to a plugin demo, then please confirm that the demo also fails on your system.
Have you tried Podium on other Vista PCs with similar problems?
It would also be nice if you can grab a screenshot of the messed up screen.
Zynewave@caco wrote:
Yes, exactly the same thing happens. I also tried unistalling and going back to 2.06 but now the same thing happens with that version now as well.
Weird.
Does it happen also if the arrangement monitor/power button is off?
Try deleting your Podium.ini file while Podium is not running (save a backup of the file first). After you have deleted it, start up Podium and check if you get the crash also with the Podium default setup.
ZynewaveI’ve made this update for the upcoming 2.08 release:
The “fade properties” dialog is renamed to “sound event properties” and is extended with an “event name” setting. This makes it possible to enter different labels for track events, even if the events links to the same sound object. Leaving the event name blank will display the sound name as in previous Podium versions.
There’s no reason to implement the event naming for note and curve sequences, right?
Zynewave@caco wrote:
Hi – I have emailed you my podium.ini file. Yes, it happens before I assign any devices to it. Sounds like you may know what is wrong 🙂
I thought it had something to do with your editor setup, but your Podium.ini file did not crash for me. Please try this: Create a new project without importing plugins. Create a new arrangement without changing the default arrangement settings. Do you still get the crash just by selecting different tracks?
ZynewaveI’ve now split up the zoom/slide option into two separate options. In 2.08 you’ll be able to enable the wheel scrolling, and disable the left-click slide option.