ZynewaveZynewaveok done with bouncing (so easy)
Great 🙂
i tried to desinstall podium and reinstall but it was not reset and i didn’t find any .ini file
Reinstalling will not overwrite your setup file, otherwise your soundcard setup etc. would be reset when installing new versions. To reset the setup to defaults use the ‘Load default setup’ setup menu. After this you need to reconfigure your MIDI and audio setup.
ZynewaveIf you have not read it already, then check this page in the guide:
The freebees demo project is prepared for bounce recording. The wave files are initially empty (to minimize download size of Podium installer) so you have to bounce record to create the wave files. Assuming that you have the plugins installed; enter into one of the songs. Turn off looping and switch on the record button. The tracks containing the bounce audio events should be red now. Start playback. The audio should now be rendered into the audio events as playback progresses.
Once you have recorded the entire song, switch off the ‘R’ (record enable) track buttons for the bounce tracks. This will enable the bounced audio and the plugins will become inactive. You can then use the ‘B’ (bounce) track button to switch between listening to the bounced audio or reactivate the plugin output.
ZynewaveI would like to be able to point to where I want to paste an event or sequence of events on the seuqencer, right click, and have it past right where I am pointing. Currently, right click paste doesn’t work unless I am pointing at an event already there, and then it pastes it over top. Not a big deal, but I would find it easier.
A paste or insert will be placed at the start of a segment selection, and if no segment is selected, then at the current cursor position. I’ll add a ‘Insert here’ kind of menu to the future plan.
Already on the plan is support for MIDI output for VST plugins (e.g. Groove Agent note patterns). Once this is done then VST plugins could actually be used as pure MIDI plugins. It’s been a couple of years since I last browsed the MFX documentation so I may look into this again at some point.
ZynewaveCool! 8)
I’ve got the samplerchan demo now. Will check it out tomorrow.
ZynewaveHey,
I guess you’re talking about this: http://www.kvr-vst.com/get/137.html
Have the company folded, or is it available somewhere else? Without the actual plugin I have no chance of debugging why it crashes. When a plugin performs an illegal action, Podium will show a dialog telling you that the plugin has crashed and to save your work and restart. If SamplerChan crashes without Podium catching it, I would guess it is because SamplerChan is running as a separate application?
Zynewave@nproject wrote:
elo
i tried to record what i was doing (my temp project for podium) on an audio track and when i did this i had many clics and crackles on the recorded sound in wav 16/44
does it comes with my audiocard(pulsar2) or podium ?
Yeah, what Duncan said 🙂 and:
Are you recording from audio inputs or are you bounce recording plugins?
What percentage is the Podium CPU indicator at? Does it ever flash red when recording?
When it flashes red, it means that buffers have been skipped because the CPU load was too high. This will affect an ongoing recording.
If you’re still having problems after trying to increase the buffer size, go to the report page in the Interfaces dialog, save a report and email it to me. I may be able to see what goes wrong.
ZynewaveBug fixed. The explanation I gave above is not entirely correct. You don’t have to set the ‘Audio enabled’ property on the tracks containing plugins. When you assign a plugin on a track then Podium internally creates the mixer feed on the track. Otherwise you wouldn’t see any meters on the track 😳
Nerd mode: So the bug was simply that the level automation failed in its check for the nearest audio mixing track and wrongfully sent the level events to the master track. The code that aborted level automation when muted, correctly told the plugin track to abort level automation. Hence the level events added to the master track was never aborted, causing the runaway level increase.
Zynewave@duncanparsons wrote:
on a similar topic, I’m having a problem with loopazoid…
If I load a kit, do a GM mapping, get everything set up nicely, using a library preset with sync and everything… when I close the project and reopen, loopazoid is there mapped to the right place, but with no kit..!
I know that kits can be saved with songs, as NTrack does it. I’ll see when 0.93 comes out whether it has been solved… Unless you can tell me from the start that it won’t be!
Just tested the LoopAZoid. When I create a program library preset, and restart Podium, the sounds are there but with no labels on the pads in the plugin editor. If I create a bank library preset, then both the sounds and the labels are correct. I haven’t read the manual for Loopa… so I don’t know what the use of individual program presets are for. Just stick with bank presets and it should work ok.
Zynewave@fst wrote:
Reproduces with the following recipe :-
– start new project
– import into project 3 audio files/drum loops etc. @ 16/44.1, and in this case mono
– in a new arrangment, drag them onto separate tracks, all feeding one master stereo out
– open each one in turn in it’s editor by double clicking it
– select a segment and then perform an editing operation ; normalise, silence, reverse etc.
– moving from clip to clip, keep performing edits, one per clip, without saving the modified audio
– sooner or later, the number of edits varies each time, Podium hangs with a ‘Podium has encountered a problem…’ etc. message. Task manager cannot kill the process, and a BSOD eventually results after approx 5 mins. (drivers not unloading probably)This is 100% repeatable on my system.
Bug found. Thanks to your dr.watson report I indeed found a bug in the code for normalize, reverse, invert editing. The bug does not crash my system, but I’m 99% sure that it is the cause for your crash. Fix will be available in 0.93 (friday/saturday).
ZynewaveI’ve just downloaded LoopAZoid, I’ll check it out.
ZynewaveThe load error has been fixed now and will be available in 0.93. It was just a silly size check in the load procedure that was set too low. The project file you mailed me loads ok now, so don’t delete your projects!
Zynewave@fst wrote:
Might just be my system, but the installer dropped another 4 shortcuts onto my desktop, all of which were 0Kb 😕 and undeleteable, but which disapeared after running 0.92 once via the old short cut.
Never seen this before, what Windows version are you using? What were the names of the 4 shortcuts? Did they have the Podium icon? Did it happen when you updated to 0.91?
Also, had a crash after the following procedure :-
– Open sequence editor for an audio track
– Normalise
– Exit editor without re-saving clip (at that point i realised i had to.. ;))
– Repeat x 2 on other audio parts
– Podium crash after the 3rd operation.
Just tried to normalize like crazy on my system, no crashes. There must be something else in your test-procedure that is causing the crash. Could you reproduce the bug and give me more details?
ZynewaveI would ask you to mail me the .pod file that will not load, but I guess it’s huge? Does a project with small 404 presets also fail to load? I have the sfz+ so I will try creating some projects with huge presets and see if I can provoke the bug.
response to a play/stop command becomes very slow, with a pronounced delay, as if Podium is reloading the patches on every transport start.
Podium will send the presets each time playback is started from the beginning, in case automation of parameters have screwed up the current preset settings. There may be some situations where Podium sends the preset unnecessarily. I haven’t worked with large presets so far, so I have not noticed this myself. I will check it out.
ZynewaveI think I know what it is that is confusing you. I need to find a way to highlight this in the UI:
A track with a mixer level parameter will control the mixer level of the closest audio enabled track. Either the parameter track itself or the first parent track that is audio enabled. In your screendump it appears that your synth track is not audio enabled, so the level track is automating the master track directly (thereby seemingly adjusting the levels of all other tracks feeding to the master track). When you don’t audio enable a track then the Podium mixer does not use processing power to create a mixer feed at that track and simply streams any audio and mixer parameters straight through the track further up the tree. One way to emphasize this in Podium would be to put up a warning button on the level track, saying that it does not control the immediate parent synth track. Any other ideas on how to highlight this in the UI?