Comments

Chienworks wrote on 1/7/2013, 6:16 AM
I can't imagine trying to run even a tiny fraction of a UI as extensive as Vegas' on a tiny touch screen. It would be an awfully frustrating experience. Perhaps something more like MoviEZ would be an appropriate choice. Vegas is a large screen, mouse driven application. It won't scale to tiny devices. If you want it ported to anything, port it to Linux.
rmack350 wrote on 1/7/2013, 9:45 AM
What sort of screen size does a Chromebook sport? That's an android device.

I can't really imagine Vegas on a 10" tablet being all that appealing, but if SCS were to design a touch friendly version of Vegas, more power to 'em. Personally, I think Android devices fill a niche that desktop PCs don't need to address. There'll be fewer desktops sold, but they'll be the right tools for their jobs.

Rob
Chienworks wrote on 1/7/2013, 11:26 AM
Well, Havspappan did mention "Android phones", so presumably he was thinking about smaller screens. But, yes, a 10" or even a 12" screen is just not enough real estate for the complexity of Vegas. Perhaps a much simpler video editing app would work nicely. There's a place for the larger desktops and running major complex things like Vegas is it.

Touch screen is different than mouse driven, but not newer or better. Here's some issues that touch enthusiasts seem to gloss over:

- Fingers are BIG / mouse pointers are tiny. When i touch the screen i cover several control buttons or menu options. I can't see what i'm touching, and i often get the wrong control. Therefore, touch screen apps have to have way larger buttons, which requires a much simpler interface. Also, touch screen apps tend to be used on smaller screens so there is less area to be divided among those larger controls. Example: the photo editor i use on my desktop has about 8 menus and 9 tool bars with a total of maybe 200 controls on screen, and about 95% of the screen is still available for image i'm editing. On my Droid phone, the photo editor has one menu and 6 buttons, and these eat up half the screen.

- Touch screen requires physical reach across the screen. At home i've got two 21" screens. I can access any point anywhere on them by moving the mouse maybe 3 or 4 inches, and my right hand is never far from the keyboard. If they were touch screens i'd be constantly reaching my arms out about as far as they would go, lifting them up, and moving them around a huge area, which also keeps them far, far away from the keyboard. That's extremely tiring and inefficient.

Keep all the "new-fangled" (actually, older than mice) touch stuff on the smaller screens for the simpler apps. I'll keep my huge mouse-driven screen handy for serious work. Vegas as a touch screen app? I think it would be very frustrating and disappointing.
Hulk wrote on 1/7/2013, 11:29 AM
In my opinion you are putting the cart before the horse. The reason that we have Android at all is because tablet and phone devices don't have enough compute to run a full blown OS like Windows. We don't want the version of Vegas that would run on these compute starved devices. I have witnessed Word 2013 running on a tablet running Microsoft Surface and just the act of typing quickly shows high CPU usage in Task Manager. Imagine trying simple editing tasks. It would be a nightmare.

The real question to ask is when will phones and tablets have enough compute to run a stripped down version of Windows and Windows Apps. Convergence. IMO Android is a stopgap measure to get to convergence.

It will begin with Haswell. Intel has already shown Haswell to be able to scale down to 8W. The max power/thermal envelope for these ultra mobile devices is 4W. Intel did say that Haswell will go below 8W but I have a feeling that means 7, perhaps 6W, not enough for tablets and phones. But who knows, we may see Haswell in Tablets, and if we do then we'll see Windows in them as well. And that IMO is when these devices get really useful.

Second, the floodgates will really begin to open with Broadwell which is a die shrink to 14nm of Haswell. It Broadwell can do 4W, which is debatable since we're not seeing 50% decreases in power/die shrink these days like we used to years ago.

Third, the next new processor design (tick) at 14nm will be Skylake and I would bet it will be scale-able to ultramobile devices. Skymont will be a 10nm die shrink of Skylake and will surely be ultramobile capable.

Convergence.

Right now Intel is competitive in the Andriod market but as devices converge to "real" OS's like Windows and iOS, there will be a move to x86 and Intel has a huge lead there. It will be interesting to see if the competitors will try to push Android, which will be death I think as they won't have access to the world of iOS and Windows apps available, or if they will compete in the ultramobile CPU x86 space against Intel. Either way it's going to be an interesting couple of years and good for the consumer.

I have a Galaxy Tab and it fun. It can do some things but it's still more cool toy for me and really useful tool like a laptop. Even with a bluetooth keyboard I can run Office Apps, Vegas, Quickboosk, Coreldraw, etc.. And truth be told the 10.1" screen would slow productivity but the high resolution would make it useful.

Of course this is all simply my opinion!

- Mark
wwjd wrote on 1/7/2013, 3:13 PM
I'd prefer Sony to spend ALL their Vegas resources first fixing, then optimizing regular Vegas.
Geoff_Wood wrote on 1/7/2013, 3:24 PM
I want a version that runs on my wrist-watch.

geoff
pwppch wrote on 1/7/2013, 7:02 PM
"I want a version that runs on my wrist-watch."

We are working on it, but 4k video is causing us some issue right now.

Peter
musicvid10 wrote on 1/7/2013, 7:37 PM
Vegas on a 15" notebook is barely navigable. I more time resizing the preview window than editing.
John_Cline wrote on 1/7/2013, 7:56 PM
We're getting an Acer Windows 8 Pro tablet soon, it's got a 1920x1080 screen, an Intel i5 dual-core processor, 4GB of RAM, an internal 128GB SSD drive and three USB3 ports for external drives. I intend to install Vegas and see what happens.

http://us.acer.com/ac/en/US/content/model-datasheet/NT.L0RAA.005
Geoff_Wood wrote on 1/7/2013, 8:55 PM
Plug in an external (additional) screen ?

geoff
Geoff_Wood wrote on 1/7/2013, 8:56 PM
How lame. My old Sinclair ZX81 was 16K , and that worked just fine !

geoff
Laurence wrote on 1/7/2013, 10:12 PM
Unlike iPhones and iPads, there is a wide range of performance capabilities between various Android devices. My old Virgin Mobile phone for instance could barely play Youtube let alone edit, whereas my new Google Nexus 4 phone actually has a video editing app and is simply amazing.
Havspappan wrote on 1/13/2013, 2:20 PM
Of course not a full version of Vegas rather the brand on a editor suitable for a phone. I sometimes do that to day on the crap editors that is available. It is valuble for short videoblogs because you can do in on the fly. But it could be done much better and for the moment Apple is leading the race.
rmack350 wrote on 1/13/2013, 11:17 PM
I appreciate Havspappan's point about a mobile Vegas being tailored to suit an Android device. There are all sorts of considerations like interface, application size, an appropriate feature set, and price tag. I can't say I've ever seen an android app for more than $25.00. given all these constraints you might find yourself with a cuts-only application that only works with the one or two codecs in use on your device.

If SCS were to do such a thing I think it's purpose ought to be to drive people to Vegas Pro. You want to provide a few cool and useful tools that push the brand forward in a positive way. For example, maybe a helper app that can do something with timecode and logging (assuming Vegas Pro itself could someday deal more professionally with timecode. Right now, helping Vegas with timecode is like teaching math to cats.).

I don't think its a good idea to build an android app that tries to mimic Vegas. Every mobile app I've ever seen attempt to mimic it's desktop parent has been an unusable failure. But, one could build apps that are more appropriate to specific Android platforms.