Connect Meeting and Client-side Speaker Audio Output Control

There is a Connect feature request from various customers in place asking for the Connect Meeting GUI to offer an option to choose audio output devices. The request is a complex one because the audio output control options are opaque to Flash; the settings for audio output are in the various operating systems (OS) of the many possible clients. Connect uses what is chosen as the OS default as depicted in our help documents:
Set up audio broadcasting
The feature request number is: CONN-4082570; one customer recently suggested that we add expanded functionality for client speaker audio output control roughly similar to what we already have in Adobe Connect for Microphone and Webcam selection.  A speaker drop-down menu for sound output is desirable for obvious reasons.
There is no set date for implementation of this enhancement in Connect and I will update this blog entry if that changes. In the meantime, if the default client OS audio output option is not the option desired for use with Connect Meeting, the following example may help: I will show how to add a Bluetooth speaker to a Windows client and toggle the audio output in Connect from the built-in laptop Realtek speaker to a new iHome Bluetooth speaker. While audio output options may vary, by showing how it is done with this common example of a Bluetooth output device, it will hopefully help to show how other optional client-side speaker output devices may also be managed in kind.
To see the enabled audio output options on a Windows client, look at the Device Manager under the Control Panel:

Here we see a Realtek device and this corresponds with the option in the lower right of the desktop tray:

Opening the mixer shows more detail:

If I play music by invoking the Audio Setup Wizard in Connect Meeting, the Realtek speaker will play:

Since our example will be to switch to a Bluetooth speaker, the first step will be to make certain that Bluetooth is enabled. On my Lenovo, that is done by pressing the keys FN>F5 simultaneously. Here we see Bluetooth is enabled:

The next step is to follow the device instructions to pair the Bluetooth speaker with the client computer; these will vary.
See the Bluetooth icon enabled and  highlighted in my system tray:

After putting the iHome speaker in pairing mode, I am able to search for it from the client:

Now we have more than one speaker option to toggle as the Device Manager and the system tray attest:

In Connect we now see the option to use the new audio output device:

Note: The iHome Bluetooth speaker also has a built-in Microphone so the Connect Audio Setup Wizard will see it in the Microphone drop down menu.
Without audio output controls built into Connect, adding and/or changing the default audio output device in the client OS is the way to toggle the audio output option in Connect. The key thing to be aware us is the danger of audio feedback loops. When separate speakers feed back into a microphone and cause echoing in a Connect Meeting. On a mobile device such as an iPAD, without a headset the speaker audio will feed right back in the microphone; it is best practice to use a headset with iPad to prevent audio loop/echos.

An Interview with Tom Krcha, Adobe XD Product Manager

