@koalaboy wrote:
Is there going to be a 64-bit version of Podium .
I think the time has come to bring the development of a native x64 version of Podium back to the Zynewave discussion table… π
There most likely will be a 64-bit version of Podium at some point. At the moment though I see no need to devote development time on it, until 64-bit Windows gains a larger marketshare. Users have reported that Podium runs fine under 64-bit Windows.
I would have agreed with this half a year ago but things have really changed now Frits.
Of course as you know I have been using Podium on Vista x64, but I have also *not* been able to get past the memory limitations of running an x86 app on an x64 OS. 2GB only for an x86 app. 4GB if the application is LAA which I am pretty sure Podium is not (correct me if I am wrong).
Podium must be run in the WoW64 emulation layer which, can make x86 applications run slower than they would on an x86 OS. π
Also most of my memory is simply not *seen* by Podium. Other benefits at CPU level will also not be used by Podum.
As you can see from the info below the x64 landsacape has changed considerably in the last 6 – 9 months. That is probably putting it mildly.
Comprehensive native x64 support now exists for both software and hardware.
Take a look…
HARDWARE
M- Audio: about 40 products now have x64 drivers
Edirol:
Various Firewire and USB interfaces. FA-66, UA-25 e.t.c
RME:
Hammerfall DPS series
Fireface 400/800
Echo Audio
Audio Fire, Gina e.t.c (AFAICT there entire product line)
I have used the dedicated x64 AudioFire 4 driver for over a year on Vista x64
There could be many other hardware vendors with x64 drivers already.
SOFTWARE Out of Beta (Full releases)
Hosts
Darkwave Studio (Free)
Cantabile 2
Reaper 3
Steinberg Cubase 5 Nuendo4
Cakewak Sonar 6,7,8
Synapse Orion 7
N Track Studio
FMod Ex
Bidule
Sonay Vegas 8.1 and 9
FX
Voxengo:
(Various) at least 13 native x64 plugins Elephant 3, Voxformer 2, Crunchessor 2 e.t.c
Line 6:
Gear Box
Pod Farm
NI
Guitar Rig
Izotope
Ozone 3 and 4
Spectron
Trash
RX (Restoration Suite)
Vinyl (Free)
Instruments
NI
Maschine
Kontakt 3.5
EMU
Emulator x3
Synapse
(5 Instruments)
4Front
True Pianos
Cakewalk
Rapture
z3ta+
Dimension Pro
Studio instruments (Drum Kit, Bass Guitar, Electric Piano, and Strings)
Pianoteq
PianoTeq 3
Garritan
Aria
Steinberg
The Grand 3
Halion 3.5
East West Play Products
(Various)
Motu
BPM
Official site
An excellent You Tube overview video
Vienna Symphonic Library
Lennar digital
Sylenth v.2.2
Spectrasonics
Stylus RMX 1.8
Vember Audio
Surge
Nusfoting
Da Hornet
Still in Beta
Instruments
Spectrasonics
Trillan (x64 version out within a few months)
Omnisphere (x64 version later this year)
NI
Battery
FX
SIR 2
PSP (Lexicon 43,84)
Going forward…
Windows 7
If you do want to try a free Windows x64 version why not download the free (and incredibly stable) Windows 7 x64 version?
1.You can use a single activation key for up to 3 PC’s
2. The Version is a Release candidate and will not expire until June 2010 next year.
3. Windows 7 appears to be very popular amongst musicians and other consumers who see it as a much better version of Vista. There have been reports of lower latency being achieved with Windows 7 compared to Vista but I do think those changes made their way into Vista SP2 as it is a definite improvement over SP1.
4. You can download the free RC version of Windows 7 either as an x64 or x86 version. Nothing stopping you from downloading both of course.
5. A 60gb or more partition should be fine for the x64 version of Windows 7.
6. What about driver and software support as Windows 7 will not be released until October later this year…?
Windows 7 has a very effective IMO and easy to use compatibility mode that you can optionally access (from a rght click menu) before you even install your software.
Easy. You get various OS options to choose from to support. Follow the prompts very easy. My Edirol Ua-25 installed this way without issues.
Of course the x64 version of Vista is also still available (but not free of course).
Thoughts?
Not seeing a x3 increase in CPU here. Just tried to automate a parameter in Trilogy. 10 -12 % fluctuation in Windows task manager (Max). A few percent difference on Podiums CPU meter. All that with at least 4 other apps running at the same time. Perhaps it is Plugin specific.
Running Vista SP2. Final not beta.
Thanks! π
So far so good with Beta 3. Not spent much time on it though. If any thing crops up here I’ll feed back. π
Was it something I said? :-s π
The worldβ’ as we know it can be a challenging place with unexpected twists and turns. Just make sure you travel light and don’t talk to strangers.
Yes UA is right the avatar is er…not nearly an accurate description of your time here. π
Hopefully we will see you here again. I think everyone here agrees you have been a HUGE help. 8)
The Navigator is a very nice piece of work. Lovely.
@Zynewave wrote:
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.
I appreciate there may be a reason or more for Editor Windows to open on start up but personally I would not want them to open if there is no info / data in them. I see no reason for that, but that is just my view. π
That is an extremely good mock up. π =D>
Yes I think the most logical place for those buttons would be above the tracks. I thought about the Inspector Panel but then if that gets closed the Global SMR buttons will be hidden as well.
I have always been a fan of those round buttons in Podium. I love the Create New Track(s) and Child Track(s) buttons you have suggested. Very clever designs! π
I need to think about the contents of the Menu you suggested though. Maybe a user defined set of say 5 -10 commands?
Again a great mock up thcilnnahoj π
Cheers Frits. The Ctrl clicking event and Automation changes are very welcome indeed.
@Zynewave wrote:
@Conquistador wrote:
@Zynewave wrote:
includes general optimization and cleanup of a large part of the engine.
Audio engine overall or just automation? What was the clean up? What sort of difference should one notice?
A little overall code cleanup, which will make my work easier in the future. Nothing you should notice in the performance. It was just a comment on what I had been doing the last few days.
Ok cool. If it makes your work easier it’s a very good thing. 8)
@Zynewave wrote:
includes general optimization and cleanup of a large part of the engine.
Audio engine overall or just automation? What was the clean up? What sort of difference should one notice?
@aMUSEd wrote:
Sorry I’ve only had a brief opportunity to test this so far. Busy with other things. It seemed to work OK – didn’t need to insert a marker to make it record properly this time and no reversions to zero but I’ll try and test some more if I get a chance this weekend.
Cheers aMUSEd. 8)
I just thought you had not seen it yet and were going to miss an opportunity to have your say as the revision is a direct response to user feedback and it looks like Frits might wrap things up within a week or even a few days from now.
But yes I too have little time for testing 2.15 as well ATM.
A bump for aMUSEd and of course anyone else watching this thread that is not already aware of the new 2.15 automation thread discussing the new changes to it. π
@Zynewave wrote:
The 2.15 release will feature a revision of the way that automation (parameter tracks) are handled. For years, the old system has often been the subject of discussion on this forum, so this update has been under preparation for a long time.
The old system handled each curve sequence on a parameter track as a separate playback object, similar to how note sequences and sound events are handled. This had the effect that parameters reset to default values when playback went over a timeline section where there were no curve sequence events. Many users have reported this to be an undesirable behaviour.
The new system still uses the same old curve sequence events and curve editor, but instead of handling all curve sequence event as individual curves, there now is a single track curve. The points in this track curve is made up of the points in the visible part of the curve sequences. The track curve stretches from the start of the arrangement to infinity on the timeline. If you have two joining curve sequences then the track curve is seemless from the last point in the first sequence to the first point in the following sequence. In the old system you could get a sharp edge in the transition between the two curve sequences.
The new system also allows for curve sequence events to be overlapped. This resulted in unpredictable playback with the old system, as playback of the individual curves would conflict. Overlapping curve sequence events can now be used to for example create a fade in/out on top of a longer fade curve.
I’ve considered many different approaches, before settling on this design. Full backward compatibility with older projects was not possible. If your older projects relies on the parameter reverting to default values on parameter tracks, you will need to modify these curves by adding points that will set the curve to the default value. I’m sorry for this inconvenience, but I found it necessary in order to get the best possible automation system.
I still need to do a lot of testing and optimization, and I’m still tracking down some crash-bugs. Those that are eager to try the new system can download the 2.15 beta1 in the VIP lounge.
Please post your thoughts about the new automation system.
Thanks for giving this a look in Frits! Seems like a sensible approach. I don’t have much time to test it though sorry.
I would be very interested in aMUSEd comments. I’ll bump the other thread as he may not be checking the forum (for now) but his inbox instead for replies to that thread about automation in the support forum.
@thcilnnahoj wrote:
Unfortunately I have disabled animations in my browser, so I can only guess what this one does! :-& :-& :-&
(Not working!?)
I could see the first three smileys you posted but the last 3 are just text. Having said that I have no problem seeing the animations from other users posts or mine. 8)