Hi, So far I couldn't find the answer: will Walter allow (much) larger font size for all the time info of the Transport (Start/End/length time of selection etc.)? I rely a lot on precise time selection so this is an important point to me, and I can't understand why the font size remained so tiny when so much is customizable, and given that the Transport itself is resizable at will... It's the only 1% that doesn't satisfy me in Reaper, and I come from Samplitude-Sequoia / Wavelab. (an alternate proposal for those info: "Enhanced Big Clock Info" at )
Agreed - it can't be done, and that is a bit of a problem.
--------------------- 1995 325i coupe, Superchipped, Mania RVR 18" alloys with 225/40/18 Continentals. Full M Tech kit(no sideskirts yet), M3 mirrors(not fitted yet). Kenwood KDC-MP6090R MP3 head unit, Kenwood C-717 10 x CD autochanger
I have this problem as well. In post production I deal with start/end and lengths quite often, and this is making me move a lot closer to the screen than I like whenever I need to read off this information.
--------------------- ReggaeRacing.com's Track Car Build Thread
Hi everyone!first post on the alpha here. Talking about the transport, is there a way to implement in WALTER that the transport shows in which region/marker you are currently in?. I say this because when I mix I like to fill my screen with the mixer so I'm not looking at the TCP. So if I could see if I am on the second verse and not the first one just staring at the transport it would be gold for me. What ya think? many thanks! JP
For the love of god.. or reaper himself... this concern has to be addressed! I have 300 files to be edit into 5 sec files each.. and I need to check every file for its duration. My eyes are going blind due to the constant squinting..
--------------------- Hey man, I'm a professional!
This is from the toolbar thread, but it's appropriate for this thread. I've always had a problem with how a lot of DAWs display selections and the length thereof. Either it was a left-to-right list like Reaper, which takes a long time to scan like any long string of numbers, or it the timecodes were simply dumped right on top of each other, with start, end and length looking the same just above each other. The length however is not a timecode position. It is provided so I don't have to read both the start and end timecodes and make my own calculations. It therefore pays to have it stand out apart from the timecode position values. Thus, an attempt at separation resulted in this illustration : The reasoning behind these design choices :Start and Length are referenced more often by the user than the End. Even if that is not the case, the user will learn after a short time that the big number at the top is always the Start timecode and the Length is the big number at the bottom. Visually the difference in height are a hook in to recognizing what those values are at much greater speed than those timecode values being of the same size. When size becomes an aspect by which those values are identified, the user will reference the text descriptions less often, or even not at all. The bounding box has no boundaries at the top and bottom to lessen the visual clutter in an area the user has to use high concentration to scan for numerical values. As the user is scanning from top to bottom first, that first scan must be as easy as possible.