[Logo] Jaikoz and SongKong Forums
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Messages posted by: toyzrme  XML
Profile for toyzrme -> Messages posted by toyzrme [15]
Author Message
Hi -
Sorry - life got busy!

I'm on Windows 7 x64. I see the settings in my User\Jaikoz directory, so I made a copy of this directory.

However, when I run the 842 x64 installer, it says "Incompatible installation detected. Uninstall, or choose another directory to install to."

I ran the installer "As Administrator", too, but got the same error.

I have Jaikoz 6.1.0 (1132) installed in the default location (C:\Program Files\JThink). I have some older versions installed nearby, e.g. (C:\Program Files\JThink\Jaikoz - 55, and similar).

Thoughts?
Hi -
LOVE Jaikoz (pro) - it saved my library, as it was basically unusable. 2 years ago I spent many hours using Jaikoz, loving how powerful and easy it was.

I had my preferences all tuned up.... but haven't used it in 2 years.

I've also built a new computer.

So: how do I move & upgrade Jaikoz from 5.x to 8.4.2, without losing my preferences?

Can I literally just copy the settings over from my User directory? Or should I install 5.x on the new computer, copy over the settings, then upgrade to 842?

Or do I need to step through installing each version to keep the settings?

Thanks!
Just verified - no user assistive settings are enabled.
If I paste a cell value directly into a cell (ie without text editing it), the CPU spikes to 100% for 15-18 seconds, then returns to 0 until I change another cell. This happens for the Artist, Title, and Album fields, at least.

BUT...testing further:
- if I *paste* into the cell (ie, not editing it as a text entry field), then it DOES spike
- if I *edit* the *title* field and type or paste text in, this does NOT spike
- editing the Artist field is different - it still spikes the CPU when I hit Enter
- just doing a *copy* of the whole cell (not in edit mode) sometimes seems to spike it for a very long time

Clicking around, highlighting cells does not spike the CPU.

FYI I have 20K files loaded into 5.1.1 64 bit, using 1.2GB (out of 8GB). Core2Duo E6600. Files sorted by Artist.

I tried on x32 version, no problems - seems to only be x64. Did not have a problem with 5.0.0 or 4.6.3.

Thanks
Maybe - the CPU is fine when I'm moving my cursor over the window, but I have a new issue, which I posted into a new topic - this is a copy below...
---------------------------------
If I paste a cell value directly into a cell (ie without text editing it), the CPU spikes to 100% for 15-18 seconds, then returns to 0 until I change another cell. This happens for the Artist, Title, and Album fields, at least.

BUT...testing further:
- if I *paste* into the cell (ie, not editing it as a text entry field), then it DOES spike
- if I *edit* the *title* field and type or paste text in, this does NOT spike
- editing the Artist field is different - it still spikes the CPU when I hit Enter
- just doing a *copy* of the whole cell (not in edit mode) sometimes seems to spike it for a very long time

Clicking around, highlighting cells does not spike the CPU.

FYI I have 20K files loaded into 5.1.1 64 bit, using 1.2GB (out of 8GB). Core2Duo E6600. Files sorted by Artist.

I tried on x32 version, no problems - seems to only be x64. Did not have a problem with 5.0.0 or 4.6.3.

Thanks
FYI I uninstalled 463 using the uninstaller, deleted the 5.0 Program Files directory (since the uninstaller didn't work), and deleted the Users\<name>\Jaikoz directory.

Then I installed the 32-bit version (5.0), and it paints normally - so it's either the x64 version having troubles, the install, or the combination of 463/x32 and 5.0/x64 (and maybe locations).
Can I also install v5.0 x32 as long as I choose yet another install directory? (just wondering if it could be a 64-bit thing)

It seems the runtime files are self-contained, but just the settings are common?
Hi -
I was just about to load up 3,000 files for an overnight Auto-correct run, and on a whim, checked for a new version.

Excited to see 5.0, I downloaded the 64-bit version to run on my Win7/x64 Core2Duo box with 8GB. Since I had 4.6.3 installed in its standard place (32bit, so "Program Files (x86)"), and the directions said you had to either wipe the old install or install to a new directory, I installed 5.0 in the 64 bit "Program Files" directory (default), since it is a different directory.

It took longer to load than 4.6.3, and when it did come up full screen, the window was blank - just the frame. Playing around, I found some controls would paint if I hovered over them (like tabs, scroll bars, etc.), but I could not get the table/grid to appear.

Finally, I shrank the window (to less than 1/4 screen) - and the table painted. BUT, when I tried scrolling right, it became noise. Or, if I expanded the window far enough right, it turned to noise.

I think there are a couple of problems, but the scrolling behavior in the small window, *might* have happened when I hit the Artwork column (couldn't tell, because it turned to noise).

At that point, I went back and ran the 32-bit 4.6.3 version, as it was late and I wanted to do the run overnight.

Questions:
1) was it OK to just install the 64-bit version in "Program Files", with 4.6.3 in "Program Files (x86)"?
2) Settings: is it ok to switch back & forth like that? I did a quick scan, and I could swear some changed, and some did not
3) Any thoughts on the UI painting?

Thanks,
Bruce

PS Would it be ok to install Jaikoz 5 on another of my boxes at home while this gets worked out?
Great idea!
Love the way the auto correction tasks work so I can customize what I want done.

But I find myself wanting to do the same given set of tasks repeatedly, but different groups at different times (like I don't change the filename from metadata until I have fixed the metadata).

It would be nice if you could define more than one 'set' (profile?) of auto-correction tasks, then run one set or another, rather than having to reconfigure the one set.

Adding hotkeys to each group/profile would be great, too!
2b> Yes, the Changes pane is similar in concept - sorry, I was not familiar with this pane, as I used it incorrectly while first learning - the visible fields did not change when I clicked on the top pane, so I ignored it.

BUT, there are key differences:
1) orientation: my suggestion is to do this laid out like the top tables (fields running L->R, with 2 rows being the old and the new value), This would take less space

2) there is no highlighting of differences in the Changes pane (although easy to fix)

3) the fields in the Changes pane are not configurable (order or inclusion), meaning some important fields can disappear off the screen, and/or require scrolling

4) part of the power I love in the upper table is seeing the fields aligned vertically - values would be much closer using that style, than the way they are in the Changes pane. i.e. individual characters would be aligned - you could instantly see differences in field length, individual characters, artwork, etc. You could even make the row taller so that artwork could be larger for comparison, without losing too much more real estate. (comparing art in the changes browser is not easy)

The layout in the changes pane requires much more visual scanning: left-right, down, then repeat; this new way would be one scan left->right
- it's also about mental effort: the Changes pane means you have to read/remember one entire value, then read the other
- the new layout uses visual pattern matching (ie does the top shape match the bottom), which the brain is much more efficient at, no memory required. It's handled at a lower level in the the cognitive 'stack'

Example: in the current view/edit table, you can scan down the artwork column for an album and tell instantly if all the artwork is the same, or one is different. This is the efficiency I want to harness. If the text in all fields were the same, the scan could be done in < .1 second. Not so with the vertical Changes pane.

A further optimization to the above idea would be to eliminate the columns that were the same - thus more columns would fit onscreen without scrolling horizontally, with less visual scanning effort. Perhaps you could configure each possible field with an 'always show/only show when different' toggle setting (you might want to default the title and artist to 'always show', just so the user knows which track they're on if only looking at this new panel)

Again, *fantastic* interface already - this would just be icing on the cake and take it to the next level.
I just noticed similar behavior and saw this post.

A question that may help clarify: does Jaikoz do its' auto-correct only from the original metadata, eg in the file? IOW, if you do one pass, it fills in *some* data, then run auto-correct again (or just manually edit fields), will it pick up the new in-memory values, or the disk (original) values?

In my case, it looks like it only uses the values on the disk (ie the original values). So, if I update a field, SAVE IT, then re-run the auto-correct, now it gets better data (ie now it will find the year or art, whereas it did not before).
This happens with or without the (split) View Pane.

I have also turned off the Column Browser - no effect.

LOVE Jaikoz - an amazing amount of functionality packed in there! And the UI is extremely efficient - takes a little bit of learning, but any good UI for experts is that way - and Jaikoz is very efficient *and* useful.

ANYWAY: the *one* place I get lost is in scrolling and comparing hundreds of files. I love the interface - you can take in so much information in one screen, esp. the highlighting of differences. But it can be hard for my old eyes to track which line in the top corresponds to the one in the bottom, esp. for the currently selected track.

Some suggestions for a minor improvement in this area:
1) highlight the currently selected row, in both the top & bottom panes
Not sure how to do this, with all the highlighting already in play - maybe at least a heavy frame or underline? larger/bold font? reverse video?

2a) add a new panel to the bottom: a side-by-side (well, top/bottom) of the selected original & fixed data - maybe repeat only the two lines (old/new values) on top of each other, in the info panel at the bottom - this would make the deltas extremely obvious, and make scrolling through with cursor keys easy

2b) same as #2a, but only show those fields that are changing in the bottom panel (ie, hide columns that are the same). But you might want to keep track name and artist regardless, for identification!

Anyway - great product - this would be icing on the cake!
Whenever doing anything in the Jaikoz UI, the CPU spikes - editing a field, or even just waving my cursor over the screen will peg one core for as long as I wave the mouse. If I'm playing a track, it will stutter because of this, making it very hard to review tracks. It's like the CPU is doing all the UI drawing, not the GPU.

Running the latest (4.6.3 NGS), Pro license.
Machine is Core 2 E6600/2.4GHz, Win 7 x64, 8GB RAM. CPU w/o Jaikoz is < 10%. GPU is nVidia GeForce 510 with 512MB RAM.

Ideas?

Thanks.
 
Profile for toyzrme -> Messages posted by toyzrme [15]
Go to:   
Powered by JForum 2.1.6 © JForum Team