Podianer.
ZynewaveWhat are the bit-resolutions of your sound files?
I can see in your project file that the sound files are are located on a Q: drive. Is this an internal drive?
ConquistadorWhat are the bit-resolutions of your sound files?
32bit
I can see in your project file that the sound files are are located on a Q: drive. Is this an internal drive?
Well spotted…yes it is. I have two other USB drives but they are *not* used with Podium. Purely for storage.
Why Q? I have partioned both of my internal hard drives. I have used Tracktion and Live for instance and had no problem using files from this partition.
FWIW the computer I run Podium on now is a new one and not the PC I had last year the last time we spoke.
It has plenty of ram on it as well. Pentium D.
ZynewaveAfter the next 1.49 release I’ll start optimizing the disk streaming. I don’t think its the actual file loading routines that is to blame, but rather the preload scheduling that could be improved.
Conquistador@Zynewave wrote:
After the next 1.49 release I’ll start optimizing the disk streaming. I don’t think its the actual file loading routines that is to blame, but rather the preload scheduling that could be improved.
Thanks! I know you have your hands full with 1.49.
Thanks again Frits. 😉
ConquistadorHi Frits,
Just a quick note on the disk streaming optimization or preload scheduling…have you been able to look at this since 1.49.?
Still having the same problem here with 1.56. The same audio files I used in that project, work perfectly well in Cubase SX3 but will not playback without skipping and dropping out during playback in 1.56. 🙁
Any idea when you can look at disk optimization / pre scheduling as everything else in Podium is 100% for me. 😉
This is the *only* issue (big or small) I have with an otherwise flawless Podium.
Thanks 😉
ZynewaveI have not forgotten about this. I was hoping I could update my development tools before looking into this, as this would be a big help in the debugging and optimization. I may have to postpone the purchase though. Microsoft wants 550US$ for an upgrade to their latest compiler version 🙁 .
I am currently occupied with another feature, but I’ll look into this soon.
ConquistadorThat explains it. 🙂
I figured it had to be something major to hold you up on this issue for this long. 😉 No problem Frits…when you are ready!
Cheers! 😉
PodianerNow it’s me with big drop outs. I mainly have audio tracks recorded from my band. All my Podium files are stored on an external USB harddrive with 7200 rpm. I have 2 GB of RAM. That shouldn’t be the problem then..
Conquistador@Podianer wrote:
Now it’s me with big drop outs. I mainly have audio tracks recorded from my band. All my Podium files are stored on an external USB harddrive with 7200 rpm. I have 2 GB of RAM. That shouldn’t be the problem then..
I think SuperCrunchy (thread starter) had around 512mb of ram I have around 4GB, so your 2GB of Ram I would have thought, should have no bearing on this issue. Just guessing but it would be strange if it did.
The issues I am still having are similar if not identical to yours.
Mainly audio tracks that will drop out when playback is started. Sometimes playing the whole project through once returns things back to normal, but that works as many times as it doesn’t here.
It’s the only problem I have with Podium.
I remember a problem I kept having with Podium hanging when scanning my VST’s, not a problem any more .
The unpredictability of the audio dropouts in Podium makes it very tricky to use it as reliability goes out the window.
Playback must be 100% reliable in any host or a huge amount of time and effort is wasted if one cannot guarantee a project will playback properly.
Hopefully Frits can do something about it sooner rather than later.
Instrument play back (triggered by midi) seems fine but importing audio files or bouncing an existing audio file seems to cause audio drop outs here.
I am pretty sure it is not 100% plug in related as I have tested Podium out thoroughly with a variety of audio only projects with no FX or instruments and still had dropouts.
Frits said he needed or preferred to have better development tools available ideally before looking at it.
Hopefully some other sort of solution can be offered soon.
Podianer@Conquistador wrote:
The unpredictability of the audio dropouts in Podium makes it very tricky to use it as reliability goes out the window.
Absolutely agree! The ridiculous thing is, I can use only 6 or 7 tracks with audio, and the drop outs still occur..Even if I have no plugin on the whole arrangement. I defragmented my hard drive. Nothing has changend then.
ZynewaveI still haven’t purchased the additional development tools, but I think I have delayed looking into this problem long enough. After the next release, I’ll start on this. I have created a test arrangement with 30+ stereo 16-bit files, which causes drop-outs on my system when starting the arrangement. This should be a good starting point to research various optimization solutions.
ConquistadorThanks Frits. Consistent and reliable playback in a host is just too important to not have. It’s probably not even something any user would look out for as it’s simply expected.
Probably the no.1 feature of any host (not just Podium) is simply to playback audio and midi. As midi data is likely going to be bounced to audio at some point in a project, consistent audio playback becomes critical.
I know you are aware of this anyway of course 😉 , and judging by the speed of past bug fixes this would long since have been adressed as have other bugs if it was not because of the development tools which I fully understand.
Thanks for letting us know when you will look into this. At least you can reproduce it.
Cheers. 🙂
PodianerIt is very confusing. Today I wanted to record some bass guitar. By now I am aware of the disk streaming issue. Thus I bounced ALL OTHER tracks to one file. I played this file during my record session, and I still got drop outs. I get the feeling this behaviour gets worse with the amount of files in the project folder. When I started the project, I didn’t have drop outs at all. Now with 7 arrangements in one project, all with several audio tracks (24 Bit; 44 kHz) I can’t get rid of the drop outs..
I really hope, that Frits manages to fix this soon.
ZynewaveThus I bounced ALL OTHER tracks to one file. I played this file during my record session, and I still got drop outs.
As it is working currently, all audio tracks in an arrangement are streaming, even if they are muted. This is to ensure that unmuting will play the track immediately, rather than having a short pause before the disk streaming is catching up. Thus if you bounce a group of audio tracks, you are actually not reducing the disk streaming. I intend to change this so that streaming of muted audio tracks is disabled if they are muted by a parent bounce track. That way bounce tracks will also reduce disk-streaming as well as CPU usage.
PodianerThis explains a lot … 😉