druidYou are so volatile Infinitoar. I don’t want to neglect you your negative experience nor your apparent need to rant. However, I wish you wouldn’t make assumptions about things that are false.
The .mini files, as I understand it (and anyone is welcome to correct me), are a way for .wav data to be visualised faster on next load. To view a waveform, you must load it and convert it to visuals. The .mini speed this up. I sincerely doubt your .wav files were removed because of the .mini files. I find the .mini make things messy and I don’t like them, however they’ve never caused me issue and I don’t think it has anything to do with your problem. Please find another scapegoat.
The ctrl button problem sounds more like a hardware or user error to me. Why would Podium decide to ignore a button on a whim? Does it depend on whether you hold the button before or after clicking, maybe? I’m not saying your hardware IS broken, I know you’ll want to tell me it works fine in other software, but I cannot believe Podium chooses to ignore key presses sometimes.
I have nothing to say to the rest, as I know you like to express your negative feelings and to vent. I would definitely recommend you choose a software package that works most for you, and if that’s not Podium, then that’s how it is. I hope you can find software that finally works how you’d like it to without making you explode.
Take care.
druidNot my week! I didn’t realise that’s what WOT is so never mind my post. Think I was thinking of Telenator’s thread about a review site…
druidWhoops, so I did misinterpret. Thanks for clearing up, sorry about that! Sounds good. I’m looking forward to seeing where music creation goes on phones, though I doubt I will ever use such a thing. Still exciting!
druiddruidI’m going to sound overly cynical, but if you are truly cautious and skeptical wouldn’t you also be distrustful of WOT? 🙂
druidThe problem is that iOS cannot play VST plugin files at all. VST plugins require an x86 processor and are programmed for a specific OS. VST plugins need different versions if they support both Windows and OSX. So, iOS won’t be able to read VST plugins without extensive redirects, and in some cases, function replacements for features that ARM processors do not have but x86 do.
You might not have meant that specifically in your post? But just in case you did, I wanted to clear up that VST won’t work on iOS. VST developers can, of course, produce versions of their software that function in a different format, but then that format won’t be VST.
druid@Zynewave wrote:
… To be able to do this I’m considering updating the Podium project file format, as the current file format is compressed and not designed to be partially updated.
This shouldn’t be a problem anymore I imagine. Space is no longer as restrictive as it used to be. Considering the quantities of samples and VST plugins most people would have, along with their host, project files almost definitely don’t require compression and just take extra processing power that these days is not desirable, in my opinion. There is a much stronger push (as I’m sure you’re aware) towards power efficiency, partially for battery, and partially because of the “green” push that is slowly taking hold everywhere (leaving aside that this push is mostly surface-deep and does not truly address the issue in a meaningful way in many cases).
Of course, this is taking the assumption that samples are not saved inside the project file as well, but then the files could be compressed themselves and then put inside a main project file which is not compressed, I guess?
If you don’t mind me asking, Frits, was the reason you compressed the project files in the first place? Was it related to space utilisation, or were there other considerations?
druidHad to edit my list as I realised I would like to see a scalable GUI in Podium, one that works throughout (not just text size) and provides a simple scrollbar or point to smoothly resize the interface in settings, making the feature simple and easy to use.
druidAh, I would’ve never made presets in plugins with unicode characters because of the fear that it would result in question marks! I’m mostly an English user anyway, but promote unicode throughout all systems (and I do use Japanese folder names). It’s a pity unicode hasn’t caught on more so, but I can understand why it’s taken so long for many people to move to the new standard.
Other than presets, are you aware of any textual data that would transmit between VST and host, that the user can edit, that might contain unicode? Are folder paths transmitted between Podium and VSTs? Naturally if the VST itself loads, it’s entirely within the VST itself, but I was wondering if some VSTs request paths from the host.
druidI don’t get a lot of time these days, either here or in Podium, so off the top of my head, I’d like to see, (I’m not sure if I want this order or not though):
1. Global MIDI CC learn. I can’t emphasise enough how much I want easy assignment to CC for controller, well, control.
2. Master tempo automation (with an envelope, to allow smooth transitions).
3. Real-time time-stretching of audio, preferably with the ability to set fixed markers in audio files and then move them, to easily stretch differently between points of audio.
4. Support for .flac and .wv (WavPack), perhaps lossy formats like .ogg and .mp3 (though I think .mp3 has licensing fees :S).
5. MIDI routing support (in other words, have a way to direct MIDI signals as well). More or less CymaticCreation’s point 7. (This would be redundant if a modular system was put into Podium, however Frits has expressed that this is not his intended design for Podium. I still miss it however :).)
6. A global clipboard to allow copy and paste of many more elements. Tracks, effect trees
7. Multi-selection of tracks and other elements (what CymaticCreation said in point 12).
8. Truly resizable GUI (fonts, activity indicators, buttons, scroll bars, etc.). I haven’t looked recently at how customisable it is, but it would be nice if a smooth size scrollbar was introduced in settings to automate the whole thing.
Number 8 above is for two reasons: Higher resolution displays are coming, and in some cases it could make the interface too small for some users (not just a small portion either, I’m talking really hi resolution on smaller actual sized screens, for example the iPad 3), and also because I have terrible eyesight. Many people have at least some form of weaker eyesight, especially as they get older – come on science, why aren’t you fixing our eyes effectively! Glasses and headphones is a terrible combination! 🙁 And don’t get me started on contacts…
druid32-bit seems to work with unicode, I tried loading and saving unicode filenames, and renaming items within Podium with Japanese.
Are there any areas that are still dependant on ASCII or similar, or has everything been uypgraded to unicode? Do notes, device names etc. all support unicode now?
druidI need access to VST as I have invested in them, so I certainly couldn’t use a host that didn’t support it. I imagine there would be quite a few people in this boat!
druidSorry I had to cover those basics, you never know what people do and don’t know. I did miss one of your points, it’s quite hard to use mobile devices to read properly I find! 🙂
I am not familiar with the Nanokeys, but most MIDI devices are class compliant, meaning default drivers should be fine. However, if installing vendor-specific drivers helps you, there’s nothing wrong with that either, and at least it helps you!
I usually find most programs won’t recognise my Remote SL if I don’t have it plugged in and powered on before loading the program. Some programs do have a rescan feature, but because I have to at least rescan with any program, I always just try to have it on before opening any audio softwareI think that’s the best way, since programs don’t dynamically react to USB devices being plugged in.
druidThanks for the heads up! I don’t keep up to date on audio stuff online anymore, so it’s great to be told about this. I do try to collect most if not all of Bootsy’s/VOS’ plugins.
Second, the links didn’t work because the tags are wrong. I assume you used the editor, and didn’t just type the tags yourself, so I can only imagine what went wrong, but those links have [/url] in front, and then afterwards, which will definitely not work properly. You can definitely have multiple links in a post.
druidThe problem is, websites such as these use other people’s reviews to base information from. There are no nerds or geeks involved. It’s simply trying to shift different bits of information and collaborate them. Sadly, this is not effective. The reviews for Podium that this information is based off, could be from 1.x for all we know. But where do we see that it’s out of date?
That is the true problem here. There are no claims there that the information is accurate, and they couldn’t; or else they’d need experts in each industry having to review all software for updates and changes.
Big software makes it better on these pages due to being well known, and therefore reviews are biased and/or based on versions that, as a big company, DO have a lot more features. It’s like the difference between selling occasional finished paintings, versus works in progress with the agreement to keep updating them. Podium has always been something that is continually worked on; that means snapshots at moments of time (i.e. reviews) will always be incomplete and misleading, at least to some degree.