Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterThanks for the detailed report Jean-Marc.
Tests with 18 channels / 32 bits / 48 kHz files
Is that 32-bit floating point or fixed point?
I must admit I haven’t tested the new optimizations with 18 channel wave files :o, so I’ll try this later today. The data throughput of one of your 18-channel files equals 20 of my stereo 16-bit, 44.1 files but of course it should be faster to load data from a single file than from 20 individual files.
Moving files (that are not playing) during playback is slower than before (can take two seconds between the mouse drag and the refresh)
Do you mean moving sound events on tracks?
Nuendo 2
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?
ZynewaveKeymasterThis happens because the rounding errors are different depending on whether the resized wave display is even or odd pixels in height. The ideal solution to this would be to draw anti-aliased waveforms, but this will have a big impact on the graphics update speed. Perhaps within a couple of years a standard computer system will be sufficiently fast so that I can substitute much of my graphics code with true anti-aliased drawing. 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.
ZynewaveKeymasterJust released Podium 1.63 which has optimizations for sound file streaming.
I’m interested to know how this works out for you, and what kind of track count you can achieve on your PC-system. If you have other hosts, it would be interesting to know how they compare to this Podium release. With my standard Dell Inspiron 9100 I can play up to ~70 tracks with stereo 16-bit, 44.1kHz wave files before file overload begins.
Anyone has links to websites that lists track count measurements in various hosts? I tried googling without success.
ZynewaveKeymaster- Optimized sound file streaming.
- Support for RF64 format wave files.
ZynewaveKeymasterWas it the imported songs or the songs already in the project that got messed up?
Was the problem with note/curve sequence events or was it only sound events?
Import does not use the sequence/object names to determine what should be imported. You can have multiple objects with the same name. Only sound objects will not be imported if the referenced sound file name (not the sound object name) is already imported in the project. If the two projects you merged shared some sound files, then that may be the problem.
ZynewaveKeymasterWhat’s everybody up to?
Well, I’m working on 1.63 😉
I’m also glad the soccer worldcup is soon over, which should give me an hour or two less TV watching per day. Thankfully I’m not interested in watching Tour de France.
ZynewaveKeymasterAre there any other sides to the disk streaming that you are going to optimize?
Plenty. This update of the wave file format support does not really optimize speed, but it is required for future optimizations.
ZynewaveKeymasterAnd a year later… (had to use search to find this topic 🙂 )
In the ongoing effort to optimize disk streaming, I have now replaced the Windows support routines I used for accessing Wave files with my own routines. Thus it is now possible to save standard wave files up to 4 GB.
I also did some further research on >4GB file formats. The format supported by e.g. Cubase/Nuendo and Sony products is using the Wave64 format. This is incompatible to standard Wave files and uses .w64 as file extension. Instead I chose the simpler solution that the ‘RF64’ format offers. This uses the format of a Wave file, but has an additional chunk in the file that specifies 64bit information needed to address beyond 4GB. It is therefore irrelevant for the user whether a wave file is larger or smaller than 4GB.
For technical background on the RF64 format:
http://www.ebu.ch/CMSimages/en/tec_doc_t3306-2 … -42570.pdfWill be available in Podium 1.63.
ZynewaveKeymaster- File access CPU indicator.
ZynewaveKeymasterI have made a modification to the way that the ‘unload plugins…’ option is handled during an offline bounce render. This appears to have fixed the crash problem with JamStix. With a bit of luck, it will also cure the similar problem that was reported with Halion. Fix will appear in release 1.62 within a day or two.
ZynewaveKeymasterIt would be nice if either of you could create and email me a simple project file with a problematic automation track. It’s difficult for me to reproduce the bug based on your descriptions.
ZynewaveKeymasterI 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 ?
They are related, yes.
ZynewaveKeymasterI’m a little lost in your description of the problem. Could you post a screenshot or give a more detailed explanation on how to reproduce the problem?
but then when i offline bounce it doesn’t always seem to pick up the correct values
It’s possible that some plugins have a problem with automation during offline bounce rendering. They may rely on real-time timers or idle notifications from the host for updating automation states. Idle notifications are skipped during bounce rendering.
ZynewaveKeymasterCould you allow the resizing in both directions please ?
Eventually, yes. It’s a bit tricky, because resizing the event to an earlier start time than the zero position inside the sequence requires that all events inside the resized sequence should be time-shifted correspondingly. Resizing the end of the sequence event only modifies the duration of the sequence event.
ZynewaveKeymaster@acousmod wrote:
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 ?
No. If it did there would be a noticeable delay when toggling mute and solo of tracks, which is not desirable during monitoring and mixing.