Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@LiquidProj3ct wrote:
Frits, is “BasicHeader.cpp” a Podium file? I getting this crash using DirectWave (simply loading sfz and playing them), so I think it’s related with DirectWave
Uploaded with ImageShack.us
BasicHeader.cpp is not part of my source code. It must be from DirectWave. I assume this bug is not new to Podium 2.33, but also occurred in previous versions?
ZynewaveKeymaster@khaos wrote:
Trancit the track you sent me wouldnt open, said it was made with a differnent version. I’m using 2.32.
Unless the file was saved with 2.33, the message you get just informs you that the file was saved with an older version. If you resave the file, then the pod file will not load in that older version. The project should still load fine.
Zynewave is it correct that for each rewire/reason instrument I want to use I need to create 2 tracks?
It’s been a while since I last tried Reason, but if you want to use the Reason mixer, I believe it is enough to just set up the Reason master mix l/r mapping on one track in Podium. Then add all the Reason MIDI tracks you need in Podium. You would only need to use multiple Reason outputs if you want to mix or apply effects to each Reason synth in the Podium mixer.
July 10, 2010 at 09:09 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.July 9, 2010 at 18:33 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.July 9, 2010 at 12:00 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymaster- Redesigned the graphics of track events.
- Minor bug fixes.
ZynewaveKeymaster- Time-stretching of note and curve sequence events on tracks.
July 8, 2010 at 20:14 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.July 8, 2010 at 18:22 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymaster@thcilnnahoj wrote:
Don’t know if it was supposed to be fixed in beta 4 already, but it’s still there. Also, the notes seem to disappear when stretching (well, shrinking) events which don’t start with a note. Both are shown in this GIF (320 KB)!
Fixed in beta 5 I hope. I discovered later that I had multiplied where I should have divided with the stretch factor 😳
Also also, converting events to unique cropped copies doesn’t always work correctly when the event is “time-contracted” – notes/automation points get cut off.
Thanks. Fixed in beta 5.
I also made a small optimization to the track event drop shadow painting in beta 5, so let me know if you still see some slow UI response that you think I should investigate.
ZynewaveKeymaster
ZynewaveKeymaster@Trancit wrote:
Could you consider to implement the midi preview from the browser???
Only sending the midi file data to the selected track…nothing more 8)
It doesn’t really fit into the current set of changes I’m making. I need to focus my development on specific areas at a time. I will look at MIDI file audition on the next update of the browser.
ZynewaveKeymaster@technogremlin wrote:
@Zynewave wrote:
I had a security check in the scanning code that allowed a max depth of 4 subfolder levels. I’ve now increased this to 8.
OK, so rebuilding my directory structure (planned, will be less levels deep) might solve this for now. Is this increase in a new free version ?
It will be in Free 2.33.
@Zynewave wrote:
Also, when I update the library (instead of rebuilding it), it creates several duplicate submenus in the insert-menu.
Yes. The database update will append new mappings (with their subfolder location) to the end of the list. You can either select to rebuild the database, or manually organize the new mappings into the desired folders.
That’s the problem I’m running in; when I choose ‘rebuild’ it seems to ignore previous blacklisted plugs, do it all over again and crash when encountering those. Then after restart I get the message they are blacklisted and I have only the option to rescan, as rebuild will do it all over again.
A rebuild of the plugin database should not reset the quarantined plugins. The crashing plugins are listed with full filepath in the “PluginQuarantine.txt” file in the setup folder. If you move the plugins to another folder, then they will be scanned again.

