bladerunnerboth good workarounds , cheers 😀 . surprised that there isn’t a way within podium to use more than one device at a time though (or at least i haven’t found one!).
bladerunner@andyy815 wrote:
I suspect it might be connected to one of the samplers: DirectWave or ShortCircuit 2. Is there something that can be done aout this?
shortcircuit 2 is very buggy so could be causing something. shortcircuit 1.1.2 is the one to go for.
bladerunnerreapers reacomp is available as a freebie
bladerunneras .mini files are only a few kilobytes in size it really wouldn’t matter (to me anyway!) too much if there were thousands of them and, like you say, users could always delete them if they are bothered by it. better that they are all in the same place than scattered around numerous folders and such (that’s the way i look at it!).
thanks for considering it :D/
bladerunner@Zynewave wrote:
In both cases it can be a nightmare to maintain the mini folder, and to validate it against moved sound files etc.
the way i think of it (and of course put me right if i have it all wrong 😉 ) there wouldn’t be any need to maintain the allocated folder would there? it wouldn’t bother me at all if lots of duplicate .mini files were happily residing in the allocated folder as a result of moving audio files and podium regenerating a new one accordingly. it’s just the tidyness factor that i am thinking of
bladerunner@Malcolm Jacobson wrote:
Hi all,
I have posted a video tutorial showing how to bounce MIDI tracks to audio on YouTube:
http://www.youtube.com/watch?v=0c6C2mf6_hc
The bounce feature is a very powerful part of Podium.
Cheers,
Malcolm.
great work! showed me something i didn’t know about the options to hide the bounce track lane 🙂
bladerunnerhi frits 🙂 is a .mini file fulfilling the same purpose as a reaper peaks file? they have an option to store all reapeaks files in one folder. does a .mini file differ in any way? if you did move the audio file to a new location would a new .mini file be created the next time the project is opened? this seems to be what happens with reaper (could be wrong). sorry for all the reaper comparisons! its just that the way they do it with reaper peaks files gave me the idea of the feature request.
bladerunner@xis23 wrote:
oopsy meant to put my other post here:
http://www.xis23.pwp.blueyonder.co.uk/rr%20-%20sphynx.mp3
First track I’ve finished with podium really. It’s kind of egyptian neurofunk
wicked track xis23. some really great motion in the bass programming. love the egyptian vibe too
bladerunnerhi frits 🙂 sorry this subject makes you sigh. perhaps is it just taking me longer than everyone else to get my head around it 🙄 lol! i have just been playing around with reapers sychronous and anticipative modes and also with podium and i think i finally get it (i read through the linked thread)…
it seems to me that podium is reporting a more accurate cpu reading than other hosts and that podiums engine is based on real time performance (so, equivalent to reapers synchronous mode right? – forgive me if i am repeating stuff that has been mentioned in other related threads) and not the rendering ahead type ability of reapers anticipative mode. when reaper is in synchronous mode i get a similar performance to podium but when in anticipative i get more performance but the trade off is in a delay to real time performance tweaks to plugins etc. (right?!). hope i’m making sense
bladerunnerthe ongoing cpu spike issue which can be clearly be seen in frits own video here
http://www.youtube.com/watch?v=Jv39dX7NP_Q
its reassuring to know that it happens on the devs own computer as i thought it might be an issue with my own particular set up. it really makes podium almost unusable for me. i haven’t seen behaviour like it in any other host. the spiking seems to be directly linked to the asio buffer size which has to be set at 2048 samples to tame the spikes. in reaper i have no such problem and can run many more softsynths at 512 samples. i have read through all of the cpu related threads in this forum and played around with all of the recommended tweaks etc. but the issue still very much remains.
i have also mentioned timestretching as an issue but i could just rewire reaper for that duty if i needed it so the cpu issue being addressed is my one wish.
i can regularly bounce tracks as a workaround but i think there is an issue that needs addressing here. do others find this is still a problem or are you bouncing tracks to get around it?
bladerunnerthe knobs/sliders on oatmeal can be centred (or reset to their default value) by using shift + right click. you can also hold shift for tiny adjustments on any knob/slider. it can be a bit of a chore programming it but the fact that you can draw your own audio and modulation waveforms makes it immensely powerful. i do use easier synths too though 😉
bladerunnerthanks for the replies! this track was written to meet the criteria for a remix assignment on my music technology degree (it’s a remix of a local band we recorded in the college studio). it was composed purely as a dancefloor piece of techno with specific requirements for intro length ie. a set amount of bars so that a dj has sufficient time to mix it etc. it is a very clinical piece as a result of all the rules we had to follow. i just wanted to share it as one of my only pieces completely realised and mixed in podium. (i got a 90% for it :shock:)
LiquidPro3ct – hi btw! yes, very repetitive indeed… the delayed sound is in fact a guitar stab sent through a filter and the beats (kick, hihat etc) were all synthesised in oatmeal so no wav loops!
this is what i normally do – a few more dynamics!
bladerunnerbladerunnerjust noticed this!! thanks for the praise Klemperer 🙂 glad you liked moon orbit – that was one of one of my patches. i am working on a bank for synth1 at the moment. i will post somewhere here when it is available (will upload it to kvr). there should be a few sounds in there you might like 😉
bladerunner