Topic: One Small Request :) …

Sobaka,

Bravo! Bravo! Bravo!

This is the right way to do features requests.
The request must be accompanied by a suggestion or an explanation like this.

Among other things, I agree on almost everything you’ve posted.

@Sobaka wrote:

– Transpose : in Semitones

For a single audio clip, zPitch should be use this value.

Other parameter should be add for “Local” time stretch: – BPM

For “Global” time stretch: the BPM of all clips match the project tempo.
If the BPM value is not set then no time stretch for that clip.

@Sobaka wrote:

Use the “Mouse Wheel” to change parameter value …

And…to get a more accurate value setting: Shift + Drag (Ctrl+Drag).

@Sobaka wrote:

to be continued …

is that a threat? 😆

May I just say that, considering all the messages so far about development of Podium turning towards different system types and it taking time away from other matters, Mac OSX support seems like a not very good idea! Unfortunately for one-man outfits, though, Apple products, including their computers, are increasing in usage, and I do wonder if things may need to be coded for both (or, heaven forbid, soemthing becomes standardised enough so that applications can run on either; but this will never happen, I’d eat a hundred hats if it did).

I just gotta chime in and say that I really enjoy reading this thread. Whole lotta interesting stuff here.

Keep up the good work!

Cheers, Alex

Telenator: I kind of agree with you, and disagree with you. I certainly wasn’t talking about iPads either, unless they suddenly gain the ability to run OS X software (which they won’t).

I have seen Macbooks become more and more popular however, and while I’m not certain if Apple can increase their share of that market, they’ve already surpassed what I initially thought they would achieve. I’m disappointed, personally (despite the positive competition it provides Microsoft, Google and so on), but I’ve known quite a few people who have switched to the Apple ecosystem, including for desktop computing environs.

sobaka: Rewriting for OS X is not as simple as you might think. The fact that Apple desktops (at least recently and for the near future) use Intel CPUs makes it much easier, but there are still many Microsoft libraries that many people use during coding for Windows. I would assume Frits also does. If so, to code for OS X means to write new bits or find new libraries that cover the same functions required, that were already coded for Windows. Any DirectX programming, which is extremely common even for 2 dimensional GUIs in Windows now, would not translate to OS X. There may be libraries (free?) available to help mitigate this effect, but they also may have a performance overhead that isn’t initially accounted for.

Image Line has been trying to produce an OS X version of FL Studio and I believe it was aimed for release sooner (possibly for the 11 release?), but I also believe now that too many issues were run into.

It really does take a lot more effort than you might think. Having done programming a little myself, I would certainly not envy needing to maintain at the very least two code bases (meaning needing to invest in infrastructure to test both as well, which also exponentially increases time spent coding for both).

An OS X version would also be typically expected to support OS X plugin formats (RTAS? I don’t remember what they are); this is something that I expect Frits has not done. That’s even more time spent.

His focus on iPad would’ve done similar, but gladly (at least for me) with x86 Windows tablets coming into market, it would allow him to save a lot of time by using close to the same ecosystem he was already programming for.

Anyway, I’ve probably gone into it enough. Sorry for the wall of text!

Oh! No real issue at all, I was surprised to see you say that only because I’d seen and heard lots of people considering moving to OS X desktops. Note, considering. Not all have shifted, I suppose. Many people are happier with the cheaper models … but they can still get even cheaper Windows PCs.

Actually, I’m quite happy if what you read is correct about Apple dekstops slipping back a little. 🙂

So yeah, I wasn’t taking issue with your post at all. Happy to read that one. 🙂 I was actually more interested in pointing out to sobaka why creating an OS X version of software made originally for Windows is likely a lot more effort than sobaka appears to think.

A thoroughly thought out list of feature requests there, sobaka!

Love the idea of the Inspector Toolbar for adjusting clips.

• Random Options on “right click” for points

• The Adjust Points dialog has a randomise dial with a button to generate seeds.
• I would love this on plugin parameters. This would give instant preset generation.

• Eq In Mixer
Currently you can enable the drawing of zPEQ on the mixer channel. At the zoom slider’s maximum, it will be ≈ 285px X 145px. I like the idea but I’m wondering what happens when you have numerous zPEQs as inserts?!

• Modulation Track
Love this idea!
To extend on it, I would prefer it didn’t control parameters on its parent track. Rather, the primary and secondary slots would be receptive to any parameter object in the Device List.

• ‘Hide Track’ button
Assuming you mean a button to ‘Hide Track Header’, that is available as a slight variant. Drag the right edge of track headers to the left. They minimise all the way down to a few pixels. No doubt this would be easy to implement.

• Some Tools For Mastering & Sound Design :

1. New option in “export sound file”. ie. Import into the project.
   1. If you’re exporting the arrangement, the master track will render a bounce. When you save the project, a *.wav file will be created in a subfolder next to the project (*.pod) file.
   2. Same goes for a stem; the bounce render of children to the master track.
   3. If it is a single sound event on the timeline it will reference the sound file you export.
   4. If it is a new sound event, one that is a merging of numerous sound events, or recordings, it will ‘save with the project’.

   Newly created sounds, as described in a, b and d, save with the project in a subdirectory of your project folder:
   …(Projects folder)(Project name)(Arrangement name)
   For circumstance c, export to the directory mentioned.

• Eq in Mixer

While the mixer limits zPEQ’s interface, though sufficient IMO…

… the Rack Editor in the Inspector can be resized for fine editing. The rack is great ’cause it shows signal flow, of selected tracks, through parent tracks right up to the master.