Yes, it would be extremely useful !
I’ve added “Save states of track inspector, mixer and embedded editor in each arrangement.” to the future list.
Does this will include also if it is the Arrangement or the Arrangement Compact view which is selected ?
I generally use a screenset with two views of the same arrangement, one of which is a minimal profile for a global view, something like the overall view in Tracktion or others (a good FR for Podium indeed).
This is very handy but I have always to manually select the Arrange, then the Compact view for the second screen and zoom it out because it doesn’t remember the previous state.
And since I have to restart Podium rather often it is really a mess…
???
Are you running Windows XP pro, acousmod?
Yes.
No other app or special task running in the background (no Internet on this computer).
But only a IDE drive, only 1 Gb Ram and only a single 3,2 GHz CPU…
Have you a SATA ?
The problems which I have described happends after several minutes playing. The files are around 1 GB each, and of course are different and they are not looping.
I use VoptXP as a defragmenter and the partition is not fragmented.
But the drive is the same as the system and the swap file (only different partitions).
Does a shorter latency is better for streaming ?
I generally use 1024 because when using plugins it takes less CPU.
I can play 8 18 channel 32-bit files at 48kHz, which equals a data throughput of 28 MB/second.
Very impressive !!
Is that 32-bit floating point or fixed point?
Floating point, that is set by default in the bounce dialog.
I work in general with 16 and 24 bits files, but I use the 32 bits files when I make premixes by bouncing in working arrangements and arranging them in a “main” arrangement. They remain editable and since I don’t want to lose quality I select the 32 bits float option (I use this like a Group function).
Generally I don’t have to mix more than three or four submixes in the “main” arrangement.
but of course it should be faster to load data from a single file than from 20 individual files
Yes, it is one great advantage of Podium above the other multitrack softwares 😀
Do you mean moving sound events on tracks?
For example pushing a sound forward on the same track.
All the GUI actions seems to be slower.
I thought you mentioned in an earlier post that Nuendo only could play 12 channels. Are you playing the full 18 channel files in Nuendo?
Nuendo can play and process files with more than 12 channels, BUT due to its bus limit, we can only hear the first 12.
For example I can apply destructive filtering or timestretching on 24 channel files, but I can only listen to them when they are imported in Podium.
Since it plays and I can hear the first 12 channels of the 18 channels files, I suppose that all the interleaved files are read ?
Although, the “0” percents seems to be inaccurate !
I have tried with theses files because I thought that it could show a different behaviour than multiple stereo files.
I suppose that with 6 channels 24 bits files it will look more than your own tests.
However, except this strange accumulation along the time, the streaming seems to be lower and more regular than before.
Another hack solution would be to always restrict channel heights to an odd pixel count, which on the other hand would result in less fluent zooming.
For me it would be a perfect solution.
I don’t know how it is made in Nuendo, but the appearance is consistant whatever the zoom value is.
Perhaps that a possibility to have an amplitude zoom slider in the arrange like in the sound editor will also help for small amplitudes.
Some example :
good :
not good :
good :
not good :
good
etc.
A (ugly) drawing is sometimes better than explantions…
What I have tried to describe before could be look something like that :
Tests with 18 channels / 32 bits / 48 kHz files, no plugin, RME driver beta 3, latency set to 1024, P4 HT 3,2 GHz, 1 Gb RAM, multithread not activated, 7200 t internal IDE drive.
Podium 1.62
– 1 file : File indicator from 0 to 20 %, very irregular, no drop outs
– 2 files : sames values but the changes are faster
– 3 files : up to 30/40 %, the bursts are faster, occasionnal drop outs even if the value stays “low”
– 4 files : higher values, very irregular, more drop outs after several minutes, but sometimes good
Podium 1.63
– 1 file : File indicator arround 0 % at the begining, but goes progressively up to 10 % after a few minutes. Moving files (that are not playing) during playback is slower than before (can take two seconds between the mouse drag and the refresh)
– 2 files : 0/1 % at begining, but can go up to 50 % or more in a irregular manner after a few minutes and can even freeze
– 3 files : 0/2 % at begining, but can go up to 50 % or more in a irregular manner with sudden bursts and drop outs after a few minutes and freeze
– 4 files : also freeze after several minutes playing.
When this happends, the sound is cut and the interface is VERY slow : it can take 20 seconds to stop Podium’s engine and Windows can become to be very slow too until I quit Podium.
RAM : the RAM used by Podium in the task manager is about 340 Mo at start but decreases during playback down to about 90 %.
Bidule :
– 1 file : 2 to 9 % disc usage depending of which file is played (I suppose that it depends on its position on the disc ?), the value remains constant during all the time
– 2 files : 4 to 12 % disc usage depending of which files are played, also constant
– 3 files : 5 to 13 %, constant
– 4 files : about 15 %, constant all the time, no drop outs
RAM used : 130 Mo, constant
Nuendo 2 :
– 1, 2, 3, and 4 files : 0 % during playback (!?), but starts at 100 % and goes to 0 very fast (less than a second with four files), no change during all the time, no drop out
– 5 files : it takes more time to go to 0 % at start, but remains constant after, no drop out
– 6 files ! : after a few seconds the values in the disc usage indicator change of direction and go to 100 % after some time resulting in sound distorsions.
Except for the 6 files test, it is possible to jump to other places during playback with only a very short interruption in the sound.
The system is not slow down.
Ram usage : 150 Mo constant or slowly growing.
I have reinstalled the 1.62 version because I don’t want to take risks during working.
I will make some other tests on another computer later, with different kinds of files (6 channels / 24 bits).
Excellent news Frits !
This one will come perfectly in time for me for the export of a 29′ / 24 bits / 18 channels project.
Thanks a lot for your continuous works.
Could we have the choice (option) ?
It is not a problem during editing.
As I have said, I use a lot the muted tracks to replace a mute event feature, so it will be a grat benefit to be able to have the tracks really not active.
For me, the fact that the envelopes are not updated when I unmute a track is a far more annoying thing.
I must always stop / restart when I unmute a track !
I don’t know if it is related, and if I have well understood, but you have said that you have splitted a big sequence ?
There is a very old bug with automation curves, hard to reproduce, which happends some times with sequences that have been splitted + clone phantom + crop sequence correctly made.
Sometimes old values that are no more in the sequence are active even if you draw other values.
The only solution is to delete the sequence and draw a new fresh one.
Perhaps that some “old” 100 or 0 values interfer with the one that you see ?
(when sequences are merged, the sent values are also sometimes shifted in comparison to the ones that are seen)
Resizing the end of the sequence event only modifies the duration of the sequence event.
I suppose that it is the same reason for which the sound is stoped when we split or change the begining position of an audio event ?
Without being of a high priority, I think that it would be a good think to be corrected, because it is something rather incomprehensible from the point of view of the user, since this limit is not present in any other software.
It is so evident to do it that it appears to be something like a bug when it is not…
Audio tracks that are muted by a parent bounce track no longer streams in the background. This reduces disk usage at the cost of short delay before tracks start playing again when unmuted.
It doesn’t work also for normal muted tracks ?