koalaboyI know what you’re saying – it’s just in practice I haven’t actually found 64bit to be that worthwhile within a single music app.
Sure, if you’re loading huge samples *in the host* directly into RAM, but the chances are you’ll use a software sampler which needs to be 64bit – Podium just has to be able to use it.
I have Sonar 64bit, which works great, and I believe Cubase isn’t too bad on 64bit (but more compatiblity problems), but my main host, Live, is only 32bit and doesn’t really suffer for it either.
Whilst I would love everything to be 64bit, I think it’s more important to solve the problems that most people will have, and that’s likely to be one or two plugins needing to be 64bit due to memory usage – if this can be achieved sooner in a different fashion, it’s good.
I’d much rather workaround hosting a couple of high-memory plugins in a 32bit host, than the vast majority of ‘old’ plugins in a 64bit host (which is why I rarely use Reaper64).
The main plugins I couldn’t ‘live without’ are UAD, and they’re not 64bit anyway.
There’s also the issue of ReWire, which doesn’t work under 64bit I think.
Don’t get me wrong, 64bit is vital in some areas (3D rendering is great with so much memory) but there’s also a lot of “the right tool for the job” to think about.
I personally think that Podium has enough to help it ‘keep up’ as it is, without having to go 64bit, especially in the price range – after all, I bought it because I like the way it does the job.
koalaboy@thcilnnahoj wrote:
Come to think of it, I’ve heard from a guy who switched from Logic to Cubase that he seriously misses this. I never seemed to ‘get it’ though. 😕
Say you want a simple 1/4 pause in your usual hi-hat groove – wouldn’t you have to insert an empty event and restart the looped sequence after that?Seems a bit complicated to me, but then again, I’ve never seen it in action!
Yes. It helps more in the early stages though, as once you know how long a section will be, you’d either just drag out a ‘real’ loop, or duplicate events to the right length – a great feature would be being able to ‘convert a ghost loop’ at a set point in the timeline, that could do this for you.
Another great variation on this is the pattern sequencer track in Reason. It’s also similar to automation tracks if you think about it – something is set to happen until you set another point telling it not to.
(I’d actually like to see a ‘pattern track’, with used defined patterns – so you could insert markers to change the current pattern to named patterns, and each pattern could be a midi event, audio event, or trigger event such as a single midi note triggering a pattern generator).
koalaboyI went to Vista64 due to hardware (core i7 and 12GB RAM) and I’m actually finding it okay. It’s still not my first choice, but everything works for my audio.
koalaboyOne of the best releases yet 😀
koalaboyI really like the track hierarchy, but I get very confused trying to manipulate it.
I tend to use the context menus to move above/below other tracks and into groups.
I can never actually work out how to move out of a group 😳
Preset chains, especially with a hierarchy can be very powerful.
koalaboyI’d like to see the ability (that I think is in Logic) which lets you mark a clip/event as ‘loop until next clip’… So I add a clip, select ‘loop until next’ as a property, and it will loop (in ghost/phantom mode) indefinitely until there’s another event/clip on the track.
This would make certain aspects of songwriting so simple, and be an absolute treat for me 😀
koalaboyAfter several experiments over the last few months, I’d really just like to see some very close integration with (or a Frits-special version of) the jBridge idea.
Keep Podium at 32bit, but allow plugins to be managed as seperate processes, either 32bit or 64bit – it wouldn’t matter.
I realise there are technical issues about window management, but if Podium could effectively treat plugins (or maybe just specified plugins ?) as a seperate process but still keep their window under its own control, it would solve all of the problems.
This could also open the door to network FX processing, similar to that seen in Reaper, etc.
The big problem with 64bit is the lack of compatiblity with VST plugins – yes, I know many more are coming on board but there are a LOT more that aren’t and never will, and it would be unfortunate to lose them on a 64bit system.
Ideally, I want to be able to host Kontak 64bit, and also some free 32bit VSTs that I like the sound of.
An Alternative could maybe be two versions of Podium, with the ability for them to be completely in sync, share the outputs, and also synchronised project load. This may be easier than the plugin processes, but I don’t know.
I have plenty of ideas, but they don’t necessarily gain anything 😆
koalaboy😀 😀
24bit driver works fine now (and I went back and tested 16/24/32 @ 32/64).
I still can’t offline bounce from Live, but realtime does work so it’s not too bad – It would be really nice if the realtime bounce could be set to process automatically as well, on the B key.
Thanks Frits. Great support as usual.
koalaboyWell, 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.
I’m not sure *why*, and it hasn’t affected any other hosts with 64bit engines, but I’m sure you’re more likely to offer a technical explanation than I can 😀
Anyway, I can live with it set to 32bit (and it’s probably better overall anyway), but let me know if you need it tested again at any time.
koalaboy@Zynewave wrote:
@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.
I’ve just done some more testing, and this happens on a brand new project, with any audio – even VSTs. Something’s going very wrong, but I’m not sure how I can track down what it is. The audio is fine in all other apps (32bit and 64bit).
Any thoughts what I could do to get more information ? It just sounds like highly distorted/clipped versions of the audio, to the extent it’s almost pure noise.
koalaboySomething like this would be great:
koalaboy@LiquidProj3ct wrote:
Bump again, please Frits consider add the option of delete and unselect notes with right click, it’s pretty uncomfortable have to switch tools [-o<
Just please not the default option 😕
The biggest thing I hate about FLStudio is the right-click delete. So many times I find myself deleting things when I want/expect a context-menu.
I like Sonar’s fully configurable option. where you can even customise what a different click in a certain ‘zone’ of the note will do. In this way, I can have my default setup completely different from somebody elses.
(Personally, I would like single-click ‘hear’. double-click add, drag from start/end to resize, shift-drag for velocity and alt-click for delete)
koalaboyThanks, Frits. Great work as usual 😀
koalaboykoalaboy@Zynewave wrote:
Interesting. If this product becomes a success, I won’t have to make my own bit-bridge implementation when I start working on a Podium x64 version.
It certainly does the job for most instances when it works. The major downside is it uses seperate processes (obviously really) and so they don’t integrate quite as well by default.
I haven’t tried the cantabile implementation, but ideally Podium could integrate to the extent that when an unsupported dll (32 or 64 bit either way) was selected, it would automatically launch the jbridge version and also keep track of the new process so that it could control the outside process window in place of the normal VST window.
This would make it pretty much seamless and remove the last quirk.
It does seem to work very well though, and hopefully it will allow me to use the current podium with my 64bit VSTs.
Of course, it also means that any 32bit VSTs, if launched this way, have access to their own memory and process space, so that those of us with a lot more memory can utilise it a bit better.
I registered a copy as soon as I saw it, as it really solves a problem.