PiginiYes, hopefully it makes sense from a developers point of view too.
PiginiCan you be more specific when you say that 1.98 did not work for you?
It crashed right away after hitting the power button which start/stops the engine. tested on 2 win98 comps with the same result. Had not done anything else before apart from showing it my vst folder again and choosing the hw in and outputs again.
Just tried it again with the same result. The error message reports an: invalid page in module kernel32.dll at 0187:bff9db61.
EAX=c00308b0 CS=0187 EIP=bff9db61 EFLGS=00010216
EBX=00000000 SS=018f ESP=0090feac EBP=00910148
ECX=00000000 DS=018f ESI=00b30f70 FS=0e47
EDX=7803b630 ES=018f EDI=006b5648 GS=0000
Bytes at CS:EIP:
53 8b 15 e4 9c fc bf 56 89 4d e4 57 89 4d dc 89
when I do exactly the same after installing 1.97 everything works as usual.
Btw. are you the one that voted for Win98 in this topic?
Yeah, so maybe I’m even the only lonely last w98 chick in that shop.
I understand that it makes no sense providing further w98 support if it would mean double coding after swiching the development package.
I often stated, that you have to use your resources wisely and have to have priorities. I’m not going back on my word, if I turn out to be the victim of such principles.
But I hope it makes sense to do the few fixes before switching the development package, to have a completely solid clean code base for the switch. So in case things start going too funky, you don’t have too many potential causes for bugs that might occur after switching.
PiginiBefore I purchased the upgrade I had downloaded a trial version and made sure Podium could compile on VS2008.
Frits:
Did you compile the 1.98 with it?? That would explain, why it did not work for me. (Tried it only yesterday, since I’m not quick with new versions 😉 ) Though some others, not using win98, found 1.98 not as reliable as previous versions. If you compiled it with the newer compiler, there might be some probs involved with it.
PiginiPigni, one huge advantage to moving up to the NT platforms is the NTFS file system which eliminates the 2GB filesize limit imposed by Fat32.
Yes , I know. But does a single audio file exceed 2GB with what you’re doing? It never happened to me. And if needed, it is possible to add Ntfs support to win98. Just as it is possible to add a native generic usb2.0 driver, supporting all flashmedia, cameras, usb drives etc. All just a matter of knowing how.
For audio work on a single computer with a multicore cpu, I would use a dedicated winXP partition optimized for audio, with all unnecessary services deactivated and nothing but audio apps on it. But for my recent setup it’s no option.
PiginiI hoped it would not happen to podium 😕 .
Win98 compatibility was one big reason why I bought it in the first place.
I want to make clear, it has nothing to do with me being stubborn, peculiar or “not keeping up with progress” or such. Therefore that post might get a bit longish, just bear with me 😉 .
I’m neither stubborn nor technically handycapped, nor poor, but I’m a technical purist to whom sentences like “It’s 10 years old. Time to move on.” mean nothing, as long as a new OS doesn’t beat the older one with performance where it counts.
I have my good reasons for favouring win98 for audio work. In my big setup I’m working with several computers at the same time, each one mostly has its dedicated single task, just like an external instrument. They have creamware cards inside(which with sfp version 4.0 work best on win98), so I don’t even need vst-plugins that often.
One thing is absolutely essential, when working that way – low latency, midi timing and reliable syncing. All post win98se OSes absolutely suck, when it comes to that, I tested it. Not always is newer better. Did you know that every cheap old soundcard with midi support via gameport adapter has a lower latency than any new usb midi interface (except for unitor8)?
BTW win98 does score higher than an audio optimized winxp in overall benchmark tests on my systems
Such things depend greatly on the particular hardware and drivers and level of optimization.
The advantages of the newer OS’s are: better general stability out of the box, more RAM supported, multiprocessor support.
Which are not important to me, because:
My win 98 systems run rock solid, they are dedicated optimized configurations, used for nothing else but audio/midi.
If necessary, disk streaming makes up for lesser RAM.
I don’t need multiple processor cores, my hardware is more than sufficient for everything i throw at it. Computers are getting faster all the time, but buying a new one is not necessary, it would be pure consumers greed and fascination for the new gadget.
BTW, solving problems on clients computers is part of my work, I know the newer OS’s inside out. But I know too what I want and what I need and what not.
Keeping podium’s win98 compatibility would be great, if it is possible at all. I know win98 users are a minority, but with some audio working environments it makes good sense.
PiginiPiginiTotalcommander http://www.ghisler.com has ftp-support built in.
It starts with a nag screen when not registered, but is fully functional.
and it’s the best filemanager on windows, good for lots of other things too.
checkout the multi rename tool f.e.
PiginiPigini… the reason I’m doing this is to bundle the plugins with Podium so that total newbie users can start making sound without having to go download various freeware synth plugins.
PLUGINS, plural??? Oh dear … 🙁 (That’s going to cost valuable time and might just let you fall behind the competition with podium as a host)
If bundling plugins with podium is so important why not cooperate with developers of the best freeware plugins and bundle them?
Like f.e. Claes’ shortcircuit is free now, but he could do with some extra PR for selling his Surge-Synth. http://www.vemberaudio.se
I believe your synthmakers plugins would be as good as synthmaker allows, but still, synthmaker plugins can’t beat the real ones, therefore can never be considered first rate. Even among the custom coded plugins the differences in terms of performance are huge. It really shows when throwing dense scores with lots of controller data at them.
I know you mean well with your synthmaker schemes, but reviewers might hold it against you, degrading Podiums overall rating, quickly putting it into the hobbyist-corner because of the “made with synthmaker”-stigma the plugins bear.
As I mentioned earlier, I can perfectly understand you need to do something different from time to time, and how interesting constructing plugins with synthmaker can be. Still, I fear it could do more damage than good for Podium.
PiginiDon’t mean to spoil your fun Fritz, dabbling in your spare time with synthmaker can surely be interesting, but I very much doubt its usefulness for the marketing of podium.
I (and many others) regard that synthmakers stuff a thing for hobbyists, it can’t compete with properly programmed plugins, performance -or otherwise and charging for synthmaker-plugins is widely considered a lame thing to do.
It can backfire and harm your reputation.
If I was thinking of buying podium right now, seeing the developer playing with synthmaker would give me some serious doubts if podium was such a wise choice afterall.
For podiums sake I can only hope, you don’t stray too far from the path.
There is enough to do in the host itself, while the web is flooded with plugins already.
PiginiI don’t see why the step from v.1.99 to v.2.00 should be any bigger than others adding just a 0.01 step to the figure.
Frits is using the version numbering the way it is meant to be, unlike some companies showing big shiny version numbers just for marketing reasons while others might just skip releasing the minor steps in order to charge for the major update later on.
If one is to judge the major improvements of v.2.00 one day, it should be compared with v.1.00, not with 1.99, because v.1.00 and v.2.00 are major releases. 1.99 to 2.00 is only a cent in the version system.
As we have seen in the past those cent improvements are sometimes smaller, sometimes bigger, because some feats need to be there before others can be added.
I don’t think it would make much sense, if Frits spared some new feats just to make it fall on the v.2.00 release, instead of working steadily onwards.
PiginiJust tested the new MMC functionality (with MTC sync) with my MMC capable Atari midi sequencer, it works perfectly. Even if it’s only start/stop for now, it helps greatly getting the midi from the Sequencer into Podium in Sync. Thanks again for it.
Here is a link to a good Midi Routing freeware proggy: http://www.hermannseib.com/english/miditrix.htm
I needed it for merging the backfeeding mtc signal with the keyboard input, but that’s surely not the only good use for a free midi matrix.
PiginiPiginiFor this, Podium must support slave sync. As we have discussed in another thread, other features need to be implemented before this is possible.
Yes, I’m aware of that. Only wanted to know if it was still on the list for future enhancements. Didn’t expect it to be next in line. Just wanted to keep the posting short, sorry if it was not clear enough.
PiginiAs you know already, I have a BCF2000. Will test the new features with it soon and with my mmc capable Atari sequencer. I’m glad you’re into remote control now, since it really gets Podium on par with the pro stuff. Podium felt solid and pro before, but remote control was the most important thing missing.
Will we see support for song position pointer and a tempo controlled metronome too?