INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Expression functionality changed, or possibly bug...  (Read 1538 times)

zirum

  • Galactic Citizen
  • ****
  • Posts: 403
  • still learning.
Expression functionality changed, or possibly bug...
« on: April 04, 2007, 03:19:19 am »

Is use an expression in "rename files from props" in order to set a subfolder of Disc # if the tag is present. I haven't used it in a while, and had lost the expression. When i now tried to write it, it had a kinda strange/inconsistent behavior.

If i use it in on a colum, i may write the folowing:
If(IsEmpty([Disc #]), Disk # not defined, Disc # defined)

But if i used it in the "rename..." i must use the following instead:
[Album Artist (auto)] - [Album]If(IsEqual([Disc #],Unknown Disc #),, \Disc [Disc #])

In the last case the [Disc #] is not empty, but Unknown Disc # instead. Is this by design? Or is it a bug?
Logged
Note to myself: Read, think, write - Read, think, write - think, read, write - think, write, read - think, write, read... Aahhw, i always mess that up...

marko

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 9139
Re: Expression functionality changed, or possibly bug...
« Reply #1 on: April 04, 2007, 03:34:28 am »

I never had much joy when using inline expressions like that. You don't mention if that is the entire rule, or just an extract from something more complex, but either way, if it were me, I'd be more comfortable coming at it from this angle:

if(isequal([disc #],unknown,8),[Album Artist (auto)] - [Album],[Album Artist (auto)] - [Album]\Disc [disc #])

-marko.

zirum

  • Galactic Citizen
  • ****
  • Posts: 403
  • still learning.
Re: Expression functionality changed, or possibly bug...
« Reply #2 on: April 04, 2007, 06:37:09 am »

I have the tendency to try writing the least amount of chars:)

What i am wondering about is why the IsEmpty works on a column in a view (because field then is empty), but not in the "rename..." (there it's 'Unknown Disc #'). Is there some kind of logic of when empty fields will result in a unknown etc. text?

The expression is as i use it. Not a part of something bigger.
Logged
Note to myself: Read, think, write - Read, think, write - think, read, write - think, write, read - think, write, read... Aahhw, i always mess that up...

zirum

  • Galactic Citizen
  • ****
  • Posts: 403
  • still learning.
Re: Expression functionality changed, or possibly bug...
« Reply #3 on: April 05, 2007, 07:08:34 am »

Any ideas from the JRiver team?

Why is a a empty [Disc #] tag equal "" in a column expression but "Unknown Disc #" in the "rename files from properties"?
Logged
Note to myself: Read, think, write - Read, think, write - think, read, write - think, write, read - think, write, read... Aahhw, i always mess that up...

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42372
  • Shoes gone again!
Re: Expression functionality changed, or possibly bug...
« Reply #4 on: April 05, 2007, 08:35:43 am »

Any ideas from the JRiver team?

Why is a a empty [Disc #] tag equal "" in a column expression but "Unknown Disc #" in the "rename files from properties"?

This is by design.

Rename files from properties will use "Unknown xxx" for blank fields.

You'll have to use if(...) statements to work around it if this is a big deal.
Logged
Matt Ashland, JRiver Media Center

zirum

  • Galactic Citizen
  • ****
  • Posts: 403
  • still learning.
Re: Expression functionality changed, or possibly bug...
« Reply #5 on: April 06, 2007, 05:40:40 am »

Thanks for the reply, matt.

It not that it's a big deal, but just wanted to have an idea of when to expect what, instead of testing every expression under each circumstance.

Sorry if i seemed a bit picky...
Logged
Note to myself: Read, think, write - Read, think, write - think, read, write - think, write, read - think, write, read... Aahhw, i always mess that up...
Pages: [1]   Go Up