Zynewave.
Zynewave
ConquistadorThanks Frits…pulling this down now. 🙂
PodianerThanks for the update! 🙂
ConquistadorMore optimizations to file streaming.
Care to share what exactly you did here? Or is that a trade secret? 😆
Or…are the optimizations mentioned below the one’s you refer to above? Nothing major just curious. 😉
[*]Optimized audio streaming in the engine to give up to 10% CPU performance boost when working with large numbers of audio channels and plugins. Podium will use SSE optimized code in the engine if it detects that SSE is supported by the CPU.
[*]To further reduce disk usage inactive bounce tracks are no longer streaming. Reenabling a bounce track causes a short delay before the bounce track starts playing.
[/list]
ZynewaveCare to share what exactly you did here? Or is that a trade secret?
Just boring stuff :wink:. Lot’s of small adjustments using a profiler tool to pinpoint the places that used most CPU time.
Conquistador@Zynewave wrote:
Care to share what exactly you did here? Or is that a trade secret?
Just boring stuff :wink:. Lot’s of small adjustments using a profiler tool to pinpoint the places that used most CPU time.
Ok…either way the improvements are very effective. 8)
acousmodI’m sorry to say that if disk streaming improvements are effective, working with 1.64 like with 1.63 has becoming very hard for me.
As I have previously described, after several minutes of playback and editing Podium becomes to be far less responsive and Windows too.
Making a window coming in the first plan or moving a plugin Gui can take several seconds to process and if it is done while Podium is playing it can result to red spikes in the file indicator and big drop outs.
It takes more time to start or stop and to power off, and when I quit Podium my screen needs several seconds to refresh.
I don’t use MIDI or small looped audio files, and the wave files are often around 500 Mb / 1 Gb.
With only a few little files or at start it is not really noticeable, but after it makes working rather impossible.
I have re-install the 1.62 and it runs perfectly smooth with the same projects, I notice no slowdown and I can move or edit what I want while playing without the interface becoming stuttering.
I have tried with another computer and a few files and I get a similar difference between the 1.62 and the 1.64.
Perhaps is there something with the poor graphic cards ?
It seems also that when Podium redraws the graphics for the files it takes much more processing when goin,g from 1.62 to 1.63/64 than the contrary, but perhaps is this only an impression.
Since the system cache grows a lot during playback, I have changed the priority in the Windows properties, but I have not noticed any difference.
I know that I have not a great computer, but versions prior to 1.63 has never show such a behavior for me.
ZynewaveAs I have previously described, after several minutes of playback and editing Podium becomes to be far less responsive and Windows too.
Making a window coming in the first plan or moving a plugin Gui can take several seconds to process and if it is done while Podium is playing it can result to red spikes in the file indicator and big drop outs.
This is most likely due to Windows swapping memory to the cache file. Podium attempts to buffer streamed sound files in memory and uses up to a certain percentage of available physical memory. It starts freeing the memory buffers if available free memory grows smaller (loading plugins etc.) That way Podium don’t have to reload the files from disk when you are looping a small section or if you have few sound files that all fit in available memory. I apparently need to fine-tune this memory buffer system.
Perhaps is there something with the poor graphic cards ?
No.
acousmodI apparently need to fine-tune this memory buffer system.
Yes, thanks !
francoisWell , i cant use this one Frits , no sound is going out of my SW1000XG synthetisers wich are connected to the cd input of my audigy.Back to 1.63 and it works fine.podium told me also one time that it could not initialise the project at 48000khz , and another time it could not initialise the sw1000 midi in. 🙄
Zynewavepodium told me also one time that it could not initialise the project at 48000khz , and another time it could not initialise the sw1000 midi in
This would normally be an indication that another program is running which locks the audio or MIDI interfaces. This could explain why you didn’t get any sound out of Podium. When you have a spare moment, I would appreciate if you could verify this one more time: Reinstall 1.64 and make sure there are no other audio/midi applications running when you start Podium.
francoisSure , i’ll do that asap , but i think my sw1000 does not receive any midi , because , if then i launch xgedit and click on the keyboard ,sounds are going out normaly
francoisOk , Frits , no more undesirable messages ,but i confirm that podium1.64 is not sending any midi to my sw1k , while the midi indicator is blinking normally.And it appears to be the same for my audigy synth , the only sound i get is from the plugins.If i then load midiox , and try to play them , it works , this is why i think that my 2 hardware devices dont receive any midi from podium.
Zynewavebut i confirm that podium1.64 is not sending any midi to my sw1k
I found the problem. One of the optimizations in 1.64 included using a Windows routine that seems to fail on OS’s prior to XP. That’s why I didn’t see the bug on my XP development machine. I now tried it on my old W2K machine, and sure enough, no MIDI output. Bug fix version will be up in a day or two.
francoisGreat 😀