Zynewave's Forum Page
Forum Replies Created
-
May 26, 2008 at 21:35 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.May 26, 2008 at 05:21 in reply to: New developer tool. Implications for future Podium versions. #12468ZynewaveKeymasterAfter a long night of debugging I have now finally figured out why Podium 1.98 and later versions can crash on Win9x. I dug out my old Win98 harddrive from the back of the closet and replaced it in my old Pentium3 PC. I got the crashes with 1.98, but not with 1.97.
The problem is related to the limited number of system resources that W9x can handle. Googling reveals that it is a very common problem for larger applications. This page has a good explanation:
http://apptools.com/rants/resources.phpThe thing that happened in Podium 1.98 was that I created the resizable toolbars. This required allocation of an extra set of large bitmaps that is used when generating the resized images. These extra bitmaps has pushed the number of bitmaps beyond what Win9x allows. If you e.g. delete the edit toolbar in the arrangement editor profile before entering the arrangement, you won’t get a crash when opening the arrangement editor because Podium doesn’t need to allocate the bitmaps for the edit toolbar.
I could spend a lot of time trying to reduce the number of bitmaps that Podium uses, but in my opinion that is a waste of time. It will restrict the things I can do to improve the UI in future Podium versions.
So unfortunately I’ll have to drop the claim that Podium is Win9x compatible.
ZynewaveKeymasterIn older Podium versions you would get a lengthy stickie note with explanations on how to create arrangements etc. The latest Podium version only creates a note with e.g.:
“Project created: 25-05-2008 18:42:30”There is no option to not create this note, but you can disable the “Popup project stickie note…” option in preferences.
ZynewaveKeymaster@Ash: Thanks for your insightful comments. Much appreciated.
@Ash wrote:
I know Podium was not intended for film scoring in the first instance, but I really do think it would be nice to see Podium being used for this application more in future, as it grows and evolves. The speed of prototyping musical ideas with Podium is an essential requirement for composers who are hard-pushed for time! The arrangement feature is very nice for composers too, since in a lot of cases, several different versions of a cue may have to be created for different situations. With the arrangement feature, these can all be neatly contained in a single project folder, along with sound effects and anything else that’s required.
Obviously, things will be improved little by little, as Podium gradually becomes what its users always imagined its potential would be, but until then, I will keep working around any issues I find.
I hope you do not mind me issuing these kinds of feature requests that deviate from what might be intended for Podium. I know they stray from Podium’s original purpose, but I just want to do my part in seeing Podium eventually become a real audio power tool for all types of musician.
Although Podium does not currently offer dedicated film-scoring features, it is an area that I plan to work on in the future. I think it will be possible to extend Podium into a capable film-scoring tool, within the curent UI framework.
May 24, 2008 at 01:48 in reply to: New developer tool. Implications for future Podium versions. #12447ZynewaveKeymaster@acousmod wrote:
Hi Pigini,
I’ve tried the latest build of Reaper on an old Pentium Tablet PC with Win98 and it works (slowly !) without any error.
I cannot tell you about Podium because the MSI installer didn’t work.
Perhaps is there something else in your config that causes the error ?If you have the time, could you try to just copy the Podium.exe to the tablet and see if it runs? I am interested in knowing if W98 compatibility is broken, or it is something else that causes Podium to fail on Pigini’s W98 machine.
May 24, 2008 at 01:46 in reply to: New developer tool. Implications for future Podium versions. #12446ZynewaveKeymaster@Pigini wrote:
@Zynewave wrote:
I’ve just released Podium 1.99. It is still compiled with VS6, so Windows compatibility is unchanged.
I guess I got excited too early about the unchanged windows 98se compatibility.
I had no time for testing earlier, just installed podium 1.99 today, and it installs alright, but after leaving the project setup and actually starting the new arrangement I get a c++ runtime error ..application requested the runtime to terminate in an unusual way. 🙁
It would have been nice to have a bugfixed final win98 version, but well …
Looks like the new developer tool puts something in the code w98 just can’t handle. It’s the same error message I get with the newer Reaper versions (started testing them when the w98 compatibility thing came up for podium). They still claim to support w98, but must have changed teir developer tool too.Podium 1.99 is not compiled with the new developer tool. It’s still made with VS6 as with all prior Podium versions. So I’m surprised that it doesn’t appear to work on W98 any more.
ZynewaveKeymasterAs acousmod said, directx seems to be a dead format. Development of the format is discontinued, and Steinberg recently dropped support for DirectX in the new versions of their products.
A major reason why I made the zPitch plugin was to test what kind of quality I could get with my own time-stretching implementation. So I have the basic DSP code needed for the implementation. I just need to find the time to integrate it into the UI.
ZynewaveKeymaster@swayzak wrote:
Decided to create a new project from scratch.
This created Midi input devices available in the “Input” part of inspector.
Assigned to default Absynth VSTi & could then play from keyboard.
However these Midi devices are not present in my main default project – just a folder of device mappings (Midi In 1 to 16).
Can I easily recreate all the midi devices (RME HDSP etc.) in my main project or have I got start from scratch ?
Sorry for taking this long to reply, but I was working on a “Load device setup” feature for Podium 2.00 that can be a help with this problem. You can download a 2.00 beta version in the VIP lounge, if you cannot wait for the final 2.00 release.
Basically what you do is create a new project with the devices set up as you want them, and then save this project as a template. Next load one of your older projects, select the template in the “Load device setup” submenu, and the device setup in your old project should then be replaced with the new template setup.
ZynewaveKeymaster@sam c wrote:
could it be powercore 3.1?
If you recently upgraded the powercore software to version 3.1, then I’d say your cpu problem could just as well be an issue with the powercore update than with a Podium update.
i will try older versions later.
Let me know if you try an older Podium version with the new powercore 3.1 drivers. Please also let me know if you manage to otherwise solve the cpu issue.
ZynewaveKeymaster@Mike G wrote:
Are play and stop the only MMC commands supported by podium?
Currently only stop/start is supported. At some point I’ll get back to extending MIDI remote control support.
ZynewaveKeymaster@acousmod wrote:
@Zynewave wrote:
Please send me the two project files you are trying to merge.
Done.
Thanks.
Your projects had a number of customizations that uncovered a few cases I hadn’t considered. You have for example moved some plugins out of the “Devices” folder and into the project root folder. I have uploaded a beta2 that fixes the crash bug, and which has further improvements in the merging of MIDI/audio/bus mappings. Please let me know if you find issues with the project merging in beta2.
ZynewaveKeymaster@acousmod wrote:
Podium also simply quits very often when merging.
Sometimes folder devices appear in the Arrangement s & Sounds section instead of the Devices (Audio Inputs folder).Please send me the two project files you are trying to merge.
ZynewaveKeymasterThis is typical behaviour for plugins with denormal problems, but since you’re only using a single powercore plugin then denormals should not be the problem.
and it is new to 1.98
You mean 1.98 and not 1.99?
I have my doubts that it is something I changed in 1.98 that’s causing this. Please verify this by reinstalling version 1.97, load exactly the same project and check if the CPU problems are gone.
Also, try to disable the “Enable plugin multiprocessing” option in Preferences and see if this has an effect.
ZynewaveKeymaster@acousmod wrote:
Not in a musical timebase arrangement.
Does that means that it is already possible in a linear timebase arrangement ? 😯 😯
You probably think about a lock option so that the event cannot be moved by the mouse. I was talking about an option to lock an event to its absolute time position, so that if you change the tempo of the arrangement, then the time locked events will move to a different bar/beat position.
ZynewaveKeymasterDoes it jump to 50% immediately when you stop?
If you have any other plugins in the effect chain above the powercore plugin, try to remove these to ensure that it’s not those that are responsible for the CPU jump.