ZynewaveZynewaveWas 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.
ZynewaveWhat’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.
ZynewaveAre 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.
ZynewaveAnd 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.pdf
Will be available in Podium 1.63.
ZynewaveZynewaveI 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.
ZynewaveIt 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.
ZynewaveI 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.
ZynewaveI’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.
ZynewaveCould 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.
Zynewave@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.
ZynewaveZynewaveGood idea. I’ve added “Save states of track inspector, mixer and embedded editor in each arrangement.” to the future list. It probably would be best to have this as an option in the preferences. I can see situations where I would prefer the layout of the editor to stay constant, independent of the arrangement.
ZynewaveWhen recording audio inputs, before. When bounce recording/rendering, after.