ZynewaveWhen Windows 7 is released (est. end of 2009) I’ll probably treat myself to a new PC with Win7 64 bit preinstalled. At that point I’ll start working on a 64 bit version of Podium. Until then I think my time is better spent on working on Podium features.
Zynewave@fedexnman wrote:
fritz have you contacted anyone at codeweavers or winehq ? it maybe an easy fix ?
AFAIK, Podium is working fine on Linux using the Wine emulator. A port of Podium to a native Linux application is however not an easy fix, and it will require months of work. Same thing can be said for an OSX port.
Zynewave@22tape wrote:
@Zynewave wrote:
Linux port. It is not going to happen for at least a couple of years.
Frits
been about 4 years now 😉
As far as I can tell, during those 4 years Linux has not gained marketshare from Windows, and I don’t see any signs for that to change in the near future. So unfortunately the answer I give today is the same same as I gave 4 years ago.
ZynewaveZynewaveBeta3 is up. In addition to bug-fixes, speed-optimizations and refined graphics, the navigator now highlights the track zoom in the tracks region. The zoom pane can be dragged up/down to set the topmost track in the tracks region.
If there are no unexpected problems with this beta, I’ll probably release 2.16 tomorrow night.
ZynewaveThe fastest way to do this is to select the sequence event you want looped (or copied) and then press the Insert key repeatedly to paste phantom copies. Afterwards you can select the phantom events and use the “clone phantom sequence” edit command.
ZynewaveJuan, I hope you get things sorted, and I’ll look forward to your return. Your input on this forum has been very much appreciated. Take care 🙂
Zynewave@LiquidProj3ct wrote:
wow, its fun. It would be nice that you can resize the “lense” or “focus” vertically also, and move it around.
I’m planning that for a later update. I’m also planning to add a zoom snapshot feature to store different zoom settings. The blank space to the left of the navigator could be used to show buttons or clickable miniature images for switching between the zoom snapshots. A zoom snapshot would store both the timeline and the tracks region vertical zoom settings.
Btw. I’ve scrapped the “lens” word and now use “zoom range” to describe the zoomed timeline (similar to “loop range”, “punch range”, etc.) and “zoom pane” to describe the sliding/resizable pane in the navigator. Does that make sense?
Two small bugs:
1. When you use the hotkeys Ctrl+Alt+Mouse wheel and do the zoom as close as you can, Podium gets freezed, you cannot “un-zoom”.
Fixed in the new beta2. Thanks.
2. If you close Podium with any editor windows opened (not embeded) when you run again Podium you will see that editor without any information opened in the project setup page. This also happens with older Podium versions.
It’s on purpose, so I don’t consider this a bug. Do others think that editor windows should not open on startup? I think it is useful to see the windows layout even if there are no sequences being edited yet.
Beta2 furthermore adds this:
Clicking in the navigator outside the zoom pane sets the zoom range centered around the clicked position. Double-clicking zooms out to the full range. Double-clicking either of the left/right zoom resize handles sets the zoom to the start/end of the sequence. Shift+click+dragging selects a zoom range. Middle-clicking sets the edit cursor position.
Using mousewheel on the zoom pane in the navigator will zoom in and out similar to how mousewheel zooming works on the timeline ruler. Using mousewheel outside the zoom pane will set the zoom range centered around the mouse position.
Fix: The 64-bit engine produced noise when outputting to 24-bit ASIO drivers.
Zynewave@koalaboy wrote:
Well, I’ve found the cause of the noise in the 64bit engine…
My Toneport UX8 had it’s ASIO driver set to 24bit. If I change it to 32bit, it works fine, and back to 24bit, and the 64bit engine gives noise.
Excellent tip. I checked my 64bit to 24bit conversion routine and found a bug. Please try again when 2.16 is released and let me know if you still have problems with noise.
Thanks.
ZynewaveIs the noise present both in live monitoring and in the bounced sound file?
It would be helpful if you can email me a short bounced wav file with the noise.
Zynewave@koalaboy wrote:
1) If, in preferences, I change to the 64bit mixing engine (I’ve not tried this before), and audio tracks just play back as noise. 32bit works perfectly.
Just tested, and I don’t have this problem. If you have any plugins on the track, try bypassing them.
2) If I try to bounce (enable offline bounce and render) any rewire track (currently trying Live 8), it’s always full of crackles/pops/glitches. Normal playback works fine.
It’s possible that Live 8 does not like faster than realtime playback. Try realtime bounce recording instead of offline rendering.
Zynewave@aMUSEd wrote:
I doubt it’s my monitor settings actually – I have a very good Iiyama monitor and have tried all contrast and brightness settings at max and it still renders as virtually black on that system (although it shows up normally on my other desktop PC). And I don’t have IE on either system.
A long shot, but if you have an older graphics card, open the display properties and check if it uses 16 bit instead of the full 24/32 bit.
I’m using IE and I don’t have any problems with the display of .png files. AFAIK the only issue IE has with .png files is that it does not support transparency. There is no transparency in the splash image.
ZynewaveYes. In the tempo event properties dialog you can input the tempo with up to three decimals.
ZynewaveThe splashscreen background should be similar to this:
http://www.zynewave.com/wiki/doku.php?id=guide:index
… with the “guide” text replaced by a version number.
That design has been there for a long time. Please be more specific about when and what difference you notice.
Zynewave