music2bmade
-
Posts
31 -
Joined
-
Last visited
Posts posted by music2bmade
-
-
On 11/20/2019 at 3:41 PM, Duncanwh said:
I have been working on a fairly long document, about 55,000 words. If I type in a sentence, perhaps just 10 words, it’s more than one and a half minutes before the sentence is entered into the page. A few corrections might mean another minute’s wait. It’s ridiculous. I have had to go back to InDesign on this document until something improves.
Did you ever mention what machine you are using? I had very slow performance (Almost unbearably so) on my Mac Mini Late 2012 until I started running my OS from an SSD drive. Now the programs fly open and are very responsive.
-
1.81 Same problem here. Nasty. Had to start completely over several times.
Will have to avoid typing in the search tool for the fonts.
-
3 hours ago, garrettm30 said:
That might depend on the music program. Finale used to (does it still?) have installed fonts for that purpose. It mucked up the font menus of all other programs with irrelevant fonts, but perhaps it would mean you could place a PDF in Publisher more reliably.
Thankfully, for all of my Finale work, my clips are saved as tiffs and so are no problem whatsoever in Publisher. It is when I get a PDF from an outside source that the problems arise, probably due to a missing font.
If the ability to read embedded fonts in PDF's is not included in Publisher I would call this a "bug." It defeats the whole purpose of a PDF which is file sharing and keeping formatting intact. (And every other program BUT Publisher seems to have no issues with PDF's) -
I am seeing strange font discrepancies in PDF's too, that none of my other publishing programs (Pages and Swift Publisher) are struggling with. Sometimes a word will be on a whole separate line from where it is supposed to be. Publisher is acting like it can't find the font and is doing substitution. PDF's should have the fonts embedded and thus never be lacking for those fonts, true?
I can't attach any files because of copyright. (My files are music saved as PDF's.)
My workaround has been to use Preview in Mac to save the file as a tIff which Publisher reads perfectly.Other than this issue I am REALLY enjoying this program. I am doing less and less on my other publishing apps.
-
You have outdone yourself!
I have been using the beta for some time now but I had no idea the worlds of creativity that would be opened by your Studio Link feature! Even by itself, I have really enjoyed Publisher but the Studio link is jaw-dropping and seamless.
I am now an Affinity fan for life!
-
Opening a file which contains missing links will ask "Do you want to locate..." If you locate the file it still is pixelated on the screen and does not print.
Using the replace feature in The Resource Manager seems to be the only way to get the file to show and print correctly. Importing the file again works as well.
As a test, I tried opening a brand new document, adding an image, saving the file and then deleting the image. When I open the document again it says the resource is missing, do you want to locate it? If I locate the file it still does not show correctly in the document nor does it print.
Basically the "locate feature" when opening a Doc with missing files does not work.
-
Definitely fixed in the latest betas. Thank you!
-
Did a complicated document this past week after the update. VERY smooth sailing. Can’t wait for the release!
I have used or tried many publisher style programs. This one is so much better than any of the consumer level programs.
Great work on bringing something better to this market.
-
I get crashes when:
- Pasting text into frames
- trying to change the font in a frame
- Selected all text in a frame
Tried making a brand new document. (Was using an older version file. last stable version before this.) Still get the same crashes. Everything really worked beautifully until I started pasting text. Even removing the formatting of text before pasting did not solve the issue.
-
Initial response: Ugh, another Beta
Second response: One step closer to final release!
Your other programs are so fantastic and stable. I expect it took a tremendous amount of this type of work to get them this way. Thank you for your hard work.
I am really liking the responsiveness and interface of Publisher. The last project I did came out great. I am dying to replace all my old stuff with it.
-
Sorry. I deleted the file. My doc was made from a very old version of the beta. I think whatever problem it was has been fixed because new docs are working without problems. There were no issues on a complete project that I worked on yesterday.
-
1 hour ago, Old Bruce said:
I can get tenths of a point adjustments here, maybe higher precision but I doubt that would be useful in real world situations.
Just created a brand new doc and the problem went away even with Align to Baseline checked. Before and after paragraph does incremental spacing as I expect.
I have had this template through the various betas so I could play with the program a bit. Maybe it is corrupted. Knowing your docs are working as expected made me wonder if this doc was any good.
-
Thanks for your response! Even with "align to baseline grid" unchecked the paragraph spacing is still augmenting by leaps and bounds.
This does seem to be some type of snapping behavior. Whatever it is, I don't think it should be the default behavior. Every other program I use allows for precision adjustments.
I have also tried making the font in the paragraph exactly the same size and font, just in case font or font size was an issue. -
In other programs I use when I increase the before and after paragraph spacing the spacing between the paragraphs increases incrementally. In Publisher nothing happens for quite a while until I have entered 5 points or so and then the lines jump a considerable amount. Is this a bug or am I missing something?
This behavior is a bit of pain when trying to precisely set up lines to fit.
-
It has been fun watching this program develop. At this time (Beta version 1.7.0.140) this program is already miles ahead of other programs I use. It is faster, more responsive and the font tools are second to none. Desktop Publishing is so complicated, and to take your Designer idea and translate it into a Publishing app is just brilliant. The separate layers for each page is not something I have ever seen.
I am waiting with bated breath for the final version. This last beta seems to be awfully close to being ready for Primetime.
Kurt Weber -
I think it is the fault of the font manager. It is too slow activating the font. Old 32 bit apps like Pages 09 have no problem. Font Reserve (which I love and use) has always seemed slow in activating fonts. Activating 900 fonts (I admit, I am a font junkie) takes about 2 minutes. Activating one font is fast but not instantaneous.
-
I bet if you quit and reopened the Publisher file you would see the font correctly.
I don't know this for sure but it seems that some programs open so quickly that FontExplorer has not had enough time to activate the font. Autoactivation works, just not quick enough. -
All the font managers do is activate/inactivate fonts. There is a simple test.
Make a Publisher doc with unusual fonts. Save the file. Open Suitcase
deactivate the font
open the Publisher doc and see if suitcase activates the font automatically.
-
On 9/23/2018 at 1:20 PM, powderizedbookworm said:
Basically the question. What is this program for?
If I'm missing something, I would be so grateful if someone could point me right!
The problem that I have always had with Word or other Word Publishing programs when doing graphic design layouts is that they use objects poorly.
Instead of long strings of text, a graphic design uses objects, including text blocks to be place attractively on the page. Programs for weddings, flyers, brochures can certainly be done in Word Processing programs but they are awkward. Apple's Pages is probably the only exception I have seen. It can easily be changed into an object-oriented graphic design program.
Design programs Like Affinity Design can certainly be used to create a multi-page book or program, but they are awkward in handling multiple pages. Creating one page at a time and then printing them one at a time is pretty painful.Enter Publisher. It has the ability like Designer to create cool pages but it has multiple pages and each page has its own layers. (A feature I am extremely excited about.) At the end you print out a 10-200 page booklet or wedding program with ease. For me Publisher completes the trilogy.
-
Still trying to wrap my head around the assets section in Designer.
-
6 minutes ago, rjvela82 said:
Yes it make sense. So taking a step back, how do you setup InDesign to not use Global Layers being that both ways are beneficial? I have never figured it out if there is a way.
I haven't seen a program that had anything OTHER than Global layers. I am very excited about this feature in Publisher.
-
14 hours ago, Peg11 said:
If you click on the Alignment button on the toolbar you will have several choices of how you want to align an object if you click on the "align to" arrow on the right. Two of them are to page and align to page margin.
It took me awhile to find this window as well, because it wasn't activated in the button I put on the toolbar. I had chosen the customize toolbar and added the the center button to the toolbar.
Again, my concern to the developers is that the default setting, or at least I think so, should be be set to "page".
-
I am suggesting to the designers that they start with it on. Most text programs have some sort of easy access to a ruler with tabs. I found it eventually and like how it works.
-
11 hours ago, Fixx said:
They are two totally different things. I seldom use layers in layout work but it is often essential in making language versions.
Interesting. Until you said this I couldn't think of reason we NEED global layers. They could be very useful in multi language docs, especially large ones. (Eg. Turn the English text layer off, turn the Spanish text layer on and print.... etc.)
Crashing after non-existing font search
in V1 Bugs found on macOS
Posted
Not getting this problem in the newest update. Looks like it is fixed.