Zynewave@Conquistador wrote:
Really strange… I cannot change Affinity settings for Podium on Vista x86 either. Are you sure I should be able to do this without an additional step somewhere?
On my system I can check/uncheck each individual CPU core in the “Processor Affinity” dialog.
Can you change the affinity for other running applications? Try to open e.g. MS Paint, and follow the task manager procedure I described.
Zynewave@aMUSEd wrote:
I’m still seeing the brushed texture even though I set it to be off.
You can’t set it to off. If you want a blank bankground then you can create a solid colored rectangle (at least 32×32 in size) in MS paint, and use that bitmap file as the texture. Use the “dye texture” option to make it match the color scheme you use.
Zynewave@LiquidProj3ct wrote:
what does “The chosen zoom resolution is stored in the setup file.” mean ?
It means that the zoom setting you last used will be remembered the next time you start up Podium.
ZynewaveZynewaveThanks for the file. It was the bypass toggling that failed to update the audio routing properly. The mono effect I was testing with had a processing latency, so it was updated for other reasons than the bypass toggle.
2.08 is released. Hopefully the bug is fully fixed now.
ZynewaveI have a stereo instrument chained into a mono effect. Bypassing the mono effect would previously only send the left channel through, as you described. In beta9 this is fixed so that both L+R produce output when the mono effect is bypassed. I just verified this with the Podium208_beta9.exe.
Are you sure you used the latest beta9 when you tested? If so, please send me a project file that shows the problem.
Zynewave@IrishGuy wrote:
Thanks Ronin. BTW – I downloaded the Zip file suggested above (http://www.zynewave.com/files/Nucleum095.zip) but when I went to extract the files I got a message saying the compressed Zip files was invalid.
I just checked, and the download works fine for me. Try to download the file again. You may need to clear your browsers cache, depending on which browser you use.
I think you are right about the GNX4 as an audio/midi interface although I haven’t tried that just yet. To be honest, my first “mini project” that I wanted to accomplish (since I have not used a DAW much before) was to use an existing midi file to drive virtual instruments and then render a WAV file all in the s/w world. This seems to be much more difficult than I expected since I haven’t even been able to get any sound out of my sound board yet.
To get going, I recommend you follow the getting started chapter in the guide, before trying with MIDI files.
http://www.zynewave.com/wiki/doku.php?id=guide:getting_started
If you try this, then let us know where you encounter problems. That may give me some clues on how to make the getting started chapter more comprehensible.
Zynewave@Conquistador wrote:
How many seconds does it take during Podium startup before the not responding message appears?
It depends. It is intermittent but if you click anywere on the screen as Podium loads a project, it can take about two seconds or so then it appears.
According to MS documentation, the “not responding” title should only appear if the app fails to respond to user input for a period longer than 5 seconds. That may happen if you click the app window during startup, and the project takes longer than 5 seconds to load. The user input should not be blocked for that long when you e.g. drag controls in a plugin editor. Something else is messing with the system in that case. I don’t know what it could be.
It is the Windows OS that appends the “not responding” text in the title bar. The Podium maximized state hides all window borders and the window title bar (unlike other applications), so that is why the screen shifts when the Windows OS forces the window title to be visible.
Thanks for clarifying that…so there is a reason for this behaviour. This brings me to another question though… why is it that Podium is doing something (at least in this area) “unlike other applications”?
It seems to be something under Podiums hood (which is way over my head just guessing here) but if Podium is doing somehting it probably should not, then should this behaviour not be changed as Windows clearly is clashing with Podium in some way or another. It also explains why the other apps I have did not exhibit this graphical shift.
Podium is hiding the window titlebar to save some valuable space that can be better used to show additional tracks etc. Other applications are doing something similar. I believe Tracktion also has done away with the standard window titlebar.
Something you could try:
When Podium is launched, open the task manager, right-click the Podium.exe on the processes page, select “set affinity” and reduce the number of enabled CPUs to only one. Let me know if you still experience problems even when only running on one CPU core.
Zynewave@Conquistador wrote:
@Zynewave wrote:
What action were you doing to cause the crash?
I think it was simply bypassing an effect or two. As the template I am setting up has some bypassed effects. It did not happen again after re starting Podium though.
Next time it crashes, try to remember what you had done leading up to the crash, and then try to reproduce the crash.
Podium has some kind of warning pop up message should that not have popped up?
If you mean the plugin crash messagebox, then that only pops up if the crash happens in the plugin code.
Zynewave@H-man wrote:
Better that anything is that testing the Comping features has got me to back playing my Guitars and not just twiddling dials and piling effects 😆 .
Fantastic 🙂
The only aspect of the new features that I had found a little confusing (Thx for raising Mike) was that the Comp Track event (first one) would commence from the cursor position and not the first loop marker, requiring the user to have to slice the Comp track at the first loop marker to get access to the other (sub) tracks.
Maybe the Comp track event could be set to auto-slice at this point? I get it that this can be remedied using the punch-in marker however I feel that new users will find this confusing and ‘eat’ the half-hour or so that I did until I figured it out.
I’ve changed it so that the comp event will be split at the loop start, not during the first take, but when the recording loops back.
PS: Possible bug? I found at one stage that I lost the ability to delete events on a track with the ‘delete’ key when there were a large number (40+) of copied or cloned events. Right click – delete would still work tho.
Hmm, the number of events should not matter. Are you sure that the tracks region had keyboard focus?
ZynewaveI don’t believe y’all thought about this simultaneously 😮
Anyway, the 2.08 release will have this addition:
Extended the number of vertical zoom resolutions in the piano roll region. The chosen zoom resolution is stored in the Podium setup file.
ZynewaveI remember having a hard time with DrumCore when I tried it during the implementation of ReWire support in Podium. There were no uninstaller with DrumCore and I had to do a system restore in Vista to get rid of it. This time I downloaded and installed the DrumCore demo on my old laptop. I try to keep my development PC as clean as possible, so that excludes software that won’t uninstall easily.
I can confirm that I also get the “DrumCore ReWire error 666 (IsPanelAppLaunched)” error when I try to use DrumCore.
The Propellerheads source code comment for ReWire error 666 reads:
/* DLL error – call the cops! */
This leaves me with no clue as to what goes wrong.
Have you tried to contact the DrumCore developers? If you have the standard 200$ drumcore version, maybe they wouldn’t mind testing it in Podium for you?
ZynewaveI’m guessing you ctrl+click the first note to start the drag. Ctrl+clicking will toggle selection of the clicked event. You need to first click the selection and then hold the control key when releasing.
Zynewave@Conquistador wrote:
Here is a screen shot of the black borders I mentioned earlier…
…
It sometimes appears when loading projects. I can understand Podium is busy doing something but even if an application becomes unresponsive for a short time (not regularly but under certain condidtions) it should not also shift the screen diagonally left, leaving black borders at the right and bottom of the screen (clearly visible in the image above) until the application (Podium in this case) becomes responsive again.
I’ve seen the “not responding” message before, but that is only when there is a bug that causes Podium to freeze completely (an endless loop in the code, not a crash). How many seconds does it take during Podium startup before the not responding message appears? And does the screen return to normal when Podium is finally ready after startup?
It is the Windows OS that appends the “not responding” text in the title bar. The Podium maximized state hides all window borders and the window title bar (unlike other applications), so that is why the screen shifts when the Windows OS forces the window title to be visible. If you restore the Podium main window so that the window frame is visible, you won’t see the shift when the “not responding” message is appended to the title.
1. Do you run Aero on Vista on your Dev machine?
Yes.
2. Do you have any internet related software running when you use a finished version (not still in Beta) of Podium?
Yes. All the standard Microsoft stuff that comes with Vista, and Avast antivirus.
What model is your CPU?
Zynewave@Conquistador wrote:
I was creating a template in Podium beyond that I am not sure what else you would like to know.
What action were you doing to cause the crash?