What follows is an excerpt from a post originally appearing on Khoi Vinh’s Subtraction blog. Read the post in its entirety here.
A few weeks ago Adobe released the first public preview of what the company is now calling Adobe XD, its major new UX/UI design and prototyping tool—you can download it here. This early version is missing several key features, and a long road to the full 1.0 launch lays ahead. Nevertheless, the preview is workable enough that professional designers can begin to see firsthand whether the app can deliver on the innovation that has been such an integral part of its promise. This milestone seemed like the right moment for me to interview Tom Krcha, a key member of the product team who has been with the project since the very beginning, before it was even called Project Comet. I asked him to reflect on how XD first came to life, what it took to get it to this release, and the long-term vision that is guiding him and the team.
Full disclosure: Since August of last year I have been an Adobe employee. As with all of my posts, this interview was not submitted to management for approval.
Khoi Vinh: Let’s start at the beginning. How did XD first come to be?
Tom Krcha: It started around mid-2014. I was working with the Behance team on some new apps, and we were prototyping new ideas all the time for them, using many different tools to do that. None of them seemed to be ideal. They lacked continuity; the ability to let you jump from an idea into a design and then mock up a quick prototype that could be easily shared—that seemed so obvious, but very distant from the reality back then. I wanted to speed up the way we iterate and communicate our ideas.
So I collected a bunch of the thoughts into a slide deck—a very quick mood board, nothing polished—and shared it with some people I knew around the company, just to see what others thought of it. Some of the ideas were around constraint-based adaptive layout, reusability, in-context editing, fast but precise vector UI and icon drawing and so on.
I quickly discovered that other folks at the company were thinking about similar things as well and in fact there was a lot of passion for this topic. We all met together and soon after assembled a small team of people, like a startup, with a mission to explore and re-think current UI/UX design workflow—if we could imagine anything and start with a blank canvas, with no limits. The whole process was really exciting.
I want to hear more about that process but first: by mid-2014 Sketch had already gained tons of traction, and the market for design tools had become quite robust. I have to imagine you and your colleagues were watching the market, right?
It’s true that there were a lot of design tools out there. But when we stepped back and took a broader view of the market, it seemed like there were a lot of opportunities to rethink traditional tooling. Demand for mobile apps had exploded. App design had matured and became more functional, and had moved towards flat design, which I think was an important break point. Designers started to think more about products and less about graphics. And motion and interaction started to play a much bigger role in app design. It was clear that we had entered a new era of designing products.
However we knew that building a new tool would take some time. It just doesn’t happen overnight. So I think everyone was less worried about what was happening at that moment and thinking further ahead. The thinking was to leapfrog the current generation of tools and jump to the future. To build an electric car of design tooling.
So do you believe most of the UX and UI design tools that debuted over the past two or three years are too focused on the “today” of the craft, and not enough on the tomorrow?
Yes. There is so much more that designers would love to have to simplify and speed up their process. Designing at the speed of thought is where we are all heading.
Getting to “speed of thought” tools requires negotiating the tradeoffs between ease of use and high fidelity—a WYSIWYG interface versus a code-intensive interface, is that right? How did you strike the right balance for XD?
That’s right; high fidelity and ease of use often go against each other. When we first started working on XD, we knew that we wanted to build a tool for any designer to pick up and start using right away, and to be able to use day to day. We decided to squarely focus on the design side and not on the development side of things, and also to stay platform agnostic. We talked to many designers—many advanced designers, but also emerging designers who haven’t necessarily adopted any given tools and who are just starting to look around, which is great, because they are less anchored to specific solutions. We learned that no matter what skill level they are, they want to start quickly and move fast. One of our core principles has been “comfort first,” meaning that the tool shouldn’t get in your way; it should be very straightforward. It should almost feel invisible, performance included.
What are some examples of those “comfort first” decisions you made?
There are many. The contextual property inspector shows you just what you need when you need it. We have recent files and UI kits available on the welcome screen for immediate use, so you don’t have to hunt for them. One of my favorites is ghosting. Whenever you have an object, let’s say a photo, that gets clipped by an artboard, we display the clipped part ghosted with opacity to help designers work easily with the full object context. This applies to the Boolean operations and soon to the masking as well. Another example is the distance decorations/guides where we combined snaplines and distance measurements together to minimize distractions. Some of these things are subtle, but when you experience them they feel so obvious.
If I’m a new user, what should I expect from the first time (or first few times) I use Adobe XD? Will that comfort be obvious to me right away, or is there a learning curve?
We tried to minimize the need for learning. The basics, such as drawing and layout, should feel familiar from first launch. There are definitely features that users need to learn about, but they will feel natural after using them one or two times. For instance you can drag an image from your computer directly into a shape in order to mask it—no need to actually tell the app to mask the image to the shape. It’s such a logical thing to do but I haven’t seen other tools do this.
We’re coming up with a set of heuristics like this that will make sense to everyone. One example is if you duplicate an object multiple times. We know that and we can show a contextual hint that says “[⌘R] Turn into Repeat Grid”, which might actually take the already duplicated objects and create a repeat grid for you quickly. Another place where it comes handy is the path editing, since there are many operations you can do on points with different key modifiers or gestures.
We’re still building the proper onboarding experience, and that’s a big part of the learning. We know that many users won’t read or watch long tutorials, but maybe there are more contextual methods of helping them learn about things that’s right within the tool. So you’ll see contextual hints that provide just enough guidance by showing you shortcuts for commands related to the currently selected object. Of course this will only be useful if it’s valuable enough and very subtle that it doesn’t interrupt the design process.
How much are you finding that the XD beta testers are struggling with the biases and preconceptions that they might bring with them from other tools?
Ha, yes. There is definitely one that I am constantly fighting with: the zoom tool. Our zoom has this Mac or iOS native feel. Pinch-to-zoom to a specific area on the trackpad or option and scroll on the mouse. It’s a buttery smooth zoom and I’m sure users will love it.
However, from the feedback we’ve learned that users are struggling to find the actual legacy zoom tool—the rectangle/marquee zoom. I definitely see a use case for that but pinch, in my opinion, has a much more natural feel. We’ll eventually support all the use cases, but it’s one of those things that I wish we could just skip.
In general though, how open to change are you finding the beta users?
I think lot of that goes back to onboarding actually. If the intention comes across clearly then it’s easy. However, we sometimes get a lot of feedback on certain things. That’s actually great. It’s exactly why we decided to start a dialog with users early on. First to really see if certain ideas are just crazy or just cool but are really edge cases, or if they will resonate well and speed up the workflows significantly. Sure, you still have to trust your expertise and gut, when making decisions, but having usage data and qualitative research helps a lot to settle on a decision. Either way, innovation is hard, especially when you are fighting expectations that are often not clearly articulated—because “it used to always be like that.” I think we can do so much better in areas such as symbols, styles and layers and not just take what’s out there.
Read the rest here.



SNSプロフィール画像テンプレートの使い方 / 無料テンプレート

※ 画像をクリックするとページに移動します。


Robbie Carman tells stories with color

Professional colorist maximizes the power of video using Adobe Creative Cloud
Robbie Carman will be presenting the session “Work Like An Editor Think Like A Colorist using Adobe Premiere Pro” in the Adobe booth at NAB 2016 on Tuesday April 19th at 10:00 AM, Wednesday, April 20th at 2:00 PM, and Thursday, April 21st at 9:00 AM.
Robbie Carman is passionate about color and the power it brings to storytelling. So much so that he established Washington, D.C.-based DC Color to focus solely on color correction. His single-mindedness paid off. DC Color has graded hundreds of hours of television, documentary, feature film and political programming. But people looking to glean ideas and information about color need not trek to Washington, D.C. Carman gladly and enthusiastically shares his knowledge in multiple venues, from online classes and training videos to books and seminars.

Adobe: What’s your background as a colorist?
Carman: When I started out, I fell in love with the aesthetic and technical side of editing, solving problems and making shots look better. As NLE tools became more sophisticated, I found myself doing more and more color work in the context of being an editor. Clients kept coming and I realized I wanted to do color full time. In 2005 I founded my own studio, and started calling myself a colorist rather than editor.
I’m lucky. A lot of one-man shops do a little of everything: filming, editing, audio, and so on. I’ve been successful doing the one thing I love, focusing on color to enhance video content and help people tell their stories.

Adobe: Where did you go to school?
Carman: I attended the School of Media Arts and Design at James Madison University. The program was a blend of traditional film school and hands-on experience. We learned by getting out and making films. That impacted the way I like to teach today. I want people to feel the same passion that I do and I try to bring that to all my presentations.
Adobe: Tell us about your work as a teacher.
Carman: I love communicating, teaching, and sharing information with people. Since the late 1990s and early 2000s, I’ve been fortunate to develop relationships with other professionals, and have co-authored seven books. I also do online training with and other sites. I love the fact that I can come home at night or go on a trip, yet still be in the classroom; I see people in that moment where they “get it” for the first time, which is so rewarding.
Two years ago, I teamed with two other colorists, Dan Moran and Pat Inhofer, to create Mixing Light, a website that teaches digital color correction for video and film. As far as we know, it’s the only website dedicated to the art and craft of color grading training. We work across multiple platforms, including Adobe Premiere Pro and SpeedGrade. We want to get people as excited as we are about color.

Adobe: What are your thoughts on the Lumetri color tools in Adobe Creative Cloud?
Carman: It’s exciting that Adobe has been integrating color workflows directly into Premiere Pro since the purchase of SpeedGrade a few years ago. People who are using Premiere Pro as their main editorial tool now have power in their hands to work like a professional colorist. And they can do so in a tool they are comfortable with, using a workflow that isn’t foreign to them. People can use as little or as much of the powerful underlying technology from SpeedGrade as they choose, and quickly improve their video content.
The tools are similar to Lightroom, which is used by millions of photographers around the world. Those same people are now doing very creative video projects. For them and other users coming to Premiere Pro from multimedia backgrounds, these tools are perfect.

Adobe: How do you tackle a typical color project?
Carman: The first step is evaluation. On the technical side, I evaluate shots with video scopes which have seen a major update in Premiere Pro. On the aesthetic side, evaluation involves asking clients lots of questions: what is their color palette? What’s their preferred level of saturation? And so on.
The next step is corrective: fixing obvious problems. Then it’s a process of truly enhancing the content. Is there a detail in the shot that stands out? Maybe it’s an actor’s bright blue eyes; can I highlight them, sharpen them, add blue?
The last step is living with the footage and looking at it a lot. There’s an old adage that films are never finished, they’re just abandoned. My job as a colorist is to do the best possible work we can do, efficiently and quickly, before we move on to the next project.
Adobe: How do you choose what tools you’ll use for a project?
Carman: The choice of workflow is part of the evaluation process. I talk to editors constantly. It’s important that I know what the project was cut on: Premiere Pro, Final Cut Pro, or Avid. I have to be versed in all of those editorial tools because I interact with them all the time. This helps me understand what an editor has done that is good and can stay, what I can rebuild, and what needs to be redone.
We’ve integrated SpeedGrade for many projects. The Direct Link workflow lets me open a Premiere Pro project directly in SpeedGrade. Adobe products also communicate well with other products, which speeds the workflow. There are times when doing a traditional conform from Premiere Pro to DaVinci Resolve is a non-starter. In these cases, it is great to be able to use Direct Link between Premiere Pro and SpeedGrade.
Adobe: Have you seen a change in how non-specialists approach color?
Carman: The most exciting thing over past 5 to 10 years is that clients walk into the suite and are already communicating like colorists! Ten years ago, if you talked about a lookup table or LUT, anyone who wasn’t a colorist would have no idea what you meant. The work Adobe and others have done to integrate color into their tools has made a big difference.
Adobe: Do you feel like developments such as the enhanced color workspace in Premiere Pro threaten your business?
Carman: Not at all. To me, it’s about putting color in the forefront. If the tools are ubiquitous, it puts the emphasis back on talent. I’m not worried about losing work. Color is what I do day in and day out, so if I can share that knowledge with people using Premiere Pro all the better!

The Value of Experiences – Five Things Every Company Should Do to Succeed


Recently, I had the opportunity to speak at the Financial Times and Paul Hastings’s inaugural event on Tomorrow’s Global Business. A few of us from the financial, technology and academic sectors shared our thoughts with FT’s Richard Waters on how incumbents in the tech industry should think about growing their businesses in the wake of continuous disruption and uncertain markets.
One of the common threads in our discussion was around unlocking value in a world of a more connected and engaged consumer. Every company is one breakthrough app away from potential extinction. Brands who win find new and unique ways to deepen customer relationships and experiences.
At Adobe, our sweet spot is helping customers deliver great digital experiences that get results. It’s something we’ve been working on ourselves and was an impetus for our successful business model transformation from a shrink-wrapped business to a SaaS-based subscription model. Moving to the cloud has enabled us to deliver innovations faster, to interact more frequently with our customers and to continuously improve the customer experience using data and insights.
In my opinion, there are five things every company must do to deliver value in today’s experience economy:

Self-disrupt: “Disrupt or be disrupted” is a common mantra at Adobe, and extends across our business model transformation, innovation ethos and employee engagement. It’s about looking inward as much as it is about looking outward. And it takes guts to make the change, especially when things are going well. My advice to management teams is to ask yourselves, “Are we doing everything to deliver the most compelling experience to our customers?” If the answer isn’t a resounding “yes,” chances are you need to make some changes. And tweak constantly because chances are, you’ll never get it all done the first time around.
Rethink your audience… and your addressable market: In today’s connected world, you’re not just engaging individuals, you’re engaging entire communities. Think about how your products or solutions scale across traditional audiences to empower a broader group. At Adobe, we’re engaging bigger communities than ever before through Behance, Adobe Stock and our creative mobile apps. Uber has leapfrogged the taxi industry by empowering a community of drivers. Netflix has successfully re-oriented its sources of content to engage a broader community and in turn expanded its viewer base.
Use insights, test and optimize: Figure out how you can create meaningful, high-value, highly relevant experiences by translating data into insights, and then test, retest and optimize the interaction. The Royal Bank of Scotland’s award-winning Superstar DJ team is a great example. That team has transformed static, one-to-one online banking interactions into a full digital dialogue which anticipates customers’ needs, and provides the data and also means to move forward quickly.
Get personal: A personalized digital experience helps you to connect with your audience in a way that’s unique to them and you. According to recent research by Adobe, more than eight out of ten consumers overwhelmingly prefer to get personalized ad content compared to generic ads. From my own experience, I’d much rather stay at a hotel that knows and anticipates my preferences or finds ways to save me time through fully mobile experiences. Not many businesses are very good at personalization yet, which means that those who are ahead of the curve have the advantage.
Build shared value: “Personal” has added meaning when your brand’s values can align with those of your customers. The work that comes out of Red Bull Media House, known for sports, music, and lifestyle offerings for adventure-seekers, is a great example where a company is connecting with its community and delivering and monetizing customer value. Our partnership with FEED, seen most recently in the Adobe + FEED Make It Challenge, brings together values that are important to us and to our community – creativity, design and social good.

Companies that are succeeding in today’s digital economy have uncovered a simple, yet powerful truth – that the relationship between brands and their customers is one of equals. The experience is king. It’s how you deliver value.
You may also like

A better way to innovate: think markets, not products
How this Olympic sport can boost creative thinking
Mobile experience is the differentiator

New App Helps Hartford Funds Reach Financial Advisors

A pair of new mobile apps is helping Hartford Funds market to both internal reps and financial advisors who recommend products to their customers.
“These are two diverse audiences,” noted Mark Kitson, director of digital marketing, Hartford Funds, who spoke at the Adobe Summit this week.
A major challenge was to differentiate the brand from the competition. “Performance cannot be the only reason to choose a mutual fund company,” he says. “Insights and value added content are key differentiators.”
Hartford Funds’ products must be purchased through financial advisors. Their marketing efforts also work to help wholesalers within the organization, who work to promote Hartford to the advisors.
The brand wanted to deliver sales material—like stats about funds, whitepaper PDFs and video—in an engaging and easy to access format.
It also wanted to take content created for one channel and leverage it in another—for example, use case studies created for email to help populate the mobile app in a responsive format, powered by Adobe Experience Manager Mobile.
The first app, created for the internal wholesalers, launched in February. An app for financial advisors will launch in April.
So far, reps are adapting to the app quickly. Of the 66 that are using it, 90% report using it at least once a week, and 50% are using it on a daily basis.
The audience for the financial advisor app will be significantly larger; there’s a potential user base of 30,000 reps around the country. The app’s content will be updated quickly, and it will be the first public presence of Hartford Funds in the App Store.
(This was originally published by Beth Negus Viveiros of Chief Marketer. View the post here.)

Dropbox-Integration jetzt für den Android Acrobat Reader verfügbar

Autor: Ulrich Isermeyer, Sr. Business Development Manager, Adobe Systems GmbH
Seit Ende letzten Jahres besteht zwischen Adobe und Dropbox eine enge Partnerschaft mit dem Ziel, die Arbeitsweise von Menschen und Organisation mit Dokumenten zu vereinfachen. Wir wollen euch dabei helfen, produktiver zu sein und PDF-Dokumente so zu nutzen, wie ihr möchtet. Dazu gehört auch der Zugriff von mehreren Geräten aus. Egal ob zu Hause, im Büro oder von unterwegs.
Vor diesem Hintergrund freue ich mich, dass wir jetzt die Dropbox-Integration auf die über 300 Millionen Kunden von Acrobat Reader ausgedehnt haben, die unsere App auf ihren Android-Gerät installiert haben. Das Dropbox-Team hat ein Update für die Android-App herausgegeben, so dass ihr die Vorteile der Integration direkt aus der Dropbox heraus nutzen können.
Erst kürzlich haben wir auch für die Nutzer von iPhone und iPad (die Adobe Acrobat Reader App für iOS steht hier zum Download zur Verfügung) ein entsprechendes Update veröffentlicht. Selbstverständlich steht die Dropbox-Integration auch für unsere Desktop-Anwendungen Acrobat DC und Acrobat Reader zur Verfügung.
Das bisherige Feedback eurerseits dazu war großartig. Viele von euch nutzen die neuen Möglichkeiten: In den wenigen Monaten seit der Verfügbarkeit haben Millionen Menschen ihren mobilen Acrobat Reader mit ihrem Dropbox-Account verknüpft. Mehr als eine Million in Dropbox gespeicherte PDF-Dateien werden jeden Monat mit Acrobat Reader Mobile geöffnet.
So verknüpft ihr eure Acrobat Reader Mobile App mit Dropbox
Aktualisiert einfach eure Acrobat Reader App auf eurem Android-Tablet oder –Smartphone, um die Vorteile der Integration mit Dropbox. Falls ihr die Acrobat Reader App noch nicht besitzt, könnt ihr sie euch jetzt hier herunterladen.
Außerdem hat Dropbox seine Android-App ebenfalls aktualisiert, welche ihr hier herunterladen könnt.
Nach dem Update oder der Installation von Acrobat Reader Mobile auf Android ist es ganz einfach, ein Dropbox Basic-, Pro- oder Business-Konto hinzuzufügen. Sobald die Verbindung hergestellt ist, habt ihr direkt aus Acrobat Reader Zugriff auf alle PDF-Dateien in eurem Dropbox-Account.
Nach der Installation von Acrobat Reader Mobile fügt ihr euer Dropbox-Konto einfach hinzu und schon erhaltet ihr Zugriff auf alle eure in Dropbox gespeicherten PDF-Dokumente.
Auf der Dropbox-Seite werdet ihr nach dem Update oder der Installation aufgefordert, “weitere Funktionen mit euren PDF-Dokumenten anzuwenden.” Mit einem Antippen könnt ihr dann den Acrobat Reader aus der Dropbox heraus öffnen und Dateien ansehen oder bearbeiten – ganz wie ihr wollt!
Mit der Vorschau der PDF-Dateien in der Dropbox-Android-App könnt ihr den Acrobat Reader öffnen und häufig genutzte Funktionen in euren Dokumenten anwenden.
Weitere Funktionen
Wenn ihr die Verbindung zwischen den Adobe- und Dropbox-Apps hergestellt habt, könnt ihr die PDF-Dateien im Acrobat Reader Mobile elektronisch signieren, Stellen hervorheben und kommentieren, und eure Änderungen werden automatisch in die Dropbox zurückgespeichert.
Es ist dann ganz einfach, die aktualisierten Dokumente mittels Dropbox-Links oder geteilten Verzeichnissen mit Freunden oder Kollegen zu teilen. Und ihr könnt euch darauf verlassen, dass die Dateien mit Dropbox synchronisiert werden – egal ob ihr auf eurem Android-Smartphone oder -Tablet, auf oder an eurem Computer arbeitet.
Haltet uns auf dem Laufenden!
Mit über 18 Milliarden in Dropbox gespeicherten PDF-Dateien freuen sich die Adobe- und Dropbox-Teams sehr darauf, die Integration nun auf allen Plattformen und Geräten anzubieten.
Wir hoffen, dass insbesondere die jetzt neu hinzugekommenen Android-Benutzer an den vielen neuen Möglichkeiten Gefallen finden. Haltet uns dazu doch auf dem Laufenden und teilt uns eure Meinung in den Kommentaren mit.
Über den Autor:
Ulrich Isermeyer ist als Senior Business Development Manager bei Adobe für die Document Cloud sowie für die Technical Communication Suite verantwortlich. Dabei berät er in Deutschland, Österreich und der Schweiz strategisch Endkunden und Vertriebspartner rund um Acrobat, eSign, Framemaker und weitere Lösungen von Adobe. 

Summit Sneaks You Have to See


Ah Sneaks … the wildly popular session at Adobe Summit where our data scientists take center stage and give us all a preview of what they’re cooking up in Adobe’s research labs. Although each Sneak demo is only about four minutes long, it represents work that has been months — or maybe even years — in the making.  While we’ve got thousands of engineers at Adobe doing a lot of amazing things, only a select few projects will ever become Sneaks. So you can see why it’s become a fan favorite at Summit and Adobe MAX events.
Some of these experiments make it into products, for example SmartPic that was shown at last year’s Summit Sneaks is now in beta in Adobe Experience Manager 6.2 – but there’s no guarantee. Whether or not these projects become product features, it’s fun to see these tech geniuses get the celebrity status they deserve for working some marketing magic.
Speaking of celebs, this year’s Sneaks was co-hosted by Thomas Middleditch, the star of HBO’s Silicon Valley, and our own Steve Hammond, senior director of strategy and innovation. They introduced seven projects that ranged from a look at the future of the shopping experience, to tech that makes designing and building apps faster than ever, to a system that helps marketers not over spam their customers – and they had some fun along the way.
Unlike our keynotes that we live stream, Sneaks is a session exclusive to those on the ground, but shhhh… we’re making some of it available for those who couldn’t be there with us. Here’s a wrap up of our favorites from our Summit 2016 with video replays:
Fusing the digital and physical world, this sneak showcased a retail store shopping kiosk that scanned the presenter’s body and suggested clothing with just the right fit and style. Thomas got in on the fun in this demo!

Even though Adobe Experience Design CC (Preview) just launched, our teams are dreaming up ways to make it more useful. This demo connects designers and marketers to create and deliver amazing mobile apps fast across the Creative Cloud and Adobe Marketing Cloud.

There was some big data wizardry on display during this sneak. It helps marketers accurately and consistently understand how every offer is performing across mediums such as email, display and mobile apps. Data algorithms also highlight trends in the data that marketers need to act on.

Admit it… you’ve hit the email unsubscribe button a time or two when you’ve gotten tired of receiving offers from a company – and sometimes you just start trashing or marking them as spam. This demo showcases how data science is helping marketers know when their customers are reaching their limit so they can dial back their emails and keep the relationship going.

You may also like

Virtual reality creates new perspective on Adobe Summit in Vegas
No more lines: A preview of shopping in the future
“Peek Behind the Sneaks” series – highlight sneaks from past events and tech innovators behind them

Video: Build apps with business impact

Content and the mobile experience are more important than ever. In fact, according to consulting firm Accenture, 82 percent of digital strategy executives think that mobile apps are integral to their business, with 81 percent of executives believing that mobile apps are key to unlocking data from across their organization.[1]
But in large enterprises, creating compelling mobile apps can be a challenge – especially when you consider the demand for mobile apps and the limited bandwidth IT and marketing have to deliver these experiences. Combine this with the challenges of delivering apps across platforms, driving engagement with those apps, and ensuring streamlined mobile content production – and it can seem daunting to go it alone. In a recent webinar, Nick Bogaty, Senior Director, Adobe Experience Manager Mobile, outlined how these challenges informed the development of Experience Manager Mobile – and how the solution is helping companies create, deliver and optimize compelling app experiences with improved time-to-market and ROI.
Watch the 60-minute webinar below, including a product demo by Klaasjan Tukker, Sr. Manager, Technical Marketing that begins at 20:00.

[1] Accenture, Growing the Digital Business: Spotlight on Mobile Apps 2015

Generating Server-side Logs to Troubleshoot On-premise Connect Installations

In order to diagnose unexpected behavior within Adobe Connect, it may be necessary for the Adobe Connect Support team to examine server-side logs from an on-premise Connect deployment. The logs directory is located in the Connect (or Breeze – it is not uncommon for Connect upgrades reside in legacy Breeze directories) directory:

Within the logs directory there are sub-directories containing various logs:

The most commonly requested log by the support team, is the debug.log. It can be found in the logs>support directory. With the services running, the current debug log will appear without a date at the top of the debug.log file list. The default rollover is 12 hours generating AM and PM logs each day:

In order to make the debug.log file more useful for purposes of diagnosis, you can enable verbose logging by adding entries to the custom.ini file located in the Connect or Breeze version sub-directory. Here you see it located in a 9.3.1 directory under the Breeze root installation/upgrade directory:

Before editing the custom.ini file, be sure to create a backup copy of it. Add the following lines in order to enable verbose logging:
Note that for versions of Connect 9.2 and prior, use yes instead of true:
Save the custom.ini file (be careful not to accidentally change the file type to .txt) and during a scheduled maintenance window, cycle the Connect and AMS/FMS services in order to load the changes and begin verbose logging (note this will bring Connect down while the services cycle):

There are rare occasions when it may be prudent to provide more than one log for a more complete diagnosis. To provide a full sample of the various Connect logs without sending a massive historical sample of log files, you may simply stop the Connect services (during scheduled downtime as this will bring down Connect) and rename the entire log directory to log.old. Then upon starting the services back up, recreate the issue being diagnosed and then stop the services.
This activity will provide a new small log directory isolating the issue under scrutiny: Zip/compress this new abbreviated log directory with all its fresh abbreviated sub-directories and provide it to the the Adobe Connect Support team to help expedite server-side analysis. This option is particularly helpful when examining a cluster as each server will have a set of logs. When providing cluster logs, always label each compressed log folder to easily identify the server from which it came.
Note that often when diagnosing unexpected behavior in Adobe Connect Meetings, it may also be prudent to enable client-side Connect addin verbose logging as well.  The relevant client-side logging tech-notes are here:
Enable logging | Meeting Add-in
Troubleshooting Verbose Meeting Addin Logging