Those things, and to imply that it is would be a disservice to everyone. Or a project that is more specifically user-directed. I canĬertainly see how Uservoice would benefit a community-developed project, It's only one small part of the decision. Most important factor in determining whether we add a particularįeature to QLab. It's certainly true that we said that to him, and that was definitelyīut it is not true that the number of people requesting a feature is the Values, he was told that not many people have requested this feature. He mentioned that when he first asked about fading OSC However, I think something that Søren said is getting taken out of We get plenty of feedback, all the time, and we read itĪll and it's very useful to us. With the greatest respect, we do not feel that we are lacking input from Its not a protest, just a positive acknowledgement that it would help a lot with this high resolution, easy to transport control signal that is also easy to convert into almost any other control signal. – That lead to the call for other users wanting this feature to chime in :) Im pretty sure I wrote the first email about OSC cues (maybe trough/with Ole Kristensen) before the premiere of “Timemap #3” ( ) in april 2008 but if i’m wrong then my bad! The point is that I have been advocating for this for circa 6 years, and it seems that a bigger voice is needed to make it happen. I have never had doubt about your intentions or ability to implement new features, but I have gotten replys in the past that suggested that you did not have a lot of users wanting this, and therefore you did not priotize it (wich is fine and understandable). I wanted you to know that there is a crowd who needs this feature more than most new features. But for very important applications, I prefer something more…developed.I never meant to make it sound like you dont want to listen to your users. Maybe this will change in future version, but right now I can't recommend it fully - although it's a great program. Also I got the strange "blocks"-problem… But it's hard to reproduce, got it only once on a 6h show…But I'm not so sure if I consider QLab again as my media program, as there were just too many bugs and workarounds at this state. The problem has to come from QLab, because after the output of the computer we make a softedge in arkaos media master, and the blackout was on both screens (but not on other screens going through the same media master pc). But for example a still image was flickering after standing still for several minutes, with no touching of the computer, only 2 still images showing (and the other image wasn't affected. But I still got some issues with QLab, but the are hard to reproduce. So, not too bad after all, in normal shows, the computer doesn't get too hot and it doesn't stutter anymore. Video takes a lot of computing.ĭoes the problem go away if you're playing back to only one screen?Īlso, I do not recommend using 3.1.2 at all. It's entirely possible this is not enough computing power for what you're doing. Hm, that's four displays off one machine, with an unspecified number of videos composited to the three display screens at any one time, at unspecified file resolutions and codecs. > PS: Using 10.9.4 with the newest, fastest macbook pro retina out there. And as is it working as it should from time to time, it shouldn't be an issue that the computer is too slow. If I knew exactly when the problem appears, I could avoid it, but I can't. I open QLab, fire the queue and it's ok, but next time it's not ok. It's very random, I just can't figure out, what triggers the problem. > I am also already using auto load, and it does help - but just not every time. Unfortunately updating to 3.1.4 didn't help to solve the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |