Le dimanche 05 juin 2011 à 15:01 +0530, Feroze Naina a écrit : > I have a question regarding the Rendering Profiles GUI > > > Rendering profiles would contain details of container, codecs, frame > rates, audio rates ,etc for a given device which the user can choose.
> We plan to distribute a set of profiles bundled with PiTiVi and also > allow the user to add custom profiles. Sounds good, we could also add default project settings profiles I guess. > We plan make and distribute our own presets based on the existing > Arista presets at http://www.transcoder.org/presets/ and also check > for updates from PiTiVi. We could use the existing Arista code to > start with. This would give us more control over changes. Couldn't we work with them to actually not replicate work, and to profit from each other? > We use one profile file to store several device presets ? (Like under > "Android", we have "G1","Nexus S","Galaxy 3", etc) > Profile GUI: I guess not... see below > We have two ways to do this. > > > a. List each device profile separately: > ( profile_list.png ) > > > Here we list just the individual profiles. So the main list view would > contain entries like " iPad , iPhone , iPod Nano, Samsung Galaxy S, > HTC G1, mkv, DVD " . > > > Though this would result in a long list, it would be easier to add and > remove profiles I guess Android is enough as a profile, no need to add a profile for each android based devise. If I am right about that, then this first solution is the best FMPOV. > > > b. Group similar profiles under a device list: > ( profile_dropdown.png , profile_android.png ) > > > Here we group similar profiles ( like Android, Computer, Nokia N > series ). The user can select it from a combobox and the select the > profile he needs. > > > We can also list the profiles created by the user under "Custom" in > the combobox. > > > nekohayo did not want the users to be able to edit the default/bundled > presets as it would require a button to "Reset to Default settings" > See what I just said, and if we actually need to have different profiles per devise, then yes this solution makes more sense. > > So far, I have made PiTiVi use Arista's profile to get container and > codec names. It is at https://github.com/feroze/pitivi-feroze/ . The > commits are currently incoherent and I'm cleaning it. Regards Thibault ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Pitivi-pitivi mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi
